Requisition Import Does Not Take Into Account A BPA Has Reached Its Agreed Amount

(Doc ID 2390365.1)

Last updated on APRIL 24, 2018

Applies to:

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

Symptoms

Using Purchasing, Version 12.
Requisition Import does not take into account a BPA has reached its Agreed Amount when creating requisition causing Create Releases not to generate a new Blanket Release.
- There arehave three approved BPA in place; one has expired, one has reached its agreed amount and one is new.
- A card is scanned and places a record in the requisition interface table.
- When Requisition Import is run, a requisition is created but has Source PO Num of BPA that has reached its agreed amount.
- Create Releases fails to generate a new Blanket Release due to Agreed Amount being reached.
Expected Behavior:
We expect the Requisition Import program to progress through the ASL sequence to determine if BPA is open, has expired or reached its agreed amount and select the next available BPA as the Source PO Num.

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