32-bit BRM Couldn't Handle Future Dates Beyond Year 2038
(Doc ID 2501708.1)
Last updated on OCTOBER 10, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 and 18.104.22.168.0 versions, Core Billing
Oracle Billing and Revenue Management(BRM) Customers encounter following issues with BRM due to it's 32-bit limitation.
1Customer business use cases involve Voucher validity for longer time periods like 15+ years, 20 years etc., but BRM’s limitation of holding the date range only upto year 2038 may limit BRM Customers from offering such extended validity for Voucher management.
2) Customer's Quality Assurance(QA) practices doesn’t permit them to move back the pin_virtual_time(PVT) to any backdate, hence they are lacking capability to move PVTs on their QA env beyond 2038 for testing purposes.
BRM Customers would like Oracle BRM Product management to consider these concerns and enhance the BRM product to allow future dates beyond 2038. Probably by making BRM a 64-bit application.
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