SAP CNV_MBT_INCL_COPY Function Module for MBT PCL Copy include - remote or local
CNV_MBT_INCL_COPY is a standard cnv mbt incl copy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MBT PCL Copy include - remote or local 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 incl copy FM, simply by entering the name CNV_MBT_INCL_COPY into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_MBT_INCL
Program Name: SAPLCNV_MBT_INCL
Main Program: SAPLCNV_MBT_INCL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_MBT_INCL_COPY 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_INCL_COPY'"MBT PCL Copy include - remote or local.
EXPORTING
IM_PACKID = "Package Number to Specify CMIS and TDMS Packages
* IM_INCLUDE_NAME = "MBT PCL: Name of new include
IM_COPY_INCLUDE = "MBT PCL: Name of Include to copy
* IM_UPD_CNVMBTINCL = 'X' "Update information in CNVMBTINCL
* IM_CREATE_REMOTE = ' ' "Create new Include in remote system
* IM_COPY_REMOTE = ' ' "Copy Include in remote system
* IM_EXEC_TARGET = "Specifies The Target System the Activity is Executed in
IMPORTING
EX_INCLUDE_NAME = "name of created include
EXCEPTIONS
NO_AUTHORITY = 1 ERROR_WHILE_UPDATE_CNVMBTRULES = 10 ERROR_WHILE_UPDATE_CNVMBTINCL = 11 INVALID_PACKAGE = 2 INVALID_SUBPROJECT = 3 INCLUDE_IN_WRONG_NAMESPACE = 4 INVALID_COPY_INCLUDE = 5 INVALID_EXECUTION_TARGET = 6 FOREIGN_LOCK_ON_SUBPROJECT = 7 ERROR_WHILE_UPDATE_OF_EXTID = 8 ERROR_WHILE_CREATING_NEW_INCL = 9
IMPORTING Parameters details for CNV_MBT_INCL_COPY
IM_PACKID - Package Number to Specify CMIS and TDMS Packages
Data type: CNVMBTPACK-PACKIDOptional: No
Call by Reference: Yes
IM_INCLUDE_NAME - MBT PCL: Name of new include
Data type: CNVMBTINCL-INCLUDE_NAMEOptional: Yes
Call by Reference: Yes
IM_COPY_INCLUDE - MBT PCL: Name of Include to copy
Data type: CNVMBTINCL-INCLUDE_NAMEOptional: No
Call by Reference: Yes
IM_UPD_CNVMBTINCL - Update information in CNVMBTINCL
Data type:Default: 'X'
Optional: Yes
Call by Reference: Yes
IM_CREATE_REMOTE - Create new Include in remote system
Data type:Default: ' '
Optional: Yes
Call by Reference: Yes
IM_COPY_REMOTE - Copy Include in remote system
Data type:Default: ' '
Optional: Yes
Call by Reference: Yes
IM_EXEC_TARGET - Specifies The Target System the Activity is Executed in
Data type: CNVMBTDEST-EXEC_TARGETOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CNV_MBT_INCL_COPY
EX_INCLUDE_NAME - name of created include
Data type: CNVMBTINCL-INCLUDE_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: Yes
ERROR_WHILE_UPDATE_CNVMBTRULES -
Data type:Optional: No
Call by Reference: Yes
ERROR_WHILE_UPDATE_CNVMBTINCL -
Data type:Optional: No
Call by Reference: Yes
INVALID_PACKAGE -
Data type:Optional: No
Call by Reference: Yes
INVALID_SUBPROJECT -
Data type:Optional: No
Call by Reference: Yes
INCLUDE_IN_WRONG_NAMESPACE -
Data type:Optional: No
Call by Reference: Yes
INVALID_COPY_INCLUDE -
Data type:Optional: No
Call by Reference: Yes
INVALID_EXECUTION_TARGET -
Data type:Optional: No
Call by Reference: Yes
FOREIGN_LOCK_ON_SUBPROJECT -
Data type:Optional: No
Call by Reference: Yes
ERROR_WHILE_UPDATE_OF_EXTID -
Data type:Optional: No
Call by Reference: Yes
ERROR_WHILE_CREATING_NEW_INCL -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_INCL_COPY 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_im_packid | TYPE CNVMBTPACK-PACKID, " | |||
| lv_no_authority | TYPE CNVMBTPACK, " | |||
| lv_ex_include_name | TYPE CNVMBTINCL-INCLUDE_NAME, " | |||
| lv_error_while_update_cnvmbtrules | TYPE CNVMBTINCL, " | |||
| lv_error_while_update_cnvmbtincl | TYPE CNVMBTINCL, " | |||
| lv_im_include_name | TYPE CNVMBTINCL-INCLUDE_NAME, " | |||
| lv_invalid_package | TYPE CNVMBTINCL, " | |||
| lv_im_copy_include | TYPE CNVMBTINCL-INCLUDE_NAME, " | |||
| lv_invalid_subproject | TYPE CNVMBTINCL, " | |||
| lv_im_upd_cnvmbtincl | TYPE CNVMBTINCL, " 'X' | |||
| lv_include_in_wrong_namespace | TYPE CNVMBTINCL, " | |||
| lv_im_create_remote | TYPE CNVMBTINCL, " ' ' | |||
| lv_invalid_copy_include | TYPE CNVMBTINCL, " | |||
| lv_im_copy_remote | TYPE CNVMBTINCL, " ' ' | |||
| lv_invalid_execution_target | TYPE CNVMBTINCL, " | |||
| lv_im_exec_target | TYPE CNVMBTDEST-EXEC_TARGET, " | |||
| lv_foreign_lock_on_subproject | TYPE CNVMBTDEST, " | |||
| lv_error_while_update_of_extid | TYPE CNVMBTDEST, " | |||
| lv_error_while_creating_new_incl | TYPE CNVMBTDEST. " |
|   CALL FUNCTION 'CNV_MBT_INCL_COPY' "MBT PCL Copy include - remote or local |
| EXPORTING | ||
| IM_PACKID | = lv_im_packid | |
| IM_INCLUDE_NAME | = lv_im_include_name | |
| IM_COPY_INCLUDE | = lv_im_copy_include | |
| IM_UPD_CNVMBTINCL | = lv_im_upd_cnvmbtincl | |
| IM_CREATE_REMOTE | = lv_im_create_remote | |
| IM_COPY_REMOTE | = lv_im_copy_remote | |
| IM_EXEC_TARGET | = lv_im_exec_target | |
| IMPORTING | ||
| EX_INCLUDE_NAME | = lv_ex_include_name | |
| EXCEPTIONS | ||
| NO_AUTHORITY = 1 | ||
| ERROR_WHILE_UPDATE_CNVMBTRULES = 10 | ||
| ERROR_WHILE_UPDATE_CNVMBTINCL = 11 | ||
| INVALID_PACKAGE = 2 | ||
| INVALID_SUBPROJECT = 3 | ||
| INCLUDE_IN_WRONG_NAMESPACE = 4 | ||
| INVALID_COPY_INCLUDE = 5 | ||
| INVALID_EXECUTION_TARGET = 6 | ||
| FOREIGN_LOCK_ON_SUBPROJECT = 7 | ||
| ERROR_WHILE_UPDATE_OF_EXTID = 8 | ||
| ERROR_WHILE_CREATING_NEW_INCL = 9 | ||
| . " CNV_MBT_INCL_COPY | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_INCL_COPY
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.| "SELECT single PACKID FROM CNVMBTPACK INTO @DATA(ld_im_packid). | ||||
| "SELECT single INCLUDE_NAME FROM CNVMBTINCL INTO @DATA(ld_ex_include_name). | ||||
| "SELECT single INCLUDE_NAME FROM CNVMBTINCL INTO @DATA(ld_im_include_name). | ||||
| "SELECT single INCLUDE_NAME FROM CNVMBTINCL INTO @DATA(ld_im_copy_include). | ||||
| DATA(ld_im_upd_cnvmbtincl) | = 'X'. | |||
| DATA(ld_im_create_remote) | = ' '. | |||
| DATA(ld_im_copy_remote) | = ' '. | |||
| "SELECT single EXEC_TARGET FROM CNVMBTDEST INTO @DATA(ld_im_exec_target). | ||||
Search for further information about these or an SAP related objects