SAP PM and S/4HANA Integration for NDT Inspection Data
Take maintenance orders and notifications from SAP Plant Maintenance or S/4HANA into Atlantis as NDT jobs, and send approved inspection results, report PDFs and technician certification evidence back, through Atlantis's open REST API and the APIs your SAP landscape already exposes.
Who this is for
Two kinds of company ask for this. Inspection service providers working inside an asset owner's SAP landscape, where the client issues work through PM orders and wants results back against the same order. And asset owners with an in-house NDT team who run SAP PM or S/4HANA Asset Management for maintenance but need a proper NDT system for methods, procedures, technician certifications, equipment calibration and reports.
What data flows, and in which direction
| Record | Direction | Notes |
|---|---|---|
| Maintenance order / work order | SAP → Atlantis | Creates or updates an Atlantis job with the order number, plant, functional location and equipment references. |
| Maintenance notification | SAP → Atlantis, or Atlantis → SAP | Either the trigger for inspection work or the route by which a rejectable finding is raised back into SAP's maintenance planning. |
| Equipment and functional location | SAP → Atlantis (reference) | Keys used to tie reports to the client's asset register. SAP remains the register. |
| Inspection result and report status | Atlantis → SAP | Result (acceptable, not acceptable, acceptable with remarks) and status once the report is approved. |
| Report PDF | Atlantis → SAP | Attached to the order or notification through SAP's document or attachment services, where enabled. |
| Technician certification evidence | Atlantis → SAP (on request) | The certification status of the technicians on the job, when the client asks for it with the result. |
| Order confirmation / completion | SAP → Atlantis | Lets the NDT job close when the order closes, and supports invoicing. |
Typical architecture
S/4HANA publishes its business APIs, including maintenance orders and maintenance notifications, as OData services listed on the SAP Business Accelerator Hub; on-premise ECC and S/4HANA systems expose comparable services through SAP Gateway, and many landscapes also route traffic through middleware the customer already runs, such as SAP Integration Suite or PI/PO. The integration uses whichever route your SAP basis and security teams prefer. Atlantis's REST API is the other end.
The usual pattern is that SAP stays the system of record for the asset hierarchy and maintenance planning, and Atlantis becomes the system of record for how the inspection was done: who did it, with which instrument and calibration, to which procedure revision, and with what result. Findings that need maintenance action are raised into SAP as notifications rather than by creating orders directly, so SAP's own planning workflow decides what happens next.
Authorisations
A dedicated SAP service user with the minimum authorisations for the agreed objects, typically read on equipment and functional location, read on maintenance orders, and create or change on notifications and attachments if results flow back. No dialog-user or broad authorisations are needed; the authorisation matrix is part of the written scope.
What the Atlantis side offers
Atlantis ERP has an open REST API. The same API the offline field app uses to fetch assigned jobs and issued equipment and to submit reports is available for integration, and the records an NDT company cares about are reachable through it: jobs and team assignments, NDT reports and their status, technician certifications with their computed status (active, expiring soon, expired, revoked), equipment with calibration status and due dates, timesheets, quotations and invoices. Which objects are exposed, in which direction and to which system is agreed during implementation, because every integration is scoped to the customer's landscape rather than shipped as a fixed connector.
- No prebuilt, certified connector is claimed. The integration is built against your system's published API and Atlantis's REST API during implementation.
- Your system stays the system of record for whatever it owns today, whether that is the asset register, the general ledger or the customer master.
- Mapping is agreed in writing before anything is built: object, field, direction, trigger, and what happens when a record fails validation.
What gets configured during implementation
- Scope workshop. Which records move, in which direction, and who owns each field. Anything not agreed here is not built.
- Access on both sides. A dedicated integration user or app registration on your system with the minimum permissions for the agreed objects, and API credentials on the Atlantis side.
- Key mapping. How a record in one system is found in the other: work-order number, equipment or functional-location ID, customer number, invoice number.
- Field mapping and code lists. Status values, units, methods and result codes translated between the two systems.
- Triggers and timing. Event-driven (on approval, on posting) or scheduled, depending on what your system supports and what the business needs.
- Errors and retries. Where a failed record is logged, who is told, and how it is re-sent once fixed.
- Test in a sandbox, then a controlled go-live on a small set of records before the full flow is switched on.
What this integration does not do
Atlantis does not calculate inspection intervals, corrosion rates or remaining life, and does not perform risk-based inspection or fitness-for-service assessments. If your SAP landscape uses those outputs, they come from the engineering tools you already use; Atlantis supplies the inspection records they depend on.
Why integrate instead of re-keying
Every NDT company that works for large asset owners ends up typing the same facts twice: the work order number from the client's system onto the job, and the result from the report back into the client's system or into accounts. Re-keying is where report numbers get transposed, where a rejected weld is closed as accepted in someone else's system, and where invoices wait because nobody has matched the timesheet to the purchase order. An integration removes the second keystroke for the records that matter, and leaves an audit trail showing what was sent, when, and what the other system replied.
If SAP is part of your picture, book an integration scoping call and bring a sample order and the list of fields your planners need back. See also the integrations overview, the NDT Reports app and Digital Twin Reporting.
Frequently asked questions
Does this work with both SAP ECC and S/4HANA?
The pattern is the same. S/4HANA publishes OData APIs for maintenance orders and notifications on the SAP Business Accelerator Hub; ECC and on-premise S/4HANA expose comparable services through SAP Gateway or the middleware you already run. Which one is used is agreed with your SAP team.
Will Atlantis create maintenance orders in SAP?
The usual recommendation is to raise a notification for a finding that needs action and let SAP's planning workflow create the order. If your process is different, it is agreed in the scope.
Can report PDFs be attached in SAP?
Where your SAP landscape has attachment or document services enabled for the relevant objects, yes; the report is attached after approval so only issued reports reach SAP.
Do we need SAP middleware?
Not necessarily. Direct API calls work where your security policy allows them; if your landscape routes all external traffic through SAP Integration Suite or PI/PO, the integration uses that.
Is this a certified connector?
No. Atlantis does not claim a certified or marketplace connector. The integration is built during implementation against your system's published API and the Atlantis REST API, scoped to the records you need.
Who owns the integration once it is live?
That is agreed in the scope: typically Atlantis maintains the Atlantis side and the mapping, and your IT team owns credentials and permissions on your system. Changes to the mapping are handled as change requests.
Sources
- SAP Business Accelerator Hub (S/4HANA APIs)
- IBM Maximo Manage REST APIs
- NetSuite OAuth 2.0 for REST web services
- QuickBooks Online API (Intuit developer help)
- Business Central API v2.0 endpoints
Speak to an ASNT NDT Level III
Discuss your inspection requirements with Atlantis NDT. Include the asset, method, location and documents you need reviewed.