SAP FMRB_DERI_RIB_OBJECT Function Module for Derive the RIB object
FMRB_DERI_RIB_OBJECT is a standard fmrb deri rib object 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 the RIB object 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 rib object FM, simply by entering the name FMRB_DERI_RIB_OBJECT 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_RIB_OBJECT 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_RIB_OBJECT'"Derive the RIB object.
EXPORTING
I_FM_AREA = "Financial Management Area
I_FISCYEAR = "Fiscal Year
I_RBBLDNR = "Budget Category for Revenue Increasing the Budget
I_BLDNR = "Budgeting ledger number
I_S_BUD_ADDRESS = "FM account assignment
* I_FLG_BYPASS_IDX = ' ' "Flag: Bypass index table
* I_STRATEGY_ID = 'RBOB' "Strategy ID
* I_ENV = 'SAP' "Environment for strategy
IMPORTING
E_S_ROBJECT = "FM account assignment
EXCEPTIONS
DERIVATION_FAILED = 1 INVALID_ROBJECT = 2 EXCLUDED_ADDRESS = 3
IMPORTING Parameters details for FMRB_DERI_RIB_OBJECT
I_FM_AREA - Financial Management Area
Data type: FIKRSOptional: No
Call by Reference: Yes
I_FISCYEAR - Fiscal Year
Data type: GJAHROptional: No
Call by Reference: Yes
I_RBBLDNR - Budget Category for Revenue Increasing the Budget
Data type: BURB_RBBLDNROptional: No
Call by Reference: Yes
I_BLDNR - Budgeting ledger number
Data type: BUBAS_BLDNROptional: No
Call by Reference: Yes
I_S_BUD_ADDRESS - FM account assignment
Data type: FMKU_S_DIMPARTOptional: No
Call by Reference: Yes
I_FLG_BYPASS_IDX - Flag: Bypass index table
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
I_STRATEGY_ID - Strategy ID
Data type: ABADRSTRATIDDefault: 'RBOB'
Optional: Yes
Call by Reference: Yes
I_ENV - Environment for strategy
Data type: ABADRENVDefault: 'SAP'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FMRB_DERI_RIB_OBJECT
E_S_ROBJECT - FM account assignment
Data type: FMKU_S_DIMPARTOptional: 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_ROBJECT - Derived RIB object is not valid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCLUDED_ADDRESS - Selected address is to be excluded from RIB
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMRB_DERI_RIB_OBJECT 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_robject | TYPE FMKU_S_DIMPART, " | |||
| lv_derivation_failed | TYPE FMKU_S_DIMPART, " | |||
| lv_i_fiscyear | TYPE GJAHR, " | |||
| lv_invalid_robject | TYPE GJAHR, " | |||
| lv_i_rbbldnr | TYPE BURB_RBBLDNR, " | |||
| lv_excluded_address | TYPE BURB_RBBLDNR, " | |||
| lv_i_bldnr | TYPE BUBAS_BLDNR, " | |||
| lv_i_s_bud_address | TYPE FMKU_S_DIMPART, " | |||
| lv_i_flg_bypass_idx | TYPE XFELD, " ' ' | |||
| lv_i_strategy_id | TYPE ABADRSTRATID, " 'RBOB' | |||
| lv_i_env | TYPE ABADRENV. " 'SAP' |
|   CALL FUNCTION 'FMRB_DERI_RIB_OBJECT' "Derive the RIB object |
| EXPORTING | ||
| I_FM_AREA | = lv_i_fm_area | |
| I_FISCYEAR | = lv_i_fiscyear | |
| I_RBBLDNR | = lv_i_rbbldnr | |
| I_BLDNR | = lv_i_bldnr | |
| I_S_BUD_ADDRESS | = lv_i_s_bud_address | |
| I_FLG_BYPASS_IDX | = lv_i_flg_bypass_idx | |
| I_STRATEGY_ID | = lv_i_strategy_id | |
| I_ENV | = lv_i_env | |
| IMPORTING | ||
| E_S_ROBJECT | = lv_e_s_robject | |
| EXCEPTIONS | ||
| DERIVATION_FAILED = 1 | ||
| INVALID_ROBJECT = 2 | ||
| EXCLUDED_ADDRESS = 3 | ||
| . " FMRB_DERI_RIB_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM FMRB_DERI_RIB_OBJECT
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_flg_bypass_idx) | = ' '. | |||
| DATA(ld_i_strategy_id) | = 'RBOB'. | |||
| DATA(ld_i_env) | = 'SAP'. | |||
Search for further information about these or an SAP related objects