Hierarchy
⤷ PM-WOC-MO (Application Component) Maintenance Orders
⤷ /MRSS/SGU (Package) User Interface for Interactive Planning Board
Basic Data
Data Element | /MRSS/T_SGU_ASGN_TO_FIRST_SLOT |
Short Description | Move Assignment to First Available Slot |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /MRSS/_BOOLEAN | |
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 | First Slot |
Medium | 15 | First Slot |
Long | 25 | Assignment to First Slot |
Heading | 40 | Assignment to First Available Slot |
Documentation
Definition
Use
If you select this option, the system determines the assignment start and end based on the resource availability within the specified planning period.
The earliest possible assignment start is the time-now line or the earliest point in time at which the resource is available. In the case of concrete or stretched assignments, travel times are taken into consideration as well.
Depending on the assignment type, the assignment start and end are determined as follows:
- For concrete assignments, the system selects the earliest possible time period that covers the complete assignment (including travel times) without interruptions caused by breaks, absences, or concrete or stretched assignments.
- For stretched assignments, the system selects the earliest possible time period that is not interrupted by another stretched or concrete assignment. If time allocations (for example, breaks, absences) exist, the assignment is stretched to the next availability period.
- For capacitive assignments, the system determines the time period based on the demand start and end.
If you select this option, you can select multiple demands to be dropped on a resource. In this case, the system plans the demands sequentially and creates assignments as described above.
Note: The system does not issue error messages during the process of assigning multiple demands. If the system cannot assign all selected demands to the selected resource, an error message is displayed after the process has been completed.
Dependencies
Example
History
Last changed by/on | SAP | 20141109 |
SAP Release Created in | 800 |