Bdoc-Business Document

Bdoc-Business Document

 

§What is Bdoc?

-Bdoc( business documents) are containers used to transport & process various business objects.

-So it carries business objects without getting into the technical aspects.

-Over and above Business Object related data other data like errors and status is also carried by Bdocs. 

 

Bdoc Terminology

 

 

 The motivation of using BDocs as data container for processing business objects and for transporting them between the CRM Middleware and the mobile clients is that you can process/transport them as one unit, instead of having to process/transport several individual table entries.

 

 BDoc type or structure has to be defined for each required business object, e.g. Contact Person, Sales Order etc. It contains all the R/3 table entries that make up the corresponding business object. 

 

  A BDoc instance is a concrete example of a given BDoc type containing all field values. 

 

  A BDoc message (or just BDoc) contains “modified“ fields only. These include new fields as well as deleted fields. The difference between a BDoc message and a BDoc instance is that there is only one BDoc instance for a Business Object but there can be multiple BDoc messages (with their own Ids) for one BDoc instance. However a BDoc instance is replicated to a mobile client using a BDoc message where all fields are filled.

 

Bdoc Terminology - example

 

 

 

Bdoc Structure

 

 

 

 A BDoc type consists of a header and a body. 

 

  The BDoc header consists of one single data segment, the so-called control segment.

  The BDoc body consists of one or more data segments and of one error segment. 

 

  The control segment merely contains header information, whereas the individual data segments contain the actual table entries that make up the corresponding business object. 

 

Bdoc  segments are arranged in a hierarchical fashion to model dependencies of data. This is achieved by specifying parent-child relationships between segments.

  On top of the hierarchy there is always a unique root data segment. It contains a unique root ID used to replicate the BDoc to the mobile clients.

Food for thought : check this slide