Split lost sales in lost orders and lost forecast

Split lost sales into lost orders and lost forecast (lost total remaining forecast) and optionally allow or forbid lost orders and lost forecast. Add orders service level and minimum orders service level. This enhancement provides greater control over lost sales based on whether it is lost orders or lost forecast.

Separate solver switches, penalties and priorities are created to control the additional properties. For example, lost forecast might be less important, however, you may require to allow lost forecast, not lost orders. There is now a way to indicate this to the optimization.

There are numerous changes to the default Supply Chain Optimization Planning Engine definition (SP_SCO) for this feature, covering classes, optimization, workflows, variables and queries.

These variables are added to SP_SCO:

  • solver_allow_lost_orders - Either allow(1) or forbid(0) 'Customer Allocations.lost orders'. Default: 1
  • solver_penalty_lost_orders - Unit penalty (unit cost) for 'Customer Allocations.lost orders'. Default: 10
  • solver_priority_lost_orders - The solver prioritized cost number (1 (first priority), 2, ... ,30 (last priority)) of 'Customer Allocations.lost orders'. Default: 3
  • solver_allow_lost_forecast - Either allow(1) or forbid(0) 'Customer Allocations.lost forecast'. Default: 1
  • solver_penalty_lost_forecast - Unit penalty (unit cost) for 'Customer Allocations.lost forecast'. Default: 10
  • solver_priority_lost_forecast - The solver prioritized cost number (1 (first priority), 2, ... ,30 (last priority)) of 'Customer Allocations.lost forecast'. Default: 3
  • solver_allow_under_min_sat_orders - Either allow(1) or forbid(0) 'Customer Allocations.under min sat orders'. Default: 0
  • solver_penalty_under_min_sat_orders - Unit penalty (unit cost) for 'Customer Allocations.under min sat orders'. Default: 200
  • solver_priority_under_min_sat_orders - The solver prioritized cost number (1 (first priority), 2, ... ,30 (last priority)) of 'Customer Allocations.under min sat orders'. Default: 3

These variables are removed from SP_SCO:

  • solver_allow_lost_sales
  • solver_penalty_lost_sales
  • solver_priority_lost_sales

These standard plan sheets are updated:

  • Alerts (SCO_Alerts)
  • Costs (SCO_Costs)
  • Customer Allocations Grid (SCO_Customer Allocations Grid)
  • Customer Allocations View (SCO_Customer Allocations View)

This multi-panel plan sheet is updated to add the Customer Allocations View panel, available through panel link:

  • 1. Plan Review (SCO_1Plan_Review)

This SCV database view is updated in the base template to use the new property min_orders_service_level:

  • SP_V_CUSTOMER_ALLOCATIONS
Note: This feature increases the size of customer allocations that can affect the optimization (solve) time. The recommendation is to consider reducing the size to customer groups or single demand point.

For additional details on the changes to SCO for this feature, see Change_log.html, accessible from the SCO Planning Engine documentation in the standard content (template files).

Note: This feature is enabled after appending the base template (base.zip) and Planning Engine SP SCO template (apsco.zip) for this release at which point the standard Planning Engine definition (SP_SCO) is updated. New instances of the Planning Engine created from this definition is includes this feature. You are not required a new role or privilege access to use this feature.