My Oracle Support Banner

R12 Non ADB Ledger Shows Incorrect Effective Date on Recurring Journal - Period is Correct but Effective Date does not Change (Doc ID 2902954.1)

Last updated on AUGUST 11, 2023

Applies to:

Oracle General Ledger - Version 12.2.10 to 12.2.10 [Release 12.2]
Information in this document applies to any platform.


The Ledger setup does not use Average Daily Balances (ADB) .

Schedule the Recurring journal Program GLPRJE: Recurring Journal Entry to run on the first of every month with
"increment date parameters ' for each run".

The program completes without any errors and creates the Recurring Journal batch based

on the scheduling parameters with the correct period name, example AUG-2022.

However, the effective date does not change and remains the same for each
recurring journal even though respective period changes to the correct period name as  AUG-2022.

Example Journal shows AUG-22 period but has 01-FEB-1951 as Effective Date.

Steps to reproduce the issue :

Navigate Journals > Schedule > Recurring
a Query up the recurring journal and pick the period
b Click on Schedule when the Submit Request window shows up
c Click on Run the job Periodically
d Select to run the job every month
e Check the checkbox: increment date parameters


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

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