Delta load of customer from R/3 (ECC5.0) to CRM5.0

Question

We have done an initial load of customers from ECC to CRM (R3AS). A change is done on a customer in ECC. I expect the changes to be reflected in CRM as a delta load. I do not see the changes. What am I missing?
All responses are appreciated and will be rewarded.

Answer 1

Hi Mani,
Here are some clues on how to proceed with processing of incomplete or failed BP deltas:
First of all you have to note that during the initial download, no delta download can occur. In particular, no delta download of customers occurs if the initial download of materials occurs at the same time. This is because the material download depends on the customer download.
During the delta download, the CRM system uses the inbound queues R3AD_CUSTOME<nnnnnnnnnn> where <nnnnnnnnnn> corresponds to the customer number in the R/3 system. If an error occurs during the download, the inbound queue for this customer is stopped. You can see the error messages in the flow trace. For the delta download, you have the option to use Transaction CRMM_BUPA_MAP for the error analysis. If you enter the customer and press Enter here, you can display the business partner number for a customer and all open BDocs (that is, those which contain errors or are being processed). To do this, you only have to click the 'Queues and BDocs during download' pushbutton. The system issues an overview of the queue and the open BDocs for this customer and in particular, you can 'look into' the BDoc. As a result, you return to the flow trace and you can display the error messages which occured as described above. During the delta download, you have the option to send the same BDoc again. This is useful if you can simply solve the problem by correcting Customizing in the CRM system. To do this, you simply click the corresponding icon in the flow trace (currently, this is the second icon from the left).
If you have to correct the error in the R/3 system, you have to delete the existing BDoc since it cannot be processed further. As a result, the inbound queue in the CRM system is released again. In this case, you are recommended to delete all existing open BDocs and to make the changes in the R/3 system.
If inconsistencies occur between the R/3 system and the CRM system, you can start a request for the customer. To do this, click the 'Get customer from the R/3 system' pushbutton. This starts a request which uses the inbound queue R3AR_CUSTOMER. Process possible errors as during an initial download.
If you still have problems and don't know how to fix, please post more specific information from the BDoc queue, such as what error message you are getting. It helps us better identify the problem.
Regards,
Rahul
PS. Please award points if it helps!
PPS. For future reference: this info was found in note 362621: Error drng data exchange customer<->business partner