My Oracle Support Banner

EAR 9.2: Sum of Monetary Amounts on Secondary Translation Ledgers Is not Balanced for Foreign Currency Items Processed in Maintenance Worksheets or External Item Groups (Doc ID 2705822.1)

Last updated on AUGUST 30, 2020

Applies to:

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

Symptoms


After implementing the solution from <Bug 29917396> (AR: AR_UPDATE GO TO NO SUCCESS DUE TO UNIQUE CONSTRAINT WHEN USING MULTI-BOOK ACCOUNTING ENTRIES), inconsistencies have been detected on the Sum of Monetary Amounts with the generated Accounting Entries from External Item Groups coming from Foreign Currency Billing Invoices, well as Maintenance Groups spawning from such Items. These inconsistencies focus of the Monetary Amounts of the Accounting Entries (Record Field PS_ITEM_DST.MONETARY_AMOUNT) from Secondary Translation Ledgers on Base Currency, where the Item transaction Foreign Currency is different.

This was working fine before the mentioned fix was implemented, (As an individual extracted fix, or via applying FSCM 9.2 Image #33), and it seems that for Translation Ledgers, the PS_ITEM_DST rows created have an incorrect Field RATE_DIV value, storing the initial exchange rate from the Primary Ledger, when in fact, should contain the value of 1. This incorrectly defaulted Exchange Rate is what generates the incorrect calculation on Monetary Amounts.

REPLICATION STEPS:

  1.- Define a Ledger Group with multiple Secondary Translation Ledgers with different Currency Codes
  2.- Define this Ledger Group into the Ledgers For A Unit definition on the GL Business Unit to be used for testing
  3.- Create in Billing module a new foreign currency Invoice under that Business Unit
  4.- Set the new Invoice in Ready status, and save the changes
  5.- Launch the Single Action Invoice PSJob (BIJOB03) for the transaction created
  6.- Confirm that the External Item Group has been interfaced into the Accounts Receivable module, and set it into Post Action of Batch Standard
  7.- Launch AR Update to post this new Item into the Customer's Account
  8.- Check Record PS_ITEM_DST, and confirm that for the Secondary Translation Ledgers, the MONETARY_AMOUNT and RATE_DIV Fields are incorrect

The Monetary Amounts on Accounting Entries coming from Translation Secondary Ledgers are incorrect, which then gets filtered into the General Ledger module via interfaced Journal Entries, and such transactions fail validations from Journal Edit due to unbalanced line amounts. These Journals cannot be posted into the Ledger while being out of balance.This delays the month end tasks.

The Secondary Translation Ledgers already get their PS_ITEM_DST Fields of FOREIGN_CURRENCY and FOREIGN_AMOUNT as the reporting Currency, so their RATE_DIV should be 1, and the MONETARY_AMOUNT would need to equal that of FOREIGN_AMOUNT.

Changes

 

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
Changes
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.