Document 1463861 Back Date - Maintain Sourcing Rules Using The Automated Generate Sourcing Rules Concurrent Request

8/27/2019 Document 1463861.
1
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.
How To Back Date - Maintain Sourcing Rules Using The Automated Generate Sourcing Rules
Concurrent Request? Demo (Doc ID 1463861.1)
In this Document
Goal
Solution
References
APPLIES TO:
Oracle Purchasing - Version 12.1.3 to 12.1.3 [Release 12.1]

Information in this document applies to any platform.
GOAL
How can the sourcing rules be maintained within the Oracle Purchasing Product?
SOLUTION
The following is a business scenario example of one approach that might be used for maintaining the Sourcing Rules from
within the Oracle Purchasing module.
The testcase below is conducted on release 12.1.3 with the following patches in place:
Patch 14007360
Patch 12591815
Patch 10192008
Patch 25549595 - introduces profile - PO: Run POASLGEN for ALL Lines - which should be set to Yes.
With these patches, the ability to back date sourcing rules was introduced for release 12.1.3.
_______________________________________________________________________
Overview of the Sourcing Logic when creating the purchasing documents:
When a user is entering a Purchase Requisition - or - Requisition Import is being run - the following takes place:
1. The profile - MRP: Default Sourcing Assignment set is located - and the Assignment Set is fetched
2. Next, the assignment set is checked for the Item - Item/Inventory Organization combination
3. If the item - item/inventory organization - combination is located in the assignment set - the sourcing rule is then fetched
4. The sourcing rule will then be used to either source from a supplier - or - an internal inventory organization
- If the source is a supplier - supplier/site - then this information will be used on the requisition
5. At this point, the profile PO: Automatic Document Sourcing is fetched
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=152suwpqci_249&id=1463861.1 1/20
8/27/2019 Document 1463861.1
- If the Value is No - then the system will look to the Approved Supplier List entry form - using the item/supplier/site
combination to locate a source document
- If the value is Yes - then the system will search and fetch the most recent Approved Blanket (Local/Global) and/or
Quotation to use as a document reference
Below is an example of how to utilize the automatic generation and updating of sourcing rules.
1. Item is created.
2. Assignment Set is created and assigned to the MRP: Default Sourcing Assignment Set Profile
8/27/2019 Document 1463861.1
8/27/2019 Document 1463861.1
3.Confirm these profiles are set to allow the sourcing rules to be automatically created
PO: Allow Auto-generate Sourcing Rules - set to Create and Update

PO: Set New BPA as Rank 1 - Yes
PO: Run POASLGEN for ALL Lines - Yes for this example - This profile ensures all lines on the Blanket Agreement are
considered, whether updated or not.
- More Details in the following Note 2252486.1 - Generate Sourcing Rules And ASLs (POASLGEN) From Blanket Agreements
Is Not Generating ASL as Expected
4. Local Blanket Agreement is created with the Supplier 'Allied Manufacturing' - LOS ANGELES.
- Business is going to be conducted with the Supplier
- Note that terms effective and start dates must be entered
8/27/2019 Document 1463861.1
8/27/2019 Document 1463861.1
Submit the Blanket Agreement for Approval - requesting that the sourcing rules be created.
5. Submit the request for the Workflow Background Process
8/27/2019 Document 1463861.1
This is now mandatory - as the workflow background process will complete the Approval workflow and submit the request -
Generate Sourcing Rules and ASLs from Blanket Agreements
This change in functionality was made for performance purposes.
6. Query back the Assignment Set and confirm that the sourcing rule was created.
8/27/2019 Document 1463861.1
Also confirm that the Approved Supplier List entry is present.
8/27/2019 Document 1463861.1
Note: A sourcing rule is created for each item - and then assigned.
7. Next, these are the proper actions to take for updating a sourcing rule so that a new supplier can be utilized.
The Blanket Agreement for the current supplier should be updated to reflect the final day which Business will be conducted
with the supplier.
Set the Effective To date as one day prior to the start date expected for Business with the new Supplier
8/27/2019 Document 1463861.1
8/27/2019 Document 1463861.1
Submit this for Approval, this time - requesting to update the Sourcing Rules checkbox - as seen above.
8. Engage the Workflow Background Process (this should be done after each approval submission that is having the Sourcing
Rule options selected).
8/27/2019 Document 1463861.1
8/27/2019 Document 1463861.1
9. Review the Sourcing Rule and ensure that it was also updated and properly back dated.
8/27/2019 Document 1463861.1
10. Create and Submit the New Blanket Agreement for Approval and Sourcing Rules Generation.
Notice the terms dates are not overlapping the previous blankets dates.
8/27/2019 Document 1463861.1
8/27/2019 Document 1463861.1
Execute the Workflow Background Process.
8/27/2019 Document 1463861.1
11. Confirm the Sourcing Rule is updated to reflect the new date period - with the new Supplier as Rank 1.
8/27/2019 Document 1463861.1
Notice that the new date range is added and the supplier is rank 1.
Here is the outcome if a new Agreement was created - with a different supplier - having terms start and end date that match
date range that is on the original agreement - sourcing rule.
8/27/2019 Document 1463861.1
Note, it does add the new supplier - and because - PO: Set New BPA as Rank 1 is set to Yes - it sets the Rank to 1.
Something to consider - the new supplier is going to be used immediately in this scenario.
This explains the primary functions of the concurrent request - Generate Sourcing Rules and ASLs from Blanket Agreements
8/27/2019 Document 1463861.1
The process to update and Generate Sourcing Rule will update existing Sourcing rules only if all of the following are true:
1. The sourcing rule is not assigned to any other item.

2. The Blanket purchase order Start and End Dates are not null.
3. If the update requires extension of any existing effective period in the Sourcing Rule, there can be only one Supplier/Site for
that effective period and must match the supplier/site on the blanket purchase order.
4. The blanket effective period do not overlap multiple effective periods in the Sourcing Rule.
5. The Sourcing Rule is not assigned multiple times to multiple items
Didn't find what you are looking for?

Document 1463861 Back Date - Maintain Sourcing Rules Using The Automated Generate Sourcing Rules Concurrent Request

Uploaded by

Copyright:

Available Formats

You might also like

Document 1463861 Back Date - Maintain Sourcing Rules Using The Automated Generate Sourcing Rules Concurrent Request

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Document 1463861 Back Date - Maintain Sourcing Rules Using The Automated Generate Sourcing Rules Concurrent Request

Uploaded by

Copyright:

Available Formats

8/27/2019 Document 1463861.

Oracle Purchasing - Version 12.1.3 to 12.1.3 [Release 12.1]

Overview of the Sourcing Logic when creating the purchasing documents:

5. At this point, the profile PO: Automatic Document Sourcing is fetched

PO: Allow Auto-generate Sourcing Rules - set to Create and Update

- Business is going to be conducted with the Supplier

- Note that terms effective and start dates must be entered

5. Submit the request for the Workflow Background Process

This change in functionality was made for performance purposes.

Also confirm that the Approved Supplier List entry is present.

Execute the Workflow Background Process.

1. The sourcing rule is not assigned to any other item.

Didn't find what you are looking for?

You might also like