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

Function CNV_MBT_CONTROL_TABLES_WRITE 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_CONTROL_TABLES_WRITE'"Get PCL control tables, remote call.
EXPORTING
PACKID = "Package Number to Specify CMIS and TDMS Packages
MODE = "flag
TABLES
* I_CNVMBTCOBJ = "conversion objects
* I_CNVMBTCONFLICTS = "Conflicts between sender and receiver system
* I_CNVMBTDOMCONFL = "Conflicts between sender and receiver system
* I_CNVMBTTREE = "Structure of conversion object / hierachy
* I_CNVMBTFORKEY = "Foreign key releations in structure + fixed values
* I_CNVMBTTABSTRUC = "Field list of tables for file transfer
* I_CNVCMIS_TAB_POST = "Postponed conflicts between sender and receiver system
* I_CNVCMIS_MAPPING = "Table for storing information about the mapping
* I_CNVMBTSELREF = "MBT PCL Selection group reference
* I_CNVMBTTABLES = "explicite list of tables to be handled during migration
* I_CNVMBTFIELDS = "explicite conversion rules for fields during migration
* I_CNVMBTFIPARS = "parameters for rules mentioned in cnvmbtfields
* I_CNVMBTDOMS = "domains / data elements with correspnding conversion rules
* I_CNVMBTRULES = "conversion rules
* I_CNVMBTRULEPARS = "conversion rules parameter structure and types
* I_CNVMBTINCL = "MBT PCL: Includes to be integrated in Conversion Objects
* I_CNVMBTRENAME = "Renaming 1:1
EXCEPTIONS
INSERT_DUPLICATE_KEY = 1
IMPORTING Parameters details for CNV_MBT_CONTROL_TABLES_WRITE
PACKID - Package Number to Specify CMIS and TDMS Packages
Data type: CNVMBTPACK-PACKIDOptional: No
Call by Reference: No ( called with pass by value option)
MODE - flag
Data type: CNVMBTRETSTR-AND_RETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNV_MBT_CONTROL_TABLES_WRITE
I_CNVMBTCOBJ - conversion objects
Data type: CNVMBTCOBJOptional: Yes
Call by Reference: Yes
I_CNVMBTCONFLICTS - Conflicts between sender and receiver system
Data type: CNVMBTCONFLICTSOptional: Yes
Call by Reference: Yes
I_CNVMBTDOMCONFL - Conflicts between sender and receiver system
Data type: CNVMBTDOMCONFLOptional: Yes
Call by Reference: Yes
I_CNVMBTTREE - Structure of conversion object / hierachy
Data type: CNVMBTTREEOptional: Yes
Call by Reference: Yes
I_CNVMBTFORKEY - Foreign key releations in structure + fixed values
Data type: CNVMBTFORKEYOptional: Yes
Call by Reference: Yes
I_CNVMBTTABSTRUC - Field list of tables for file transfer
Data type: CNVMBTTABSTRUCOptional: Yes
Call by Reference: Yes
I_CNVCMIS_TAB_POST - Postponed conflicts between sender and receiver system
Data type: CNVCMIS_TAB_POSTOptional: Yes
Call by Reference: Yes
I_CNVCMIS_MAPPING - Table for storing information about the mapping
Data type: CNVCMIS_MAPPINGOptional: Yes
Call by Reference: Yes
I_CNVMBTSELREF - MBT PCL Selection group reference
Data type: CNVMBTSELREFOptional: Yes
Call by Reference: Yes
I_CNVMBTTABLES - explicite list of tables to be handled during migration
Data type: CNVMBTTABLESOptional: Yes
Call by Reference: Yes
I_CNVMBTFIELDS - explicite conversion rules for fields during migration
Data type: CNVMBTFIELDSOptional: Yes
Call by Reference: Yes
I_CNVMBTFIPARS - parameters for rules mentioned in cnvmbtfields
Data type: CNVMBTFIPARSOptional: Yes
Call by Reference: Yes
I_CNVMBTDOMS - domains / data elements with correspnding conversion rules
Data type: CNVMBTDOMSOptional: Yes
Call by Reference: Yes
I_CNVMBTRULES - conversion rules
Data type: CNVMBTRULESOptional: Yes
Call by Reference: Yes
I_CNVMBTRULEPARS - conversion rules parameter structure and types
Data type: CNVMBTRULEPARSOptional: Yes
Call by Reference: Yes
I_CNVMBTINCL - MBT PCL: Includes to be integrated in Conversion Objects
Data type: CNVMBTINCLOptional: Yes
Call by Reference: Yes
I_CNVMBTRENAME - Renaming 1:1
Data type: CNVMBTRENAMEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INSERT_DUPLICATE_KEY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_CONTROL_TABLES_WRITE 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_packid | TYPE CNVMBTPACK-PACKID, " | |||
| lt_i_cnvmbtcobj | TYPE STANDARD TABLE OF CNVMBTCOBJ, " | |||
| lv_insert_duplicate_key | TYPE CNVMBTCOBJ, " | |||
| lt_i_cnvmbtconflicts | TYPE STANDARD TABLE OF CNVMBTCONFLICTS, " | |||
| lt_i_cnvmbtdomconfl | TYPE STANDARD TABLE OF CNVMBTDOMCONFL, " | |||
| lt_i_cnvmbttree | TYPE STANDARD TABLE OF CNVMBTTREE, " | |||
| lt_i_cnvmbtforkey | TYPE STANDARD TABLE OF CNVMBTFORKEY, " | |||
| lt_i_cnvmbttabstruc | TYPE STANDARD TABLE OF CNVMBTTABSTRUC, " | |||
| lt_i_cnvcmis_tab_post | TYPE STANDARD TABLE OF CNVCMIS_TAB_POST, " | |||
| lt_i_cnvcmis_mapping | TYPE STANDARD TABLE OF CNVCMIS_MAPPING, " | |||
| lt_i_cnvmbtselref | TYPE STANDARD TABLE OF CNVMBTSELREF, " | |||
| lv_mode | TYPE CNVMBTRETSTR-AND_RETURN, " | |||
| lt_i_cnvmbttables | TYPE STANDARD TABLE OF CNVMBTTABLES, " | |||
| lt_i_cnvmbtfields | TYPE STANDARD TABLE OF CNVMBTFIELDS, " | |||
| lt_i_cnvmbtfipars | TYPE STANDARD TABLE OF CNVMBTFIPARS, " | |||
| lt_i_cnvmbtdoms | TYPE STANDARD TABLE OF CNVMBTDOMS, " | |||
| lt_i_cnvmbtrules | TYPE STANDARD TABLE OF CNVMBTRULES, " | |||
| lt_i_cnvmbtrulepars | TYPE STANDARD TABLE OF CNVMBTRULEPARS, " | |||
| lt_i_cnvmbtincl | TYPE STANDARD TABLE OF CNVMBTINCL, " | |||
| lt_i_cnvmbtrename | TYPE STANDARD TABLE OF CNVMBTRENAME. " |
|   CALL FUNCTION 'CNV_MBT_CONTROL_TABLES_WRITE' "Get PCL control tables, remote call |
| EXPORTING | ||
| PACKID | = lv_packid | |
| MODE | = lv_mode | |
| TABLES | ||
| I_CNVMBTCOBJ | = lt_i_cnvmbtcobj | |
| I_CNVMBTCONFLICTS | = lt_i_cnvmbtconflicts | |
| I_CNVMBTDOMCONFL | = lt_i_cnvmbtdomconfl | |
| I_CNVMBTTREE | = lt_i_cnvmbttree | |
| I_CNVMBTFORKEY | = lt_i_cnvmbtforkey | |
| I_CNVMBTTABSTRUC | = lt_i_cnvmbttabstruc | |
| I_CNVCMIS_TAB_POST | = lt_i_cnvcmis_tab_post | |
| I_CNVCMIS_MAPPING | = lt_i_cnvcmis_mapping | |
| I_CNVMBTSELREF | = lt_i_cnvmbtselref | |
| I_CNVMBTTABLES | = lt_i_cnvmbttables | |
| I_CNVMBTFIELDS | = lt_i_cnvmbtfields | |
| I_CNVMBTFIPARS | = lt_i_cnvmbtfipars | |
| I_CNVMBTDOMS | = lt_i_cnvmbtdoms | |
| I_CNVMBTRULES | = lt_i_cnvmbtrules | |
| I_CNVMBTRULEPARS | = lt_i_cnvmbtrulepars | |
| I_CNVMBTINCL | = lt_i_cnvmbtincl | |
| I_CNVMBTRENAME | = lt_i_cnvmbtrename | |
| EXCEPTIONS | ||
| INSERT_DUPLICATE_KEY = 1 | ||
| . " CNV_MBT_CONTROL_TABLES_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_CONTROL_TABLES_WRITE
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_packid). | ||||
| "SELECT single AND_RETURN FROM CNVMBTRETSTR INTO @DATA(ld_mode). | ||||
Search for further information about these or an SAP related objects