SAP Digital Manufacturing and S/4HANA: A Plant Leader’s Guide to the Shop-Floor Data Loop

The model is not the weak point. The loop between the shop floor and SAP is.

Altivate | Published 22 October 2026

1. Why the loop, not the model

Plant reviews can reach the same question: can I trust the numbers in SAP? The order shows complete, but the line ran short. Scrap on the shift report does not match scrap in the ERP. The OEE figure looks healthy in a month the plant knows was bad. Finance asks why work-in-progress valuation moved, and nobody on the floor can explain it.

These can be loop problems rather than analytics problems. A manufacturing execution system (MES) such as SAP Digital Manufacturing (SAP DM) receives orders from SAP S/4HANA and sends back what actually happened: good quantity, scrap, activity time, labour, the components that went into the product and the quality results. When that traffic is late, arrives at the wrong granularity or fails quietly in a queue, the ERP stops describing the plant. Every KPI, plan and AI use case built on the ERP then inherits the gap, and the gap can go unnoticed until a review.

This guide is written for the person who answers for the plant: the Head of Manufacturing or plant operations, with the COO and CIO as the second readers. It explains, level by level, what SAP documents about the loop between SAP DM and S/4HANA, where it breaks in practice, and what to check. It closes with a free loop register you can run with your team this week.

This guide documents how the loop can fail according to SAP’s own pages. It does not claim how often each failure occurs in any plant.

Every SAP statement here comes from SAP Help Portal pages and the SAP Notes they cite, and was checked in October 2026. Where SAP documents a behaviour only for one edition, such as SAP S/4HANA Cloud Public Edition, the qualifier is kept. Where we could not verify a behaviour from a primary SAP source, we say so and describe it as plant practice, not as SAP behaviour.

2. What SAP Digital Manufacturing is, and where it sits in ISA-95

ISA-95, also published as ANSI/ISA-95 and IEC 62264, is the international set of standards for integrating business logistics systems with manufacturing control systems. Its level model is the cleanest way to locate each piece of the loop:

ISA’s overview includes SCADA among Level 3 systems, while other ISA material places SCADA functions at Level 2. Map your plant’s SCADA functions and decide which system owns each event.

For SAP ERP and SAP S/4HANA integrations using SAP Cloud Integration, inbound data reaches DM over HTTPS; outbound confirmations use Cloud Connector to call ERP BAPIs over RFC. Supported direct SAP S/4HANA OData scenarios bypass Cloud Integration but still reach the on-premise S/4HANA system through Cloud Connector; this route does not apply to SAP ERP. SAP S/4HANA Cloud Public Edition uses direct integration through communication arrangements and requires neither SAP Cloud Integration nor Cloud Connector. Production Connector and DM for edge computing serve separate plant-connectivity or edge scenarios:

• SAP Digital Manufacturing is the MES in this loop. Operators work in production operator dashboards (PODs), such as the Work Center, Order and Operation Activity PODs, and work in progress is recorded against shop-floor control (SFC) records, terms SAP’s documentation uses throughout. SAP Digital Manufacturing was previously called SAP Digital Manufacturing Cloud (SAP DMC); SAP’s own material from 2019 to 2022 uses that name, so older guides and notes may too.
• SAP Cloud Integration carries the SAP ERP and SAP S/4HANA flows that use it; the direct S/4HANA scenarios above bypass it, and SAP S/4HANA Cloud Public Edition does not need it. For the standard SAP ERP and SAP S/4HANA flows that use Cloud Integration, SAP ships a package named “SAP S/4HANA Integration with SAP Digital Manufacturing” and recommends deploying all of its integration flows, in a Cloud Integration tenant on a separate SAP Business Technology Platform (BTP) subaccount. Section 3 covers the package and its lifecycle.
• Production Connector and SAP Digital Manufacturing for edge computing sit at the plant end of the landscape. Production Connector is available as a standalone Windows installation or as a module on SAP Digital Manufacturing for edge computing. SAP documents the edge module for OPC UA server connections, and client certificates in Manage Web Servers are supported only for the Windows installation. The Windows installation can call the edge APIs using CA and client certificates; when edge services run inside a Production Connector automation sequence, a Cloud Connector connection is not needed.

