My Oracle Support Banner

The Exception InvalidOrderDataFault in OSM Response does not indicate which field is missing (Doc ID 1407636.1)

Last updated on JANUARY 16, 2020

Applies to:

Oracle Communications Order and Service Management - Version 7.0.3 and later
Information in this document applies to any platform.

Goal

When you use the operation "createOrderBySpecification" of the OSM Web Services (WS)  API and the exception "InvalidOrderDataFaultType" occurs, the response doesn't show which field 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>

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.