One of most common error when using SAP Bex Connector is that the session could run out of memory. Thus, loading scripts could fail throwing different message errors (as example see extract below):
-------Extracted from logs---
Error in GetTables: No more memory available to extend an internal table.
07:12:51,925  - Error: RfcAbapRuntimeException
07:12:51,925  - BexConnectorDataReader.Read() - Error occured during read!
System.Exception: Exception ---> System.Exception: RfcAbapRuntimeException ---> SAP.Middleware.Connector.RfcAbapRuntimeException: No more memory available to extend an internal table.
When sending a request to SAP, a task is allocated to a process. Each process has a certain amount of memory allocated to it. So even though the server has enough memory, when using Bex Connector, it is possible to run out of the session memory
One of common procedure that could be used to exclude QlikView scripts syntax error, is to ask the SAP Admin to run "ST22 transaction" and analyse possible existing dumps to determine if the error is due to insufficient memory.Ex
: TSW_NEW_PAGE_ALLOC_FAILED or TSV_TNEW_OCCURS_NO_ROLL-MEMORY found in the result of ST22 transaction indicate a memory issues.
An additional test is to ask the SAP admin, to run the same query that failed in QlikView using RSRT transaction.
Once the issue with memory is confirmed i.e. "session run out of memory issue", simply limit the amount of data rows extracted by using variables
or select less granular dimensions.
For more Qlik SAP Bex Connector limitations click here