SAP FM_RIB_PROTOCOL_DISPLAY Function Module for Display protocols of budget increase by RIB using ALV









FM_RIB_PROTOCOL_DISPLAY is a standard fm rib protocol display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display protocols of budget increase by RIB using ALV 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 protocol display FM, simply by entering the name FM_RIB_PROTOCOL_DISPLAY 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_PROTOCOL_DISPLAY 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_PROTOCOL_DISPLAY'"Display protocols of budget increase by RIB using ALV
EXPORTING
I_REPID = "
I_RIB_METHOD = "
I_FM_AREA = "
* I_SORT_BY_REV = 'X' "
I_FM_CURRENCY = "
I_TEST = "
I_MANUAL = "
* IT_EVENTS = "

TABLES
T_PROTOCOL = "
T_ERRORPROTOCOL = "
T_MESSAGES = "
T_BHDGD = "
.



IMPORTING Parameters details for FM_RIB_PROTOCOL_DISPLAY

I_REPID -

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

I_RIB_METHOD -

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

I_FM_AREA -

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

I_SORT_BY_REV -

Data type: FMDY-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FM_CURRENCY -

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

I_TEST -

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

I_MANUAL -

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

IT_EVENTS -

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

TABLES Parameters details for FM_RIB_PROTOCOL_DISPLAY

T_PROTOCOL -

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

T_ERRORPROTOCOL -

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

T_MESSAGES -

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

T_BHDGD -

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

Copy and paste ABAP code example for FM_RIB_PROTOCOL_DISPLAY 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_repid  TYPE SY-REPID, "   
lt_t_protocol  TYPE STANDARD TABLE OF FMUT_T_PROTOCOL, "   
lv_i_rib_method  TYPE FM01UD-UDMETHODE, "   
lt_t_errorprotocol  TYPE STANDARD TABLE OF FMUT_T_PROTOCOL, "   
lv_i_fm_area  TYPE FM01-FIKRS, "   
lt_t_messages  TYPE STANDARD TABLE OF BPAKRETURN, "   
lt_t_bhdgd  TYPE STANDARD TABLE OF BHDGD, "   
lv_i_sort_by_rev  TYPE FMDY-XFELD, "   'X'
lv_i_fm_currency  TYPE FM01-WAERS, "   
lv_i_test  TYPE FMDY-TESTMODE, "   
lv_i_manual  TYPE FMDY-XFELD, "   
lv_it_events  TYPE SLIS_T_EVENT. "   

  CALL FUNCTION 'FM_RIB_PROTOCOL_DISPLAY'  "Display protocols of budget increase by RIB using ALV
    EXPORTING
         I_REPID = lv_i_repid
         I_RIB_METHOD = lv_i_rib_method
         I_FM_AREA = lv_i_fm_area
         I_SORT_BY_REV = lv_i_sort_by_rev
         I_FM_CURRENCY = lv_i_fm_currency
         I_TEST = lv_i_test
         I_MANUAL = lv_i_manual
         IT_EVENTS = lv_it_events
    TABLES
         T_PROTOCOL = lt_t_protocol
         T_ERRORPROTOCOL = lt_t_errorprotocol
         T_MESSAGES = lt_t_messages
         T_BHDGD = lt_t_bhdgd
. " FM_RIB_PROTOCOL_DISPLAY




ABAP code using 7.40 inline data declarations to call FM FM_RIB_PROTOCOL_DISPLAY

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 REPID FROM SY INTO @DATA(ld_i_repid).
 
 
"SELECT single UDMETHODE FROM FM01UD INTO @DATA(ld_i_rib_method).
 
 
"SELECT single FIKRS FROM FM01 INTO @DATA(ld_i_fm_area).
 
 
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_sort_by_rev).
DATA(ld_i_sort_by_rev) = 'X'.
 
"SELECT single WAERS FROM FM01 INTO @DATA(ld_i_fm_currency).
 
"SELECT single TESTMODE FROM FMDY INTO @DATA(ld_i_test).
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_manual).
 
 


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!