1 / 13

Initial Download for Business Data

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

marty
Télécharger la présentation

Initial Download for Business Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. BDocs • BDoc Introduction • BDoc Classes- Overview • sBDoc (Synchronization BDoc) • mBDoc (Messaging BDoc)

  3. CRM Server Mobile Clients KNA1 ADRC KNVV CRM Server BDoc “David” Business Documents (BDocs) 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.

  4. KNA1 KNA1 KNVV Business Documents (BDocs) Distinction BDoc type (structure) Customer BDoc “David” NAME1 = “David” NAME2 = “Boon” KUNNR = “60078” BDoc instance ( All fields ) Also: “insert” or “delete BDoc message Customer BDoc “David” . Task = “update” Fields CITY1 = “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.

  5. mBDoc (Messaging BDoc) mBDoc 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 mBDoc messages. • Generated structure /BUPA_HEAD002 BUS_E1_MAIN • Extension • This is optional structure. • To be modeled with DDIC • Contains the transaction data.

  6. Type, sender, timestamp, … sBDoc structure Eg. Order Header Business Partner Master Control segment Body Error segment Data segment Data segment Business Partner Address … sBDoc (Synchronization BDoc) • Only used for data synchronization with mobile clients. • sBDoc types contain direct mappings to tables of the consolidated database. sBDoc 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 sBDoc types are supported.

  7. Structure of a BDoc

  8. Common Bdoc types

  9. BDoc processing

  10. Common services

More Related