The best manufacturing ERP for discrete manufacturers with complex BOMs

SAP's guide to Production Engineering and Operations (PEO) in S/4HANA describes an external product lifecycle management (PLM) system that sends engineering changes as individual bills of materials (BOMs), after which production engineering decides how to incorporate them in manufacturing. We crown SAP S/4HANA with PEO for the discrete manufacturer that puts that PLM-to-production handover first, provided the S/4HANA release and PEO license in your quote demonstrate it. The change-notice scenario saves a new version of the manufacturing BOM and of the shop-floor routing, then prompts an update of the production version, whose valid-from date defaults to the manufacturing effective date on the change record.

Microsoft Dynamics 365 Supply Chain Management is the better pick when a central engineering company must release multilevel product structures to operational legal entities and you want each engineering version tracked as an inventory dimension.

What should a discrete manufacturer with complex BOMs weigh in an ERP?

Tech-Clarity's BOM management buyer's guide treats configurable product families and selectable components as BOM requirements in their own right, and it ties the more extensive configuration pattern to assemble-to-order and engineer-to-order work. That applies where you sell configured products, so test it on one of yours. Have each vendor enter your options and constraints and show the manufacturing BOM and routing that result.

The same guide lists effectivity, release state, approvals and change impact among the things to check in how a BOM change is controlled. Give each vendor one approved design change and have it carried from your PLM system to the production objects that receive it, with the effective dates shown. SAP documents a change-notice handover and Microsoft a release from an engineering company, and those are different routes, so run the same change through both.

SAP's MRP documentation for S/4HANA says the planning run chooses the BOM whose validity period contains the planned order's start date. Microsoft makes version tracking in transactions a choice for each engineering product category: with it on, the engineering version is an inventory dimension and stock is managed per version, and with it off, effective dates select the BOM and route. Write down your revision policy, then have each vendor show what happens to stock on hand and to open orders when a new version takes effect.

ASCM's supply chain dictionary describes time-phased MRP as netting on-hand and on-order stock against the requirements that a master schedule and a multilevel BOM create, then offsetting what is left by lead time. Ask each vendor for a measured run on your own data with the same planning settings and the hardware named, and compare the elapsed time and the materials each run covered.

The same dictionary separates the master production schedule from the sales forecast and treats the forecast as an input to that schedule. Have each vendor transfer a forecast by the route in its proposal and run planning on it, and ask who accepts the forecast before that run.

How SAP and Microsoft compare on complex BOMs

SAP S/4HANA with PEO: engineering changes handed from PLM to production

PEO's Analyze Change Impact app determines the effect of a change from the net change between the current and previous BOM versions, and it lists the manufacturing objects affected, production orders and purchase orders among them. SAP's comparison of handover strategies sets the change notice beside external snapshots, in which the PLM system compiles and controls what is handed over.

The handover from engineering BOM to manufacturing BOM runs either interactively in SAP's visual planner or through an automated function that flattens lower-level phantom BOMs into shop-floor BOMs. For a given material and plant, SAP says you cannot switch between the two from one change cycle to the next, so ask which method the proposed configuration assigns to each of your plants.

A 2023 FPS03 release note that SAP applies to S/4HANA and S/4HANA Cloud Private Edition describes change notices carrying source BOMs with phantom BOMs from an external PLM system into PEO. SAP's PEO setup lesson says the activated PEO features are not part of the standard S/4HANA Enterprise license and are activated plant by plant. Have the quote name the edition and release, and list the charges for PEO and for the PLM integration.

A configurable BOM in SAP's S/4HANA documentation is a parent BOM that holds the components every variant needs plus selectable components, and dependencies decide which of those are chosen when the product is configured. For a made-to-order product, an order BOM carries the changes for one sales order and leaves the master BOM unchanged. SAP defines a production version as holding a BOM alternative, a routing assignment, lot-size ranges and validity periods.

