BRM Receives UTCDatetime Value As Local Time (Doc ID 1598873.1)

Last updated on OCTOBER 04, 2016

Applies to:

Oracle Communications Order to Cash Integration Pack for Oracle Communications Billing and Revenue Management - Version 11.2 and later
Information in this document applies to any platform.
Communications Family Pack 11.2

Symptoms

ACTUAL BEHAVIOR
---------------
During sync from Siebel to BRM (SyncCustomerPartyListBRMProvABCSImpl) it is seen that BRM receives UTCDatetime value as Local time.

Note: Siebel uses UTC time and BRM uses Local time.

EXPECTED BEHAVIOR
-----------------------
Expect for BRM to receive time in UTC also


The issue has the following business impact:
If customer accounts are created with UTC date, BRM team say that billing programs will not work according to expectation with an example that if customer is created in Siebel at 7 PM colombia time, it will created in next day. So, Billing program will not consider that client if it try to take data for today even though client is created today in real.

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