![Pathlock CEO Piyush Pandey on Reshaping Application Access Governance: Insights from KuppingerCole Reports](https://pathlock.com/wp-content/uploads/2023/08/KC_Report_Piyush_insights-112x112.jpg")
![Pathlock Reshapes the Access Governance Market with a Series of Strategic Mergers](https://pathlock.com/wp-content/uploads/2022/05/MicrosoftTeams-image-7-112x112.png")
SAP Fiori is the modern user experience interface for SAP applications, built on web technologies. However, the underlying SAP NetWeaver ABAP stack still uses traditional transaction codes (T-Codes) for various administrative, configuration, maintenance, and development tasks. These T-codes help troubleshoot issues such as application authorization errors and cache issues, and accelerate setup processes, serving as entry points into various technical and UI configuration areas of Fiori.
Developers can use these transaction codes to access the SAP Fiori launchpad designer, the Gateway Service Builder, and for debugging backend issues. Administrators can use T-codes to configure and maintain gateway services, monitor and troubleshoot application performance, and manage the cache to resolve UI inconsistencies.
What is T-Code to Launch SAP Fiori Launchpad in SAP GUI?
SAP Fiori launchpad can be launched with “/UI2/FLP” transaction code.
The /UI2/FLP transaction code is used in the SAP GUI client’s command field to open the Fiori launchpad in the default browser of the operating system. This mechanism provides a quick way to open the Fiori launchpad from within the SAP GUI client, helping to test or troubleshoot whether the Fiori launchpad is correctly configured and accessible from the backend system.
How to Open Fiori Launchpad via Direct Web Browser Access?
“/UI2/FLP” t-code is used to access the Fiori Launchpad directly in a browser by typing or copying the URL corresponding to an organization endpoint for Fiori launchpad as below:
https://<host>:<port>/sap/bc/ui2/flp
The above-mentioned is the standard URL structure for the Fiori launchpa , where:
- “https” defines the protocol,
- “host” name defines the server’s name, i.e., fioriserver,
- “port” defines the port number, i.e., 443,
- “/sap/bc/ui2/flp” is a standard path for Fiori launchpad’s ICF service.
Example URL can look like “https://fioriserver.demo.com:443/sap/bc/ui2/flp”.
In some cases, the following URL format is used, which is an older path to the Fiori launchpad and is helpful for backward compatibility with older SAP S/4HANA systems.
“https://<host>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html”
Upon accessing the URL, the launchpad will prompt for SAP credentials if SSO is not configured. After authentication, apps and tiles relevant to the assigned role will be displayed.
How to Open Fiori Launchpad via /etc/hosts File Modifications?
“/UI2/FLP” Transaction code is used to open the Fiori launchpad by pointing a server to a specific IP address and resolve the Server DNS name to that IP address by making changes in the host file
This workaround is particularly helpful in development lab environments, as it allows the local development machine to point to a specific Fiori frontend server without modifying the global DNS configuration, even in the absence of DNS services.
Steps for local DNS override:
First, obtain the IP address of the server hosting the SAP Fiori environment. This can be a pre-configured virtual machine. For example, https://fioriserver.demo.com:443/sap/bc/ui2/flp is the Fiori launchpad URL, and “fioriserver.demo.com” is the DNS name we want to resolve locally, which is mapped to IP address 10.20.6.40, accessible within the local lab environment.
On the client machine, i.e., macOS, launch Terminal from the Utilities folder.
- Run the following command to open the host file.
sudo nano /etc/hosts
- Add the following entry to the host file.
10.20.6.40 fioriserver.demo.com
- Save the file and exit.
- To ensure that changes in the host file are implemented immediately, flush the DNS cache.
sudo killall -HUP mDNSResponder
What are Transaction Codes to Launch Fiori Launchpad Designer?
“/UI2/FLPD_CUST” is the t-code that launches the Fiori launchpad designer in “customizing” mode, and changes made here affect only the current SAP client, where as “/UI2/FLPD_CONF” T-code opens the launchpad designer in configuration mode, and changes made are applied to all clients.
The following is the standard URL for client-specific customization for “/UI2/FLPD_CUST”
“https://<host>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=<client>&scope=CUST”
, where:
- “ https://<host>:<port>” portion defines the protocol, server name, and port number,
- “/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html” portion is the standard path to the Fiori launchpad designer application.
- “?sap-client=<client>” is the crucial part, and this portion of the URL defines the specific client to which the changes will be implemented.
- “&scope=CUST” parameter explicitly tells the launchpad designer to open in customization mode.
The following is the standard URL for cross-client configurations for “/UI2/FLPD_CONF
https://<host>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?scope=CONF
, where:
- “sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html” is the path to the designer application,
- “?scope=CONF” parameter explicitly sets the designer to configuration mode.
Uses and Differences for (/UI2/FLPD_CUST, scope=CUST) and (/UI2/FLPD_CONF, scope=CONF
- Customization (/UI2/FLPD_CUST, scope=CUST) is useful when the changes performed are required for a specific SAP client. Developers can create, customize, and test new Fiori content in their development client without impacting other clients, and quickly set up Fiori content for demo or proof of concept within a single client.
- Configuration (/UI2/FLPD_CONF, scope=CONF) helps define core Fiori content such as standard catalogs, comment semantic objects, and foundational tiles that should be available and consistent across all clients. Provide a standardized Fiori user experience across different departments or user groups within the exact SAP System.
What are T-Codes to Open SAP Fiori Launchpad Content Manager ?
/UI2/FLPCM_CUST and /UI2/FLPCM_CONF are the transaction codes to open SAP Fiori Launchpad Content Management in customizing mode and in configuration mode respectively. Below is the description of each of transaction codes:
| T-Codes | Description |
|---|---|
| /UI2/FLPCM_CUST | /UI2/FLPCM_CUST transaction code launches the Fiori launchpad content manager (FLPCM) in customizing mode, and changes made using this transaction are client-specific. Using this code, administrators can edit catalogs, tiles, and target mapping in the current client, filter content based on role, app ID, and create copies of the standard catalogs. |
| /UI2/FLPCM_CONF | /UI2/FLPCM_CONF FLPCM in configuration mode, and changes made using this transaction are applied cross-clients. It’s used for defining global configuration and base catalogs for all clients, providing a standardized user experience. |
Side Note: Fiori launchpad content manager (FLPCM) is a GUI-based tool introduced in S/4HANA 1809 and later versions to manage large volumes of Fiori catalogs, groups, and roles. Unlike launchpad designer, FLPCM provides mechanisms to efficiently handle bulk operations, advanced filtering, direct integration with Fiori catalogs and roles, making it a suitable tool for both developers and administrators.
What are T-Codes for Gateway and OData Service Management?
/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 transaction codes for SAP Gateway Hub and OData Services management. Below is the description of each of the URL:
| T-Codes | Description |
|---|---|
| /IWFND/MAINT_SERVICE | This 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_ALIAS | It 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_ACTIVATE | This 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_SRV | Manages the already registered OData services, such as adjusting service details after backend upgrades, refreshing metadata, and switching system aliases without re-registering the service. |
What are Transaction Codes for Semantic Object and Navigation Configuration?
/UI2/SEMOBJ_SAP, /UI2/SEMOBJ, /UI2/NAV and /UI2/NAVPROV are the four transaction codes that are used for creating, modifying and managing semantic object and navigation configuration with in SAP Fiori Launchpad:
| T-Codes | Description |
|---|---|
| /UI2/SEMOBJ_SAP | It enables administrators to view predefined semantic objects delivered by SAP, along with its best practices for reusing standard semantic objects where available. While configuring a tile for a standard SAP Fiori app, such as Manage Purchase Orders, this T-code can be used to confirm the correct semantic object, e.g., PurchaseOrder and Action, as ‘manage’. |
| /UI2/SEMOBJ | It is used to create and manage custom semantic objects, which are particularly useful when a custom Fiori application is integrated with business entities not typically covered by SAP’s standard semantic objects. For example, if a custom Fiori application, such as “customer contracts,” is created, the UI2/SEMOBJ T-code can be used to create a new semantic object, i.e., zCustomerContract, and used to configure a Fiori tile to launch this app. |
| /UI2/NAV | It is used to define a mapping between a semantic object-action pair and a Fiori application or any other navigation target, thereby maintaining intent-based navigation. For example, when a user clicks on the “Manage Sales Orders” tile , the Fiori launchpad checks for its target mapping. It finds the SAP UI5 component associated with a specific system alias, launching the Sales Orders Fiori app. |
| /UI2/NAVPROV | It is used to define “navigation providers,” which are services or roles that solve navigation targets to the Fiori launchpad. While /UI2/NAV defines explicit target mappings, navigation providers all support more dynamic or role-based mapping for navigation options. |
What are T-Codes for System Configuration and Launchpad Integrity Checks?
/UI2/CUST, /UI2/FLC, /UI2/FLIA, /UI2/FLP_CONTCHECK, /UI2/FLP_INTENTCHECK and /UI2/FLT are the transaction codes to access key utilities that are used for system configuration and launchpad integrity checks.
T-Codes for Cache, Personalization, and Development in Fiori Launchpad
The SAP Fiori launchpad relies on caching to provide a fast and responsive user experience, and it offers personalization capabilities that allow users to customize their launchpad.
Cache and Personalization Transaction Codes
| T-Codes | Description |
|---|---|
| /UI2/CACHE | This utility registers OData Services and launchpad resources that need to be cached on the client side for performance optimization. |
| /UI2/CACHE_DEL | Provides a mechanism to delete cached data and force the Fiori launchpad to fetch the latest information from the backend, which is helpful after configuration changes and for troubleshooting. |
| /UI2/PERS_DEL | Allows administrators to delete user-specific personalization settings and reset the Fiori launchpad to its default layout and settings. |
CHIPs and POWL Transaction Codes
| T-Codes | Description |
|---|---|
| /UI2/CHIP | This utility is used to manage SAP UI CHIP, which are reusable UI components, such as graphs, tables, and alerts, for dashboards or side panels. |
| /UI2/POWL | Using this utility, administrators can define Personal Object Worklists (POWL) queries to display a list of work items relevant to different user sets. POWL queries are mapped to OData service entities, and specific fields can be exposed in the OData service. |
What are T-Codes for NetWeaver Business Client Configuration and UI Settings?
/UI2/NWBC, /UI2/NWBC_CFG_CUST, /UI2/NWBC_CFG_SAP, /UI2/NWBC_CFG_P_CUST and /UI2/NWBC_CFG_P_SAP are transaction codes are primarily used for configuring and mapping NetWeaver Business Client, which serves as a unified environment to access classic SAP GUI transactions, Web Dynpro, and Fiori content.
| T-Codes | Description |
|---|---|
| /UI2/NWBC | This transaction code is used to launch NetWeaver Business Client from within the SAP GUI and opens the NWBC interface in either desktop or browser mode. |
| /UI2/NWBC_CFG_CUST, /UI2/NWBC_CFG_SAP | The T-code defines global and system-specific settings that control NWBC’s appearance and behavior, including Shell configuration, branding, theme, connection, and performance settings. |
| /UI2/NWBC_CFG_P_CUST | The T-code is used to configure and define customer-specific parameters, which override the corresponding parameters in the SAP standard table. |
| /UI2/NWBC_CFG_P_SAP | The T-code is used to review and adjust SAP-defined default parameters. |
Conclusion
While SAP provides extensive official documentation, real-world implementation and complex scenarios often reveal highly practical and time-saving T-codes, enabling efficient task completion. Explore shared solutions and troubleshooting steps to reduce the time spent on recurring issues, minimize rework effort, and provide learning from well-documented remedies found in community blogs or knowledge bases.
SAP Fiori and SAPUI5 are continually evolving, with new features, tools, and best practices being introduced regularly. Establishing a centralized knowledge base in the form of an organization community or a SharePoint site, having knowledge base articles for specific scenarios, step-by-step guides for configuration and customization, scenario-based resolutions helps minimize dependency on individual experts, promotes a culture of shared responsibility, and supports faster project rollouts and consistent deployment across different regions.
