SAP GLE_ECS_GLEWR_1200 Function Module for
GLE_ECS_GLEWR_1200 is a standard gle ecs glewr 1200 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 gle ecs glewr 1200 FM, simply by entering the name GLE_ECS_GLEWR_1200 into the relevant SAP transaction such as SE37 or SE38.
Function Group: GLE_ECS_GLEWR_PP
Program Name: SAPLGLE_ECS_GLEWR_PP
Main Program: SAPLGLE_ECS_GLEWR_PP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GLE_ECS_GLEWR_1200 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 'GLE_ECS_GLEWR_1200'".
EXPORTING
I_TAB_OBJKEY = "
IMPORTING
E_TAB_OBJKEY_NOT_VALID = "
E_TAB_OBJKEY_NEW = "
IMPORTING Parameters details for GLE_ECS_GLEWR_1200
I_TAB_OBJKEY -
Data type: BANK_TAB_OBJKEYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GLE_ECS_GLEWR_1200
E_TAB_OBJKEY_NOT_VALID -
Data type: BANK_TAB_OBJKEYOptional: No
Call by Reference: Yes
E_TAB_OBJKEY_NEW -
Data type: BANK_TAB_OBJKEYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GLE_ECS_GLEWR_1200 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_tab_objkey | TYPE BANK_TAB_OBJKEY, " | |||
| lv_e_tab_objkey_not_valid | TYPE BANK_TAB_OBJKEY, " | |||
| lv_e_tab_objkey_new | TYPE BANK_TAB_OBJKEY. " |
|   CALL FUNCTION 'GLE_ECS_GLEWR_1200' " |
| EXPORTING | ||
| I_TAB_OBJKEY | = lv_i_tab_objkey | |
| IMPORTING | ||
| E_TAB_OBJKEY_NOT_VALID | = lv_e_tab_objkey_not_valid | |
| E_TAB_OBJKEY_NEW | = lv_e_tab_objkey_new | |
| . " GLE_ECS_GLEWR_1200 | ||
ABAP code using 7.40 inline data declarations to call FM GLE_ECS_GLEWR_1200
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