Define RFC destinations.
In SAP Customer Relationship Management (SAP CRM), create the RFC connection from SAP CRM to SAP ERP (transaction SM59):
type: 'ABAP Connections'. Use a suitable ERP user, such as CRMOLTP.
In SAP ERP, create the RFC connection from SAP ERP to SAP CRM (transaction SM59):
type: 'ABAP Connections'. Use a suitable CRM user, such as RFC.
Note
Check the transaction SM30, view CRMRFCPAR, to see whether there is an entry for this connection to SAP CRM:
User: CRM
Object name: '*'
RFC destination: here you enter the connection that you just created
Load type: '*'
SAP CRM: Register the CSA* queues in the qRFC monitor.
Check whether queues with the name CSABUPA* (or CSA*) and R3A* exist.
Note
If CSA* is already active, you cannot add CSABUPA* because it is contained in CSA*. In this case, leave this as CSA*. Ensure that the queues are registered.
SAP CRM: Create sites and subscriptions for data distribution using the middleware (transaction SMOEAC).
Create a subscription to the following replication objects and publications for the ERP system:
Replication Object |
Type |
Publications |
---|---|---|
BUAG_MAIN |
Simple Bulk |
Business Agreements (MESG) |
BUPA_MAIN |
All Business Partners (MESG) |
|
BUPA_REL |
All Business Partner Relationships (MESG) |
Caution
Do not create a subscription for the ERP system to publications with the replication object VEND_MAIN.
Settings for the SAP Business Partner
Create number ranges for the SAP Business Partner and assign these to a grouping.
Note
You have to do this in both SAP CRM and SAP ERP. The groupings that you use in the CRM system for business partner distribution in the ERP system, must be identical in the ERP system, and vice versa. You use the grouping criteria to find the corresponding number ranges in the target system. The business partners do not have to have the same number in the CRM and ERP system. However, if this is required, make sure that you create number ranges in the CRM and ERP system that are large enough. In the target system (such as SAP ERP), use external number assignment to assign a number range to each grouping criterion used for identical numbering. In the ERP system, you can also activate the function module COM_BUPA_MWX_MAP_NUMRANGE as described below.
CRM outbound
SAP CRM: Activate the function modules for data distribution (transaction SM30, view V_BUT_CALL_FU).
In SAP CRM, activate BDoc generation for the middleware. Activate the following function modules by setting the Call indicator. The item numbers determine the sequence in which the function modules with the same event and object are executed within a group. The sequence is important only if the absolute values of the items can differ from one another.
Event |
Object |
Item |
Function Module |
Call |
---|---|---|---|---|
CRMOU |
BUPA |
1000000 |
BUPA_OUTBOUND_BPS_FILL_CENTRAL |
X |
1200000 |
CRM_BUPA_OUTB_BPS_FILL_MD |
X |
||
1300000 |
CRM_BUPA_BDOC_BPS_FILL_DATA |
X |
||
2000000 |
ABA_FSBP_OUTBOUND_BPS_FILL |
X |
||
BUPR |
1000000 |
BUPA_OUTBOUND_BPR_FILL_CENTRAL |
X |
|
1200000 |
CRM_BUPA_OUTB_BPR_FILL_MD |
X |
||
1300000 |
CRM_BUPA_BDOC_BPR_FILL_DATA |
X |
||
BPOUT |
BUPA |
200000 |
BUPA_MWX_BDOC_CREATE_MAIN |
X |
BUPR |
100000 |
BUPA_MWX_BDOC_CREATE_REL |
X |
|
CLEAR |
BUPA |
1000000 |
BUPA_OUTBOUND_CLEAR_FLAGS |
X |
2000000 |
ABA_FSBP_OUTBOUND_CLEAR_FLAGS |
X |
Note
Do not activate the following function modules in the CRM system if you use the Leasing scenario; that is, do not set the Call indicator. However, do not delete any entries from the table because the function modules can be used for other purposes.
Event |
Object |
Item |
Function Module |
Call |
---|---|---|---|---|
CRMOU |
BUPA |
Any |
CRM_BUPA_BDOC_BPS_FILL_VENDOR |
|
ABA_FSBP_EMP_TO_ROLE_OUTBOUND |
||||
BPOUT |
BUPA |
VEND_MWX_CREATE_MAIN_BDOC |
||
BUPA_OUTBOUND_MAIN*) |
||||
BUPA_OUTBOUND_ALE_MAIN |
||||
BUPR |
UDM_OUTBOUND_ALE_REL |
|||
BUPA_OUTBOUND_REL*) |
||||
BUPA_OUTBOUND_ALE_REL |
||||
BUPX |
MDS_BUPA_OUTBOUND |
|||
R3AOU |
BUPA |
BUPA_MWX_BDOC_UP_CURRSTATE_SET |
||
XIOUT |
BUPA |
Any *) |
||
BUPR |
Any *) |
*) If an XI distribution of business partners is required for other systems (ERP systems or third-party systems), you have to activate these function modules. In this case, ensure that XI does not distribute the business partner data to the same ERP system as the middleware.
ERP inbound and synchronization
SAP ERP: Call the transaction SM30, table CRMSUBTAB, and check whether the following entries have been made. Set the Inactive indicator as below:
User |
Object Name |
Upload/Download |
Object Class |
Function Module |
Inactive |
---|---|---|---|---|---|
CRM |
BUPA_MAIN |
U |
BUPA |
FSL_BUPA_MAIN_INBOUND |
|
CRM |
BUPA_MAIN |
U |
BUPA |
COM_BUAG_MAIN_INBOUND |
|
CRM |
BUPA_REL |
U |
BUPA |
COM_BUPA_REL_INBOUND |
|
CRM |
VEND_MAIN |
U |
BUPA |
COM_VEND_MAIN_INBOUND |
X |
Define function modules for data exchange
SAP ERP: Call the transaction SM30, view COM_BUPA_CALL_FU, and activate the following function modules by setting the Call indicator.
Event |
Object |
Item |
Function Module |
Call |
---|---|---|---|---|
R3OBI |
BUPA |
1000100 |
FSL_BUPA_MAIN_BP_INBOUND |
X |
BUPA |
1000100 |
FILA_BUPA_MAIN_BP_INBOUND |
X |
|
BUPR |
1000000 |
COM_BUPA_REL_BP_INBOUND |
X |
|
R3IN |
BUPA |
800 |
FSL_BUPA_INBOUND_FILTER_IDENT |
X*) |
800 |
FILA_BUPA_INBOUND_FILTER_IDENT |
X*) |
||
900 |
FSL_BUPA_INBOUND_MWX_ADD_ROLES |
X |
||
900 |
FILA_BUPA_INBOUND_ADD_ROLES |
X |
||
1000 |
FSC_BUPA_MWX_FILTER_MAIN |
X |
||
10000 |
COM_BUPA_MWX_FILTER_MAIN |
X |
||
BUPR |
10000 |
COM_BUPA_MWX_FILTER_REL |
X |
|
100000 |
COM_BUPA_MWX_MAP_REL_CENTRAL |
X |
*) Activate only if the identification types CRM002 and CRM004 are not used in the ERP system.
If you want to use the same numbers that you used in the CRM system for the SAP Business Partner in the ERP system, you have to activate the following check module. If a business partner created in the ERP system does not receive the same number, this function module terminates processing and creates a BDoc error that you can view in the CRM system.
Event |
Object |
Item |
Function Module |
Call |
---|---|---|---|---|
R3IN |
BUPA |
50000 |
COM_BUPA_MWX_MAP_NUMRANGE |
X |
Note
Do not activate the following functions modules in the CRM system if you use full service leasing; that is, do not set the Call indicator. However, do not delete any entries from the table because the function modules can be used for other purposes.
Event |
Object |
Item |
Function Module |
Call |
---|---|---|---|---|
R3OBI |
BUPA |
Any |
COM_BUPA_MAIN_BP_INBOUND |
|
PI_BP_PROXY_BAPI_CUSTOMER |
||||
BUPR |
PI_BP_PROXY_BAPI_CUSTOMER |
|||
VEND |
PI_BP_PROXY_BAPI_VENDOR |
|||
R3IN |
BUPA |
COM_BUPA_MWX_MAP_MAIN_CENTRAL |
||
FSL_BUPA_MWX_MAP_MAIN_CENTRAL |
*) |
*) Obsolete, do not use this entry. Delete this entry but do not delete any other entries.
SAP ERP: Activate function modules
SAP ERP: Call the transaction SM30, view V_BUT_CALL_FU, and activate the following function modules by setting the Call indicator. The item numbers determine the sequence in which the function modules with the same event and object are executed within a group. The sequence is important only if the absolute values of the items can differ from one another.
Event |
Object |
Item |
Function Module |
Call |
---|---|---|---|---|
CRMIN |
BUPA |
1000000 |
BUPA_INBOUND_MAIN_CENTRAL |
X |
2000000 |
ABA_FSBP_INBOUND_MAIN |
X |
||
BUPR |
1000000 |
BUPA_INBOUND_REL_CENTRAL |
X |
|
CRMOU |
BUPA |
1000000 |
BUPA_OUTBOUND_BPS_FILL_CENTRAL |
X |
BUPR |
1000000 |
BUPA_OUTBOUND_BPR_FILL_CENTRAL |
X |
|
BPOUT |
BUPX |
1000000 |
MDS_BUPA_OUTBOUND |
X |
(The CRMOU and BPOUT events are relevant for internal synchronization via CVI.)
Other function modules may be required, such as for the MERGE event.
Caution
If you use the Leasing scenario, do not activate the following function module in the CRM system; that is, do not set the Call indicator.
Event |
Object |
Item |
Function Module |
Call |
---|---|---|---|---|
CRMIN |
BUPR |
Any |
FS_BPREL_DIST_CRITERIA_ROLE |