Hierarchy
⤷ BC-BMT-OM (Application Component) Organizational Management
⤷ SP00 (Package) Organization and Planning
Basic Data
Data Element | MAXKAP |
Short Description | Maximum Number of Attendees for Business Event |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEC3 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | Maximum |
Medium | 15 | Max.attendees |
Long | 20 | Maximum no.attendees |
Heading | 3 | Max |
Documentation
Definition
Definition:
Maximum business event capacity is the maximum number of
people who can attend the business event, determined
by the room capacity.
Capacity depends on the size of the room.
Calculation of the Value:
The maximum capacity can be set directly for the
training business event, its business event type, the room
and the room's resource type (the "room" indicator in infotype
1023). In order to determine the maximum capacity of a
business event in transactions, the individual values for the
maximum capacity in respect of the named object types are
read and a minimum is formed. If no values are found
for the maximum capacity, the maximum business event capacity
is set at the value KAP from table T77S0.
Effects on Booking/Firm booking:
If the number of bookings for an external or planned
(status 2) internal training business event has reached
maximum capacity, then only the following are possible:
Essential business event bookings (priority <= MAXMU, where
MAXMU is the maximum priority for an essential business event
booking in table T77S0), or
Bookings on a waiting list (priority >= MINWL, where MINWL
is the minimum priority for a waiting list booking in table
77S0).
When essential business event bookings are made, a different
attendee booked with priority p (MAXMU < p <MINWL),
that is, a "normal" booking which is neither a waiting
list booking nor an essential business event booking, must be
put back on the waiting list so that maximum capacity
is not exceeded ("an essential business event booking with
displacement"). If the number of attendees who can
be "put back" is not sufficient when a definite booking
is made, only one booking can be made on the waiting list.
If the bookings with priority <= MAXMU (essential bookings)
for an external or planned (status 2) internal training
business event have exceeded its maximum capacity, bookings can
only be made with priority >= MINWL (on the waiting list).
If a planned (status 2) internal training business event is
firmly booked (via RHFIXK00), all of the bookings with
priority < MINWL (that is, all non-waiting list
bookings) are definitely taken into account up to
maximum capacity.
If the number of bookings for a firmly-booked (status
1) internal training business event has reached its maximum
capacity, no more bookings can be made for this
training business event.
See domain OPTKAP.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in |