Initial Download for Business Data R 3 AS

Initial Download for Business Data R 3 AS : Start Initial Load For Business Adapter Object CRM R/3 Inbound Adapter R/3 CRS_FIRST_DOWNLOAD_TRIGGER q. RFC BAPIMTCS Specific Extractor q. RFC Inbound Message Flow Validation Service CRM Application CRM Database Outbound Message Flow R/3 Tables

BDocs • • BDoc Introduction BDoc Classes- Overview s. BDoc (Synchronization BDoc) m. BDoc (Messaging BDoc)

Business Documents (BDocs) CRM Server Mobile Clients KNA 1 ADRC KNVV CRM Server BDoc “David” BDocs acts as a process container for processing Business objects and for transporting them as one unit instead of having to process/transport several individual table entries.

Business Documents (BDocs) Distinction BDoc type (structure) KNA 1 KNVV BDoc instance Customer BDoc “David” NAME 1 = “David” ( All fields ) NAME 2 = “Boon” KUNNR = “ 60078” BDoc message Also: “insert” or “delete Customer BDoc “David”. Task = “update” Fields CITY 1 = “New York” , Street = “ 1 Broadway” (Contains only modified fields) • BDocs Type: This is a structure that needs to be defined to each Business object. • BDoc Instance: The BDoc type with all the required fields. • BDoc message: This contains “modified” fields only. It also includes deleted fields. There will be one BDoc instance for a Business Object, but there can be multiple BDoc messages (with their own Id’s) for one BDoc instance.

m. BDoc (Messaging BDoc) m. BDoc type consists of two parts: Classical Part • This is a mandatory structure. • The BDoc header and segments are arranged in a hierarchical fashion. • To be modeled with BDoc modeler. • This is used to determine the receivers of m. BDoc messages. • Generated structure Extension • This is optional structure. • To be modeled with DDIC • Contains the transaction data. /BUPA_HEAD 002 BUS_E 1_MAIN

s. BDoc (Synchronization BDoc) • Only used for data synchronization with mobile clients. • s. BDoc types contain direct mappings to tables of the consolidated database. s. BDoc types are used to make data persistent in the CDB and to exchange messages between the CRM Server and mobile clients. • Realignment and dependencies between s. BDoc types are supported. s. BDoc structure Type, sender, timestamp, … Eg. Order Header Business Partner Master Control segment Body Error segment Data segment … Business Partner Address

Structure of a BDoc

Common Bdoc types

BDoc processing

Common services