In PEO's version-controlled scenario, MRP uses the latest released version of the planning BOM and, where one is available, the latest released planning routing, and production versions are needed to run MRP. For version-controlled manufacturing BOMs without unitized parameter effectivity, the Manage Production Versions app shows the validity period of each BOM and routing version combination. Once a production order is in execution, an order-specific routing changes only operation activities that have not started, are on hold and are editable, and the change applies to that order alone.

MRP Live, SAP's planning run on the HANA database, has a performance log report, and a second report shows which engine planned each material. SAP's consumption logic compares planned independent requirements with actual customer requirements by quantity and date, inside a consumption period set in the material master or in Customizing.

Microsoft Dynamics 365 Supply Chain Management: one engineering company releasing to operational legal entities

An engineering company in Supply Chain Management releases a multilevel BOM structure together with its parent product in one action, lower-level products and BOMs included. Each receiving company holds a release policy and accepts products automatically or manually; with manual acceptance, a user there reviews the release and chooses whether the BOM and routes come in and which effective-from dates apply. Routes can be created locally where plants differ, and under Microsoft's data ownership rules the lines a receiving company adds persist when the engineering company releases the product again. Engineering products are released only from the engineering company, and each receiving company needs a product template before it takes a release.

Changes go through workflow-supported engineering change requests and change orders. A change order proposes its changes on a copy of the engineering data and leaves master data untouched until the order is processed. A business impact search lists the open sales orders, purchase orders, production orders and inventory affected, and electronic signatures can be required to approve and activate the changed BOMs and routes.

Every engineering product has at least one engineering version, which holds its BOM and routes with effective-from and effective-to dates. With version tracking on, each version is treated as a variant of a product master, and master planning plans supply per version.

Constraint-based product configuration models build one generic structure, and each configured variant comes out with its own BOM and its own route. Dimension-based configuration puts every possible component on one BOM and uses configuration groups and rules to pick among them, which Microsoft describes as suited to limited variability. BOM versions must be approved before planning or manufacturing uses them, and their validity can be limited by period, quantity, site and product dimensions. When a production order is created, the engineering BOM is copied to the order and becomes the manufacturing BOM at estimation, where phantom lines are replaced by their components.

Planning Optimization, Microsoft's planning engine for cloud deployments, performs its calculation in a service outside Supply Chain Management and returns planned orders and pegging data. Microsoft's migration guidance says it is included in the Supply Chain Management license. The migration guidance also describes a test in which two plans with the same settings, one per planning engine, are compared by planned-order quantity per period.

A master plan in Supply Chain Management reads demand from a selected forecast model, with settings for how forecast requirements are reduced and for forecast time fences. Microsoft's separate Demand planning app sends its forecast across through an export profile that carries a single time series to a target legal entity and forecast model, and the profile does not run until someone runs it or sets a schedule. Each production user of Demand planning needs a license.

Normet, a Finnish maker of mining and tunneling equipment, configures machines in Dynamics 365 Sales through a configurator integrated with Sovelia, its engineering application, according to a Microsoft customer story. The structured BOMs sit in Sovelia and flow to Dynamics 365, where they become production and purchase orders. The story puts a single machine at 2,000 to 3,000 components, with BOMs structured across five to ten levels.

Which manufacturing ERP is best for a discrete manufacturer with complex BOMs?

We crown SAP S/4HANA with PEO for the discrete manufacturer whose first requirement is carrying engineering changes from PLM into production, on the condition that the S/4HANA release and PEO license in your quote demonstrate that handover. SAP documents the route from the incoming change to the dated production version, with production engineering in control of how each change is incorporated and an impact analysis built on the net change between BOM versions. For this buyer, we give SAP's documented PLM-to-production handover priority. Before you sign, have SAP run one of your approved design changes from your PLM system through to the production version on the release it proposes.

Microsoft documents an explicit route for releasing product structures from one engineering company to operational legal entities, and a setting that makes the engineering version an inventory dimension. Where those two come ahead of the PLM handover, Dynamics 365 Supply Chain Management is the better pick, and SAP keeps the crown only for the buyer who puts the handover first. Have Microsoft quote Supply Chain Management, engineering change management, the PLM interface and Demand planning as named scope.

Other manufacturing ERP providers