Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-REP (Application Component) Report Tree⤷
SM38 (Package) ABAP Reporting
Basic Data
| Data Element | OPT |
| Short Description | SLIS: Status of saved lists |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| 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 | 36 | Status of radio button group status |
| Heading | 0 |
Documentation
Definition
Lists found in report trees can be either private or public. Setting this authorization attributes determines for whom the list is visible.
Private Lists:
Private lists are only visible for those people who have explicitly inserted the list in their report tree.
Public Lists:
Public lists are visible to everyone in principle. Whether or not the list is actually visible depends on the attributes of the node under which the list is found. If the node attribute is private, the list is only visible for those people who have explicitly inserted the list in the node. If the node attribute is public, the list is visble to everyone.
Supplementary Documentation - OPTIONSET 0001
Use
Operator used to search for reservations according to the requirements date.
Example
>= 01.03.96: the system searches for reservations whose requirements date is the same as or later than the date specified.
Procedure
If you do not enter an operator, the system uses the operator =, that is, it searches for reservations with the same requirements date as the date entered.
Dependencies
If you always use the same operator, you can define it as parameter OBD. To do this, choose System -> User profile -> User parameters.
Supplementary Documentation - OPTKAP 1000
Use
When the business event is created in infotype 1024 (capacity), the value of this field is written to the fields for maximum and optimum capacity.
Supplementary Documentation - OPTKAP 3000
Use
Definition of optimum capacity for business events:
The optimum capacity of a business event is the maximum number of attendees with which the optimum business event result can be achieved for the individual attendee.
Calculating the value:
Optimum capacity can be set directly for the business event, for the respective business event type, for the respective room, and for the resource type for the room (indicator "room" in infotype 1023).
To specify the optimum capacity of a business event in transactions, the individual values for optimum capacity are read at the specified object types and used to calculate the minimum. If no values are found for optimum capacity this way, optimum business event capacity is set to the value KAP in T77S0.
If the value set this way exceeds the maximum capacity of the business event, optimum business event capacity is set to maximum business event capacity.
Effects when booking/firmly booking:
If the number of bookings on an external or planned (status 2) internal business event has reached or exceeded optimum capacity, the system only allows essential bookings (priority <= MAXMU, where MAXMU is the maximum priority for an essential booking in table T77S0) or bookings on the waiting list (priority >= MINWL, where MINWL is the minimum priority for a waiting-list booking in table T77S0).
If the maximum capacity of the business event is not yet reached, new essential bookings (priority <= MAXMU) do not reset attendees who are already booked ("essential bookings without displacement").
If a planned (status 2) internal business event is firmly booked (using RHFIXK00), all bookings with priority < MINWL (that is, all non-waiting-list bookings) are taken into account (up to maximum capacity). If optimum capacity is still not reached, attendees on the waiting list (that is, bookings with priority >= MINWL) receive places on the business event up to optimum capacity.
If the number of bookings on a fixed (status 1) internal business event has reached or exceeded optimum capacity, only essential bookings (and no waiting-list bookings) are possible.
Supplementary Documentation - OPTKAP 7001
Use
Capacity of the room
Optimal number of event attendees which the room can accomodate. When booking attendees, a warning message is output if the room capacity is exceeded.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19990505 |
| SAP Release Created in |
