SAP KL_UTILS_OBJECT_TEXT_GET_NT Function Module for Get Object Text for Netting Groups
KL_UTILS_OBJECT_TEXT_GET_NT is a standard kl utils object text get nt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Object Text for Netting Groups 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 object text get nt FM, simply by entering the name KL_UTILS_OBJECT_TEXT_GET_NT 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_OBJECT_TEXT_GET_NT 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_OBJECT_TEXT_GET_NT'"Get Object Text for Netting Groups.
EXPORTING
I_OBJNR = "Object Number
IMPORTING
E_TEXT = "Text for External Transaction
IMPORTING Parameters details for KL_UTILS_OBJECT_TEXT_GET_NT
I_OBJNR - Object Number
Data type: ONR00-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for KL_UTILS_OBJECT_TEXT_GET_NT
E_TEXT - Text for External Transaction
Data type: SY-MSGLIOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KL_UTILS_OBJECT_TEXT_GET_NT 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_text | TYPE SY-MSGLI, " | |||
| lv_i_objnr | TYPE ONR00-OBJNR. " |
|   CALL FUNCTION 'KL_UTILS_OBJECT_TEXT_GET_NT' "Get Object Text for Netting Groups |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| IMPORTING | ||
| E_TEXT | = lv_e_text | |
| . " KL_UTILS_OBJECT_TEXT_GET_NT | ||
ABAP code using 7.40 inline data declarations to call FM KL_UTILS_OBJECT_TEXT_GET_NT
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.| "SELECT single MSGLI FROM SY INTO @DATA(ld_e_text). | ||||
| "SELECT single OBJNR FROM ONR00 INTO @DATA(ld_i_objnr). | ||||
Search for further information about these or an SAP related objects