SAP BAPI_CTREQUEST_CREATE Function Module for Create request with tasks (method for object CTREQUEST)
BAPI_CTREQUEST_CREATE is a standard bapi ctrequest create 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 request with tasks (method for object CTREQUEST) 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 bapi ctrequest create FM, simply by entering the name BAPI_CTREQUEST_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCTS_OBJECT_CTREQUEST
Program Name: SAPLSCTS_OBJECT_CTREQUEST
Main Program: SAPLSCTS_OBJECT_CTREQUEST
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CTREQUEST_CREATE 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 'BAPI_CTREQUEST_CREATE'"Create request with tasks (method for object CTREQUEST).
EXPORTING
* REQUEST_TYPE = "W = Customizing request, otherwise Workbench request
AUTHOR = "Author of request to be created
TEXT = "Short text for the request to be created
* TRANSLAYER = "Transport layer of request
* PROJECT = "Project assignment for the request
IMPORTING
REQUESTID = "Number of the created request
HEADER = "Header information for request
RETURN = "Return structure of the errors
TABLES
* AUTHORLIST = "List of task authors and task types
TASK_LIST = "List of header information for the tasks
IMPORTING Parameters details for BAPI_CTREQUEST_CREATE
REQUEST_TYPE - W = Customizing request, otherwise Workbench request
Data type: BAPISCTS01-TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
AUTHOR - Author of request to be created
Data type: BAPISCTS01-AUTHOROptional: No
Call by Reference: No ( called with pass by value option)
TEXT - Short text for the request to be created
Data type: BAPISCTS01-TEXTOptional: No
Call by Reference: No ( called with pass by value option)
TRANSLAYER - Transport layer of request
Data type: BAPISCTS02Optional: Yes
Call by Reference: No ( called with pass by value option)
PROJECT - Project assignment for the request
Data type: BAPISCTS03Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_CTREQUEST_CREATE
REQUESTID - Number of the created request
Data type: BAPISCTS01-REQUESTIDOptional: No
Call by Reference: No ( called with pass by value option)
HEADER - Header information for request
Data type: BAPISCTS06Optional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return structure of the errors
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CTREQUEST_CREATE
AUTHORLIST - List of task authors and task types
Data type: BAPISCTS12Optional: Yes
Call by Reference: No ( called with pass by value option)
TASK_LIST - List of header information for the tasks
Data type: BAPISCTS07Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_CTREQUEST_CREATE 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_requestid | TYPE BAPISCTS01-REQUESTID, " | |||
| lt_authorlist | TYPE STANDARD TABLE OF BAPISCTS12, " | |||
| lv_request_type | TYPE BAPISCTS01-TYPE, " | |||
| lv_author | TYPE BAPISCTS01-AUTHOR, " | |||
| lv_header | TYPE BAPISCTS06, " | |||
| lt_task_list | TYPE STANDARD TABLE OF BAPISCTS07, " | |||
| lv_text | TYPE BAPISCTS01-TEXT, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_translayer | TYPE BAPISCTS02, " | |||
| lv_project | TYPE BAPISCTS03. " |
|   CALL FUNCTION 'BAPI_CTREQUEST_CREATE' "Create request with tasks (method for object CTREQUEST) |
| EXPORTING | ||
| REQUEST_TYPE | = lv_request_type | |
| AUTHOR | = lv_author | |
| TEXT | = lv_text | |
| TRANSLAYER | = lv_translayer | |
| PROJECT | = lv_project | |
| IMPORTING | ||
| REQUESTID | = lv_requestid | |
| HEADER | = lv_header | |
| RETURN | = lv_return | |
| TABLES | ||
| AUTHORLIST | = lt_authorlist | |
| TASK_LIST | = lt_task_list | |
| . " BAPI_CTREQUEST_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CTREQUEST_CREATE
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 REQUESTID FROM BAPISCTS01 INTO @DATA(ld_requestid). | ||||
| "SELECT single TYPE FROM BAPISCTS01 INTO @DATA(ld_request_type). | ||||
| "SELECT single AUTHOR FROM BAPISCTS01 INTO @DATA(ld_author). | ||||
| "SELECT single TEXT FROM BAPISCTS01 INTO @DATA(ld_text). | ||||
Search for further information about these or an SAP related objects