SCO: Support moving only forecast to back-orders

The default Supply Chain Optimization Planning Engine definition (SP_SCO) is updated to support moving only forecast to back-orders. This provides greater control on delaying satisfied demand based on whether the demand consists of orders or forecast. For example, users now have the option to delay satisfying forecast to a later bucket while forbidding a delay in satisfying orders.

These entities are updated in SP_SCO:

  • Classes
    • Customer Allocations
  • Solver Optimization

The ’Allow Back-orders’ property in Customer Allocations is updated to:

  • Allow Forecast To Back-orders
  • Allow Orders To Back orders

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).

This interface is updated to map the new allow back-orders properties:

  • SP - SCV - SCO - Import Customer Allocations

This SCV database view is updated in the base template to use the new properties backorders_allowed_flag_orders and backorders_allowed_flag_forecast:

  • SP_V_CUSTOMER_ALLOCATIONS
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 includes this feature. You are not required a new role or privilege access to use this feature.