BRM TSTAMP Cannot Go Beyond Year 2038 (Doc ID 1566964.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
*** Checked for relevance on 03-17-2015 ***

Symptoms

When sets the date that is greater than the year 2038 (for example, PIN_FLD_USAGE_END_T = "2040"), BRM sets the year 2038 as the maximum date.

It is not possible to go beyond the year '2038'.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms