What SAP data is most useful to visualise in XR for a utility?

Network asset hierarchies in SAP Plant Maintenance (PM), FI-CA account balances by geographic area, and field service order locations pulled from SAP Work Manager are the most spatially meaningful SAP datasets for utility XR use cases.

How does an XR application connect to SAP IS-U or S/4HANA Utilities?

XR applications typically use SAP OData APIs published through SAP BTP API Management or SAP Gateway. For near-real-time scenarios, SAP Event Mesh on BTP can push change events to the XR layer without constant polling.

Does SAP offer any native XR tools for utilities?

SAP has offered SAP Augmented Reality as an experimental capability and collaborates with third-party spatial computing vendors. There is no packaged SAP IS-U or S/4HANA Utilities XR product; integration requires custom development.

XR Visualization of Real-Time SAP IS-U and S/4HANA Data

SAP IS-U on ECC and S/4HANA Utilities together manage billing, device management, meter reading, and financial settlement for electric, gas, and water utilities. Most of this data is viewed through standard SAP Fiori apps, SAP Analytics Cloud reports, or legacy SAPGUI transactions. XR visualization layers are a non-standard addition, but for specific data types, they provide a genuinely different way of interpreting operational state.

This post is specifically about the SAP side of the utility XR question. The companion post on XR for general ERP data visualization covers Oracle and cross-platform considerations. The AR-for-SAP financial module angle is covered separately at Enhancing ERP: Integrating AR with SAP.

SAP IS-U Data Types With a Spatial Dimension

SAP IS-U manages connections and meter points against a premises and installation hierarchy. That hierarchy has a physical location: a street address, a grid coordinate, or a network topology position. When that location data is joined with operational state, the result is inherently spatial.

Scenarios where XR adds value over a conventional SAP dashboard:

Outage and restoration context: Displaying FI-CA account counts by premise location over a GIS network model, drawn from SAP IS-U meter installation records, lets an operations manager see revenue exposure from an outage spatially rather than as a count in a table.
Field service and PM asset inspection: A technician using AR glasses during a substation inspection can surface SAP Plant Maintenance equipment records, maintenance history, and open work orders against the physical asset in their field of view, without switching to a mobile device.
Billing exception geography: Accounts with open billing exceptions or disconnection orders, extracted from IS-U contract account data, can be plotted on a 3D grid model to identify concentrations that point to a systematic metering or tariff configuration issue.

Integration Architecture on SAP BTP

Real-time XR visualization of SAP data requires a defined integration path. SAP Business Technology Platform provides the recommended current approach:

SAP API Management on BTP governs and rate-limits OData API calls from the XR application to IS-U or S/4HANA Utilities.
SAP Event Mesh can publish IS-U business events, such as meter reading exceptions or billing run completions, to the XR layer without the application polling SAP constantly.
SAP HANA Cloud can serve a denormalised spatial view of IS-U data, joining installation location, device, and account status, which the XR engine queries for its rendering feed.

This architecture keeps the XR application decoupled from the core SAP system. When IS-U is patched or when a migration to S/4HANA Utilities occurs, the API Management layer absorbs most of the API change management rather than requiring the XR application to be rebuilt.

For a detailed look at SAP BTP’s broader role in utility integrations and extensions, see Unlocking Business Potential with SAP BTP.

S/4HANA Utilities and the Clean-Core Consideration

Under SAP’s clean-core guidance, custom Z-code inside the IS-U core should be minimised. This applies equally to any XR data feed that was historically built as a custom ABAP report or RFC function module. On S/4HANA Utilities, the preferred path is to expose IS-U data through standard OData services or SAP BTP side-by-side extensions rather than calling bespoke RFCs from an XR application.

This matters practically because a custom RFC-based XR data feed will not survive a technical upgrade from ECC IS-U to S/4HANA Utilities without rework. Building the integration via BTP from the outset avoids that rework.

Honest Scope: Where XR Adds Less Value

General SAP IS-U billing transactions, rate schedule maintenance, FI-CA financial postings, and IDOC monitoring are procedural tasks. They do not benefit from spatial or immersive representation. Pushing these workflows into an XR environment adds device and development overhead without improving the decision or the outcome. The value of XR in an SAP utilities context is narrow but real for spatial operational data.

For teams evaluating whether an XR initiative alongside an SAP IS-U or S/4HANA Utilities programme is worth the investment, AvanSaber can assess what your specific operational data and use cases justify.