This content has been marked as final. Show 5 replies
As per Oracle documentation - +"When creating sourcing rules in the Sourcing Rule window, you must define allocation percentages. Master Scheduling/MRP uses these allocation percentages when creating planned orders, which Purchasing imports as requisitions through Requisition Import. In a group of requisitions imported from Master Scheduling/MRP, the requisitions show the percentage allocation you define. In other words, at the end of a planning period, a group of orders to those suppliers approximately equals the percentage split you defined. However, when you create an individual requisition in Purchasing, Purchasing sources to the supplier with the highest allocated percentage. The Approved Supplier List (ASL) entry for that supplier is then referenced in order to pick up source document information (from a purchase agreement or quotation), if source documents exist. If a percentage allocation is the same for some suppliers, and you have ranked the suppliers in the Sourcing Rule window, Purchasing sources to the one with the highest rank."+
In your case, as I understand - you are trying to create requisition from Purchasing, not from MRP. Hence, percentage allocations might not help much.
G V Ranjith
Thanks Ranjith. I could gather the same from Oracle documentation as well which says purchasing uses limited functionality of ASL. But my requirement is to handle ASL with different Suppliers with varying allocation percentages (All the Suppliers have BPA for same item). The create release program should fire releases against Suppliers BPAs as per their allocation percentage.
Under standard feture, it seems non-achievable. Seeking help for any clue/guidance, how to handle the requirement...
You might need to customize the application.
Following is the documentation explaining the functionality (Answers your question, very straightforward)
<Admin edit - deleted MOS Doc>
From note : FAQ - SOURCING/ASL (Doc ID 1264801.1)
Paarthy, I am aware of what all you shared me from metalink - anywayz thanks for that. Basically, I was looking for guideline over the kind of cutomization to meet my requirement (which is not a standard functionality).