KL_READ_JBKLOBJ1_S5 SAP Function module - Lesen jbdklobj1 mit Objekttypkonstanten und Länderrisk.

KL_READ_JBKLOBJ1_S5 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name KL_READ_JBKLOBJ1_S5 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: KLSEL
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM KL_READ_JBKLOBJ1_S5 - KL READ JBKLOBJ1 S5

CALL FUNCTION 'KL_READ_JBKLOBJ1_S5' "Lesen  jbdklobj1 mit Objekttypkonstanten und Länderrisk.
  EXPORTING
    i_objart =                  " ftr_object_key-obart  Objektart
    i_jbdobj1_proj_tab =        " kl2_jbdobj1_projektion_tab
    i_akt_datum =               " sy-datum      Datum und Zeit, aktuelles (Applikationsserver-)Datum
    i_control =                 " klcontrol     Steuergrößen für die Ausfallrisiko-Limitierung
  IMPORTING
    e_jbdobj1_projektion_tab =   " kl2_jbdobj1_projektion_tab
  TABLES
    c_error_itab =              " bapierr       OR: structure of error-handling
* CHANGING
*   i_jbdobj1_proj_typ =        " kl2_jbdobj1_projektion_typ
  EXCEPTIONS
    NOTHING_FOUND = 1           "
    .  "  KL_READ_JBKLOBJ1_S5

ABAP code example for Function Module KL_READ_JBKLOBJ1_S5

The ABAP code below is a full code listing to execute function module KL_READ_JBKLOBJ1_S5 including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_jbdobj1_projektion_tab  
 
 TYPE KL2_JBDOBJ1_PROJEKTION_TAB
,
it_c_error_itab  
 
 TYPE STANDARD TABLE OF BAPIERR,"TABLES PARAM
wa_c_error_itab
 
 LIKE LINE OF it_c_error_itab
.


DATA(ld_i_jbdobj1_proj_typ) = 'Check type of data required'.


DATA(ld_i_objart) = some text here

DATA(ld_i_jbdobj1_proj_tab) = 'Check type of data required'.

DATA(ld_i_akt_datum) = '20210129'.

DATA(ld_i_control) = '20210129'.
 

"populate fields of struture and append to itab
append wa_c_error_itab to it_c_error_itab.
.

CALL FUNCTION 'KL_READ_JBKLOBJ1_S5'
  EXPORTING
    i_objart =                   ld_i_objart
    i_jbdobj1_proj_tab =         ld_i_jbdobj1_proj_tab
    i_akt_datum =                ld_i_akt_datum
    i_control =                  ld_i_control
  IMPORTING
    e_jbdobj1_projektion_tab =    ld_e_jbdobj1_projektion_tab
  TABLES
    c_error_itab =               it_c_error_itab
* CHANGING
*   i_jbdobj1_proj_typ =         ld_i_jbdobj1_proj_typ
  EXCEPTIONS
    NOTHING_FOUND =              1
    .  "  KL_READ_JBKLOBJ1_S5

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_i_jbdobj1_proj_typ
 
 TYPE KL2_JBDOBJ1_PROJEKTION_TYP ,
ld_e_jbdobj1_projektion_tab
 
 TYPE KL2_JBDOBJ1_PROJEKTION_TAB ,
ld_i_objart
 
 TYPE FTR_OBJECT_KEY-OBART ,
it_c_error_itab
 
 TYPE STANDARD TABLE OF BAPIERR ,
wa_c_error_itab
 
 LIKE LINE OF it_c_error_itab,
ld_i_jbdobj1_proj_tab
 
 TYPE KL2_JBDOBJ1_PROJEKTION_TAB ,
ld_i_akt_datum
 
 TYPE SY-DATUM ,
ld_i_control
 
 TYPE KLCONTROL .


ld_i_jbdobj1_proj_typ = '20210129'.

ld_i_objart = some text here 

"populate fields of struture and append to itab
append wa_c_error_itab to it_c_error_itab.
ld_i_jbdobj1_proj_tab = '20210129'.
ld_i_akt_datum = '20210129'.
ld_i_control = '20210129'.