Thursday, February 28, 2019

Selective deletion logs – reviewed outside RSA1

Selective deletion of data in InfoProvider can be performed on manage screen in RSA1. There is a tab called Content and button Delete Selection that allows this activity. This button displays a pop up window that contains several other button for particular activities.

Main function of the popup is behind Deletion Selection that allows entering selection for the deletion. Once this is done, a job can be setup that will perform physical deletion.

Another button of the popup that I want to focus on is called a Log. This displays an ALV grid display of all selective deletions done on particular InfoProv in past. The grid can be further drilled down to details of each deletion.  Thsi shows all condition/selection that was used for deletion. 

Sometimes I want to evaluate deletion logs outside the RSA1 t-code. In order to this there is a Function Module called RSDRD_LIST_ACTION_LOG. Via the FM for which just InfoProv needs to be provided as input parameter the same ALV grid with the all selective deletions done on particular InfoProv in past is displayed.

The FM has another input parameter that is optional called I_WITH_AGGREGATES. This enables to display aggregate deletions at InfoProv as well.

Table which stored deletion logs is called RSDRDLOGHEADER. This si a header table with info on who, when, which InfoProv, Delete Mode and number of records that were deleted.

Detail information on which fields were used for the deletions is stored in table RSDRDLOGPOSITION. Key which links both tables is POSITION_ID.

Monday, February 18, 2019

Loading large flat files via SAP GUI into BW

Recently I needed to upload a large flat file into BW object. A size of the file was above 100MB. I was using classical data flow for uploads of the flat files. Means the file was uploaded via infopackage to PSA. From there there was a DTP to upload it further.

When I ran the upload to the PSA I got following error in the upload monitor:

Not enough memory for Data Provider
Message No. FES013

SAP GUI file functions have a limitations on the size of file to be uploaded / downloaded. That was clear to me. However my impression was that the issue can occur with the files a way too larger than just 100MB. However when I did a split of the file into smaller chunks I realized that ideal file size that work within any issues is below 20MB. Which is quite small portion of data. I used SAP GUI version 740 which is quite new. Therefore this finding was a surprise to me. 

Within SAP Note 875871 they mention that this limit is tied to user workstation where SAP GUI is running. They specifically mention that issues are present when there is only 1 or 2 GB of RAM available at user workstation. This wasn’t really my case as I worked with laptop having 8GB of RAM.

All in all it is quite surprising that in today’s age of big data there is such issue. Only solution is to either do split of files to smaller chunks (ideally below 20MB) or upload the whole file into application server of BW and upload it from there.

More information:
875871 - DP: Memory bottleneck when you upload very large files