SAP Fiori Transaction Code Lookup | Utilities and FI-CA S/4HANA 2025

In 30 seconds

What it is 27 supplied transaction codes link to at least one Utilities or FI-CA Fiori app in the September 2026 export. A shared code means the apps are related to the same transaction, not that one replaces it or that the others are redundant. Build your own business-task register from this table; do not treat it as a completed mapping.

Transactions EA05, EASIBI, EL01, EL27, EL28, EL31, EMMACL, ES21, ES22, FP04, FP04H, FP30, FP31, FPE1, FPM3, FPM4

You use it when You have a list of transactions your Utilities or FI-CA users run and need to find which Fiori apps the SAP export associates with each one.

Guide covers Migration / Fiori Apps, Roles and Launchpad

Why it matters

Consultants scope Fiori by starting from the transaction list their users already run. That only works if the lookup is built correctly: a supplied transaction code is SAP’s association between an app and a transaction, not a certificate that the app replaces it. Read the code column as a starting point for investigation, and confirm what each app can and cannot do before you put it on a role.

How to read an association

App / group	Supplied code	Correct treatment
F2562 Manage Business Partner Items	FP04	Preserve the association. Do not infer that every FP04 scenario is supported or that the app has only write-off functionality.
F3125 Display Write-Offs	FP04H	Preserve FP04H exactly; do not replace it with FP04.
F2185 Resolve Implausible Meter Readings	EL27	The export resolves this transaction association; treat it as supplied.
F2186, F2709, F2801, F3253	EA05	Retain all four links; overview, billing outsort and invoicing outsort apps remain separate records, not duplicates.
F3133 Process Missing Billing Orders	EL01	Preserve as supplied; investigate the business-task relationship before approving replacement.
F3134 Display Outstanding Billing Items	EL28	Preserve as supplied; a display app must not automatically be treated as result-entry replacement.
F5493 and F5494	FKKBIXBIT_ERR_MON	Preserve the shared value; separately validate consumption-item versus billable-item error-log scope.
F4494 Reverse Document	Not supplied	Do not insert a transaction code as a source fact. Any replacement assessment for this app is editorial.

The lookup

Supplied transaction code	Associated apps	Component
EA05	F2186 — Resolve Outsorted Billing Documents; F2709 — Periodic Billing Overview; F2801 — Outstanding Billing Overview; F3253 — Resolve Outsorted Invoicing Documents	IS-U-BI, IS-U-IN
EASIBI	F3339 — Process Billing Orders; F3358 — Process Billing Errors	IS-U-BI
EL01	F3133 — Process Missing Billing Orders	IS-U-BI
EL27	F2185 — Resolve Implausible Meter Readings	IS-U-DM-MR
EL28	F3134 — Display Outstanding Billing Items	IS-U-BI
EL31	F3132 — Display Suppressed Billing Orders; F2786 — Periodic Meter Reading Overview	IS-U-BI, IS-U-DM-MR
EMMACL	F7256 — Manage BPEM Clarification Cases	IS-U-TO-MMA
ES21	F3131 — Block Utilities Contracts	IS-U-MD
ES22	F2708 — Release Blocked Utilities Contracts	IS-U-MD-CA
FKKBIX_BILLPLAN	F2824 — Manage Billing Plans	FI-CA-INV-FIO
FKKBIX_BILLREQ_MON	F2389 — Manage Credit/Debit Memos	FI-CA-INV-FIO
FKKBIXBIT_ERR_MON	F5493 — Display Error Logs - Consumption Items; F5494 — Display Error Logs - Billable Items	FI-CA-INV-FIO
FKKBIXBIT_MON	F1427 — Analyze Unbilled Items; F2621 — Manage Billable Items	FI-CA-INV-FIO, FI-CAX-INV-FIO
FKKBIXBIT_UPLOAD	F4664 — Upload Billable Items	FI-CA-INV-FIO
FKKBIXBIT02_TRANS_MA	F7031 — My Inbox for Convergent Invoicing	FI-CA-INV-FIO
FKKBIXCIT_MON	F3410 — Manage Consumption Items	FI-CA-INV-FIO
FKKBIXCIT_UPLOAD	F5081 — Upload Consumption Items	FI-CA-INV-FIO
FKKINV_MON	F2622 — Manage Invoicing Requests	FI-CA-INV
FKKINVBILL_DISP	F2250 — Display Billing Documents	FI-CA-INV-FIO
FKKINVDOC_DISP	F2048 — Manage Invoicing Documents	FI-CA-INV-FIO
FP04	F2562 — Manage Business Partner Items	FI-CA-FIO
FP04H	F3125 — Display Write-Offs	FI-CA-FIO
FP30	F2588 — Search Payments; F3978 — Search Payments in Lots	FI-CA-FIO
FP31	F3977 — Search Payments in Payment Runs	FI-CA-FIO
FPE1	F6109 — Manage Documents (FI-CA)	FI-CA-FIO
FPM3	F3678 — Maintain Dunning Notices	FI-CA-FIO
FPM4	F3126 — Display Returns	FI-CA-FIO

