My Oracle Support Banner

Java.Lang.Exception: Date Supplied In Local Timezone But Interactiontimezone UTC (Doc ID 1423015.1)

Last updated on AUGUST 24, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Information in this document applies to any platform.


While processing a sales order from CM we are getting the following error:

"java.lang.Exception: 2012-02-20T12:12:07 - Date supplied in LOCAL timezone but "InteractionTimeZone" configuration=UTC" in default_group~app_soa~default_group~1.log.

Snippet of SOA log
 ============>>12/02/20 17:55:38
<< == Inside SB Code == >>12/02/20 17:55:38 << ==
Inside Add Sub Process:ServiceBundles == >>12/02/20 17:55:38
<< == Before Modify Customer == >>12/02/20 17:55:38 <<
== Before Modify Customer Before Set Dynamic Partner Link Scope==
>>12/02/20 17:55:38 << == Before Modify Customer Before
Invoke== >>12/02/20 17:55:38 java.lang.Exception:
2012-02-20T12:12:07 - Date supplied in LOCAL timezone but
"InteractionTimeZone" configuration=UTC12/02/20 17:55:38       at
Source)12/02/20 17:55:38       at
Source)12/02/20 17:55:38       at
Source)12/02/20 17:55:38       at
oracle.tip.adapter.brm.BRMXMLToFlist.parseDoc(Unknown Source)12/02/20
17:55:38       at oracle.tip.adapter.brm.BRMXMLToFlist.convert(Unknown
Source)12/02/20 17:55:38       at
Source)12/02/20 17:55:38       at


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.