ELA: Receiving “Period count for Calendar and Schedule do not match (18157,205)” Error and Duplicate Payment Schedule Entries Are Created After an Amendment for a No Proration Lease Is Created To Extend the Payment End Date
(Doc ID 3063330.1)
Last updated on DECEMBER 12, 2024
Applies to:
PeopleSoft Enterprise FIN Lease Administration - Version 9.2 to 9.2 [Release 9]PeopleSoft Enterprise FIN Asset Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Symptoms
Receiving “Period count for Calendar and Schedule do not match (18157,205)” Error and Duplicate Payment Schedule Entries Are Created After an Amendment for a No Proration Lease Is Created To Extend the Payment End Date
The issue can be reproduced at will with the following steps:
1. Create A New Operating Lease with Commencement Date = 01/01/2024 and Termination Date = 04/30/2024
Navigation: Lease Administration > Payables Leases > Create New Payables Lease
2. Select No Proration for the Proration Method
3. Add Advanced Base Rent for the entire period
4. Add Miscellaneous Rent from 01/01/2024 to 02/28/2024 (One day before the Period end Date)
5. Activate the Lease
6. Calculate the Depreciation, Create Accounting Entries, and Close the Depreciation from Period 1 to Period 4.
Navigation: Asset Management > Depreciation > Processing > Calculate Depreciation
Navigation: Asset Management > Accounting Entries > Create Accounting Entries
7. Create an Amendment and change the Miscellaneous Rent End Date to 02/29/2024
Navigation: Lease Administration > Payables Leases > Maintain Payables Lease
8. Click on the Preview Payment Schedule
9. Notice Error "Period count for Calendar and Schedule do not match (18157,205)" is displayed
10. Click OK, Save, and Activate the Amendment
11. Review the Payment Schedule of the Miscellaneous Rent after the Amendment is Activated.
12. Notice that the Last Payment Schedule is Doubled
Detailed DEMO Replication Steps Attached
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 |
Cause |
Solution |
References |