I understand
We have to make something here as well because these tables are huge and take a lot of time to get all data.
Those notes where indeed implemented, but the issue is with the transport of the abap program itself.
When we keep the default $TMP he is uploading into the system (abap exists, we checked) but the transport is empty. So he is not making the right link between the transport and the function/functions that should exist in it.
When we change the $TMP to the correct development class they are using for the ‘normal’ ABAP team, it results in the error 1723420 - Unable to load DS generated ABAP into ECC: error code <RS_CORR_INSERT:1>
But the attached aw_upload in that note seems older then the one delivered by SAP in the installation folder of BODS 4.2
We tried first the one of the installation folder but that failed.
Last attempt will be now the attached file and if that fails as well, then we have no other option than to file a new ticket.
aragornII (BOB member since 2006-12-21)