My Oracle Support Banner

Wrong Price Is Sent To Store And Other Downstream Systems (Doc ID 2791082.1)

Last updated on JULY 13, 2021

Applies to:

Oracle Retail Pricing Cloud Service - Version 19.1 and later
Information in this document applies to any platform.

Symptoms

In RPCS (or RMFCS), when a price is set with more than 2 decimal places - i.e. 14.0155 - the UI will round it to the respective currency defined in the system (in this case 2 decimal places - 14.02). However, the system will save the price in the back end as 14.0155 and will send that price down to other systems through integration, like a POS system.
This may have a high impact on a retailer.

EXPECTED BEHAVIOR
-----------------------
Price committed on database must have same value as UI.

 

Steps to replicate:

1. Create an emergency same day Price Change as Fixed Price
2. Define a new retail price with 4 decimal places and notice that UI will round it to 2 decimal places
  Edit Price for Price Change before approval
3. Approve Price Change so it becomes executed
4. Verify the selling retail price in Price Inquiry -> 2 decimal places
5. Verify the selling retail price in RPM_FUTURE_RETAIL -> 4 decimal places
6. Verify the selling retail price in RPM_PRICE_CHG_PAYLOAD -> 4 decimal


Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.