SAP ABAP Data Element XLLKA (Late Lock Active)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
LO-BM (Application Component) Batches
⤷
VBDRV (Package) Batch Derivation
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-BM (Application Component) Batches⤷
VBDRV (Package) Batch Derivation
Basic Data
| Data Element | XLLKA |
| Short Description | Late Lock Active |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | LtLckActve |
| Medium | 15 | Late Lck Active |
| Long | 40 | Late Lock Active for Sender Batches |
| Heading | 7 | LtLkAct |
Documentation
Definition
Specifies that the late lock is active for sender batches during the shipping approval.
Use
Set this indicator if you want to post goods issues for sender batches while the shipping approval is being used.
Dependencies
The sender batches are temporarily locked when the transaction starts, in the processing between selection and display, but are released again before they are displayed. When you save, the sender batches are locked again and are checked to see if any of the sent values have been changed in the meantime. These additional checks can cause reduced performance and might also cause errors when you save derivations.
Example
History
| Last changed by/on | SAP | 20020107 |
| SAP Release Created in | 470 |
