Opening transaction in SAPGUI for HTML via URL fails (sometimes)

[tobias_grimm_ksg]

Hello, I would like to open the transaction QM02 (Edit Quality Notification) in the web browser for a certain quality notification number by clicking an link. SAP provides a target mapping for this:

• Catalog: X-SAP-UI2-ADCAT:SAP_TC_QM_BE_APPS:S4QM
• Semantic Objekt and Action: QualityNotification-change
• Target: Transaction QM02

The following URL parameters are intended for this navigation:

• QualityNotification > Mapped to dynpro target field RIWO00-QMNUM
• DynproNoFirstScreen > Mapped to DYNP_NO1ST (=1)
• sap-tag & sap-ach

The link therefore looks like this:

https://<host>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=
<client>#QualityNotification-change?QualityNotification=000230000001

When clicking this link, in about 50% of the attempts it works just as expected. SAPGUI for HTML opens with QM02, selection screen is skipped and the quality notification provided in the URL is opened. I can simple change the notification number from 000230000001 to 000230000002 and it will open this one instead. Everything works perfectly smooth just as expected:

However, in the other 50% of attempts, instead of directly opening the transaction, the following selection popup is displayed instead:

When the user closes the dialog, he simply sees the main selection screen of QM02. Now, when he enters a quality notification number manually, the transaction works fine. But, if he now clicks another link to open QM02 for a different notification, it will always open the notification he entered first in the session:

This is very dangerous as it will lead to the user editing the wrong notification. 
It feels like instead of creating a new session for QM02, an existing session is reused and therefore the notification number provided from the URL is ignored.

My questions are: 

• Why is the behavior so inconsistent? 
• What can I do to have the invoke of QM02 in the browser work every time?

What I already tried (with the same inconsistent behavior all the time): 

• Trying different quality notifications
• Trying with different users/logins
• Trying in different systems and clients (dev/test/prod)
• Trying in multiple browsers (Chrome, Firefox, Edge, ...) and clearing cache
• Trying with fresh browser restart and existing browser session
• Trying with another SAP GUI session (NWBC) open in the background (or not)
• Trying with different authentication methods (username/password or SSO)

My system: 

• SAP S/4HANA 2023 SAP SP01
• S/4HANA FOUNDATION 2023
• SAP FIORI FES 2023 FOR S/4HANA
• SAP FIORI FOR SAP
• S/4HANA 2023 ABAP PLATFORM 2023
• SAPUI5: 1.120.25

[tobias_grimm_ksg · Accepted solution]

I am now using a direct link to the WebGUI:

https://<host>/sap/bc/gui/sap/its/webgui?
~transaction=*QM02%20RIWO00-QMNUM=000200001234?sap-client=<client>

It looks like this approach is much more reliable than using the FIORI environment.

[DanielP]

@tobias_grimm_ksg - Try with this instead:

https://YOURSERVER.com/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?flp#QualityNotifica...

Hope this helps. /Daniel

[tobias_grimm_ksg]

Thank you for your answer. Unfortunately, it did not solve the problems.