SAP Fiori TCodes List: Complete Guide with Descriptions

Categories :

Last Update :10 August 2026

Publish Date :10 August 2026

Admin

Content Writer

This guide is for SAP learners, administrators, developers, and consultants. It explains essential SAP Fiori TCodes, their purposes, configuration uses, troubleshooting applications, and practical selection for common Fiori tasks.

SAP Fiori TCodes List: Complete Guide with Descriptions

SAP Fiori is an advanced and role-based solution for interaction with the applications developed by SAP, however, the technical configuration of user-friendly UI still requires several SAP Tcodes. For SAP developers, admins, and consultants, knowledge of the correct SAP Fiori Tcodes will make their life easier in such processes as enabling OData services, configuring LaunchPad, and other important activities.

But Fiori T-codes may not be available in all SAP systems. They may differ from one SAP S/4HANA release to another as well as differ based on deployment model and architecture. This document provides details about the commonly used Fiori T-codes, their purpose, and when to use them.

For those looking to acquire SAP skills on a wider scale, the SAP courses at Srijan Institute are worth considering. For both beginners and experienced SAP practitioners alike, this guide can provide some insight into the technical transactions needed for SAP Fiori.

What Are SAP Fiori TCodes?

Transaction codes in SAP systems are short commands that allow users to directly access particular functions in the system. A Fiori TCode in SAP is normally referred to as a transaction that is used for configuring, administering, monitoring or troubleshooting the technical foundation for SAP Fiori.

It is important to distinguish between Fiori apps and Fiori TCodes. Fiori apps are designed primarily for users to perform business tasks through role-based interfaces, whereas TCodes are commonly used by administrators, developers, and consultants to manage the technical environment behind those applications. Fiori-related TCodes support activities such as OData service activation, SAP Gateway administration, Fiori Launchpad configuration, ICF service management, authorization analysis, and error investigation.

The exact transaction required depends on the task, SAP release, and system architecture. Therefore, professionals should verify the appropriate TCode and procedure for their environment. For learners seeking practical knowledge of these technical components, structured SAP training can provide valuable context and hands-on understanding.

SAP Fiori TCodes List with Descriptions

SAP Fiori TCode	Description	Primary Fiori Use	When to Use
/IWFND/MAINT_SERVICE	Used to activate, maintain, and manage OData services on the SAP Gateway/frontend server. It is one of the key transactions used when preparing backend services for Fiori applications.	OData service activation and maintenance	Use when a Fiori application requires an OData service to be registered, activated, or maintained.
/IWFND/ERROR_LOG	Displays errors generated during OData request processing on the Gateway/frontend server. It provides technical information that can help administrators identify the cause of failed Fiori requests.	Frontend Gateway and OData troubleshooting	Use when a Fiori app produces a Gateway, OData, or service-related error.
/IWBEP/ERROR_LOG	Provides access to errors occurring during OData processing in the backend Gateway system. It helps identify problems originating from backend services or application logic.	Backend Gateway troubleshooting	Use when an OData request reaches the backend but fails during processing.
SICF	Provides access to Internet Communication Framework service maintenance. Administrators can use it to check whether required HTTP services and ICF nodes are active.	ICF and web service management	Use when a Fiori application or related web service cannot be reached because an ICF service may be inactive.
SU53	Displays failed authorization checks for the current user. It is commonly used to identify missing authorizations when users cannot access Fiori applications or related SAP functions.	Authorization troubleshooting	Use when users receive authorization errors or cannot access assigned Fiori functionality.
ST22	Displays ABAP short dumps generated by runtime errors. The transaction provides technical information that can help identify backend problems affecting Fiori applications.	ABAP runtime error analysis	Use when a Fiori request or backend process results in an ABAP runtime dump.
SM21	Provides access to the SAP system log, which records system-level events, warnings, and errors. It can provide additional context when troubleshooting complex Fiori issues.	System-level monitoring	Use when the problem may involve broader SAP system events rather than only Fiori or Gateway components.
/UI2/FLPD_CUST	Supports customer-specific Fiori Launchpad configuration in SAP environments where the Launchpad Designer transaction is available. Its relevance depends on the SAP release and configuration approach.	Launchpad customization	Use in supported systems for applicable Launchpad content and configuration activities.
/UI2/FLPD_CONF	Provides Launchpad Designer configuration capabilities in supported SAP environments. Its availability and recommended use depend on the SAP release and Launchpad architecture.	Launchpad configuration	Use when performing supported Launchpad configuration activities through Launchpad Designer.
/UI2/FLPCM_CUST	Launchpad Content Manager transaction used for managing client-specific Launchpad content. It can support activities involving business catalogs and application content in supported environments.	Launchpad content management	Use when managing or customizing Fiori Launchpad content at the client level.

