ERP integration

The ERP stays the system of record.

Each adapter owns authentication, pagination, field mapping and retries. The product owns the canonical model and the workspace. The connector is a standalone library, not a copy of any one CMMS. The same layer reads the SAP enterprise structure — company codes, plants, business areas and controlling areas — for the landscape dashboard.

Open SAP landscape

Adapters

SAP S/4HANA Cloud

Reference adapter
Transport
OData V2/V4
Auth
OAuth2 client credentials
Entities
Company codes, plants, business areas, equipment, functional locations, notifications, orders, confirmations

SAP ECC 6.0

Planned
Transport
RFC/BAPI or OData via Gateway
Auth
SAP NW RFC SDK or OAuth2
Entities
Same enterprise structure and canonical entities, ECC field names

IBM Maximo

Planned
Transport
REST / OSLC
Auth
API key or OAuth2
Entities
Assets, locations, work orders, preventive maintenance

Oracle EAM

Planned
Transport
Oracle REST APIs
Auth
OAuth2 or basic
Entities
Assets, work orders, operations, materials

SAP API inventory

Released S/4HANA Cloud APIs. The exact API list and communication arrangement must be confirmed in the client sandbox before UAT.

Swipe to see all columns →

EntityAPIDirection

Equipment

Asset master and criticality

API_EQUIPMENTInbound

Functional location

Location hierarchy

API_FUNCTIONALLOCATIONInbound

Maintenance notification

Request and breakdown

API_MAINTNOTIFICATIONBidirectional

Maintenance order

Execution header and status

API_MAINTENANCEORDERBidirectional

Confirmation

Labour and time

API_MAINTENANCEORDERCONFIRMATIONOutbound

Measuring point

Meters and condition

API_MEASURINGPOINTInbound

What is real here

Real

The OData client, OAuth2 flow, pagination, retry policy, canonical mapping, simulator and CI contract tests.

Synthetic

The four plant datasets, KPI values, names and work orders on this site.

Not yet validated

A real SAP sandbox: communication arrangement, API list, authorisations and field-level business validation.

The simulator is not SAP and is never described as certified. It exercises the same client code over HTTP so contract failures surface before a sandbox is available.