.png)
SAP Asset Performance Management Integration Guide
Integrate SAP Asset Performance Management with enterprise applications through documented REST or OData APIs, secure authentication, scheduled workflows, and verified SAP event capabilities.
SAP Asset Performance Management integration options at a glance
SAP Asset Performance Management integrations should use the product-specific REST or OData APIs published through SAP Business Accelerator Hub and verified for the target tenant, edition, and release. Martini can authenticate with OAuth 2.0, client credentials, API-management credentials, or other documented SAP security patterns, then orchestrate retrieval and update workflows for assets, indicators, recommendations, models, and related resources. Where selected APIs support batch, asynchronous, pagination, or changed-since processing, Martini can coordinate high-volume synchronization. Event or webhook coverage is resource-specific and must be confirmed; otherwise scheduled polling can provide incremental synchronization. Direct database access is not an appropriate pattern for this managed cloud application.
| Integration point | Supported by SAP Asset Performance Management? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | SAP publishes cloud APIs for SAP Asset Performance Management resources through SAP Business Accelerator Hub. Use them to retrieve or update supported assets, models, indicators, recommendations, and related resources. | Martini can authenticate, consume the documented HTTP API, paginate responses, map payloads, apply business rules, and expose a simplified REST API for downstream consumers. |
| OData-style APIs | Yes | Selected SAP cloud APIs may use OData conventions for filtering, ordering, field selection, and pagination. Exact resource names, OData version, and query options are API-specific. | Martini can construct HTTP requests with documented OData query parameters, process response pages, transform results, and persist synchronization checkpoints. |
| Bulk / async / batch APIs | Limited | Selected SAP APIs may provide OData batch requests, asynchronous jobs, bulk import or export, or server-side pagination. Availability and limits must be confirmed for the chosen SAP APM package. | Martini can orchestrate batch submission and status polling where documented, or use bounded paginated workflows with checkpointing and partial-failure handling. |
| Authentication | Yes | SAP cloud integrations may use OAuth 2.0, client credentials, API keys, client secrets, scopes, roles, certificates, or SAP Cloud Identity Services depending on the API and deployment. | Martini stores environment-specific credentials as secrets, obtains or uses access tokens, applies required headers, and supports reusable authenticated API workflows. |
| Events / webhooks / outbound callbacks | Not confirmed | Event and notification support must be verified for each SAP APM resource, tenant, and API version. Do not assume that asset, indicator, recommendation, or strategy changes generate notifications. | If a supported callback or event endpoint is confirmed, Martini can receive it through an API workflow. Otherwise, Martini can implement scheduled polling with documented filters or timestamps. |
| Database access | No | Direct access to the managed SAP APM application database is not a documented integration approach and should not be used for application synchronization. | Martini should consume SAP-published APIs or approved SAP integration services rather than connecting to the underlying SaaS database. |
How SAP Asset Performance Management exposes data and business events
SAP APM REST APIs
SAP provides cloud APIs through SAP Business Accelerator Hub and product documentation. The specific SAP APM package, resource names, operations, API version, tenant URL, and permissions must be verified before implementation.
Martini implementation pattern
Martini implementation pattern: a workflow obtains SAP authentication, calls the documented REST resource, follows pagination or filters, maps the response to a canonical model, and writes or publishes the result to the target system. A Martini REST API can also hide SAP-specific details from consuming applications.
Implementation sequence
SAP APM OData-style APIs
Some SAP cloud APIs use OData conventions for filtering, ordering, field selection, and pagination. Supported query options and resource paths are specific to the selected SAP APM API.
Martini implementation pattern
Martini implementation pattern: construct OData-compatible HTTP requests with documented query parameters, process page links or skip and limit controls, normalize SAP values, and continue from a durable checkpoint. Unsupported query options should be rejected rather than inferred.
Implementation sequence
SAP APM batch and asynchronous processing
Selected SAP APIs may support OData batch requests, asynchronous jobs, bulk import or export, or other high-volume patterns. These capabilities are not universal across SAP APM resources.
Martini implementation pattern
Martini implementation pattern: submit a documented batch or asynchronous request, record its correlation or job identifier, poll the documented status resource, process successful and failed items separately, and retry only transient failures within defined limits.
Implementation sequence
SAP APM authentication
SAP cloud APIs may use OAuth 2.0, client credentials, API keys, client secrets, scopes, roles, certificates, or SAP Cloud Identity Services. The required combination depends on the API and tenant configuration.
Martini implementation pattern
Martini implementation pattern: keep credentials and certificates in environment-specific secrets, obtain or refresh tokens according to the configured lifetime, attach the required authorization information, and classify authentication failures separately from business or transport errors.
Implementation sequence
Common SAP Asset Performance Management integration patterns
Pattern 1: Synchronize SAP S/4HANA equipment with SAP APM assets
When to use this pattern
Use this pattern when equipment, functional-location, and asset master information must remain aligned between SAP S/4HANA Asset Management and SAP Asset Performance Management. Confirm that the selected SAP APM API supports the required asset operations before designing the write path.
Integration direction
Example Mapping
| SAP Asset Performance Management Field | Canonical Field | Target Field |
|---|---|---|
| Equipment identifier | asset.sourceId | Asset identifier |
| Technical object description | asset.name | Asset name |
| Functional location | asset.locationId | Functional location reference |
| Object status | asset.status | Asset status |
Martini implementation pattern
A scheduled Martini workflow retrieves changed SAP S/4HANA objects using documented filters, maps identifiers and technical attributes, validates mandatory organizational data, and upserts supported SAP APM assets. It stores the source and target identifiers, retries transient failures with bounded backoff, and routes unsupported operations or validation errors to reconciliation.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Send SAP APM recommendations to maintenance execution
When to use this pattern
Use this pattern when SAP APM recommendations or risk findings should become SAP S/4HANA maintenance notifications, work orders, or review tasks. Human approval can be inserted before execution when recommendations require operational review.
Integration direction
Example Mapping
| SAP Asset Performance Management Field | Canonical Field | Target Field |
|---|---|---|
| Recommendation identifier | recommendation.sourceId | External reference |
| Recommendation severity | recommendation.priority | Maintenance priority |
| Asset identifier | recommendation.assetId | Equipment |
| Recommendation status | recommendation.status | Notification status |
Martini implementation pattern
Martini retrieves recommendations through a confirmed API or scheduled query, applies severity, asset-class, and approval rules, and calls the relevant SAP S/4HANA API. Correlation IDs and source references prevent duplicate orders when a time window is retried; permanent validation errors are retained for review.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- validation
- retry and error handling
Pattern 3: Publish asset health to operational applications
When to use this pattern
Use this pattern when service, operations, or customer-facing teams need current asset health, risk, indicators, or active recommendations in applications such as ServiceNow or Salesforce.
Integration direction
Example Mapping
| SAP Asset Performance Management Field | Canonical Field | Target Field |
|---|---|---|
| Asset identifier | asset.id | Configuration item or asset reference |
| Health indicator value | indicator.value | Health value |
| Risk level | risk.level | Priority or risk |
| Recommendation text | recommendation.description | Case or task description |
Martini implementation pattern
A scheduled Martini workflow retrieves changed SAP APM resources, normalizes timestamps, units, and status values, applies target visibility and threshold rules, and writes the result to the operational application. Martini can also expose a controlled REST API for consumers that need a stable interface. Duplicate prevention uses source identifiers and current-state versus historical-data rules.
Martini capabilities used
- scheduling
- API consumption
- REST API exposure
- data mapping
- transformation
- business rules
Pattern 4: Consolidate asset performance data for analytics
When to use this pattern
Use this pattern when asset health and reliability information must be combined with maintenance, production, financial, or operational data in SAP Datasphere, SAP Analytics Cloud, or another approved data platform.
Integration direction
Example Mapping
| SAP Asset Performance Management Field | Canonical Field | Target Field |
|---|---|---|
| Asset identifier | asset.id | Asset key |
| Indicator timestamp | measurement.observedAt | Observation timestamp |
| Indicator value | measurement.value | Measure value |
| Failure criticality | risk.criticality | Criticality dimension |
Martini implementation pattern
Martini extracts supported SAP APM resources with server-side filters and pagination, validates units and timestamps, transforms payloads into the analytics model, and loads the approved ingestion endpoint. For high-volume indicators, the workflow can use documented batch or asynchronous processing; partial failures are reconciled by page, batch, or source identifier.
Martini capabilities used
- workflows
- API consumption
- pagination
- data mapping
- transformation
- validation
- reconciliation
Applications commonly integrated with SAP Asset Performance Management
SAP Asset Performance Management commonly participates in SAP intelligent asset management architectures and can also be integrated with selected operational, analytics, and service applications. Availability and direction depend on the tenant, enabled services, and APIs exposed by each product.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Exchange equipment, functional locations, maintenance notifications, maintenance orders, maintenance plans, and execution status. | SAP S/4HANA → Martini → SAP Asset Performance Management | Martini retrieves changed SAP S/4HANA asset or maintenance data, maps identifiers and technical attributes, validates required fields, and calls the documented SAP APM API. Reverse flows can deliver recommendations or status updates to SAP S/4HANA with correlation and duplicate-prevention logic. |
| SAP Business Network Asset Collaboration | Share asset master data, equipment structures, models, documents, and collaboration information across asset owners, operators, manufacturers, and service providers. | SAP Business Network Asset Collaboration → Martini → SAP Asset Performance Management | Martini orchestrates API calls between the SAP services, normalizes asset and model identifiers, applies scope and ownership rules, and records reconciliation checkpoints. Exact synchronization scope must be verified for the enabled services. |
| SAP Analytics Cloud | Present asset health, risk, reliability, and maintenance performance in analytical dashboards and planning workflows. | SAP Asset Performance Management → Martini → SAP Analytics Cloud | A scheduled Martini workflow retrieves changed indicators, recommendations, and asset status, converts timestamps and units, validates analytical dimensions, and submits the result to an approved SAP Analytics Cloud ingestion endpoint or intermediary service. |
| SAP Datasphere | Combine SAP APM information with maintenance, finance, production, supply chain, and operational datasets. | SAP Asset Performance Management → Martini → SAP Datasphere | Martini extracts supported SAP APM resources with pagination or delta filters, applies canonical mappings and data-quality checks, and loads approved ingestion endpoints. SAP-managed replication may be preferable for some high-volume scenarios. |
| SAP Integration Suite | Centralize SAP-to-SAP and SAP-to-non-SAP API mediation, transformation, eventing, monitoring, and security. | SAP Asset Performance Management → Martini → SAP Integration Suite | Martini can consume endpoints exposed by Integration Suite, or expose controlled APIs for flows managed there. Workflows handle transformation, routing, validation, error classification, and correlation across the platforms. |
| ServiceNow | Create or update incidents, service tasks, or operational cases when an asset indicator or recommendation crosses a defined threshold. | SAP Asset Performance Management → Martini → ServiceNow | Martini polls or consumes a specifically confirmed SAP notification source, applies severity and approval rules, maps the result to ServiceNow fields, and stores source recommendation identifiers to prevent duplicate cases. |
| IBM Maximo | Exchange asset, work-management, and maintenance information where SAP APM and IBM Maximo coexist. | SAP Asset Performance Management → Martini → IBM Maximo | Martini maps SAP APM assets, indicators, and recommendations to the target Maximo data model through documented APIs, applies cross-system identifier rules, and routes validation failures for reconciliation. Specific API coverage must be verified. |
| Salesforce | Surface customer- or service-relevant asset health, installed-base status, and maintenance recommendations in CRM or field-service processes. | SAP Asset Performance Management → Martini → Salesforce | A Martini workflow retrieves changed SAP APM data, normalizes health and recommendation values, applies customer visibility rules, and sends selected information to Salesforce. Returned service status can be correlated to the originating SAP identifier. |
How to build a SAP Asset Performance Management integration in Martini
Objective
Establish the SAP APM endpoint and the authentication pattern required by the selected API, tenant, and deployment configuration.
Instructions in Martini
- Confirm the SAP APM API package, tenant URL, release, and required scopes
- Configure OAuth 2.0, client credentials, API keys, or certificates as documented
- Store client secrets, tokens, and certificates in environment-specific Martini secrets
- Test authorization without exposing credentials in workflow logs
Objective
Select event-driven processing only when a specific SAP APM callback or event is confirmed; otherwise use scheduled polling with documented filters.
Instructions in Martini
- Verify event or callback support for each resource before relying on it
- Use a Martini API or webhook-oriented workflow for a confirmed inbound notification
- Use the Scheduler Trigger for polling when events are unavailable
- Define a timestamp, status, or change-marker checkpoint
Objective
Call the selected SAP APM REST or OData-style API and retrieve the required resource set reliably.
Instructions in Martini
- Apply server-side filters, field selection, and ordering where documented
- Implement pagination and preserve stable source identifiers
- Use batch or asynchronous processing only when confirmed for the selected resource
- Separate current indicator values from historical measurements
Objective
Coordinate API calls, enrichment, validation, routing, and target writes as a maintainable Martini workflow.
Instructions in Martini
- Represent the source-to-target process as a workflow with explicit stages
- Add lookups or enrichment for asset, model, and organizational references
- Route records based on status, severity, asset class, or approval state
- Maintain correlation IDs across calls and downstream operations
Objective
Convert SAP-specific payloads into a canonical model and then into the target application format.
Instructions in Martini
- Map SAP identifiers, technical attributes, statuses, and recommendation fields
- Normalize timestamps, time zones, units, decimal precision, and enumerations
- Validate mandatory fields before creating or updating target objects
- Keep mappings version-controlled and configurable by environment
Objective
Control whether a record is created, updated, ignored, escalated, or sent for human approval.
Instructions in Martini
- Define thresholds for health, risk, severity, and recommendation status
- Require approval where recommendations should not automatically create maintenance work
- Use source identifiers and external references for idempotent upserts
- Reject unsupported object operations rather than assuming UI capabilities are API capabilities
Common SAP Asset Performance Management data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Assets | Represent physical or functional assets whose health, performance, risk, and maintenance status are monitored. | SAP S/4HANA, ServiceNow, IBM Maximo, Salesforce, SAP Datasphere | Martini retrieves or updates supported asset resources, preserves SAP identifiers, normalizes technical attributes, and applies upsert and duplicate-prevention rules. |
| Asset models | Classify assets and define common attributes, indicators, or analytical structures. | SAP Business Network Asset Collaboration, SAP Datasphere, SAP Analytics Cloud | Martini maps model identifiers and attributes, validates required classifications, and synchronizes only operations confirmed by the selected API. |
| Indicators | Capture measurements or calculated values such as temperature, pressure, vibration, health, or risk indicators. | SAP Analytics Cloud, SAP Datasphere, ServiceNow, operational portals | Martini handles pagination or changed-since queries, normalizes units and timestamps, distinguishes current from historical values, and applies threshold rules. |
| Recommendations | Represent maintenance or operational recommendations generated from asset analysis, rules, engineering knowledge, or observed conditions. | SAP S/4HANA, ServiceNow, IBM Maximo, Salesforce | Martini applies severity, approval, and asset-class rules, maps recommendations to target work or service objects, and retains source IDs to prevent duplicate execution. |
| Maintenance strategies | Define preventive, predictive, or risk-based approaches for determining maintenance actions. | SAP S/4HANA, SAP Datasphere, SAP Analytics Cloud | Martini can synchronize supported strategy data, validate effective dates and status values, and route unsupported operations or schema mismatches for review. |
| Failure modes and risks | Describe possible failure modes, consequences, likelihood, criticality, and mitigation activities. | SAP S/4HANA, analytics platforms, ServiceNow, IBM Maximo | Martini transforms risk and criticality values, applies business thresholds, and maintains correlation between source risk information and downstream actions. |
Authentication and security considerations
Use SAP-approved authentication
The exact authentication pattern depends on the SAP APM API, tenant, and deployment. OAuth 2.0, client credentials, API keys, client secrets, scopes, roles, certificates, SAP Cloud Identity Services, and mutual TLS may apply in different configurations.
Protect integration credentials
- Store client IDs, client secrets, tokens, and certificates in environment-specific Martini secrets.
- Request only the scopes and business roles required by each workflow.
- Separate interactive SAML single sign-on from backend service-to-service authentication.
- Plan for token renewal, credential rotation, and tenant-specific configuration.
Operational considerations for SAP Asset Performance Management integrations
Tenant and API variation
Verify the SAP APM edition, release, tenant, API package, resource names, operations, and enabled services before implementation. An object visible in the application interface should not be assumed to be publicly available through an API.
Reliability and volume
- Implement pagination and prefer documented server-side filters, changed-since parameters, and field selection.
- Confirm quotas and throttling behavior, then use bounded concurrency and exponential backoff for 429 and transient 5xx responses.
- Use source identifiers, external references, or supported idempotency keys to prevent duplicate maintenance actions.
- Reconcile partial batch success and retain counts for processed, rejected, and retried items.
Data and lifecycle changes
- Normalize timestamps, time zones, units, precision, status values, and enumerations.
- Monitor SAP API versioning and test mappings after tenant upgrades.
- Keep mappings and environment configuration separate from workflow logic.
- Do not use direct access to the managed SAP APM database.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate beyond a single API call
Martini coordinates authentication, retrieval, pagination, enrichment, validation, business rules, target writes, and reconciliation in one maintainable workflow. This is more robust than isolated scripts that replicate error handling and configuration for every integration.
Keep integrations adaptable
Reusable workflows, mappings, APIs, and environment-specific secrets help teams respond to SAP tenant variation, API changes, and different target data models without creating a separate point-to-point implementation for every system.
Expose controlled interfaces
Martini can expose a REST API that hides SAP-specific details from downstream consumers while preserving centralized security, transformation, monitoring, retry, and duplicate-prevention logic.
Frequently asked questions
SAP Asset Performance Management can be integrated through documented REST or OData-style APIs published for the relevant SAP APM edition, tenant, and release. Integrations can use OAuth 2.0 or other configured SAP security mechanisms, scheduled polling, pagination, and selected batch or asynchronous capabilities. Event or webhook support must be verified per resource rather than assumed.
Yes. Martini can consume SAP APM REST APIs, authenticate using the required SAP security pattern, orchestrate workflows, map and transform assets, indicators, recommendations, models, and other supported resources, and write to downstream applications. Event-driven processing is available only where a specific SAP callback or event is confirmed.
No. A dedicated SAP Asset Performance Management connector is not required. Martini can integrate using SAP's confirmed native REST or OData-style APIs, authentication methods, and any specifically documented event, callback, file, or approved SAP integration endpoint.
Lonti does not charge an additional per-connector or per-vendor fee to integrate SAP Asset Performance Management. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from SAP, SAP BTP, cloud infrastructure, API management, or other third-party systems depending on subscriptions, usage, and deployment model.
Use the documented REST or OData-style API for the required SAP APM resource, after verifying the API package, operations, query options, and permissions in SAP Business Accelerator Hub. Batch or asynchronous processing may be appropriate for selected high-volume APIs. GraphQL and current SAP APM SOAP interfaces were not confirmed in the supplied research.
Event, webhook, and outbound callback coverage is not confirmed universally. It must be checked for each SAP APM resource, tenant, and API version. If no suitable notification exists, Martini can use scheduled polling with documented timestamps, status filters, or change markers.
Martini can use documented modified-time filters, delta markers, status filters, pagination, or confirmed events. A workflow stores the last successful checkpoint and can safely replay a bounded time window when source identifiers, upserts, and idempotency rules prevent duplicates.
Martini maps SAP payloads into canonical and target-specific models, normalizes units and timestamps, and applies validation and business rules. Workflows can classify authentication, authorization, validation, throttling, transient server, and business failures, retry transient errors with bounded backoff, and route permanent failures to reconciliation.
Related Martini documentation
API Integration
Data Processing
Security Operations
Connect SAP Asset Performance Management with Martini
Use Martini to build maintainable SAP Asset Performance Management integrations around documented APIs, secure workflows, data mappings, and reliable synchronization.