SAP CNV_MBT_PDV_AUTHORITY_CHECK Function Module for DMIS Authority check for Development of Portfolio and Project Objects

Search SAP Function Modules

CNV_MBT_PDV_AUTHORITY_CHECK is a standard cnv mbt pdv 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 DMIS Authority check for Development of Portfolio and Project Objects 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 pdv authority check FM, simply by entering the name CNV_MBT_PDV_AUTHORITY_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_MBT_PDV_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_PDV_AUTHORITY_CHECK'"DMIS Authority check for Development of Portfolio and Project Objects
  EXPORTING
*  IM_AREA =  "MBT PCL: Scenario
*  IM_MSGV2 =  "Message Variable
*  IM_MSGV3 =  "Message Variable
*  IM_MSGV4 =  "Message Variable
   IM_OBJECTTYPE =  "BTP Technical Object Type
*  IM_OBJECTNAME =  "BTP Technical Object Name
   IM_NAME' ' =  "BTP Object Namespace
   IM_ACTIVITY =  "Activity
*  IM_MSGTY =  "Message Type
*  IM_MSGID =  "Message Class
*  IM_MSGNO =  "Message Number
*  IM_MSGV1 =  "Message Variable

EXCEPTIONS
   NO_AUTHORITY = 1    INVALID_CALL = 2 

.

IMPORTING Parameters details for CNV_MBT_PDV_AUTHORITY_CHECK

IM_AREA - MBT PCL: Scenario

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

IM_MSGV2 - Message Variable

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

IM_MSGV3 - Message Variable

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

IM_MSGV4 - Message Variable

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

IM_OBJECTTYPE - BTP Technical Object Type

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

IM_OBJECTNAME - BTP Technical Object Name

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

IM_NAMESPACE - BTP Object Namespace

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

IM_ACTIVITY - Activity

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

IM_MSGTY - Message Type

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

IM_MSGID - Message Class

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

IM_MSGNO - Message Number

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

IM_MSGV1 - Message Variable

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

EXCEPTIONS details

NO_AUTHORITY - Authority check failed

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

INVALID_CALL - Invalid Call of Function

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

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

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

Search for further information about these or an SAP related objects