SAP KL_UTILS_GET_EXT_KEY Function Module for Credit Limit: Get External Key Fields
KL_UTILS_GET_EXT_KEY is a standard kl utils get ext key SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Credit Limit: Get External Key Fields 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 kl utils get ext key FM, simply by entering the name KL_UTILS_GET_EXT_KEY into the relevant SAP transaction such as SE37 or SE38.
Function Group: KLUTILS
Program Name: SAPLKLUTILS
Main Program: SAPLKLUTILS
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function KL_UTILS_GET_EXT_KEY 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 'KL_UTILS_GET_EXT_KEY'"Credit Limit: Get External Key Fields.
EXPORTING
I_EXTADMNR = "
IMPORTING
E_EXT_SCHL = "
EXCEPTIONS
NO_OBJ_TYP = 1 NO_EXT_KEY = 2
IMPORTING Parameters details for KL_UTILS_GET_EXT_KEY
I_EXTADMNR -
Data type: KLEXTOBJADMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for KL_UTILS_GET_EXT_KEY
E_EXT_SCHL -
Data type: KLJCUROptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_OBJ_TYP - Cannot find object type
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_EXT_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KL_UTILS_GET_EXT_KEY 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_e_ext_schl | TYPE KLJCUR, " | |||
| lv_i_extadmnr | TYPE KLEXTOBJADM, " | |||
| lv_no_obj_typ | TYPE KLEXTOBJADM, " | |||
| lv_no_ext_key | TYPE KLEXTOBJADM. " |
|   CALL FUNCTION 'KL_UTILS_GET_EXT_KEY' "Credit Limit: Get External Key Fields |
| EXPORTING | ||
| I_EXTADMNR | = lv_i_extadmnr | |
| IMPORTING | ||
| E_EXT_SCHL | = lv_e_ext_schl | |
| EXCEPTIONS | ||
| NO_OBJ_TYP = 1 | ||
| NO_EXT_KEY = 2 | ||
| . " KL_UTILS_GET_EXT_KEY | ||
ABAP code using 7.40 inline data declarations to call FM KL_UTILS_GET_EXT_KEY
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