An ArcGIS – SAP integration links GIS features to SAP PM/EAM objects — functional locations and equipment — so maintenance notifications and work orders can be raised and viewed on the map. Master data flows from SAP through OData services on SAP Gateway or BTP Integration Suite; geometry, network topology and linear referencing stay in ArcGIS, with the functional location key as the join.
Swedish Technology builds the interface as versioned custom development with a signed-off field mapping, an exception queue and reconciliation reporting, then hands over the source and runbooks.
What problem does this solve?
SAP PM is where the money lives. Budgets, maintenance plans, cost centres, procurement and the audited asset register are all anchored to functional locations and equipment numbers. ArcGIS is where the network lives: what connects to what, where the pipe actually runs, which segment of the road is which. The two were built by different teams for different purposes, and the identifiers rarely line up. Planners end up working from an SAP list of functional locations that nobody can point to on a map.
The consequences are concrete. A notification is raised for a functional location with no usable coordinates, so the crew is sent to the wrong access point. A pipe replaced in the field is updated in ArcGIS but the equipment record in SAP still shows the old material and installation date, so remaining-life calculations are wrong. Condition surveys are stored in GIS while maintenance plans are built in SAP, and the link between them is an analyst with a spreadsheet.
Linear assets make it harder again. SAP represents a road, pipeline or cable as a functional location with a length; ArcGIS represents it as a route with measures, and defects, treatments and inspections are events along that route. Any integration that ignores linear referencing forces the organisation to split real assets into artificial fixed segments, and those segments then never match the way work is actually planned.
How the solution works
The design decision is ownership, agreed field by field. SAP owns functional locations, equipment, classification, maintenance plans, notifications, orders and costs. ArcGIS owns geometry, network connectivity, the linear referencing system and any spatial derivation. The integration layer moves only what each system does not own: functional location and equipment master data into ArcGIS as attributes on features, and location context, defect geometry and inspection results back into SAP as notifications, order confirmations or measurement documents.
Technically that means OData services published through SAP Gateway on S/4HANA or ECC, orchestrated by SAP BTP Integration Suite or the older PI/PO landscape where one is already in place, on the SAP side; and ArcGIS REST feature-service operations, attribute rules and Field Maps on the GIS side. Between them sits a service that holds the field mapping, translates code lists and units, converts route-and-measure locations into the segment description SAP expects, manages an exception queue, and produces a reconciliation report. Swedish Technology delivers this as custom development with a signed-off mapping specification and full hand-over.
- 1Input SAP functional locations, equipment, classification and maintenance plans; ArcGIS features, routes and measures. A key strategy defines whether TPLNR/EQUNR is stored on the feature, the GIS GlobalID is stored in SAP, or both.
- 2Capture Changes are detected from SAP through change pointers, CDS view deltas or OData query on a changed-on timestamp; from ArcGIS through editor tracking, attribute rules or a change-detection query.
- 3Processing The service validates each record against the mapping specification, translates code lists (notification type, priority, damage code, unit of measure), resolves the key, and converts geometry to or from route-and-measure or a coordinate pair.
- 4Integration Writes go through OData services on SAP Gateway (or BTP Integration Suite / PI-PO channels) and through ArcGIS feature-service applyEdits, using idempotency keys so retries never create duplicate notifications.
- 5Action Planners see notifications and orders on the network map with status and priority; crews confirm work in Field Maps; a defect captured in the field creates an SAP notification with the correct functional location and a measure along the route.
- 6Reporting Dashboards show backlog, overdue plans and condition by asset class or corridor; a scheduled reconciliation lists SAP objects without geometry, GIS features without an SAP key, and rejected messages awaiting an owner.
Reference architecture
Five components: SAP, its integration technology, the mapping service, ArcGIS, and the governance artefacts that keep the mapping honest as both systems change.
| Layer | What it contains |
|---|---|
| SAP PM / EAM | S/4HANA (on-premise or private cloud) or SAP ECC with Plant Maintenance. Functional locations, equipment, classification, notifications, orders, measuring points and measurement documents are exposed through standard or custom OData services. |
| SAP integration technology | SAP Gateway for OData exposure; SAP BTP Integration Suite (Cloud Integration) or SAP PI/PO for orchestration, mapping and monitoring where the landscape already uses them; RFC/BAPI only where OData is not available. |
| Integration service | The custom component: field mapping, code-list translation, key resolution, route-and-measure conversion, queue with retry and dead-letter, idempotency, correlation IDs and audit logging. |
| ArcGIS Enterprise | Enterprise geodatabase, feature services, ArcGIS Roads and Highways or the Location Referencing capability where linear assets are in scope, attribute rules for validation, branch versioning where edits need review. |
| User applications | Web maps and Experience Builder apps for planners and supervisors, Field Maps for crews, ArcGIS Pro for editors, dashboards for management reporting — all authenticated through portal or Entra ID SSO. |
| Governance | Version-controlled field-mapping specification, key strategy, exception-handling rules with a named owner, and monitoring that shows last successful sync per entity. |
Deployment options: In the UAE and GCC, SAP is usually on-premise or in a national cloud region and ArcGIS Enterprise is on-premise. The integration service is deployed inside the same network or a DMZ, with no data leaving the environment. Where BTP Integration Suite is already licensed and permitted, it can carry the transport while the mapping logic stays on-premise.
Key capabilities
Functional location and equipment sync
Every mapped asset carries its SAP key, and planners can move from a map feature to the SAP object without searching.
custom developmentNotifications and orders on the map
Maintenance backlog, priority and crew assignment are visible spatially, so work can be bundled by area instead of by list order.
custom developmentCreate a notification from a feature
A user selects a pipe, pole or road segment and raises an SAP notification with functional location, damage code and position already filled in.
custom developmentLinear asset support
Defects and treatments are recorded as events along a route with from/to measures, matching how roads and pipelines are actually maintained.
custom developmentMeasurement documents from the field
Readings and condition scores captured in Field Maps post to SAP measuring points, feeding condition-based maintenance plans.
custom developmentOrder confirmation from the field
Crews confirm completion on the map application and SAP is updated, removing a second data-entry step in the office.
custom developmentReconciliation and data-quality reporting
Orphan SAP objects, features without keys and rejected messages are listed weekly instead of surfacing during an audit.
custom developmentBilingual map and field applications
Arabic and English labels, domain values and reports for government maintenance teams.
availableIntegrations
The SAP interface is normally one part of a wider asset-information programme; these are the connections that appear alongside it.
| System | Integration point & data exchanged | Direction |
|---|---|---|
| SAP PM / S/4HANA Asset Management | Functional locations, equipment, classification, notifications, orders, measuring points and measurement documents via OData services on SAP Gateway. | bi-directional |
| SAP BTP Integration Suite / PI-PO | Transport, orchestration and monitoring of the interfaces where the landscape already standardises on them. | bi-directional |
| ArcGIS Enterprise / Field Maps | Feature services, linear referencing, field capture forms and dashboards used by planners, editors and crews. → ArcGIS Experience Builder Custom Widgets | bi-directional |
| ArcGIS Pro | Editor and planner workflows: look up or raise SAP records for a selected feature through a custom add-in. → ArcGIS Pro Add-in Development | bi-directional |
| Pavement and condition surveys | Condition indices held in ArcGIS as route events trigger SAP notifications above defined thresholds. → Road Inspection & Pavement Condition Intelligence in GIS | outbound |
| RFID / RTLS | Tag-based verification of equipment existence and last-seen location, used to validate the SAP equipment register. → ArcGIS RTLS & RFID Integration: Live Location in GIS | inbound |
Industry use cases
Water and electricity utilities
Network features in ArcGIS carry the SAP functional location; leak and outage notifications appear on the network map and crews are dispatched spatially.
Roads authorities
Pavement condition events along routes generate SAP notifications for treatment; the maintenance programme is planned on the corridor map and costed in SAP.
Pipelines and oil & gas
Inspection findings recorded by chainage feed SAP notifications; equipment and functional location hierarchies stay aligned with the spatial model.
Rail and metro
Track, signalling and station assets referenced linearly; possession planning uses the map while orders and costs remain in SAP.
Municipal facilities and street lighting
Faults reported by the public or by field crews create SAP notifications with the exact asset, cutting the repeat-visit rate.
UAE & GCC considerations
Utilities, roads authorities and industrial operators across the UAE and GCC typically run SAP on-premise or in a national cloud region under data-residency rules, with ArcGIS Enterprise inside the same network, and security teams commonly refuse interfaces that route asset or maintenance data through public cloud middleware. That shapes the design towards an on-premise integration service, with SAP BTP used only where it is already licensed and approved. Maintenance KPIs are frequently reported to a regulator or a parent entity, which makes the reconciliation report a deliverable rather than an optional extra. Field crews work bilingually, so notification texts, damage codes and map applications are delivered in Arabic and English, and government procurement usually names the field-mapping specification, source code and hand-over documentation as contract deliverables. We have delivered integration components in fully air-gapped environments where no outbound connectivity was permitted at all.
Implementation approach
- 1Discovery (2–3 weeks) Workshops with maintenance planning, SAP basis/functional and GIS teams. Inventory of PM configuration, existing interfaces, ArcGIS data model and the identifiers actually in use.
- 2Key strategy and data profiling Measure how many functional locations and equipment records can be matched to GIS features today. This figure sets the real scope; a low match rate means a clean-up project comes first.
- 3Field-mapping specification Field by field: SAP object and field, GIS layer and attribute, direction, transformation, code-list translation, mandatory flag and data owner sign-off.
- 4Interface design Choose per flow between standard OData services, custom Gateway services, BTP Integration Suite flows or batch extracts; define error handling, idempotency, volumes and monitoring.
- 5Build and unit test Iterative development against SAP and ArcGIS test systems, with recorded payloads so testing can continue when either system is unavailable.
- 6Data clean-up and initial load Resolve duplicates, missing geometry and orphan functional locations; run the initial synchronisation in controlled batches with a rollback plan.
- 7Pilot (4–8 weeks) One district, plant area or corridor runs live including field capture, with daily reconciliation, a defect log and measured message volumes.
- 8Roll-out, hand-over and support Extend by area; deliver source code, runbooks, monitoring dashboards and admin training; agree regression testing for SAP transports and ArcGIS Enterprise upgrades.
Security & deployment
The interface runs under dedicated technical users with least-privilege authorisation objects in SAP and a scoped ArcGIS service account, with credentials held in a vault rather than in configuration. End users authenticate to the map applications through Entra ID or portal SSO, so ArcGIS layer permissions and SAP authorisation checks both continue to apply — the integration never grants a user more than their own roles allow. All traffic is TLS, payloads are logged with correlation IDs and sensitive fields masked, and message history is retained for the period the audit function requires. The service is deployed on-premise, in a UAE-region private cloud or air-gapped, and transports follow the customer's existing SAP change-management process.
Limitations & prerequisites
- SAP authorisation and transport governance usually set the pace of the project; access to a development system and a named SAP functional contact are prerequisites, not details.
- Standard OData services do not always expose every field a maintenance process needs; custom Gateway services or CDS views may be required, which is ABAP work on the customer's side.
- The functional location hierarchy and a GIS network model are different structures. Some assets need documented aggregation or split rules, and a few will never map one-to-one.
- Linear referencing must exist and be maintained in ArcGIS before route-and-measure events can be exchanged; building an LRS is a project of its own.
- Real-time in both directions multiplies cost and failure modes; a common compromise is real-time for notifications and scheduled batch for master data.
- Attachments, photos and long inspection texts do not travel well through record-level interfaces; a document platform or object storage is normally needed alongside.
- SAP release upgrades, support packs and S/4HANA conversions can change service behaviour, so regression testing must be part of the SAP maintenance calendar, not an afterthought.
Integration options between ArcGIS and SAP PM
Four patterns, from lightest to heaviest. Most organisations combine two.
| Criterion | Batch extract / reporting join | Read-only SAP look-up in GIS | Custom bi-directional service | BTP Integration Suite flows |
|---|---|---|---|---|
| What users get | Aligned reporting, next day | SAP details shown for a selected feature | Notifications and confirmations both ways | Governed, monitored enterprise interfaces |
| Write-back to SAP | No | No | Yes, per flow | Yes |
| Effort | Weeks | Weeks | Weeks to months | Months, plus platform setup |
| SAP-side work | Extracts or CDS views | OData service exposure | OData services plus authorisations | Integration artefacts and operations |
| Data residency fit (UAE) | High — stays internal | High | High — service on-premise | Depends on cloud approval |
| Field capture in ArcGIS | No | No | Yes, via Field Maps | Yes, with a GIS-side component |
| Best for | Analysis and KPI reporting | Fast visibility with low risk | Operational maintenance workflows | Landscapes already standardised on BTP |
A pragmatic sequence is a read-only look-up first to prove the key strategy, then a custom service for the two or three flows that change daily work, moved onto BTP later if the organisation standardises there.
FAQ
The number of SAP objects and flows in scope, whether each is one-way or bi-directional, whether standard OData services are sufficient or custom Gateway services and CDS views are needed, the state of the identifiers on both sides, and whether linear referencing is involved. Field capture with bilingual forms adds scope on the ArcGIS side.
Discovery and the field-mapping specification take 3–5 weeks. A first production flow — usually notifications displayed on the map — is typically live in 8–14 weeks, longer where SAP development and transport approvals are on a fixed release calendar. Full bi-directional coverage is generally a four to eight month programme.
Yes. SAP, ArcGIS Enterprise and the integration service can all sit inside your network with no outbound connectivity, which is the usual requirement for UAE government and utility entities. Air-gapped deployment is possible with local package installation.
Not necessarily. If your landscape already uses BTP Integration Suite or PI/PO, using it keeps interface governance in one place. If it does not, direct OData calls from a dedicated integration service are simpler, cheaper and easier to keep inside the network.
ArcGIS holds the linear referencing system — routes with measures — and events such as defects, treatments and inspections are recorded with from/to measures. The integration converts between those measures and the segment description SAP expects on the functional location. Where no LRS exists, building one is a prerequisite project.
An extract of functional locations, equipment and a month of notifications and orders; the ArcGIS feature classes with schemas; the code lists in use (notification types, damage codes, priorities); documentation of existing interfaces; and access to SAP and ArcGIS test systems.
Message delivery is made reliable with a queue, retries and idempotency keys, so a transient failure never creates duplicate notifications. Business-level correctness depends on data quality: records that fail validation go to an exception queue with a named owner, and a weekly reconciliation report shows what is unmatched.
You do. Source code, the field-mapping specification, transport documentation, deployment scripts and runbooks are handed over as named deliverables. We can continue under a support agreement, including regression testing when SAP support packs or ArcGIS Enterprise upgrades are applied.
SAP has the asset, ArcGIS has the location — and they disagree?
Send us a functional location extract and your GIS feature classes. We reply with a key strategy, a draft field mapping and the realistic integration options with effort and risk.
Book an Integration WorkshopSources & evidence
- SAP Help Portal — SAP S/4HANA (on-premise) documentation — Asset Management / Plant Maintenance functional documentation
- SAP Business Accelerator Hub — SAP APIs and OData services — catalogue of standard OData services used for PM objects
- SAP Help Portal — SAP Integration Suite
- Esri — What is linear referencing? (ArcGIS Pro)
- Esri — What is a feature service? (ArcGIS Enterprise)
Vendor and product names are trademarks of their respective owners; references are for technical context and do not imply partnership, certification or endorsement unless stated on the vendor's official pages.