Why it matters
Utilities programmes often promise “Fiori for the back office” before anyone has counted the apps. The count is small, and it is shaped in a specific way: SAP has invested in exceptions, monitoring and overviews along meter to cash, and very little in replacing core master data and processing transactions. If you plan the user experience around that shape, billing and operations specialists get a better working day. If you ignore it, you promise a Fiori-only launchpad you cannot deliver.
The 20 apps, in process order
Meter reading — IS-U-DM-MR
| App ID | Exact app name | Supplied transaction code | Application component | Status | Backend stack | Source row |
|---|---|---|---|---|---|---|
| F2185 | Resolve Implausible Meter Readings | EL27 | IS-U-DM-MR | Available | Initial Shipment Stack | 1818 |
| F2786 | Periodic Meter Reading Overview | EL31 | IS-U-DM-MR | Available | Initial Shipment Stack | 1819 |
Contract billing — IS-U-BI
| App ID | Exact app name | Supplied transaction code | Application component | Status | Backend stack | Source row |
|---|---|---|---|---|---|---|
| F2186 | Resolve Outsorted Billing Documents | EA05 | IS-U-BI | Available | Initial Shipment Stack | 1810 |
| F2709 | Periodic Billing Overview | EA05 | IS-U-BI | Available | Initial Shipment Stack | 1811 |
| F2801 | Outstanding Billing Overview | EA05 | IS-U-BI | Available | Initial Shipment Stack | 1812 |
| F3132 | Display Suppressed Billing Orders | EL31 | IS-U-BI | Available | Initial Shipment Stack | 1813 |
| F3133 | Process Missing Billing Orders | EL01 | IS-U-BI | Available | Initial Shipment Stack | 1814 |
| F3134 | Display Outstanding Billing Items | EL28 | IS-U-BI | Available | Initial Shipment Stack | 1815 |
| F3339 | Process Billing Orders | EASIBI | IS-U-BI | Available | Initial Shipment Stack | 1816 |
| F3358 | Process Billing Errors | EASIBI | IS-U-BI | Available | Initial Shipment Stack | 1817 |
Invoicing — IS-U-IN
| App ID | Exact app name | Supplied transaction code | Application component | Status | Backend stack | Source row |
|---|---|---|---|---|---|---|
| F3135 | Periodic Invoicing Overview | Not supplied | IS-U-IN | Available | Initial Shipment Stack | 1820 |
| F3253 | Resolve Outsorted Invoicing Documents | EA05 | IS-U-IN | Available | Initial Shipment Stack | 1821 |
| F3424 | Periodic Billing and Invoicing Analysis | Not supplied | IS-U-IN | Available | Initial Shipment Stack | 1822 |
Exception management (BPEM) — IS-U-TO-MMA
| App ID | Exact app name | Supplied transaction code | Application component | Status | Backend stack | Source row |
|---|---|---|---|---|---|---|
| F7255 | BPEM Clarification Case Overview | Not supplied | IS-U-TO-MMA | Available | Initial Shipment Stack | 1827 |
| F7256 | Manage BPEM Clarification Cases | EMMACL | IS-U-TO-MMA | Available | Initial Shipment Stack | 1828 |
Master data and contract account — IS-U-MD, IS-U-MD-CA
| App ID | Exact app name | Supplied transaction code | Application component | Status | Backend stack | Source row |
|---|---|---|---|---|---|---|
| F3131 | Block Utilities Contracts | ES21 | IS-U-MD | Available | Initial Shipment Stack | 1825 |
| F2708 | Release Blocked Utilities Contracts | ES22 | IS-U-MD-CA | Available | Initial Shipment Stack | 1826 |
Measurement concept management — IS-U-LIB-UCM
| App ID | Exact app name | Supplied transaction code | Application component | Status | Backend stack | Source row |
|---|---|---|---|---|---|---|
| F8838A | Display Measurement Concept Instances | Not supplied | IS-U-LIB-UCM | Available | Initial Shipment Stack | 1823 |
| F8878A | Manage MCM Templates | Not supplied | IS-U-LIB-UCM | Available | Initial Shipment Stack | 1824 |
Waste management — IS-U-WA
| App ID | Exact app name | Supplied transaction code | Application component | Status | Backend stack | Source row |
|---|---|---|---|---|---|---|
| F8874 | Weighing Overview | Not supplied | IS-U-WA | Available | Initial Shipment Stack | 1829 |
Decide
| Question | If yes | If no |
|---|---|---|
| Is the scenario an exception, overview or monitoring task? | Strong Fiori candidate. Shortlist the app and test it with real volumes. | Expect SAP GUI for HTML to remain the working UI. Plan the launchpad tile for it. |
| Does the app’s supplied code match the transaction your users run today? | Treat it as an association. Compare the actual tasks performed, including reversals and mass changes. | Do not infer a gap. A blank code means the export supplies none. |
| Is the process in scope for this customer (waste, measurement concepts)? | Include the app in role design. | Leave it out of the launchpad. Catalogued is not the same as required. |
Do this
- Prepare · Utilities functional lead — List the transactions your billing, meter reading and operations teams actually use, with monthly volumes, from usage statistics.
- Prepare · Utilities functional lead — Map each one to the apps above by business task, not by transaction code. Record exclusions explicitly.
- Explore · Fiori lead — Activate the shortlisted apps in the sandbox for the exact target stack and confirm each one against SAP’s implementation information.
- Explore · Business process owner — Run one normal case, one exception and one high-volume case per app.
- Realize · Security lead — Build roles from the approved shortlist. Keep GUI fallback until task coverage, authorization and performance are all proven.
Build the billing journey around its overview, order processing, errors, outsorts and invoicing exceptions, in that order. Keep meter-reading exceptions separate from billing exceptions: they have different owners and different clocks. BPEM clarification cases in Utilities (F7255, F7256) are not the same thing as Convergent Invoicing clarification cases (F2349).
Four apps share EA05, two share EL31 and two share EASIBI. A shared code tells you the apps are related. It does not tell you which one your users need. A display app is not a replacement for result entry, and an overview is not a replacement for processing.
All values above come from the SAP export of September 2026 for product 2025 (Private Cloud). App IDs, names, components, statuses and transaction codes are reproduced exactly as supplied. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library.
On a Utilities conversion, the most valuable early win is usually the periodic billing and invoicing overviews for the billing team lead, because they replace a morning routine of several reports. Start the adoption story there.
Related reading
- Fiori 2025 App Explorer — search all 3,185 apps, including descriptions and role hints.
- SAP Utilities billing and invoicing — process fundamentals.
- FI-CA and Convergent Invoicing Fiori apps in S/4HANA 2025
Frequently asked questions
How many SAP Utilities Fiori apps are there in S/4HANA 2025?
The September 2026 export for product 2025 (Private Cloud) contains 20 apps whose application component begins with IS-U. That is the SAPUI5 population only. It does not count SAP GUI for HTML tiles, and it is a snapshot, so check the live library for your exact target stack.
Does a Fiori app with transaction code EA05 replace EA05?
Not necessarily. Four different apps carry EA05 in the export: two overviews, a billing outsort app and an invoicing outsort app. The code is an association supplied by SAP, not a statement of functional equivalence. Validate each business scenario before removing GUI access.
Which business role do the billing apps belong to?
The export descriptions for F2709 and F3135 name the role template SAP_BR_BILLING_SPECIALIST_ISU, and F7256 names SAP_BR_OPERATIONS_SPEC_ISU. Treat these as starting points for role design, not as a complete authorization specification.
Further reading
Continue your trail
You now have the Migration context.
Save this guide, continue to the next concept or return to the Knowledge Library with your context intact.
Migration
22 resources in this area.
Practical SAP notes, structured for review, reuse and long-term maintenance.
Working on an FI-CA or IS-U implementation? I take on a limited number of advisory and architecture engagements.
Get in touch →