Price Request API List Price And Selling Price UOM Different
(Doc ID 2373013.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Advanced Pricing - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Pricing Engine
Price Request API List price and selling price UOM different
The price request API is returning the Unit List and Unit selling price is different UOMs.
We have an item having primary UOM = MTH (Month)
Pricelist for this item is setup with primary UOM as YR (Year)
While calling Price Request API, We are passing MTH as the order UOM.
API output is coming with unit List Price in UOM MTH, but the unit selling price UOM is being used as YR.
As per link https://docs.oracle.com/cd/E18727_01/doc.121/e13428/T327893T327913.htm :
The List price (undiscounted base price) is returned in unit_price and the discounted price (after applying all the discounts/surcharges) is in adjusted_unit_price. Remember that these are per unit price expressed in unit of measure pricing_uom_code. Pricing_uom_code could be different from the line_uom_code (Ordered UOM). Therefore, if the price list is set in a unit of measure EACH and has been marked as primary, and if the order is in Dozen and there is no price list line for Dozen, then the pricing engine would return the price in EACH.
Sales Order is showing prices/UOM correctly.
But API is not mirroring the Sales Order form.
Prices returned by API is CORRECT. But there is inconsistency as far as UOM considered for List and Selling price is concerned.
Expecting both Unit List and Selling prices to be in same UOM, YR in this case, as pricelist is with primary UOM as YR, and no price in UOM MTH exists.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document