My Oracle Support Banner

32-bit BRM Could Not Handle Future Dates Beyond Year 2038 (Doc ID 2501708.1)

Last updated on JANUARY 16, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On : and versions, Core Billing of Oracle Billing and Revenue Management (BRM):

The following issues with BRM are due to 32-bit limitation:

1) A business use case involves Voucher validity for longer time periods like 15+ years, 20 years, etc., but BRM has limitation of holding the date range only up to year 2038.
    This limits BRM users from offering such extended validity for Voucher management.

2) A business Quality Assurance (QA) practice does not permit the user to move back the pin_virtual_time (PVT) to any backdate.
    This limits the capability to move PVTs on QA environment beyond 2038.

Would Oracle BRM Product management 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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.