Skip to content

Supply Planning data model

Supply Planning converts a demand requirement into a feasible, time-phased response. Its central grain is:

material × location × period

That grain is extended when the decision needs an origin and destination, production resource, order, inventory lot, or scenario version. Master data defines what can happen; transactions describe the starting position and commitments; configuration selects the rules; the Supply Plan records the result.

Four connected data layers

Layer Main data Role in the model
Master data Materials, locations, units, transportation network, production resources and routings, BOMs and production versions Defines products, nodes, units, feasible flows, and production alternatives
Transactional data Inventory positions, open orders, deliveries, and production orders Establishes the initial balance, aging, receipts, firm production, commitments, and work already in progress
Configuration data Supply Planning setup, inventory policies, and Configured Planning Views Selects horizon, calendar, scenario versions, capacity behavior, replenishment rules, protection targets, and Planning Book presentation
Planning data Demand Plan, Supply Plan, and consolidated planned loading orders Provides the requirement and persists the versioned production, purchase, transfer, vehicle allocation, inventory, service, and constraint response

Grains that interact

Decision object Logical grain Question answered
Demand requirement material, demand location, period, version What is required, where, and when?
Inventory material, location, period; optionally lot or aging band What is available and what may expire?
Transfer or purchase material, origin, destination, period; optionally order or vehicle What should move, from where, and when?
Consolidated vehicle allocation Supply Plan, origin, destination, fleet, vehicle type, and dispatch period How many planned trips support the constrained transfer flow?
Production material, production location, resource or routing, period What should be produced and which capacity does it consume?
Inventory policy material, location, validity, priority What protection and replenishment rule applies?
Supply Plan line scenario version plus the applicable physical grain What did the selected scenario decide?

These grains must not be flattened prematurely. A material-location balance cannot explain a transportation lane, and a total production quantity cannot explain which resource or routing consumed capacity.

Main relationships

Origin Relationship Destination
Demand Plan creates requirements for material, demand location, and period
Inventory positions initialize available inventory, aging, and shelf-life exposure
Open orders provide committed or in-progress purchase, production, transfer, and sales flows
Deliveries reconcile and position quantities in picking, transit, or completed against their order lines
Production orders provide firm output and component consumption for production commitments already released to the operation
Transportation network authorizes and characterizes origin-destination replenishment alternatives
Production versions and BOMs connect output material to components and an eligible production path
Resources and routings consume and limit production capacity by location and period
Production costs value resource, routing, and shift decisions
Logistics and location costs value inventory at nodes and flows between locations
Inventory policies define safety stock, target or maximum stock, replenishment, priority, and validity
Supply Planning setup selects horizon, calendar, network version, capacity behavior, and execution options
Configured Planning View presents and governs input for one user's Supply Planning Book or Enterprise deployment workspace
Supply Planning execution transforms all inputs into the versioned Supply Plan
Supply Plan feeds S&OE, production sequencing, DRP, Inventory Optimization, and Cost-to-Serve
Consolidated planned loading orders connect the constrained transfer result to planned fleet usage, load formation, and vehicle-allocation cost

Transformation flow

  1. Validate materials, locations, units, and calendars.
  2. Select the network, production, capacity, and policy versions for the scenario.
  3. Load the released demand requirement.
  4. Position initial inventory, orders already committed or in progress, their delivery lines, and firm production orders.
  5. Expand feasible purchase, production, and transfer alternatives.
  6. Apply lead time, lot, multiple, capacity, shelf-life, priority, and inventory-policy rules.
  7. Generate the unconstrained or constrained response, according to the execution profile.
  8. Persist a Supply Plan version with physical outputs and explanatory indicators.
  9. Consolidate constrained transfer flows into planned trips by lane, fleet, and vehicle type when fleet allocation is enabled.
  10. Compare service, stock, write-off, cost, margin, and constraints before promoting or operationalizing the scenario.

Integrity rules

  • every material, location, and unit reference must resolve before execution;
  • each demand requirement must belong to an explicit plan version and period;
  • an origin-destination flow must exist in the selected network version;
  • production requires an eligible production version, routing, resource, and component structure when applicable;
  • initial inventory, open orders, and deliveries cannot silently change unit;
  • each delivery resolves one existing order item and is counted only once in the remaining balance;
  • each firm production order reconciles location and output material with its routing and bill of materials before contributing supply or component demand;
  • policy validity and priority must resolve to one effective rule for each material-location-period;
  • capacity, lead time, lot, and multiple must use the same calendar and unit context as the plan;
  • every Supply Plan output must remain traceable to its scenario and input versions.
  • every consolidated loading-order row must keep a complete lane, fleet, vehicle, dispatch date, and non-negative trip count.

Continue