SAP CNV_MBT_DEX_GET_VALUES Function Module for DMIS Data Extract Values
CNV_MBT_DEX_GET_VALUES is a standard cnv mbt dex get values SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DMIS Data Extract Values 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 dex get values FM, simply by entering the name CNV_MBT_DEX_GET_VALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_MBT_DEX
Program Name: SAPLCNV_MBT_DEX
Main Program: SAPLCNV_MBT_DEX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_MBT_DEX_GET_VALUES 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_DEX_GET_VALUES'"DMIS Data Extract Values.
EXPORTING
IM_DEXID = "DMIS PCL Data Extract ID
* IM_CHECK_CHANGED = '-' "Boolean Variable (X=True, -=False, Space=Unknown)
* IM_EXPORT = 'X' "Boolean Variable (X=True, -=False, Space=Unknown)
* IM_IMPORT = '-' "Boolean Variable (X=True, -=False, Space=Unknown)
* IM_GET_ALL = 'X' "Boolean Variable (X=True, -=False, Space=Unknown)
IMPORTING
EX_IMPORT_PATH = "Logical path name
EX_EXPORT_PATH = "Logical path name
EX_MAX_FILE_SIZE = "Length of a file in bytes
EX_MAX_BLOCK_SIZE = "Length of a file in bytes
EX_CHANGED = "Boolean Variable (X=True, -=False, Space=Unknown)
TABLES
* IMT_CNVMBTDEXHEADA = "DMIS PCL Data Extract Header Attributes
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for CNV_MBT_DEX_GET_VALUES
IM_DEXID - DMIS PCL Data Extract ID
Data type: CNV_MBT_DEXIDOptional: No
Call by Reference: Yes
IM_CHECK_CHANGED - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: '-'
Optional: Yes
Call by Reference: Yes
IM_EXPORT - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: Yes
IM_IMPORT - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: '-'
Optional: Yes
Call by Reference: Yes
IM_GET_ALL - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CNV_MBT_DEX_GET_VALUES
EX_IMPORT_PATH - Logical path name
Data type: PATHINTERNOptional: No
Call by Reference: Yes
EX_EXPORT_PATH - Logical path name
Data type: PATHINTERNOptional: No
Call by Reference: Yes
EX_MAX_FILE_SIZE - Length of a file in bytes
Data type: FILESIZEOptional: No
Call by Reference: Yes
EX_MAX_BLOCK_SIZE - Length of a file in bytes
Data type: FILESIZEOptional: No
Call by Reference: Yes
EX_CHANGED - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: No
Call by Reference: Yes
TABLES Parameters details for CNV_MBT_DEX_GET_VALUES
IMT_CNVMBTDEXHEADA - DMIS PCL Data Extract Header Attributes
Data type: CNVMBTDEXHEADAOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Attributes values not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_DEX_GET_VALUES 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_dexid | TYPE CNV_MBT_DEXID, " | |||
| lv_not_found | TYPE CNV_MBT_DEXID, " | |||
| lv_ex_import_path | TYPE PATHINTERN, " | |||
| lt_imt_cnvmbtdexheada | TYPE STANDARD TABLE OF CNVMBTDEXHEADA, " | |||
| lv_ex_export_path | TYPE PATHINTERN, " | |||
| lv_im_check_changed | TYPE BOOLEAN, " '-' | |||
| lv_im_export | TYPE BOOLEAN, " 'X' | |||
| lv_ex_max_file_size | TYPE FILESIZE, " | |||
| lv_im_import | TYPE BOOLEAN, " '-' | |||
| lv_ex_max_block_size | TYPE FILESIZE, " | |||
| lv_ex_changed | TYPE BOOLEAN, " | |||
| lv_im_get_all | TYPE BOOLEAN. " 'X' |
|   CALL FUNCTION 'CNV_MBT_DEX_GET_VALUES' "DMIS Data Extract Values |
| EXPORTING | ||
| IM_DEXID | = lv_im_dexid | |
| IM_CHECK_CHANGED | = lv_im_check_changed | |
| IM_EXPORT | = lv_im_export | |
| IM_IMPORT | = lv_im_import | |
| IM_GET_ALL | = lv_im_get_all | |
| IMPORTING | ||
| EX_IMPORT_PATH | = lv_ex_import_path | |
| EX_EXPORT_PATH | = lv_ex_export_path | |
| EX_MAX_FILE_SIZE | = lv_ex_max_file_size | |
| EX_MAX_BLOCK_SIZE | = lv_ex_max_block_size | |
| EX_CHANGED | = lv_ex_changed | |
| TABLES | ||
| IMT_CNVMBTDEXHEADA | = lt_imt_cnvmbtdexheada | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " CNV_MBT_DEX_GET_VALUES | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_DEX_GET_VALUES
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.| DATA(ld_im_check_changed) | = '-'. | |||
| DATA(ld_im_export) | = 'X'. | |||
| DATA(ld_im_import) | = '-'. | |||
| DATA(ld_im_get_all) | = 'X'. | |||
Search for further information about these or an SAP related objects