BOMs, routes, production orders, process manufacturing, and production costing

How AX 2012 discrete and process manufacturing — BOMs, formulas, routes, resources, production orders, master planning, and production costing — upgrade to D365, and where the platform deltas hide beneath identical names.

What you will be able to do

• Identify the platform deltas between AX 2012 and D365 discrete manufacturing that the upgrade tooling does not resolve automatically
• Explain how formulas and co/by-products use BOMTable, BOMVersion, and PmfFormulaCoBy — not deprecated Pds* tables
• Map AX 2012 work centres to D365 resources (WrkCtrResource) and resource groups (WrkCtrResourceGroup)
• Describe the production order lifecycle changes and what 'in-flight' means for a Wave 5 cutover
• Reproduce production costing and variance analysis in D365 using the costing sheet and cost groups

Introduction

AX 2012 and D365 Finance & Operations share a manufacturing lineage. Production orders use ProdTable in both systems. BOMs sit in BOMTable and BOMVersion. Routes live in RouteTable and RouteVersion.

BOMs, formulas, and BOM versions

The discrete BOM model is identity-mapped. BOMTable holds the BOM header; BOMVersion carries the effectivity-date window and the approved/active flags; BOMLine holds the component lines with quantity, scrap factor, unit conversion, and line type. The data upgrade carries these forward.

Routes, operations, and resources

AX 2012 R2 used the legacy work-centre table as the primary work-centre record. AX 2012 R3 introduced the resource model (WrkCtrResource and WrkCtrResourceGroup) as an overlay, and many installations continued to reference both. In D365, the legacy table is retired entirely.

The production-order lifecycle

Subledger journal entries. Every production posting (material issue, route-card confirmation, report-as-finished, end) now creates a subledger journal entry before the general ledger voucher. The subledger-to-GL transfer can be batched.

Production costing and variance analysis

The costing sheet in D365 is the same construct as in AX 2012 — a hierarchical tree of cost-group nodes that classifies costs as material, labour, overhead (indirect), or outsourcing. The data upgrade carries the costing sheet forward. The delta is enforcement:

Master planning and Planning Optimization

The built-in master-planning engine (ReqCalc) that AX 2012 estates use is deprecated in D365. Microsoft's direction is Planning Optimization — a cloud-native microservice that runs outside the application database and returns planned orders via integration.

Subcontracting

AX 2012 R3 subcontracting uses a route operation linked to a vendor, with a service item on the operation that generates a purchase order when the production order is released. D365 preserves this model but adds an explicit resource type:

In-flight production orders — Wave 5

A production order is in-flight if it is in any status between Started and Reported-as-finished at the moment of cutover. It has accumulated WIP: material issues have been posted, route-card confirmations have been posted, and the resulting debit to WIP accounts sits in the AX 2012 general ledger.

Knowledge check

Summary

Manufacturing is identity-mapped at the concept level between AX 2012 and D365 — but the platform has changed beneath the concepts. The work is validation, not redesign.