SAP ECC_SCE_REQUEST Function Module for Single KB Download
ECC_SCE_REQUEST is a standard ecc sce request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Single KB Download 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 ecc sce request FM, simply by entering the name ECC_SCE_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: CFG_ERP_DB_TRANS
Program Name: SAPLCFG_ERP_DB_TRANS
Main Program: SAPLCFG_ERP_DB_TRANS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ECC_SCE_REQUEST 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 'ECC_SCE_REQUEST'"Single KB Download.
EXPORTING
IT_KBNAME = "KB Name
IT_KBVERSION = "KB Version
IMPORTING
ET_ERROR_MESSAGES = "Error Messages
IMPORTING Parameters details for ECC_SCE_REQUEST
IT_KBNAME - KB Name
Data type: COMT_CFGD_KBNAMEOptional: No
Call by Reference: Yes
IT_KBVERSION - KB Version
Data type: COMT_CFGD_KBVERSIONOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ECC_SCE_REQUEST
ET_ERROR_MESSAGES - Error Messages
Data type: BAPIRET2_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ECC_SCE_REQUEST 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_it_kbname | TYPE COMT_CFGD_KBNAME, " | |||
| lv_et_error_messages | TYPE BAPIRET2_TAB, " | |||
| lv_it_kbversion | TYPE COMT_CFGD_KBVERSION. " |
|   CALL FUNCTION 'ECC_SCE_REQUEST' "Single KB Download |
| EXPORTING | ||
| IT_KBNAME | = lv_it_kbname | |
| IT_KBVERSION | = lv_it_kbversion | |
| IMPORTING | ||
| ET_ERROR_MESSAGES | = lv_et_error_messages | |
| . " ECC_SCE_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM ECC_SCE_REQUEST
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