SAP FMRB_DERI_NEW_RIB_RULE Function Module for Derive a proposal for RIB master data









FMRB_DERI_NEW_RIB_RULE is a standard fmrb deri new rib rule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Derive a proposal for RIB master data processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for fmrb deri new rib rule FM, simply by entering the name FMRB_DERI_NEW_RIB_RULE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMRB_CUST_TOOLS
Program Name: SAPLFMRB_CUST_TOOLS
Main Program: SAPLFMRB_CUST_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FMRB_DERI_NEW_RIB_RULE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'FMRB_DERI_NEW_RIB_RULE'"Derive a proposal for RIB master data
EXPORTING
I_FM_AREA = "Financial Management Area
I_FISCYEAR = "Fiscal Year
I_RBBLDNR = "Budget Category for Revenue Increasing the Budget
I_S_RIB_RULE = "RIB Rule (RIB Object/Cover Group)
* I_STRATEGY_ID = 'RBMD' "Strategy ID
* I_ENV = 'SAP' "Environment for strategy
* I_REF_CURRENCY = "Currency Key

IMPORTING
E_S_MASTER_DATA = "Deriving a Proposal for RIB Master Data: Target Fields

EXCEPTIONS
DERIVATION_FAILED = 1 INVALID_MASTER_DATA = 2 NO_RULE_ASSIGNED = 3
.



IMPORTING Parameters details for FMRB_DERI_NEW_RIB_RULE

I_FM_AREA - Financial Management Area

Data type: FIKRS
Optional: No
Call by Reference: Yes

I_FISCYEAR - Fiscal Year

Data type: GJAHR
Optional: No
Call by Reference: Yes

I_RBBLDNR - Budget Category for Revenue Increasing the Budget

Data type: BURB_RBBLDNR
Optional: No
Call by Reference: Yes

I_S_RIB_RULE - RIB Rule (RIB Object/Cover Group)

Data type: FMRB_S_RIB_RULE
Optional: No
Call by Reference: Yes

I_STRATEGY_ID - Strategy ID

Data type: ABADRSTRATID
Default: 'RBMD'
Optional: Yes
Call by Reference: Yes

I_ENV - Environment for strategy

Data type: ABADRENV
Default: 'SAP'
Optional: Yes
Call by Reference: Yes

I_REF_CURRENCY - Currency Key

Data type: WAERS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FMRB_DERI_NEW_RIB_RULE

E_S_MASTER_DATA - Deriving a Proposal for RIB Master Data: Target Fields

Data type: FMRB_S_RBMD_TARGET
Optional: No
Call by Reference: Yes

EXCEPTIONS details

DERIVATION_FAILED - Call of the derivation tool failed

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_MASTER_DATA - Derived RIB rule is not valid

Data type:
Optional: No
Call by Reference: Yes

NO_RULE_ASSIGNED - Derivation tool does not assign any rule

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMRB_DERI_NEW_RIB_RULE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_i_fm_area  TYPE FIKRS, "   
lv_e_s_master_data  TYPE FMRB_S_RBMD_TARGET, "   
lv_derivation_failed  TYPE FMRB_S_RBMD_TARGET, "   
lv_i_fiscyear  TYPE GJAHR, "   
lv_invalid_master_data  TYPE GJAHR, "   
lv_i_rbbldnr  TYPE BURB_RBBLDNR, "   
lv_no_rule_assigned  TYPE BURB_RBBLDNR, "   
lv_i_s_rib_rule  TYPE FMRB_S_RIB_RULE, "   
lv_i_strategy_id  TYPE ABADRSTRATID, "   'RBMD'
lv_i_env  TYPE ABADRENV, "   'SAP'
lv_i_ref_currency  TYPE WAERS. "   

  CALL FUNCTION 'FMRB_DERI_NEW_RIB_RULE'  "Derive a proposal for RIB master data
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_FISCYEAR = lv_i_fiscyear
         I_RBBLDNR = lv_i_rbbldnr
         I_S_RIB_RULE = lv_i_s_rib_rule
         I_STRATEGY_ID = lv_i_strategy_id
         I_ENV = lv_i_env
         I_REF_CURRENCY = lv_i_ref_currency
    IMPORTING
         E_S_MASTER_DATA = lv_e_s_master_data
    EXCEPTIONS
        DERIVATION_FAILED = 1
        INVALID_MASTER_DATA = 2
        NO_RULE_ASSIGNED = 3
. " FMRB_DERI_NEW_RIB_RULE




ABAP code using 7.40 inline data declarations to call FM FMRB_DERI_NEW_RIB_RULE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
DATA(ld_i_strategy_id) = 'RBMD'.
 
DATA(ld_i_env) = 'SAP'.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!