My Oracle Support Banner

Discrepancy Between XSD And XML For BRMPricesServices (Doc ID 1521082.1)

Last updated on OCTOBER 11, 2018

Applies to:

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

Goal

It is seen that more data is getting returned as a response to OOB BRMPricesServices web service request .

This is not in par with the XSD provided:

For example :

Consider the following snippet from PCM_OP_PRICE_GET_PRICE_LIST.xsd . This is for deals array in output flist :

 

<xsd:complexType name="DEALS_ARRAY_PCM_OP_PRICE_GET_PRICE_LIST_1317">
     <xsd:sequence>
        <xsd:element name="ACCOUNT_OBJ" minOccurs="1" maxOccurs="1">
           <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                 <xsd:pattern value="([0-9]*\.)+[0-9]*(\s)+(((/)*|(/)(account)((/)*([a-zA-Z_]*))*))(\s)+[\-]*[0-9]+(\s)+[0-9]*"/>
                 <xsd:pattern value=""/>
              </xsd:restriction>
           </xsd:simpleType>
        </xsd:element>
        <xsd:element name="DESCR" minOccurs="0" maxOccurs="1">
           <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                 <xsd:maxLength value="1023"/>
              </xsd:restriction>
           </xsd:simpleType>
        </xsd:element>
        <xsd:element name="DISCOUNTS" minOccurs="0" maxOccurs="256">
           <xsd:complexType>
              <xsd:complexContent>
                 <xsd:extension base="DISCOUNTS_ARRAY_PCM_OP_PRICE_GET_PRICE_LIST_131729">
                    <xsd:attribute name="elem" type="xsd:string"/>
                 </xsd:extension>
              </xsd:complexContent>
           </xsd:complexType>
        </xsd:element>
        <xsd:element name="END_T" minOccurs="1" maxOccurs="1">
           <xsd:simpleType>
              <xsd:restriction base="xsd:dateTime"/>
           </xsd:simpleType>
        </xsd:element>
        <xsd:element name="FLAGS" type="xsd:int" minOccurs="0" maxOccurs="1"/>
        <xsd:element name="NAME" minOccurs="1" maxOccurs="1">
           <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                 <xsd:maxLength value="255"/>
              </xsd:restriction>
           </xsd:simpleType>
        </xsd:element>
        <xsd:element name="PERMITTED" minOccurs="0" maxOccurs="1">
           <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                 <xsd:maxLength value="255"/>
              </xsd:restriction>
           </xsd:simpleType>
        </xsd:element>
        <xsd:element name="PRODUCTS" minOccurs="0" maxOccurs="256">
           <xsd:complexType>
              <xsd:complexContent>
                 <xsd:extension base="PRODUCTS_ARRAY_PCM_OP_PRICE_GET_PRICE_LIST_131728">
                    <xsd:attribute name="elem" type="xsd:string"/>
                 </xsd:extension>
              </xsd:complexContent>
           </xsd:complexType>
        </xsd:element>
        <xsd:element name="START_T" minOccurs="1" maxOccurs="1">
           <xsd:simpleType>
              <xsd:restriction base="xsd:dateTime"/>
           </xsd:simpleType>
        </xsd:element>
     </xsd:sequence>
  </xsd:complexType>
...



Now see the below corresponding snippet from PCM_OP_PRICE_GET_PRICE_LIST.xml :


<brm:DEALS elem="0">
<brm:ACCOUNT_OBJ>0.0.0.1 /account 1 0</brm:ACCOUNT_OBJ>
<brm:CREATED_T>2012-12-22T08:05:44Z</brm:CREATED_T>
<brm:DESCR>SP Elm Muqeem Transactional Subscription Slots - Renew Subscription Deal</brm:DESCR>
<brm:END_T>1970-01-01T00:00:00Z</brm:END_T>
<brm:FLAGS>4194304</brm:FLAGS>
<brm:MOD_T>2012-12-22T08:07:36Z</brm:MOD_T>
<brm:NAME>SP Elm Muqeem Transactional Subscription Slots - Renew Subscription</brm:NAME>
<brm:PERMITTED>/service/telco/elm</brm:PERMITTED>
<brm:POID>0.0.0.1 /deal 119601 2</brm:POID>
<brm:PRODUCTS elem="0">
<brm:CODE>SP Elm Muqeem Transactional Subscription Slots</brm:CODE>
<brm:CYCLE_DISCOUNT>0</brm:CYCLE_DISCOUNT>
<brm:CYCLE_END_OFFSET>12</brm:CYCLE_END_OFFSET>
...



Notice above that the elements in the xml are more than in xsd.
For example, here  '<brm:POID>' is there is the xml, but its definition is missing in the xsd file.

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
 webservices.input.validation.enabled=true
webservices.output.validation.enabled=true
References


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