GL Manual Journals Document Sequences Not Consistent With GL Dates
(Doc ID 2362247.1)
Last updated on FEBRUARY 16, 2018
Applies to:Oracle Fusion General Ledger Cloud Service - Version 22.214.171.124.0 and later
Oracle Fusion General Ledger - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
we created a manual GL journal entry with an Accounting date 1st of February, 2018; and the system assigned the document sequence number 20 to it.
Than, we created another manual GL journal entry with an Accounting date of the 30th of January, 2018 (so prior to the first one).
The system assigned the document sequence number 21 to it.
So, GL dates and document sequences are not consistent.
An Italian fiscal requirement is that if you use a specific GL date for a manual GL journal entry (and you assign a document sequence number to it), than you cannot assign the following document sequence number to a manual GL journal entry with a GL date that is prior to the last used.
The issue is because the system only assigns GL document sequences while posting manual GL journal entries, instead of assigning the document sequence number while creating the journal entry.
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