3733443 - PO Price does not match awarded Supplier Quotation price from Ariba

• A Purchase Requisition (PR) is created with a specific net value.

• An RFQ is generated from the PR and sent to SAP Ariba Sourcing.

• The bidding process is completed, and the quotation is awarded to a supplier for a lower or different amount than the original PR.

• The awarded supplier quotation is successfully transferred back to SAP S/4HANA.

• However, when the follow-on Purchase Order (PO) is created, it retains the original net price from the Purchase Requisition instead of adopting the awarded quotation price.

SAP S/4HANA Cloud Public Edition

1. Create a Purchase Requisition (e.g., for 100 EUR). Ensure the PO Price field in the PR is maintained as Net Price (Order price adoption indicator).

2. Create an RFQ referencing the PR and publish it to Ariba Sourcing.

3. Award a supplier quotation in Ariba for a different amount (e.g., 90 EUR) and transfer it to S/4HANA.

4. Create the follow-on Purchase Order.

5. Observe that the PO price is 100 EUR (from the PR) instead of the 90 EUR awarded in the quotation.

In the Purchase Requisition, the PO Price field is maintained as Net Price (or the 'Order price adoption' indicator is set). Due to system hierarchy and design, this setting forces the system to prioritize the PR price. Whenever a PO is created from this PR, the system ensures that the PO net price remains identical to the PR price, overriding the price provided in the linked quotation.

To ensure the Purchase Order adopts the correct quotation price, the "PO Price -> Net Price" setting must not be applied to PRs undergoing the RFQ/Ariba process.

Option 1: Process Adjustment (Manual) Ensure users do not maintain the PO Price (Net Price) in the default values for PRs that will go through the RFQ -> Quotation process.

Option 2: Custom Logic via BAdI (Automated Workaround) If your business process requires both direct PR-to-PO conversions (where PR price should be kept) and PR-to-RFQ processes, you can automate this distinction using extensibility.

1. Implement the BAdI MM_PUR_S4_PR_MODIFY_ITEM.

2. Build custom logic to evaluate the routing of the PR based on specific identifying fields (e.g., Purchasing Group, Material Group, or custom fields).

3. Condition A: If the logic determines the PR is intended for direct PO conversion, the BAdI can maintain the PO Price field as Net Price.

4. Condition B: If the logic determines the PR will follow the RFQ -> Ariba -> Quotation process, the BAdI should ensure the PO Price field remains empty. This avoids the pricing conflict and allows the PO to successfully adopt the quotation price.

Note: For Option 2 to function reliably, the system must have clear, consistent parameters to differentiate between the two procurement routes at the time of PR creation.

purchase requisition price, po price not updated, quotation price not adopted, rfq ariba integration, po uses pr net price, s/4hana cloud public edition, mm_pur_s4_pr_modify_item, rfq to po, supplier quotation transfer, manage purchase order app, operational procurement, net price override, pricing conflict pr vs quotation, purchase order pricing, ariba sourcing quotation , KBA , MM-PUR-RFQ-2CL , RFQ/Quotation (Public Cloud) , Problem