My Oracle Support Banner

Upgrade BRM 12: JCA Adapter Date/Time Fields Changes from DateTime to String (Doc ID 2505135.1)

Last updated on OCTOBER 21, 2019

Applies to:

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

Goal

On Oracle Communications Billing and Revenue Management (BRM) version 12.0, it is observed that following changes are made in the BRM 12 JCA Adapter for all XXX_T (Timestamp) fields corresponds to BRM 7.5 in the file "PCM_OP_AR_ACCOUNT_ADJUSTMENT.xsd".

BRM 7.5:

<xsd:element name="END_T" minOccurs="0" maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:dateTime"/>
</xsd:simpleType>
</xsd:element>

BRM 12.0:

<xsd:element name="END_T" type="xsd:string" minOccurs="0" maxOccurs="1"/>


Neither this change is mentioned in the documentation nor impact of putting the Adapter with AIA PIPs in integrated systems such as RODOD is mentioned.

Why was this change made to this Date tag in XSD?

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.