PURCHASE RELEASE DOES NOT VALIDATE BLANKET'S 'AMOUNT AGREED' LINE LIMIT

BUG:4439005 There is no validation in Line level amount agreed. Releases always take price from header level
not from line level.

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

Set the site profile Concurrent: TM Transport Type to QUEUE if using the RAC system

Receiving Transaction Manager Not Active - Unable To Perform Receipt [ID 1284918.1]

Applies to:

Oracle iProcurement - Version: 12.1.3 and later   [Release: 12.1 and later ]
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Desktop Rcv/Returns/Correction

Trying to submit receipts, corrections or returns from iProcurement but get the following error message:Receiving transaction manager not active

EXPECTED BEHAVIOR
---------------------------
Expect the Receipt to be completed and Receiving Transaction Processor has completed successfully

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In Iprocurement select requisition to receive
2. Enter required data and press submit
3. on screen receive Items: review and submit get foolowing error message
4. 'Receiving transaction manager for receipt, return and correct items are not active'

Cause

The issue appears to be caused by the Receiving Transaction Manger not operating correctly

Solution

To implement the solution, please execute the following steps:

  Execute the below steps

  1. Relink receiving executables.
      cd $PO_TOP/bin
      $ adrelink force=y ranlib=y "PO RCVOLTM"
      $ adrelink force=y ranlib=y "PO RVCTP"

2. Bounce the Receiving Transaction Manager.

3. Retest the issue.
If using a RAC system, set the site profile Concurrent: TM Transport Type to QUEUE, bounce the middle tier and then retest

Please review Note 458453.1
What is the Difference Between PIPE and QUEUE for Profile Concurrent:TM Transport Type ?
and
Note 823587.1
Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12
for more information on this profile

Price breaks effective dates

In Oracle Purchasing, on a blanket agreement , the price breaks effective dates are available only
if not using cumulative pricing. Logged Enhancement Request 3891628

Cumulative Pricing can not be used with global agreements.

Cumulative Pricing can not be used with global agreements.
Ref: P4-56 PO User Guide

Log File to appear in HTML format

Set Profile Option Viewer: Text = Browser

GBPA does not allow to enter OSP line type

You cannot enter an Ouside Processing Item in a Global Blanket Purchase Agreement regardless of the item's defining Organization.