EEX9.1+: When User Copies an Expense Line for a Date Range Having Different Exchange Rates, Monetary Amount and Exchange Rate Calculated Incorrectly at Distribution Level. (Doc ID 1932155.1)

Last updated on SEPTEMBER 13, 2016

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

When user copies an Expense Line with different date range on an Expense Report and each date has different exchange rate, after saving the Expense Report monetary amounts in record EX_SHEET_DIST differs from those present at EX_SHEET_LINE record.

Setup:
--------
1-Make sure to have different exchange rates in each day in Market table setup page.
   Navigation :Setup Supply chain > Common Definition > market Rates > market Rates.
 
     e.g: Do inquire for the :  - Index : Model,  currency From To is: USD and INR, Rate Type : CRRNT.
     Set the the following rates as an example for issue replication:
      03/08/2014 65.00000000
      03/07/2014 61.11000000
      03/06/2014 61.75000000
      03/05/2014 70.00000000

Steps :
--------
1. Creates an Expense Report, Which contains same business unit as defined at user profile, change the business unit on the Accounting Detail page.
      The first Expense Line is reflecting current date e.g 5th of August 2014, amount 2500 INR and currency as e.g: INR, exchange rate retrieved as 65.00000000.
         e.g : User VP1 with Employee ID KU0042 with default business unit US001, change the distribution BU to be IND01.

2. Copy the Expense Line created to a range of dates.
         e.g :from 5th of March to 7th of March 2014. Then save the Expense report.

Actual Result:
----------------
Monetary amounts in EX_SHEET_DIST record differs from those present at EX_SHEET_LINE record. Subsequently generating wrong accounting entries.

Expected Result:
--------------------
The monetary amount should be similar in the two records : EX_SHEET_DIST and EX_SHEET_LINE


Please see the Replication Steps document for more details related to complete configuration and the replication steps necessary to reproduce the issue.

Cause

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