What Is The Defaulting Rule For Requisition/Release Referencing BPA With Multiple Overlapping Price Breaks ?

Metalink Note id: 796606.1

Goal

What is the defaulting rule for Requisition or Release referencing BPA with multiple overlapping price breaks ?

For example:
1. Create a global agreement GBPA
2. Add a description_based item
3. Add price break line for quantity 4, for example 10
4. Submit and approve agreement.
5. Add a new price break line for the same quantity 4 at a lower price 9
6. Submit and approve agreement.
7. Add another price break line for the same quantity 4 at a higher price 12
8. Submit and approve agreement.
9. Use the GBPA to source into requisition.

In this example, there are overlapping price breaks for the same quantity 4.

Solution

By design, when there are multiple overlapping price breaks, the system compares price breaks by creation dates, then by prices, following this defaulting rule:

· Use price from the most recently created price break record.
· Use lowest price from amongst the matching price break records.

For price break records created in the same days, they will all be used to determine the lowest price.

If there is a business need outside of the above defaulting rules, customizing pricing logic using custom hooks can be used.

Reference notes for Custom Hooks:

Note 360121.1 Custom Hooks in Oracle Purchasing
Note 360122.1 How To Create Custom Pricing Hook in 11.5.9 and onwards

References

BUG:5176035 - REQS DO NOT DERIVE CORRECT ITEM PRICING FROM PRICE BREAK WITH EFF. DATES ON BPA
BUG:8363413 - REQUISITION NOT TAKING LATEST PRICE BREAK ENTERED ON THE SAME DAY
NOTE:360121.1 - Custom Pricing Hooks in Oracle Purchasing
NOTE:360122.1 - How To Create Custom Pricing Hook in 11.5.9 and Onwards