Professional Documents
Culture Documents
Constrained Forecast Run (Finite Heuristic)
Constrained Forecast Run (Finite Heuristic)
(Finite Heuristic)
November 20, 2020
• The OBP finite heuristic takes order data and input key figure values and uses them to calculate a
priority-driven, order-based supply plan, taking constraints into account.
• For demands, the priority is derived from the demand prioritization rules maintained in planning
run profiles. For sources of supply, the priorities are integrated from external systems.
• As opposed to the confirmation run, the constrained forecast run does not consider sales orders
or forecast consumption
• Maximum Lateness
• Production Capacity
• Supplier Constraint
• Lot sizes
a) Tries to satisfy all demands within the scope of the planning run. Demands are sorted by
priority, with higher priority demands satisfied first.
b) First tries to satisfy each demand by searching for available stock at the demand location. If the
available stock isn't enough to satisfy the demand, it uses Production data structures or
Transportation lanes (for stock transfers and for procurement) to fulfill demand.
c) Chooses the sources of supply by priority and then does the following:
i)For production data structures, creates the production receipts and component demands.
Ii)For transportation lanes (stock transfer), creates a receipt in the target location and a demand
at the source location.
Iii)For transportation lanes (procurement), creates a purchase requisition.
d) Repeats steps 2 to 4 for all demands (from high priority demands to low priority demands).
Copyright © 2020 Accenture All rights reserved. 5
Basic Settings:
• Switchable Constraint
• Each demand prioritization rule consists of a pre-allocation segment, one or more demand prioritization
segments in a sequence, and a catch-all segment. Segments are the building blocks for the demand
prioritization rules.
• Rules for other Demand types Such as Forecast, Sales orders can be maintained from Segment 1 onwards.
• The remaining demand types/categories are assigned “catch-all segment(9999)”. If no rule assigned for
Forecast/Sales order, they are considered as part of “catch-all segment”.
• To prioritize demand within a segment, you can choose one of the 2 options:
4301
4101
4311
4301
4101
4311
4301
4311
DC1 DC2 • For example, you have 2 DC, with portion size equivalent to
100 and 50.
100 50
• Gating Factor
• Projected Stock
• Supply Usage: In the Supply Usage tab, you can directly trace the pegging relationship of
individual receipts on any level of the supply chain to their independent demands