SAP CME_API_DTYPE_EXPORT_EXTENSION Function Module for CME Data Type - Export Extension Data in XSTRING
CME_API_DTYPE_EXPORT_EXTENSION is a standard cme api dtype export extension SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CME Data Type - Export Extension Data in XSTRING 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 cme api dtype export extension FM, simply by entering the name CME_API_DTYPE_EXPORT_EXTENSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: CME_API_DTYPE
Program Name: SAPLCME_API_DTYPE
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CME_API_DTYPE_EXPORT_EXTENSION 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 'CME_API_DTYPE_EXPORT_EXTENSION'"CME Data Type - Export Extension Data in XSTRING.
EXPORTING
I_SETTYPE_NAME = "Set Type Name
* I_SETTYPE_OWNER_ID = "CME Owner -External Name-
* I_SETTYPE_OWNER_GUID = "Owner
IT_EXTENSIONS_IN = "Extension Data
IMPORTING
ES_EXTENSIONS_OUT = "CME Extension Concept -Structure for Including XSTRING-
IMPORTING Parameters details for CME_API_DTYPE_EXPORT_EXTENSION
I_SETTYPE_NAME - Set Type Name
Data type: COMT_FRGTYPE_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_SETTYPE_OWNER_ID - CME Owner -External Name-
Data type: CME_OWNER_ID_COptional: Yes
Call by Reference: No ( called with pass by value option)
I_SETTYPE_OWNER_GUID - Owner
Data type: DML_OWNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IT_EXTENSIONS_IN - Extension Data
Data type: ANY TABLEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CME_API_DTYPE_EXPORT_EXTENSION
ES_EXTENSIONS_OUT - CME Extension Concept -Structure for Including XSTRING-
Data type: CME_S_EXTENSIONSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CME_API_DTYPE_EXPORT_EXTENSION 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_i_settype_name | TYPE COMT_FRGTYPE_ID, " | |||
| lv_es_extensions_out | TYPE CME_S_EXTENSIONS, " | |||
| lv_i_settype_owner_id | TYPE CME_OWNER_ID_C, " | |||
| lv_i_settype_owner_guid | TYPE DML_OWNER, " | |||
| lv_it_extensions_in | TYPE ANY TABLE. " |
|   CALL FUNCTION 'CME_API_DTYPE_EXPORT_EXTENSION' "CME Data Type - Export Extension Data in XSTRING |
| EXPORTING | ||
| I_SETTYPE_NAME | = lv_i_settype_name | |
| I_SETTYPE_OWNER_ID | = lv_i_settype_owner_id | |
| I_SETTYPE_OWNER_GUID | = lv_i_settype_owner_guid | |
| IT_EXTENSIONS_IN | = lv_it_extensions_in | |
| IMPORTING | ||
| ES_EXTENSIONS_OUT | = lv_es_extensions_out | |
| . " CME_API_DTYPE_EXPORT_EXTENSION | ||
ABAP code using 7.40 inline data declarations to call FM CME_API_DTYPE_EXPORT_EXTENSION
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