SAP CO_ZR_OPERATION_RELEASE Function Module for Release an operation with objects that are subordinate to it in hierarchy
CO_ZR_OPERATION_RELEASE is a standard co zr 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 Release an operation with objects that are subordinate to it in hierarchy 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 co zr operation release FM, simply by entering the name CO_ZR_OPERATION_RELEASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: COZR
Program Name: SAPLCOZR
Main Program: SAPLCOZR
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CO_ZR_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 'CO_ZR_OPERATION_RELEASE'"Release an operation with objects that are subordinate to it in hierarchy.
EXPORTING
AFVGD_IMP = "
CAUFVD_IMP = "
* FLG_FRE = ' ' "
* FLG_TFR = ' ' "
TRTYP = "
* CHECK_ONLY_IMP = ' ' "Only check whether release is possible
* NO_CHECK_IMP = ' ' "Release without check
EXCEPTIONS
FREE_FAILED = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCOZR_001 User Exit for Checking the Release of Activities
EXIT_SAPLCOZR_002 User Exit for Checking the Release of the Network
EXIT_SAPLCOZR_003 Release Control for Automatic Batch Determination: Handling of Tolerances
IMPORTING Parameters details for CO_ZR_OPERATION_RELEASE
AFVGD_IMP -
Data type: AFVGDOptional: No
Call by Reference: No ( called with pass by value option)
CAUFVD_IMP -
Data type: CAUFVDOptional: No
Call by Reference: No ( called with pass by value option)
FLG_FRE -
Data type: RC27X-FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FLG_TFR -
Data type: RC27X-FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TRTYP -
Data type: TC10-TRTYPOptional: No
Call by Reference: No ( called with pass by value option)
CHECK_ONLY_IMP - Only check whether release is possible
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_CHECK_IMP - Release without check
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FREE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CO_ZR_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_afvgd_imp | TYPE AFVGD, " | |||
| lv_free_failed | TYPE AFVGD, " | |||
| lv_caufvd_imp | TYPE CAUFVD, " | |||
| lv_flg_fre | TYPE RC27X-FLG_SEL, " SPACE | |||
| lv_flg_tfr | TYPE RC27X-FLG_SEL, " SPACE | |||
| lv_trtyp | TYPE TC10-TRTYP, " | |||
| lv_check_only_imp | TYPE TC10, " SPACE | |||
| lv_no_check_imp | TYPE TC10. " SPACE |
|   CALL FUNCTION 'CO_ZR_OPERATION_RELEASE' "Release an operation with objects that are subordinate to it in hierarchy |
| EXPORTING | ||
| AFVGD_IMP | = lv_afvgd_imp | |
| CAUFVD_IMP | = lv_caufvd_imp | |
| FLG_FRE | = lv_flg_fre | |
| FLG_TFR | = lv_flg_tfr | |
| TRTYP | = lv_trtyp | |
| CHECK_ONLY_IMP | = lv_check_only_imp | |
| NO_CHECK_IMP | = lv_no_check_imp | |
| EXCEPTIONS | ||
| FREE_FAILED = 1 | ||
| . " CO_ZR_OPERATION_RELEASE | ||
ABAP code using 7.40 inline data declarations to call FM CO_ZR_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.| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_flg_fre). | ||||
| DATA(ld_flg_fre) | = ' '. | |||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_flg_tfr). | ||||
| DATA(ld_flg_tfr) | = ' '. | |||
| "SELECT single TRTYP FROM TC10 INTO @DATA(ld_trtyp). | ||||
| DATA(ld_check_only_imp) | = ' '. | |||
| DATA(ld_no_check_imp) | = ' '. | |||
Search for further information about these or an SAP related objects