SAP RIB_INIT_FROM_MEMORY Function Module for









RIB_INIT_FROM_MEMORY is a standard rib init from memory 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 init from memory FM, simply by entering the name RIB_INIT_FROM_MEMORY 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_INIT_FROM_MEMORY 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_INIT_FROM_MEMORY'"
EXPORTING
* IP_F_FMAA_INT = "
* IP_FLG_BDGTMEM = "
* IP_FLG_INCR_EVNT = "
* IP_FLG_PAY_INTVS = "
* IP_FLG_COM_INTVS = "
* IP_FLG_SURPL = "
* IP_FLG_INCHECK = "
IP_GJAHR = "
IP_FIKRS = "
* IP_FLG_REVN_POOL = "
* IP_F_REVN_POOL = "
* IP_FLG_ALL = "
* IP_FLG_CNTRL = "
* IP_FLG_RECVS = "
* IP_FLG_POOLS = "
.



IMPORTING Parameters details for RIB_INIT_FROM_MEMORY

IP_F_FMAA_INT -

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

IP_FLG_BDGTMEM -

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

IP_FLG_INCR_EVNT -

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

IP_FLG_PAY_INTVS -

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

IP_FLG_COM_INTVS -

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

IP_FLG_SURPL -

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

IP_FLG_INCHECK -

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

IP_GJAHR -

Data type: FM01UD-GJAHR
Optional: No
Call by Reference: Yes

IP_FIKRS -

Data type: FM01UD-FIKRS
Optional: No
Call by Reference: Yes

IP_FLG_REVN_POOL -

Data type:
Optional: Yes
Call by Reference: Yes

IP_F_REVN_POOL -

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

IP_FLG_ALL -

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

IP_FLG_CNTRL -

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

IP_FLG_RECVS -

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

IP_FLG_POOLS -

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

Copy and paste ABAP code example for RIB_INIT_FROM_MEMORY 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_f_fmaa_int  TYPE FMKT_FMAA_INT, "   
lv_ip_flg_bdgtmem  TYPE FMKT_FMAA_INT, "   
lv_ip_flg_incr_evnt  TYPE FMKT_FMAA_INT, "   
lv_ip_flg_pay_intvs  TYPE FMKT_FMAA_INT, "   
lv_ip_flg_com_intvs  TYPE FMKT_FMAA_INT, "   
lv_ip_flg_surpl  TYPE FMKT_FMAA_INT, "   
lv_ip_flg_incheck  TYPE FMKT_FMAA_INT, "   
lv_ip_gjahr  TYPE FM01UD-GJAHR, "   
lv_ip_fikrs  TYPE FM01UD-FIKRS, "   
lv_ip_flg_revn_pool  TYPE FM01UD, "   
lv_ip_f_revn_pool  TYPE FMKT_POOL_INT, "   
lv_ip_flg_all  TYPE FMKT_POOL_INT, "   
lv_ip_flg_cntrl  TYPE FMKT_POOL_INT, "   
lv_ip_flg_recvs  TYPE FMKT_POOL_INT, "   
lv_ip_flg_pools  TYPE FMKT_POOL_INT. "   

  CALL FUNCTION 'RIB_INIT_FROM_MEMORY'  "
    EXPORTING
         IP_F_FMAA_INT = lv_ip_f_fmaa_int
         IP_FLG_BDGTMEM = lv_ip_flg_bdgtmem
         IP_FLG_INCR_EVNT = lv_ip_flg_incr_evnt
         IP_FLG_PAY_INTVS = lv_ip_flg_pay_intvs
         IP_FLG_COM_INTVS = lv_ip_flg_com_intvs
         IP_FLG_SURPL = lv_ip_flg_surpl
         IP_FLG_INCHECK = lv_ip_flg_incheck
         IP_GJAHR = lv_ip_gjahr
         IP_FIKRS = lv_ip_fikrs
         IP_FLG_REVN_POOL = lv_ip_flg_revn_pool
         IP_F_REVN_POOL = lv_ip_f_revn_pool
         IP_FLG_ALL = lv_ip_flg_all
         IP_FLG_CNTRL = lv_ip_flg_cntrl
         IP_FLG_RECVS = lv_ip_flg_recvs
         IP_FLG_POOLS = lv_ip_flg_pools
. " RIB_INIT_FROM_MEMORY




ABAP code using 7.40 inline data declarations to call FM RIB_INIT_FROM_MEMORY

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 GJAHR FROM FM01UD INTO @DATA(ld_ip_gjahr).
 
"SELECT single FIKRS FROM FM01UD INTO @DATA(ld_ip_fikrs).
 
 
 
 
 
 
 


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!