RCP963_GET_DATA_FOR_GUID SAP Function module

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

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

Pattern for FM RCP963_GET_DATA_FOR_GUID - RCP963 GET DATA FOR GUID

CALL FUNCTION 'RCP963_GET_DATA_FOR_GUID' "
  EXPORTING
*   i_obj_kind =                " rmsae_wbo_obj_kind
    i_guid =                    " pvs_pnguid
*   i_keydate = SY-DATUM        " sydatum
*   i_flg_with_txt =            " rmste_flag
*   i_flg_auth_f4 = SPACE       " flag
*   i_flg_language = SPACE      " flag
  IMPORTING
    e_subcat =                  " rcpe_subcat
    e_pname =                   " pvs_pnode
    e_txt =                     " pvs_pnodetx
    .  "  RCP963_GET_DATA_FOR_GUID

ABAP code example for Function Module RCP963_GET_DATA_FOR_GUID

The ABAP code below is a full code listing to execute function module RCP963_GET_DATA_FOR_GUID 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_subcat  
 
 TYPE RCPE_SUBCAT
,
ld_e_pname  
 
 TYPE PVS_PNODE
,
ld_e_txt  
 
 TYPE PVS_PNODETX
.


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

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

DATA(ld_i_keydate) = '20210129'.

DATA(ld_i_flg_with_txt) = '20210129'.

DATA(ld_i_flg_auth_f4) = '20210129'.

DATA(ld_i_flg_language) = '20210129'.
.

CALL FUNCTION 'RCP963_GET_DATA_FOR_GUID'
  EXPORTING
*   i_obj_kind =                 ld_i_obj_kind
    i_guid =                     ld_i_guid
*   i_keydate =                  ld_i_keydate
*   i_flg_with_txt =             ld_i_flg_with_txt
*   i_flg_auth_f4 =              ld_i_flg_auth_f4
*   i_flg_language =             ld_i_flg_language
  IMPORTING
    e_subcat =                   ld_e_subcat
    e_pname =                    ld_e_pname
    e_txt =                      ld_e_txt
    .  "  RCP963_GET_DATA_FOR_GUID

IF SY-SUBRC EQ 0.
  "All OK
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_subcat
 
 TYPE RCPE_SUBCAT ,
ld_i_obj_kind
 
 TYPE RMSAE_WBO_OBJ_KIND ,
ld_e_pname
 
 TYPE PVS_PNODE ,
ld_i_guid
 
 TYPE PVS_PNGUID ,
ld_e_txt
 
 TYPE PVS_PNODETX ,
ld_i_keydate
 
 TYPE SYDATUM ,
ld_i_flg_with_txt
 
 TYPE RMSTE_FLAG ,
ld_i_flg_auth_f4
 
 TYPE FLAG ,
ld_i_flg_language
 
 TYPE FLAG .


ld_i_obj_kind = '20210129'.
ld_i_guid = '20210129'.
ld_i_keydate = '20210129'.
ld_i_flg_with_txt = '20210129'.
ld_i_flg_auth_f4 = '20210129'.
ld_i_flg_language = '20210129'.