replication bp contacts

Stand: 05.06.2009 11:14:00 1 / 21

SAP AGNeurottstr. 16

D-69190 Walldorf

Replication of BusinessPartner Activities in CRMActivities

05.06.2009

Replication of Business Partner Activities in CRM Activities

2 / 21

© Copyright 2002 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components ofother software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks ofMicrosoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, andOS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks of IBM Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® andother Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology inventedand implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned hereinas well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Marketsand Commerce One. All other product and service names mentioned are the trademarks of their respectiveowners.


3 / 21

Inhalt

1.1 Functional Scope............................................................................... 41.2 Data Mapping Contact - Activity......................................................... 51.3 Technical Implementation.................................................................. 7

1.3.1 General Information...........................................................................71.3.2 Delta Download.................................................................................71.3.3 Initial Download................................................................................9

1.4 CRM Middleware............................................................................... 91.4.1 Basic System Settings in CRM ..........................................................91.4.2 Administration Console .....................................................................91.4.3 Contact Replication ...........................................................................9

1.5 Settings ........................................................................................... 141.5.1 OLTP System Settings.....................................................................141.5.2 Settings and Modifications in CRM .................................................191.5.3 Customer Enhancements in the OLTP System .................................19

1.6 Further Notes .................................................................................. 201.6.1 Template Activity............................................................................201.6.2 Error Analysis .................................................................................211.6.3 Sizing ..............................................................................................21


4 / 21

1 Replication of Business Partner Activities in CRMActivities

This unit describes the integration of the business partner contacts of an OLTP system inthe activities of the CRM system. You will obtain an overview of the data mapping,replication processes and required Customizing activities.

The information below assumes that you have successfully replicated business partners.

1.1 Functional ScopeWhen OLTP business partner contacts are replicated in CRM activities, data isautomatically exchanged between the business objects business partner contact (BORobject type BCONTACT, application component FI-CA-BT-CC) and activity (BOR objecttype BUS2000126, application CRM-BTX-ACT – business transaction/activitymanagement). The synchronization of data enables the contacts to be integrated in theSAP CRM contact management

Data replication only functions – via download – in the following direction: OLTPCRM. The initial download and delta download sub-functions can be used. Both newlycreated contacts and changes to existing contacts are replicated. Upload functions(CRM OLTP) are not supported.

This makes the information on the contact available in all the SAP CRM functions (forexample the IC or business partner cockpit).

The replicated data includes:

Data on the contact itself (essentially the contact partner, affected employees,data, type and direction of the contact, as well as priority)

Notes

Object links

The object links allow for access to other systems. This enables you to branch to thedisplay transaction of the respective linked business objects in the OLTP system. Inaddition, a separate object link enables the contact itself to be displayed in the OLTPsystem. Note that these links are exclusively OLTP object links and do not take intoaccount generic objects, such as MS Word documents.

All the changes made in the OLTP system are made in the replicated activity. Changescan be made in the CRM system- however they are not replicated in the OLTP system.

You can set up filters in the CRM middleware and in special OLTP tables that help youselect the contacts to be replicated, for example all manually created contacts or onlythe contacts of a certain contact class.

The contact replication functionality is available as of CRM release 3.1 and IS-U release4.64.


5 / 21

1.2 Data Mapping Contact - ActivityThe graphic below shows how the OLTP contact is mapped onto the CRM activity.

Overview of contact mappingThe graphic shows the relevant sub-objects of the OLTP contact and CRM activity, aswell as the names of the tables with which you define the mapping procedures. Theallocation of OLTP contact keys to CRM activity GUIDs are recorded in theBPCT_CRM_GUIDS table.

In CRM, the activities can be divided into contacts and tasks. The replication functionsstipulate that when the data is transferred, the OLTP contact is mapped to an activitywith the business transction category Contact (000).The contacts can also be mapped in an ativity with a different business transaction type.This transaction type must use the contact (BUS2000126) as a business transactioncategory and meet the following minimum requirements:

ActivityCustomer Contact

NoteSTXHSTXL

Objects LinksBCONT_OBJ

Admin dataODERADM_H

AktivityACTIVITY_H

OrganizationORGMAN

PartnerPARTNER

DatesAPPOINTMENT

TextsTEXTSTXHSTXL

Document FlowDOC_FLOW

n.n. ...

BPCT_CRM_CLASS

BPCT_CRM_DIRECTBPCT_CRM_PRIO

BPCT_CRM_CLASS

BPCT_CRM_TDID