The edge deployment is infrastructure the plant will own. SAP DM for edge computing runs on a Kubernetes cluster configured through Helm values. It requires an external, dedicated database, PostgreSQL or Microsoft SQL Server; the embedded PostgreSQL is for proof of concept only and supports neither high availability nor backup and restore, and changing database type later means a reinstall. Productive use also needs an external Kafka cluster (Strimzi Kafka, installed manually); switching Kafka clusters later causes downtime. We found no SAP statement that the edge deployment as a whole offers high availability, so do not plan as if it does.

For the service view of SAP DM, including how Altivate approaches an implementation, see our SAP Digital Manufacturing page; for a general introduction to the product, see our article on SAP Digital Manufacturing and Industry 4.0. For the wider integration architecture behind Cloud Integration, see Integration Architecture Is a Contract Before It Is a Tool.

3. Orders down: release, the RMES notification and the echo

SAP describes order integration as “the control point from production planning to the order”. Production order data is transferred from SAP S/4HANA or SAP ERP to DM for execution. The order is typically converted from a planned order produced by an MRP run, and it is released as a production order in DM.

Prerequisites that decide whether the loop is sound

For SAP ERP or SAP S/4HANA using the IDoc/DRF integration path, check the following prerequisites. SAP S/4HANA Cloud Public Edition uses SAP_COM_0522 for order integration; assess that edition’s prerequisites separately.

• Unique identities. Multiple ERP systems need unique system IDs, and plant names must be unique across ERP systems at client level. Where they are not, plant mapping is required.
• Business functions. LOG_PP_MES_INT_01, LOG_PP_MES_INT_02 and LOG_PP_MES_INT_03, the technical basis for the Data Replication Framework, must be implemented.
• One BAdI. BAdI CO_MES_INT_REDISTRIBUTION must be implemented in the ERP.

The release echo

The last prerequisite is where a quiet fault starts. Releasing an order in the DM Manage Orders app sends a release notification, RMES, back to the ERP. Without BAdI CO_MES_INT_REDISTRIBUTION implemented (SAP Note 2165261), the ERP then communicates an order change back to DM, which SAP says “can cause issues”. As an illustration of how that can look on the floor: orders that re-arrive, change under the operator, or carry a status the planner did not set. The symptom looks like a planning problem; the cause is a missing enhancement in the ERP.

What to check: the BAdI is implemented in every ERP client that feeds DM, and a test release in DM produces no inbound order change. Owner: the ERP basis or integration lead, with the plant planner confirming the test.

Discrete or process: decided by one flag

DM handles an order as discrete-industry or process-industry according to the “Auto complete and confirm” flag set at material level in the integrated ERP: active means discrete handling, inactive means process handling. A material maintained with the wrong setting changes floor behaviour without any change in DM, so the flag belongs on the master-data checklist (section 8).

What the order carries

For SAP S/4HANA Cloud Public Edition, SAP documents that the order-specific BOM and routing or recipe are created in DM from the transferred order data, and that orders with a production resource and tool (PRT) assignment can be transferred, but only material PRT assignments are supported. If your plant relies on other PRT types, plan how the operator will see them before go-live.

The package and its lifecycle

SAP’s standard SAP ERP and SAP S/4HANA flows that use Cloud Integration run through the package named above; custom integration flows can be configured separately. SAP points to three notes: SAP Note 3050090 for the artifacts required per message type, SAP Note 3315636 for the change log, and SAP Note 3549024 for troubleshooting. If any of your flows still run on the Neo environment, note that the Neo version of this package is already deprecated. SAP says a future release will stop updates and bug fixes, gives no date, and strongly recommends moving to the Cloud Foundry version. Do not wait for the date: an integration that no longer receives fixes is a plant risk, not an IT preference.

4. Confirmations up: yield, scrap, activity and labour

This is the half of the loop that decides whether the ERP describes the plant. As production is done on the floor, the DM order confirms yield and scrap to S/4HANA. If components were assembled, they are included in the confirmation so they can be issued to the order in the ERP. SAP documents several confirmation types, each with its own prerequisites:

The reporting step is a granularity decision

SAP ties three documented flows to ERP reporting steps on the routing: activity confirmation needs at least one, planned-order scrap needs at least one, and serial reporting works best with the last operation as one (below). The planned-order scrap rule shows what that means: if scrap happens on a step that is not a reporting step, DM uses the next reporting step it finds. That is correct behaviour, and where you place reporting steps is a choice with a cost.

