Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_REQ (Package) CTS: Request Editing
Basic Data
| Data Element | LOCKFLAG |
| Short Description | Lock status or import status of an object entry |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AS4FLAG | |
| 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 | Status |
| Medium | 15 | Status |
| Long | 20 | Lock/Import Status |
| Heading | 0 |
Documentation
Definition
Use
The LOCKFLAG field in table E071 is used in different ways.
For requests created in the current system, the flag was given character values. For this reason, the field also has the type character.
In the case of an imported request, LOCKFLAG (in the target system) was filled with binary values. Only the last two bits were functional for Releases before 3.1x.
Conflicts between these two different forms did not normally occur because the naming convention allowed imported requests and requests created in the current system to be distinguished.
The functionality of this table field was enhanced, replacing the binary form with a consistent and compatible use of character values, and channeling the read and write access to the field with two new function modules.
These function modules allow those using E071-LOCKFLAG to use meaningful symbolic names in their code instead of cryptical technical values.
The two function modules are called TRINT_E071_LOCKFLAG_READ and TRINT_E071_LOCKFLAG_WRITE.
Notes
The F4 help for the field (in the E071 editor) refers to the fixed values of domain LOCKFLGTXT.
Procedure
Examples
The following technical values are currently implemented:
Requests created in the system:
" " Object entry without lock
"X" Object entry with lock
Imported requests:
" " Object not (yet) imported
"1" Object imported with errors
"2" Object imported successfully
"3" Object generated/activated successfully
Special values for logical objects:
"4" Object imported successfully into shadow area
"5" Logical import from shadow area to target client failed
For upgrade only:
"6" Import in shadow tables of the substitution upgrade was successful
Dependencies
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
