Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP00 (Package) Organization and Planning
Basic Data
| Data Element | KPRIOX |
| Short Description | Booking Priority |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR2 | |
| 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 | Priority |
| Medium | 15 | Priority |
| Long | 20 | Priority |
| Heading | 2 | Pr |
Documentation
Definition
A priority's meaning is based on the entries in table 77S0:
MAXMU = maximum priority for an essential booking
NPRIO = default priority for a normal booking
MINWL = minimum priority for a waiting-list booking
Thus, a booking with priority
<= MAXMU
is an essential business event booking, i.e. the attendee
must attend the business event and is sure not to be put back on
the waiting list if further bookings are made later.
MAXMU < priority < MINWL
is a normal business event booking.
The system sets the value NPRIO from the above range
as a default value.
>= MINWL
is a booking onto the waiting list.
Supplementary Documentation - KPRIOX 3000
Use
For prebookings: priority has no fixed significance in the case of prebookings as it does for bookings. The user can decide how and if to use the priority feature for prebookings. The system automatically proposes the value SEMIN NPRIO from table T77S0.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