• Report at every operation and the ERP sees work-in-progress, scrap location and activity close to real time. The price is message volume, more failure points and more confirmations to reverse when an operator makes a mistake.
• Report only at the last operation and the ERP receives less operation-level progress and scrap-location detail until then. Costs, and in SAP S/4HANA Cloud event-based work in process, may still be posted earlier through goods issues, activity confirmations or receipts; check the WIP and settlement design for your edition separately.

There is no universal right answer. The wrong answer is the one nobody chose: reporting steps inherited from a template, so that cost accounting, planning and the plant each assume a different granularity. Write the choice down per routing family, with the reason and the owner.

Labour that waits for approval

Direct labour, as documented for S/4HANA Cloud Public Edition, reaches the ERP only after a time record is approved. If approval slips to Friday, labour cost in the ERP lags the floor by a week. Name who approves, and by when.

Goods receipt: the double-posting trap

The Goods Receipt plugin requires that automatic goods receipt is not enabled in the ERP for the relevant operations. SAP lists this as a prerequisite but does not describe the failure. If both are active, the same output could be posted twice, so treat it as a risk to test before go-live, not as documented behaviour. Two further details catch teams out. First, for by-products with the Backflush indicator enabled, DM does not send an integration message reporting those goods receipts to the ERP, so check where by-product stock is meant to be recorded. Second, the older directives MATERIAL_DOCUMENT and GOODS_RECEIPT_CONFIRMATION are deprecated; a configuration copied from an early project may still map to them. For supported production-order goods receipts, cancellation needs the GOODS_RECEIPT_CANCEL_PROD_ORDER directive. SAP does not support cancellation of automatic receipts, receipts posted upon SFC completion, or over-delivered receipts; check the posting path before relying on reversal.

Serial and batch numbers of assembled components

DM can transfer the serial and batch numbers of assembled semi-finished components inside yield, planned-order, scrap and container-close messages, but the goods-movement section with movement type 261 is included only in the Production Order Yield Confirmation and Production Order Scrap Confirmation messages. The ERP needs Batch Management, a serial number profile and control keys that allow confirmations but not automatic goods receipt. Serial reporting is not supported for time-based components, and SAP recommends making the last routing operation an ERP reporting step so that all consumed components are reported.

5. When the ERP is unreachable: message statuses and retries

Every interface fails sometimes: the ERP is down for maintenance, a planner has the order locked, a certificate expires. What matters is whether a failure is visible, who sees it and what they may do about it.

The statuses

Each integration message carries an Overall Status: New, Queued, Failed Before Queue, In Process, Delivered, Completed, Failed or Inactive. Three facts about them change how a plant should operate:

• Queueing is not universal. New, Queued and Failed Before Queue apply only to certain message types where queued processing is used. Do not assume every message waits in a queue while the ERP is away. Ask, per message type in your scope, what happens when the target is unreachable.
• Delivered is not done. If the “CPI Async Mode” switch is activated in the Manage Collaboration Directives app, outbound messages show Delivered when SAP Cloud Integration has received them but they have not yet been sent to the ERP. The status changes to Completed only once sent successfully. A dashboard that counts Delivered as success overstates the loop.
• Two statuses, two truths. Messages carry both an Overall Status, covering the lifecycle across DM, the ERP and the middleware, and a DM Integration Status, covering DM’s integration layer only. With an external error such as “Order locked in ERP”, the Overall Status is Failed while the DM Integration Status is Completed. SAP Cloud ALM uses the DM Integration Status.

The In Process retry hazard

Failed, Failed Before Queue and, with caution, In Process messages can be retried. The caution is the point. SAP says to retry an In Process message only when you are certain the scenario did not succeed in the target system, otherwise data can become inconsistent. For an outbound message, that means only if the ERP was not updated; for an inbound one, only if the data was not created in DM. In Process messages that need no retry should be set to Inactive.

In plant terms: a yield confirmation sits In Process and a supervisor, closing the shift, retries it. If the first attempt had already posted, the repeat may make the data inconsistent. Check the ERP posting before retrying and reconcile any repeated attempt against the original message.

What to check: a written rule for who may retry In Process messages, and the check they must make in the ERP first. Owner: the integration lead writes the rule; the plant decides who holds the right.

Retry at message level

SAP advises retrying at message level, not submessage level, so that a repeat failure still raises the Message Failed event. Retrying a submessage can silence the very alert that would have told someone the problem was not fixed.

