SAP Function Modules

READ_TABLE_BUFFERED SAP Function module







READ_TABLE_BUFFERED 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 READ_TABLE_BUFFERED into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: V56A
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM READ_TABLE_BUFFERED - READ TABLE BUFFERED





CALL FUNCTION 'READ_TABLE_BUFFERED' "
  EXPORTING
    i_table =                   " dd02d-tabname
    i_key1 =                    " dd03d-fieldname
*   i_key2 = SPACE              " dd03d-fieldname
*   i_key3 = SPACE              " dd03d-fieldname
*   i_key4 = SPACE              " dd03d-fieldname
    i_value1 =                  "
*   i_value2 = SPACE            "
*   i_value3 = SPACE            "
*   i_value4 = SPACE            "
*   i_buffer_type = 'X'         " c
  IMPORTING
    e_table_workarea =          "
  EXCEPTIONS
    NO_ENTRY_FOUND = 1          "
    NO_TABLE_NAME = 2           "
    .  "  READ_TABLE_BUFFERED

ABAP code example for Function Module READ_TABLE_BUFFERED





The ABAP code below is a full code listing to execute function module READ_TABLE_BUFFERED 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_table_workarea  TYPE STRING .


DATA(ld_i_table) = some text here

DATA(ld_i_key1) = some text here

DATA(ld_i_key2) = some text here

DATA(ld_i_key3) = some text here

DATA(ld_i_key4) = some text here
DATA(ld_i_value1) = 'some text here'.
DATA(ld_i_value2) = 'some text here'.
DATA(ld_i_value3) = 'some text here'.
DATA(ld_i_value4) = 'some text here'.
DATA(ld_i_buffer_type) = 'Check type of data required'. . CALL FUNCTION 'READ_TABLE_BUFFERED' EXPORTING i_table = ld_i_table i_key1 = ld_i_key1 * i_key2 = ld_i_key2 * i_key3 = ld_i_key3 * i_key4 = ld_i_key4 i_value1 = ld_i_value1 * i_value2 = ld_i_value2 * i_value3 = ld_i_value3 * i_value4 = ld_i_value4 * i_buffer_type = ld_i_buffer_type IMPORTING e_table_workarea = ld_e_table_workarea EXCEPTIONS NO_ENTRY_FOUND = 1 NO_TABLE_NAME = 2 . " READ_TABLE_BUFFERED
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "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_e_table_workarea  TYPE STRING ,
ld_i_table  TYPE DD02D-TABNAME ,
ld_i_key1  TYPE DD03D-FIELDNAME ,
ld_i_key2  TYPE DD03D-FIELDNAME ,
ld_i_key3  TYPE DD03D-FIELDNAME ,
ld_i_key4  TYPE DD03D-FIELDNAME ,
ld_i_value1  TYPE STRING ,
ld_i_value2  TYPE STRING ,
ld_i_value3  TYPE STRING ,
ld_i_value4  TYPE STRING ,
ld_i_buffer_type  TYPE C .


ld_i_table = some text here

ld_i_key1 = some text here

ld_i_key2 = some text here

ld_i_key3 = some text here

ld_i_key4 = some text here
ld_i_value1 = 'some text here'.
ld_i_value2 = 'some text here'.
ld_i_value3 = 'some text here'.
ld_i_value4 = 'some text here'.
ld_i_buffer_type = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name READ_TABLE_BUFFERED or its description.