SAP CNV_MBT_ULV_DISPLAY_MSG Function Module for ULV: Display messages
CNV_MBT_ULV_DISPLAY_MSG is a standard cnv mbt ulv display msg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ULV: Display messages 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 cnv mbt ulv display msg FM, simply by entering the name CNV_MBT_ULV_DISPLAY_MSG into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_MBT_ULV
Program Name: SAPLCNV_MBT_ULV
Main Program: SAPLCNV_MBT_ULV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CNV_MBT_ULV_DISPLAY_MSG 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 'CNV_MBT_ULV_DISPLAY_MSG'"ULV: Display messages.
EXPORTING
* IS_MSG = "Application Log: Message Data
* I_EXPORT_SUBOBJECT = "Application log: sub-object
* I_DISPLAY_SETTINGS = "ULV logger default settings
* I_NO_TOOLBAR = ' ' "Do not show toolbar
* IR_CONTAINER = "External custom containerto display messages
* IT_MSG = "List of BAL_S_MSG messages
* I_MSGTY_SLO = 'X' "Adapt messages types and problem class to SLO standard
* I_FULLSCREEN = ' ' "Display messages in fullscreen mode
* I_LOGNUMBER = "Application log: log number
* I_OBJECT = "Application log: Object name (Application code)
* I_SUBOBJECT = "Application log: sub-object
* I_EXTNUMBER = "Application Log: External ID
* I_EXPORT_OBJECT = "Application log: Object name (Application code)
IMPORTING Parameters details for CNV_MBT_ULV_DISPLAY_MSG
IS_MSG - Application Log: Message Data
Data type: BAL_S_MSGOptional: Yes
Call by Reference: Yes
I_EXPORT_SUBOBJECT - Application log: sub-object
Data type: BALSUBOBJOptional: Yes
Call by Reference: Yes
I_DISPLAY_SETTINGS - ULV logger default settings
Data type: CNV_MBT_ULV_LOG_DISP_SETTINGSOptional: Yes
Call by Reference: Yes
I_NO_TOOLBAR - Do not show toolbar
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
IR_CONTAINER - External custom containerto display messages
Data type: CL_GUI_CONTAINEROptional: Yes
Call by Reference: Yes
IT_MSG - List of BAL_S_MSG messages
Data type: CNV_MBT_T_BAL_S_MSGOptional: Yes
Call by Reference: Yes
I_MSGTY_SLO - Adapt messages types and problem class to SLO standard
Data type: ABAP_BOOLDefault: 'X'
Optional: Yes
Call by Reference: Yes
I_FULLSCREEN - Display messages in fullscreen mode
Data type: ABAP_BOOLDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_LOGNUMBER - Application log: log number
Data type: BALOGNROptional: Yes
Call by Reference: Yes
I_OBJECT - Application log: Object name (Application code)
Data type: BALOBJ_DOptional: Yes
Call by Reference: Yes
I_SUBOBJECT - Application log: sub-object
Data type: BALSUBOBJOptional: Yes
Call by Reference: Yes
I_EXTNUMBER - Application Log: External ID
Data type: BALNREXTOptional: Yes
Call by Reference: Yes
I_EXPORT_OBJECT - Application log: Object name (Application code)
Data type: BALOBJ_DOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_ULV_DISPLAY_MSG 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_is_msg | TYPE BAL_S_MSG, " | |||
| lv_i_export_subobject | TYPE BALSUBOBJ, " | |||
| lv_i_display_settings | TYPE CNV_MBT_ULV_LOG_DISP_SETTINGS, " | |||
| lv_i_no_toolbar | TYPE FLAG, " SPACE | |||
| lv_ir_container | TYPE CL_GUI_CONTAINER, " | |||
| lv_it_msg | TYPE CNV_MBT_T_BAL_S_MSG, " | |||
| lv_i_msgty_slo | TYPE ABAP_BOOL, " 'X' | |||
| lv_i_fullscreen | TYPE ABAP_BOOL, " SPACE | |||
| lv_i_lognumber | TYPE BALOGNR, " | |||
| lv_i_object | TYPE BALOBJ_D, " | |||
| lv_i_subobject | TYPE BALSUBOBJ, " | |||
| lv_i_extnumber | TYPE BALNREXT, " | |||
| lv_i_export_object | TYPE BALOBJ_D. " |
| CALL FUNCTION 'CNV_MBT_ULV_DISPLAY_MSG' "ULV: Display messages |
| EXPORTING | ||
| IS_MSG | = lv_is_msg | |
| I_EXPORT_SUBOBJECT | = lv_i_export_subobject | |
| I_DISPLAY_SETTINGS | = lv_i_display_settings | |
| I_NO_TOOLBAR | = lv_i_no_toolbar | |
| IR_CONTAINER | = lv_ir_container | |
| IT_MSG | = lv_it_msg | |
| I_MSGTY_SLO | = lv_i_msgty_slo | |
| I_FULLSCREEN | = lv_i_fullscreen | |
| I_LOGNUMBER | = lv_i_lognumber | |
| I_OBJECT | = lv_i_object | |
| I_SUBOBJECT | = lv_i_subobject | |
| I_EXTNUMBER | = lv_i_extnumber | |
| I_EXPORT_OBJECT | = lv_i_export_object | |
| . " CNV_MBT_ULV_DISPLAY_MSG | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_ULV_DISPLAY_MSG
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_no_toolbar) | = ' '. | |||
| DATA(ld_i_msgty_slo) | = 'X'. | |||
| DATA(ld_i_fullscreen) | = ' '. | |||
Search for further information about these or an SAP related objects