Ansicht
Dokumentation

DTL_MT_STATUS_SET - (re)set status of mass transfer conv. obj. to a specific phase

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

Functionality

Purpose

To the conversion objects in the DTL, status information is assigned that indicates if the conversion object has been created, the selection parameter is determined ("DB Analysis"), its runtime objects generated, the access plan(s) calculated and / or the data loaded. For some of the processing steps, this status information usually prevents a reprocessing. For example, if the runtime objects are generated and the respective flag is set, it is usually not possible to generate the runtime objects again. The same is true for the access plan calculation and the data load. In case of the data load, the "loaded" flag is set even if the data load was only performed in test mode. For the access plan calculation, by contrast, it can be specified that already calculated access plans should be recalculated.

It should be possible (either for all conversion objects of a mass transfer, or for a list of conversion objects) to reset status information. This function is provided by this API. It resets status flags according to a so-called scenario. So when the API is called, one of the possible scenarios must be specified:

P - reset "loaded" flag and "calculated" flag only in DMC_MT_TABLES in case of the "small package copy". The problem here is that a new access plan has been calculated for the new package, but the "loaded" and "calculated" flags of the mass transfer are still set. They need to be reset only in DMC_MT_TABLES, not in the access plan header and runtime info tables, because a new access plan is used.

C - access plans have been calculated. That means, if the data load has already been performed, the respective flag is reset not only in the administration table DMC_MT_TABLES but also on the access plan headers and in the runtime info records. For objects with status "failed", the "calculated" flag is reset as well.

G - conversion objects have been generated. That means, the flags for data load and for calculation are reset. For objects with status "failed", the "generated" flag is reset as well.

A - DB Analysis is completed. In this case, the flags for data load, access plan calculation as well as runtime object generation are reset to false. For objects with status "failed", the selection parameter field is cleared as well.

D - conversion objects have been defined. In this case, the flags for data load, access plan calculation as well as runtime object generation are reset to false. The selection parameter field in DMC_MT_TABLES is cleared. For objects with status "failed", the "defined" flag is reset as well.

Note that it is not possible by means of this API to reset the "defined" flag. It is not sufficient only to reset this flag, but the conversion object itself would need to be deleted before it can be created anew. An update of an existing conversion object is not possible. If conversion objects need to be deleted, API DTL_MT_CONVOBJS_RESET can be used.

In general, this API is called in synchronous mode. However, if it is necessary to reset LOADED flags of conversion objects, a job is scheduled to perform this task.

Input parameters

Parameter name	Type		Description		Required / Optional
I_MT_ID	DMC_MT_IDENTIFIER	Mass transfer identifier		R
I_SCENARIO	CHAR1		Scenario for status change	R
I_PACKID	CNV_MBT_PACKID	PCL Package Id		R
I_SESSION_ID	CNV_MBT_SESSION_ID	PCL Session ID		R
I_ACC_PREC_ID	DMC_ID		Access Plan ID		O
IT_TABLES	DMC_RANGES_TABNAME	If specified, the processing is restricted to the conversion		objects included in this table

Export parameters

E_LOGNUMBER
Application log number of the application log the API created

E_STATUS
Structure containing status information such as a status (running, finished with errors / warnings; success), time stamps for start and end, etc.

For all the conversion objects of the mass transfer, the status fields of the DMC_MT_TABLES entries are changed according to the scenario which is specified in input parameter IM_SCENARIO. The changes are described in the following table. The first value is set if none of the fields "in process" and "failed" are true for the specific table entry; the second value is set if at least one of these fields are true. ' - ' means that no change to the field is performed.

Overview of changes done in each of the scenarios:

D - Conversion objects are reset to status "DEFINED"
The generated, calculated and loaded flags are reset to false. The selection parameter and the PREC_USED indicator field are initialized

A - Conversion objects are reset to status "DB ANALYSIS DONE"
The generated, calculated and loaded flags are reset to false. The PREC_USED indicator is initialized.

G - Conversion objects are reset to status "GENERATED"
The calculated and loaded flags are reset to false. The PREC_USED indicator is initialized.

C - Conversion objects are reset to status "CALCULATED"
The loaded flags are reset to false.

P - Refresh Package
The PREC_USED indicator is initialized, and the Loaded and calculated flags are reset to false, but only in table DMC_MT_TABLES. In all other scenarios, the loaded flags are also reset to false on access plan level.

Example

Notes

Further information

Parameters

E_LOGNUMBER
E_STATUS
IT_TABLES
I_ACC_PREC_ID
I_MT_ID
I_PACKID
I_SCENARIO
I_SESSION_ID

Exceptions

Function Group

DMC_DTL

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

Length: 7242 Date: 20240523 Time: 120735     sap01-206 ( 127 ms )