Kontakt

Ansicht
Dokumentation

DMCDTL_MT_CONVOBJECTS_DEFINE - API: Create conversion objects of a mass transfer

DMCDTL_MT_CONVOBJECTS_DEFINE - API: Create conversion objects of a mass transfer

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report is only to be used in the context of the migration basis technology (MBT) as part of the data transfer layer (DTL). It creates conversion 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).

Integration

For each conversion 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 of class CL_DMC_SUPER_CONV_OBJECT which is then called to create the conversion 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 conversion objects must have been completely defined

Features

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

  • sender / receiver structure cannot be retrieved from sender / receiver system DDIC
  • rule cannot be created because there is already a rule with the same identifier in the project hierarchy
  • no or more than one export parameter specified for field-related rule
  • rule call refers to a non-existing rule identifier
  • rule call refers to a non-existing formal parameter
  • for a rule call, the mapping of formal and actual parameters is incomplete
  • for a rule call, a non-existing sender field is specified as input parameter
  • type mismatch of formal and actual parameters in a rule call
  • for a structure relationship, a non-existing sender or receiver structure is specified
  • specified selection parameter field does not exist in top-level sender structure
  • a conversion object with the specified identifier already exists
  • more or less than one top-level structure specified for sender / receiver container
  • a primary structure relationship is not specified for every receiver structure
  • Wrong field referred in foreign key relationship
  • no data found in PCL for the conversion 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 conversion 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 conversion objects which have been created, along with possible errors that prevented a certain object from being created.

Activities

Example






General Data in Customer Master   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3869 Date: 20240520 Time: 054718     sap01-206 ( 56 ms )