SAP GLE_ECS_DB_GET_NUMKR Function Module for
GLE_ECS_DB_GET_NUMKR is a standard gle ecs db get numkr 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 db get numkr FM, simply by entering the name GLE_ECS_DB_GET_NUMKR into the relevant SAP transaction such as SE37 or SE38.
Function Group: GLE_ECS_DB_READER
Program Name: SAPLGLE_ECS_DB_READER
Main Program: SAPLGLE_ECS_DB_READER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GLE_ECS_DB_GET_NUMKR 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_DB_GET_NUMKR'".
EXPORTING
I_AWREF_OBJ = "
IMPORTING
E_NUMKR = "
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for GLE_ECS_DB_GET_NUMKR
I_AWREF_OBJ -
Data type: NROBJOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GLE_ECS_DB_GET_NUMKR
E_NUMKR -
Data type: NUMKROptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GLE_ECS_DB_GET_NUMKR 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_failed | TYPE STRING, " | |||
| lv_e_numkr | TYPE NUMKR, " | |||
| lv_i_awref_obj | TYPE NROBJ. " |
|   CALL FUNCTION 'GLE_ECS_DB_GET_NUMKR' " |
| EXPORTING | ||
| I_AWREF_OBJ | = lv_i_awref_obj | |
| IMPORTING | ||
| E_NUMKR | = lv_e_numkr | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " GLE_ECS_DB_GET_NUMKR | ||
ABAP code using 7.40 inline data declarations to call FM GLE_ECS_DB_GET_NUMKR
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