Ansicht
Dokumentation
APO-OPT-PPS: Optimization Costs ( RELNAPO_30A_SP1_OPT-PPS6 )
rdisp/max_wprun_time - Maximum work process run time PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Short text
APO-OPT-PPS: Optimization Costs
Use
As of Release 3.0A (First Customer Shipment (FCS) and Support Package 1 (SP1)), the following new features and changes apply for the maintenance and evaluation of optimization costs.
Maintenance of mode costs
Up until now, you could define in the optimization profile the costs of executing an activity in a particular mode for each mode priority from A to O individually, whereby you had to enter the constant costs or increasing costs in descending order of mode priority .
As of Release 3.0A (FCS + SP1), you can only define the mode costs by interval for a maximum of four consecutive mode priority intervals.
Example:
You define the following costs in the optimization profile: 10 for modes up to priority D, 20 for modes up to priority H, 40 up to priority L and 80 for the rest. The mode costs are therefore as follows:
- 10 for modes with priority A to D
- 20 for modes with priority E to H
- 40 for modes with priority I to L
- 80 for modes with priority M to O
If you do not define any fixed costs, the system continues to use the following standard values for the costs:
- 1 for a mode with priority A
- 2 for a mode with priority B
- ...
- 15 for a mode with priority O
The standard value for variable costs is 0.
Delay costs dependent on order priority
Up until now, you could optimize your schedule, for example, in terms of the time delays for the orders in the optimization horizon (total delay for all orders and/or maximum delay for an individual order). As of Release 3.0A (FCS + SP1), you can weight the delay for an order by using a cost factor that is dependent on the order priority. How much the delay of an individual order costs, depends on the duration of the delay and the order priority.
Delay costs = Duration of delay in seconds x costs dependent on priority
The order priority is specified in the sales order or - depending on theproduct - in the product master. An order can have a priority between 1 (highest priority) and 255 (lowest priority). You define order delays in the optimization profile in the Costs tab page. You enter high costs for the orders with high priority and low costs for the orders with low priority. (You must enter constant or decreasing costs as the order of priority descends). You can only define the costs by interval for a maximum of four consecutive order priority intervals. If you do not enter any values for the costs, the system uses the default value of 1 for all priorities.
When optimizing, the system calculates the total costs for the delayed orders and the maximum delay costs for the individual order. You define the weightings for this objective function on the Basic settings tab page.
BAL_S_LOG - Application Log: Log header data Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 3261 Date: 20240426 Time: 225837 sap01-206 ( 88 ms )
