My Oracle Support Banner

Approved Standard PO Unit Pirce Auto Reference Global Blanket Purchase Agreement (GBPA) When Update Standard PO Need-by Date Even Global Blanket Purchase Agreement (GBPA) is Created After Standard Purchase Order (Doc ID 2561261.1)

Last updated on AUGUST 06, 2020

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Purchase Order

ACTUAL BEHAVIOR
---------------
Update need-by date of Standard Purchase Order and find its unit price is auto sourced from Global Blanket Purchase Agreement (GPBA), even Standard Purchase Order is created before Global Blanket Purchase Agreement.

EXPECTED BEHAVIOR
-----------------------
Update need-by date of Standard Purchase Order, after approved its unit price should NOT be updated with linked Global Blanket Purchase Agreement (GPBA),  if Standard Purchase Order is first created, then create Global Blanket Purchase Agreement (GPBA).

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. create standard PO-X for item-A and approve it (when create SPO and approved, it didn't refer to any global agreement as there is none)
2. create Global blanket agreement for item-A (*after SPO above in #1 is created and approved)
3. when update PO line's need-by date in PO-X (created in #1) , system auto reference to Global BPA created in #2, and auto update the unit price per the global GBPA.
4. when update PO line's promise date in PO-X (created in #1),  system doesn't search for the global BPA and doesn't populate it to PO.



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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.