Show TOC

Function documentationImplementing Custom-Specific Checks

 

By implementing the BAdI definition /TMWFLOW/TRANS_DEFINED_CHECK, you can implement your own check logics and integrate them into the transport-related checks framework. Before each transport operation, for example, a release transport request is triggered (by the WebClient UI or the Administration Cockpit), the respective BAdI implementation method is called to perform the check. Based on combined check results (also from other checks), the system will decide whether the end user can continue the action.

  • Check before save

    By implementing the method CHECK_BEFORE_SAVE_TRANS_REQ, you can perform your own specific check before you try to save objects on a transport request in the managed system.

    Prerequisites:

    You have enabled this check by setting the Cross-System Object Lock switch to active in the managed development system.

    Descriptions of the importing method parameters:

    • IV_TRANSPORT_REQUEST: The ID of the transport request to which the objects are being saved

    • IV_SRC_SYS_TMS_SID: TMS short SID of the managed system

    • IV_SRC_SYS_TMS_DOMAIN: TMS domain of the managed system

    • IT_LOCKS_4_OBJECT: CTS locks for the objects to be saved

    • IT_LOCKS_4_TABLE_KEY: CTS locks for the table keys to be saved

    Descriptions of the exporting method parameters:

    • ET_CHECK_RESULT: Check results

    • ET_ERROR_MESSAGE: Error messages for runtime exceptions

  • Check before release

    By implementing the method CHECK_BEFORE_IMPORT, you can perform your own specific check before transport requests are imported into the target systems.

    Descriptions of the importing method parameters:

    • IT_TRANS_REQUESTS_TO_SYS: The internal table of mapping between target systems and transport requests to be imported

    • IV_TASKLIST_ID: The ID of the task list from which the import is to be triggered

    • IV_CYCLE_GUID: The GUID of the relevant cycle

    • IV_CHANGE_GUID: The GUID of the relevant change document

    • IV_IMMEDIATE: Whether the operation is triggered immediately (ABAP_TRUE) or scheduled at a later time (ABAP_FALSE)

    Descriptions of the exporting method parameters:

    • ET_CHECK_RESULT: Check results

    • ET_ERROR_MESSAGE: Error messages for runtime exceptions

  • Check before decouple

    By implementing the method CHECK_BEFORE_DECOUPLE, you can perform your own specific check before transport requests are decoupled.

    Descriptions of the importing method parameters:

    • IT_TRANSPORT_REQUEST: The IDs of the transport requests to be decoupled

    • IV_TASKLIST_ID: The ID of the task list where the decouple is to be triggered

    • IV_CYCLE_GUID: The GUID of the relevant cycle

    • IV_CHANGE_GUID: The GUID of the relevant change document

    Descriptions of the exporting method parameters:

    • ET_CHECK_RESULT: Check results

    • ET_ERROR_MESSAGE: Error messages for runtime exceptions

  • Check before assign

    By implementing the method CHECK_BEFORE_ASSIGN, you can perform your own specific check before transport requests are assigned.

    Descriptions of the importing method parameters:

    • IT_TRANSPORT_REQUEST: The IDs of the transport requests to be assigned

    • IV_TARGET_TASKLIST_ID: The ID of the task list where the assign is to be triggered

    • IV_TARGET_CYCLE_GUID: The GUID of the relevant cycle

    • IV_TARGET_CHANGE_GUID: The GUID of the relevant change document

    Descriptions of the exporting method parameters:

    • ET_CHECK_RESULT: Check results

    • ET_ERROR_MESSAGE: Error messages for runtime exceptions

  • Check before reassign change

    By implementing the method CHECK_BEFORE_REASSIGN_CHNG, you can perform your own specific check before a request for change or a change document is reassigned.

    Descriptions of the importing method parameters:

    • IV_CHANGE_GUID: The GUID of the request for change or the change document to be reassigned

    • IV_SOURCE_CYCLE_GUID: The GUID of the source cycle

    • IV_TARGET_CYCLE_GUID: The GUID of the target cycle

    Descriptions of the exporting method parameters:

    • ET_CHECK_RESULT: Check results

    • ET_ERROR_MESSAGE: Error messages for runtime exceptions

    The exporting parameter ET_CHECK_RESULT contains the check results shown in the Transport-Related Checks popup window and assignment block. For the result entry, the RESULT_STATUS field is important as it determines whether the transport operation, for example release transport requests, can continue or not. As long as there is one entry whose RESULT_STATUS is filled with the value STOP, the transport operation will be stopped.

More Information

Automatic and Manual Check

Transport-Related Checks