bdoc monitoring guide

Business Process Document

SAP CRM BDoc trouble shooting guide 07 Jul 2011 Confidential

Page - 1 - of 6

1.0: Business Process Requirement

Bdoc (Business Document) is a logical Object. It is envelop of all business data that is necessary to run a

business process.

Every Business Object, which transact with application database to write data needs a BDoc. Every

Business object has its dedicated Bdoc.

A Bdoc contains different sets of data partitioned in terms of segments. Segments are mapped to tables.

Below is the Structure of Bdoc:



Page - 2 - of 6

A Bdoc can have different statuses. Below are the different statuses of Bdoc.

Transaction codes used in Bdoc trouble shooting:

Transaction code Description

SMW01 Display Bdoc Messages

SMW02 Display Bdoc message summary

Bdoc errors in SANDISK Project:

Failed Bdocs in the system (CPP) needs to be investigated and corrective measures to be made for the

data consistency in the SanDisk system landscape.

Here we will discuss few Bdoc errors.

Example #1:

Issue: CUSTOMER_MAIN Bdoc is in E04 (Validation) error Terms of payment Z123 not available.

Reason for error: Terms of payment Z123 is not available in CPP configuration.



Page - 3 - of 6

Solution: Since we do not the separate configuration for the terms of payment in CPP system, we will

replicate the respective configuration object from EPP to CPP.

DNL_CUST_PAYM - customizing object need to be replicate from EPP to CPP to solve customizing issue.

Example #2:

Issue: CUSTOMER_MAIN Bdoc is in E04 (Validation) error Customer group 75 is not available; enter a

valid customer group

Reason for error: Customer group 75 is not available in CPP configuration.

Solution: Since we do not the separate configuration for the terms of payment in CPP system, we will

replicate the respective configuration object from EPP to CPP.

DNL_CUST_KTOKD - customizing object need to be replicate from EPP to CPP to solve customizing issue.



Page - 4 - of 6

Example #3:

Issue: CUSTOMER_MAIN Bdoc is in E04 (Validation) error Business partner with GUID

4DDB764036D259E6E10000000AB34AA1 does not exist

Reason for error: BP- GUID in CPP is not matching with the GUID in EPP

Solution: We need to define the request for this customer and do the request load from EPP to CPP.

So that EPP GUID and CPP GUID for this customer will match.

Example #4:

Issue: CRM_FM_FPO Bdoc is in E01 (Technical Error) status with error NO rebates and/or 6-period Sales

Volume; NB_DAYS; Use T-code ZTPM002 to maintain; Product/ Hierarchy G

Reason for error: Sales volumes missing and need to be maintained.

Solution: Embedded is the solution for this kind of issues in SanDisk project.

Maintaining sales volume.doc



Page - 5 - of 6

Example #5:

Issue: PRODUCT_MAT Bdoc is in E04 (validation Error) status with error Division 75 does not exist

Reason for error: Newly added Division is not CPP.

Solution: Customizing Adapter object for product needs to be replicated to CPP.

Example #6:

Issue: PRODUCT_MAT Bdoc is in E08 (mapping Error) status with error Category for product hierarchy

07137IS-5BK--00128 does not exist

Reason for error: Newly added product hierarchy is missing in CPP.

Solution: Below mentioned customizing objects need to run in CPP system to replicate the newly added

PH in EPP.

DNL_CUST_PROD0

DNL_CUST_PROD1

DNL_CUST_PROD3



Page - 6 - of 6

2.2: Special Configuration / Custom data maintenance RFC (Remote Function Call) needs to be established between the EPP and CPP system. And both systems

should be up and running to run the Customizing objects replication

2.3: Important Transactions used during the process Transaction Name Purpose of the Transaction

R3AS To start the customizing object

R3AM1 To monitor the customizing object status

SMW01 To check the resulted Bdocs generated on this object run

SMQ2 To monitor the data coming to CPP system

SMQ1 To monitor the data/Request going out of CPP system

bdoc monitoring guide

Documents