1. Extending BDocs by Robert Kuhn

BDoc Modeler: Transaction SBDM

• Tool used for displaying, creating and enhancing BDoc types

• Definition and Enhancement requires knowledge of the application

• BDoc types consist of two parts:

Classical Part

• Hierarchical segment structure
• Modeled with the BDoc modeler – SBDM
• Generated Structure
• Contains data relevant for Receiver Determination
• Part is mandatory
• Consist of a BDoc header and segments which may be arranged in hierarchical fashion – NOT MAPPED TO DB TABLES – thus needs to be filled in completely at runtime

Extension Part:

• Complex data type
• Modeled with DDIC – SE11
• Contains the actual data: Master and Transaction
• This part is optional
• Extension only exists for Messaging BDocs
• Can not be used for receiver determination

BDoc like an envelope with Extension part that CRM middleware can not access and Header Part which the middleware can access to determine receiver

2 Replication types are supported:

• Simple intelligent – by definition of replication rules
• Simple Bulk – everybody gets all or nothing

With mBDocs, the whole message is distributed – not possible to select certain parts of it.

Displaying BDocs

You can use transaction SMW01 to display BDoc messages.

• Green Light: successfully processed
• Yellow: in process
• Red: contains error condition
• BDoc errors should be checked daily and errors addressed without delay
• More information on BDoc error solving to be published in a Best Practice Document – also see SAP note 526853

You can use transaction SMW02 to display BDoc messages in an aggregated view on the basis of various criteria