This scenario and Fixes are applicable only if you are using just a normal query transform to pull the SAP table records in BODS staging tables.
In a normal scenario,we pull the SAP table from the data store and make it as a source and a query transform to transfer the required fields to the target table. If you double click the SAP table which you have pulled inside the designer area you can see a check box “Execute in background (batch) “unchecked. – Thanks to Dirk venken on pointing this out.
When the table extraction job is executed in BODS, what happens in SAP is, it will be executed in one of the application servers (If you have many) Work processes. Execute transaction SM51 in SAP and double click on the app servers and check on the active work processes using the BODS system user ID as a filter to see what operation is getting carried out.
Program /BODS/* will be executed for extracting the data from SAP , but the main point to note here is SAP will execute this processes ,i.e. this table extraction process through a dialogue work process. Dialogue work process in fine when the data volume is minimum and for relatively smaller tables. But it’s always advisable to go with the back ground process, Rather than the dialogue one if the operation is going to be resource intensive and high data volume operations.
Due to this, large tables like BSEG, EDIDC, EDIDS, etc. will run for the longer time or will be terminated with an ABAP dump or core dump in BODS. (Unless you have logically separated the data extraction based on multiple filters for same table in different query transforms and finally merging them in to a single table, this could be a pain where your BODS job might go for changes frequently when the filters needs to be modified.)
In order to make this extraction run in the back ground processes we need to mark the check box “Execute in back ground (Batch)”. Once you check this and re-execute the job, you may see this error in the BODS job log “RFC_ABAP_RUNTIME_FAILURE – Exception_Key: READ_REPORT_LINE_TOO_LONG”
The reason for the dump is SAP System is trying to read the program /BODS/JOB_RUN in to a structure PROGTAB-Line has a length of 72 , but Program /BODS/JOB_RUN has lines width > 72.
The following note is available in the market place and if the pilot note suggested by SAP is not applicable to your version, open an incident to request Product Support release the note for your organization.