SAP OIO_HD_OPERATION_RELEASE Function Module for OLM clear hold flag on order operation
OIO_HD_OPERATION_RELEASE is a standard oio hd operation release SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OLM clear hold flag on order operation 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 oio hd operation release FM, simply by entering the name OIO_HD_OPERATION_RELEASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIO_HD
Program Name: SAPLOIO_HD
Main Program: SAPLOIO_HD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIO_HD_OPERATION_RELEASE 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 'OIO_HD_OPERATION_RELEASE'"OLM clear hold flag on order operation.
EXPORTING
IV_AUFNR = "Order Number
IV_VORNR = "Operation Number
* IF_WITH_COMMIT = 'X' "Issue database commit
* IF_ENQUEUE = 'X' "Enqueue objects
EXCEPTIONS
ORDER_IN_USE = 1 REQUISITION_IN_USE = 2 DELIVERY_IN_USE = 3 ORDER_NOT_FOUND = 4 OPERATION_NOT_FOUND = 5 ERROR = 6
IMPORTING Parameters details for OIO_HD_OPERATION_RELEASE
IV_AUFNR - Order Number
Data type: AUFNROptional: No
Call by Reference: No ( called with pass by value option)
IV_VORNR - Operation Number
Data type: VORNROptional: No
Call by Reference: No ( called with pass by value option)
IF_WITH_COMMIT - Issue database commit
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IF_ENQUEUE - Enqueue objects
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ORDER_IN_USE - Requested order is locked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
REQUISITION_IN_USE - Related requisition in use
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DELIVERY_IN_USE - Related delivery is in use
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ORDER_NOT_FOUND - Requested order does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPERATION_NOT_FOUND - Requested operation does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR - Other error found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIO_HD_OPERATION_RELEASE 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_iv_aufnr | TYPE AUFNR, " | |||
| lv_order_in_use | TYPE AUFNR, " | |||
| lv_iv_vornr | TYPE VORNR, " | |||
| lv_requisition_in_use | TYPE VORNR, " | |||
| lv_if_with_commit | TYPE FLAG, " 'X' | |||
| lv_delivery_in_use | TYPE FLAG, " | |||
| lv_if_enqueue | TYPE FLAG, " 'X' | |||
| lv_order_not_found | TYPE FLAG, " | |||
| lv_operation_not_found | TYPE FLAG, " | |||
| lv_error | TYPE FLAG. " |
|   CALL FUNCTION 'OIO_HD_OPERATION_RELEASE' "OLM clear hold flag on order operation |
| EXPORTING | ||
| IV_AUFNR | = lv_iv_aufnr | |
| IV_VORNR | = lv_iv_vornr | |
| IF_WITH_COMMIT | = lv_if_with_commit | |
| IF_ENQUEUE | = lv_if_enqueue | |
| EXCEPTIONS | ||
| ORDER_IN_USE = 1 | ||
| REQUISITION_IN_USE = 2 | ||
| DELIVERY_IN_USE = 3 | ||
| ORDER_NOT_FOUND = 4 | ||
| OPERATION_NOT_FOUND = 5 | ||
| ERROR = 6 | ||
| . " OIO_HD_OPERATION_RELEASE | ||
ABAP code using 7.40 inline data declarations to call FM OIO_HD_OPERATION_RELEASE
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.| DATA(ld_if_with_commit) | = 'X'. | |||
| DATA(ld_if_enqueue) | = 'X'. | |||
Search for further information about these or an SAP related objects