EGL9.2: Allocation (FS_ALLC) Process Calculates TimeSpan Incorrectly for a Leap Year and Daily Calendar.
(Doc ID 2704182.1)
Last updated on AUGUST 24, 2020
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Allocation (FS_ALLC) process calculates timespan incorrectly for a leap year and daily calendar.
Example: Daily calendar accounting entries added for June 30,2020 (aka Period 366 for FY 2020) are not being picked up by the Allocation processes
because the underlying delivered code is treating Period 366 F2020 as Period 1 FY 2021. So when it builds the SQL to search for transactions,
it is using Period 1 FY 2021 instead of Period 366 and FY 2020.
Steps to replicate:
Run Allocation (FS_ALLC) for Fiscal Year 2020 with timespan using Daily Calendar.
Note that Year 2020 being a leap year, February 2020 has 29 days.
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 |