technical overview of data exchange

Please note that we are recording this live session!

Welcome to your Virtual Classroom Live Session!

SAP Business Partner in CRM 3.0 - Technical overview of

Data Exchange

Session start: 5 pm CET

Approx. duration: 60 min

Trainer: Carmen Bolz Ulf Hoffmann

SAP AG 2002, Technical overview of data exchange

Hotline EMEA 0041-21-620-7750, AMERICAS 001-800-647-9383, ASIA PACIFIC 00972-3-687-3030

Your Instructors

Ulf Hoffmann Development

mySAP CRM Common Relationship Data

Carmen Bolz Info Development & Product Management

mySAP CRM Common Relationship Data



E-Learning Series - Overview

Part 1:Part 1:

Part 2:Part 2: Debugging session for data exchange

Part 3:Part 3: Data exchange for customer enhancements

Technical overview of data exchange



Prerequisites

Required:

Technical understanding

Basic know-how in data exchange

Know the content of the following Virtual Classroom session:

SAP Business Partner in CRM 3.0 - Data Exchange V00212



Objectives

After completing this course you will be able to:

Describe the Integration Architecture for the data exchange of business partners

Understand the structure of messaging BDocs for business partners

Explain the data exchange scenario from R/3 to CRM and vice versa



Session Overview

Topic 1 Topic 2 Topic 3 Topic 4

Integration Architecture

Messaging BDocs

Data exchange from R/3 to CRM

Data exchange from CRM to R/3




CRM serverCRM server

Mobile ClientMobile Client


Flow withsBDoc

Mapping:sBDoc mBDoc

XIF Adapter

Simple intelligent Replication

CRM Adapter

XIF Adapter

Flow withmBDoc

R/3 Adapter

External interfaces (XML, IDoc)

External interfaces (XML, IDoc)

Mapping:mBDoc sBDoc

Replication/ Realignment

CDB Service

Flow withsBDoc

Outbound Adapter

Site-Types

R/3 Adapter

Both XMLand IDocs can begenerated from the ABAP complex data type used to define the externalinterface




Messaging BDocs



Session Overview




Messaging BDocs

Messaging BDocs consist of two parts:

Classic part

Modeled with BDoc Modeler: /1CRMG0/CRMW_BUPA_HEAD002 for BUPA_MAIN

Generated hierarchical segment structure

Includes fields for MW-Services: All fields relevant for replication

BDoc Extension

Complex DDIC structure: BUS_EI_MAIN for BUPA_MAIN

Includes application data (business parter, BP relationships)

Monitoring with SMW01

Both BDoc parts

Flow context

Error messages



Complex structure

HEADER =========================> identifier, taskCENTRAL_DATA ==================> SAP_ABA components of BP

COMMON =======================> data structureDATA DATAX

BANKDETAILS ===================> data table CURRENT_STATE =========> table complete?Table with data

TASK =========> for each lineDATA_KEY ======> identifierDATA =========> data structureDATAX =========> update flag/field

CRMDATA =========================> CRM components of BP

Task for whole object

Current state flag for each table

Task for each line

Update flags for each field of a data stucture

Documentation within SE11 for BUS_EI_EXTERN




Question and Answer

Question 1:

What‘s the function of the classical BDoc part?

Answer:

The classical BDoc part decides if the CRM validation has to be called

The classical BDoc part is evaluated by the replication

The classical BDoc part includes the data for the mobile client




Messaging BDocs



Session Overview




Data exchange from R/3 to CRM (I)

Customer masterR/3

BTE

PlugIn

Mapping to complex structure

MW

FilterMapping to BAPIMTCS

qRFC

1

2 34

5

R/3



Modules and Customizing within R/3

1) Publication: BTE 1321 = PI_BP_CUSTOMER_BTE_1321 (TBE31). PI_BP_MAP_CUST_TO_BUPA: fill complex structure (TYPE-POOL BUSEI).

2) PI_BP_MAIN_TO_BAPIMTCS / PI_BP_REL_TO_BAPIMTCS creates BAPIMTCS = MW data format enables the use of generic tools for filtering and RFC data transfer.

3) Transfer BAPIMTCS to MW, i.e. CRS_SEND_TO_SERVER.

The MW filter CRM_FILTER_DOWNLOAD_DATA deletes BAPIMTCS Filter conditions maintained within CRM transaction R3AC1. Transferred to CRMFILTAB within R/3.

4) Determine logical destination (CRMRFCPAR) for the qRFC.

5) Queuenames: R3AD_CUSTOME*** for customers and contacts.

