.png)
SAP Digital Manufacturing Integration Guide
Connect SAP Digital Manufacturing with enterprise applications through REST and OData APIs, selected event-driven capabilities, OAuth 2.0, and orchestrated Martini workflows.
SAP Digital Manufacturing integration options at a glance
SAP Digital Manufacturing primarily integrates through documented REST and OData APIs for production orders, SFCs, materials, resources, operations, and routings. Selected event-driven scenarios can use SAP eventing capabilities, including SAP Event Mesh, although coverage depends on the product configuration and event model. Some APIs may provide pagination, OData batch requests, or asynchronous processing, which must be confirmed per service. API access generally uses SAP BTP OAuth 2.0 client credentials, tenant-specific URLs, roles, scopes, and service configuration. Martini can schedule incremental synchronization, consume APIs, process supported event notifications, map manufacturing data, validate state transitions, and expose APIs for downstream applications.
| Integration point | Supported by SAP Digital Manufacturing? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST and OData APIs | Yes | SAP Digital Manufacturing exposes documented REST and OData-style APIs for production orders, SFCs, materials, resources, operations, routings, and execution data. APIs may support filtering, paging, and structured JSON responses. | Martini can consume REST APIs from workflows, manage authentication, map and validate responses, apply business rules, and expose normalized APIs for downstream systems. |
| Event notifications and SAP Event Mesh | Limited | Selected production, execution, or business events can be published through SAP eventing capabilities, including SAP Event Mesh-related patterns. Coverage depends on the enabled event model and tenant configuration. | Martini can process supported event notifications, correlate events with SAP object identifiers, retrieve complete state through APIs, and apply deduplication and retry logic. |
| Bulk, batch, and asynchronous processing | Limited | Selected OData services may provide batch requests, paging, or asynchronous processing. Support must be verified for the specific Digital Manufacturing API rather than assumed universally. | Martini can implement paginated and checkpointed workflows, use documented batch behavior where available, and control concurrency for high-volume synchronization. |
| OAuth 2.0 and SAP BTP authentication | Yes | Server-to-server access generally uses OAuth 2.0 client credentials with SAP BTP service configuration, tenant-specific authorization URLs, client credentials, roles, role collections, and scopes. | Martini can securely manage environment-specific credentials, obtain access tokens, invoke tenant-specific endpoints over HTTPS, and keep secrets outside workflow logic. |
| Scheduled synchronization | Yes | Polling is appropriate for incremental synchronization of Production Orders, SFCs, Materials, Resources, Operations, and Routings when event coverage is unavailable or incomplete. | Martini can start workflows on a schedule, follow pagination, apply modification filters, persist checkpoints, and retry transient failures. |
| File and attachment APIs | Not confirmed | A general-purpose file or attachment API for all SAP Digital Manufacturing objects was not confirmed. Specific manufacturing functions or adjacent SAP services may support file exchange. | Martini can process files when a documented SAP endpoint or approved adjacent service is confirmed, but the integration should not assume a universal Digital Manufacturing file interface. |
| Direct database and analytics access | Not confirmed | Direct access to the underlying Digital Manufacturing persistence layer is not a recommended integration mechanism. Analytics and export capabilities may exist in related SAP services. | Martini should use documented operational APIs, events, or supported SAP data services rather than relying on direct database access. |
How SAP Digital Manufacturing exposes data and business events
SAP Digital Manufacturing REST and OData APIs
SAP Digital Manufacturing provides documented REST-based APIs and OData-style resources for manufacturing data and operations. Depending on the API, collections may support filtering, paging, structured JSON responses, and selected batch or asynchronous behavior.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with SAP BTP OAuth 2.0, calls the tenant-specific API, follows pagination, maps the response into a canonical manufacturing model, applies validation and state rules, and writes the result to the target system. The workflow records checkpoints and routes transient and business errors separately.
Implementation sequence
SAP Digital Manufacturing event notifications
SAP Digital Manufacturing supports selected event-driven scenarios through SAP eventing capabilities, including SAP Event Mesh-related patterns. Event availability, delivery behavior, and payload detail depend on the configured event model; generic webhooks for every object should not be assumed.
Martini implementation pattern
Martini implementation pattern: receive a supported event through the configured event integration, validate its identity and delivery metadata, deduplicate it, and call the relevant SAP API when the event does not contain complete object state. Martini then transforms the current state and routes it to downstream applications.
Implementation sequence
SAP Digital Manufacturing batch and scheduled synchronization
Selected APIs may support OData batch requests, asynchronous processing, or standard pagination, while scheduled polling remains a practical option when event coverage is incomplete. The exact behavior must be confirmed for each API.
Martini implementation pattern
Martini implementation pattern: a scheduler starts an incremental workflow, retrieves pages using a stable change criterion, controls concurrency, and uses batch behavior only where documented. The workflow commits checkpoints after successful processing and retries transient failures without reprocessing completed business objects.
Implementation sequence
Common SAP Digital Manufacturing integration patterns
Pattern 1: Synchronize production orders to Digital Manufacturing
When to use this pattern
Use this pattern when SAP S/4HANA or SAP ECC is the enterprise source for released Production Orders and SAP Digital Manufacturing is the shop-floor execution target. It supports incremental order creation or updates while protecting manufacturing state and data quality.
Integration direction
Example Mapping
| SAP Digital Manufacturing Field | Canonical Field | Target Field |
|---|---|---|
| ProductionOrder | productionOrderId | Production Order identifier |
| Material | materialId | Material |
| Quantity | plannedQuantity | Order quantity |
| Operations | operations | Operations and routing structure |
Martini implementation pattern
A scheduled Martini workflow retrieves changed orders using documented filters and pagination, maps materials, quantities, dates, operations, and routings, validates units and plant identifiers, and creates or updates the corresponding SAP Digital Manufacturing data. It uses source and target IDs for idempotency, persists checkpoints, and routes rejected orders or transient API failures for retry and review.
Martini capabilities used
- workflows
- API consumption
- OAuth 2.0 configuration
- data mapping
- business rules
- error handling
Pattern 2: Synchronize SFC execution status to enterprise systems
When to use this pattern
Use this pattern when shop-floor execution status must update SAP S/4HANA, SAP EWM, reporting services, or other operational applications. Selected event notifications can reduce polling, but the current SFC state should be retrieved when event payloads are incomplete.
Integration direction
Example Mapping
| SAP Digital Manufacturing Field | Canonical Field | Target Field |
|---|---|---|
| SFC | shopFloorControlId | SFC or execution reference |
| Status | executionStatus | Production execution status |
| Quantity | completedQuantity | Confirmed quantity |
| Operation | operationId | Operation reference |
Martini implementation pattern
Martini receives a supported event or polls changed SFCs, correlates the SFC with its Production Order and Operation, retrieves complete details when needed, and applies valid-state and quantity rules before updating the target. Duplicate event identifiers and source object keys protect against repeated confirmations, while transient failures use controlled retries.
Martini capabilities used
- event-driven workflows
- API consumption
- data mapping
- deduplication
- business rules
- retry handling
Pattern 3: Synchronize materials and resources
When to use this pattern
Use this pattern when SAP S/4HANA, SAP ECC, or another approved master-data source must keep Materials and Resources aligned with SAP Digital Manufacturing. It is useful for preventing incomplete or incompatible definitions from reaching production execution.
Integration direction
Example Mapping
| SAP Digital Manufacturing Field | Canonical Field | Target Field |
|---|---|---|
| Material | materialId | Material identifier |
| UnitOfMeasure | baseUnit | Base unit |
| Resource | resourceId | Resource identifier |
| Plant | siteId | Site or plant |
Martini implementation pattern
A Martini workflow retrieves changed master data, maps SAP identifiers, units, plants, and statuses, validates required fields and relationships, and upserts approved Materials or Resources. Invalid definitions are rejected with actionable errors, while checkpoints and source keys prevent duplicate processing.
Martini capabilities used
- scheduled workflows
- API consumption
- mapping and transformation
- validation
- upsert logic
- audit logging
Pattern 4: Escalate manufacturing exceptions
When to use this pattern
Use this pattern when production, execution, or quality-related conditions should create an operational case or notification. Examples include repeated operation failures, prolonged exception states, or nonconforming production results requiring review.
Integration direction
Example Mapping
| SAP Digital Manufacturing Field | Canonical Field | Target Field |
|---|---|---|
| ProductionOrder | productionOrderId | ServiceNow correlation field |
| SFC | shopFloorControlId | Incident reference |
| Resource | resourceId | Configuration or asset reference |
| Status | exceptionStatus | Incident state and priority |
Martini implementation pattern
Martini consumes selected SAP data or events, enriches the exception with the related Production Order, SFC, Operation, and Resource, evaluates severity rules, and creates or updates a ServiceNow incident. Correlation keys prevent duplicate cases, and failed writes are retried or placed in an operational error route.
Martini capabilities used
- event and API workflows
- data enrichment
- business rules
- API exposure and consumption
- deduplication
- error routing
Applications commonly integrated with SAP Digital Manufacturing
SAP Digital Manufacturing is commonly positioned alongside SAP planning, ERP, warehouse, eventing, analytics, and operational applications. Martini can orchestrate these relationships through documented SAP APIs and supported event mechanisms, while keeping mappings, validation, retries, and downstream interfaces in reusable workflows.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Synchronize production orders, materials, routings, confirmations, inventory information, and manufacturing execution status between enterprise planning and shop-floor execution. | SAP S/4HANA → Martini → SAP Digital Manufacturing | Use scheduled or API-triggered Martini workflows to retrieve changed production data, map SAP identifiers and quantities, validate manufacturing state, upsert the corresponding objects, and record synchronization checkpoints and failures. |
| SAP ERP Central Component (SAP ECC) | Connect established SAP ERP production planning, material master, inventory, and order processes with Digital Manufacturing execution. | SAP ERP Central Component (SAP ECC) → Martini → SAP Digital Manufacturing | Consume the available SAP APIs or integration endpoints, transform legacy ERP structures into the Digital Manufacturing model, apply unit and plant validation, and route rejected orders to an operational error process. |
| SAP Extended Warehouse Management (SAP EWM) | Coordinate component staging, goods movements, consumption, and finished-goods handling with production execution. | SAP Digital Manufacturing → Martini → SAP Extended Warehouse Management (SAP EWM) | Process relevant production or material events and API responses in Martini, correlate them with warehouse identifiers, apply movement rules, and send validated updates to the supported EWM interface with retry and duplicate protection. |
| SAP Integrated Business Planning (SAP IBP) | Align production execution results, constraints, and operational status with supply and production planning processes. | SAP Integrated Business Planning (SAP IBP) → Martini → SAP Digital Manufacturing | Run controlled synchronization workflows that transform planning quantities, materials, dates, and execution feedback, apply site-specific business rules, and maintain checkpoints for incremental exchange. |
| SAP Analytics Cloud | Provide reporting on production performance, order status, resource utilization, quality-related activity, and operational KPIs. | SAP Digital Manufacturing → Martini → SAP Analytics Cloud | Retrieve approved operational data through supported SAP APIs or data services, normalize timestamps and manufacturing identifiers, enrich the payload, and publish it through a controlled API or downstream data exchange. |
| SAP Event Mesh | Distribute selected manufacturing events to downstream applications and integration workflows without relying only on polling. | SAP Digital Manufacturing → SAP Event Mesh → Martini | Consume supported event notifications through the configured eventing mechanism, correlate each event with the current manufacturing object when necessary, retrieve complete details through an API, and process duplicates safely. |
| ServiceNow | Create incidents or operational cases for manufacturing exceptions, prolonged execution failures, or equipment-related issues. | SAP Digital Manufacturing → Martini → ServiceNow | Use a Martini workflow to evaluate selected production or quality-related conditions, enrich the exception with Production Order, SFC, Operation, and Resource information, and create or update a ServiceNow incident with retry handling. |
| Microsoft Power BI | Combine manufacturing execution data with operational and business reporting. | SAP Digital Manufacturing → Martini → Microsoft Power BI | Expose normalized manufacturing data through a Martini API or deliver it through an approved intermediate data service, applying incremental extraction, field mapping, timestamp normalization, and monitoring. |
How to build a SAP Digital Manufacturing integration in Martini
Objective
Establish tenant-specific SAP Digital Manufacturing access using the OAuth 2.0 client-credentials flow and the roles, scopes, destinations, and service configuration required by each API.
Instructions in Martini
- Create or obtain the SAP BTP OAuth client and required service configuration
- Store client credentials and tenant URLs as secure environment configuration
- Confirm API-specific roles, scopes, and service entitlements
- Test HTTPS access against a non-production tenant
Objective
Select scheduled polling, an inbound API request, or a supported SAP event mechanism based on the required latency and confirmed event coverage.
Instructions in Martini
- Use a scheduler for incremental synchronization when events are unavailable
- Use a supported event path for selected production or execution events
- Use a Martini API when another application needs to initiate processing
- Document the event type, replay behavior, and source identifier
Objective
Request the required SAP Digital Manufacturing objects while respecting pagination, filtering, API permissions, and any documented batch or asynchronous behavior.
Instructions in Martini
- Retrieve Production Orders, SFCs, Materials, Resources, Operations, or Routings through documented APIs
- Follow the API pagination mechanism
- Use stable incremental criteria and store a checkpoint
- Avoid assuming a universal bulk endpoint
Objective
Coordinate API calls, event processing, enrichment, validation, target writes, and persistence of processing state in a maintainable Martini workflow.
Instructions in Martini
- Correlate related manufacturing objects by stable identifiers
- Retrieve current state when event payloads are incomplete
- Separate business validation failures from transient transport failures
- Control concurrency for high-volume processing
Objective
Transform SAP-specific payloads into the target application model while enforcing manufacturing, unit, quantity, plant, resource, and state-transition rules.
Instructions in Martini
- Map SAP identifiers to canonical and target fields
- Normalize quantities, units, timestamps, and time zones
- Validate required fields and object relationships
- Reject invalid or stale state transitions with actionable error details
Objective
Create, update, or publish validated results to enterprise applications such as SAP S/4HANA, SAP EWM, ServiceNow, or analytics services.
Instructions in Martini
- Use upsert or equivalent operations where supported
- Include source identifiers and correlation keys
- Apply downstream business rules before committing changes
- Record the target response and synchronization status
Common SAP Digital Manufacturing data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Production Orders | Synchronize released manufacturing orders, quantities, materials, dates, routings, operations, and execution status. | SAP S/4HANA, SAP ECC, SAP EWM, planning and analytics applications | Martini retrieves or receives relevant order data, maps identifiers and quantities, validates state transitions, performs create or update operations, and stores correlation and checkpoint data. |
| SFCs | Track shop-floor control units, quantities, operations, statuses, and execution history. | SAP S/4HANA, SAP EWM, ServiceNow, analytics applications | Martini processes API responses or selected event notifications, correlates SFCs with Production Orders and Operations, deduplicates updates, and routes exceptions. |
| Materials | Synchronize products, components, units of measure, and manufacturing reference data. | SAP S/4HANA, SAP ECC, SAP EWM, planning systems | Martini maps material identifiers, units, descriptions, and lifecycle fields, validates required attributes, and applies source-of-truth rules before writing targets. |
| Resources | Represent machines, work centers, production assets, and other operational resources. | SAP S/4HANA, analytics platforms, operational applications | Martini synchronizes resource identifiers and attributes, applies plant and status rules, and maintains source-to-target correlation keys. |
| Operations | Represent routing steps, activities, resources, work instructions, and execution information. | SAP S/4HANA, SAP EWM, ServiceNow, reporting systems | Martini maps operation sequence and status data, validates relationships to Routings and Resources, and prevents invalid or stale execution updates. |
| Routings | Define the sequence and structure of manufacturing operations used to produce a Material. | SAP S/4HANA, SAP ECC, planning and execution systems | Martini transforms routing structures, validates operation and resource references, and synchronizes changes incrementally with version and effective-date controls where available. |
Authentication and security considerations
OAuth 2.0 and SAP BTP configuration
SAP Digital Manufacturing API access generally uses OAuth 2.0 client credentials through SAP BTP. Access also depends on tenant-specific service configuration, destinations, roles, role collections, scopes, and entitlements.
Secure Martini configuration
- Store client IDs, client secrets, authorization URLs, and tenant endpoints as secure environment configuration.
- Use HTTPS and restrict API permissions to the scopes required by each workflow.
- Separate development, test, and production credentials and tenants.
- Do not write access tokens or client secrets to workflow logs.
Operational considerations for SAP Digital Manufacturing integrations
Pagination and throttling
Follow the documented pagination model and use bounded concurrency. Apply exponential backoff for transient failures, including HTTP 429 and temporary 5xx responses, rather than assuming a universal SAP Digital Manufacturing rate limit.
State and idempotency
Use Production Order, SFC, Material, Resource, Operation, and event identifiers as correlation keys. Maintain checkpoints or a processing ledger so retries do not create duplicate confirmations, incidents, or status changes.
Manufacturing validation
Validate state transitions, quantities, units of measure, plant and resource references, timestamps, and relationships between Routings and Operations before writing updates.
Lifecycle and observability
Pin documented API versions where possible, test changes in a non-production tenant, monitor schema changes, capture SAP error payloads and correlation identifiers, and retain replayable business context without exposing secrets.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than an API call
Point-to-point scripts often combine authentication, pagination, mapping, state rules, retries, and logging in code that is difficult to reuse. Martini separates these concerns into workflows, APIs, mappings, reusable logic, and secure configuration.
Support changing manufacturing processes
Martini can combine scheduled API synchronization with selected event-driven processing, enrich SAP data, apply business rules, and expose stable interfaces to downstream applications without making each consumer understand SAP-specific details.
Improve operational control
- Centralize retry, duplicate handling, validation, and error routing.
- Keep mappings and environment-specific credentials manageable across deployments.
- Monitor workflow outcomes and preserve correlation information for troubleshooting.
- Extend integrations with custom logic when the documented API behavior requires it.
Frequently asked questions
SAP Digital Manufacturing can be integrated primarily through documented REST and OData APIs, with selected event-driven scenarios using SAP eventing capabilities such as SAP Event Mesh. OAuth 2.0 through SAP BTP is generally used for server-to-server access. Scheduled workflows, incremental synchronization, and API-based orchestration are appropriate when event coverage is incomplete.
Yes. Martini can consume SAP Digital Manufacturing REST and OData APIs, authenticate with SAP BTP OAuth 2.0, process supported event notifications, schedule synchronization, transform manufacturing payloads, expose downstream APIs, and implement validation, deduplication, retries, and error routing.
No dedicated SAP Digital Manufacturing connector is required. Martini can integrate using the product's confirmed native REST and OData APIs, OAuth 2.0 authentication, scheduled workflows, and selected event-driven mechanisms such as SAP Event Mesh where configured.
Lonti does not charge an additional per-connector or per-vendor fee to integrate SAP Digital Manufacturing. The integration is subject to the provisioned capacity of the Martini environment. Separate SAP, SAP Event Mesh, cloud infrastructure, or other third-party costs may apply based on licensing, usage, and deployment model.
REST and OData APIs are the primary recommended mechanisms for new integrations. Use documented filtering, paging, and API-specific batch or asynchronous features where available. Selected event-driven scenarios can use SAP eventing capabilities, but GraphQL, SOAP, and a universal file or database interface should not be assumed.
Selected event-driven integrations are available through SAP eventing capabilities, including SAP Event Mesh-related patterns. This is not blanket webhook coverage for every object or state transition. The event type, delivery mechanism, retention, replay behavior, and payload completeness must be confirmed for the specific tenant and use case.
Martini can run scheduled or event-driven workflows that retrieve Production Orders, SFCs, Materials, Resources, Operations, or Routings, follow pagination, map SAP fields to a canonical model, validate manufacturing rules, and write target updates. Checkpoints, source identifiers, and processing ledgers support incremental and idempotent synchronization.
Yes. Martini can expose a controlled REST API that abstracts SAP-specific endpoints from downstream applications. The façade can authenticate callers, apply authorization and business rules, translate request and response models, orchestrate SAP API calls, and return consistent errors without granting every consumer direct SAP access.
Related Martini documentation
API Workflows
Data Processing
Security Operations
Connect SAP Digital Manufacturing with Martini
Use Martini to build maintainable SAP Digital Manufacturing integrations across production execution, enterprise planning, warehouse operations, event processing, and analytics.