SAP K_KABR_READ Function Module for









K_KABR_READ is a standard k kabr read 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 k kabr read FM, simply by entering the name K_KABR_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: KO79
Program Name: SAPLKO79
Main Program:
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function K_KABR_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 'K_KABR_READ'"
EXPORTING
* I_BELNR = ' ' "
* I_OBJNR = ' ' "
* ARCHIVE_HANDLE = 0 "
* I_APPEND = ' ' "
* I_PROTOCOL = ' ' "

TABLES
* T_AUAK = "
* T_AUAW = "
* T_AUAA = "
* T_AUAB = "
* T_AUAO = "
* T_AUAS = "
* T_AUAI = "
* T_AUAV = "
* T_AUAT = "
* T_AUAY = "

EXCEPTIONS
WRONG_ACCESS_TO_ARCHIVE = 1 NOT_ENOUGH_INFO = 2
.



IMPORTING Parameters details for K_KABR_READ

I_BELNR -

Data type: AUAK-BELNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_OBJNR -

Data type: AUAK-OBJNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ARCHIVE_HANDLE -

Data type: SY-TABIX
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_APPEND -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PROTOCOL -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for K_KABR_READ

T_AUAK -

Data type: AUAK
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAW -

Data type: AUAW
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAA -

Data type: AUAA
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAB -

Data type: AUAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAO -

Data type: AUAO
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAS -

Data type: AUAS
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAI -

Data type: AUAI
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAV -

Data type: AUAV
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAT -

Data type: AUAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_AUAY -

Data type: AUAY
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

WRONG_ACCESS_TO_ARCHIVE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_ENOUGH_INFO -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for K_KABR_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:
lt_t_auak  TYPE STANDARD TABLE OF AUAK, "   
lv_i_belnr  TYPE AUAK-BELNR, "   SPACE
lv_wrong_access_to_archive  TYPE AUAK, "   
lt_t_auaw  TYPE STANDARD TABLE OF AUAW, "   
lt_t_auaa  TYPE STANDARD TABLE OF AUAA, "   
lv_i_objnr  TYPE AUAK-OBJNR, "   SPACE
lv_not_enough_info  TYPE AUAK, "   
lt_t_auab  TYPE STANDARD TABLE OF AUAB, "   
lv_archive_handle  TYPE SY-TABIX, "   0
lt_t_auao  TYPE STANDARD TABLE OF AUAO, "   
lv_i_append  TYPE C, "   SPACE
lt_t_auas  TYPE STANDARD TABLE OF AUAS, "   
lv_i_protocol  TYPE C, "   SPACE
lt_t_auai  TYPE STANDARD TABLE OF AUAI, "   
lt_t_auav  TYPE STANDARD TABLE OF AUAV, "   
lt_t_auat  TYPE STANDARD TABLE OF AUAT, "   
lt_t_auay  TYPE STANDARD TABLE OF AUAY. "   

  CALL FUNCTION 'K_KABR_READ'  "
    EXPORTING
         I_BELNR = lv_i_belnr
         I_OBJNR = lv_i_objnr
         ARCHIVE_HANDLE = lv_archive_handle
         I_APPEND = lv_i_append
         I_PROTOCOL = lv_i_protocol
    TABLES
         T_AUAK = lt_t_auak
         T_AUAW = lt_t_auaw
         T_AUAA = lt_t_auaa
         T_AUAB = lt_t_auab
         T_AUAO = lt_t_auao
         T_AUAS = lt_t_auas
         T_AUAI = lt_t_auai
         T_AUAV = lt_t_auav
         T_AUAT = lt_t_auat
         T_AUAY = lt_t_auay
    EXCEPTIONS
        WRONG_ACCESS_TO_ARCHIVE = 1
        NOT_ENOUGH_INFO = 2
. " K_KABR_READ




ABAP code using 7.40 inline data declarations to call FM K_KABR_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 BELNR FROM AUAK INTO @DATA(ld_i_belnr).
DATA(ld_i_belnr) = ' '.
 
 
 
 
"SELECT single OBJNR FROM AUAK INTO @DATA(ld_i_objnr).
DATA(ld_i_objnr) = ' '.
 
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_archive_handle).
 
 
DATA(ld_i_append) = ' '.
 
 
DATA(ld_i_protocol) = ' '.
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!