difference between request download and initial download
- The initial load will use a task type modify just as the request load did, prior to our activities to enable it to insert or update subtractively, i.e. the initial load will never delete but only add.
- No matter what the selection of materials looks like in CRM Tx R3AC1 (adapter object ‘MATERIAL’) at the time you start an initial load via CRM Tx R3AS, the processing of the last block information of that initial load will not only set its status to ‘Done’ in the initial load monitor (Tx R3AM1), but it will also activate the delta load for all materials (according to filters in R3AC1).
Details: It will link the object ‘MATERIAL’ to the RFC destination of the corresponding ERP system in CRM Tx R3AC4, which in turn has an impact on the event link in ERP table TBE31 (event 00001250).
- An initial download brings the selected range of materials into CRM. Further changes or new materials in the range would come with the delta upload.
- A request download for specific materials would bring the current data from ERP for those materials. This should work without any initial download. One usecase is an inconsistency between ERP and CRM due to any reason.
We had a transaction dima for this, but I am not sure if it still exist.
