The Exception InvalidOrderDataFault in OSM Response does not indicate which field is missing
edited Feb 9, 2012 7:35PM in Order and Service Management (Communications Industry) (MOSC) 2 comments
When you use the operation "createOrderBySpecification" of the OSM WS API and the exception "InvalidOrderDataFaultType" occurs, the response doesn't show which is the field that is missing in the input XML.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:ord="http://xmlns.oracle.com/communications/ordermanagement">
<faultcode>ord:fault</faultcode>
<faultstring>Mandatory check failed</faultstring>
<faultactor>unknown</faultactor>
<detail>
<InvalidOrderDataFault xmlns="http://xmlns.oracle.com/communications/ordermanagement">
<Description>Mandatory check failed</Description>
</InvalidOrderDataFault>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:ord="http://xmlns.oracle.com/communications/ordermanagement">
<faultcode>ord:fault</faultcode>
<faultstring>Mandatory check failed</faultstring>
<faultactor>unknown</faultactor>
<detail>
<InvalidOrderDataFault xmlns="http://xmlns.oracle.com/communications/ordermanagement">
<Description>Mandatory check failed</Description>
</InvalidOrderDataFault>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
0