SAP BAPI_PRODORD_CREATE_CAP_REQ Function Module for BAPI: Create Capacity Requirements for Production Orders
BAPI_PRODORD_CREATE_CAP_REQ is a standard bapi prodord create cap req SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI: Create Capacity Requirements for Production Orders 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 prodord create cap req FM, simply by entering the name BAPI_PRODORD_CREATE_CAP_REQ into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2005_BAPI
Program Name: SAPL2005_BAPI
Main Program: SAPL2005_BAPI
Appliation area:
Release date: 25-Feb-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PRODORD_CREATE_CAP_REQ 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_PRODORD_CREATE_CAP_REQ'"BAPI: Create Capacity Requirements for Production Orders.
EXPORTING
* WORK_PROCESS_GROUP = 'COWORK_BAPI' "Logon/Server Group Name
* WORK_PROCESS_MAX = 99 "Maximum number of work processes that can be used
IMPORTING
RETURN = "Return Parameters
TABLES
ORDERS = "Order Numbers
* DETAIL_RETURN = "Return Structure for Order BAPIs
* APPLICATION_LOG = "ApplicationLog Handle
IMPORTING Parameters details for BAPI_PRODORD_CREATE_CAP_REQ
WORK_PROCESS_GROUP - Logon/Server Group Name
Data type: BAPI_ORDER_CNTRL_PARAM-WORK_PROC_GROUPDefault: 'COWORK_BAPI'
Optional: Yes
Call by Reference: No ( called with pass by value option)
WORK_PROCESS_MAX - Maximum number of work processes that can be used
Data type: BAPI_ORDER_CNTRL_PARAM-WORK_PROC_MAXDefault: 99
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_PRODORD_CREATE_CAP_REQ
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PRODORD_CREATE_CAP_REQ
ORDERS - Order Numbers
Data type: BAPI_ORDER_KEYOptional: No
Call by Reference: Yes
DETAIL_RETURN - Return Structure for Order BAPIs
Data type: BAPI_ORDER_RETURNOptional: Yes
Call by Reference: Yes
APPLICATION_LOG - ApplicationLog Handle
Data type: BAPI_ORDER_APPLICATION_LOGOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_PRODORD_CREATE_CAP_REQ 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: | ||||
| lt_orders | TYPE STANDARD TABLE OF BAPI_ORDER_KEY, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_work_process_group | TYPE BAPI_ORDER_CNTRL_PARAM-WORK_PROC_GROUP, " 'COWORK_BAPI' | |||
| lt_detail_return | TYPE STANDARD TABLE OF BAPI_ORDER_RETURN, " | |||
| lv_work_process_max | TYPE BAPI_ORDER_CNTRL_PARAM-WORK_PROC_MAX, " 99 | |||
| lt_application_log | TYPE STANDARD TABLE OF BAPI_ORDER_APPLICATION_LOG. " |
|   CALL FUNCTION 'BAPI_PRODORD_CREATE_CAP_REQ' "BAPI: Create Capacity Requirements for Production Orders |
| EXPORTING | ||
| WORK_PROCESS_GROUP | = lv_work_process_group | |
| WORK_PROCESS_MAX | = lv_work_process_max | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| ORDERS | = lt_orders | |
| DETAIL_RETURN | = lt_detail_return | |
| APPLICATION_LOG | = lt_application_log | |
| . " BAPI_PRODORD_CREATE_CAP_REQ | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PRODORD_CREATE_CAP_REQ
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 WORK_PROC_GROUP FROM BAPI_ORDER_CNTRL_PARAM INTO @DATA(ld_work_process_group). | ||||
| DATA(ld_work_process_group) | = 'COWORK_BAPI'. | |||
| "SELECT single WORK_PROC_MAX FROM BAPI_ORDER_CNTRL_PARAM INTO @DATA(ld_work_process_max). | ||||
| DATA(ld_work_process_max) | = 99. | |||
Search for further information about these or an SAP related objects