Reversal Period Is Not Populated On Journal Entry Automatically Generated In Secondary Ledger

(Doc ID 2328597.1)

Last updated on NOVEMBER 15, 2017

Applies to:

Oracle Fusion General Ledger Cloud Service - Version 11.12.1.0.0 and later
Oracle Fusion General Ledger - Version 11.1.10.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.12.1.0.0 version, Post Journal Entries

A journal is created in the primary ledger with reversal period information. When the journal is posted it is replicated to the secondary ledger but
in the resulting journal the reversal period is not populated.
The expectation is that the reversal period gets populated with the information from the journal in the primary ledger.

STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Define a Reversal Criteria Set and assign it to the primary ledger.
2. Create a journal in the primary ledger with the appropriate category and see it gets the reversal period populated.
3. Post the journal in the primary ledger.
4. See that the resulting journal in the secondary ledger does not bring over the reversal period information.

Changes

 

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