BPA Pricing is defaulting to Reqs/POs when no BPA is referenced in FBDI Upload of purchasing data
Summary
BPA Pricing is defaulting to Reqs/POs when no BPA is referenced in FBDI Upload of purchasing data, this is causing the wrong pricing to appear on Reqs and OrdersContent
We use BPAs to manage pricing by project and dates and reference those BPAs in our FBDI uploads. If there is no BPA referenced in the BPA field, but a valid BPA exists for the item/supplier combination, Oracle is by default pulling that pricing into our Reqs and POs. This is not desired, we are expecting the system default list pricing to populate. We need the option to leave the BPA field blank and pull in the default pricing.
3