SAP FM_RIB_CUSTOMIZING_DETERMINE Function Module for Determine the customizing for Revenue Increasing the Budget
FM_RIB_CUSTOMIZING_DETERMINE is a standard fm rib customizing determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine the customizing for Revenue Increasing the Budget 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 fm rib customizing determine FM, simply by entering the name FM_RIB_CUSTOMIZING_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMUT
Program Name: SAPLFMUT
Main Program: SAPLFMUT
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_RIB_CUSTOMIZING_DETERMINE 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 'FM_RIB_CUSTOMIZING_DETERMINE'"Determine the customizing for Revenue Increasing the Budget.
EXPORTING
IP_FIKRS = "
IP_GJAHR = "
IMPORTING
OP_FLG_EU_ACTIV = "
OP_F_FM01UD = "
OP_F_FMUP01_54 = "
OP_F_FMUP01_57 = "
OP_F_FMUP01_83 = "
OP_F_LEDGER = "
OP_WAERS = "
OP_FLG_KOM_ACTIV = "Indicator: Local authorities active
EXCEPTIONS
PROFIL_INCONSISTENT = 1 DATA_NOT_FOUND = 2
IMPORTING Parameters details for FM_RIB_CUSTOMIZING_DETERMINE
IP_FIKRS -
Data type: FM01-FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
IP_GJAHR -
Data type: FMUDRULE-GJAHROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FM_RIB_CUSTOMIZING_DETERMINE
OP_FLG_EU_ACTIV -
Data type: FMISPS-EU_ACTIVEOptional: No
Call by Reference: No ( called with pass by value option)
OP_F_FM01UD -
Data type: FM01UDOptional: No
Call by Reference: No ( called with pass by value option)
OP_F_FMUP01_54 -
Data type: FMUP01Optional: No
Call by Reference: No ( called with pass by value option)
OP_F_FMUP01_57 -
Data type: FMUP01Optional: No
Call by Reference: No ( called with pass by value option)
OP_F_FMUP01_83 -
Data type: FMUP01Optional: No
Call by Reference: No ( called with pass by value option)
OP_F_LEDGER -
Data type: FMUT_LEDGEROptional: No
Call by Reference: No ( called with pass by value option)
OP_WAERS -
Data type: FM01-WAERSOptional: No
Call by Reference: No ( called with pass by value option)
OP_FLG_KOM_ACTIV - Indicator: Local authorities active
Data type: FMISPS-KOM_ACTIVEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PROFIL_INCONSISTENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_RIB_CUSTOMIZING_DETERMINE 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_ip_fikrs | TYPE FM01-FIKRS, " | |||
| lv_op_flg_eu_activ | TYPE FMISPS-EU_ACTIVE, " | |||
| lv_profil_inconsistent | TYPE FMISPS, " | |||
| lv_ip_gjahr | TYPE FMUDRULE-GJAHR, " | |||
| lv_op_f_fm01ud | TYPE FM01UD, " | |||
| lv_data_not_found | TYPE FM01UD, " | |||
| lv_op_f_fmup01_54 | TYPE FMUP01, " | |||
| lv_op_f_fmup01_57 | TYPE FMUP01, " | |||
| lv_op_f_fmup01_83 | TYPE FMUP01, " | |||
| lv_op_f_ledger | TYPE FMUT_LEDGER, " | |||
| lv_op_waers | TYPE FM01-WAERS, " | |||
| lv_op_flg_kom_activ | TYPE FMISPS-KOM_ACTIVE. " |
|   CALL FUNCTION 'FM_RIB_CUSTOMIZING_DETERMINE' "Determine the customizing for Revenue Increasing the Budget |
| EXPORTING | ||
| IP_FIKRS | = lv_ip_fikrs | |
| IP_GJAHR | = lv_ip_gjahr | |
| IMPORTING | ||
| OP_FLG_EU_ACTIV | = lv_op_flg_eu_activ | |
| OP_F_FM01UD | = lv_op_f_fm01ud | |
| OP_F_FMUP01_54 | = lv_op_f_fmup01_54 | |
| OP_F_FMUP01_57 | = lv_op_f_fmup01_57 | |
| OP_F_FMUP01_83 | = lv_op_f_fmup01_83 | |
| OP_F_LEDGER | = lv_op_f_ledger | |
| OP_WAERS | = lv_op_waers | |
| OP_FLG_KOM_ACTIV | = lv_op_flg_kom_activ | |
| EXCEPTIONS | ||
| PROFIL_INCONSISTENT = 1 | ||
| DATA_NOT_FOUND = 2 | ||
| . " FM_RIB_CUSTOMIZING_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM FM_RIB_CUSTOMIZING_DETERMINE
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.| "SELECT single FIKRS FROM FM01 INTO @DATA(ld_ip_fikrs). | ||||
| "SELECT single EU_ACTIVE FROM FMISPS INTO @DATA(ld_op_flg_eu_activ). | ||||
| "SELECT single GJAHR FROM FMUDRULE INTO @DATA(ld_ip_gjahr). | ||||
| "SELECT single WAERS FROM FM01 INTO @DATA(ld_op_waers). | ||||
| "SELECT single KOM_ACTIVE FROM FMISPS INTO @DATA(ld_op_flg_kom_activ). | ||||
Search for further information about these or an SAP related objects