SAP CNV_MBT_ADM_SUBPRO_CREATE_DARK Function Module for Create project and subproject without user interaction (dark)
CNV_MBT_ADM_SUBPRO_CREATE_DARK is a standard cnv mbt adm subpro create dark SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create project and subproject without user interaction (dark) 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 adm subpro create dark FM, simply by entering the name CNV_MBT_ADM_SUBPRO_CREATE_DARK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_MBT_ADM
Program Name: SAPLCNV_MBT_ADM
Main Program: SAPLCNV_MBT_ADM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_MBT_ADM_SUBPRO_CREATE_DARK 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_ADM_SUBPRO_CREATE_DARK'"Create project and subproject without user interaction (dark).
EXPORTING
IP_PROJECT = "Package Number to Specify CMIS and TDMS Packages
* IP_SUBPROJECT = "Identification of MBT Subproject
* IP_SCENARIO = "MBT PCL: Scenario
* IP_CREATE_SUBPROJECT = "Flag (X = yes, initial = no)
* IP_CREATE_PROJECT = "Flag (X = yes, initial = no)
* IP_PROJECT_DESCRIPT = "Project description
* IP_SUBPROJ_DESCRIPT = "Subproject description
* IP_COT_CONTEXT_ID = "SAP LT project ID
* IP_NAME' ' = "SLO COT Namespace
IMPORTING
EP_PROJECT = "Identification of MBT Project
EP_SUBPROJECT = "Identification of MBT Subproject
EXCEPTIONS
PROJECT_NOT_CREATED = 1 WRONG_USER_FLAG = 10 SUBPROJECT_NOT_CREATED = 2 WRONG_PROJECT = 3 WRONG_CLIENT = 4 SUBPROJECT_ALREADY_EXIST = 5 PROJECT_DOESNOT_EXIST = 6 NO_PROJECT_NAME = 7 NO_SCENARIO = 8 NO_AUTHORIZATION = 9
IMPORTING Parameters details for CNV_MBT_ADM_SUBPRO_CREATE_DARK
IP_PROJECT - Package Number to Specify CMIS and TDMS Packages
Data type: CNV_MBT_PROJOptional: No
Call by Reference: No ( called with pass by value option)
IP_SUBPROJECT - Identification of MBT Subproject
Data type: CNV_MBT_SUBPROJOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_SCENARIO - MBT PCL: Scenario
Data type: CNV_MBT_SCENARIOOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_CREATE_SUBPROJECT - Flag (X = yes, initial = no)
Data type: CNV_MBT_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_CREATE_PROJECT - Flag (X = yes, initial = no)
Data type: CNV_MBT_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_PROJECT_DESCRIPT - Project description
Data type: CNV_MBT_TXTOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_SUBPROJ_DESCRIPT - Subproject description
Data type: CNV_MBT_TXTOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_COT_CONTEXT_ID - SAP LT project ID
Data type: CNV_MBT_COT_CONTEXT_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_NAMESPACE - SLO COT Namespace
Data type: CNV_MBT_COT_NAMESPACEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_MBT_ADM_SUBPRO_CREATE_DARK
EP_PROJECT - Identification of MBT Project
Data type: CNV_MBT_PROJOptional: No
Call by Reference: Yes
EP_SUBPROJECT - Identification of MBT Subproject
Data type: CNV_MBT_SUBPROJOptional: No
Call by Reference: Yes
EXCEPTIONS details
PROJECT_NOT_CREATED - Project could not be created
Data type:Optional: No
Call by Reference: Yes
WRONG_USER_FLAG - Problem with the registered user
Data type:Optional: No
Call by Reference: Yes
SUBPROJECT_NOT_CREATED - Subprojecgt could not be created
Data type:Optional: No
Call by Reference: Yes
WRONG_PROJECT - Subproject not assigned to the project
Data type:Optional: No
Call by Reference: Yes
WRONG_CLIENT - Not the correct client
Data type:Optional: No
Call by Reference: Yes
SUBPROJECT_ALREADY_EXIST -
Data type:Optional: No
Call by Reference: Yes
PROJECT_DOESNOT_EXIST -
Data type:Optional: No
Call by Reference: Yes
NO_PROJECT_NAME - Creating subproject requires a project name but the import parameter is initial
Data type:Optional: No
Call by Reference: Yes
NO_SCENARIO - When creating a project the import parameter is mandatory
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORIZATION - User hasn“t got the required authorizations
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_ADM_SUBPRO_CREATE_DARK 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_project | TYPE CNV_MBT_PROJ, " | |||
| lv_ip_project | TYPE CNV_MBT_PROJ, " | |||
| lv_project_not_created | TYPE CNV_MBT_PROJ, " | |||
| lv_wrong_user_flag | TYPE CNV_MBT_PROJ, " | |||
| lv_ep_subproject | TYPE CNV_MBT_SUBPROJ, " | |||
| lv_ip_subproject | TYPE CNV_MBT_SUBPROJ, " | |||
| lv_subproject_not_created | TYPE CNV_MBT_SUBPROJ, " | |||
| lv_ip_scenario | TYPE CNV_MBT_SCENARIO, " | |||
| lv_wrong_project | TYPE CNV_MBT_SCENARIO, " | |||
| lv_wrong_client | TYPE CNV_MBT_SCENARIO, " | |||
| lv_ip_create_subproject | TYPE CNV_MBT_FLAG, " | |||
| lv_ip_create_project | TYPE CNV_MBT_FLAG, " | |||
| lv_subproject_already_exist | TYPE CNV_MBT_FLAG, " | |||
| lv_ip_project_descript | TYPE CNV_MBT_TXT, " | |||
| lv_project_doesnot_exist | TYPE CNV_MBT_TXT, " | |||
| lv_no_project_name | TYPE CNV_MBT_TXT, " | |||
| lv_ip_subproj_descript | TYPE CNV_MBT_TXT, " | |||
| lv_no_scenario | TYPE CNV_MBT_TXT, " | |||
| lv_ip_cot_context_id | TYPE CNV_MBT_COT_CONTEXT_GUID, " | |||
| lv_ip_namespace | TYPE CNV_MBT_COT_NAMESPACE, " | |||
| lv_no_authorization | TYPE CNV_MBT_COT_NAMESPACE. " |
|   CALL FUNCTION 'CNV_MBT_ADM_SUBPRO_CREATE_DARK' "Create project and subproject without user interaction (dark) |
| EXPORTING | ||
| IP_PROJECT | = lv_ip_project | |
| IP_SUBPROJECT | = lv_ip_subproject | |
| IP_SCENARIO | = lv_ip_scenario | |
| IP_CREATE_SUBPROJECT | = lv_ip_create_subproject | |
| IP_CREATE_PROJECT | = lv_ip_create_project | |
| IP_PROJECT_DESCRIPT | = lv_ip_project_descript | |
| IP_SUBPROJ_DESCRIPT | = lv_ip_subproj_descript | |
| IP_COT_CONTEXT_ID | = lv_ip_cot_context_id | |
| IP_NAMESPACE | = lv_ip_namespace | |
| IMPORTING | ||
| EP_PROJECT | = lv_ep_project | |
| EP_SUBPROJECT | = lv_ep_subproject | |
| EXCEPTIONS | ||
| PROJECT_NOT_CREATED = 1 | ||
| WRONG_USER_FLAG = 10 | ||
| SUBPROJECT_NOT_CREATED = 2 | ||
| WRONG_PROJECT = 3 | ||
| WRONG_CLIENT = 4 | ||
| SUBPROJECT_ALREADY_EXIST = 5 | ||
| PROJECT_DOESNOT_EXIST = 6 | ||
| NO_PROJECT_NAME = 7 | ||
| NO_SCENARIO = 8 | ||
| NO_AUTHORIZATION = 9 | ||
| . " CNV_MBT_ADM_SUBPRO_CREATE_DARK | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_ADM_SUBPRO_CREATE_DARK
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