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

Function AP_SCE_EXTRACT 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 'AP_SCE_EXTRACT'"Extract configuration data.
EXPORTING
IT_KBID = "Knowledge Base ID (NoLogsys)
* IV_SYNCHRONOUS = 'F' "Flag
IMPORTING Parameters details for AP_SCE_EXTRACT
IT_KBID - Knowledge Base ID (NoLogsys)
Data type: COMT_CFGDT_KBID_IOptional: No
Call by Reference: Yes
IV_SYNCHRONOUS - Flag
Data type: COMT_CFGD_FLAGDefault: 'F'
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for AP_SCE_EXTRACT 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_kbid | TYPE COMT_CFGDT_KBID_I, " | |||
| lv_iv_synchronous | TYPE COMT_CFGD_FLAG. " 'F' |
|   CALL FUNCTION 'AP_SCE_EXTRACT' "Extract configuration data |
| EXPORTING | ||
| IT_KBID | = lv_it_kbid | |
| IV_SYNCHRONOUS | = lv_iv_synchronous | |
| . " AP_SCE_EXTRACT | ||
ABAP code using 7.40 inline data declarations to call FM AP_SCE_EXTRACT
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.| DATA(ld_iv_synchronous) | = 'F'. | |||
Search for further information about these or an SAP related objects