When a table is replicated to the target system, the replicated data can also be saved to database tables in the SAP Landscape Transformation Replication Server system for a period of time. Thus, if any data is missing from the target system, you can view this data and replicate it again from the SAP Landscape Transformation Replication Server system to the target system. You can do this, for example, if data is missing after a point-in-time recovery of the target system to a previous state.
You can activate replication logging when creating the configuration in the guided procedure. Alternatively, you can use transaction LTRS (advanced replication settings) to activate replication logging for an existing configuration. You can also deactivate replication logging here.
Under Replication Logging, you can specify settings for replication logging. If replication logging is active, the system saves the replicated data entries in the SAP Landscape Transformation Replication Server system. Thus, if any data is missing from the target system, you can view this data and replicate it again from the SAP Landscape Transformation Replication Server system to the target system.
By default, replication logging applies to all tables in a configuration. Under Object or Table-Specific Settings, you can activate replication logging for specific tables in a configuration. You can also change the recording interval for the tables; the default is three days.
You can display and, if necessary, retransfer already replicated data packages with the expert function Logged Replication Data in the SAP Landscape Transformation Replication Server cockpit.
Note
For more information refer to:
SAP Note 2544694 - How to enable Replication Logging for tables in a configuration – SLT
SAP Note 2953252- How to use SLT Replication Logging to recover from lost data on the target DB
SAP Note 3106954- How to view data in replication logging packages – SLT, SLT Guide Online
Note
Replication logging only works for target systems that are connected to the SAP LT Replication Server system by means of a database connection. It is therefore not possible for scenarios with RFC connected target systems, such as Central Finance, and BW scenarios, such as ODP.
Data packages which have been read from SAP cluster tables are stored in table IUUC_RL_DATA_CL. All other data packages (originating from transparent and SAP pool tables) are stored in table IUUC_RL_DATA.
Note
In Expert Functions, in transaction LTRC, you can open the menu for the logged replication data.
When you select a table, the system displays all packages for the table by default. You can reduce the number of packages by adjusting the time interval accordingly.
To view the replicated records, choose an entry in the Package ID field.
To transfer the data in all listed packages from the SAP Landscape Transformation Replication Server system to the target system again, choose Transfer.