Schedule Demo
Comprehensive List of SAP Fiori T-Codes
4-min read
Published: 07.14.2025 | Updated: 07.17.2025

List SAP Fiori T-Codes by Function and Type

T-CodeFunctionType
/UI2/FLPLaunch SAP Fiori LaunchpadFiori Launchpad and UI2 Transaction Codes
/UI2/FLPD_CUSTLaunch Fiori Launchpad Designer (Client-specific customization)Fiori Launchpad and UI2 Transaction Codes
/UI2/FLPD_CONFLaunch Fiori Launchpad Designer (Cross-client configuration)Fiori Launchpad and UI2 Transaction Codes
/UI2/FLPCM_CUSTLaunch Fiori Launchpad Content Manager – Client-specific customizationFiori Launchpad and UI2 Transaction Codes
/UI2/FLPCM_CONFLaunch Fiori Launchpad Content Manager – Cross-client configurationFiori Launchpad and UI2 Transaction Codes
/UI2/FLCPerform Fiori Launchpad configuration and consistency checksFiori Launchpad and UI2 Transaction Codes
/UI2/FLIAAnalyze Fiori Launchpad intent navigation mappingFiori Launchpad and UI2 Transaction Codes
/UI2/FLP_CONTCHECKCheck content configuration issues in Fiori LaunchpadFiori Launchpad and UI2 Transaction Codes
/UI2/FLP_INTENTCHECKVerify intent-based navigation consistency in FLPFiori Launchpad and UI2 Transaction Codes
/UI2/FLTMaintain and translate Fiori Launchpad textsFiori Launchpad and UI2 Transaction Codes
/UI2/CUSTAccess SAP Fiori Implementation Guide (IMG)Fiori Launchpad and UI2 Transaction Codes
/UI2/CACHERegister OData/UI2 services for cachingFiori Launchpad and UI2 Transaction Codes
/UI2/CACHE_DELDelete cache entries (global/user-level)Fiori Launchpad and UI2 Transaction Codes
/UI2/PERS_DELCleanup personalization data (user-specific settings)Fiori Launchpad and UI2 Transaction Codes
/UI2/CHIPRegister UI2 CHIPs (reusable UI components)Fiori Launchpad and UI2 Transaction Codes
/UI2/NAVRegister target mappings for intent-based navigationFiori Launchpad and UI2 Transaction Codes
/UI2/NAVPROVDefine navigation providers for UI2-based navigationFiori Launchpad and UI2 Transaction Codes
/UI2/SEMOBJDefine custom semantic objects for navigationFiori Launchpad and UI2 Transaction Codes
/UI2/SEMOBJ_SAPView SAP-delivered standard semantic objectsFiori Launchpad and UI2 Transaction Codes
/UI2/GW_ACTIVATEActivate Gateway services for UI2SAP Gateway and OData Configuration
/UI2/GW_APPS_LOGReview Gateway application logsSAP Gateway and OData Configuration
/UI2/GW_ERR_LOGAccess Gateway error logs specific to UI2 appsSAP Gateway and OData Configuration
/UI2/GW_MAINT_SRVMaintain Gateway UI2/OData servicesSAP Gateway and OData Configuration
/UI2/GW_SYS_ALIASManage SAP system aliases for Gateway routingSAP Gateway and OData Configuration
/n/UI2/GW_SYS_ALIASAlias: Same as /UI2/GW_SYS_ALIASSAP Gateway and OData Configuration
/UI2/NWBCStart NWBC (NetWeaver Business Client) in UI2 environmentNWBC and POWL Tools
/UI2/NWBC_CFG_CUSTMaintain customer-specific NWBC configurationNWBC and POWL Tools
/UI2/NWBC_CFG_SAPMaintain SAP-delivered NWBC configurationNWBC and POWL Tools
/UI2/NWBC_CFG_P_CUSTDefine customer-specific NWBC launch parametersNWBC and POWL Tools
/UI2/NWBC_CFG_P_SAPDefine SAP-specific NWBC launch parametersNWBC and POWL Tools
/UI2/POWLRegister Personal Object Worklist (POWL) for OData consumptionNWBC and POWL Tools

/IWFND/MAINT_SERVICE, /IWFND/ERROR_LOG, /UI2/GW_SYS_ALIAS, /UI2/GW_ACTIVATE, /UI2/GW_APPS_LOG, /UI2/GW_ERR_LOG and /UI2/GW_MAINT_SRV are the commonly used transaction codes related to SAP Fiori, that are used for SAP Gateway Hub and OData Services management.

T-CodesDescription
/IWFND/MAINT_SERVICEThis T-code enables administrators to register new services with the SAP Gateway hub, activate the service to make the service endpoint available to client applications, and is also used for troubleshooting connectivity issues with existing services.
/IWFND/ERROR_LOG It’s used for monitoring and troubleshooting issues with the OData service. Whenever an error occurs during OData requests, such as authentication failures or problems with backend and front-end misconfiguration, the log is updated. For each error entry, administrators can drill down to obtain detailed information.
/UI2/GW_SYS_ALIASIt is used to define and maintain system aliases that connect the Fiori launchpad to the backend system. System aliases are crucial for routing OData requests from the Gateway hub to the backend system where the service’s data is stored.
/UI2/GW_ACTIVATEThis command is used to enable and activate the ICF nodes, services, and components required for the Gateway to function and serve Fiori applications.
/UI2/GW_APPS_LOG This T-Code provides a viewer for application-specific logs generated by Fiori applications and the Gateway component. Unlike the generic Gateway error logs, it provides detailed logs specific to the functionality of individual Fiori applications and Gateway services, which helps in debugging failed app loads, incorrect data rendering, or performance issues.
/UI2/GW_ERR_LOG It provides a dedicated viewer for Gateway-specific errors, which helps troubleshoot issues where apps are not loading correctly or if there are rendering problems on the Fiori launchpad.
/UI2/GW_MAINT_SRVManages the already registered OData services, such as adjusting service details after backend upgrades, refreshing metadata, and switching system aliases without re-registering the service.

Read More on SAP Transaction Codes by Module: