SAP KL_OBJECT_READ Function Module for KL: Lesen des KL Finanzobjektes
KL_OBJECT_READ is a standard kl object read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for KL: Lesen des KL Finanzobjektes 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 object read FM, simply by entering the name KL_OBJECT_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: KLLRFO
Program Name: SAPLKLLRFO
Main Program: SAPLKLLRFO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function KL_OBJECT_READ 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_OBJECT_READ'"KL: Lesen des KL Finanzobjektes.
EXPORTING
I_OBJNR = "OR: OBJNR, internal number of financial object in ISB
IMPORTING
E_VJBKLOBJ1 = "Generierte Tabelle zum View V_JBKLOBJ1
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for KL_OBJECT_READ
I_OBJNR - OR: OBJNR, internal number of financial object in ISB
Data type: JBKLOBJ1-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for KL_OBJECT_READ
E_VJBKLOBJ1 - Generierte Tabelle zum View V_JBKLOBJ1
Data type: V_JBKLOBJ1Optional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Objektnummer nicht gefunden
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for KL_OBJECT_READ 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_objnr | TYPE JBKLOBJ1-OBJNR, " | |||
| lv_not_found | TYPE JBKLOBJ1, " | |||
| lv_e_vjbklobj1 | TYPE V_JBKLOBJ1. " |
|   CALL FUNCTION 'KL_OBJECT_READ' "KL: Lesen des KL Finanzobjektes |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| IMPORTING | ||
| E_VJBKLOBJ1 | = lv_e_vjbklobj1 | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " KL_OBJECT_READ | ||
ABAP code using 7.40 inline data declarations to call FM KL_OBJECT_READ
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 OBJNR FROM JBKLOBJ1 INTO @DATA(ld_i_objnr). | ||||
Search for further information about these or an SAP related objects