Kontakt

Ansicht
Dokumentation

IUUC_REDEFINE_DB_TRIGGERS - Redefine the DB triggers for one or multiple tables

IUUC_REDEFINE_DB_TRIGGERS - Redefine the DB triggers for one or multiple tables

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

When SAP Landscape Transformation Replication Server replicates a table to the target system, it creates a database trigger that records any changes in a logging table.

Normally, if you want to adjust the trigger for a table that has the status In Replication, we recommend stopping the replication process (in transaction LTRC), adjusting the settings for the trigger (in transaction LTRS) and restarting the replication process for the table (using transaction LTRC).

However, in certain situations, you can redefine the trigger for the table, without stopping the replication process for the table.

It is not possible to redefine triggers if you are using one of the following databases in the source system:

  • SAP MaxDB
  • Sybase ASE

Features

You can use this report to redefine a trigger for a table in the following situations:

  • If a table has an active trigger, and the settings for the trigger are changed (using transaction LTRS), you must use this report in order for the changes to take effect.
  • For a configuration, you can specify whether triggers should record changes to a single client specified in the RFC connection, or if they should record changes to all clients. If you change this setting, you must us this report in order for the changes to take effect.
  • You want use transaction LTRS to specify options for archiving for the table.
  • You want to change your configuration from a 1:1 configuration (where a single source system replicates data to a single target system) to a 1:N configuration (where a single source system replicates data to multiple single target systems).
  • You want to use table ranges to improve performance, or you want to stop using table ranges. Note that you use transaction LTRS to specify settings for table ranges.
  • You want to exclude specific fields from the replication process.

Selection

Specify the relevant mass transfer ID, and the relevant table (or tables).

Note

The field Lock Timeout Value is only relevant if the source system database is Microsoft SQL Server. We recommend not changing the default value.

The field Use Ranges for Logging Table is only relevant if you want to change the settings for ranges as described below.

Additional Information,,

Changing Settings for Table Ranges

For a table with an active trigger, you can use table ranges to improve performance. Alternatively, if the table is already using ranges, you can stop using the ranges.

In Advanced Replication Settings (transaction LTRS), you can divide the logging table into ranges. Dividing the table into ranges improves performance because the jobs can transfer the data for each range at the same time. For more information about ranges, see the documentation for transaction LTRS under Performance Options.

If the relevant table is not using table ranges, and you want to use ranges, make the appropriate settings for the table in transaction LTRS, and select the Use Ranges for Logging Table checkbox in this report. Note that if you are using this option, we recommend running the report at a time of low activity for the source system table. Reason is that in this case, a hash calculation must be done for each existing logging table record.

If the relevant table is using table ranges, and you want to stop using ranges, make the appropriate settings for the table in transaction LTRS, and select the Use Ranges for Logging Table checkbox in this report.

Changing Your Configuration from a 1:1 Configuration to a 1:N Configuration

Note that we do not recommend changing your configuration from a 1:1 configuration (where a single source system replicates data to a single target system) to a 1:N configuration (where a single source system replicates data to a multiple single target systems). Such a change can result in inconsistencies. If changing the configuration cannot be avoided, the following additional activities are required:

1.,,In the source system, add the following authorizations to the user assigned to the RFC connection from the SAP LT Replication Server system to the source system:

  • Authorization object S_DEVELOP (ABAP Workbench)

  • Field Activity: Value 42

  • Field Devclass: Value $TMP

  • Field OBJNAME: /1CADMC/* and /1LT/*

  • Field OBJTYPE: TABL

  • Field P_GROUP:

2.,,In the SAP Landscape Transformation Replication Server system, for the relevant configuration, in table IUUC_MT_HEADER set the value of the field MULTI_LOGTAB_USE to X. In table IUUC_REPL_CONFIG, set the value of the field REUSE_SENDER to X. Ensure that field SCENARIO_GUID in table IUUC_MT_HEADER contains the GUID of the configuration. Note that you can obtain the GUID of the configuration from table IUUC_REPL_MAP.

3.,,In transaction LTRC, stop the replication process for the configuration by deactivating the configuration.

4.,,In transaction LTRC, use the expert function Reset Status of Tables and Synonyms and select the checkbox Reset Table/Syn. Receiver.

5.,,In transaction LTRC, use the expert function Reset Replication Object Definition.

6.,,In the SAP Landscape Transformation Replication Server system, run report IUUC_REDEFINE_DB_TRIGGERS, and specify the corresponding mass transfer ID. Note that executing this report will not only change the trigger definition but also the definition of the logging table. We therefore recommended running the report at a time of low activity for the relevant tables.

7.,,Remove the authorizations assigned to the RFC user in step 1 above.

8.,,Restart the replication process for the configuration.

Recording Changes to a Single Client Instead of All Clients

If a configuration is recording changes to all clients in a system, you can change this behavior such that the configuration only records changes to a single client specified in the RFC connection. To do this, proceed as follows:

For a configuration, you can specify whether triggers should record changes to a single client specified in the RFC connection, or if they should record changes to all clients.

1.,,In the SAP Landscape Transformation Replication Server system, open transaction SE16. For tables IUUC_MT_HEADER and IUUC_REPL_CONFIG, set the value of the fields CLIENT_SPECIFIC and RFC_CLIENT_ONLY to X.

2.,,Run report IUUC_REDEFINE_DB_TRIGGERS for the relevant configuration.

3.,,Ensure that the logging table does not contain any records that refer to other clients. That is, it should only contain records for the client specified in the RFC connection.

4.,,Regenerate the runtime objects as described in SAP Note 2109952.

Excluding Specific Fields from the Replication Process

You can exclude certain fields from the replication process. This can be advantageous in certain situations. For example, 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, it would make sense to avoid replicating any changes to this field to the target system

Prerequisites

The source system must be an ABAP-based SAP system running on SAP HANA (minimum support package stack 12). The source system must have the add-on DMIS2011 with at least support package SP12.

To do this, proceed as follows:

  • In the source system, use transaction SM30 to create an entry in table IUUC_BL_TAB for the relevant table.
  • Specify the name of the table in the field Table Name, and set the value of the field SWITCH to 'X'.
  • By default, the system will exclude the field with the naming convention "_DATAAGING" from the replication process (assuming a field with the naming convention "_DATAAGING" exists in the relevant table). However, if you want to exclude specific fields from the replication process, you need to specify them in table IUUC_BL_FIELD.

  • In the SAP Landscape Transformation Server system, run report IUUC_REDEFINE_DB_TRIGGERS and specify the relevant mass transfer ID and the table name.

Changing Settings for Archiving

If you are replicating data to a target system, and want to change settings for archiving (using the 'Options for Archiving' feature in transaction LTRS), you must recreate the trigger in order for the changes to take effect. For more information about the different options, see Options for Archiving.






Addresses (Business Address Services)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 10327 Date: 20240520 Time: 093004     sap01-206 ( 167 ms )