SAP CNV_MBT_REORG_CHECK_CONDITIONS Function Module for Check conditions for deleting a reorg object
CNV_MBT_REORG_CHECK_CONDITIONS is a standard cnv mbt reorg check conditions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check conditions for deleting a reorg object processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for cnv mbt reorg check conditions FM, simply by entering the name CNV_MBT_REORG_CHECK_CONDITIONS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_MBT_REORG
Program Name: SAPLCNV_MBT_REORG
Main Program: SAPLCNV_MBT_REORG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CNV_MBT_REORG_CHECK_CONDITIONS pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CNV_MBT_REORG_CHECK_CONDITIONS'"Check conditions for deleting a reorg object.
EXPORTING
IP_REF_TYPE = "Deletion types
IP_REF_NAME = "Name of the object
IMPORTING
EP_FULFILLED = "'X' = condition fulfilled
EXCEPTIONS
NO_DELREF_ENTRY = 1 NOT_ALL_PACK_DELETED = 10 NOT_ALL_SUBPROJECTS_DELETED = 11 DELETION_SUBPROJECT_ACTIVE = 12 EXCLUDED_FROM_REORG = 13 STILL_RUNNING = 2 STATUS_IS_ERROR = 3 STATUS_IS_ABORTED = 4 STATUS_IS_FINISHED = 5 UNKNOWN_STATUS = 6 PACKAGE_DOES_NOT_EXIST = 7 ALREADY_DELETED = 8 PACKAGE_ACTIVE = 9
IMPORTING Parameters details for CNV_MBT_REORG_CHECK_CONDITIONS
IP_REF_TYPE - Deletion types
Data type: CNV_MBT_DEL_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IP_REF_NAME - Name of the object
Data type: CNV_MBT_OBJECT_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_MBT_REORG_CHECK_CONDITIONS
EP_FULFILLED - 'X' = condition fulfilled
Data type: CNV_MBT_CHAROptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_DELREF_ENTRY - The deletion object does not exist in the reorg table cnvmbtdelref.
Data type:Optional: No
Call by Reference: Yes
NOT_ALL_PACK_DELETED - Not all packages of the subproject are deleted.
Data type:Optional: No
Call by Reference: Yes
NOT_ALL_SUBPROJECTS_DELETED - Not all subprojects of the project are deleted.
Data type:Optional: No
Call by Reference: Yes
DELETION_SUBPROJECT_ACTIVE - Deletion of the subproject is still active in a batch job
Data type:Optional: No
Call by Reference: Yes
EXCLUDED_FROM_REORG - Package is excluded from reorg/deletion
Data type:Optional: No
Call by Reference: Yes
STILL_RUNNING - The status of the object is deletion is still running.
Data type:Optional: No
Call by Reference: Yes
STATUS_IS_ERROR - Status of the object is error.
Data type:Optional: No
Call by Reference: Yes
STATUS_IS_ABORTED - Status of the object is aborted.
Data type:Optional: No
Call by Reference: Yes
STATUS_IS_FINISHED - Status of the object is finished.
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_STATUS - Status of the object is not defined.
Data type:Optional: No
Call by Reference: Yes
PACKAGE_DOES_NOT_EXIST - The package does not exist.
Data type:Optional: No
Call by Reference: Yes
ALREADY_DELETED - The object was already deleted.
Data type:Optional: No
Call by Reference: Yes
PACKAGE_ACTIVE - The package is still active.
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_REORG_CHECK_CONDITIONS Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_ip_ref_type | TYPE CNV_MBT_DEL_TYPE, " | |||
lv_ep_fulfilled | TYPE CNV_MBT_CHAR, " | |||
lv_no_delref_entry | TYPE CNV_MBT_CHAR, " | |||
lv_not_all_pack_deleted | TYPE CNV_MBT_CHAR, " | |||
lv_not_all_subprojects_deleted | TYPE CNV_MBT_CHAR, " | |||
lv_deletion_subproject_active | TYPE CNV_MBT_CHAR, " | |||
lv_excluded_from_reorg | TYPE CNV_MBT_CHAR, " | |||
lv_ip_ref_name | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_still_running | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_status_is_error | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_status_is_aborted | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_status_is_finished | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_unknown_status | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_package_does_not_exist | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_already_deleted | TYPE CNV_MBT_OBJECT_NAME, " | |||
lv_package_active | TYPE CNV_MBT_OBJECT_NAME. " |
  CALL FUNCTION 'CNV_MBT_REORG_CHECK_CONDITIONS' "Check conditions for deleting a reorg object |
EXPORTING | ||
IP_REF_TYPE | = lv_ip_ref_type | |
IP_REF_NAME | = lv_ip_ref_name | |
IMPORTING | ||
EP_FULFILLED | = lv_ep_fulfilled | |
EXCEPTIONS | ||
NO_DELREF_ENTRY = 1 | ||
NOT_ALL_PACK_DELETED = 10 | ||
NOT_ALL_SUBPROJECTS_DELETED = 11 | ||
DELETION_SUBPROJECT_ACTIVE = 12 | ||
EXCLUDED_FROM_REORG = 13 | ||
STILL_RUNNING = 2 | ||
STATUS_IS_ERROR = 3 | ||
STATUS_IS_ABORTED = 4 | ||
STATUS_IS_FINISHED = 5 | ||
UNKNOWN_STATUS = 6 | ||
PACKAGE_DOES_NOT_EXIST = 7 | ||
ALREADY_DELETED = 8 | ||
PACKAGE_ACTIVE = 9 | ||
. " CNV_MBT_REORG_CHECK_CONDITIONS |
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_REORG_CHECK_CONDITIONS
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects