In LTRS transaction, if the Trigger Options for Source System folder is available for your Configuration (and its Change Data Capture mechanism), you can also specify settings related to data aging under the Options for Recording Changes section.
Note
If you are using data aging functionality in the source system, the field used for data aging can have a large volume of updates to reflect the current temperature of the data. In this situation, avoid recording any changes to this field and replicating the changes to the target system.
It provides the following options:
Record Changes to All Fields
If you choose this option, the SAP Landscape Transformation Replication Server records all changes to all fields. It replicates these changes to the target system.
Do Not Record Changes to Specific Fields
If you choose this option, the SAP Landscape Transformation Replication Server does not record any changes to specific fields. You specify the non-key fields under Excluded Fields.
- Do Not Record Changes to Specific Fields and Standard Data Aging Field
If you choose this option, SAP Landscape Transformation Replication Server will not record any changes to specific fields and the standard data aging field ( _DATAAGING). You specify the non-key fields under Excluded Fields. If you do not specify any fields under Excluded Fields, this option works for the standard data aging field ( _DATAAGING) only.
Note
Restricting Access to the Source System
By default, the SAP LT Replication Server system has unrestricted access to all tables in the ABAP-based SAP source system. However, there may be situations where you want to restrict the access to data. To do this, you can use table DMC_C_WL_TABL_OP in the ABAP-based SAP source system. This table is delivered empty, which means that the SAP LT Replication Server system has unrestricted access to all tables.
In this table, you can specify which remote RFC user can access which tables in the source system. In addition, you can specify the type of the action that can be performed on the table.
The following actions are possible:
- Read table metadata
- Load data from the table
- Replicate data from the table
- Create a freeze trigger for the table: A standard database trigger records changes to a table (INSERT, UPDATE, and DELETE statements) in a logging table. If a freeze trigger exists for a table, then the system returns an error message if a standard database trigger records a change for the table. Instead of creating an entry in the logging table for the trigger, the system creates an error message. In this way, you can use freeze triggers to prevent changes to the source system table, and to be informed if any attempt is made to change data in the table.
If the DMC_C_WL_TABL_OP table contains at least one entry, then the system restricts access to data to only those entries. If you want additional access to data, you need to create additional entries in the table.
If the action READ_METADATA is permitted for a table, and the table has include structures, you must also permit the action READ_METADATA for the include structures. Note that it is not necessary to permit other actions such as LOAD_DATA or REPLICATE_DATA for the include structures.
Note
Note
Note
For SAP Landscape Transformation Replication Server versions SP13 and lower, the IUUC_TAB_ALLOWED table was used to restrict access to the ABAP-based SAP source system. For SP14 and higher, the table DMC_C_WL_TABL_OP is used to restrict access. If you are installing SAP LT Replication Server for the first time (using SP15), both tables will be delivered empty, and you can use the table, DMC_C_WL_TABL_OP, as described in this section.
If you are upgrading to SP15 from a lower SP, the system checks whether there are any entries in the DMC_C_WL_TABL_OP table. If the table is empty, the system checks whether there are any entries in the IUUC_TAB_ALLOWED table. If there are entries in the IUUC_TAB_ALLOWED table, then these entries will be considered by the system. If you subsequently make an entry in the DMC_C_WL_TABL_OP table, then only the DMC_C_WL_TABL_OP table will be considered by the system; the IUUC_TAB_ALLOWED table will be disregarded completely. So, while it is possible to continue using the IUUC_TAB_ALLOWED table, we strongly recommend using the DMC_C_WL_TABL_OP table instead.
Note that if you permit actions for a table using the IUUC_TAB_ALLOWED table, and the table has include structures, you must also permit actions for the include structures.