Kontakt

Ansicht
Dokumentation

DTL_MT_RT_REMOTE_GEN - generate runtime objects in remote systems only (OBSOLETE)

DTL_MT_RT_REMOTE_GEN - generate runtime objects in remote systems only (OBSOLETE)

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This API allows to generate the runtime objects of all or selected conversion objects of a mass transfer. Only the runtime objects in the sender and / or the receiver system or generated, but not those in the central system.

Generating the runtime objects for a receiver system is required if, after a data transfer is completed, the same data should be transferred into another receiver system.

Generating the runtime objects for a sender system is required if, after all runtime objects (for all systems) have been generated, the sender system is exchanged (e.g. system copy, snapshot system).

The API can be called in three different modes:

E Schedule a batch job to perform the generation (asynchronous processing)

S Return state

L Return list of application log numbers

Input parameters:

  • I_MODE
    Controls if the activity should be executed, or if status or log information is requested, or if the data transfer jobs should be canceled Required
  • I_MT_ID
    Mass transfer identifier. Required if called in execution mode
  • I_PACKID
    PCL package ID
  • I_SESSID
    PCL session ID.
  • I_NO_OF_JOBS
    Number of batch jobs to be created Optional (default 1)
  • IM_RESTART
    If set to true, this parameter indicates that for a running run time objects generation, additional jobs should be started, possibly due to the cancellation of jobs of the initial invocation. In this case, the status "in_process" of MT_TABLES entries must not be reset. Only the difference between I_NO_OF_JOBS and the number of already running or scheduled jobs will be scheduled.
  • I_GEN_SND
    the runtime objects should be generated on the sender side
  • I_GEN_RCV
    the runtime objects should be generated on the receiver side

Returning parameters:

  • E_LOGNUMBER
    Log number of the schedule log if API is called in execution mode
  • ET_LOGNUMBERS
    Table of logs for the session ID if called in "get log" mode, together with the batch job name and batch job count.
  • ET_STATUS
    Filled if API is called in "get status" mode: Tables containing status information both for the scheduling API and for the scheduled batch job. This information includes a status (running, finished with errors / warnings; success), time stamps for start and end, batch job number, server etc

Error situations handled by this API if called in execution mode. In this case, processing is cancelled, and no batch jobs are scheduled:

  • runtime object generation is neither requested for the sender system nor for the receiver system
  • mass transfer does not exist - activity is cancelled

Further information

This API schedules a batch job for report DTL_MT_RT_REMOTE_GEN which does the actual processing





Parameters

ET_LOGNUMBERS
ET_STATUS
E_LOGNUMBER
IT_TABLES
I_GEN_RCV
I_GEN_SND
I_MODE
I_MT_ID
I_NUM_OF_JOBS
I_PACKID
I_RESTART
I_SESSID

Exceptions

Function Group

DMC_DTL

PERFORM Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 3684 Date: 20240523 Time: 114027     sap01-206 ( 60 ms )