Enhancements to BDoc Types 

You need to enhance BDoc types in the following scenarios:

·        Scenario 1

The customer wants to create a new table and add a new segment to the BDoc type to ensure that the newly added table fields are populated in the adapter by using the data sent from CRM server. For more information, see Creating a Table and Adding a Segment.

·        Scenario 2

The customer wants to add only a few fields in a table and change the BDoc type to ensure that the adapters can populate the fields by using the data sent from CRM server. For more information, see Adding Fields to a Table.

·        Scenario 3

The customer wants to enter the fields in CRM server (either through data entry or programming) and store them in both CRM and CDB / mobile client tables. For more information, see Entering the Fields in CRM Server.

·        Scenario 4

The customer wants to perform either of the following:

Enter the field in CRM server (either through data entry or programming). However, the field is not relevant to the CDB / mobile client.

Enter the field in the mobile client. However, the field is relevant to CDB only and not CRM server.

In this scenario, data exchange is not required. Therefore, you do not need to modify the user exits. However, if required, you can modify the required CDB table and synchronization BDoc type segment. If the BDoc segment or table is modified, you must generate metadata and table scripts by using Client Console. For more information, see Generating Metadata for Business Document Typesand Generating Table Scripts.

·        Scenario 5

The customer wants to apply only additional mappings and conversion rules on the existing fields in the BDoc type instead of adding new fields or tables. For more information, see Applying Mappings and Conversion Rules.