CACS_STDCTR_GET_FPB_DATA_RFC SAP Function module

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

Associated Function Group: CACS_STDCTR_TOOLS_RFC
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CACS_STDCTR_GET_FPB_DATA_RFC - CACS STDCTR GET FPB DATA RFC

CALL FUNCTION 'CACS_STDCTR_GET_FPB_DATA_RFC' "
  EXPORTING
*   id_perskeytp = 'U'          " fpb_keytp
*   id_perskey =                " fpb_key
    id_applid =                 " fpb_appid
*   id_with_ancestors = 'X'     " flag
*   id_subcontext =             " fpb_appsubcon
*   id_date = SY-DATUM          " datum
*   id_origin = SPACE           " char1
*   id_resolve =                " fpb_resolve_flag
*   id_convert_to_ext = 'X'     " flag
  IMPORTING
    et_fieldcat =               " fpb_t_fieldlist
    ev_appl =                   " cacsappl
    es_msg =                    " balmt
    .  "  CACS_STDCTR_GET_FPB_DATA_RFC

ABAP code example for Function Module CACS_STDCTR_GET_FPB_DATA_RFC

The ABAP code below is a full code listing to execute function module CACS_STDCTR_GET_FPB_DATA_RFC 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_fieldcat  
 
 TYPE FPB_T_FIELDLIST
,
ld_ev_appl  
 
 TYPE CACSAPPL
,
ld_es_msg  
 
 TYPE BALMT
.


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

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

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

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

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

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

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

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

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

CALL FUNCTION 'CACS_STDCTR_GET_FPB_DATA_RFC'
  EXPORTING
*   id_perskeytp =               ld_id_perskeytp
*   id_perskey =                 ld_id_perskey
    id_applid =                  ld_id_applid
*   id_with_ancestors =          ld_id_with_ancestors
*   id_subcontext =              ld_id_subcontext
*   id_date =                    ld_id_date
*   id_origin =                  ld_id_origin
*   id_resolve =                 ld_id_resolve
*   id_convert_to_ext =          ld_id_convert_to_ext
  IMPORTING
    et_fieldcat =                ld_et_fieldcat
    ev_appl =                    ld_ev_appl
    es_msg =                     ld_es_msg
    .  "  CACS_STDCTR_GET_FPB_DATA_RFC

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_et_fieldcat
 
 TYPE FPB_T_FIELDLIST ,
ld_id_perskeytp
 
 TYPE FPB_KEYTP ,
ld_ev_appl
 
 TYPE CACSAPPL ,
ld_id_perskey
 
 TYPE FPB_KEY ,
ld_es_msg
 
 TYPE BALMT ,
ld_id_applid
 
 TYPE FPB_APPID ,
ld_id_with_ancestors
 
 TYPE FLAG ,
ld_id_subcontext
 
 TYPE FPB_APPSUBCON ,
ld_id_date
 
 TYPE DATUM ,
ld_id_origin
 
 TYPE CHAR1 ,
ld_id_resolve
 
 TYPE FPB_RESOLVE_FLAG ,
ld_id_convert_to_ext
 
 TYPE FLAG .


ld_id_perskeytp = 'Check type of data required'.
ld_id_perskey = 'Check type of data required'.
ld_id_applid = 'Check type of data required'.
ld_id_with_ancestors = 'Check type of data required'.
ld_id_subcontext = 'Check type of data required'.
ld_id_date = 'Check type of data required'.
ld_id_origin = 'Check type of data required'.
ld_id_resolve = 'Check type of data required'.
ld_id_convert_to_ext = 'Check type of data required'.