Show TOC

  BusinessPartnerReplication

Purpose

You can replicate business partner data between two systems using this integration scenario. In the process a copy of the source system object is made in the target system.

Prerequisites

The integration scenario BusinessPartnerReplication is in the Integration Repositoryin the software component SAP ABA 7.00 in the namespace http://sap.com/xi/ABA...

Process Flow

The integration scenario has two component views. These are defined via the release of the sending system. The releases SAP_ABA 640 and 700 can be used as senders and receivers.

Each of the views consists of the following asynchronous communication steps between sender and receiver:

  1. Send Business Partner

    Sending is triggered in the sending system by creating or changing the business partner data in the dialog, or by using the report BUPA_SEND. For this, the Customizing in table CRMC_BUT_CALL_FU must be set up accordingly. Make the necessary settings in Customizing for Business Partner under Start of the navigation path Data Distribution Next navigation step Activate Function Modules End of the navigation path .

    For more information, see the documentation of report BUPA_SEND.

    The sending system transfers the data to the Integration Server.

  2. Receive Business Partner

    After the data is processed on the Integration Server (and in particular after the mapping has taken place), the data is transferred to the receiving system that has been determined. Inbound management takes place in the receiving system. It is also controlled using the settings in table CRMC_BUT_CALL_FU.

    Technical or business errors can occur in the receiving system when the messagesare posted. An error message is then created, which is made available in the local Integration Engineduring inbound processing. The message must be posted later by the system administrator after the problem has been solved.

    For more information on monitoring or on error analysis for XML messages, see Monitor for Processed XML Messages and Defining Conditions and Actions for Troubleshooting .