If you want to build practical expertise in these areas, a dedicated SAP Fiori course can help you understand how Fiori apps, Gateway, OData, Launchpad content, and authorizations work together.

Read More:
SAP Workflow TCodes List

Most Commonly Used SAP Fiori TCodes

SAP Fiori TCode	Primary Purpose	When to Use It
/IWFND/MAINT_SERVICE	OData service maintenance	Use it to check, activate, and maintain OData services required by Fiori applications.
/IWFND/ERROR_LOG	Frontend Gateway error analysis	Use it when a Fiori application generates a Gateway or OData-related error on the frontend.
/IWBEP/ERROR_LOG	Backend Gateway error analysis	Use it when an issue originates during backend OData or Gateway processing.
SICF	ICF service management	Use it to check and activate relevant Internet Communication Framework services required by applications.
SU53	Authorization analysis	Use it when a user encounters an authorization-related error while accessing a Fiori application.
ST22	ABAP dump analysis	Use it to investigate ABAP runtime errors or short dumps affecting Fiori functionality.
SM21	SAP system log analysis	Use it to review system-level events and errors that may affect Fiori applications.

SAP Fiori TCodes for App Management and Configuration

Configuration / Management Task	Exact TCode	What It Is Used For
Activate and maintain OData services	/IWFND/MAINT_SERVICE	Activate and maintain OData services required by Fiori apps. SAP documents this as the standard transaction for activating individual OData services in relevant Gateway scenarios.
Check ICF/Web services	SICF	Check, activate, and maintain relevant Internet Communication Framework services required for Fiori applications.
Manage business catalogs and Launchpad content	/UI2/FLPCM_CUST	Manage client-specific Fiori Launchpad content, including business catalogs.
Manage system-wide Launchpad content	/UI2/FLPCM_CONF	Manage Launchpad content in the configuration scope for system-wide changes.
Manage technical catalogs, tiles and target mappings	/UI2/FLPAM	Use the Fiori Launchpad App Manager for technical catalogs and related app/target-mapping management in supported releases.
Maintain technical catalogs	/UI2/FLPCAT	Create and maintain technical catalogs in supported SAP environments.
Maintain business roles and assignments	PFCG	Create/change roles and assign Fiori business catalogs and spaces/pages to roles.
Check authorization problems	SU53	Analyze failed authorization checks when users cannot access Fiori content or functionality.
Check Launchpad content consistency	/UI2/FLC	Check the consistency of delivered and customized Fiori Launchpad content.
Check orphaned Launchpad catalogs/groups	/UI2/FLC1	Identify and clean up orphaned Launchpad content where applicable.

SAP Fiori TCodes for Monitoring and Troubleshooting

Problem / Monitoring Area	TCode	Purpose	When to Use It
Frontend Gateway/OData errors	/IWFND/ERROR_LOG	Displays errors occurring during OData request processing in the Gateway/frontend system	When a Fiori app returns a Gateway, OData, or service-related error
Backend Gateway/OData errors	/IWBEP/ERROR_LOG	Displays errors occurring during backend OData processing	When /IWFND/ERROR_LOG indicates a backend error or the issue originates in the backend
Authorization failures	SU53	Shows failed authorization checks for a user	When a user cannot access an app or encounters an authorization error
Detailed authorization tracing	ST01	Performs authorization and other system traces	When SU53 does not provide enough information to identify the authorization issue
ABAP runtime errors	ST22	Displays and analyzes ABAP short dumps	When a Fiori-related backend process generates an ABAP runtime error
SAP system events	SM21	Displays the SAP system log	When investigating broader system-level warnings or errors
ICF service status	SICF	Maintains and checks Internet Communication Framework services	When a required web service or ICF node may be inactive

