SAP DMS_VEG_GET_METADATA Function Module for Get Metadata in form of scenedata and formdata
DMS_VEG_GET_METADATA is a standard dms veg get metadata 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 Metadata in form of scenedata and formdata 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 dms veg get metadata FM, simply by entering the name DMS_VEG_GET_METADATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: DMS_VEG_TEMPLATE
Program Name: SAPLDMS_VEG_TEMPLATE
Main Program: SAPLDMS_VEG_TEMPLATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DMS_VEG_GET_METADATA 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 'DMS_VEG_GET_METADATA'"Get Metadata in form of scenedata and formdata.
EXPORTING
* IV_DOCUMENT = "Document number
* IV_DOC_TYPE = "Document Type
* IV_DOC_PART = "Document Part
* IV_DOC_VERS = "Document Version
* IV_MATERIAL = "Material Number
* IV_PLANT = "Plant
* IV_DATE = "Date
IMPORTING
ET_SCENEDATA = "Scene data for PDF Conversion
ET_FORMDATA = "Form Data for PDF Conversion
ES_DOCUMENTID = "Table Type for VEG Convserion
ET_MESSAGES = "Message Table
IMPORTING Parameters details for DMS_VEG_GET_METADATA
IV_DOCUMENT - Document number
Data type: DOKNROptional: Yes
Call by Reference: Yes
IV_DOC_TYPE - Document Type
Data type: DOKAROptional: Yes
Call by Reference: Yes
IV_DOC_PART - Document Part
Data type: DOKTL_DOptional: Yes
Call by Reference: Yes
IV_DOC_VERS - Document Version
Data type: DOKVROptional: Yes
Call by Reference: Yes
IV_MATERIAL - Material Number
Data type: MATNROptional: Yes
Call by Reference: Yes
IV_PLANT - Plant
Data type: WERKS_DOptional: Yes
Call by Reference: Yes
IV_DATE - Date
Data type: DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DMS_VEG_GET_METADATA
ET_SCENEDATA - Scene data for PDF Conversion
Data type: DMS_TBL_SCENE_DATAOptional: No
Call by Reference: Yes
ET_FORMDATA - Form Data for PDF Conversion
Data type: DMS_TBL_FORMDATAOptional: No
Call by Reference: Yes
ES_DOCUMENTID - Table Type for VEG Convserion
Data type: DMS_S_VEG_CNVOptional: No
Call by Reference: Yes
ET_MESSAGES - Message Table
Data type: DMS_TBL_MSGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DMS_VEG_GET_METADATA 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_iv_document | TYPE DOKNR, " | |||
| lv_et_scenedata | TYPE DMS_TBL_SCENE_DATA, " | |||
| lv_et_formdata | TYPE DMS_TBL_FORMDATA, " | |||
| lv_iv_doc_type | TYPE DOKAR, " | |||
| lv_iv_doc_part | TYPE DOKTL_D, " | |||
| lv_es_documentid | TYPE DMS_S_VEG_CNV, " | |||
| lv_et_messages | TYPE DMS_TBL_MSG, " | |||
| lv_iv_doc_vers | TYPE DOKVR, " | |||
| lv_iv_material | TYPE MATNR, " | |||
| lv_iv_plant | TYPE WERKS_D, " | |||
| lv_iv_date | TYPE DATUM. " |
|   CALL FUNCTION 'DMS_VEG_GET_METADATA' "Get Metadata in form of scenedata and formdata |
| EXPORTING | ||
| IV_DOCUMENT | = lv_iv_document | |
| IV_DOC_TYPE | = lv_iv_doc_type | |
| IV_DOC_PART | = lv_iv_doc_part | |
| IV_DOC_VERS | = lv_iv_doc_vers | |
| IV_MATERIAL | = lv_iv_material | |
| IV_PLANT | = lv_iv_plant | |
| IV_DATE | = lv_iv_date | |
| IMPORTING | ||
| ET_SCENEDATA | = lv_et_scenedata | |
| ET_FORMDATA | = lv_et_formdata | |
| ES_DOCUMENTID | = lv_es_documentid | |
| ET_MESSAGES | = lv_et_messages | |
| . " DMS_VEG_GET_METADATA | ||
ABAP code using 7.40 inline data declarations to call FM DMS_VEG_GET_METADATA
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