TFW_READ SAP Function module

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

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

Pattern for FM TFW_READ - TFW READ

CALL FUNCTION 'TFW_READ' "
  EXPORTING
    iv_tfw_object =             " tfw_appl_object
    iv_minitp_type =            " tfw_minitp_type
    i_object_keys =             " any
*   iv_reset_buffer = SPACE     " boole-boole
*   iv_context =                " tfw_context
*   iv_client = SY-MANDT        " mandt
  IMPORTING
    e_data =                    " any
    e_read_information =        " any
    et_return =                 " bapiret2_t
  EXCEPTIONS
    READ_NOT_POSSIBLE = 1       "
    PROBLEMS_WITH_BADI = 2      "
    .  "  TFW_READ

ABAP code example for Function Module TFW_READ

The ABAP code below is a full code listing to execute function module TFW_READ 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_data  
 
 TYPE ANY
,
ld_e_read_information  
 
 TYPE ANY
,
ld_et_return  
 
 TYPE BAPIRET2_T
.


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

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

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


DATA(ld_iv_reset_buffer) = some text here

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

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

CALL FUNCTION 'TFW_READ'
  EXPORTING
    iv_tfw_object =              ld_iv_tfw_object
    iv_minitp_type =             ld_iv_minitp_type
    i_object_keys =              ld_i_object_keys
*   iv_reset_buffer =            ld_iv_reset_buffer
*   iv_context =                 ld_iv_context
*   iv_client =                  ld_iv_client
  IMPORTING
    e_data =                     ld_e_data
    e_read_information =         ld_e_read_information
    et_return =                  ld_et_return
  EXCEPTIONS
    READ_NOT_POSSIBLE =          1
    PROBLEMS_WITH_BADI =         2
    .  "  TFW_READ

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_data
 
 TYPE ANY ,
ld_iv_tfw_object
 
 TYPE TFW_APPL_OBJECT ,
ld_e_read_information
 
 TYPE ANY ,
ld_iv_minitp_type
 
 TYPE TFW_MINITP_TYPE ,
ld_et_return
 
 TYPE BAPIRET2_T ,
ld_i_object_keys
 
 TYPE ANY ,
ld_iv_reset_buffer
 
 TYPE BOOLE-BOOLE ,
ld_iv_context
 
 TYPE TFW_CONTEXT ,
ld_iv_client
 
 TYPE MANDT .


ld_iv_tfw_object = 'Check type of data required'.
ld_iv_minitp_type = 'Check type of data required'.
ld_i_object_keys = 'Check type of data required'.

ld_iv_reset_buffer = some text here
ld_iv_context = 'Check type of data required'.
ld_iv_client = 'Check type of data required'.