SAP BEx Connector | Load fails with Field Not Found
Article Number: 000049368 | Last Modified: 2018/11/21
Load fails with error Field Not Found using SAP BEx Connector. Upon limiting the outcome to lesser number of records, this error ceases to occur.
SAP Connector 6.1 and above.
There is a limitation on mass extraction using BEx queries from SAP. See below section from our documentation.
Memory consumption A common problem with the BEx Connector is that the SAP BW system runs out of memory when executing a load script that extracts a large amount of data. In general, SAP claims that BEx queries should not be used for mass data extraction. This is discussed in SAP Note 1968598. How much data can be extracted at one time depends on the allocated memory on the app server where the SAP BW system is running. A common configuration is to have 2GB of memory available, which should allow an upper limit of approximately 500000 cells per extraction with the BEx Connector. There can, however, be other factors besides the amount of extracted data that affects the memory consumption during query execution. This is discussed in SAP Note 1879725.For other possible causes refer article Qlik BEx Connector Field Not Found Error.
If large amounts of data will be extracted from BEx queries, it is important to test the capacity of the SAP BW to make sure the extraction will not fail in production. It is possible to increase the query execution capacity in terms of data volumes by increasing the allocated memory in the SAP BW system. Make sure the BEx queries that will be used have variables that can be used to reduce the data volume, such as variables for time slicing (year, month, day). Limit the number of records using these variables.