Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
*** Checked for relevance on 05-15-2014 ***
After installing patch 13508946 in production, along with BIP 10.1.3.4.2, it was noticed that date conversion is not happening correctly.
When the same query is used in SQL prompt and through BIP, we get different numbers.
select BIPEXT.INFSTRTOTIMET(NVL(:PARAM_START_DATE, '01-FEB-70 08.00.00 AM'),2) Date1, bipext.infstrtotimet(NVL(:PARAM_END_DATE, '01-FEB-37 08.00.00 AM'),2)-1 Date2 FROM DUAL;
Where PARAM_START_DATE is “12/25/2011 -0800” and PARAM_END_DATE is “01/23/2012 -0800”
BIP Result :
The one from SQL prompt is the correct one.
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