SAP industry solutions explained: IS-U, IS-Retail
Industry Solutions is the SAP area for the industry-specific solutions layered on the core ERP — utilities (IS-U), retail (IS-Retail), oil and gas (IS-Oil), banking and insurance, public sector and healthcare, discrete industries and mill products (DIMP). This page covers which industries have a solution of their own, the work by project phase, the routes in, and how far industry depth carries.
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. Each solution adds that master data, the processes around it and the regulator's reports.
- Utilities (IS-U)
- Business partner, contract account and installation, not a customer; device management and meter reading; billing and invoicing as separate steps; contract accounts receivable and payable (FI-CA) as the sub-ledger; market communication with grid operators.
- Retail (IS-Retail)
- Articles instead of materials, sites for stores and warehouses, merchandise category hierarchies, assortments and listing, plus a point-of-sale interface feeding sales and stock back on the retailer's own schedule.
- Oil and gas (IS-Oil)
- Hydrocarbon product management, where a quantity converts between temperature-dependent units; the trader's and scheduler's workbench; transportation and distribution; exchanges between competitors.
- Banking and insurance
- Policy and claims management with collections and disbursements (FS-CD) on the insurance side, deposits and loans on the banking side.
- Public sector and healthcare
- Funds and grants management (PSM), where a budget is a legal instrument checked before the spending; patient management (IS-H).
- Discrete industries and mill products (DIMP)
- Automotive, aerospace and defence, high tech and mill products, ordered by dimension and characteristic rather than by piece.
The IS- prefix is historical: several began as add-ons and now ship inside the ERP itself, though job adverts still use the old names (the wider shift).
Design, cutover, and the first billing run
- 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).
Doors in: the industry, the core area, the live system
- 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.
- From the core area — FI people moving to FI-CA, SD and logistics people moving to merchandise flows.
- From the programme's edges — AMS on a live industry system, or a migration seat: often the only doors open without industry history.
Name the component you configured, the cycle you ran end to end, the object you owned. Interviews probe there — how billing and invoicing differ in IS-U, what a merchandise category hierarchy does that a material group does not — so your CV should name the solution, not only the industry (what interviews test).
Where industry depth travels, and where it stops
Each solution leans on the core beneath it: utilities billing into Finance, 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).
Industry depth travels between employers inside the industry, rarely outside it, and its rules are local — worth weighing before you move countries. Niches this small are often staffed by referral.
Related reading
- SAP FI explained: finance in SAP
General ledger, payables, receivables, assets and the close — the books of record.
- SAP Supply Chain & Logistics explained
Warehouses, transport and planning — EWM, TM and everything that moves.
- SAP PM explained: asset management in SAP
Equipment, maintenance orders and prevention — the physical world's area.
- The SAP CV: what actually gets read
The project table, the four facts, and the mistakes that bury strong experience.
Work with SAP?
Join to get your public SAP profile. Your city appears on the map once 5 professionals are mapped there.