RCP341_OBJ_VIA_CLASS_READ SAP Function module

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

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

Pattern for FM RCP341_OBJ_VIA_CLASS_READ - RCP341 OBJ VIA CLASS READ

CALL FUNCTION 'RCP341_OBJ_VIA_CLASS_READ' "
  EXPORTING
    i_valfrom =                 " pvs_adatum
    i_valto =                   " pvs_bdatum
*   i_key_type_master_pob =     " pvs_pnode_type
    i_estcat =                  " eseestcat
*   it_restriction_keys =       " rcpty_api_key
*   i_flg_pob_search = ESP1_FALSE  " esp1_boolean
  IMPORTING
    et_result_keys =            " rcpty_api_key
  EXCEPTIONS
    INTERNAL_ERROR = 1          "
    .  "  RCP341_OBJ_VIA_CLASS_READ

ABAP code example for Function Module RCP341_OBJ_VIA_CLASS_READ

The ABAP code below is a full code listing to execute function module RCP341_OBJ_VIA_CLASS_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_et_result_keys  
 
 TYPE RCPTY_API_KEY
.


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

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

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

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

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

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

CALL FUNCTION 'RCP341_OBJ_VIA_CLASS_READ'
  EXPORTING
    i_valfrom =                  ld_i_valfrom
    i_valto =                    ld_i_valto
*   i_key_type_master_pob =      ld_i_key_type_master_pob
    i_estcat =                   ld_i_estcat
*   it_restriction_keys =        ld_it_restriction_keys
*   i_flg_pob_search =           ld_i_flg_pob_search
  IMPORTING
    et_result_keys =             ld_et_result_keys
  EXCEPTIONS
    INTERNAL_ERROR =             1
    .  "  RCP341_OBJ_VIA_CLASS_READ

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_et_result_keys
 
 TYPE RCPTY_API_KEY ,
ld_i_valfrom
 
 TYPE PVS_ADATUM ,
ld_i_valto
 
 TYPE PVS_BDATUM ,
ld_i_key_type_master_pob
 
 TYPE PVS_PNODE_TYPE ,
ld_i_estcat
 
 TYPE ESEESTCAT ,
ld_it_restriction_keys
 
 TYPE RCPTY_API_KEY ,
ld_i_flg_pob_search
 
 TYPE ESP1_BOOLEAN .


ld_i_valfrom = 'Check type of data required'.
ld_i_valto = 'Check type of data required'.
ld_i_key_type_master_pob = 'Check type of data required'.
ld_i_estcat = 'Check type of data required'.
ld_it_restriction_keys = 'Check type of data required'.
ld_i_flg_pob_search = 'Check type of data required'.