Hierarchy

⤷

⤷

Basic Data
Data Element | LOT_DEV_ENQ_MODE |
Short Description | Lock Mode for Lot Devices for Adding |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LOT_DEV_ENQ_MODE | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Lock Mode |
Medium | 15 | Lock Mode Devs |
Long | 20 | Lock Mode for Devs |
Heading | 10 | Lock Mode |
Documentation
Definition
This parameter determines how the devices to be added to the sample lot are locked.
There are two options:
- In the Lock at Individual Device Level, the system tries to individually lock every device to be added to the sample lot. If a device cannot be locked, the system skips it and continues with the next device.
- In the Generic Lock, the system tries to lock all devices for the client in question. If this is not possible, the system waits for one minute and tries to set the lock again. The system keeps retrying for the amount of lock attempts that you defined previously.
Use
If there is a large number of lock entries, the lock at individual device level can lead to problems with the lock table or it can cause performance problems. SAP, therefore, recommends that you only use this type of lock for small to medium-size sample lots.
The generic lock is the most efficient way to allocate a large number of devices to a sample lot. In this case, all devices for a client are locked at the same time. However, you should only use this option if other users do not have to access transactions that change data during period in which the device data is changed.
Dependencies
This parameter is only used when an update is executed.
Example
Example 1: You want to add 100 devices to a sample lot. In this case, a generic lock is not necessary because this number of locks can be processed without any problems. As result, you can set a lock at individual device level.
Example 2: You want to add 30 000 devices to a sample lot. Here, you can consider using a generic lock because the lock table may not be sufficient to process this many devices and the runtime for the locks may increase considerably. In this case, setting the locks may take longer than actually changing the device data.
History
Last changed by/on | SAP | 20050223 |
SAP Release Created in | 472 |