this is a first post in a series of middleware monitoring related activities in the context of BDoc Type BUPA_MAIN. Do take into account that some of the posts may no longer be relevant, as it really depends on the release you are currenlty working in. Nevertheless, I consider them useful for anyone who wants to learn more about BDOC monitoring in SAP CRM.
BDOC Type: BUPA_MAIN
Error message: Business partner with GUID XXX does not exist
During replication of a Business partner (customer/contact person) from R/3 towards CRM something went wrong.
Via Bdoc Monitoring (transaction code SMW01) you see the following:
In the first line you see the impacted business partner number: 0000120547
This might sometimes trigger another error message to turn up. In case of other relevant error message, first resolve the error (probably located in the R/3 system – for example in the case of an invalid email-address).
If the error message still stays the same, you should try to download this business partner again from the R/3 system.
Launch the transaction CRMM_BUPA_MAP.
Fill out the R/3 business partner number and press enter.
Normally, if the business partner exists in the R/3 system, the GUID will automatically be filled in. Next, press the button “Gather information about customer”.
Next verify via SMW01 (for Bdoc Type BUPA_MAIN) and select “5 minutes”.
If the Bdoc status has a green colour, the business partner was correctly downloaded.
You can delete the previous Bdoc for this business partner which had the error.
In the CRM system you can look if the business partner does exist in table BUT000.
The SAP University Team