The 2-week list retention

By default, Completed and Inactive messages are removed from the dashboard list 2 weeks after creation. The retention period can be customised in Retention Settings. Two weeks is shorter than many month-end reconciliations. If an investigation needs a message that completed three weeks ago, it will no longer be in the dashboard list by default; decide now whether to lengthen retention or keep the evidence elsewhere.

Who monitors, with what

SAP documents four monitoring options, and they do not see the same things:

The last row matters most. If central IT watches only Cloud ALM, a message stuck in Not Started is invisible, and the “Order locked in ERP” case can look Completed while the ERP was never updated.

What to check: a named person reviews the Integration Message Dashboard for each plant on a fixed cadence, failure notifications are switched on for every message type that moves quantity, cost or quality, and Cloud ALM is treated as a complement, not a replacement. When an incident needs SAP, the integration support component is MFG-DM-ME-INT, and raising it requires an S-user (SAP Note 3323881). Know who holds that S-user before the night shift needs it.

“It keeps working when the ERP is down”: read the scope

SAP states that DM floor stock management supports mistake proofing and maintains high availability even when the ERP is down. Read the scope exactly: that statement is about floor stock management, not about the whole loop, the edge deployment or every message type. It applies only to materials with inventory management enabled in the ERP. Plan your ERP-outage procedure on what is documented for your message types, not on the general impression that the floor carries on regardless.

6. Quality in the loop: inspection lots down, results up

Quality is where a loop failure turns into a customer problem. For SAP S/4HANA Cloud Public Edition, configure SAP_COM_0522 and the quality master data for an in-process inspection lot (type 03), including a base sample quantity of 1. Releasing the order in S/4HANA creates the lot and transfers its characteristics; release it separately in DM for shop-floor work. Operators record results in the Order POD, Work Center POD or Operation Activity POD, and conditional characteristics, which apply after an acceptance or rejection, are supported for production orders. To synchronise recorded results back to S/4HANA, configure SAP_COM_0318 and the quality inspection plugins in the chosen POD. SAP says synchronisation follows completion of an operation activity.

SAP also documents inspection-characteristic transfer and result recording for SAP ERP and SAP S/4HANA. Their prerequisites differ from the Public Edition communication arrangements described above; confirm the procedure for your edition before applying it.

The lock after release

In the standard integration, inspection-lot updates are locked once a production order is released in DM: later changes made in the ERP are not communicated. SAP documents the lock, and the override below, for discrete-industry production orders processed in POD 2.0, with the SAP ERP or SAP S/4HANA inspection-characteristics transfer setup as a prerequisite; the page does not state whether it covers SAP S/4HANA Cloud Public Edition. The plant consequence is direct. A quality engineer adds a characteristic in the ERP after release, believes the floor is now measuring it, and the floor never sees it.

SAP documents a setup that lifts the lock for two scenarios made through transaction CO02, in the same discrete, POD 2.0 scope:

• Adding characteristics to an existing operation needs SupportChangeAfterRelease = True in the custom XSLT of the “Production Order Download (LOIPRO05 V2)” integration flow.
• Adding a new inspection operation additionally needs the AutoTriggerChangeProduction element uncommented in that XSLT.

Both also need the master-data settings in SAP Note 3335254: routing Quantity Validation = Yes and output material Autocomplete and Confirm = Yes. Adding an operation resets non-completed SFCs to In Queue, so do it with the line supervisor in the room, not as a background change. For SFCs already completed, SAP says results for added characteristics cannot be recorded in the user interface and must go through the Quality Inspection API.

What to check: whether your quality team changes inspection plans after release, how often, and whether the override is configured or a manual procedure exists. Owner: the quality manager, with the integration lead.

7. Genealogy and OEE inputs

Traceability and OEE are both reconstructions. They are only as good as the events captured at Level 3 at the moment work happened. Once the shift is over, an event that was never captured in DM, or never sent to the ERP, may not be recoverable from either system.

Genealogy: what SAP DM records

The inventory ID is a unique identifier for a specific instance of material consumed or manufactured, and SAP calls it “a key record for genealogy”. It is generated when inventory is transferred from the ERP, when work on an SFC is completed in the POD (where it equals the SFC, except in consolidated mode), on goods receipt, or when floor stock is received. The SFC Report app then shows, per SFC (or per charge in process industries), the production log, component consumption including non-BOM components, traceability copies through split, merge, serialize and relabel, nonconformances, data collection, tooling, work-instruction views and electronic signatures. It can print a Product Genealogy and a Product History PDF.

