Purchase Optimization added

The default Supply Chain Optimization Planning Engine definition (SP_SCO) is updated to include a new Optimization: Concept

  • Purchase Optimization

After running the main optimization with a time limit, the quality of the purchase plan may be sub-optimal. With Purchase Optimization, in most cases, an optimal or near optimal purchase plan is found. For example, sub-optimal purchase plan may occur when ’min purchase qty’ is used for ’Supplier Allocations’.

This new variable is added to the SP_SCO Planning Engine definition:

  • solver_reoptimize_purchase. Default: FALSE

Setting this PE variable to TRUE, enables the Purchase Optimization, to run after the Solver optimization from workflows "100 - Solve" and "110 - Solve without Init“. The optimization can also be executed directly. Update solver parameters max_time and discrete_buckets in Purchase Optimization to control behavior.

For additional details on the optimization, see ScoDocumentation.html > Optimizations > Purchase Optimization, accessible from the SCO Planning Engine documentation in the standard content (template files) and "Find Out More" from the Supply Chain Optimization (SP_SCO) Planning Engine definition.

Note: This feature is enabled after appending the Planning Engine SP SCO template (apsco.zip) for this release at which point the optimization is added to the standard Planning Engine definition (SP_SCO). 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.