Ansicht
Dokumentation

IUUC_CREATE_NONSAP_TABLES - Create SAP DDIC table definitions, synonyms, etc

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Purpose

If data are to be transferred and / or replicated from non-SAP systems into SAP by means of DB connections defined in the SAP system, the following objects need to be created:

• In order to perform a data load, in the SAP DDIC of the central system used for the transfer, corresponding tables need to be created (only in the DDIC, not in the DB system). For these, an artificial name with a namespace prefix is used. Furthermore, a synonym (or alias) is created to link this SAP DDIC table to the DB table in the non-SAP system.

• In order to perform a permanent replication, DB triggers and logging tables need to be created in the nonSAP system. For these logging tables, we again need corresponding SAP DDIC tables in the SAP system, and a linkage of these to the nonsap system logging tables by means of synonyms.

This report allows to create all the objects mentioned above except for the DB triggers. The user can choose to create the objects required for either one or both of the processing types mentioned above (initial load or replication).

Integration

In order to prepare a data replication, after creating the logging tables by means of this report, report IUUC_CREATE_NONSAP_TRIGGERS can be used.

Prerequisites

A mass transfer ID must have been created before, and tables of the non-SAP system must have been assigned to this mass transfer.

Features

Selection

Specify the mass transfer to which the tables for which triggers are to be created are assigned. This mass transfer must be linked to a DB connection pointing to the nonSAP sender system database. If the DB connection has not yet been linked to the mass transfer ID, you can do this here by specifying also the DB connection name.

You can only process tables belonging to the same DB schema. The name of this schema must be specified.

Depending on the DB system, the logging tables might need to be assigned to a tablespace, which needs to be specified.

In order to define table fields with the correct field size, it is necessary to specify if the referred DB system is a Unicode system or not.

You can further restrict the set of tables for which triggers are to be created, if this should not be done for all tables of the mass transfer.

Standard Variants

Output

Activities

If you create logging tables, then the names of the synonyms and the SAP DDIC table definitions will be created according to the naming convention /1CADMC/nnnnnnnn (namespace prefix + 8-digit number).

Concerning the initial load, the name of the synonym and the SAP DDIC table definition will be /1CADMC/Lnnnnnnn (namespace prefix + L + 7-digit number).

Example

ROGBILLS - Synchronize billing plans   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 3110 Date: 20240520 Time: 081533     sap01-206 ( 65 ms )