SAP FMRB_CONVERT_RIB_RULE_TO_MSGVX Function Module for Condense FM account assignment into message variable(s)
FMRB_CONVERT_RIB_RULE_TO_MSGVX is a standard fmrb convert rib rule to msgvx SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Condense FM account assignment into message variable(s) 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 fmrb convert rib rule to msgvx FM, simply by entering the name FMRB_CONVERT_RIB_RULE_TO_MSGVX into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMBAS_ADDRESS
Program Name: SAPLFMBAS_ADDRESS
Main Program: SAPLFMBAS_ADDRESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMRB_CONVERT_RIB_RULE_TO_MSGVX 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 'FMRB_CONVERT_RIB_RULE_TO_MSGVX'"Condense FM account assignment into message variable(s).
EXPORTING
I_FM_AREA = "Financial Management Area
I_S_RIB_RULE = "RIB Rule (RIB Object/Cover Group)
* I_FLG_ADD_FM_AREA = ' ' "Flag: Include the FM area into the output
* I_FLG_ONLY_ONE_MSG_VAR = ' ' "Flag: Limit the output to only one message variable
* I_HEADING_CHARS = "Character(s) used as prefix for the output
* I_GET_DELIM_CHARS_ONLY = ' ' "Flag: Only return the characters used as delimiter
IMPORTING
E_MSGV1 = "Messages, message variables
E_MSGV2 = "Messages, message variables
E_DELIMITER_CHARS = "Delimiter characters used for the concatenation
E_FLG_REV_CVRGRP = "Flag: 'X' = RIB rule uses a revenue cover group
IMPORTING Parameters details for FMRB_CONVERT_RIB_RULE_TO_MSGVX
I_FM_AREA - Financial Management Area
Data type: FIKRSOptional: No
Call by Reference: Yes
I_S_RIB_RULE - RIB Rule (RIB Object/Cover Group)
Data type: FMRB_S_RIB_RULEOptional: No
Call by Reference: Yes
I_FLG_ADD_FM_AREA - Flag: Include the FM area into the output
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
I_FLG_ONLY_ONE_MSG_VAR - Flag: Limit the output to only one message variable
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
I_HEADING_CHARS - Character(s) used as prefix for the output
Data type: COptional: Yes
Call by Reference: Yes
I_GET_DELIM_CHARS_ONLY - Flag: Only return the characters used as delimiter
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FMRB_CONVERT_RIB_RULE_TO_MSGVX
E_MSGV1 - Messages, message variables
Data type: SYST-MSGV1Optional: No
Call by Reference: Yes
E_MSGV2 - Messages, message variables
Data type: SYST-MSGV1Optional: No
Call by Reference: Yes
E_DELIMITER_CHARS - Delimiter characters used for the concatenation
Data type: COptional: No
Call by Reference: Yes
E_FLG_REV_CVRGRP - Flag: 'X' = RIB rule uses a revenue cover group
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMRB_CONVERT_RIB_RULE_TO_MSGVX 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_e_msgv1 | TYPE SYST-MSGV1, " | |||
| lv_i_fm_area | TYPE FIKRS, " | |||
| lv_e_msgv2 | TYPE SYST-MSGV1, " | |||
| lv_i_s_rib_rule | TYPE FMRB_S_RIB_RULE, " | |||
| lv_e_delimiter_chars | TYPE C, " | |||
| lv_i_flg_add_fm_area | TYPE XFELD, " ' ' | |||
| lv_e_flg_rev_cvrgrp | TYPE XFELD, " | |||
| lv_i_flg_only_one_msg_var | TYPE XFELD, " ' ' | |||
| lv_i_heading_chars | TYPE C, " | |||
| lv_i_get_delim_chars_only | TYPE XFELD. " ' ' |
|   CALL FUNCTION 'FMRB_CONVERT_RIB_RULE_TO_MSGVX' "Condense FM account assignment into message variable(s) |
| EXPORTING | ||
| I_FM_AREA | = lv_i_fm_area | |
| I_S_RIB_RULE | = lv_i_s_rib_rule | |
| I_FLG_ADD_FM_AREA | = lv_i_flg_add_fm_area | |
| I_FLG_ONLY_ONE_MSG_VAR | = lv_i_flg_only_one_msg_var | |
| I_HEADING_CHARS | = lv_i_heading_chars | |
| I_GET_DELIM_CHARS_ONLY | = lv_i_get_delim_chars_only | |
| IMPORTING | ||
| E_MSGV1 | = lv_e_msgv1 | |
| E_MSGV2 | = lv_e_msgv2 | |
| E_DELIMITER_CHARS | = lv_e_delimiter_chars | |
| E_FLG_REV_CVRGRP | = lv_e_flg_rev_cvrgrp | |
| . " FMRB_CONVERT_RIB_RULE_TO_MSGVX | ||
ABAP code using 7.40 inline data declarations to call FM FMRB_CONVERT_RIB_RULE_TO_MSGVX
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 MSGV1 FROM SYST INTO @DATA(ld_e_msgv1). | ||||
| "SELECT single MSGV1 FROM SYST INTO @DATA(ld_e_msgv2). | ||||
| DATA(ld_i_flg_add_fm_area) | = ' '. | |||
| DATA(ld_i_flg_only_one_msg_var) | = ' '. | |||
| DATA(ld_i_get_delim_chars_only) | = ' '. | |||
Search for further information about these or an SAP related objects