BRM JCA Adapter Does Not Accept GMT/UTC Time For End_t (Doc ID 1089269.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 20-Nov-2013
*** Checked for relevance on 05-29-2016 ***

Symptoms

BRM JCA Adapter does not accept timezone with datetime in xml payload. It always assumes the timezone to be PDT which is the server timezone.

Steps to Reproduce

When using the Order to Bil PIP 2.5, Siebel places an order. The order datetime is mapped to END_T of PCM_OP_SUBSCRIPTION_PURCHASE_DEAL. The order xml payload is passed to BRM JCA Adapter which converts the order datetime into UTC format and creates the input flist for BRM opcode. During this conversion, it ignores the timestamp of the datetime and always assumes it to be PDT (which is the server timezone).

e.g. If order date is passed in xml payload as

<brm:END_T>2010-03-24T21:54:40</brm:END_T>


then BRM JCA adapter converts it into

0 PIN_FLD_END_T TSTAMP [0] (1269492880) 24/03/2010 21:54:40:000 PM


please note that (1269492880) is Thu, 25 Mar 2010 04:54:40 UTC.
Tried sending different values, but the JCA adapter ignores the timestamp in all the cases below:

<brm:END_T>2010-03-24T21:54:40+00:00</brm:END_T>
<brm:END_T>2010-03-24T21:54:40-07:00</brm:END_T>
<brm:END_T>2010-03-24T21:54:40+05:00</brm:END_T>



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