VWS Periodic Charge Expiry For Pre-Charge Events Include An Incorrect PC_RENEWAL_DATE Value
(Doc ID 2822094.1)
Last updated on NOVEMBER 23, 2021
Applies to:Oracle Communications Network Charging and Control - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC), 188.8.131.52.0 version,
A periodic charge can be configured with a pre-charge notification in the "Notifications" tab of the periodic charge configuration screen. In Customer's case, periodic charges are set up to have the first (and only) pre-charge notification 1 day before the charge. It sends a notification called RENEWALPENDING at this time from the Voucher and Wallet Server (VWS) through to the Service Logic Controllers (SLCs) to be processed by the InvokeOSD special control plan. The notification event is processed by the InvokeOSD control plan (the date is reformatted and then sent via Data Access Pack (DAP) to Customer specific system).
One of the fields in this event is the PC_RENEWAL_DATE field. This is set to the date/time the periodic charge will renew. In this case, this is 1 day after the notification is sent. So the NCC VWS is configured to convert this date to "local time" (i.e. the timezone specified by the periodic charge) and sent as a string. For example:
The date/time is specified as a GMT date/time (i.e. no timezone), but in actual fact the VWS has converted this to the timezone specified by the periodic charge (Europe/Rome). In the database the date/time is actually going to be 2021-07-21T22:05:00Z. This work as intended.
Unfortunately between the hours of 10pm GMT and 12pm GMT, the DAY of this date is wrong, The above example should be 2021-07-23, not 2021-07-22. It seems that in the VWS date manipulation code to calculate the local time of the periodic charge renewal, something goes wrong when the day changes due to timezones. The other 22 hours of each day the calculated PC_RENEWAL_DATE is right.
How to resolve this?
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