Business Process Document

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:

SAP CRM BDoc trouble shooting guide Confidential Page - 1 - of 6

07 Jul 2011

Business Process Document

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

Transaction codes used in Bdoc trouble shooting: Transaction code SMW01 SMW02 Description Display Bdoc Messages 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.

SAP CRM BDoc trouble shooting guide Confidential Page - 2 - of 6

07 Jul 2011

Business Process Document

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.

SAP CRM BDoc trouble shooting guide Confidential Page - 3 - of 6

07 Jul 2011

Business Process Document

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

SAP CRM BDoc trouble shooting guide Confidential Page - 4 - of 6

07 Jul 2011

Business Process Document

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

SAP CRM BDoc trouble shooting guide Confidential Page - 5 - of 6

07 Jul 2011

Business Process Document

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 R3AS R3AM1 SMW01 SMQ2 SMQ1 Purpose of the Transaction To start the customizing object To monitor the customizing object status To check the resulted Bdocs generated on this object run To monitor the data coming to CPP system To monitor the data/Request going out of CPP system

SAP CRM BDoc trouble shooting guide Confidential Page - 6 - of 6

07 Jul 2011