Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all, when I'm trying to extract from BEx queries using BEx connector in QlikView I've been encountering the below error from screenshot.
I was told that job is not created on BW side, just a dump was created. (I don't have much expertise on SAP side)
(https://community.qlik.com/t5/Official-Support-Articles/Qlik-SAP-Bex-Connector-Exception-condition-...) I've asked them to check the possibilities from this post but they've ruled these out as for a different set of selections in the same source I'm able to extract data.
please suggest me on what I could try to resolve this or what could be the possible reasons for this.
thanks in advance.
The issue likely lies in the query design or selection conditions. Since other selections from the same source work, you can try this:
Ensure the failing query doesn’t contain complex variables, custom exits, or calculated key figures that may break during extraction.
Ask your SAP team to check the short dump details in ST22. This can pinpoint whether it’s a connector issue or something in the query logic or variable resolution.
On the Qlik side, enable verbose logging for the SAP BEx connector. This may provide more context on where it breaks during the handshake.
Open the same query in BEx Analyzer with the exact selection. If it crashes there too, it confirms an issue in the query or variable processing.
The issue likely lies in the query design or selection conditions. Since other selections from the same source work, you can try this:
Ensure the failing query doesn’t contain complex variables, custom exits, or calculated key figures that may break during extraction.
Ask your SAP team to check the short dump details in ST22. This can pinpoint whether it’s a connector issue or something in the query logic or variable resolution.
On the Qlik side, enable verbose logging for the SAP BEx connector. This may provide more context on where it breaks during the handshake.
Open the same query in BEx Analyzer with the exact selection. If it crashes there too, it confirms an issue in the query or variable processing.
Hi , Thanks for the reply!
I tried following your suggestions , there was no error in ST22 as well indeed the issue was with Query design.
But when we tried to check in BEx query definition there was a condition that the 'period from' value should be a closed month, so the extracts werent working. Now with a different range May-December in which May is a 'period from' which is a closed month I'm able to make these extracts.