SAP FMCU_GET_ROLLUP_RECEIVER Function Module for Get receiver according to transfer rules









FMCU_GET_ROLLUP_RECEIVER is a standard fmcu get rollup receiver SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get receiver according to transfer rules 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 fmcu get rollup receiver FM, simply by entering the name FMCU_GET_ROLLUP_RECEIVER into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCU_GET_ROLLUP_RECEIVER 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 'FMCU_GET_ROLLUP_RECEIVER'"Get receiver according to transfer rules
  EXPORTING
   I_FM_AREA =  "Financial Management Area
   I_F_DIMPART =  "FM account assignment
   I_BUDTYPE =  "Budget Type
   I_VALTYPE =  "Value Type
   I_FYEAR =  "Fiscal Year

 IMPORTING
   E_F_DIMPART =  "Table with FM account  assignments
   E_BUDTYPE =  "Budget Type

EXCEPTIONS
   NO_RULE = 1    MASTER_DATA_ERROR = 2    FUND_STATUS_ERROR = 3
.



IMPORTING Parameters details for FMCU_GET_ROLLUP_RECEIVER

I_FM_AREA - Financial Management Area

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

I_F_DIMPART - FM account assignment

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

I_BUDTYPE - Budget Type

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

I_VALTYPE - Value Type

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

I_FYEAR - Fiscal Year

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

EXPORTING Parameters details for FMCU_GET_ROLLUP_RECEIVER

E_F_DIMPART - Table with FM account assignments

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

E_BUDTYPE - Budget Type

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

EXCEPTIONS details

NO_RULE - No rules for rollup

Data type:
Optional: No
Call by Reference: Yes

MASTER_DATA_ERROR - Error when accessing master data

Data type:
Optional: No
Call by Reference: Yes

FUND_STATUS_ERROR - Error when determining fund status

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMCU_GET_ROLLUP_RECEIVER 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_no_rule  TYPE STRING, "   
lv_i_fm_area  TYPE FIKRS, "   
lv_e_f_dimpart  TYPE FMKU_S_DIMPART, "   
lv_e_budtype  TYPE BUKU_BUDTYPE, "   
lv_i_f_dimpart  TYPE FMKU_S_DIMPART, "   
lv_master_data_error  TYPE FMKU_S_DIMPART, "   
lv_i_budtype  TYPE BUKU_BUDTYPE, "   
lv_fund_status_error  TYPE BUKU_BUDTYPE, "   
lv_i_valtype  TYPE BUKU_VALTYPE, "   
lv_i_fyear  TYPE GJAHR. "   

  CALL FUNCTION 'FMCU_GET_ROLLUP_RECEIVER'  "Get receiver according to transfer rules
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_F_DIMPART = lv_i_f_dimpart
         I_BUDTYPE = lv_i_budtype
         I_VALTYPE = lv_i_valtype
         I_FYEAR = lv_i_fyear
    IMPORTING
         E_F_DIMPART = lv_e_f_dimpart
         E_BUDTYPE = lv_e_budtype
    EXCEPTIONS
        NO_RULE = 1
        MASTER_DATA_ERROR = 2
        FUND_STATUS_ERROR = 3
. " FMCU_GET_ROLLUP_RECEIVER




ABAP code using 7.40 inline data declarations to call FM FMCU_GET_ROLLUP_RECEIVER

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.

 
 
 
 
 
 
 
 
 
 


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!