Generate Sourcing Rules And ASLs From Blanket Agreements Ranking not Behaving As Expected
(Doc ID 1678447.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle Purchasing - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
The Sourcing rule being used, has effective dates from 01-APR to 31-MAR for 2013, 2014 and 2015. One BPA is defined for Supplier A, which was originally Rank 1 with 100% allocation.
A new BPA was created for same item, and with same effective dates as current BPA. The BPA is for a different Supplier.
When Generate Sourcing Rules is run, it adds the new BPA/Supplier to the Sourcing rule, but its added as Rank 1, with old rule changed to Rank 2.
<Bug 13961772> - POASLGEN IS NOT PROPERLY UPDATING SOURCING RULES changed the functionality. After this fix, the rank of the newly added bpa/supplier will have the rank 1
and the original supplier will be updated to Rank 2.
This change is not preferred by all customers, who were used to the old style.
STEPS
-------------------
1. Login to the E-Business Suite and choose the Purchasing Module.
2. Part number A1
Part Number B1
There are 2 GPA available for these 2 part number
GPA# 1, Effective Date: 01-Apr-2014 and End Date 31-Mar-2015
Supplier: Suplier 1
Supllier Site : Site 1
3. GPA# 279219, Effective Date: 01-Apr-2014 and End Date 31-Mar-2015
Supplier Name : Supplier 2
Supplier Site : Site 2
Run the Generate Sourcing Rule Program first for GPA# 1 and
Supplier: Suplier 1
Supllier Site : Site 1
4. Than run Sourcing Rule program for another GPA# 2 and
Supplier: Suplier 1
Supllier Site : Site 1
5. Expected Results:
Effective Date: 01-Apr-2014 and End Date 31-Mar-2015
Sourcing Rule should be created with Allocation 100% and Rank1 for GPA# 1 Supplier: Supplier 1 & Supplier Site : Site 1
and Allocation 100% and Rank2 for Supplier Name : Supplier 2, Supplier Site : Site 2
However this is just reversed, the most recent one become Rank1, this is not the intended functionality as described in <Note 1463861.1> and <Note 1455712.1>.
Inftc error occurred ...PO_PDOI_COLUMN_NOT_NULL
Sourcing Rules creation API returned failure
This error occurs if the start and end date on the blanket are null. Hence please be sure to confirm and specify the start and end dates on the blanket agreement and try the same again.
Sourcing rule effective dates will be decided based on the blanket's effective dates. Hence blanket effective dates are required.
Sourcing rule start date is validated to ensure that it is within the blanket effective dates.Hence please try the flow once with blankets effective dates.
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 |
| References |