How to “Convert” SAP GUI T-Codes into Fiori Apps

 A Colleague asked me this recently — and yes, it’s also a common interview question.

As an SAP Security Consultant, enabling SAP GUI transactions as Fiori tiles is a core skill, especially in S/4HANA landscapes.

Below is the 4-step workflow I consistently use to expose standard SAP GUI transactions in the Fiori Launchpad.

---

1️⃣ Check if the Transaction Is Web-Ready

(SE93)

Before doing anything else, verify the transaction in SE93.

• Ensure SAP GUI for HTML is supported

• Test whether the transaction runs in a browser

👉 If it doesn’t work in a browser, it cannot work as a Fiori tile.

---

2️⃣ Create the Technical Definition

(Launchpad App Manager – FLPAM)

This step defines the technical identity of the app.

• Map the T-code to a Semantic Object

• Assign an Action (e.g., Display, Manage)

• Maintain the technical parameters required to launch the app

This is where the backend knows what the app is and how it should be called.

---

3️⃣ Add to a Business Catalog

(Fiori Content Manager – FLPCM)

Now make it visible to users.

• Add the technical app to a Business Catalog

• Assign it to the appropriate Spaces / Pages

• Ensure the tile is user-friendly and business-relevant

This step controls what the user sees in the Launchpad.

---

4️⃣ Assign via Role

(PFCG)

Final step — authorization and access.

• Add the Fiori Launchpad Business Catalog to the role menu

• Generate the role to pull required authorizations
  (including S_SERVICE, ICF, and backend checks)

Once assigned, the user can launch the transaction directly from Fiori.

---

🎯 Why This Matters

• One Launchpad

• One login

• No switching between SAP GUI and browser

It delivers a seamless user experience and aligns perfectly with S/4HANA and Fiori UX principles.