SAP CNV_MBT_ULV_EVALUATE_MSG Function Module for ULV: Evaluate a message list

Search SAP Function Modules

CNV_MBT_ULV_EVALUATE_MSG is a standard cnv mbt ulv evaluate 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: Evaluate a message list 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 evaluate msg FM, simply by entering the name CNV_MBT_ULV_EVALUATE_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_EVALUATE_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_EVALUATE_MSG'"ULV: Evaluate a message list
  EXPORTING
   IT_MSG =  "List of BAL_S_MSG messages
*  I_NUMBER_OF_RECORDS = 0 "Number of records checked during message list has been created
*  I_FULLSCREEN = ' ' "Display messages in fullscreen mode
*  I_FOR_SAVE = ' ' "Check for Save-Operation
*  I_SAVE_WITH_ERRORS = ' ' "Allow also saving with errors
*  I_MSGTY_SLO = 'X' "Adapt messages types and problem class to SLO standard
*  I_EXPORT_OBJECT =  "Application log: Object name (Application code)
*  I_EXPORT_SUBOBJECT =  "Application log: sub-object

EXCEPTIONS
   ERRORS_IN_CHECK = 1    USER_ABORT = 2 

.

IMPORTING Parameters details for CNV_MBT_ULV_EVALUATE_MSG

IT_MSG - List of BAL_S_MSG messages

Data type: CNV_MBT_T_BAL_S_MSG
Optional: No
Call by Reference: Yes

I_NUMBER_OF_RECORDS - Number of records checked during message list has been created

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

I_FULLSCREEN - Display messages in fullscreen mode

Data type: ABAP_BOOL
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_FOR_SAVE - Check for Save-Operation

Data type: ABAP_BOOL
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_SAVE_WITH_ERRORS - Allow also saving with errors

Data type: ABAP_BOOL
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_MSGTY_SLO - Adapt messages types and problem class to SLO standard

Data type: ABAP_BOOL
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_EXPORT_OBJECT - Application log: Object name (Application code)

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

I_EXPORT_SUBOBJECT - Application log: sub-object

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

EXCEPTIONS details

ERRORS_IN_CHECK - Errors in passed message list

Data type:
Optional: No
Call by Reference: Yes

USER_ABORT - In save mode user has selected 'abort' due to warnings

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_MBT_ULV_EVALUATE_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.

ABAP code using 7.40 inline data declarations to call FM CNV_MBT_ULV_EVALUATE_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.

Search for further information about these or an SAP related objects