Two documented boundaries define where the record of genealogy lives:

• Systems of record differ. SAP S/4HANA or SAP ERP is the system of record for inventory management; SAP DM is the system of record for floor stock management. A recall query must know which one to ask.
• Some consumption lives only in DM. With order-specific consumption, where movement type 261 is posted in the ERP, the stock is already consumed there. DM creates an inventory ID reserved for that order, and its consumption during assembly is not reported back to the ERP. SAP also notes that some transactions, such as goods issue 261, cannot be tracked in the ERP or EWM, whereas DM logs them with quantities at SFC level for genealogy.

For serialised materials there is one more trap. IDoc INVCON03 does not support serial numbers by default; transferring stock for serialised materials needs a serial-number segment under E1ICIT in an extended IDoc, plus customising (SAP Note 3452935).

What to check: pick one shipped serial or batch from last month and rebuild its genealogy from the SFC Report alone. If you cannot, find which event was never captured. Owner: the quality or traceability lead.

OEE: SAP’s formula and its caveats

DM calculates OEE as Availability x Performance x Quality. Availability compares productive time with expected productive time. Performance compares the time needed to produce good and bad items with the time at designed speed. For Quality, SAP divides value operating time by net operating time. In SAP’s worked example both times use the same standard rate, so four good items out of six give a Quality KPI of 66.6%. Check the standard rate that was maintained before execution started, alongside the underlying yield and scrap counts; rates added later are not considered in that calculation.

The caveats SAP documents are where plant OEE goes wrong:

• With no shift configured, shift duration is taken as 24 hours.
• Only one shift interval is considered; day overrides and shift calendar rules are ignored.
• SFC operations run outside any shift are treated as open and distort future shifts. SAP recommends a continuous shift without gaps or overlaps.
• The OEE calculations do not consider hold and resume, sign-off, cancellation, active buyoffs or dispositioned SFCs. For hold and resume and sign-off, SAP spells out the effect: OEE “consider[s] such SFCs as active until the operation activity is completed”, which affects the Performance KPI.

A plant that runs several shifts, uses day overrides for holidays and puts SFCs on hold at every quality stop can get an OEE figure that does not match how the plant actually ran. SAP documents each of these caveats. Agree the definition before anyone is measured on it, rather than treating it as a dashboard defect.

The register adds generic checks that are plant practice, not SAP behaviour: each equipment signal that feeds OEE, such as counts, run state and downtime reasons, needs a named owner and a sample comparison against a manual count.

8. Master data fitness: the quiet failure

Master-data errors can distort the loop without an interface failure. An order may download and a confirmation may post while its routing, material settings or BOM are wrong.

The facts already in this guide show how much rides on it:

• Routings decide reporting. Activity confirmation needs a routing with at least one ERP reporting step and a work centre with a standard value key; planned-order scrap attributes to the next reporting step; serial reporting works best with the last operation as a reporting step (section 4).
• Material settings decide behaviour. The “Auto complete and confirm” flag decides discrete or process handling (section 3), and the quality override needs it set on the output material (section 6).
• BOMs guide execution and genealogy checks. For S/4HANA Cloud Public Edition, DM builds the order-specific BOM from the transferred order. An incorrect ERP BOM can misdirect execution; compare it with the components actually recorded as assembled or consumed in the SFC Report, including non-BOM components. SAP also documents local BOM and routing overrides in DM, and changes made there are not reflected back to the ERP, so record which system owns each BOM and routing.
• Plant identity must be unique. Plant names must be unique across ERP systems at client level; otherwise plant mapping is required (section 3).
• Control keys decide postings. Serial and batch transfer needs control keys that allow confirmations but not automatic goods receipt (section 4).

Treat these as owned data with a review cadence, not as configuration. For each item, name the owner and the test that proves it right: a routing checked against the line as it runs, a BOM against what operators assemble, standard values against measured times. For a broader data-maturity effort, the digital maturity assessment gives a way to rate evidence rather than confidence.

9. Where AI fits in the loop

A scrap-prediction model trained on confirmations reported at the last operation learns where scrap was booked, not where it happened. A downtime model trained on a misconfigured shift learns the configuration. So the first AI decision is not which model, but which data-fitness gates a use case must pass before it is funded:

• Granularity gate: the confirmations the use case needs are reported at the operation level it assumes.
• Completeness gate: failed and In Process messages for the period are resolved, not retried blind, and none had left the dashboard list before reconciliation.
• Definition gate: OEE, scrap and labour definitions are written down and match how DM actually calculates them.
• Traceability gate: the genealogy test in section 7 passes for a sample of real product.

What SAP documents about AI in DM today

We found three AI-related items in SAP’s DM documentation as of October 2026:

• Joule in SAP DM is opened from the shell bar and gives conversational access to information about DM. SAP describes it as drawing on the product documentation published on the SAP Help Portal; we found no SAP statement that it acts on plant data. Onboarding is through SAP Note 3506025, conversations expire after 15 minutes of inactivity, and SAP cautions users to review Joule’s output before using it.
• Visual inspection supports manual and machine-learning-based inspection: trained models uploaded through Manage Machine Learning Models classify SFC images as conformant or nonconformant and map defects to nonconformance codes, and results can be confirmed or rejected to build qualified training data. The page carries a caution: “In a future release, this capability will be deprecated.” No date and no successor are named. Do not start a new dependency on it without that answer from SAP.
• Premium AI features are gated: they need an additional entitlement and authorisation; SAP directs customers to their account executive.

We found no primary SAP source for predictive quality in DM or for a generally available shop-floor AI agent, so this guide claims neither. For how to read SAP’s wider AI status labels, see SAP AI Needs a Status Ledger; for an introduction to the AI themes around the product, see our article on SAP Digital Manufacturing and AI.

The hand-off

Once the loop is sound, the next question is how much authority an AI system should have over the plant: whether it observes, recommends or acts, and what independent boundary protects production, quality and safety state. That is the subject of our companion paper, AI on the Factory Floor. This guide makes the data trustworthy; that paper decides what the model may do with it.

10. Run the loop register

The free SAP manufacturing loop register turns this guide into a working session. It lists checks grouped by the six loop stages covered here: orders down, confirmations up, ERP-unreachable handling, quality, genealogy and OEE inputs, and master data. For each check your team records:

• Status: Met, Partial, Gap or Not applicable. Use Not applicable for checks outside your edition or configured scope, and record the reason in Notes. Base the status on evidence you can show, not on confidence.
• Owning system: S/4HANA, SAP DM, Cloud Integration, the equipment layer or the plant process. The register pre-fills it; change it if your landscape differs.
• Owner: a named person, not a department.
• Notes: the test, report or configuration that proves the status.

The output is a gap list, Gaps first and then Partials, not a score. A gap on a check that moves quantity, cost or quality, such as an unimplemented redistribution BAdI, an unwritten In Process retry rule or a quality lock nobody knows about, outranks any number of Partials on reporting convenience. No average hides a failed check.

Run it with three people in the room: the plant’s operations lead, the ERP or integration lead and the quality manager. Gaps can sit between two of them, which is one reason they stay open.

Download the SAP manufacturing loop register (XLSX), with the checks, status choices, owner columns and a gap list that puts Gaps first, then Partials. Use the open CSV register when a portable tabular format is preferable.

The one thing to do after reading: ask your integration lead to show you, today, the Integration Message Dashboard for your plant, filtered to Failed and In Process, and who is responsible for each line on it.

Next step: Book a free SAP assessment. Altivate can review your loop register with your plant and integration teams and help you decide what to fix first. See also how we approach SAP for manufacturing.

Sources and verification status

Checked October 2026. SAP Help Portal pages for SAP Digital Manufacturing carry no publication date; “documented” here means documented as current when we read the page. Edition qualifiers are SAP’s. The granularity trade-off, the data-fitness gates, the generic genealogy and OEE practice checks and the register are an Altivate synthesis, not SAP guidance.

• ISA, ISA-95 standard: ISA-95 and IEC 62264; Levels 0 to 4; SCADA among the Level 3 examples.
• ISA InTech, ISA-95 evolves to support smart manufacturing and IIoT: SCADA functions at Level 2.
• SAP Help Portal, SAP Digital Manufacturing Cloud events and webinars, 2019-2022: former product name.
• SAP Help Portal, Technical integration with SAP S/4HANA or SAP ERP: Cloud Integration for ERP-to-DM data, Cloud Connector calling ERP BAPIs for DM-to-ERP data.
• SAP Help Portal, Integration with SAP S/4HANA Cloud Public Edition: no SAP Cloud Integration or Cloud Connector; communication arrangements.
• SAP Help Portal, User-defined customizing options: custom integration flows in place of the standard package.
• SAP Help Portal, Enable direct communication to SAP S/4HANA: direct OData scenarios that bypass Cloud Integration.
• SAP Help Portal, Order processing mode: local BOM and routing overrides; DM changes not reflected back to the ERP.
• SAP Help Portal, Transferring a process order, S/4HANA Cloud Public Edition: SAP_COM_0522 for order integration.
• SAP Help Portal, SAP DM integration with SAP S/4HANA: order and confirmation flow: order download, yield and scrap confirmation, the discrete and process flag, the RMES release notification and BAdI CO_MES_INT_REDISTRIBUTION.
• SAP Help Portal, Integration prerequisites and the Cloud Integration package: system IDs, plant names, business functions, the package, SAP Notes 3050090, 3315636 and 3549024, the Neo deprecation.
• SAP Help Portal, Production order activity confirmation: prerequisites and directive mapping.
• SAP Help Portal, Direct labour confirmation: S/4HANA Cloud Public Edition, SAP_COM_0522.
• SAP Help Portal, Planned order scrap confirmation: Log NC and the next-reporting-step rule.
• SAP Help Portal, Work in Process – Event-Based, SAP S/4HANA Cloud: WIP driven by goods issue, activity confirmation and receipt.
• SAP Help Portal, Inspection characteristics: in-process lots, S/4HANA Cloud Public Edition.
• SAP Help Portal, Inspection results recording, S/4HANA Cloud Public Edition: SAP_COM_0318, synchronisation after an operation activity.
• SAP Help Portal, Inspection characteristics, SAP ERP or SAP S/4HANA and results recording, SAP ERP or SAP S/4HANA: separate pages; prerequisites differ from Public Edition.
• SAP Help Portal, Updating inspection lots after release (production order): the lock after release, the CO02 override, SAP Note 3335254 and the Quality Inspection API note; prerequisite is the SAP ERP or SAP S/4HANA inspection-characteristics setup.
• SAP Help Portal, PRT assignment: material PRTs only, S/4HANA Cloud Public Edition.
• SAP Help Portal, Integration Message Dashboard and message status: statuses, queued scope, retry caution, 2-week retention, CPI Async Mode, Overall and DM Integration Status.
• SAP Help Portal, Monitoring integration messages: the four monitoring options, message-level retry, the Cloud ALM Not Started gap; and monitoring integration messages: Fetch CPI Logs scope, Public Edition messages processed directly in DM.
• SAP Help Portal, Edge database, edge Kafka and Production Connector with edge services: database, Kafka, Kubernetes and Helm, certificates, Cloud Connector.
• SAP Help Portal, Production Connector on edge and edge web server: edge module, OPC UA scenarios, client certificates for the Windows installation only.
• SAP Help Portal, Goods Receipt plugin: prerequisites, by-product backflush, directives.
• SAP Help Portal, Cancelling goods receipts: supported and unsupported cancellation scenarios.
• SAP Help Portal, Serial and batch numbers of semi-finished components: message types, movement type 261, time-based components.
• SAP Help Portal, Floor stock integration and floor stock management: systems of record, order-specific consumption, INVCON03 and SAP Note 3452935, the ERP-down statement and its scope.
• SAP Help Portal, Inventory ID and SFC Report: genealogy records and reports.
• SAP Help Portal, OEE calculations, Quality KPI and Performance KPI: formula, Quality KPI worked example, standard rate maintained before execution, shift caveats.
• SAP Help Portal, Visual inspection and Joule in SAP Digital Manufacturing: capability, deprecation caution, premium entitlement, Joule scope and expiry.
• SAP Help Portal, Support components: MFG-DM-ME-INT and the other components; SAP Note 3323881.
• Not confirmed in a primary SAP source as of October 2026: maintenance-order integration between DM and S/4HANA, end-of-maintenance dates for SAP ME and SAP MII, high availability for DM for edge computing, guaranteed queueing for every message type while the ERP is unreachable, predictive quality or a generally available shop-floor AI agent in DM, and edition coverage beyond what each page states.