SAP CNV_MBT_START_COPY Function Module for Start function for CMIS and TDMS copy

Search SAP Function Modules

CNV_MBT_START_COPY is a standard cnv mbt start 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 Start function for CMIS and TDMS copy 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 start copy FM, simply by entering the name CNV_MBT_START_COPY into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNV_MBT_COPY_CONTROL
Program Name: SAPLCNV_MBT_COPY_CONTROL
Main Program: SAPLCNV_MBT_COPY_CONTROL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_MBT_START_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_START_COPY'"Start function for CMIS and TDMS copy
  EXPORTING
   I_NEW_PACKID =  "Package Number to Specify CMIS and TDMS Packages
   I_ORIG_PACKID =  "Package Number to Specify CMIS and TDMS Packages
*  I_DO_INIT = 'X' "Initialize all work areas and buffers
*  I_LOG_ON = ' ' "Write log entries into existing log
*  I_TEST_RUN = 'X' "Test run - no log / messages / no DB changes

 IMPORTING
   E_DONE =  "Copy successfully done
   E_COPY_VAR =  "Variants in TDMS and CMIS copy functionality

EXCEPTIONS
   INVALID_CALL = 1    INCONSISTENT_COPY_VAR = 10    NO_TARGET_PROCTYPE_FOUND = 11    DELETION_ERROR = 12    TREE_CHANGE_ERROR = 13    INVALID_PACKID = 2    INVALID_PROC_TYPE = 3    INVALID_SCENARIO = 4    INVALID_SUBPROJECT = 5    NO_PROCTYPE_FOUND = 6    NO_PROCTRANS_FOUND = 7    CANCELED_BY_USER = 8    COPY_VAR_NO_DATA = 9 

.

IMPORTING Parameters details for CNV_MBT_START_COPY

I_NEW_PACKID - Package Number to Specify CMIS and TDMS Packages

Data type: CNV_MBT_PACKID
Optional: No
Call by Reference: No ( called with pass by value option)

I_ORIG_PACKID - Package Number to Specify CMIS and TDMS Packages

Data type: CNV_MBT_PACKID
Optional: No
Call by Reference: No ( called with pass by value option)

I_DO_INIT - Initialize all work areas and buffers

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LOG_ON - Write log entries into existing log

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TEST_RUN - Test run - no log / messages / no DB changes

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CNV_MBT_START_COPY

E_DONE - Copy successfully done

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

E_COPY_VAR - Variants in TDMS and CMIS copy functionality

Data type: CNV_MBT_COPY_VARIANT
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INVALID_CALL - Missing value for parameter

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_COPY_VAR - Inconsistency found in Copy Variant

Data type:
Optional: No
Call by Reference: Yes

NO_TARGET_PROCTYPE_FOUND - No target process type found

Data type:
Optional: No
Call by Reference: Yes

DELETION_ERROR - Relayed error from CNV_MBT_PCL_DEL_CUST_ENTRIES

Data type:
Optional: No
Call by Reference: Yes

TREE_CHANGE_ERROR - Error occured during IMG tree change

Data type:
Optional: No
Call by Reference: Yes

INVALID_PACKID - Package ID does not exist

Data type:
Optional: No
Call by Reference: Yes

INVALID_PROC_TYPE - PROC_TYPE for package is not valid

Data type:
Optional: No
Call by Reference: Yes

INVALID_SCENARIO - Invalid scenario found in package

Data type:
Optional: No
Call by Reference: Yes

INVALID_SUBPROJECT - Subproject does not exist

Data type:
Optional: No
Call by Reference: Yes

NO_PROCTYPE_FOUND - No PROC_TYPE found for package

Data type:
Optional: No
Call by Reference: Yes

NO_PROCTRANS_FOUND - No valid transfer rules found

Data type:
Optional: No
Call by Reference: Yes

CANCELED_BY_USER - Value selection was canceled by user

Data type:
Optional: No
Call by Reference: Yes

COPY_VAR_NO_DATA - No data found for copy variant

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_MBT_START_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.

ABAP code using 7.40 inline data declarations to call FM CNV_MBT_START_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.

Search for further information about these or an SAP related objects