SAP industry solutions explained: IS-U, IS-Retail

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026

SAP industry solutions are the industry-specific functions SAP layers on its core ERP, often called SAP IS after the old IS- prefix: utilities (IS-U), retail (IS-Retail), oil and gas (IS-Oil), insurance and banking, public sector, healthcare, and discrete industries and mill products (DIMP). Each adds the master data, processes and regulatory reports a generic ERP has no home for.

Which industries get their own SAP solution?

The ones carrying objects and regulatory reporting the core ERP has no home for: supply points, meters and contract accounts; article, site and assortment structures at retail volume; temperature-corrected quantities; policies and claims; patients; a budget that is a legal instrument. The main ones, with the name used today and the code job adverts still use:

Oil and gas demand is concentrated: much of it comes from the greenfield programmes in the Gulf, where the national energy companies are the anchor customers.

Are the IS add-ons still separate products in S/4HANA?

Mostly not — most of them now live in the S/4HANA codeline itself. In ECC an industry solution was switched on through the switch framework, with one industry business function set per system, which is why a utility and a retailer could never share an ECC system. S/4HANA folded most of that functionality into the core, so a utilities project today configures utilities processes inside the same product a manufacturer runs. The exceptions matter: some components were simplified or replaced on the way, and healthcare's patient management was not carried across at all. Job adverts still use the old codes (the wider shift). SAP also markets industry cloud solutions built on its Business Technology Platform beside the ERP; this page is about the industry functionality inside it.

How does an industry solution project run?

Like any ERP programme in shape, but with volume and regulation deciding the hard parts at every phase:

• Design — workshops with meter operations, category managers or claims handlers, in the regulator's vocabulary rather than SAP's; the question is whether the standard object covers the local rule.
• Build — configuration in the industry component and the core beneath it, plus specs for market messages, tariff structures or the point-of-sale feed.
• Test — volume is the test: a billing run at real contract volumes, a mass activity that must finish inside its window. Defects are as often performance as logic.
• Cutover — migrating objects no generic template covers: installations, devices and contract accounts; articles, sites and assortments.
• Hypercare and AMS — the first cycle in production is the exam: the first billing run, the first market exchange, the first season (project shapes).

How do industry solutions lean on the core modules?

Every one of them posts into, sells through or buys through a standard module, so an industry consultant works the border daily: utilities billing into Finance through FI-CA, retail merchandise into MM, networks and plants into Asset Management. Two neighbours sit beyond it: master data governance, because article and business-partner records break first, and integration, because market communication is message traffic (which combinations work).

FI-CA is the border most often underestimated. Utilities, insurance, telecommunications and public bodies share it because they bill millions of small accounts, so it runs as mass activities — payment runs, dunning, interest — split into parallel jobs rather than processed one document at a time. A Finance consultant who knows the general ledger still has to learn contract-account postings, clearing rules and the reconciliation to the ledger before an industry billing project will trust them with the sub-ledger.

How do people get into industry solution work?

Mostly from inside the industry — a utility's billing team, a retailer's master-data desk, an insurer's policy administration, the classic key-user route. Others cross from a core area, FI people to FI-CA or SD people to merchandise flows, or enter through AMS or a migration seat. Interviews probe the solution, not the industry — how billing and invoicing differ in IS-U — so your CV should name the component. The depth travels between employers inside the industry, rarely outside it, and its rules are local; niches this small are often staffed by referral.