FERC_MASTER_DATA_UPDATE SAP Function module - IS-U/FERC: Update FERC master data information on CO objects

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

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

Pattern for FM FERC_MASTER_DATA_UPDATE - FERC MASTER DATA UPDATE

CALL FUNCTION 'FERC_MASTER_DATA_UPDATE' "IS-U/FERC: Update FERC master data information on CO objects
  EXPORTING
    run_id =                    " fe_run_id     Regulatory reporting run identification number
    object_number =             " j_objnr       Object number
*   clearing_object =           " fe_clrg_obj   Flag: CO object treated as clearing object
*   clearing_group =            " fe_cobj_cat   Clearing group
*   paths =                     " fe_paths      Number of paths starting from a sender object
*   regulatory_indicator =      " fe_ind        Regulatory indicator
  EXCEPTIONS
    PARAMETERS_NOT_INITIALIZED = 1  "
    .  "  FERC_MASTER_DATA_UPDATE

ABAP code example for Function Module FERC_MASTER_DATA_UPDATE

The ABAP code below is a full code listing to execute function module FERC_MASTER_DATA_UPDATE 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_run_id) = 'Check type of data required'.

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

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

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

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

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

CALL FUNCTION 'FERC_MASTER_DATA_UPDATE'
  EXPORTING
    run_id =                     ld_run_id
    object_number =              ld_object_number
*   clearing_object =            ld_clearing_object
*   clearing_group =             ld_clearing_group
*   paths =                      ld_paths
*   regulatory_indicator =       ld_regulatory_indicator
  EXCEPTIONS
    PARAMETERS_NOT_INITIALIZED =    1
    .  "  FERC_MASTER_DATA_UPDATE

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_run_id
 
 TYPE FE_RUN_ID ,
ld_object_number
 
 TYPE J_OBJNR ,
ld_clearing_object
 
 TYPE FE_CLRG_OBJ ,
ld_clearing_group
 
 TYPE FE_COBJ_CAT ,
ld_paths
 
 TYPE FE_PATHS ,
ld_regulatory_indicator
 
 TYPE FE_IND .


ld_run_id = 'Check type of data required'.
ld_object_number = 'Check type of data required'.
ld_clearing_object = 'Check type of data required'.
ld_clearing_group = 'Check type of data required'.
ld_paths = 'Check type of data required'.
ld_regulatory_indicator = 'Check type of data required'.