SAP RIB_UPDATE Function Module for

Search SAP Function Modules

RIB_UPDATE is a standard rib update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rib update FM, simply by entering the name RIB_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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

Function RIB_UPDATE 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 'RIB_UPDATE'"
  EXPORTING
   I_GJAHR =  "
   I_FIKRS =  "
   I_T_FMUDREL_ALL =  "
   I_T_FMUDPOOL_ALL =  "
   I_T_FMUDRULE_ALL =  "

CHANGING
*  C_F_CURRENT_ADDRESS =  "
*  C_F_CURRENT_SENDER =  "
   C_T_FMUDREL_DB =  "
   C_T_FMUDRULE_DB =  "
   C_T_FMUDPOOL_DB =  "
   C_F_FMUDRULE_ACTUAL =  "
   C_T_FMUDREL_ACTUAL =  "
   C_T_FMUDPOOL_ACTUAL =  "

EXCEPTIONS
   ACTION_SUCCESS = 1 

.

IMPORTING Parameters details for RIB_UPDATE

I_GJAHR -

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

I_FIKRS -

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

I_T_FMUDREL_ALL -

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

I_T_FMUDPOOL_ALL -

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

I_T_FMUDRULE_ALL -

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

CHANGING Parameters details for RIB_UPDATE

C_F_CURRENT_ADDRESS -

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

C_F_CURRENT_SENDER -

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

C_T_FMUDREL_DB -

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

C_T_FMUDRULE_DB -

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

C_T_FMUDPOOL_DB -

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

C_F_FMUDRULE_ACTUAL -

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

C_T_FMUDREL_ACTUAL -

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

C_T_FMUDPOOL_ACTUAL -

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

EXCEPTIONS details

ACTION_SUCCESS -

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

Copy and paste ABAP code example for RIB_UPDATE 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.

ABAP code using 7.40 inline data declarations to call FM RIB_UPDATE

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