Std Price Picked from PURCH_ITEM_ATTR Instead of PURCH_ITEM_BU (Doc ID 1451295.1)

Last updated on JULY 11, 2016

Applies to:

PeopleSoft Enterprise SCM eProcurement - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
***Checked for relevance on 03-MAR-2014***

Symptoms

An item updated is used in a requisition is not applying pricing as expected. The standard price is taken from PURCH_ITEM_ATTR instead of PURCH_ITEM_BU.  It is expected that the Item Std Price be used from BU Attributes in preference over the Purchasing Attributes.

Steps to recreate the issue:

  1. Do the Item Set up for BU Price and Purchasing Price. Make sure Price is different to identify the Price default.
  2. Ensure you have multiple UOM's . Vendor UOM is not Std UOM.
  3. Purchasing Item Attributes--Define the Price
  4. Purchasing Controls--BU Attributes--Define the Price
  5. Item-Vendor---Item-Vendor UOM--Make sure its not the Std UOM
  6. Verity is Enabled
  7. ePro-Business Unit Options-Allow Business Item Attributes is checked
  8. Create a Requisition-Go to ePro-Create Requisition
  9. Enter the ITEM---ITEMPRICE2 in Item ID field and click on Search
  10. Click on Add
  11. You will get a Warning Message-Click OK
  12. Review and Submit

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