SAP BAPI_PRODORD_RELEASE_OPERATION Function Module for BAPI: Release Production Order Operations
BAPI_PRODORD_RELEASE_OPERATION is a standard bapi prodord release operation 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: Release Production Order Operations 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 release operation FM, simply by entering the name BAPI_PRODORD_RELEASE_OPERATION 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: 26-Feb-2014
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PRODORD_RELEASE_OPERATION 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_RELEASE_OPERATION'"BAPI: Release Production Order Operations.
EXPORTING
* RELEASE_CONTROL = '1' "Release control operation
* 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 Parameter(s)
TABLES
OPERATIONS = "External Key of an Operation
* DETAIL_RETURN = "Return Structure for Order BAPIs
* APPLICATION_LOG = "ApplicationLog Handle
IMPORTING Parameters details for BAPI_PRODORD_RELEASE_OPERATION
RELEASE_CONTROL - Release control operation
Data type: BAPI_ORDER_FUNC_CNTRL-RELEASE_CNTRL_OPERDefault: '1'
Optional: No
Call by Reference: No ( called with pass by value option)
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_RELEASE_OPERATION
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PRODORD_RELEASE_OPERATION
OPERATIONS - External Key of an Operation
Data type: BAPI_ORDER_OPERATION_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_RELEASE_OPERATION 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_return | TYPE BAPIRET2, " | |||
| lt_operations | TYPE STANDARD TABLE OF BAPI_ORDER_OPERATION_KEY, " | |||
| lv_release_control | TYPE BAPI_ORDER_FUNC_CNTRL-RELEASE_CNTRL_OPER, " '1' | |||
| lt_detail_return | TYPE STANDARD TABLE OF BAPI_ORDER_RETURN, " | |||
| lv_work_process_group | TYPE BAPI_ORDER_CNTRL_PARAM-WORK_PROC_GROUP, " 'COWORK_BAPI' | |||
| lt_application_log | TYPE STANDARD TABLE OF BAPI_ORDER_APPLICATION_LOG, " | |||
| lv_work_process_max | TYPE BAPI_ORDER_CNTRL_PARAM-WORK_PROC_MAX. " 99 |
|   CALL FUNCTION 'BAPI_PRODORD_RELEASE_OPERATION' "BAPI: Release Production Order Operations |
| EXPORTING | ||
| RELEASE_CONTROL | = lv_release_control | |
| WORK_PROCESS_GROUP | = lv_work_process_group | |
| WORK_PROCESS_MAX | = lv_work_process_max | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| OPERATIONS | = lt_operations | |
| DETAIL_RETURN | = lt_detail_return | |
| APPLICATION_LOG | = lt_application_log | |
| . " BAPI_PRODORD_RELEASE_OPERATION | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PRODORD_RELEASE_OPERATION
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 RELEASE_CNTRL_OPER FROM BAPI_ORDER_FUNC_CNTRL INTO @DATA(ld_release_control). | ||||
| DATA(ld_release_control) | = '1'. | |||
| "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