Hierarchy
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net⤷
PM-WOC-MO (Application Component) Maintenance Orders⤷
/MRSS/OPT (Package) Multi Resource Scheduling: Optimizer
Basic Data
| Data Element | /MRSS/T_OPTIMIZER_RELEVANT |
| Short Description | Object Relevant for Optimization? |
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 | Relevant? |
| Medium | 15 | Relevant? |
| Long | 20 | Relevant? |
| Heading | 9 | Relevant? |
Documentation
Definition
Determines whether the objects are relevant for optimization.
Use
If you select this checkbox, the corresponding entered objects, that is, demands and assignments, are relevant for optimization. This means that they are copied over with the next run.
Objects that do not meet the criteria are excluded from the optimization run.
Exception: If objects are relevant for optimization due to, for example, their relationships, they are later added again to the group of objects being transferred to the optimizer.
Dependencies
Example
One example of the above-mentioned exception can be a relationship that relates to a nonrelevant demand. Let us assume an end-start relationship between demand A and demand B.
Let us also assume that, due to Customizing, demand A should be excluded from the optimization run and demand B is included.
So that the optimizer can decide correctly whether demand B can be scheduled, that is, whether the relationship criterion is met, demand A, or the respective assignment, must also be included in the optimization although Customizing says otherwise.
History
| Last changed by/on | SAP | 20141109 |
| SAP Release Created in | 800 |
