SAP AS ABAP Administration · Presentation Layer: SAP GUI & NWBC

A 2013-era admin assumes that moving to S/4HANA and the Fiori Launchpad means classic SAP GUI transactions are gone. Where is that assumption wrong?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Presentation Layer: SAP GUI & NWBC

A team needs users to reach a single Web Dynpro application from any PC without rolling out SAP GUI or NWBC. What delivery option fits, and what is the only client-side requirement?

How does SAP GUI for HTML turn classic Dynpro screens into something a plain browser can display, and since which release is that component built in?

In NWBC, which area is driven by the user's assigned roles and which shows the actual transaction data, and why does that split matter?

Why can a single NWBC window show a classic ERP transaction and a Web Dynpro application at the same time, technically?

At the transport level, how does NWBC reach a managed system differently from the classic SAP GUI?

When defining an NWBC connection, what URL path and connection Type distinguish an ABAP system from a portal?

Start learning today

Free to start — download the app or use it in your browser.