ECA 9.2: The Billing Plan Schedule for a Recurring Yearly Contract Is Not Correct When Leap Years Are Involved
(Doc ID 2967253.1)
Last updated on AUGUST 17, 2023
Applies to:
PeopleSoft Enterprise FIN Contracts - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
The Billing Plan schedule for a recurring yearly contract is not correct when leap years are involved.
Replication Steps:
- Create a Schedule with Frequency as 'Annual', Month as '03-March', and Day of the Month as 1.
- Create a contract with a recurring contract line.
- Associate a recurring billing plan to the contract line (Navigation: Customer Contracts > Schedule and Process Billing > Define Billing Plan).
- Go to the Recurring Detail tab of the billing plan. Use the start date as 3/1/2023 and the end date as 2/28/2030. Use the schedule created in Step 1 and do a preview.
- Notice that period one has a start and end date of 3/1/2023 to 2/28/2024 and period 2 has a start and end date of 2/29/2024 to 2/28/2025 and so on...
- The expected dates for the periods are - period one should have a start and end date of 3/1/2023 to 2/29/2024 and period 2 should have a start and end date of 3/1/2024 to 2/28/2025 and so on...
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 |