Diff ...between Bdoc's and Idoc's in XI integration !

[Former Member]

Hi All

In XI integration what is the difference between Bdoc's and Idoc's ?

Both or same ? different ? how the integration will be done ?

Adv...thanx and regards

kiran LVS

[Former Member · Accepted solution]

Hi

An IDoc transfer is quicker in comparison to SOAP/XML because the IDoc document contains no metadata information (tags)unlike an XML document, and therefore, the size of document sent down the line is substantially smaller in comparison.

IDocs can be used to send messages to the SAP Exchange Infrastructure where an IDoc XML document will be established and mapped into other XML Schemata. The XML messages can be routed to other Business Systems. IDocs can be used to send messages to the Business Connector where an IDoc XML document will beestablished and mapped into other XML Schemata such as Rosetta Net, xCBL or customer‘s ownschemata.IDocs can be used to send messages to a flat file.IDocs can be used to send messages to an ALE converter, where IDocs are mapped into standardizedmessage formats (EDI communication).IDocs can be used to send messages to an ALE Messaging System. In contrast to an ALE converter, the message handler will not perform any conversion or mapping but instead receives IDocs and sends

them to applications for processing. IDocs can be used to send messages to an EDI Sub-System. In contrast to an ALE converter, the EDISub-System does not use direct program-to-program communication for transferring IDocs.

A messaging BDoc consists of up to two parts:

Part 1: classical part

This part is mandatory.

The classical part consists of a BDoc header and segments, which may be arranged in a hierarchical fashion. The segments of the classical part are not mapped to database tables.

This part is to be modeled with the (CRM Server based) BDoc Modeler. Only the classical part is used to determine the receivers of mBDoc messages. Since there is no mapping to database tables (that is, no CDB), this part always needs to be filled completely by the application at runtime.

Part 2: Extension part

This part is optional.

The complex data type is modeled with the Data Repository Tools (SE11).

The extension does only exist for messaging BDocs.

The extension part is used to hold delta or extract data intended to pass into the CRM Server application (inbound case) or to send to remote systems (outbound case). The extension part cannot be used for receiver determination.

Bdocs are specific to CRM. They do not leave the CRM system, but perform their updates from it. They are much bigger because they contain the entire data-model of the object they are supposed to update. They can contain delta or creation information and can be processed by flow processes.

So they are data-containers that are used to update CRM & CRM dependent systems.

Idocs are data-containers as well, but they are structured for their purpose (not for the object they contain) and they can be transfered between systems.

[Former Member]

Thanks a lot to all contributers

and points awarded to all !!!

regards

kiran LVS

[Former Member]

Hi Prasad

Any more links on this pl...

regards

kiran LVS

[Former Member]

Hi Kiran

Here you can find some more information

IDOC: An intermediate document, container for exchanging data between R/3 and other SAP and non-SAP applications. Structured collection of segments. Segments are structured collection of data elements.

BDOCS: Business Documents are the semantical layer for the whole CRM, regardless of implementation details. A major achievement of a semantical layer is, that the need for point-to-point mappings are eliminated. Using BDocs mean fast integration of applications. The definition of Business Documents (BDoc) does not contain implementation details. It differs depending on the underlying technology, so that the optimal representation of a BDoc can be used:

Implementation examples:

• CRM Server: Internal tables

• Laptops: ADO record sets

• Non-SAP System: XML Decoupling of Messaging

An Intermediate Document (IDoc) is a SAP standard format for data transfer between systems.

IDocs are mainly used for Application Link Enabling (ALE) and for Electronic Data Interchange

(EDI). They are not used for processing inside an application.

Business Documents (BDocs) are used by the CRM Middleware to exchange data with mobile

clients. Furthermore BDocs are the central data structure to process business objects internally.

In contrast to Idocs, for which the internal processing has to be implemented manually, the coding to

process BDoc may be generated automatically.

Business Document

• tRFC or qRFC

• Usage in CRM for data exchange

• Possibly complex data structures

both in transport and processing

• Runtime objects, e.g. services

generated from BDoc repository

information

• Internally created

• Uses delta field communication

Intermediate Document

• Asynchronous

• Usage in ALE and EDI

• Consisting of

control record

data record

status record

• Message-oriented

• Transfers all fields

-- i hope this will solved your question

regards

--- prasad