Hierarchy
⤷ PE (Application Component) Training and Event Management
⤷ PP09 (Package) Training and Event Management
Basic Data
Data Element | RVORH |
Short Description | Number of available resources |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEC8 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Available |
Medium | 15 | No. available |
Long | 20 | Available resources |
Heading | 10 | Available |
Documentation
Definition
This specifies the number of resources of the corresponding resource type available in status 1 in the current time period. The schedule selected is also taken into account for this.
Number available means the following, depending on the value entered for Required:
- Value = X
Number available = number of resources that can be reserved i.e. that are neither locked nor reserved by another business event or, in the case of persons, persons that are available in the time period, again taking the selected schedule into account.
- Value = ' '
Number available = 0, since the resource does not need to be considered during planning.
- Value = *
Number available = number of (non-locked) resources of the corresponding type regardless of whether they are reserved (or in the case of persons available) since multiple reservation is possible.
The criterion as to when a resource constitutes an instance of a specific resource type depends on the availability features of the resource type. (Instances are either all objects of a particular object type or all objects that have a certain relationship with the business event type).
If no criterion has been defined in the availability features (general case), an instance of the resource type exists if the relationship with the abbreviation SPECA ("is a specialization of"; see T77S0) has been created between the resource and the resource type.
In order to qualify as instances of a resource type, the resource found in this way must belong to the location if
- the resources are location-dependent (as defined in infotype 1023 appended to the resource type) and you are carrying out business event planning using locations (switch ORT = 1 in T77S0)
or - you entered a location when you started the transaction.
A check is carried out to verify that the relevant relationship (abbreviation TORTA - "belongs to") exists between the resource and the location.
If the resource in question is an internal person (Object type OTYPE PERNR in T77S0), no check is carried out.
The availability check for persons involves the following:
- The system checks whether the person is already booked as an attendee on another business event in the same period, in which case he or she is not available and not included in the resource list. (This is business event attendance and instructor incompatibility.)
The following check is only carried out if the HR Time Management component is installed and integration with this has been activated via switch PLOGI PLOGI and PLOGI TIME in T77S0. (You are required to enter the active plan version in PLOGI PLOGI, and the value X in PLOGI TIME).
- In the case of internal persons (object type OTYPE PERNR in T77S0), the system reads the personal shift plan and absence records from Time Management for the period concerned.
Any absences (e.g. illness, vacation, days off depending on shift) that are incompatible with acting as instructor for the planned business are specified in T77KA. If such an incompatibility is found, the person is considered to be unavailable and is not included in the resource list.
History
Last changed by/on | SAP | 19950526 |
SAP Release Created in |