SAP CNV_MBT_DEV_AUTHORITY_CHECK Function Module for MBT PCL authority check









CNV_MBT_DEV_AUTHORITY_CHECK is a standard cnv mbt dev authority check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MBT PCL authority check 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 dev authority check FM, simply by entering the name CNV_MBT_DEV_AUTHORITY_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNV_MBT_AUTH
Program Name: SAPLCNV_MBT_AUTH
Main Program: SAPLCNV_MBT_AUTH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CNV_MBT_DEV_AUTHORITY_CHECK 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_DEV_AUTHORITY_CHECK'"MBT PCL authority check
EXPORTING
* IM_AREA = "
* IM_MSGV3 = "
* IM_MSGV4 = "
* IM_NAMSP = "MBT PCL Development Namespace
* IM_PACKID = "Package Number to Specify CMIS and TDMS Packages
IM_ACTIVITY = "
* IM_MSGTY = "
* IM_MSGID = "
* IM_MSGNO = "
* IM_MSGV1 = "
* IM_MSGV2 = "

EXCEPTIONS
NO_AUTHORITY = 1
.



IMPORTING Parameters details for CNV_MBT_DEV_AUTHORITY_CHECK

IM_AREA -

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

IM_MSGV3 -

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

IM_MSGV4 -

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

IM_NAMSP - MBT PCL Development Namespace

Data type: CNVMBTNAMSP-NAMSP
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_PACKID - Package Number to Specify CMIS and TDMS Packages

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

IM_ACTIVITY -

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

IM_MSGTY -

Data type: BALMI-MSGTY
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_MSGID -

Data type: BALMI-MSGID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_MSGNO -

Data type: BALMI-MSGNO
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_MSGV1 -

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

IM_MSGV2 -

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

EXCEPTIONS details

NO_AUTHORITY -

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

Copy and paste ABAP code example for CNV_MBT_DEV_AUTHORITY_CHECK 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_im_area  TYPE CNVMBTPACK-SCENARIO, "   
lv_no_authority  TYPE CNVMBTPACK, "   
lv_im_msgv3  TYPE CNVMBTPACK, "   
lv_im_msgv4  TYPE CNVMBTPACK, "   
lv_im_namsp  TYPE CNVMBTNAMSP-NAMSP, "   
lv_im_packid  TYPE CNVMBTPACK-PACKID, "   
lv_im_activity  TYPE CNVMBTPACK, "   
lv_im_msgty  TYPE BALMI-MSGTY, "   
lv_im_msgid  TYPE BALMI-MSGID, "   
lv_im_msgno  TYPE BALMI-MSGNO, "   
lv_im_msgv1  TYPE BALMI, "   
lv_im_msgv2  TYPE BALMI. "   

  CALL FUNCTION 'CNV_MBT_DEV_AUTHORITY_CHECK'  "MBT PCL authority check
    EXPORTING
         IM_AREA = lv_im_area
         IM_MSGV3 = lv_im_msgv3
         IM_MSGV4 = lv_im_msgv4
         IM_NAMSP = lv_im_namsp
         IM_PACKID = lv_im_packid
         IM_ACTIVITY = lv_im_activity
         IM_MSGTY = lv_im_msgty
         IM_MSGID = lv_im_msgid
         IM_MSGNO = lv_im_msgno
         IM_MSGV1 = lv_im_msgv1
         IM_MSGV2 = lv_im_msgv2
    EXCEPTIONS
        NO_AUTHORITY = 1
. " CNV_MBT_DEV_AUTHORITY_CHECK




ABAP code using 7.40 inline data declarations to call FM CNV_MBT_DEV_AUTHORITY_CHECK

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 SCENARIO FROM CNVMBTPACK INTO @DATA(ld_im_area).
 
 
 
 
"SELECT single NAMSP FROM CNVMBTNAMSP INTO @DATA(ld_im_namsp).
 
"SELECT single PACKID FROM CNVMBTPACK INTO @DATA(ld_im_packid).
 
 
"SELECT single MSGTY FROM BALMI INTO @DATA(ld_im_msgty).
 
"SELECT single MSGID FROM BALMI INTO @DATA(ld_im_msgid).
 
"SELECT single MSGNO FROM BALMI INTO @DATA(ld_im_msgno).
 
 
 


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!