SAP COM_SCE_API_CONFIG_RESULT_XML Function Module for externe Representation der Konfiguration im XML Format
COM_SCE_API_CONFIG_RESULT_XML is a standard com sce api config result xml SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for externe Representation der Konfiguration im XML Format 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 com sce api config result xml FM, simply by entering the name COM_SCE_API_CONFIG_RESULT_XML into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_SCE_API
Program Name: SAPLCOM_SCE_API
Main Program: SAPLCOM_SCE_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_SCE_API_CONFIG_RESULT_XML 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_SCE_API_CONFIG_RESULT_XML'"externe Representation der Konfiguration im XML Format.
EXPORTING
IV_DOCUMENT_GUID = "interne 16 stellige GUID
* IV_GUID = "interne 16 stellige GUID
* IV_CONFIG_ID = "Konfigurations Identifier
* IV_IPC_CLIENT = "client for IPC
IMPORTING
EV_RETCODE = "0:Erfolg, 1: Fehler
ET_CFGXML = "XML Container für die externe Repräsentation der Konfigurati
IMPORTING Parameters details for COM_SCE_API_CONFIG_RESULT_XML
IV_DOCUMENT_GUID - interne 16 stellige GUID
Data type: COMT_SCE_GUIDOptional: No
Call by Reference: Yes
IV_GUID - interne 16 stellige GUID
Data type: COMT_SCE_GUIDOptional: Yes
Call by Reference: Yes
IV_CONFIG_ID - Konfigurations Identifier
Data type: COMT_IPC_CONFIG_IDOptional: Yes
Call by Reference: Yes
IV_IPC_CLIENT - client for IPC
Data type: COMT_SCE_CLIENTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for COM_SCE_API_CONFIG_RESULT_XML
EV_RETCODE - 0:Erfolg, 1: Fehler
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
ET_CFGXML - XML Container für die externe Repräsentation der Konfigurati
Data type: COMT_SCE_CFGXML_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for COM_SCE_API_CONFIG_RESULT_XML 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_ev_retcode | TYPE SY-SUBRC, " | |||
| lv_iv_document_guid | TYPE COMT_SCE_GUID, " | |||
| lv_iv_guid | TYPE COMT_SCE_GUID, " | |||
| lv_et_cfgxml | TYPE COMT_SCE_CFGXML_TAB, " | |||
| lv_iv_config_id | TYPE COMT_IPC_CONFIG_ID, " | |||
| lv_iv_ipc_client | TYPE COMT_SCE_CLIENT. " |
|   CALL FUNCTION 'COM_SCE_API_CONFIG_RESULT_XML' "externe Representation der Konfiguration im XML Format |
| EXPORTING | ||
| IV_DOCUMENT_GUID | = lv_iv_document_guid | |
| IV_GUID | = lv_iv_guid | |
| IV_CONFIG_ID | = lv_iv_config_id | |
| IV_IPC_CLIENT | = lv_iv_ipc_client | |
| IMPORTING | ||
| EV_RETCODE | = lv_ev_retcode | |
| ET_CFGXML | = lv_et_cfgxml | |
| . " COM_SCE_API_CONFIG_RESULT_XML | ||
ABAP code using 7.40 inline data declarations to call FM COM_SCE_API_CONFIG_RESULT_XML
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.| "SELECT single SUBRC FROM SY INTO @DATA(ld_ev_retcode). | ||||
Search for further information about these or an SAP related objects