Ledger's Period Type Not Matching Calendar's Period Type, the Ledger Setup Cannot be Updated
(Doc ID 1522010.1)
Last updated on JANUARY 04, 2023
Applies to:
Oracle General Ledger - Version 12.0.0 and laterInformation in this document applies to any platform.
Symptoms
A new Calendar has been defined, using Period Type 'A' (example). A new Ledger has been defined using the newly set up Calendar.
Afterwards the users decided they need another Period Type for this Calendar and entered more periods in its setup using Period Type 'B'. As the Calendar can still be updated, the users deleted the periods using the incorrect Period Type 'A' .
Further they noticed the Ledger created as shown above is still pointing out to the Calendar using the incorrect Period Type 'A', which no longer exists in the Calendar's definition.
Attempting to adjust this setup at Ledger level is not possible, the fields are greyed out. Therefore, this Ledger cannot be used with the Calendar defined for it.
Changes
Setup 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 |