PRC:PO: Purchase Order Price Is Not Updated After A Change Order Created From Initiate Retroactive Price Update Process Is approved
(Doc ID 2886417.1)
Last updated on JANUARY 26, 2024
Applies to:
Oracle Fusion Purchasing Cloud Service - Version 11.13.22.04.0 and laterOracle Fusion Purchasing - Version 11.13.21.10.0 and later
Information in this document applies to any platform.
Symptoms
Purchase Agreements
ACTUAL BEHAVIOR
---------------
Purchase Order/Change Order
Purchase Order Price is not updated after a change order created from Initiate Retroactive Price Update Process is approved. Change Order is being automatically cancelled after the Approval.
EXPECTED BEHAVIOR
-----------------------
Price to be updated after a change order created from Initiate Retroactive Price Update Process is approved.
Buyer / Approver to be notified that the Change Order was cancelled after the approval.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Blanket Purchase Agreement (BPA), for an item and make sure that the Retroactive price options are enabled:
Reprice Open Orders only
Communicate price updates
2. Create 2 Requisitions from this agreement, approve the requisitions
3. Go to Process Requisitions and create a Purchase Order, add these 2 requisition lines to the purchase order
4. Approve the Purchase Order
5. Change Blanket Purchase Agreement (BPA) line price, approve the change
8. Run Initiate Retroactive Price Update Process for the Blanket Purchase Agreement (BPA)
9. Review Purchase Order. Change Order is created by Initiate Retroactive Price Update Process and submitted for approval.
10. Change Order Approver approves the change
11. Buyer reviews the purchae order. Price is not changed.
12. Go to Document history
Document History shows that after the document was approved, the change was automatically cancelled by the application
Cancel Change Order Application The change order <number> has 1 or more validation errors. (PO-2055683)
Problem 2: You have to go to Document History to see that there was a problem to the change order.
Problem 3: Document History error message is not detailed
Problem 4: Change order approver was not notified of this potential problem during the approval.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |