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_PRIORITY_FACTOR |
| Short Description | Factor for Adjusting Non-Fulfillment Costs by Priority |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 4 | |
| Decimal Places | 2 | |
| Output Length | 5 | |
| 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 | Factor |
| Medium | 15 | Factor |
| Long | 20 | Factor |
| Heading | 6 | Factor |
Documentation
Definition
Defines a factor by which the non-fulfillment costs of a demand are changed depending on its priority
Use
You use this function to determine how demand priorities are included in the optimization process.
Dependencies
You define this factor in Customizing for SAP Multiresource Scheduling under Optimizer and Travel Times -> Optimizer -> Define Factors for Demand Priority.
Example
Let's assume that you have configured the following settings in Customizing:
Very High 10.00
High 5.00
Medium 1.00
Low 0.50
Let's also assume that the standard non-fulfillment costs for demands are set to 100.
For demands that have a very high priority, the non-fulfillment costs are increased by a factor of 10 (100 x 10.00). For demands that have a low priority, the non-fulfillment costs are reduced (100 x 0.50).
Since the optimizer attempts to avoid high solution costs, demands that have high non-fulfillment costs are planned first.
Demands with low non-fulfillment costs can remain open in favor of the "more expensive" demands or (if permitted) can be rescheduled.
History
| Last changed by/on | SAP | 20141109 |
| SAP Release Created in | 610 |
