SAP GUI for HTML (Web GUI)

SAP GUI for HTML keeps the classic transaction intact and changes only where its screens are drawn:

1. A user clicks a launchpad tile whose intent resolves to a target mapping of the transaction type, for example ME23N with a system alias.
2. The launchpad opens the transaction through the ICF service webgui on the ABAP system.
3. The Internet Transaction Server, which is part of the ABAP kernel, runs the dynpro and maps each screen field one to one onto an HTML page.
4. Every user action goes back to the server, which processes the dialog step and returns the next page.

Because the rendering happens on the application server, it consumes server CPU, and SAP suggests dedicating application servers when Web GUI usage is heavy. SAP GUI for HTML is therefore a server-side translation of an existing transaction, not a new user interface.

SAP GUI for HTML sits in the UI applications layer, next to SAPUI5 apps and Web Dynpro ABAP applications. The three reach users the same way: a tile or link fires an intent, and a target mapping decides what opens. Underneath, they differ completely. A SAPUI5 app calls OData services; a Web GUI transaction runs the classic dynpro logic directly, with no OData service in between.

The SAP Fiori Apps Reference Library reflects this. Classic transactions appear with the application type "SAP GUI" and use the transaction code as the app ID: ME23N, for instance, is listed as Display Purchase Order with the intent PurchaseOrder-display. SAP also provides SAP Fiori visual themes for classic applications so that Web GUI screens look closer to the launchpad around them. SAP GUI for HTML is a launch target inside SAP Fiori, not an SAP Fiori app.

Use SAP GUI for HTML when:

• no SAP Fiori app covers the task, or the SAP Fiori app covers only part of what users need;
• occasional users need one classic transaction and should not install SAP GUI for Windows;
• a role must offer every step of a job from one launchpad during a staged move to SAP Fiori apps.

Prefer an SAP Fiori app when one exists for the scenario, when users work on phones or tablets, or when the task benefits from drafts, side-by-side navigation and responsive layouts. A practical decision path: check the SAP Fiori Apps Reference Library for a transactional app or successor first, and fall back to the transaction only when the gap is real. SAP GUI for HTML is the right choice when coverage matters more than a native SAP Fiori experience.

SAP states that most functions of SAP GUI for Windows also run in SAP GUI for HTML, and lists the exceptions in SAP Note 314568. Examples from SAP's documentation:

• files cannot be dragged from the desktop file explorer onto an SAP screen;
• OLE automation is not available from the browser, which limits Microsoft Office integration;
• printing works through PDF documents generated in the SAP system;
• some search help (F4) behavior and some controls are restricted;
• mobile browsers lack functions such as right-click, so SAP does not generally release iOS as a platform.

Beyond technical restrictions, the screen itself does not change: dense layouts designed for a desktop client stay dense in a browser frame, and the transaction does not become responsive. The limits of SAP GUI for HTML come from translating a desktop dialog, not from the launchpad around it.

• On-premise and Private Edition: administrators activate the ICF services for Web GUI once per system, in SICF or through the SAP_FIORI_FOUNDATION_S4 task list run in STC01. They create target mappings of the transaction type for custom transactions and can check in SE93 which GUIs a transaction is flagged for in its GUI support settings.
• Hub deployment (deprecated): the launchpad runs on a separate front-end server, so each system alias needs HTTP or HTTPS destinations in SM59, named after the alias with the suffix _HTTP or _HTTPS. Embedded deployment is SAP's recommended option.
• Public Edition: SAP delivers selected SAP GUI for HTML apps in its business catalogs; the 2502 release, for example, added Maintain Quota Arrangement as a new SAP GUI for HTML app.
• SAP ERP: the ITS has been integrated into the kernel since SAP Web Application Server 6.40.

SAP GUI for HTML exists across deployments; what varies is who decides which transactions are exposed.

Work from the launchpad down to the transaction:

1. Intent resolution. Run /UI2/FLIA for the user. If no target mapping matches, the problem is catalog or role assignment, not Web GUI.
2. ICF services. An HTTP error or blank page usually means the webgui services are inactive in SICF on the system that runs the transaction.
3. System alias and destinations. In hub deployments, a missing or misnamed HTTP destination in SM59 sends the request nowhere.
4. Backend authorization. The transaction opens but stops with an authorization message; check the backend role for the transaction start authorization and analyze it with SU53 inside the session.
5. Transaction restrictions. The screen opens but a function misbehaves; compare it against SAP Note 314568 before raising a defect.

Most Web GUI tile failures are configuration or authorization gaps that appear in steps 1 to 4 before the transaction itself is ever at fault.