Do this

Prepare · Functional lead — Build a many-to-many business-task register: one row per business task, the transaction(s) it uses today, and the app(s) this lookup associates with those transactions.
Prepare · Functional lead — Record the evidence for each proposed mapping (the export row, or the app description) and record exclusions explicitly when an app does not cover the task.
Explore · Fiori lead — Never overwrite the source transaction code or app name with a proposed mapping. Keep the supplied values and your interpretation in separate columns.
Explore · Business process owner — For any transaction code not in this table, search the Fiori 2025 App Explorer before concluding no app exists — the code may belong to a core-ERP app outside Utilities/FI-CA scope.

Utilities and FI-CA share no transaction codes at all in this export. Of the 27 distinct codes in the table above, 9 appear only on IS-U apps and 18 only on FI-CA apps; not one code appears on both an IS-U and an FI-CA app. That is a clean split, and it reflects how separate the two functional areas are even where they meet, as in Convergent Invoicing billing for Utilities contracts. Do not assume a code from one area applies in the other.

A code that links to more than one app is common: 108 of the 514 distinct supplied codes in the full export link to more than one app. Do not read a multi-app link as redundancy — it usually means SAP split one transaction’s scope across an overview, a processing app and an exception app.

Across the full September 2026 export of 3,185 apps for product 2025 (Private Cloud), 726 apps carry a supplied transaction code, across 514 distinct codes, of which 108 link to more than one app. The Utilities and FI-CA lookup above is the subset of that population scoped to IS-U and FI-CA apps. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library.

Build the business-task register as a living document, not a one-time export. Every time a business process owner disputes a mapping, record the outcome instead of quietly changing the row — the audit trail is what makes the shortlist defensible during sign-off.

Fiori 2025 App Explorer — search all 3,185 apps by code, component or keyword.
SAP Utilities Fiori apps in S/4HANA 2025
FI-CA and Convergent Invoicing Fiori apps in S/4HANA 2025

Frequently asked questions

How many Utilities and FI-CA transaction codes have a Fiori app association?

27 distinct transaction codes link to at least one IS-U or FI-CA Fiori app in the September 2026 export. Across the full 3,185-app export, 726 apps carry a supplied transaction code; those codes resolve to 514 distinct values, and 108 of the 514 are linked to more than one app.

If a transaction code links to two apps, does that mean I need both?

Not automatically. A shared code tells you SAP associated both apps with the same transaction, usually because each app covers one facet of it (an overview versus a processing app, for example). Decide per business task, not per code.

What does it mean if my transaction code is not in this table?

Either no Utilities or FI-CA Fiori app in this export carries that code, or the app that does carry it sits outside the Utilities/FI-CA scope. Search the Fiori 2025 App Explorer for the code directly before concluding no app exists.