Why the Business Partner / Customer exchange does not work?
Sometimes, the exchange between BP’s in a CRM system and Customers in the ECC system fails; sometimes bdoc’s are not created or perhaps they fail with a not very clear error message.
As per my experience, the most of the times the problem lies in tables CRMC_BUT_CALL_FU in CRM system or table COM_BUPA_CALL_FU in the ECC system. These tables contain the necessary Function Modules for making the exchange to work, therefore, you should ensure that the necessary FM’s are active in these tables and on the other hand ensure that any other FM created by you is not interfering in the data exchange.
And, which are the necessary FM’s in these tables? You can find this information in the following notes: 908157 and 757955. Be aware that in note 908157 you can find the FM´s that DO NOT HAVE TO BE ACTIVE from release CRM 5.0 and in note 757955 you can find the FM’s that MUST be active from release CRM 5.0
You can maintain these tables using transaction SM30.
Other typically tables or transactions to be checked when the exchange is not working:
In the ECC system:
- TX: BF31 (table TBE31)
The following FM’s must be present:
00001321 BC-MID PI_BP_CUSTOMER_BTE_1321
CAM_1000 BC-MID PI_BP_COMP_ADDR_COLLECT_DATA
CAM_2000 BC-MID PI_BP_PERS_ADDR_COLLECT_DATA
CAM_3000 BC-MID PI_BP_PERSON_COLLECT_DATA
- TX: BF11 (table TBE11)
The following Events have to be active:
NDI New Dimension Integration
- TX: BF34/BF24 (tables TBE34/TBE34/TPS34)
User exits for the Business Partner relevant events.
At last but not at least, please ensure that this is not a filtering issue!
For download, please check the filters for CUSTOMER_MAIN and CUSTOMER_REL objects in R3AC1 transaction. For the upload, ensure that for your R/3 site, the “All Business Partners (MESG) ” and “All Business Partner Relationships (MESG) ” subscriptions are included in SMOEAC transaction.
The CRM agent will create an account & contact in CRM which replicates to ECC, but if the agent is still editing the data we'll see this error even though the data did replicate between the 2 systems.