SAP CNV_MBT_MSG_CHECK_VALIDITY Function Module for Checks if the message is still valid or not









CNV_MBT_MSG_CHECK_VALIDITY is a standard cnv mbt msg check validity SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks if the message is still valid or not 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 msg check validity FM, simply by entering the name CNV_MBT_MSG_CHECK_VALIDITY into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNV_MBT_MSG
Program Name: SAPLCNV_MBT_MSG
Main Program: SAPLCNV_MBT_MSG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CNV_MBT_MSG_CHECK_VALIDITY 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_MSG_CHECK_VALIDITY'"Checks if the message is still valid or not
EXPORTING
P_PACKID = "Package Number to Specify CMIS and TDMS Packages
P_PNAME = "Character field of length 40

IMPORTING
EP_VALID = "Flag (X = yes, initial = no)
.



IMPORTING Parameters details for CNV_MBT_MSG_CHECK_VALIDITY

P_PACKID - Package Number to Specify CMIS and TDMS Packages

Data type: CNVMBTPACK-PACKID
Optional: No
Call by Reference: No ( called with pass by value option)

P_PNAME - Character field of length 40

Data type: CNVMBTPARAMS-PNAME
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CNV_MBT_MSG_CHECK_VALIDITY

EP_VALID - Flag (X = yes, initial = no)

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

Copy and paste ABAP code example for CNV_MBT_MSG_CHECK_VALIDITY 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_ep_valid  TYPE CNV_MBT_FLAG, "   
lv_p_packid  TYPE CNVMBTPACK-PACKID, "   
lv_p_pname  TYPE CNVMBTPARAMS-PNAME. "   

  CALL FUNCTION 'CNV_MBT_MSG_CHECK_VALIDITY'  "Checks if the message is still valid or not
    EXPORTING
         P_PACKID = lv_p_packid
         P_PNAME = lv_p_pname
    IMPORTING
         EP_VALID = lv_ep_valid
. " CNV_MBT_MSG_CHECK_VALIDITY




ABAP code using 7.40 inline data declarations to call FM CNV_MBT_MSG_CHECK_VALIDITY

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 PACKID FROM CNVMBTPACK INTO @DATA(ld_p_packid).
 
"SELECT single PNAME FROM CNVMBTPARAMS INTO @DATA(ld_p_pname).
 


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!