Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP00 (Package) Organization and Planning
Basic Data
| Data Element | DELOC |
| Short Description | Lock/Delete Flag |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 3 | L/D |
| Medium | 15 | Lock/delete flg |
| Long | 20 | Lock/delete flag |
| Heading | 2 | LD |
Documentation
Definition
The contents of this field are derived from the contents of the
fields "Lock Flag" and "Delete Flag" for the relevant business
event in infotype 1026 (Additional Data - Business Event).
The following applies:
- Delete Flag (1026) = 'X' => Field Value = 'L'
(Business event has the delete flag set)
- Lock Flag (1026) = 'X' => Field Value = 'S'
(Business event has the lock flag set)
- Delete and Lock Flags (1026) = ' ' => Field Value = ' '
(Neither flag is set)
The reason that these two infotype fields can be reduced to one
field is that only one flag may be set at any one time for any one
business event, or, rather, that it is meaningless to set a lock
flag where a delete flag is already set.
Documentation on the individual fields from infotype 1026
Documentation on the field "Lock Flag":
The field which marks a business event with a lock flag is set
using report RHFIXKOO. The lock is purely temporary, i.e., no new
bookings may be made while the lock flag is on (cancellations
are, however, possible). The difference between this flag
and the delete flag is that the lock flag can be reset
at any time (using the "Unlock" function in report RHFIXK00).
This allows the user the option of only setting a lock flag
initially instead of the delete flag if he/she is still unsure
about a business event cancellation. Setting a lock flag is also
useful when parallel business events of the same type have
been planned and the business event coordinator wants one
of these business events filled to capacity before
bookings are accepted for the others.
The lock flag does not affect the rest of the business event data.
This is why it is also possible to set or remove a lock flag using
the transactions PP01 and PP02. As long as the business event remains
in Status 2, the lock flag has a meaning. For business events in
Status 1 (firm or cancelled), separate limitations apply (see the
RHFIXK00 documentation). Locking or unlocking a business event
in Status 1 is therefore meaningless. Accordingly, it is also
meaningless to set a lock flag if a delete flag is already
set (the report RHFIXK00 automatically resets the lock flag when a
business event is being cancelled).
Documentation on the field "Delete Flag"
When a business event is being cancelled, the field is set via the
report RHFIXK00. The business event is now only earmarked for
deletion, i.e., the business event data and bookings are not
in fact deleted, but remain stored in the system
(deleting all the business event data later requires
a different report, e.g., RHDELE00).
Once a business event is marked with a delete flag,
no new attendees can be booked on it.
In contrast to the lock flag, the delete flag is final and
irreversible. If there is any uncertainty about cancelling
a business event, it is better not to use the delete flag initially.
The main concern at this stage is to prevent new bookings
from being made for a business event that may well be cancelled,
and can be achieved equally well by simply using the lock flag.
The delete flag therefore marks a business event as "cancelled".
A "cancelled business event" differs in one other respect from a
"locked" business event: it may only contain priority bookings
>= MINWL (minimum capacity for a waiting list booking in T77S0),
in other words, waiting list bookings only. The report RHFIXK00
does this automatically during cancellation of a business event
by quite simply moving all the bookings to the waiting list.
This is why the delete flag can only be set via the report RHFIXK00,
and not by using the transactions PP01 or PP02, for instance.
Setting a delete flag will at the same time nullify the meaning
of any lock flag that might be set for the same business event.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
