Updated recently
Last updated:
Quick Answer: This Dynamics 365 supply chain management guide walks through what the SCM app family actually contains and how it works together: product master data, bills of material and routings, MRP and master planning, warehouse work with waves and tasks, procurement and sales flow, and inventory costing. The short version: SCM is where physical reality is modelled, and almost every problem you will meet in a live plant traces back to master data that was designed too quickly.
Who Should Use This Dynamics 365 Supply Chain Management Guide — and Who Should Not
Dynamics 365 Supply Chain Management is built for organisations that make things or move physical goods. If your business buys and sells, stores and ships but does not manufacture, you still have a legitimate use case — warehouse management, inventory accuracy, planning optimisation and procurement — but you are buying a bigger tool than you need, and Business Central will often cover your requirements at a third of the implementation cost.
Three groups should read this and think again. If your business is a pure distributor of a few thousand SKUs with simple put-away and pick, the warehouse functionality here is probably overkill. If you need fine-grained production scheduling — finite capacity scheduling of a complex job shop — that is a specialised manufacturing execution problem, and the answer is dedicated MES rather than forcing an ERP to do it. And if you are evaluating for a career, know that SCM roles concentrate in manufacturing clusters, and moving from finance into supply chain is easier than the reverse because finance knowledge transfers.
For the broader picture of how the Dynamics apps divide up, see our Dynamics 365 complete guide, and for the pay bands for this role, the Dynamics 365 Supply Chain Management salary India 2026 guide.
The SCM Module Map
| Area | What it covers | What a consultant really configures |
|---|---|---|
| Product information management | Products, variants, BOMs, routings, engineering change | Product model groups, product dimensions, BOM lines and versions, routing operations, where-used, engineering change management |
| Production planning | MRP, work templates, calendars | Planning parameters, master planning and MRP settings, work templates, resource profiles and calendars, planned order handling |
| Production control | Production orders, job scheduling, reporting | Production order templates, job and operation scheduling, capacity and resource assignment, report progress and end reporting, production feedback |
| Warehouse management | Warehouse work, waves, tasks, tracking | Warehouses, locations, zones, work and template groups, wave and task creation, cross-docking, license plate tracking |
| Inventory | Stock, availability, costing | Item model groups, unit of measure and conversions, storage dimensions, available-to-promise logic, inventory costing methods, transfer orders |
| Cost accounting | Cost categories, costing versions, variances | Cost categories, costing versions with cost elements, cost pools and allocation rules, settlement runs, standard cost updates |
| Procurement | RFQ, quotations, purchase orders, agreements | RFQ and quotation handling, purchase agreements and terms, purchase order policies and workflow, vendor scoring |
| Sales and marketing | Sales orders, agreements, availability | Sales agreements, sales order policies, availability and ATP checks, quotation handling, delivery and transport information |
| Planning | Demand and supply planning, optimisation | Master planning, planned orders, demand and supply planning, planning optimisation across sites, pegging and fixing relations |
| Quality management | Inspections, quarantine, non-conformance | Quality orders, inspections and test parameters, quality charges, quarantine and non-conformance handling |
Product Master Data: Product, BOM and Routing
Everything downstream depends on three objects, and configuring SCM means spending real time on them. The product carries the identity, the item model group (which decides whether the item is stocked, purchased, manufactured or a service), the unit of measure and conversions, and the storage dimensions that define how it is tracked. The BOM defines what a manufactured item is made of: component lines with quantities, notes such as whether a line is a phantom (assembled then consumed, never stocked), and versions carrying an approval status so the planner knows which to trust. The routing defines how it is made: a sequence of operations, each pointing at a resource, each with a setup and run time and a work template saying which tasks and reports it should generate.
Conceptual illustration — how a product becomes a producible thing
(not a screen path; the object relationships)
Product
item model group : Manufactured
unit of measure : Each
storage dimensions : Size (S/M/L), Finish
|
+-- BOM (version: Approved)
| line 1 : Motor qty 1 (purchased)
| line 2 : Frame qty 1 (purchased)
| line 3 : Harness qty 1 (phantom - assembled, not stocked)
|
+-- Routing
op 10 : Frame weld -> resource WeldCell-1 work template: Weld report
op 20 : Harness assy -> resource AssyLine-2 work template: Assembly report
op 30 : Test -> resource TestBench-1 work template: Quality report
MRP uses the APPROVED BOM; the planner sees planned orders
Production control uses the ROUTING to create operations and tasks
Three rules violated constantly, each with expensive consequences. Never leave a BOM version unapproved — planning reads only what it trusts, and a draft BOM is invisible to MRP. Never change a released BOM in place; create a new version and route it through engineering change management, because plants running the old version will report the old quantities against the wrong components. And never design a routing without checking that its resources exist, have capacity calendars and carry work templates, because a routing operation with no resource is a production order that cannot be scheduled.
Planning: How MRP Turns Demand Into Planned Orders
MRP in Dynamics 365 SCM is a calculation, not a magic box. You set planning parameters on the item model group — planning method, horizon, days of supply, safety stock, lead time derivation. Then MRP explodes demand: it takes sales orders, forecasts and dependent demand from parent BOMs, nets off inventory and existing supply, applies safety stock, and outputs two things — demand elements to plan manually, and planned orders for items it thinks should be bought or made.
The behaviour that surprises people is netting. MRP does not tell you what to buy; it tells you the net requirement after existing stock, on-hand purchase orders and forecast supply. If a planner overrides the suggested quantity, they must record the fixing relation, otherwise the next run re-raises the same requirement and the purchase team buys twice. Recording overrides properly separates a disciplined plant from one that lives on spreadsheets beside the ERP.
Master planning sits above MRP and adds the judgement MRP cannot have: consolidated demand across products, pegging of supply to demand, and planning at a higher level (by product family, by region) when the business needs it. Planning optimisation, available in current SCM versions, runs alongside MRP to suggest order quantities across sites and propose transfers when it believes that is cheaper than buying. It is worth understanding, but it supplements rather than replaces clean master data — the same principle that broke the MRP run below applies here.
Warehouse Work: Locations, Templates, Waves and Tracking
Warehouse management in SCM is about the physical movement of goods, and it is heavily configuration-driven. Goods live in locations, optionally grouped into zones for inbound, outbound, picking and storage. Behaviour is defined by work templates, which say what tasks get created for a movement (receiving, picking, put-away, cycle counting) and what reports and movements accompany them. Work templates roll up into work template groups, and the group applied to a product or warehouse decides which rules run — which is why a warehouse that behaves inconsistently usually has inconsistent group assignment rather than a broken template.
Waves are the release mechanism: work is created and held until it is released in a wave, so that many pick tasks can be created together and then optimised as a batch — by location, by carrier, by order priority. Tasks are the executable units of warehouse work, with a status that tracks them from created to started to completed. Batch and serial number tracking add traceability on top, which is what makes the product acceptable in pharma, food and automotive — and what makes traceability migration painful, because every historical lot has to be loaded correctly or the plant cannot release anything.
Not every warehouse needs this depth. If your operation is receive-store-pick-ship with no lot control and no wave optimisation, a lighter configuration is faster to implement and simpler to run. The Dynamics 365 Supply Chain Management certification path covers what employers look for in this area.
Procurement, Sales and the Order-to-Cash Flow
The commercial side of SCM is where it meets the finance world. A request for quotation becomes a quotation, and once accepted a purchase order; receiving against it creates the receipt that updates on-hand inventory; the invoice posts the liability; a three-way match compares the purchase order, receipt and invoice before payment is released. That matching logic is why finance teams get involved in SCM projects, and it is worth knowing before a planning interview that the plant and the accounts department want different things from the same system.
On the sales side, sales orders carry a requested delivery date, and availability checks — including available-to-promise logic where configured — determine whether a date can be promised. Transfer orders move stock between sites or warehouses without an external purchase and sale, which matters for a multi-plant company deciding whether to source internally or buy locally. The difference between a healthy SCM process and an unhealthy one shows up in three places: how long it takes to answer “where is my material”, how often a planner overrides the plan, and how many expedite freight invoices the company pays a year.
Costing: Cost Categories, Costing Versions and Standard Cost
Costing is where planning meets finance, and where consultants get caught out. Cost categories define what is being costed — materials, labour, machine time, freight. A costing version defines a costing object, such as a product or process, and the cost elements used to accumulate cost into it. Settlements then move actual cost from the general ledger into the cost accounting ledger so variances can be analysed by cost category and dimension.
The two costing methods that matter most in manufacturing are standard cost and moving average. Standard cost gives a stable reference for planning and variance analysis, which is exactly what a plant controller wants; moving average is easier to run and is common in process and distribution businesses. Whichever is chosen, the update process must be controlled: a standard cost update changes every future valuation, so it needs approval, effective dating and a plan for what happens to work in progress. Uncontrolled standard cost updates are one of the most reliable ways to produce an unexplainable month-end variance.
War Story: The Production Order That Nobody Could Complete
A Pune industrial equipment manufacturer went live on Dynamics 365 SCM for a new assembly plant. Production planning was configured, the BOM was clean, the MRP run produced sensible planned orders, and the whole thing looked ready. The first production order could not be scheduled.
The routing had been designed during the blueprint workshop by the product engineering team without plant involvement, and every operation pointed at a work centre code that existed on paper but had no resource record with a capacity calendar and no work template attached. The planner could create the production order and the engineering team could see the operations, but the report progress screen had nowhere to send them — there was no work template to generate the report task. Production had no way to book time against an operation, so the order sat at zero percent forever while the line waited for parts already on the shelf.
The fix took three weeks of plant time and a rework of the routing design: create resource records with realistic calendars and capacity profiles, attach work templates per operation type, correct the template groups so completion triggers the next operation, and rebuild the routings with plant engineers in the room rather than design engineers alone. The customer also picked up a lesson they had not expected — the resource master is data, and data takes time to build. Nobody had budgeted for it.
The cost surprise on top: because operations could not be booked, actual labour never posted, so every production order ran at zero cost and standard-versus-actual variance reporting showed nothing for two months. A reporting system that is confidently wrong is worse than no reporting. If you take one thing from this guide, take the sequence: resource calendar and work template before routing, routing before production order, production order before cost settlement.
Training Resources
Work through the SCM modules and objects with SkilBrill Power Platform Functional Consultant Training — Dynamics 365 SCM functional design and configuration practice across master data, planning, warehouse and costing, with case-based labs and career support.
FAQ
What is covered in Dynamics 365 Supply Chain Management?
Product information management, production planning and control, warehouse management, inventory, cost accounting, procurement, sales and marketing, planning and quality management. In practice, SCM is the manufacturing and distribution execution layer of the Dynamics 365 family.
What is the difference between a BOM and a routing in Dynamics 365 SCM?
The BOM defines what a manufactured item is made of — the component lines, quantities and versions. The routing defines how it is made — the sequence of operations, each tied to a resource with a calendar and a work template. MRP explodes the BOM; production control schedules the routing.
How does MRP work in Dynamics 365 SCM?
MRP nets demand from sales orders, forecasts and dependent parent demand against on-hand inventory, existing purchase orders and supply, applies safety stock, and outputs planned orders or demand elements. It does not decide what to buy — it proposes, and planners override with recorded fixing relations or the next run will repeat the requirement.
Is Dynamics 365 SCM overkill for a small distributor?
Often, yes. For a simple buy-sell operation, Business Central covers sales, purchasing, inventory and basic warehouse functions at a fraction of the implementation cost. SCM earns its complexity when you have real manufacturing, lot traceability, or warehouse execution worth optimising.
How long does a Dynamics 365 SCM implementation take?
Typically 6–12 months for a manufacturing organisation, because master data — products, BOMs, routings, resources and calendars — has to be built and validated before planning can be trusted. Distribution-only implementations are shorter. The long pole is master data, never the software.