OLTP CRM

BPCT_CRM_GUIDS

Validate

ContactBCONT


6 / 21

Procedure Limitation

Text procedure The text procedure must be defined for the CRM_ORDERH textobject, and must contain at least the A002 (“note”) text type.

Partnerprocedure

The partner procedure must contain entries from partner functions,which have the 0006 “contact partner” and 0007 “contact person”.The business partner or contact person from the IS-U contact ismapped to these entries.

The procedure can also contain other partner functions. The systemautomatically allocates the user who created the contact in SAP IS-Uto the entries, which have the 0008 “responsible person” and 0005“co-worker” partner function categories. Otherwise, the normalpartner determination for activities applies for the entries.

Date profile The date profile must contain at least the ORDERACTUAL “actualdate” date type.

The following additional mapping rules apply:

In CRM, a transaction is created with the contact business transation category(BUS2000126). You can choose the business transaction type in theBPCT_CRM_CLASS table.

The category of the activity (for example on-site visit or E-mail) for an OLTPactivity is determined in the BPCT_CRM_CLASS table.

The partner GUID transfers the partner to the CRM system. The OLTP businesspartner is mapped in the CRM contact partner, the OLTP contact person ismapped in the CRM contact person.

The ‚responsible person’ is determined from the ERNAM field in the BCONTtable (created by). If a business partner does not exist, the activity is still createdwith the ‘responsible person’ as the partner, and an error message is entered inthe error lohg

The ‚co-worker’ is determined in the same way as the ‘responsible person.’

The contact direction is converted using the BPCT_CRM_DIRECT table.

The contact priority is converted using the BPCT_CRM_PRIO.

The organizational data is copied from the template activity. If no activity isspecified, it is determined ‘dynamically’ according to the rules of the activity fordetermining organizational data.

The object links are created in CRM with the BCON relationship category.

Contacts in which a deletion indicator has been set are not replicated.

For more information on mapping rules, see unit 8.5.


7 / 21

1.3 Technical Implementation

1.3.1 General InformationThe CRM middleware is used to replicate the data.

To achieve this, the new download object SI_BCONTACT was created. This objecttakes the data from the OLTP system and converts it to a messaging BDoc category,BUS_TRANS_MSG.

1.3.2 Delta DownloadIf the data replication function is active, when a contact is saved in the OLTP (eitherthrough initial data creation or changes to existing data), a queued RFC (qRFC) sendsthe data to the CRM system. There, the contact is asynchronously converted to the dataof the activity and updated.

In the OLTP system, a business transaction event (BTE) with the description IBSSIBCOtriggers distribution for the delta mechanism. During distribution, the system decideswhether the contact meets the filter conditions defined in the CRM middleware.Distribution is followed by an evaluation of the settings for mapping. If the contact fulfillsthe conditions for replication, the data is transferred to the middlware components andwritten to the inbound queue in the CRM system.


8 / 21

BCONTACT_ACTION:Save contact

BCONTACT_ACTION:Save contact

Start delta download:Check for business

transaction event

Start delta download:Check for business

transaction event

BTE IBSSIBCO:Delta download active ?

BTE IBSSIBCO:Delta download active ?

Check for filtering:Does contact meet

the filter conditions?

Check for filtering:Does contact meet

the filter conditions?

Map dataMap and put data in

BAPIMTCS

Map dataMap and put data in

BAPIMTCS

CRMFILTAB:Contact in filter?

CRMFILTAB:Contact in filter?

Send data :Call middleware,qRFC call to CRM

Send data :Call middleware,qRFC call to CRM

BPCT_CRM_CLASS:Contact class of mapping

data for replication

BPCT_CRM_CLASS:Contact class of mapping

data for replication

Write to inbound queue:R3AD_BUPA<partner>

Write to inbound queue:R3AD_BUPA<partner>

CRM

Delta download : process flow in OLTP system and filtering process

Process LUW:R3AD_BUPA<partner>

Process LUW:R3AD_BUPA<partner>

1. Start middleware flow:Mapping step: unpack

BAPIMTCS for BAPI structure

1. Start middleware flow:Mapping step: unpack

BAPIMTCS for BAPI structure

5. Resume flow :Further process

mBDoc BUS_TRANS_MSG

5. Resume flow :Further process

mBDoc BUS_TRANS_MSG

3. Merge data:Transferred data plus

template activity in mBDoc

3. Merge data:Transferred data plus

template activity in mBDoc

2. Read template activity:Transferred data plus

