Ansicht
Dokumentation

ISXV_CTR_ADPT_ID - Define Adapters for Data Replication

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this Customizing activity you define the adapters you want to use for data replication between different applications.

You can use adapters to handle data integration in various systems, such as between SAP CC, SAP CI and SAP CRM in a standard but flexible manner.

SAP ERP adapters and non-SAP ERP adapters are available. This means for example that an SAP ERP adapter is used to replicate contract data to SAP Convergent Invoicing and a non-SAP ERP adapter is used for replication to SAP Convergent Charging.

The reason for using different adapter types is to control rollback response in the application if incorrect data replication takes place and it is necessary to change or write this data to a different system.

Dedicated control of the rollback response is only technically possible between SAP Systems. If an error occurs during data replication to an external system, you can only perform rollback without errors to a status prior to replication in SAP Systems. You can only return the transaction response of data in all involved SAP Systems to an error-free status if an external system is the last system to be executed during data replication.

This has the following implications on the definition of change or create replication scenarios:

• A non-SAP ERP adapter must always be the last adapter in the chain of all adapter calls, so that if replication in the external system is terminated, all upstream SAP Systems can respond to the termination.

• Only one non-SAP ERP adapter can be used during write/change accesses if a non-SAP System is involved, to ensure that (incorrect) data that has already been replicated is not retained.

Adapters are therefore still classified as change and read adapters for the reasons listed above. You can use an adapter as a read or change adapter. There are no restrictions to the number of times you can use read or change adapters.

To ensure that only non-SAP ERP change adapters are used in a chain of several adapter calls, the use of adapters is organized using scenarios.

SAP supplies standard adapters and a standard scenario that contain the adapter used for contract data replication for SAP Convergent Invoicing and SAP Convergent Charging.

Defined adapters for the SAP standard scenario:

Adapter ID	Adapter Type	Maintain	Read	Bezeichnung
FICA	A ERPadapter	X	X	FICA contract adapter
CC	B NonERPadapter	X	X	SAP CC

X

Define your adapters in the first step. Assign an adapter ID and specify whether the adapter is to be used for an internal or external system. Define default values and specify whether this adapter is to be used for change and/or read accesses to the respective system.

If you want to define your own adapters, you have to create an implementation for BAdI: Adapter for Master Data Distribution.

Then assign your new adapter to a replication scenario. This can be done in SAP Customizing under Define Scenario for Contract Distribution.

X

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.

Length: 3906 Date: 20240523 Time: 163738     sap01-206 ( 66 ms )