Last updated on MAY 03, 2017
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 and later
Information in this document applies to any platform.
There are a series of checks that take place in the CalculateLatestPrice function within PV_NEWSRCH_WRK.UNIT_OF_MEASURE.FieldFormula. I
in our testing, we used an item that two UOMs - EA as the item's standard UOM, and BX (with a conversion rate of 5 EA per BX).
Neither of these UOMs is tagged as the default req UOM.
The preferred/priority supplier location has a default UOM of BX and a price of 165.
When we search for this item in ePro, the results display the supplier's price of 165 but with the standard UOM of EA.
This mismatch is a bug and a very confusing one.
Given that neither of the item's UOMs are tagged as the default req UOM, I would think that the system would retrieve the preferred supplier's default UOM and associated price.
In our case, that would be 165 per BX. In looking at the code mentioned above (CalculateLatestPrice), it's hard to tell whether the developer's wanted to do this (i.e. display the preferred supplier's default UOM) or whether they wanted to convert that to the item's standard UOM. In the end, what is happening achieves neither and displays a confusing and inaccurate mismatch of price and UOM in the results.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms