Symptom
In the Process Purchase Requisitions v2 app, when creating purchase orders from purchase requisitions, some purchase orders are automatically created in the background. These purchase orders will open in the Display Purchase Order – Advanced app only. Other purchase orders will open in the Manage Purchase Orders app.
This KBA explains the reasons for both scenarios.
Environment
-
SAP Fiori
-
SAP S/4HANA Cloud Public Edition all versions
Reproducing the Issue
-
Open the Process Purchase Requisitions V2 app.
-
Select a purchase requisition.
-
Choose “Create Purchase Order”.
-
The purchase order opens in the “Display Purchase Order – Advanced” app.
Cause
When a purchase order is created from a purchase requisition in the Process Purchase Requisitions V2 app, the system performs a simulation and executes a feature check on all the fields. The customer can see the following pop-up on the screen while a simulation is being performed:
- If the feature check finds only features that are supported in the Manage Purchase Orders app, the system navigates to the Manage Purchase Orders app, where you can enhance the Purchase Order if required.
- If the feature check finds features that are not supported in the Manage Purchase Orders app, then the purchase order will be created in the background, and the system navigates to the Display Purchase Orders - Advanced (WEBGUI) application.
These feature check ensure whether the document can be displayed/changed in the Manage Purchase Orders Fiori app. The Fiori app covers a set of standard features. The more complex feature set of the Display Purchase Orders – Advanced WEBGUI app is selectively accessed only when needed, reducing unnecessary complexity.
Example: Creating stock transport orders.
Stock transport orders are different from a standard purchase order and have additional fields, e.g. the “Supplying Plant” field. These fields are not a part of the standard functionality of the Manage Purchase Orders app. Hence, after choosing the “Create Purchase Order” button for a purchase requisition with a stock transport order, the corresponding stock transport order will be created in the background, and the system navigates you to the Display Purchase Orders – Advanced app, where it can be processed.
In general, if a field does not exist in the Manage Purchase Orders app, but it is filled in the purchase requisition, then the corresponding purchase order is accessed in the Display Purchase Orders – Advanced WEBGUI app.
Resolution
With the updated process flow in V2 app, there is no Edit screen before the Advanced Purchase Order creation. Meanwhile, if your process requires this functionality, you can continue using the Process Purchase Requisition app, which remains valid for the previous scope and process navigation flow.
We encourage you to adopt V2 for the latest improvements and process alignment.
The Output messages might be configured as "Schedule" option instead of "Immediate" in case any change is required before sending the Purchase Order to Supplier.
In parallel, the Create Purchase Order -Advanced app can be used to convert the Purchase Requisition to Purchase Orders as is shown in steps bellow:
Using the Create Purchase Order – Advanced app
1) Navigate to the Create Purchase Order – Advanced app.
2) Choose “Document Overview On”.
3) Choose the “Select Variant” option and choose “Purchase Requisitions”.
4) On the following screen, you can search and filter for specific purchase requisitions. Multiple selections are also possible.
5) After selecting the required purchase requisition, choose “Adopt”.
6) This will convert the selected purchase requisition into a purchase order.
Here, you can now edit any required data in the purchase order, add attachments, notes, etc.
Keywords
"process purchase requisition", "purchase requisition conversion", "Advanced Purchase order creation" , KBA , MM-PUR-REQ-SOC-2CL , Fiori UI for Sourcing Purchase Requisitions (Public Cloud) , MM-FIO-PUR-PO-2CL , Fiori UI for Purchase Orders (Public Cloud) , Problem
Product
Attachments
| Pasted image.png |
| Pasted image.png |
SAP Knowledge Base Article - Public