My Oracle Support Banner

RMS Using Operational Exchange Rate Type on Second Leg When Applying Triangulation (Doc ID 2797823.1)

Last updated on AUGUST 10, 2021

Applies to:

Oracle Retail Merchandising System - Version 16.0.2 and later
Information in this document applies to any platform.

Symptoms

When a Purchase Order is created for a location that doesn't match the system currency the triangulation will occur:
 - First converts Supplier Currency into System Currency
 - Second converts from System Currency into Location Currency that will insert into TRAND_DATA when PO is received.
Additionally, this issue happens when a PO is placed in USD for instance and the location is in Dubai (AED) and the system has been configured to be in KWDs.

If we have Exchange Rate type 'P' available in the system the PO is using that to convert from Supplier Currency into System Currency, but when inserting the transaction in TRAN_DATA it's using always the Operational Exchange Rate to calculate PO Cost.

Steps to reproduce the issue:


1. Define an Expense Profile to a certain Supplier that will be used to create a PO.
2. Define Currency Rates for all currencies that will be used when creating the PO in the next step (Operational and Purchase Order type).
3. Create a PO for a Supplier / Location that both have a different currency from System Currency.
4. Define consolidation_ind = 'Y'.
5. Receive Purchase Order.
6. Validate Purchase Order Cost on TRAN_DATA for the Purchase Order received.
7. The first conversion from Supplier Currency into System currency will use the 'P' type.
8. The second conversion from System Currency into Location currency will use 'O' type.

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.