Communication Configuration in SAP LT Replication Server: SAP ERP and Central Finance

To enable the initial load and replication of CO data and the replication of FI data from SAP ERP systems into Central Finance on an ongoing basis, you must configure communication between the systems in the SAP Landscape Transformation Replication Server (SAP LT Replication Server).

Note Note

The initial load of FI data is managed via Customizing activities in the Central Finance system.

End of the note.

Prerequisites

Software Components

The add-on DMIS 2011_1_700 (or higher depending on the release of the system) is installed in all involved systems. This requires the purchase of the SAP LT Replication Server license.

Note
The minimum support package (SP) level for the steps described in this document is SP08.

End of the note.
SAP Note 2124481 has been installed in all involved systems.

Authorizations

The following authorizations have been assigned to the configuration user in the SAP LT Replication Server system:
- SAP_IUUC_REPL_ADMIN
- SAP_MWB_PROJECT_MANAGER
The authorization SAP_IUUC_REPL_REMOTE has been assigned to the RFC user in the source system.

Process

Define Configuration

A configuration defines the connection between the source (SAP ERP) system and the target (Central Finance) system.

In the SAP LT Replication Server system, go to transaction LTR (Configuration and Monitoring Dashboard).
Choose the New pushbutton.
Under Specify General Data, enter a configuration name (without any spaces) and a description.
Under Specify Source System, choose RFC Connection and enter the RFC destination.
Under Specify Target System, choose RFC Connection and enter the target system in the RFC destination field. In the Scenario for RFC Communication field, choose Standard RFC scenario.
Under Specify Transfer Settings, define the initial load mode. SAP recommends that you choose the option Performance Optimized. However you should note that this requires approximately 10% additional storage in the source system during the initial load. In the No. of Data Transfer Jobs field, enter the value 1. Note that you can increase this value later on if required.
Under Review and Create, review your settings. If all the settings are correct, choose Create Configuration.

The system creates a new configuration with a new mass transfer ID.

Define Objects

Before you start the replication, you have to create the initial load and replication objects. This scenario involves working with three tables: AUFK, CFIN_ACCHD, and COBK.

In transaction SE38, start program IUUC_REPL_PREDEF_OBJECTSand enter the mass transfer ID that was created by the system.

Define Initial Load Object

Choose Copy Predefined Object, and enter REPL_CFIN in the Project and Subproject fields.
In the Predefined Object field, specify the predefined initial load object. Use the value help to view all available objects.
For every table, there is a load object and a replication object. The load object contains the suffix L (CFI_L). Select one of the load objects.
Under Target Object, specify the table name. Use the same table that you specified for the predefined object. For example, if your predefined initial load object is CFI_AUFK_L, the corresponding table name is AUFK.
Ensure that the option Create Predefined Load Object is selected. Confirm your settings.
Repeat the process for the other tables.

Define Replication Object

Choose Copy Predefined Object, and enter REPL_CFIN in the Project and Subproject fields.
In the Predefined Object field, you specify the predefined replication object. Use the value help to view all available objects.
For every table, there is a load object and a replication object. The replication object contains the suffix R (CFI__R). Select one of the replication objects.
Under Target Object, specify the table name. Use the same table that you specified for the predefined replication object. For example, if your predefined replication object is CFI_AUFK_R, your table name is AUFK.
Ensure that the option Create Predefined Replication Object is selected. Confirm your settings.
Repeat the process for the other tables.

Activate Replication Object

Navigate back to the overview of the predefined objects (program IUUC_REPL_PREDEF_OBJECTS) and set the status of the initial load and replication objects to Active.

Control Load/Replication Using SAP LT Replication Server

Note Note

This sections describes how to trigger the initial load and replication of postings from SAP LT Replication Server. Before you can do this, you must first complete the rest of the initial load settings in Customizing for Central Finance.

End of the note.

Once you have activated the objects, you can use SAP LT Replication Server to control the load and replication of data. In the SAP LT Replication Server Cockpit (transaction LTRC) enter your mass transfer ID. On the Table Overview tab page, you can stop or start a table by choosing the Data Provisioning pushbutton.

Enter the table (AUFK, CFIN_ACCHD, COBK) for which you have defined your predefined objects and choose Start Replication.

Note Note

If you choose the option Start Load, the system will execute an initial load of the data that is currently in the system but there will be no delta replication. Choosing Start Replication, executes an initial load of the data and activates delta recording. After the initial load, the replication of delta data will start automatically.

End of the note.

You can monitor the load and the replication in the SAP LT Replication Server Cockpit (transaction LTRC). On the Data Transfer Monitor tab page, you can view the table name once the initial load or replication object has been created. You can check the logs on the Application Log tab page. Before you can view the log entries, you must first define a filter. The log contains details about any problems that occurred during the replication process and details about data that could not be replicated to the target system because of incorrect settings.

More Information

For more information about new developments for the SAP LT Replication Server, see SAP Note 2154420.