ORDUPD.PC Calculates Incorrect Unit Retail (unit_retail) on Open Purchase Orders
Last updated on JANUARY 03, 2018
Applies to:Oracle Retail Merchandising System - Version 14.1 and later
Information in this document applies to any platform.
ORDUPD.PC calculates wrong unit_retail because date condition is missing for price_hist. It considers all the previous price changes from price hist for associated items of order. It calculates the difference and sums it up.
As a result, unit_retail in ORDLOC is wrong. Sometimes it is a high negative value and sometimes it is high positive value which depends on existing data in price hist for associated items of the order.
Steps to Reproduce:
- Post and process a XTSF message in which requested item is not ranged to a ‘to location’ of transfer.
- Pick any open purchase order.
- Run ORDUPD base batch.
- Notice that the retail_value is incorrectly updated in the order.
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