Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Checked for relevance on 10-April-2013
*** Checked for relevance on 12-27-2014 ***
The UTC_TIME_OFFSET is configured as -0400 which works fine in the timings when daylight saving is present, but when the daylight saving was revoked on 7th Nov the rating engine is rating the EDRs with a time difference of 1 hour than the actual event time. Events are getting rated with 1 hour less time of what it is there in EDR file.
The account 1000497 was created on 12-NOV-2010 11:08:49 but while rating this EDR, the rating engine considered EDR time as 1 hour less of what was there in EDR file
Input EDR example:
In case of above EDR, time is 11:47:33 but while rating it has been considered as 10:47:33.
Hence EDR is getting rejected with error as "Customer login (001000497) not valid for time (1289576853)". This error is because it checks for account creation time which is currently in the future i.e. 12-NOV-2010 11:08:49
In above case, while rating expected EDR time should be considered as it is mentioned in EDR file i.e. 11:47:33 instead of 10:47:33.
In this example, SIMPLESAMPLE_v1_InMap.dsc input grammar has been used. The pipeline rating engine is rating the EDRs as per UTC offset time -> -0400 currently configured in pipeline but after the daylight saving was revoked the offset time shall be -0500.
The current workaround to this issue is to modify the UTC offset configuration to “-0500” but once the daylight saving is introduced next year this setting needs to be changed again.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms