SAP Digital Manufacturing
SAP's manufacturing execution system for running production on the shop floor, run by SAP as software as a service. The product behind the SAP Digital Manufacturing door: what is entered there is what people build for it, such as plugins for its Production Operator Dashboard, and the product itself is not an option.
Where it sits
Used by
Required dependency. The product the plugin runs in: the extension is uploaded into a DM tenant and the widget is placed on a panel in the POD Designer.
Functional boundary
The proxy URL is a widget property the browser calls, so the [EdgeFlow Proxy API](external:cogniac-edgeflow-proxy) has to be reachable from the SAP DM client itself, on a local network and over HTTPS: its own repository asks for a certificate the browser trusts and documents generating one for the Pi's LAN IP. NC logging needs an SFC selected in the work list: without one the request is rejected with an error message.
LicenceNeither the package manifest nor the repository tree declares a licence
Required dependency. The product whose POD 2.0 configuration it writes: the run starts from a Manage PODs 2.0 export or a bundled SAP template, and the result is imported back into Manage PODs 2.0, where the Production Process placeholders are resolved in the designer.
Functional boundary
A requirement that needs code: the skill generates configuration and states that it says so instead of faking it. Dialog and container targets have no verified enter event, so a dashboard placed there loads only through its Refresh button. Production Processes are outside it — it wires PODs to them and does not design them.
Optionally used: the REST API specification and MDO entity tools are used; the server starts without the specifications and the tools that need them say which step is missing the licensed release whose REST OpenAPI specifications and MDO Extractor metadata are tenant-bound content the repository does not redistribute, loaded locally before those tools answer
Functional boundary
Three of its five reference corpora are not shipped: without an api.sap.com key and session cookie, a tenant bearer token and a local SAPUI5 fetch, the REST, MDO and UI5 tools return a message naming the preparation step that is missing. The HTTP transport has no authentication until `MCP_AUTH_TOKEN` is set, so anything past localhost needs that or an authenticating reverse proxy. Packing the ZIP, uploading it through Manage POD 2.0 Extensions and placing the widget in the POD Designer stay manual steps outside the agent, and the SAPUI5 fetch defaults to the SDK's newest version, which the README says is not the version a tenant runs. Node.js 22 or newer.
Required dependency. The samples are uploaded into a Digital Manufacturing tenant and run there: a POD 1.0 plugin through the POD Designer, a POD 2.0 extension through the Manage PODs 2.0 app, and the bootcamp unit lists tenant access as a prerequisite.
Functional boundary
Nothing here runs on its own: a plugin sample needs a Digital Manufacturing tenant to be uploaded into, and the integration samples need a Cloud Integration tenant plus an ERP system, or a mock server as the outbound example uses, before they do anything.
Connected from
data. Reads the enabled primary nonconformance codes from the catalogue at widget initialisation, and logs an NC incident against the active SFC with the captured image as an attachment.
Functional boundary
The proxy URL is a widget property the browser calls, so the [EdgeFlow Proxy API](external:cogniac-edgeflow-proxy) has to be reachable from the SAP DM client itself, on a local network and over HTTPS: its own repository asks for a certificate the browser trusts and documents generating one for the Pi's LAN IP. NC logging needs an SFC selected in the work list: without one the request is rejected with an error message.
LicenceNeither the package manifest nor the repository tree declares a licence
data, outbound. Each module drives one of the product's standard applications through its standard user interface, and carries that application's name.
RepositoryThe declared repository is archived
data. the MDO Extractor entity metadata behind list_mdo_entities, get_mdo_entity and search_mdo_entities: the OData V4 $metadata document is exported from the tenant and indexed locally
Functional boundary
Three of its five reference corpora are not shipped: without an api.sap.com key and session cookie, a tenant bearer token and a local SAPUI5 fetch, the REST, MDO and UI5 tools return a message naming the preparation step that is missing. The HTTP transport has no authentication until `MCP_AUTH_TOKEN` is set, so anything past localhost needs that or an authenticating reverse proxy. Packing the ZIP, uploading it through Manage POD 2.0 Extensions and placing the widget in the POD Designer stay manual steps outside the agent, and the SAPUI5 fetch defaults to the SDK's newest version, which the README says is not the version a tenant runs. Node.js 22 or newer.
data, outbound. The samples extend the product and call its APIs: the side-by-side Assembly POD example works against the DM public APIs, and the in-app service sample fetches reason codes from the DM APIs through a destination.
Functional boundary
Nothing here runs on its own: a plugin sample needs a Digital Manufacturing tenant to be uploaded into, and the integration samples need a Cloud Integration tenant plus an ERP system, or a mock server as the outbound example uses, before they do anything.
Details
Graph
For your agent
- Ref
external:sap-digital-manufacturing- JSON
- /externals/sap-digital-manufacturing.json
- MCP
- Connecting an agent