Last updated on MAY 31, 2016
Applies to:JD Edwards EnterpriseOne General Ledger - Version 9.1 and later
Information in this document applies to any platform.
Providing a Leap Date for February is often overlooked by customers. As a consequence, this causes table data integrity issues that must be corrected in order to report February Financial End results. This takes a tremendous
amount of time and effort both by the customer and the support engineer to re-align the data to correctly reflect the correct period assigned to the transaction.
What is need is an informational message is displayed when a user is entering a February date in a respective date pattern reminding the user that the operating year entered is a Leap Year.
Leap Year is determined by:
To determine whether a year is a leap year, follow these steps:
1. If the year is evenly divisible by 4, go to step 2. ...
2. If the year is evenly divisible by 100, go to step 3. ...
3. If the year is evenly divisible by 400, go to step 4. ...
4. The year is a leap year (it has 366 days).
5. The year is not a leap year (it has 365 days).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms