My Oracle Support Banner

EGL: After Extending the Period End Cutoff Date, Running 'Edit Journal' With the Date in the Extended Open Period Returns a 'Journal Date yyyy-mm-dd is not within the open period:... (5010,2)' Error/Warning (Doc ID 3002031.1)

Last updated on MARCH 21, 2024

Applies to:

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

Symptoms

Journal Source Security is enabled and used with Period End Cutoff Date schedule to extend period end for specific Journal Sources.  When journal is created with date within the extended date range defined on the Period End Cutoff Date range, edit of which
results to error below:

Error/s:

'Journal Date yyyy-mm-dd is not within the open period: Fiscal year yyyn period x to fiscal year yyyn period y. (5010,2)'


Steps to replicate:

1.  Set up Journal Source Security By Role. (Set Up Financials/Supply Chain > Security > Journal Source Security by Role)

2.  Set up Period End Cut Off. (Set Up Financials/Supply Chain > Common Definitions > Journals > Journal Source Security > Period-End Cutoff Schedule)
      - In Open Period Display, you have periods open for Period 5 FY 2023 (i.e. May 1-31, 2023)
      - Period End Cut Off for Source XXX Period for Period 4 = 05/25/2023

3.  Create journal for the source. (General Ledger > Journals > Journal Entry > Create/Update Journal Entries)
     Example:  Journal is created for Source xxx with Journal Date = 04/01/2023. At save, warning message will be received indicating period being closed.

4.  Run Edit Journal. (General Ledger > Journals > Process Journals > Edit Journal Request)

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.