Ansicht
Dokumentation

IUUC_CREATE_LOGGING_TABLES_RCV - Create Logging Tables for NZDT in the Receiver System

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Purpose

In this activity, you create logging tables in the receiver system.

These tables are required for the delta replay, as all replicated changes of the original tables need to be also in the receiver system.

As this activity will take some time, it is strongly recommended to schedule batch jobs for its execution. To get the logging tables created and activated as quick as possible, it is recommended to schedule multiple batch jobs. This should be done using the field "number of batch jobs" on the selection screen, not by using the menu function "Execute in background". Only in this case the report can correctly circumvent namespace checks that might otherwise prevent the correct creation of logging tables with field names that shouldn't be used any longer (for technical reasons, the field names of the logging tables need to be the same as the field names of the corresponding original tables).

The report can also be executed to create the tables in the clone system. If they are to be created in the sender system, it must be distinguished if this report runs before or after clone isolation. If it runs before the clone isolation, we need to set a flag to control that later, in the clone system, the logging tables are deleted (and recreated, if requested). Otherwise this flag must not be set to make sure that the logging tables can still be set on the clone.

The selection for table names is only recommended for testing purposes. For the productive incremental upgrade, all tables must be considered.

The following statement is only relevant for Oracle and DB6 (aka IBM DB2 LUW) data base systems:
The logging tables will be assigned to the same tablespace as the respective original tables, unless you specify one or several data classes. In the latter case, the tablespace assignment is done according to the data class(es) you specify (data classes are assigned to table spaces). If you specify multiple data classes, the same number of logging tables is created for each data class (table space).
Example:
You need to create 1200 logging tables and you specify three data classes. In the corresponding assignment table (the name is DB-specific, for example, TAORA, or TADB6), you have done the assignment of data class to table space:

data class,,table space

LOGGING1,,PSAPLOG1

LOGGING2,,PSAPLOG2

LOGGING3,,PSAPLOG3

As a result, to each of the three tablespaces PSAPLOG1, PSAPLOG2 and PSAPLOG3, 400 logging tables will be assigned.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 2989 Date: 20240531 Time: 144659     sap01-206 ( 69 ms )