*** = customer number (Default: leading 0 up to 10 digits in the case of numbers; number of digits customizable in CRMQNAMES)



Data exchange from R/3 to CRM (II)

CRM

qRFC

R/3 Adapter - MW

Online Flow

Mapping to mBDoc

R/3 Adapter - BP

CRM Adapter

Replication

BP Inbound

BP Outbound

6

78

910

1213

11

CRM



Modules and Customizing within CRM

6) RFC calls BAPI_CRM_SAVE. MW calls R/3 Adapter for objects CUSTOMER_MAIN or CUSTOMER_REL (R3AC1): BUPA_MWX_BDOC_DOWNLOAD_R3A.

7) Unpack BAPIMTCS by CRM_BUPA_BAPIMTCS_TO_MAIN / CRM_BUPA_BAPIMTCS_TO_REL.

8) Call MW Flow: SMOF0_NEXT_GENERATION_HANDLER.

9) MW Flow determines application function module (SMW3BDOCIF) for BDoc validation. BUPA_MAIN: CRM_BUPA_MAIN_VAL BUPA_REL: CRM_BUPA_REL_VAL

10) Interfaces include MW, CRM, and SAP_ABA specific parameters. MW: (administration, error messages, classic BDoc part). CRM: CRM specific BP enhancements SAP_ABA: central BP parts. => Decoupling during BP inbound processing (reuse, e.g. R/3).




11) Validate and save BDoc data via BAPIs. Return of BDoc status and messages to MW.

MW calls BAPI_TRANSACTION_COMMIT or BAPI_TRANSACTION_ROLLBACK.

12) BP outbound processing creates a new BDoc, triggered by BADIs that have been registered during the BAPI calls.

13) BP outbound processing starts new flow context. No BDoc validation as in (9) but BDoc notification. Publication of changes to other adapters and the mobile client.



Monitoring BDocs with SMW01

1. Change customer within R/3

2. Use the transaction CRMM_BUPA_MAP in the CRM system in order to map the customer number to the GUID

3. Start SMW01 with this GUID as root ID

4. Result shows all BDocs for this customer / BP




Question and Answer

Question 2:

What happens if a filter-relevant field has been changed so that the data can now

pass through the filter?

Answer:

The BP can never be replicated to CRM

The BP has to be transferred to CRM in its current state with all data

Only the changed data of the BP is sent from R/3 to CRM




Question and Answer

Question 2:

What happens if a filter-relevant field has been changed so that the data can now pass through the filter?

Answer:

The BP can never be replicated to CRM

The BP has to be transferred to CRM in its current state with all data

Only the changed data of the BP is sent from R/3 to CRM




CRM serverCRM server



Flow withsBDoc

Mapping:sBDoc mBDoc

XIF Adapter

Simple intelligent Replication

CRM Adapter

XIF Adapter

Flow withmBDoc

R/3 Adapter

Mapping:mBDoc sBDoc

Replication/ Realignment

CDB Service

Flow withsBDoc

Outbound Adapter

Site-Types

R/3 Adapter



CRM 3.0 Integration Architecture

Messaging BDocs



Session Overview




Data exchange from CRM to R/3 (I)

CRM

CRM

R/3 Adapter - BP

BP masterBADI

Mapping BP to BDOC

MW

Mapping to BAPIMTCS

qRFC

Select data

Online Flow

Replication

R/3 Adapter - MW

1

2

34

5

67

qRFC




1) Publication via BADI implementations (BUPA_MWX_SAVE, SE19). BP outbound processing: BUPA_MWX_BDOC_CREATE, creates complex structure and BDoc.

2) BDoc transferred to MW by method cl_smw_mflow=>process_outbound. Flow started within MW via qRFC with destination NONE.

3) Depending on subscription (TA SMOEAC) MW Flow calls the R/3 adapter.

4) Call application again, in order to translate the BDoc into BAPIMTCS structures.

Therefore within table SMOFUPLMAP two upload modules are registered, BUPA_MWX_BDOC_UPLOAD_MAIN_R3A for the BPs and BUPA_MWX_BDOC_UPLOAD_REL_R3A for the relationships.

5) Enhancement of BDoc data, e.g. contact data.

6) Translation into BAPIMTCS structures by CRM_BUPA_MAIN_TO_BAPIMTCS and CRM_BUPA_REL_TO_BAPIMTCS. Resend BAPIMTCS to the MW R/3 adapter.

7) qRFC into R/3. Destination: SMOF_READ_SMOFERPSH with parameter I_SITETYPEID = ‚SMOFERPSITE‘. The queuename is CSABUPA*** or. *** is the BP ID with leading 0 in the case of only digits. CSA_MASS_BUPA in the case of mass BDocs.



