SAP CNV_MBT_DEXTYPE_GET_DEFINITION Function Module for Get Data Extract Type definition details









CNV_MBT_DEXTYPE_GET_DEFINITION is a standard cnv mbt dextype get definition 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 Data Extract Type definition details 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 dextype get definition FM, simply by entering the name CNV_MBT_DEXTYPE_GET_DEFINITION into the relevant SAP transaction such as SE37 or SE38.

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



Function CNV_MBT_DEXTYPE_GET_DEFINITION 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_DEXTYPE_GET_DEFINITION'"Get Data Extract Type definition details
EXPORTING
IM_DEX_TYPE = "DMIS PCL Data Extract Type
* IM_FILE_TYPE = ' ' "DMIS PCL Data Extract File type
* IM_ELEMENT_CLASS = ' ' "DMIS PCL Data Extract Element class

IMPORTING
EX_CNVMBTDEXTYPE = "DMIS PCL Data Extract Types

TABLES
* EXT_CNVMBTDEXTYPE = "DMIS PCL Data Extract Types
* EXT_CNVMBTDEXTYPEDEF = "DMIS PCL Data Extract Types - Definition of elements

EXCEPTIONS
DATA_EXTRACT_TYPE_NOT_DEFINED = 1 INVALID_CALL = 2 INTERNAL_ERROR = 3
.



IMPORTING Parameters details for CNV_MBT_DEXTYPE_GET_DEFINITION

IM_DEX_TYPE - DMIS PCL Data Extract Type

Data type: CNV_MBT_DEXTYPE
Optional: No
Call by Reference: Yes

IM_FILE_TYPE - DMIS PCL Data Extract File type

Data type: CNV_MBT_DEXFILETYPE
Default: SPACE
Optional: Yes
Call by Reference: Yes

IM_ELEMENT_CLASS - DMIS PCL Data Extract Element class

Data type: CNV_MBT_DEXELEMENTCLASS
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CNV_MBT_DEXTYPE_GET_DEFINITION

EX_CNVMBTDEXTYPE - DMIS PCL Data Extract Types

Data type: CNVMBTDEXTYPE
Optional: No
Call by Reference: Yes

TABLES Parameters details for CNV_MBT_DEXTYPE_GET_DEFINITION

EXT_CNVMBTDEXTYPE - DMIS PCL Data Extract Types

Data type: CNVMBTDEXTYPE
Optional: Yes
Call by Reference: Yes

EXT_CNVMBTDEXTYPEDEF - DMIS PCL Data Extract Types - Definition of elements

Data type: CNVMBTDEXTYPEDEF
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

DATA_EXTRACT_TYPE_NOT_DEFINED - the given Data Extract type is not defined

Data type:
Optional: No
Call by Reference: Yes

INVALID_CALL -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_MBT_DEXTYPE_GET_DEFINITION 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_dex_type  TYPE CNV_MBT_DEXTYPE, "   
lv_ex_cnvmbtdextype  TYPE CNVMBTDEXTYPE, "   
lt_ext_cnvmbtdextype  TYPE STANDARD TABLE OF CNVMBTDEXTYPE, "   
lv_data_extract_type_not_defined  TYPE CNVMBTDEXTYPE, "   
lv_im_file_type  TYPE CNV_MBT_DEXFILETYPE, "   SPACE
lv_invalid_call  TYPE CNV_MBT_DEXFILETYPE, "   
lt_ext_cnvmbtdextypedef  TYPE STANDARD TABLE OF CNVMBTDEXTYPEDEF, "   
lv_internal_error  TYPE CNVMBTDEXTYPEDEF, "   
lv_im_element_class  TYPE CNV_MBT_DEXELEMENTCLASS. "   SPACE

  CALL FUNCTION 'CNV_MBT_DEXTYPE_GET_DEFINITION'  "Get Data Extract Type definition details
    EXPORTING
         IM_DEX_TYPE = lv_im_dex_type
         IM_FILE_TYPE = lv_im_file_type
         IM_ELEMENT_CLASS = lv_im_element_class
    IMPORTING
         EX_CNVMBTDEXTYPE = lv_ex_cnvmbtdextype
    TABLES
         EXT_CNVMBTDEXTYPE = lt_ext_cnvmbtdextype
         EXT_CNVMBTDEXTYPEDEF = lt_ext_cnvmbtdextypedef
    EXCEPTIONS
        DATA_EXTRACT_TYPE_NOT_DEFINED = 1
        INVALID_CALL = 2
        INTERNAL_ERROR = 3
. " CNV_MBT_DEXTYPE_GET_DEFINITION




ABAP code using 7.40 inline data declarations to call FM CNV_MBT_DEXTYPE_GET_DEFINITION

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_file_type) = ' '.
 
 
 
 
DATA(ld_im_element_class) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!