AIA/BRM: Future Date Is Getting Committed When PCM_OP_CUST_MODIFY_CUSTOMER Is Run (Doc ID 1261564.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.1.0 [Release 7.4.0]
Information in this document applies to any platform.
***Checked for relevance on 15-Apr-2013***
Checked for relevance on 28-May-2016

Symptoms

There are 5 hours difference in PURCHASE_START_T, USAGE_START_T, CYCLE_START_T when calling PCM_OP_CUST_MODIFY_CUSTOMER in the timestamp when a user passed them from AIA and at the time it reaches CM.

For example, for modify_customer from AIA:

<brm:PURCHASE_START_T>1970-01-01T00:00:00</brm:PURCHASE_START_T>
<brm:CYCLE_START_T>1970-01-01T00:00:00</brm:CYCLE_START_T>
<brm:USAGE_START_T>1970-01-01T00:00:00</brm:USAGE_START_T>
<brm:PURCHASE_END_T>1970-12-31T00:00:00</brm:PURCHASE_END_T>
<brm:CYCLE_END_T>1970-12-31T00:00:00</brm:CYCLE_END_T>
<brm:USAGE_END_T>1970-12-31T00:00:00</brm:USAGE_END_T>


in corresponding fragment of cm.pinlog

3 PIN_FLD_PURCHASE_START_T TSTAMP [0] (18000) Thu Jan 1 00:00:00 1970
3 PIN_FLD_CYCLE_START_T TSTAMP [0] (18000) Thu Jan 1 00:00:00 1970
3 PIN_FLD_USAGE_START_T TSTAMP [0] (18000) Thu Jan 1 00:00:00 1970
3 PIN_FLD_PURCHASE_END_T TSTAMP [0] (31467600) Thu Dec 31 00:00:00 1970
3 PIN_FLD_CYCLE_END_T TSTAMP [0] (31467600) Thu Dec 31 00:00:00 1970
3 PIN_FLD_USAGE_END_T TSTAMP [0] (31467600) Thu Dec 31 00:00:00 1970


The BRM server timezone is UTC-5.

The offset 18000 should not be applied, as the purchased product should start now. When 18000 offset is applied, the time stamp is set to 5 hours ahead from the current time because this 18000 is relative time from current time for opcode PCM_OP_CUST_MODIFY_CUSTOMER.

AIA 2.4 and 7.4 PS3 JCA Adapter is used.

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