Authored by Naga Lokesh Magham & Verified by Anoop Prasad, SAP Digital Manufacturing & Practice, Körber Stellium
A functional walkthrough of the changes that matter to production, quality, and integration teams — in discrete and process manufacturing alike.
If you run production on SAP Digital Manufacturing (SAP DM), release 2608 is not a “read it later” release. Several changes affect how goods receipts, component consumption, and shop floor confirmations behave by default — and if your team doesn’t adjust configuration or ways of working, you could see gaps in inventory, missed goods movements, or blocked transactions on go-live day.
This article covers
Why SAP DM 2608 requires Shop Floor Readiness
- Auto Goods Receipt Processing Moves from MES to ERP for Process Manufacturing
- Backflush Component Consumption Moves from SAP DM to ERP
- New SFC Processing Rules for Discrete and Process Manufacturing
- Platform, Security, and Integration Changes in SAP DM 2608
- SAP DM 2608 Readiness Checklist Before Go-Live
Why SAP DM 2608 requires Shop Floor Readiness
SAP has been explicit that the driving goals behind 2608 are traceability, data integrity, and predictability. In practice, that means SAP DM is pulling back from silently completing certain transactions on your behalf, and instead making sure every goods movement and consumption event is deliberate, visible, and traceable back to a system of record — usually your connected SAP ERP system.
The two biggest shifts affect process manufacturing directly. A third set of changes affects shop floor control (SFC) processing across both discrete and process environments. And a fourth bucket covers platform-wide housekeeping, security, and admin changes that every SAP DM customer should scan regardless of industry.
Auto Goods Receipt Processing Moves from MES to ERP for Process Manufacturing
If your recipes are configured with Auto GR = Yes, this is the headline change (SAP Note 3682288).
Today, when an operator posts a quantity confirmation, SAP DM automatically posts the goods receipt for the finished material, co-products, and by-products. From 2608 onward, that automatic posting inside SAP DM stops for finished materials and co-products (and by-products where backflush applies). Instead, SAP DM sends the confirmation to your connected SAP ERP system, and the goods receipt is posted there, based on ERP-side configuration.
What this means operationally:
- Inventory, floor stock visibility, and cloud events for these goods receipts will no longer appear in SAP DM by default.
- Quantity confirmations tied to these goods receipts can no longer be cancelled using the Manage Cancellations app in SAP DM.
- If your team relies on the Manage Floor Stocks app or DM-side dashboards to see finished goods and co-product receipts in near real time, that visibility moves to ERP unless you take action.
The good news: SAP DM still gives you a way to keep tracking this in-app. The Post button in the Goods Receipt POD plugin will be enabled so operators can manually post, and there, goods receipts for finished materials and co-products directly in SAP DM. By-products behave a little differently: the Post button is always enabled for by-products regardless of the Auto GR setting, but whether that receipt is reported back to ERP depends on the Backflush indicator on the BOM item.
Bottom line for process manufacturing leads: decide now whether your operators need to actively post goods receipts in the POD going forward, or whether you’re comfortable relying entirely on ERP-side visibility. This is a process and training decision, not just a system one.
Backflush Component Consumption Moves from SAP DM to ERP
A closely related change (SAP Note 3682383) applies to backflush-enabled BOM components.
Currently, when a quantity confirmation is posted, SAP DM automatically backflushes (consumes) components flagged as Backflush Enabled and reduces inventory accordingly. From 2608, SAP DM will stop reducing inventory and reporting this consumption automatically. The backflush event is instead handed to your connected ERP system, which processes the consumption based on its own configuration.
Practical impact:
- Component consumption for backflush items will no longer automatically reflect in SAP DM inventory, the Manufacturing Data Objects, or the SFC Report.
- As with goods receipts, you retain a manual option: the Material Consumption POD plugin will visibly flag backflush components (with an italic “Backflush” label) and enable manual posting if your team wants DM-side traceability.
- Manually posted consumption in SAP DM will not be sent back to ERP or SAP EWM, and cannot be cancelled from SAP DM, so this is a one-way, DM-only record for visibility purposes.
For plants that use SAP DM dashboards or Insights reporting to monitor real-time material consumption, this is worth flagging to your quality and planning teams well before go-live — the default behavior is changing under existing configurations, not just for new ones.
New SFC Processing Rules for Discrete and Process Manufacturing
SAP Note 3742101 introduces a set of guardrails that apply to both discrete and process manufacturing, wherever SFCs, process lots, buyoffs, or dispositions are used.
- Process lots — Process lots become more locked-down: you can no longer nest a process lot inside another, add an SFC that has quantity in Complete Pending status, or mix active SFCs from different resources into the same lot.
- SFCs that belong to a process lot can no longer be individually scrapped, serialized, merged, split, invalidated, quantity-adjusted, changed in production, or held/released — those actions now have to happen at the lot level.
- Buyoffs — A buyoff with a decision still pending (accept/reject) can no longer be deleted or disabled — it has to be resolved first.
- Cancelling confirmations — Quantity confirmations can only be cancelled under specific material and routing flag combinations (Autocomplete/Confirm off, Quantity Validation and Relaxed flow should be in same state either enabled or disabled but not vice versa). Confirmations outside those combinations are no longer supported via SAP DM.
- Special operations / disposition — Pulling an SFC into a special routing via SFC Start now requires specific conditions to be met (entry step alignment, Autocomplete/Confirm and Quantity Validation flags, and SFC status).
- Error handling — API error messages are clearer and more actionable, and scenarios that previously failed silently (no error code) will now return one. Error codes themselves are unchanged, so downstream error-handling logic keeps working.
None of this requires new licensing or infrastructure, but it does mean shop floor SOPs, exception-handling playbooks, and any custom automation built around cancellations, process lots, or buyoffs should be reviewed and re-tested against 2608 behavior before go-live.
Platform, Security, and Integration Changes in SAP DM 2608
SAP Note 3764341 rounds up broader administrative and integration changes. Most won’t need urgent action, but a few deserve a look depending on your setup:
- Collaboration links for new plants — New plants created after 2608 will no longer auto-connect three collaboration links (EWM staging, defect code fetch, REO back-schedule). Existing plants are unaffected, but new plant rollouts need this step added manually.
- Analytics domain change — If your organization allowlists domains for the embedded SAP Analytics Cloud, the domain is moving from *.sapanalytics.cloud to *.analytics.cloud.sap. Update firewall, browser policy, and CSP allowlists if you’ve explicitly restricted cross-site access.
- Reprint access — The Reprint Documents app role template now excludes several personas (Automation Engineer, Production Engineer, Production Operator, and limited Admin/Engineer roles) by default. If those roles need reprint access, it has to be reassigned manually after upgrade.
- API deprecations — Two older API endpoint sets (Shop Floor Control Production Activities V1, Edge Order V1) are deprecated with decommission dates in 2704 and 2708 respectively. If custom integrations still call these, they should be migrated to the V2 equivalents now.
- Edge computing customers — If you use NGINX Ingress Controller for edge computing deployments, migration to NGINX Gateway Fabric is recommended given Ingress is being retired industry-wide — and it requires planned downtime plus two external IPs instead of one.
SAP DM 2608 Readiness Checklist Before Go-Live
- Inventory every routing/recipe with Auto GR = Yes and every BOM with Backflush Enabled = Yes, and decide plant-by-plant whether operators need to manually post in the POD for DM-side visibility going forward.
- Brief production supervisors and quality teams on the new cancellation restrictions for quantity confirmations, process lots, and buyoffs; these change what “undo” looks like on the floor. Ask your integration team to confirm ERP-side configuration is ready to receive and post the goods receipts and backflush consumption that SAP DM will no longer post automatically.
- Audit custom automation, reports, and dashboards that assume real-time DM-side inventory or consumption visibility for backflush items and Auto GR orders; these may now show gaps unless manual posting is adopted.
- Check any integrations still calling the deprecated V1 endpoints and plan migration to V2 ahead of the 2704/2708 decommission dates.
2608 is ultimately about making SAP DM behave more like a system of engagement and less like a silent system of record for goods movements it doesn’t own end-to-end. That’s a healthy direction for data integrity — but only if plant, quality, and integration teams adjust their playbooks in step with it.
Prepare Your SAP DM Environment for Release 2608
The SAP Digital Manufacturing 2608 release introduces changes that may affect shop floor processes, ERP integration, inventory visibility, and existing configurations.
Körber Stellium can help you assess the impact, identify readiness gaps, and prepare your production and integration teams for a smoother transition.
Explore SAP Digital Manufacturing Solutions | Get a Free SAP DM Assessment
