SAP COM_SETT_EEW_META_DATA_CREATE Function Module for
COM_SETT_EEW_META_DATA_CREATE is a standard com sett eew meta data create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 com sett eew meta data create FM, simply by entering the name COM_SETT_EEW_META_DATA_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_ATTR_WZ
Program Name: SAPLCOM_ATTR_WZ
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_SETT_EEW_META_DATA_CREATE 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 'COM_SETT_EEW_META_DATA_CREATE'".
EXPORTING
* IV_SETTYPE_ID = "
IV_SETTYPE_MV = "
IR_PROJECT = "
IV_DEVCLASS = "
IT_DEVCLASS = "
IMPORTING Parameters details for COM_SETT_EEW_META_DATA_CREATE
IV_SETTYPE_ID -
Data type: COMT_FRGTYPE_IDOptional: Yes
Call by Reference: Yes
IV_SETTYPE_MV -
Data type: DDOBJNAMEOptional: No
Call by Reference: Yes
IR_PROJECT -
Data type: CL_OXT_PROJECT_OLOptional: No
Call by Reference: Yes
IV_DEVCLASS -
Data type: DEVCLASSOptional: No
Call by Reference: Yes
IT_DEVCLASS -
Data type: TOXT_RT_DEVCLASSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for COM_SETT_EEW_META_DATA_CREATE 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_settype_id | TYPE COMT_FRGTYPE_ID, " | |||
| lv_iv_settype_mv | TYPE DDOBJNAME, " | |||
| lv_ir_project | TYPE CL_OXT_PROJECT_OL, " | |||
| lv_iv_devclass | TYPE DEVCLASS, " | |||
| lv_it_devclass | TYPE TOXT_RT_DEVCLASS. " |
|   CALL FUNCTION 'COM_SETT_EEW_META_DATA_CREATE' " |
| EXPORTING | ||
| IV_SETTYPE_ID | = lv_iv_settype_id | |
| IV_SETTYPE_MV | = lv_iv_settype_mv | |
| IR_PROJECT | = lv_ir_project | |
| IV_DEVCLASS | = lv_iv_devclass | |
| IT_DEVCLASS | = lv_it_devclass | |
| . " COM_SETT_EEW_META_DATA_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM COM_SETT_EEW_META_DATA_CREATE
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