SAP CO_ZF_ORDER_LOCK Function Module for NOTRANSL: PPS-Auftrag: Sperren eines Auftrages
CO_ZF_ORDER_LOCK is a standard co zf order lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: PPS-Auftrag: Sperren eines Auftrages 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 zf order lock FM, simply by entering the name CO_ZF_ORDER_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: COZF
Program Name: SAPLCOZF
Main Program: SAPLCOZF
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CO_ZF_ORDER_LOCK 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_ZF_ORDER_LOCK'"NOTRANSL: PPS-Auftrag: Sperren eines Auftrages.
EXPORTING
AUFNR = "Order Number
* AUTYP = '10' "Order category
* CLIENT = SY-MANDT "ABAP System Field: Client ID of Current User
* SCOPE = '2' "ABAP System Field: Highlighted Input in Dynpro Field
* SIMULATE = ' ' "Selection Indicator
EXCEPTIONS
ORDER_ALREADY_LOCKED = 1 SYSTEM_FAILURE = 2
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_SAPLCOZF_001 Customer Exits in Function Group COZF
EXIT_SAPLCOZF_002 Customer Exits in Function Group COZF
EXIT_SAPLCOZF_003 Exit for Predefining Fields in the Order Header
IMPORTING Parameters details for CO_ZF_ORDER_LOCK
AUFNR - Order Number
Data type: AUFK-AUFNROptional: No
Call by Reference: No ( called with pass by value option)
AUTYP - Order category
Data type: T003O-AUTYPDefault: '10'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - ABAP System Field: Client ID of Current User
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
SCOPE - ABAP System Field: Highlighted Input in Dynpro Field
Data type: SY-DATARDefault: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SIMULATE - Selection Indicator
Data type: RC27X-FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ORDER_ALREADY_LOCKED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CO_ZF_ORDER_LOCK 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_aufnr | TYPE AUFK-AUFNR, " | |||
| lv_order_already_locked | TYPE AUFK, " | |||
| lv_autyp | TYPE T003O-AUTYP, " '10' | |||
| lv_system_failure | TYPE T003O, " | |||
| lv_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_scope | TYPE SY-DATAR, " '2' | |||
| lv_simulate | TYPE RC27X-FLG_SEL. " SPACE |
|   CALL FUNCTION 'CO_ZF_ORDER_LOCK' "NOTRANSL: PPS-Auftrag: Sperren eines Auftrages |
| EXPORTING | ||
| AUFNR | = lv_aufnr | |
| AUTYP | = lv_autyp | |
| CLIENT | = lv_client | |
| SCOPE | = lv_scope | |
| SIMULATE | = lv_simulate | |
| EXCEPTIONS | ||
| ORDER_ALREADY_LOCKED = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " CO_ZF_ORDER_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM CO_ZF_ORDER_LOCK
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 AUFNR FROM AUFK INTO @DATA(ld_aufnr). | ||||
| "SELECT single AUTYP FROM T003O INTO @DATA(ld_autyp). | ||||
| DATA(ld_autyp) | = '10'. | |||
| "SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| "SELECT single DATAR FROM SY INTO @DATA(ld_scope). | ||||
| DATA(ld_scope) | = '2'. | |||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_simulate). | ||||
| DATA(ld_simulate) | = ' '. | |||
Search for further information about these or an SAP related objects