Ansicht
Dokumentation

DMCDTL_MT_CONVOBJ_DEF_SENDCNT - Create migration objects of a mass transfer (only sender container)

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

Purpose

This report creates migration objects for a certain mass transfer. For the objects to be created, initial entries must already exist in table DMC_MT_TABLES. The metadata required to create the conversion objects are taken from the process control layer (PCL).
It is assumed that these migration objects are only needed to provide the necessary metadata for the generation of a data selection function module, but not for a real data transfer. Therefore, only rudimentary migration objects are created. They only include the sender data, but no data concerning the receiver side, and data mapping.

Integration

For each migration object to be created, this report calls function module PCL_GET_CONVOBJ to get the metadata of this object.. Then, some mapping is done to make these data suitable for method CREATE_CONV_OBJECT_EXTRACT_ACS of class CL_DMC_SUPER_CONV_OBJECT which is then called to create the migration object on DTL side.

To enable the calling API to return status information to the PCL, the report maintains activity records. For details see the documentation of class CL_DMC_ACT_REC.

Prerequisites

Project, Subproject and Mass Transfer must have been created.

On PCL side, the metadata for the migration objects must have been completely defined

Features

The following error situations are handled by this report. In each case, the corresponding migration object is not created:

• sender structure cannot be retrieved from sender system DDIC

• specified selection parameter field does not exist in top-level sender structure

• a conversion object with the specified identifier already exists

• Wrong field referred in foreign key relationship

no data found in PCL for the migration object

Selection

The processing is done for a certain mass transfer the ID of which must be specified.

It is possible to control whether along with the migration objects, also the selection parameter field in the root table of the sender container should be determined, or if this should be left to a later processing step. (Parameter P_SELPAR)

Parameter P_TADIR controls if the correction and transport system interface is used in the "official" way (with detrimental effects on the performance) or if the TADIR entries are directly accessed.

Standard Variants

Output

There is no list output but an application log is created that lists all migration objects which have been created, along with possible errors that prevented a certain object from being created.

Activities

Example

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3025 Date: 20240601 Time: 011453     sap01-206 ( 55 ms )