template activity

2. Read template activity:Transferred data plus

template activity

4. Customer enhancement :BAdI to furtherprocess mBDoc

4. Customer enhancement :BAdI to furtherprocess mBDoc

Process mBDoc:BUS_TRANS_MSG

Process mBDoc:BUS_TRANS_MSG


9 / 21

Delta and initial download : process flow in CRM

1.3.3 Initial DownloadThe initial download (first time the contact data is applied in the CRM system), adownload request is generated in the CRM system. The request triggers the selection ofdata in the OLTP system. The RFC sends the contacts in blocks to the CRM system,where they are further processed.

The filters are applied in the same way as during a delta download.

1.4 CRM Middleware

1.4.1 Basic System Settings in CRMFor information on the system settings in CRM, see the CRM Master Guide 3.0. Thiscan be found in the SAP Service Marketplace under http://service.sap.com. Choose LoginNow and enter your user name and password. Then choose Solution Details Cross-Industry Solutions mySAP CRM Media Library Documentation Installation &Upgrade Guides mySAP CRM SAP CRM 3.0 CRM Master Guide 3.0.

1.4.2 Administration ConsoleIf you want to download data from ERP to the CRM system, you must define sites andsubscriptions. You do this in CRM using the administration console. In the menu of theCRM system, choose Middleware Administration Administration Console.

1.4.3 Contact ReplicationWith CRM release 3.1, business partner contacts from an OLTP system containing theFI-CA component can be replicated in a CRM system.FilterYou can use the filter conditions (see SAP online help) to limit the dataset during theinitial and delta downloads. The BPCONTACT and PARTNER (contact number andbusiness partner number respectively) of the OLTP table BCONT are predefined by SAPfor the SI_BCONTACT download object.

For general information on CRM filters, go to Help SAP Library SAP CustomerRelationship Management and SAP Enterprise Buyer Customer RelationshipManagement Basis Techniology CRM Middleware Adapters and Site TypesAdapters Adapter Framework Perform Configuration Object ManagementManage Objects Define Filter for Object.

Note:

In order to compare delta downloads with the filter conditions, you store the filtersin the CRMFILTAB table of the OLTP system, which is accessed via the Filtersync. (R/3) pushbutton.

http://service.sap.com/


10 / 21

If required, after the download, ensure that this table no longer contains nowredundant filters that were set for the delta downownload.

Sample filter(transction R3AC1 filter criteria for object SI_BCONTACT)

Initial DownloadBefore you start the initial download, make your settings for the block size of theselection (which also determines the number of data records in a mBDoc) and the filterconditions. To do this, go to the SAP Easy Access menu and choose MiddlewareData Exchange Object Management Business Objects (transaction R3AC1). Useappropriate filters to test the initial download, for example by downloading the first 100contacts to the CRM system in block sizes of 10 contacts. In this way, you can easilyand quickly identify and correct any potential errors.


11 / 21

Object overview of the download objects (transaction R3AC1)

The initial download of the contacts can be repeated as many times as necessary.

Note:

If you encounter problems replicating the filter settings, an alternative method is touse the report EXPORT_SMOF_CRMFILTAB. This is a special OLTP report.Make sure that the fileter settings are identical in both systems (R/3 OLTP tableCRMFILTAB).

