Generate Sourcing Rules and ASLs from Blanket Agreements is Not Properly Updating Sourcing Rule (Doc ID 1455712.1)

Last updated on AUGUST 21, 2016

Applies to:

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

Symptoms

Oracle Applications 12.1

After modifying the Site value on a Blanket Purchase Agreement (BPA), re-approving the BPA, and running 'Generate Sourcing Rules and ASLs from Blanket Agreements', the Approved Supplier List (ASL) and the Sourcing Rule are updated with an additional record displaying the new Supplier/Site combination. However, the Sourcing Rule shows the old Site with Allocation % = 100 and Rank = 1. The new Site shows Rank = 2. When creating a Requisition for the item of interest, the old Supplier/Site combination defaults, but no sourcing document information defaults onto the Source Details tab.

The expectation is that the new sourcing information (Supplier/Site/Sourcing Document) should populate in the Requisition form.


STEPS
-------------------
1.  From the responsibility Purchasing

2. Create and approve Blanket Purchase Agreement (BPA)
Supplier = A1
Site = S1
Effective Dates = 1-JAN-2012 - 31-DEC-2012
Item = ItemX

3. Run Generate Sourcing Rules and ASLs from Blanket Agreements
Sourcing Rule PURCH_xxxx is created

4. Create Requisition for ItemX
All the Sourcing information correctly defaults onto the Requisition (Supplier, Site, Source Doc).

5. Modify the BPA by changing the Site = S2
Save and approve the BPA

6. Run Generate Sourcing Rules and ASLs from Blanket Agreements

7. Query the ASL for ItemX
Both Supplier/Site combination display

8. Query Sourcing Rule PURCH_xxxx
It displays both Supplier/Site combination:

Supplier = A1
Site = S1
Allocation = 100%
Rank = 1

Supplier = A1
Site = S2
Allocation = 100%
Rank = 2

9. Create a new Requisition for ItemX
The Supplier and Site default to :
Supplier = A1
Site = S1
and nothing defaults onto the Source Details tab.


BUSINESS IMPACT
-----------------------
Due to this issue, sourcing rules are not being properly updated and Requisitions are not being properly sourced.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms