- Home
- Integrations
- SAP IS-U integration
Solution
SAP IS-U field service integration for smart meter crews
PIEBENCH is built to integrate with SAP IS-U. Connectorly can read consumers, premises and meters from IS-U to create service points and work orders, and send approved meter installations back, over the OData or REST services your SAP team exposes, or through a SQL staging table. It is built to integrate, not SAP-certified, and needs no custom ABAP on the PIEBENCH side.
The usual problem
Many DISCOMs run billing and customer data on SAP IS-U (Industry Solution for Utilities). It holds the consumer, the premises, the installation and the device. It is the system of record, and it is not built for a technician standing at a meter board with a phone.
So field data reaches IS-U the slow way. Crews fill in paper or a separate app, someone exports a sheet, and an SAP team uploads it in batches. Every hand-off adds delay, and every re-keyed serial is a chance for the device in IS-U to disagree with the device on the wall.
What PIEBENCH does with IS-U
| Direction | Typical data | Becomes |
|---|---|---|
| SAP IS-U → PIEBENCH | Consumers (business partners, contract accounts), premises and installations | Service points with location, ready for crews |
| SAP IS-U → PIEBENCH | Device or meter master data | Meters in PIEBENCH's inventory |
| SAP IS-U → PIEBENCH | Service orders or a list of premises to visit | Work orders for crews |
| PIEBENCH → SAP IS-U | Approved installation: new device serial, old device and final reading, initial reading, date, location | A device replacement your SAP team can post |
Exactly which objects you exchange depends on what your SAP team exposes. PIEBENCH doesn't need to know IS-U's internal tables; it needs an endpoint or a table with the fields agreed.
How the connection works
SAP systems typically expose data to outside applications as OData services over HTTP, published through SAP Gateway. To Connectorly, an OData service is a REST API: it connects with Basic authentication, a Bearer token or OAuth 2.0, reads a sample, and suggests field mappings.
Some SAP teams prefer not to open services and instead write to a staging table in a separate database. Connectorly can read PostgreSQL, MySQL, Microsoft SQL Server and SQLite directly, so that route works too.
In both cases the steps are the same:
- Connect and test against the service or table.
- Accept or change the AI-suggested field matches, for example SAP's device number field to PIEBENCH's meter serial.
- Add a filter, such as one division or one set of premises, and a schedule.
- For outbound data, choose which approved events to send, such as meter installations.
Connectorly logs every run, retries failed sync jobs up to five times, and tracks each outbound delivery. Setup on the PIEBENCH side typically takes about 10 minutes once the SAP side is ready. See how integrations work.
What "built to integrate" means here
PIEBENCH has been tested against SAP IS-U-style data and services. It is not SAP-certified, and we don't claim it is. In practice that means your SAP team stays in control of what is exposed and how inbound records are posted. PIEBENCH's job is to deliver clean, approved, consistently mapped data to the place they choose.
Why this beats a batch upload
- Fewer re-keyed serials. Serials are scanned from the barcode in the field and travel to SAP without being typed again.
- Only checked data. Installations are sent after a supervisor approves them, so SAP isn't cleaning up rejected jobs.
- Faster. Data moves on a schedule you set instead of once a week.
- Traceable. Every run and delivery is logged, so a missing device change can be traced to a specific job.
Integrations are included in Pro ($499 a month) and Enterprise. If your SAP setup needs something unusual, Enterprise includes custom integrations. See pricing.
Built to integrate with your systems
HES, MDM, SAP IS-U, Oracle CC&B and billing systems, over REST, OAuth or a direct SQL connection. How integrations work
Questions buyers ask
Can a field app integrate with SAP IS-U without heavy custom development?
Yes. Connectorly connects to the OData or REST services your SAP team exposes, or to a SQL staging table, and maps the fields with AI suggestions. There is no custom code on the PIEBENCH side. Your SAP team decides what to expose and how inbound records are posted.
Is PIEBENCH SAP-certified?
No. PIEBENCH is built to integrate with SAP IS-U and has been tested against IS-U-style data and services, but it is not SAP-certified. It connects through standard interfaces (OData or REST over HTTP, or a staging database) rather than an SAP-certified add-on.
Which SAP IS-U data can PIEBENCH use?
Typically consumers and premises (to create service points), device or meter master data, and lists of premises or service orders to visit (to create work orders). Approved meter installations go back to SAP. The exact objects depend on what your SAP team exposes.
Does PIEBENCH replace SAP FSM or SAP Mobile Asset Management?
It can cover the same field work for smart meter projects, with offline capture, approvals and attendance built for metering crews. Whether to replace an existing SAP mobile solution depends on how much else it does for you. Many teams start with one project or agency to compare.
How long does an SAP IS-U integration take?
On the PIEBENCH side, about 10 minutes once the SAP service or staging table exists. Most of the time goes into the SAP team agreeing which data to expose, so involve them at the start.
Can billing system data come in without SAP at all?
Yes. If your billing system is not SAP, Connectorly connects the same way to any REST API or a PostgreSQL, MySQL, SQL Server or SQLite database. See the Oracle CC&B and HES/MDM integration pages for other common systems.
Free trial · no card
See it with your own crew
Start a free trial, or ask us for a walkthrough of your rollout.