SAP FMTXT_DISPLAY_BM Function Module for Display Generated Budget Memo
FMTXT_DISPLAY_BM is a standard fmtxt display bm 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 Generated Budget Memo 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 fmtxt display bm FM, simply by entering the name FMTXT_DISPLAY_BM into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMTXT
Program Name: SAPLFMTXT
Main Program: SAPLFMTXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMTXT_DISPLAY_BM 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 'FMTXT_DISPLAY_BM'"Display Generated Budget Memo.
EXPORTING
* I_BM_TEMPLATE = "Template for Budget Texts
I_S_GENERATOR_PARAMS = "Importing Parameters for Budget Text (or Memo) Generator
* I_CVGRP = "Cover Group (only for automatic or manual cover groups!)
* I_RIB_LEDGER = "Budget Category for Revenue Increasing the Budget
* I_S_RIB_OBJECT = "RIB Object or RIB Source Address (for use with cover group)
* I_FLG_BYPASS_BUFFER = ' ' "Checkbox
* I_FLG_NO_HEADER = ' ' "Checkbox
IMPORTING
E_S_GENERATOR_EXP_PARAMS = "Exporting Parameters for Budget Text (or Memo) Generator
EXCEPTIONS
INVALID_COVER_GROUP = 1 INVALID_RIB_RULE = 2 MISSING_INPUT_PARAMETER = 3 INVALID_TEXT_STREAM = 4 ERROR_DIALOGBOX_CREATION = 5
IMPORTING Parameters details for FMTXT_DISPLAY_BM
I_BM_TEMPLATE - Template for Budget Texts
Data type: BUKU_TXTTEMPLOptional: Yes
Call by Reference: Yes
I_S_GENERATOR_PARAMS - Importing Parameters for Budget Text (or Memo) Generator
Data type: FMTXT_S_GENERATOR_IMP_PARAMSOptional: No
Call by Reference: Yes
I_CVGRP - Cover Group (only for automatic or manual cover groups!)
Data type: FMCE_CVRGRPOptional: Yes
Call by Reference: Yes
I_RIB_LEDGER - Budget Category for Revenue Increasing the Budget
Data type: BURB_RBBLDNROptional: Yes
Call by Reference: Yes
I_S_RIB_OBJECT - RIB Object or RIB Source Address (for use with cover group)
Data type: FMRB_S_RIB_OBJECTOptional: Yes
Call by Reference: Yes
I_FLG_BYPASS_BUFFER - Checkbox
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
I_FLG_NO_HEADER - Checkbox
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FMTXT_DISPLAY_BM
E_S_GENERATOR_EXP_PARAMS - Exporting Parameters for Budget Text (or Memo) Generator
Data type: FMTXT_S_GENERATOR_EXP_PARAMSOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_COVER_GROUP - Invalid Cover Group
Data type:Optional: No
Call by Reference: Yes
INVALID_RIB_RULE - Invalid RIB Rule
Data type:Optional: No
Call by Reference: Yes
MISSING_INPUT_PARAMETER - Missing Input Parameter
Data type:Optional: No
Call by Reference: Yes
INVALID_TEXT_STREAM - Invalid Text Stream sent to the Textedit Control
Data type:Optional: No
Call by Reference: Yes
ERROR_DIALOGBOX_CREATION - Error in Dialogbox Creation
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMTXT_DISPLAY_BM 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_bm_template | TYPE BUKU_TXTTEMPL, " | |||
| lv_invalid_cover_group | TYPE BUKU_TXTTEMPL, " | |||
| lv_e_s_generator_exp_params | TYPE FMTXT_S_GENERATOR_EXP_PARAMS, " | |||
| lv_invalid_rib_rule | TYPE FMTXT_S_GENERATOR_EXP_PARAMS, " | |||
| lv_i_s_generator_params | TYPE FMTXT_S_GENERATOR_IMP_PARAMS, " | |||
| lv_i_cvgrp | TYPE FMCE_CVRGRP, " | |||
| lv_missing_input_parameter | TYPE FMCE_CVRGRP, " | |||
| lv_i_rib_ledger | TYPE BURB_RBBLDNR, " | |||
| lv_invalid_text_stream | TYPE BURB_RBBLDNR, " | |||
| lv_i_s_rib_object | TYPE FMRB_S_RIB_OBJECT, " | |||
| lv_error_dialogbox_creation | TYPE FMRB_S_RIB_OBJECT, " | |||
| lv_i_flg_bypass_buffer | TYPE XFELD, " ' ' | |||
| lv_i_flg_no_header | TYPE XFELD. " ' ' |
|   CALL FUNCTION 'FMTXT_DISPLAY_BM' "Display Generated Budget Memo |
| EXPORTING | ||
| I_BM_TEMPLATE | = lv_i_bm_template | |
| I_S_GENERATOR_PARAMS | = lv_i_s_generator_params | |
| I_CVGRP | = lv_i_cvgrp | |
| I_RIB_LEDGER | = lv_i_rib_ledger | |
| I_S_RIB_OBJECT | = lv_i_s_rib_object | |
| I_FLG_BYPASS_BUFFER | = lv_i_flg_bypass_buffer | |
| I_FLG_NO_HEADER | = lv_i_flg_no_header | |
| IMPORTING | ||
| E_S_GENERATOR_EXP_PARAMS | = lv_e_s_generator_exp_params | |
| EXCEPTIONS | ||
| INVALID_COVER_GROUP = 1 | ||
| INVALID_RIB_RULE = 2 | ||
| MISSING_INPUT_PARAMETER = 3 | ||
| INVALID_TEXT_STREAM = 4 | ||
| ERROR_DIALOGBOX_CREATION = 5 | ||
| . " FMTXT_DISPLAY_BM | ||
ABAP code using 7.40 inline data declarations to call FM FMTXT_DISPLAY_BM
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.| DATA(ld_i_flg_bypass_buffer) | = ' '. | |||
| DATA(ld_i_flg_no_header) | = ' '. | |||
Search for further information about these or an SAP related objects