Data exchange from CRM to R/3 (II)

qRFC

Customer masterR/3PlugIn

Mapping to complex structure

MW

BP master

8

9

10

R/3



Modules and Customizing within R/3

8) RFC calls CRM_UPLOAD_TRIGGER within R/3.

MW calls COM_BUPA_MAIN_INBOUND for the BPs or COM_BUPA_REL_INBOUND for relations (registered in SMOFSUBTAB).

9) Depending on COM_BUPA_CALL_FU entries inbound processing for:

Customer master: PI_BP_PROXY_BAPI_CUSTOMER uses PI_BP_BAPIMTCS_TO_MAIN and PI_BP_BAPIMTCS_TO_REL in order to create the complex structure (TYPE-POOL BUSEI).

BP (>=4.6C): COM_BUPA_MAIN_BP_INBOUND creates the complex DDIC structure with COM_BUPA_BAPIMTCS_TO_MAIN, saves data with COM_BUPA_CONV_EI2BAPI.

(COM_BUPA_REL_BP_INBOUND, COM_BUPA_BAPIMTCS_TO_REL and COM_BUPR_CONV_EI2BAPI for relationships).

10) Status is sent back to CRM within COM_BUPA_MAIN_INBOUND via CRS_SEND_TO_SERVER

Mapping

R/3: Tables: CRMKUNNR for customers, CRMPARNR for contact persons

CRM: Transaction CRMM_BUPA_MAP

Tables: CRMM_BUT_CUSTNO, CRMM_BUT_CONTNO




Question and Answer

Question 3:

Before the data is transferred from CRM to R/3, the R/3 adapter sometimes

selects additional data from the data base. Why is the BDoc data enhanced?

Answer:

Because the BDoc includes no data but only the relevant identifiers.

When the data of a contact relationship is exchanged, the R/3 system needs to know the data of the person as well.




Question and Answer

Question 3:

Before the data is transferred from CRM to R/3, the R/3 adapter sometimes selects additional data from the data base. Why is the BDoc data enhanced?

Answer:

Because the BDoc includes no data but only the relevant identifiers.

When the data of a contact relationship is exchanged, the R/3 system needs to know the data of the person as well.



Event Logic of BP Inbound/Outbound Processing

CRM: Transaction CRMC_BUT_CALL_FU

Events:

CRM Inbound (Validation: Calls BP Inbound incl. BAPIs)

CRM Outbound (fill structure)

More for customer appends, R/3 adapter and extraction

R/3: Transaction COM_BUPA_CALL_FU

Events:

R/3 Object Inbound (BP or Customer)

Mapping Inbound (BP, Filter, number range)

Mapping Outbound (BP, fill structure)

R/3 Object Outbound (BP, call MW)

More for customer appends and extraction (BP)



CRM: Transaction CRMC_BUT_CALL_FU



Extractors for Initial Load, Request, and Direct Send

R/3

Customer (CRMSUBTAB)

CUSTOMER_MAIN / REL: PI_BP_CUSTOMER_MAIN_EXTRACT

BP (CRMSUBTAB)

BUPA_MAIN CRS_BUPA_MAIN_EXTRACT

BUPA_REL CRS_BUPA_REL_EXTRACT

CRM

1) Select GUIDs (CRMSUBTAB)

BUPA_MAIN CRM_BUPA_MAIN_EXTRACT_GUIDS

BUPA_REL CRM_BUPA_REL_EXTRACT_GUIDS

2) Select data within R/3 adapter, (TA R3AC1)

BUPA_MWX_BDOC_DOWNLOAD_R3A calls: CRM_BUPA_MAIN_EXTRACT_FILL, CRM_BUPA_REL_EXTRACT_FILL

Direct Send uses Report CRM_BUPA_SEND_BP, can be replaced by request



Summary

You are now able to:

Describe the Integration Architecture for the data exchange of business partners

Understand the structure of messaging BDocs for business partners

Explain the data exchange scenario from R/3 to CRM and vice versa




Question and Answer

Feedback Question:

Do you consider this session as helpful?

Answer:

Yes, very helpful.

Yes, it was okay.

No, I expected something else.



E-Learning Series - Overview

Part 2:Part 2:

Part 1:Part 1:

Part 3:Part 3: Data exchange for customer enhancements

Technical overview of data exchange (V00279)

Debugging session for data exchange

technical overview of data exchange

Documents

data exchangeknow

data exchangepart

data exchange v00212sap

asia pacific

data exchange scenario

abap complex data type

instructorssap ag

vice versasap ag