Ansicht
Dokumentation

DTL_MT_CONVOBJS_RESET - Delete conversion objects of a mass transfer

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

Functionality

This API is used to delete all or a subset of the conversion objects of a certain mass transfer.

It can be called in 4 different modes (input parameter IM_MODE):

E,,Start deletion of conversion objects

S,,Return state

L,,Return list of application log numbers

K,,Cancel the currently running batch jobs

Conversion objects assigned to the specified mass transfer are deleted.

In Table DMC_MT_TABLES, flag "DEFINED" is set to false for these conversion objects.

The generated runtime objects for the conversion objects (function modules and function groups) are deleted in sender, receiver and DTL system.

Input parameters

• IM_MODE
  Controls if the conversion objects should be deleted, or if status or log information is requested, or if the running jobs should be canceled Required

• IM_APPLIC
  MWB application Optional (default SLO)

• IM_MT_ID
  Mass transfer ID Required if called in execution mode

• IM_NO_OF_JOBS
  Number of batch jobs to be created Optional (default 1)

• IM_RESET_ALL
  states if all conversion objects of the specified mass transfer shall be deleted. Optional

• IT_TABLES
  Ranges-Table to specify those conversion objects that should be deleted. Required if called in execution mode, and if parameter IM_RESET_ALL is not set to true.

• IM_PACKID
  PCL package ID Required in execution mode

• IM_SESSION_ID
  PCL session ID Required

• IM_RESTART
  If set to true, this parameter indicates that for a reset of conversion objects, 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 IM_NO_OF_JOBS and the number of already running or scheduled jobs will be scheduled.

• I_TADIR
  If set to true, the necessary TADIR entries for the conversion objects and their sub-objects are not created by the corresponding function modules of the correction and transport system (CTS), but (to improve the performance) directly in the API. So this parameter deactivates the standard CTS handling when the conversion objects are deleted. In this case, the TADIR entries are kept.

Return parameters:

• EX_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 number

• EX_STATISTICS
  Total number of objects, and number of failed / successfully processed objects, and currently processed objects

• ET_STATUS
  Filled if API is called in "get status" mode: Tables containing status information both for the scheduling and for each of the scheduled batch jobs. This information includes a status (running, finished with errors / warnings; success), time stamps for start and end, batch job number, server etc

Error situations that are handled ff called in exection mode. In all these situation, processing is cancelled, and no batch jobs are scheduled::

• Application does not exist

• mass transfer does not exist

• API called with invalid combination of input parameters: if IM_RESET_ALL is set to true, table IT_TABLES must be initial; if IM_RESET_ALL is set to false, table IT_TABLES must NOT be initial

Example

Notes

When the conversion objects along with their runtime objects are deleted, in the affected systems, either there must be sufficient space available for REDO logs which might become quite large. Or, prior to the invocation of this function, an offline backup is done and then the redo-logs are switched off. After completion of this function, another offline backup should be made. Then, the redo-logs would be switched on again.

As a first step, the API resets all "in process" and "failed" entries in DMC_MT_TABLES to FALSE. Therefore, it must not be called if another conversion object creation or deletion, data load, access plan calculation or runtime object generation is currently running. Otherwise, the "in process" information for an object which is being processed would be reset, and possibly two jobs would process the same object in parallel. The only exception is that these APIs can be called in "restart" mode. Then, the "in process" entries in DMC_MT_TABLES are NOT reset.

Further information

Refer also to the documentation of report DMCDTL_MT_CONVOBJECTS_RESET for which this API schedules batch jobs.

Parameters

ET_LOGNUMBERS
ET_STATUS
EX_LOGNUMBER
EX_STATISTICS
IM_APPLIC
IM_MODE
IM_MT_ID
IM_NO_OF_JOBS
IM_PACKID
IM_RESET_ALL
IM_RESTART
IM_SESSION_ID
IT_TABLES

Exceptions

Function Group

DMC_DTL

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

Length: 5625 Date: 20240523 Time: 113734     sap01-206 ( 102 ms )