SAP FMRB_READ_DOC_DISTRIB_BUDGET Function Module for Read distributed budget values from RIB documents
FMRB_READ_DOC_DISTRIB_BUDGET is a standard fmrb read doc distrib budget SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read distributed budget values from RIB documents 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 read doc distrib budget FM, simply by entering the name FMRB_READ_DOC_DISTRIB_BUDGET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMRB_EVALUATION
Program Name: SAPLFMRB_EVALUATION
Main Program: SAPLFMRB_EVALUATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMRB_READ_DOC_DISTRIB_BUDGET 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_READ_DOC_DISTRIB_BUDGET'"Read distributed budget values from RIB documents.
EXPORTING
I_FM_AREA = "Financial Management Area
I_FISCYEAR = "Fiscal Year
* I_CEFFYEAR = '0000' "Year of cash effectivity
* I_VERSION = '000' "Version
I_BLDNR = "Budgeting ledger number
I_S_SENDER_ADDRESS = "FM account assignment
I_T_RECEIVER_ADDRESSES = "Table with FM account assignments
IMPORTING
E_TOTAL_DISTRIBUTED = "Budget amount in local currency
TABLES
* E_T_FMBH = "Funds management budget header (entry documents)
* E_T_FMBL = "Funds management budget document lines (entry documents)
EXCEPTIONS
INVALID_COMMITMENT_ITEM = 1
IMPORTING Parameters details for FMRB_READ_DOC_DISTRIB_BUDGET
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_CEFFYEAR - Year of cash effectivity
Data type: GNJHRDefault: '0000'
Optional: No
Call by Reference: Yes
I_VERSION - Version
Data type: BUKU_VERSIONDefault: '000'
Optional: Yes
Call by Reference: Yes
I_BLDNR - Budgeting ledger number
Data type: BUBAS_BLDNROptional: No
Call by Reference: Yes
I_S_SENDER_ADDRESS - FM account assignment
Data type: FMKU_S_DIMPARTOptional: No
Call by Reference: Yes
I_T_RECEIVER_ADDRESSES - Table with FM account assignments
Data type: FMKU_T_DIMPARTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FMRB_READ_DOC_DISTRIB_BUDGET
E_TOTAL_DISTRIBUTED - Budget amount in local currency
Data type: LVALXX9Optional: No
Call by Reference: Yes
TABLES Parameters details for FMRB_READ_DOC_DISTRIB_BUDGET
E_T_FMBH - Funds management budget header (entry documents)
Data type: FMBHOptional: Yes
Call by Reference: Yes
E_T_FMBL - Funds management budget document lines (entry documents)
Data type: FMBLOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INVALID_COMMITMENT_ITEM - Commitment item category not supported
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FMRB_READ_DOC_DISTRIB_BUDGET 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: | ||||
| lt_e_t_fmbh | TYPE STANDARD TABLE OF FMBH, " | |||
| lv_i_fm_area | TYPE FIKRS, " | |||
| lv_e_total_distributed | TYPE LVALXX9, " | |||
| lv_invalid_commitment_item | TYPE LVALXX9, " | |||
| lt_e_t_fmbl | TYPE STANDARD TABLE OF FMBL, " | |||
| lv_i_fiscyear | TYPE GJAHR, " | |||
| lv_i_ceffyear | TYPE GNJHR, " '0000' | |||
| lv_i_version | TYPE BUKU_VERSION, " '000' | |||
| lv_i_bldnr | TYPE BUBAS_BLDNR, " | |||
| lv_i_s_sender_address | TYPE FMKU_S_DIMPART, " | |||
| lv_i_t_receiver_addresses | TYPE FMKU_T_DIMPART. " |
|   CALL FUNCTION 'FMRB_READ_DOC_DISTRIB_BUDGET' "Read distributed budget values from RIB documents |
| EXPORTING | ||
| I_FM_AREA | = lv_i_fm_area | |
| I_FISCYEAR | = lv_i_fiscyear | |
| I_CEFFYEAR | = lv_i_ceffyear | |
| I_VERSION | = lv_i_version | |
| I_BLDNR | = lv_i_bldnr | |
| I_S_SENDER_ADDRESS | = lv_i_s_sender_address | |
| I_T_RECEIVER_ADDRESSES | = lv_i_t_receiver_addresses | |
| IMPORTING | ||
| E_TOTAL_DISTRIBUTED | = lv_e_total_distributed | |
| TABLES | ||
| E_T_FMBH | = lt_e_t_fmbh | |
| E_T_FMBL | = lt_e_t_fmbl | |
| EXCEPTIONS | ||
| INVALID_COMMITMENT_ITEM = 1 | ||
| . " FMRB_READ_DOC_DISTRIB_BUDGET | ||
ABAP code using 7.40 inline data declarations to call FM FMRB_READ_DOC_DISTRIB_BUDGET
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_ceffyear) | = '0000'. | |||
| DATA(ld_i_version) | = '000'. | |||
Search for further information about these or an SAP related objects