Ansicht
Dokumentation

CNV_MBT_ACTION_LOG - For additional required functionality

BAL_S_LOG - Application Log: Log header data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Functionality

Checks the state of the Product Lock. If the state is active then the SAP LT engines will be checked wheather they are open or closed. By default the Product Lock is not active and the SAP LT engines are closed. When the SAP Product Lock is active and the SAP LT engine 2 (LT organizational change) is closed then it is not possible to load/create a package that is assigned to this engine. The state of the SAP Product Lock will be returned in the export parameter EP_PLK_STATE ( 1 = active; _ = not active).

The function module checks the existence of PCL and CWB packages (loaded and basis packages) as well as Analysis IDs.

The function module can be called with creating an action log (import parameter IP_NO_ACTON_LOG is initial) or without (IP_NO_ACTION_LOG = 'X') for checking reasons.

Product Lock state check

If the Prdduct Lock state is inactive the function module returns with the exception plk_not_active.

SAP LT engines state check

Based on the values in the import parameter the used engines will be determined. For these engines the state will be check. If the state is closed then no use is allowed and the function module returns with the exception engine_closed.

Action Log create

If all checks were successful then an action log will be written if the import parameter IP_NO_ACTION_LOG is initial. For tests the parameter can be set to X and then no action log will be written.

CWB packages

To call the fumo for checking the state of the SAP LT engines then you have to fill in the basis package number into import paramter IP_PACKID, the value 'X' into parameter IP_CWB_PACKAGE and parameter IP_NO_ACTION_LOG with 'X'. The execution checks the existence of the package and the assignment to an engine. If the package exist and it is assigned to engine that is closed then the exception ENGINE_CLOSED will be thrown.

To call the fumo for creating the action log you have to enter the package number of the loaded package into field IP_PACKID, the value 'X' into parameter IP_CWB_PACKAGE, an short description for the action (CREATED, LOCKED,...) and leave the other parameters initial.

The name in import parameter should identify the kind of action that is performed with the object (package, analysis). If this field contains no value the default value 'Create' is taken for the action.

PCL packages

It is similar to the fumo call for CWB packages. The only difference is that the import parameter IP_CWB_PACKAGE remains blank.

Analysis ID

It is similar to the fumo call for CWB packages. The only difference is that the import parameter IP_CWB_PACKAGE remains blank.

Example

Notes

Further information

Parameters

EP_ACTION_ID
EP_PLK_STATE
IP_ACTION
IP_ANALYSE_ID
IP_CWB_PACKAGE
IP_DESTINATION_ID
IP_NO_ACTION_LOG
IP_PACKID

Exceptions

ANALYSE_ID_NOT_EXIST
CREATE_ACTION_LOG_FAILED
ENGINE_CLOSED
FUMO_NOT_EXIST
GET_RFC_DESTINATION_FAILED
NO_ENGINE_STATE
NO_PLK_STATE
PACKID_NOT_EXIST
READ_DEPENDENT_PACK_FAILED

Function Group

CNV_MBT_ACTION_LOG

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

Length: 3630 Date: 20240523 Time: 102029     sap01-206 ( 76 ms )