How to Use SAP Fiori TCodes

Using a Fiori TCode effectively starts with identifying the exact task or problem. Instead of searching randomly through transaction codes, determine whether the requirement concerns OData, Gateway, Launchpad configuration, authorizations, services, or backend errors.

For example, if a Fiori app displays an OData-related error, start by reviewing the relevant Gateway error log. If the error points to authorization, investigate the user's permissions with SU53. If the system generates an ABAP dump, move to ST22 for detailed analysis.

A practical process is:

Identify the Fiori application or issue.
Determine the affected technical component.
Select the appropriate TCode.
Review the configuration or error information.
Apply the required correction according to your organization's procedures.
Test the application again.
Document the change where necessary.

TCode access also depends on SAP authorizations. Users should not make configuration changes in production systems without the required permissions and change-management approval. SAP release documentation should also be consulted because transaction availability and recommended configuration procedures can change between releases.

SAP Fiori TCodes vs Fiori Apps

SAP Fiori TCodes and Fiori apps are related but serve different purposes. Fiori apps are user-facing applications designed around specific business tasks, while TCodes generally provide access to SAP functions used for administration, configuration, monitoring, or troubleshooting.

Aspect	SAP Fiori TCodes	SAP Fiori Apps
Main purpose	Technical and administrative activities	Business process execution
Typical users	Consultants, developers, administrators	Business users
Interface	Often SAP GUI or technical interface	Fiori Launchpad/web interface
Focus	Configuration and system management	Role-based user experience
Example	/IWFND/MAINT_SERVICE	Purchase order management app

For instance, an administrator might enable an OData service via /IWFND/MAINT_SERVICE such that the Fiori app can work seamlessly with the backend system. The business user would access the customized application via the Fiori Launchpad.

Knowing the difference between the two concepts enables one to distinguish between these two terms at the beginner level, especially that TCodes are the technical concept whereas Fiori is the user experience.

Conclusion

SAP Fiori Tcodes knowledge becomes vital for the professionals who need to configure, administrate, monitor, and troubleshoot Fiori. Tcodes like /IWFND/MAINT_SERVICE, /IWFND/ERROR_LOG, /IWBEP/ERROR_LOG, SICF, SU53, and ST22 may be helpful in resolving the typical issues related to services, Gateway, authorizations, and runtime. But the correct Fiori Tcode will vary depending on the version of the SAP

Learning these transactions forms just one aspect of being adept in SAP Fiori. Experts must be knowledgeable about OData, SAP Gateway, Fiori Launchpad, business roles, authorizations, and SAP S/4HANA.

For anyone looking for practical and structured learning opportunities, Srijan Institute could serve as an excellent learning source. Are you ready to hone your SAP Fiori skills? Check out Srijan Institute's SAP and Fiori training courses.

FAQ Related to SAP FIORI Tcodes List

Q1. What are the most commonly used SAP Fiori TCodes?

A. Common SAP Fiori TCodes include /IWFND/MAINT_SERVICE for OData services, /IWFND/ERROR_LOG for Gateway errors, SICF for web services, SU53 for authorizations, and ST22 for dumps.

Q2. Is there a TCode for SAP Fiori Launchpad?

A. There is no single universal Fiori Launchpad TCode. Depending on the SAP release, transactions such as /UI2/FLPD_CUST, /UI2/FLPD_CONF, and /UI2/FLPCM_CUST support configuration and content management.

Q3. Which TCode is used to activate OData services in SAP Fiori?

A. /IWFND/MAINT_SERVICE is commonly used to activate and maintain OData services required by SAP Fiori applications in SAP Gateway environments, depending on the system architecture.

Q4. Which TCode is used to check SAP Fiori errors?

A. /IWFND/ERROR_LOG helps check frontend Gateway errors, while /IWBEP/ERROR_LOG investigates backend errors. ST22 analyzes ABAP dumps, and SU53 helps identify authorization failures.

Q5. What is the difference between SAP Fiori apps and SAP TCodes?

A. SAP Fiori apps provide role-based interfaces for business tasks, while SAP TCodes provide access to SAP functions commonly used for configuration, administration, monitoring, and troubleshooting.

Table of Content

Related Blog