Last updated on MAY 27, 2016
Applies to:PeopleSoft Enterprise FIN Asset Management - Version 9.2 and later
Information in this document applies to any platform.
The customer is trying to extend the final period in a 5-4-4 calendar to 5 weeks every 5 years. When they set the calendar up this way, they enter the depreciation tab as 5/53, 4/53, and so on. The software generates the calendar entries in the ps_cal_detp_tbl with the pd_alloc_total of 52 for the extended year but enters the correct fraction in the pd_alloc field such that the depreciation is spread over 53 weeks instead of 52. The depreciation calculated for the assets is correct but the pd_alloc_total is 52 rather than 53 on the ps_cal_detp_tbl.
Also, the depreciation tab on the detail calendar is blank for the 53 week years whereas it is populated with the correct fractions when using 52 periods: 5/52, 4/52.
The expectation is that the pd_alloc_total for the extended fiscal year will be 53 on the ps_cal_detp_tbl table for all periods. It is also expected that the pd_alloc and pd_alloc_total fields on the Depreciation tab of the Detail Calendar will be displayed as defined.
This issue can be replicate by performing the following steps:
1) Create a 5-4-4 calendar via Calendar Builder.
2) Extend the end date of period 12 of the affected fiscal year (i.e. 2016) by a week.
3) Tab to Depreciation and change the pd_alloc_total fields for all periods to 53.
4) Change the pd_alloc to 5 for the extra week. Save.
5) Review the calendar entries in the ps_cal_detp_tbl table for the affected fiscal year. Note that the pd_alloc_total for all periods is 52 rather than 53. Also note that the pd_alloc values are fractions that accommodate the extra week that was added to the fiscal year.
6) Define the calendar to a business unit and generate an asset. Navigate to the Review Depreciation Info page to validate that the depreciation for the extended year was generated correctly.
7) Navigate back to the Depreciation tab of the Detail Calendar to see that the pd_alloc and pd_alloc_total fields for the fiscal year have been spaced out.
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