SAP CNV_00001_CHECK_EXECUTION Function Module for Checks whether the currently running program can be run by user calling it

Search SAP Function Modules

CNV_00001_CHECK_EXECUTION is a standard cnv 00001 check execution 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 whether the currently running program can be run by user calling it 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 00001 check execution FM, simply by entering the name CNV_00001_CHECK_EXECUTION into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_00001_CHECK_EXECUTION 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_00001_CHECK_EXECUTION'"Checks whether the currently running program can be run by user calling it
  EXPORTING
*  PACKID =  "Package number
*  DELIVERY_ROLE =  "Check whether the user has delivery role
*  EXPERT_ROLE =  "Check whether the user is CWB expert
*  NO_EXEC_SLO_DEV_SYSTEM =  "No execution in SLO development system
*  NO_EXEC_SLO_CONS_SYSTEM =  "No execution in SLO consolidation system
*  SINGLE_EXECUTION =  "Check single execution
*  SINGLE_EXEC_PARAM =  "Parameter for single execution
*  AUTHORITY_CHECK =  "Parameter for authority check
*  ERROR_MESSAGE = 'X' "Parameter to through error message

 IMPORTING
   CONDITIONS_FILLED =  "

EXCEPTIONS
   NOT_ACTIVE_PACKAGE = 1    NO_DELIVERY_ROLE = 2    NO_EXPERT_ROLE = 3    SLO_DEV_SYSTEM = 4    SLO_CONS_SYSTEM = 5    EXECUTED_ONCE = 6    NO_SINGLE_EXEC_PARAM = 7    EXISTING_PARAMETER = 8    NO_AUTHORITY = 9 

.

IMPORTING Parameters details for CNV_00001_CHECK_EXECUTION

PACKID - Package number

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

DELIVERY_ROLE - Check whether the user has delivery role

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

EXPERT_ROLE - Check whether the user is CWB expert

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

NO_EXEC_SLO_DEV_SYSTEM - No execution in SLO development system

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

NO_EXEC_SLO_CONS_SYSTEM - No execution in SLO consolidation system

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

SINGLE_EXECUTION - Check single execution

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

SINGLE_EXEC_PARAM - Parameter for single execution

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

AUTHORITY_CHECK - Parameter for authority check

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

ERROR_MESSAGE - Parameter to through error message

Data type: DEF_PAR_FU-REQ_MODE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CNV_00001_CHECK_EXECUTION

CONDITIONS_FILLED -

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

EXCEPTIONS details

NOT_ACTIVE_PACKAGE - No active package

Data type:
Optional: No
Call by Reference: Yes

NO_DELIVERY_ROLE - No delivery role

Data type:
Optional: No
Call by Reference: Yes

NO_EXPERT_ROLE - No expert role

Data type:
Optional: No
Call by Reference: Yes

SLO_DEV_SYSTEM - SLO development system

Data type:
Optional: No
Call by Reference: Yes

SLO_CONS_SYSTEM - SLO consolidation system

Data type:
Optional: No
Call by Reference: Yes

EXECUTED_ONCE - One execution is already performed

Data type:
Optional: No
Call by Reference: Yes

NO_SINGLE_EXEC_PARAM - Parameter for single execution is not defined

Data type:
Optional: No
Call by Reference: Yes

EXISTING_PARAMETER - Parameter for single execution exists

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY - No authority

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_00001_CHECK_EXECUTION 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_00001_CHECK_EXECUTION

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