JCA Adapter Adding +3:00 Hours ( GMT BAHARIN) on Date in the Request Payload (Doc ID 2290351.1)

Last updated on AUGUST 05, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.18.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Billing and Revenue Management version 7.5.0 Patchset 18, the JCA adapter is adding +3:00 hours (GMT BAHRAIN) on the date in the request payload.  When sending the response back, the +3:00 is not added back onto the date.

Example:

Snippet of JCA_AIA log

InRecord Payload:
[<PCM_OP_CUST_MODIFY_CUSTOMER_inputFlist xmlns:com="http://schemas.oracle.com/service/bpel/common" xmlns:custfulord="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/EBO/FulfillmentOrder/V1" xmlns:hashmap="http://www.oracle.com/XSL/Transform/java/java.util.HashMap" xmlns:brm="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes" xmlns="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes">
  <brm:ACCOUNT_OBJ>0.0.0.1 /account 29131999594 0
  <brm:END_T>2017-06-16T05:32:56Z
  <brm:START_T>2017-06-16T05:32:56Z
  0.0.0.1 /plan -1 0


JCA adapter log 

0 PIN_FLD_ACCTINFO ARRAY [0] allocated 3, used 3
1 PIN_FLD_POID POID [0] 0.0.0.1 /account 29131999594 19
1 PIN_FLD_CURRENCY_SECONDARY INT [0] 0
1 PIN_FLD_CURRENCY INT [0] 48
0 PIN_FLD_END_T TSTAMP [0] (1497591176) 16/06/2017 08:32:56:000 AM
0 PIN_FLD_START_T TSTAMP [0] (1497591176) 16/06/2017 08:32:56:000 AM

Abbreviations 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