SAP CO_ZF_ORDER_LOCK_MULTI Function Module for NOTRANSL: Sperren von Aufträgen und abhängiger Segmente mit Protokoll
CO_ZF_ORDER_LOCK_MULTI is a standard co zf order lock multi 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: Sperren von Aufträgen und abhängiger Segmente mit Protokoll 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 multi FM, simply by entering the name CO_ZF_ORDER_LOCK_MULTI 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_MULTI 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_MULTI'"NOTRANSL: Sperren von Aufträgen und abhängiger Segmente mit Protokoll.
EXPORTING
* LOCK_MODE = 'S' "Lock (S) or unlock specification
* EXPLODE_PRODNET = ' ' "
* FLG_VERS_ENQ = "
* I_CHANGE_DIALOG = "
* I_SCOPE = '2' "Control Lock Behavior When Calling the Update Task
TABLES
ENQUEUE_TAB = "Table of the order numbers to be edited
NOT_LOCKED = "Table of order numbers of not locked
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_MULTI
LOCK_MODE - Lock (S) or unlock specification
Data type:Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPLODE_PRODNET -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
FLG_VERS_ENQ -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CHANGE_DIALOG -
Data type: RC27X-FLG_SELOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SCOPE - Control Lock Behavior When Calling the Update Task
Data type: DDENQSCOPEDefault: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CO_ZF_ORDER_LOCK_MULTI
ENQUEUE_TAB - Table of the order numbers to be edited
Data type: ORDTYP_PREOptional: No
Call by Reference: No ( called with pass by value option)
NOT_LOCKED - Table of order numbers of not locked
Data type: ORD_PREOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CO_ZF_ORDER_LOCK_MULTI 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_lock_mode | TYPE STRING, " 'S' | |||
| lt_enqueue_tab | TYPE STANDARD TABLE OF ORDTYP_PRE, " | |||
| lt_not_locked | TYPE STANDARD TABLE OF ORD_PRE, " | |||
| lv_explode_prodnet | TYPE ORD_PRE, " ' ' | |||
| lv_flg_vers_enq | TYPE ORD_PRE, " | |||
| lv_i_change_dialog | TYPE RC27X-FLG_SEL, " | |||
| lv_i_scope | TYPE DDENQSCOPE. " '2' |
|   CALL FUNCTION 'CO_ZF_ORDER_LOCK_MULTI' "NOTRANSL: Sperren von Aufträgen und abhängiger Segmente mit Protokoll |
| EXPORTING | ||
| LOCK_MODE | = lv_lock_mode | |
| EXPLODE_PRODNET | = lv_explode_prodnet | |
| FLG_VERS_ENQ | = lv_flg_vers_enq | |
| I_CHANGE_DIALOG | = lv_i_change_dialog | |
| I_SCOPE | = lv_i_scope | |
| TABLES | ||
| ENQUEUE_TAB | = lt_enqueue_tab | |
| NOT_LOCKED | = lt_not_locked | |
| . " CO_ZF_ORDER_LOCK_MULTI | ||
ABAP code using 7.40 inline data declarations to call FM CO_ZF_ORDER_LOCK_MULTI
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_lock_mode) | = 'S'. | |||
| DATA(ld_explode_prodnet) | = ' '. | |||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_i_change_dialog). | ||||
| DATA(ld_i_scope) | = '2'. | |||
Search for further information about these or an SAP related objects