SAP SCCR_EXECUTE_EXIT_FG Function Module for Execute exit type FG
SCCR_EXECUTE_EXIT_FG is a standard sccr execute exit fg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute exit type FG 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 sccr execute exit fg FM, simply by entering the name SCCR_EXECUTE_EXIT_FG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCCR_CCCEXIT_EXIT_WRAPPER
Program Name: SAPLSCCR_CCCEXIT_EXIT_WRAPPER
Main Program: SAPLSCCR_CCCEXIT_EXIT_WRAPPER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SCCR_EXECUTE_EXIT_FG 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 'SCCR_EXECUTE_EXIT_FG'"Execute exit type FG.
EXPORTING
FUNCTION_MODULE = "
* GT_E071K = "
* RFCDEST = "
* CC_SOURCECLIENT = "
* TEST = "
* CLII = "
* APPL = "
* MODUS = "
* RUNS_IN_SOURCE = "
* GT_E071 = "
IMPORTING
RCOD = "
EXCEPTION_MESSAGE = "
REMOVE_TAB = "
TABLES
* GEN_TAB = "
* E071_TAB = "
* E071K_TAB = "
EXCEPTIONS
RFC_NOT_ALLOWED = 1
IMPORTING Parameters details for SCCR_EXECUTE_EXIT_FG
FUNCTION_MODULE -
Data type: RS38L_FNAMOptional: No
Call by Reference: No ( called with pass by value option)
GT_E071K -
Data type: TR_KEYSOptional: Yes
Call by Reference: No ( called with pass by value option)
RFCDEST -
Data type: RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
CC_SOURCECLIENT -
Data type: SYMANDTOptional: Yes
Call by Reference: No ( called with pass by value option)
TEST -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
CLII -
Data type: CCCLIINDEPOptional: Yes
Call by Reference: No ( called with pass by value option)
APPL -
Data type: CCAPPLDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
MODUS -
Data type: CCMODUSOptional: Yes
Call by Reference: No ( called with pass by value option)
RUNS_IN_SOURCE -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
GT_E071 -
Data type: TR_OBJECTSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SCCR_EXECUTE_EXIT_FG
RCOD -
Data type: SYSUBRCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTION_MESSAGE -
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
REMOVE_TAB -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SCCR_EXECUTE_EXIT_FG
GEN_TAB -
Data type: E071Optional: Yes
Call by Reference: Yes
E071_TAB -
Data type: E071Optional: Yes
Call by Reference: Yes
E071K_TAB -
Data type: E071KOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
RFC_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCCR_EXECUTE_EXIT_FG 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_rcod | TYPE SYSUBRC, " | |||
| lt_gen_tab | TYPE STANDARD TABLE OF E071, " | |||
| lv_function_module | TYPE RS38L_FNAM, " | |||
| lv_rfc_not_allowed | TYPE RS38L_FNAM, " | |||
| lv_gt_e071k | TYPE TR_KEYS, " | |||
| lv_rfcdest | TYPE RFCDEST, " | |||
| lt_e071_tab | TYPE STANDARD TABLE OF E071, " | |||
| lv_exception_message | TYPE STRING, " | |||
| lt_e071k_tab | TYPE STANDARD TABLE OF E071K, " | |||
| lv_remove_tab | TYPE XSTRING, " | |||
| lv_cc_sourceclient | TYPE SYMANDT, " | |||
| lv_test | TYPE FLAG, " | |||
| lv_clii | TYPE CCCLIINDEP, " | |||
| lv_appl | TYPE CCAPPLDATA, " | |||
| lv_modus | TYPE CCMODUS, " | |||
| lv_runs_in_source | TYPE FLAG, " | |||
| lv_gt_e071 | TYPE TR_OBJECTS. " |
|   CALL FUNCTION 'SCCR_EXECUTE_EXIT_FG' "Execute exit type FG |
| EXPORTING | ||
| FUNCTION_MODULE | = lv_function_module | |
| GT_E071K | = lv_gt_e071k | |
| RFCDEST | = lv_rfcdest | |
| CC_SOURCECLIENT | = lv_cc_sourceclient | |
| TEST | = lv_test | |
| CLII | = lv_clii | |
| APPL | = lv_appl | |
| MODUS | = lv_modus | |
| RUNS_IN_SOURCE | = lv_runs_in_source | |
| GT_E071 | = lv_gt_e071 | |
| IMPORTING | ||
| RCOD | = lv_rcod | |
| EXCEPTION_MESSAGE | = lv_exception_message | |
| REMOVE_TAB | = lv_remove_tab | |
| TABLES | ||
| GEN_TAB | = lt_gen_tab | |
| E071_TAB | = lt_e071_tab | |
| E071K_TAB | = lt_e071k_tab | |
| EXCEPTIONS | ||
| RFC_NOT_ALLOWED = 1 | ||
| . " SCCR_EXECUTE_EXIT_FG | ||
ABAP code using 7.40 inline data declarations to call FM SCCR_EXECUTE_EXIT_FG
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