- SAP Managed Tags:
CRM Middleware integrates various data producers both SAP and Non-SAP systems with the SAP CRM landscape.
This document gives you a basic introduction on middleware monitoring on erred BDOCs and reprocessing it to clear the queues. Document restricted in finding the queue names and error segments of the BDOC. Hope this document serves the purpose at some point of time. Thanks and happy reading. Feedbacks are welcome!.
Step1: Start SMW01 with the following settings.
Choose ‘Errors’ in ‘Bdoc State’.
On execution, BDOCs with mistakes can be seen.
Relevant BDOCs for monitoring at a particular customer were the following
BUPA_MAIN Contains the master data of a business partner (triggered on creation and change of a business partner)
BUPA_REL Used when you create a relationship between two business partners
PRODUCT_MAT Used for data exchange of products/materials
CRM_EQ_DMBDOC Used for data exchange of equipments
BUS_TRANS_MSG For data exchange of transactional data
Step2: Selecting the particular row of the BDOC with error and click on the extensive data button.
Step3: Extensive error data segments.
Step4: Data error segments further navigate into segments in details. 
Step5: Number ranges for contact persons are different in CRM and R/3 systems. For customer the business partner number is the same in both CRM and R/3.
Lookup for Business partner (Customer/Contact Person/Employee) BP
Lookup for Customer in R/3 XD03
Lookup for a Contact Person VAP3
Step6: In order to know who created, for example a business partner in SAP CRM, you can look up this information in table BUT000 via transaction SE16.
Step7: Using transaction SU01/SU01D we can see who the user is.
Step8: Reprocess the BDOC is necessary to further send/receive the data segments.
Cheers,
Vivek Raj Kumar M.
2 Comments
| User | Count |
|---|---|
| 16 | |
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
