Skip to Content
Technical Articles

Business Partner Sales Area data replication to SAP CRM system not been triggered

Business Partner Sales Area data replication to SAP CRM system not been triggered

 

Problem

There is no BAPI to create business partner sales area data on SAP ECC.

This data might be created through the Customer Processing API (Class CMD_EI_API).

Whether you have the replication of customer data to SAP CRM configured on your system, the event that starts the data replication should be triggered when a BAPI commit is executed.

Solution

After creating the business partner sales area data using the customer API, execute a custom RFC function to send the sales area data to SAP CRM system.

 

BAPI’s on CRM

Sales Data

BAPI_BUPA_FRG0010_ADD -> Add Sales Data for a Business Partner and Sales Area

BAPI_BUPA_FRG0010_CHANGE -> Change Sales Data for a Business Partner and Sales Area

 

Shipping Data

BAPI_BUPA_FRG0020_ADD -> Add Shipping Data for a Business Partner and Sales Area

BAPI_BUPA_FRG0020_CHANGE -> Change Shipping Data for a Business Partner and Sales Area

 

Billing Data

BAPI_BUPA_FRG0030_ADD -> Add Billing Data for a Business Partner and Sales Area

BAPI_BUPA_FRG0030_CHANGE -> Change Billing Data for a Business Partner and Sales Area

 

Status/Sales Area

BAPI_BUPA_FRG0100_CREATE -> Create Status Information for a Business Partner

BAPI_BUPA_FRG0100_CHANGE -> Change Status Information for a Business Partner

 

Transaction control for BAPIs

BAPI_TRANSACTION_COMMIT -> Execute external Commit when using BAPIs

BAPI_TRANSACTION_ROLLBACK -> Execute external Rollback when using BAPIs

 

Ps.: CRM_BUPA_SALES_AREA_TO_CRM – Sales area data conversion: ECC -> CRM

 

Debugguing data exchange between the systems

ECC -> CRM

On ECC system, get from T-CODE SM59 the user configured on CRM RFC connection.

On CRM system, start a trace using the RFC user on T-CODE ST12.

On ECC system, execute the process that triggers the data exchange.

On CRM system, finish the trace.

On the trace analysis or SQL summary, search for the table BUPA_DEBUG.

On the query statements for this table, you will be able to find the function modules that can be debugged. Insert a row on the table BUPA_DEBUG for each function that need to be debugged:

After this, you will be able to debug the process through the function module BUPA_INBOUND_DEBUG, that is just used to force the process to wait 30 seconds.

At this time, you are supposed to run SM50 in a parallel session and catch in debug the current process.

 

CRM -> ECC

On CRM system, get from T-CODE SM59 the user configured on ECC RFC connection.

Set an external breakpoint on FUNCTION CRM_GENERIC_R3_IN for RFC user.

 

Ps.: There are fields that have different length on the two environments.

For example, the field pricing procedure assigned to this customer (Data element KALKS on ECC/ CRMT_CUST_PRIC_PROC on CRM).

The field conversion occurs on SAP ECC system on function module CVI_CRM_MAPPING.

 

Further information

T-CODE

COM_BUPA_CALL_FU/ CRMC_BUT_CALL_FU -> Determining FMs for Data Exchange:BP

SM59 -> RFC Destinations (Display/Maintain)

SMW01 -> Display BDocs

ST12 -> Single transaction analysis

Be the first to leave a comment
You must be Logged on to comment or reply to a post.