Then go to the SAP Easy Access menu of the CRM system and choose MiddlewareData Exchange Initial Data Tranfer Start (transaction R3AS- start initial download).In the Load Object field, enter SI_BCONTACT and select the sender or recipient page(using the F4 help if necessary.

Note:

For information on the data exchange, go to Help SAP Library SAPCustomer Relationship Management and SAP Enterprise Buyer CustomerRelationship Management Basis Technology CRM Middleware Adapterssnd Site Types Adapters Adapter Framework Diverse. If errors occur, seethe outbound and inbound queues (transactions SMQ1 and SMQ2) of therespective systems.


12 / 21

If you have executed the transaction, there should be the same number of BDocs in theCRM system as the blocks you selected. You can verify this in a number of differentways. Several of these are listed in the SAP Easy Access menu of the CRM systemunder Middleware Monitoring. For an overview of the BDocs, choose MiddlewareMonitoring Message Flow Display BDocs (Transaktion SMW01). (In turn, the BDoctype is BUS_TRANS_MSG. This BDOc type is the same as is used for the replication ofcontracts.

BDoc overview (transaction SMW01)

Caution

If an error occurs in a block then the data records of the block are not created.You can manually re-transport blocks containing errors, for example via the filter.

Note:

In the event of an error, choose the Extension Data pushbutton to display thedata structure of the BDoc.


13 / 21

Data structure of a BDoc (activity header- ACTIVITY_H)

The BDoc type used is BUS_TRANS_MSG, which is a standard CRM BDoc type.Generally, the data structures contain all the tables required to process a transaction. Inthis case, that means the following structures:

ORDERADM_H – transaction header

ACTIVITY_H – activity data

PARTNER – Partner (data)

ORGMAN – organizational data

APPOINTMENT – date data

DOC_FLOW – object links


14 / 21

(STATUS) – status information

TEXT und TLINE – notes/texts

Once you have corrected the errors, use the pushbutton (Retry to processmessage) to re-trigger the BDocs.

CautionBefore you start the initial download of the contacts, ensure all the businesspartners were created without error.

Delta DownloadGenerally, the delta download is triggered if you use the standard functionality whensaving a contact, meaning when you create a new contact, or change an existing one.The queues thereby generated can be recognized by the ‘D’ in the queue name (forexample, delta download of partner with OLTP key 14895 =R3AD_BUPA_0000014895). Initial downloads can be recognized by the ‘I.’ Otherwise,the processing of queries is identical to that during the initial download.

During the initial download, a lock entry is automatically generated in the outboundqueue for delta downloads with the business partner type. Delete this if necessary.

For more information, see the standard help in the SAP Library.

Business PartnerFor information on the OLTP settings for replicating business partners, see the SAPService Marketplace under http://service.sap.com. Choose Login now and enter your username and password. Then choose Solution Details Industry Solutions mySAP Utilities

Product Information mySAP CRM for Utilities Cookbooks & Guidelines IS-USpecific Set-up-and-Download Guide for Business Partners.

1.5 Settings

1.5.1 OLTP System SettingsYou make the most important settings in several Customizing tables. Currently, youcannot maintain these table in the IMG, you must therefore use transaction SM30(enhanced table maintenance).

Central Mapping Settings: Table BPCT_CRM_CLASSYou can configure the central mapping rules in the BPCT_CRM_CLASS table. This tablecontrols the following functions (dependent on the contact class, contact action, contacttype and direction):

Should there be a replication (distribution)?

http://service.sap.com/


15 / 21

Should a template be used when an activity is created (GUID of business partneror contact type)?

Which transaction type and activity category should be used?

Should the activity description be predefined or summarized from the texts of thecontact class/history?

Example

You can configure the system to replication all the contacts that consist of a certaincombination of contact class, action, and type- with the exception of those contactswith the contact direction ‘internal.’

Replication settings (table BPCT_CRM_CLASS)

The screen below is the detailed screen for a single entry.


16 / 21

Replication settings (table BPCT_CRM_CLASS)The entry displayed above would have the following effects:

All contact with class 1 and action 1 would be replicated (distribution has beenselected),, provided there is no special entry that prevents distribution for certain contacttypes or directions. When the contact is created in CRM, the data of the templatecontact is displayed with that of the GUID 48345...C61. The contact contains thetransaction type 0000 and category 001.

Caution

To activate the replication, you must make at least one entry in theBPCT_CRM_CLASS table (with, for example contact class = contact action = contacttype = contact direction = SPACE). Make sure the Distribution indicator is set in theentry. If you do this, all the selected contacts – subject to whether the middlewarefilter has been set – are replicated

Note:

Provided you have integrated the CRM accordingly, all the fields have F4 help.


17 / 21

Mapping the Contact Direction: - Table BPCT_CRM_DIRECT

The Contact Direction field in the OLTP can have many different, as well as user-definedattributes. The comparable field in the activity is defined with fixed values from the datadictionary. Therefore, a mapping rule must be defined between these two fields.

If there is no entry in the table, either the value from the template activity is used or anew activity, ‘No Direction’ is created for the direction.

Display View “Mapping Contact Direction: Contact -> Activity”: Overview

Settings for mapping the contact direction (table BPCT_CRM_DIRECT)

Modelling the Contact Priority: Tabelle BPCT_CRM_PRIO

Both the Contact Priority field in the OLTP and the comparable field in the activity canhave a number of different, as well as user-defined fields. Therefore, a mapping rulemust be defined between these two fields.

If a suitable entry cannot be found during the download, the original priority is replicated.This may result in an error in the contact in CRM.


18 / 21

Display View “Mapping of Contact -> Activity”: Overview

Contact priority settings (table BPCT_CRM_PRIO)

Modelling the Text ID: Table BPCT_CRM_TDID

In the standard system, the contacts have the BCONT texts object with the BCON textID. During replication, the text object is replaced with the text object of the activity. TheBCON text ID is converted to the A002 text ID (notes) of the activity.

If you have defined an additional text ID for the BCONT text object, you must enter thisID here, and specify the required target text ID for the CRM_ORDERH text object. Notethat if you use the F4 help, the system displays all the text ID for the CRM_ORDERHtext object. Only select a text ID that you have also defined in the text procedure for thetransction type.


19 / 21

Display View “Mapping of Text Contact -> Activity”: Overview

Text ID settings (table BPCT_CRM_TDID)To ensure that all F4 helps in the Customizing tables function (especially those for thetemplate activity in table BPCT_CRM_CLASS), you have to have set up a dialog-enabled RFC connection and the logical system for the CRM system. Carry out thefollowing to do this:

1. Set up the logical system in the CRM system in the Customizing menu underSAP WEB Application Server SAP WEB Application Server Application LinkEnabling (ALE) Sender and Receiver Systems Logical Systems DefineLogical System

2. Once you have done this, enter a standard destination for dialogs. To do this goto the Customizing in the CRM system and select SAP WEB Application Server

Application Link Enabling (ALE) Sender and Receiver Systems Systemsin Network Define Target Systems for RFC Calls

1.5.2 Settings and Modifications in CRMApart from the middleware filter settings and basic activity settings, you do not have tomake any special settings for replication in CRM:

You can still use the ECRM_BCONT_DOWNLOAD BAdI in order to modify replication tomeet your requirements. To do this, modify the CRM_DOWNLOAD_FILL_DATA methodof the IF_EX_ECRM_BCONT_DOWNLOAD interface.

1.5.3 Customer Enhancements in the OLTP SystemIn the OLTP, customers can enhance the contact by creating the customer includeCI_BCONT. During replication, use the field contents in the following way:

In the OLTP system, create an append structure for structureBAPI_BCONTACT_CRM_LOCAL

In this structure, include all the fields of the CI_BCONT customer include that youwant to be transported to the CRM system.


20 / 21

In the CRM system, create an append structure for structureBAPI_BCONTACT_CRM.

Nehmen Sie in diese Struktur alle Felder des Kundenincludes CI_BCONT auf,die Sie ins CRM-System während der Replikation transportieren wollen

In this structure, include the same fields (data type/length), in the same order, asabove

These fields can now be used for further processing in the BAdI.

The graphic below gives an overview of this procedure. The fields F1, F2 and F4 fromthe customer enhancement are transported to the CRM system, whereas the field F3 isnot.

CI_BCONTBCONT F1 F2 F3

BAPI_BCONTACT_CRM_LOCAL F1 F2 F4

Append structure ZCON_BCONT

BAPI_BCONTACT_CRM F1 F2 F4

Append structure ZCON_BCONT_CRM

BAdI ECRM_BCONT_DOWNLOADMethod CRM_DOWNLOAD_FILL_DATA

BAdI ECRM_BCONT_DOWNLOADMethod CRM_DOWNLOAD_FILL_DATA

MOVE-CORRESPONDING

Message BDocBUS_TRANS_MSGMessage BDoc

BUS_TRANS_MSG

F4

CRM

OLTP

Modelling user-defined fields

1.6 Further Notes

1.6.1 Template ActivityIn most cases, you do have to use a template activity. When you define the transactiontype, use procedures that set up the replicated contacts in accordance with yourrequirements.


21 / 21

1.6.2 Error AnalysisIn the case of delta downloads, the queue name used in contact replication isR3AD_BUPA<partner number>. In the case of initial downloads, it isR3AI_SI_BCONTACT.

If a contact was not correctly replicated, use either transaction SMQ2 (qRFC monitor forinbound queue) or SMQ1 (qRFC monitor for outbound queue) to check the replicationqueues. Here you can find messages that refer to the error(s). You can display the BDocand its data using transaction SMW01.

If a contact is incorrectly created in CRM, you can re-work it using transactionCRMD_BUS2000126. Note that if this occurs, you should check your replication settingsin Customizing (see unit 8.5)

1.6.3 SizingIf you want to use contact replication, first use the QuickSizer to estimate how muchhard disk and CRM hardware are required.

You can find the requirements for activity management in the Quick Sizer Navigationunder mySAP Customer Relationship Management.

replication bp contacts

Documents