Symptom
In the Manage Purchase Orders app, some purchase orders are displayed in the app itself and can be changed from there, but others are open in the Display Purchase Order - Advanced (WEBGUI) app.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the Manage Purchase Order App.
- Search for and select a purchase order.
- Observe that the navigation leads to a GUI application/tile instead of staying within the Fiori app’s page.
Cause
When a PO is selected in the Manage Purchase Orders app, the system executes a number of checks on the fields at header and item levels:
- If all the field checks pass, the PO will be displayed in the app itself.
- If any of the field checks fail, then the PO will be displayed in Advanced (WEBGUI) application.
The reason for this, is that the app does not cover all the features of the traditional backend transaction ME22N/ME23N(App Change/Display Purchase Order - Advanced). The complexity of the backend GUI transactions is deliberately removed.
So in general, if a field does not exist in the app, but it is filled in the purchase order, then the corresponding document is open in the WEBGUI app where the user can process these fields if required. You may come across this behavior, for example, for purchase orders that were not created by the app; for POs that were changed in the Gui App afterward; or for other specific fields that are populated right after PO is created in the app.
When navigating from other apps to the Manage Purchase Orders app, the PO is displayed in the app but changes cannot be performed due to the reasons explained above. Therefore, to edit this PO, open it directly in the Manage Purchase Orders app, where the system can redirect it to the Advanced app.
This is standard system behavior.
Resolution
For unsupported purchase orders, an "Advanced indicator" is displayed next to the PO number (it is exclusively displayed in the Manage Purchase Orders app).
In the "Advanced indicator", users can view the specific information of Unsupported Features.
Keep in mind that this behavior cannot be configured. The PO will open in the Fiori app or in the WEBGUI app depending exclusively on the checks mentioned in the Cause section.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Keywords
fiori, manage purchase requisitions, manage purchase orders, redirect to gui, gui tile, object page, navigation, cross-app navigation, intent, launchpad, s/4hana cloud, public cloud, purchase requisition, purchase order, gui fallback , KBA , MM-FIO-PUR-PO-2CL , Fiori UI for Purchase Orders (Public Cloud) , Problem
SAP Knowledge Base Article - Public