0 / HTTP Header for all Faults / HTTP/1.1 500 Internal Server Error
Content-Type: application/soap+xml; charset=utf-8
Content-Length: nnn
1. / e-PRIOR cannot process the message because of an anomalous condition / soapenv:Envelope xmlns:SOAP-ENV="
soapenv:Body>
soapenv:Fault>
<faultcode> soapenv:Server</faultcode>
<faultstring>Server Error</faultstring>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
2. / The namespace for a SOAP Envelope object (Envelope, Header or Body Part) is invalid / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:VersionMismatch</faultcode>
<faultstring>BEA-382032: The message must be an instance of: {
<detail>
<con:fault xmlns:con="
<con:errorCode>BEA-382032</con:errorCode>
<con:reason>The message must be an instance of: {
<con:details>
<err:InvalidEnvelope xmlns:err="
<err:localpart>Envelope</err:localpart>
<err:namespace>
</err:InvalidEnvelope>
</con:details>
<con:location>
<con:path>request-pipeline</con:path>
<con:error-handler>true</con:error-handler>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
3. / The root element of the message is not Envelope / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>BEA-382032: The message must be an instance of: {
<detail>
<con:fault xmlns:con="
<con:errorCode>BEA-382032</con:errorCode>
<con:reason>The message must be an instance of: {
<con:details>
<err:InvalidEnvelope xmlns:err="
<err:localpart>Envel</err:localpart>
<err:namespace>
</err:InvalidEnvelope>
</con:details>
<con:location>
<con:path>request-pipeline</con:path>
<con:error-handler>true</con:error-handler>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
4. / The message does not have a Body part / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>BEA-382033: A soap:Envelope must contain a soap:Body</faultstring>
<detail>
<con:fault xmlns:con="
<con:errorCode>BEA-382033</con:errorCode>
<con:reason>A soap:Envelope must contain a soap:Body</con:reason>
<con:location>
<con:path>request-pipeline</con:path>
<con:error-handler>true</con:error-handler>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
5. / Message is not well formed because it lacks information about the operation in the Body Block (like the wrapper element) / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Undefined operation</faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>2</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
6. / Message in the Body Block not well formed because it does not validate against its XSD / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Undefined incoming message</faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>1</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
7. / Multiple Messages (i.e. more than one) in the Body Block / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Undefined incoming message</faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>1</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
8. / Message Body violates hard business rule / Used in synchronous web service calls: e.g. Query Request:
<soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Hard business rule violated</faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>DocumentTypeCode:4</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
9. / Envelope lacks header block / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Unauthorized Access</faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>5</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
10. / Envelope lacksheader elements in the header block [e.g. no SupplierID (applicable for all requests) OR CustomerID (only applicable for write requests)] / Same as ID 9
11. / Wrong information in the Header Block (e.g. no real GLN). / Same as ID 9
12. / Unauthorised Access to the Operation according to the Header information / Same as ID 9
13. / Message not well-formed / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>BEA-382030: Failure while unmarshalling message: Failed to parse XML text</faultstring>
<detail>
<con:fault xmlns:con="
<con:errorCode>BEA-382030</con:errorCode>
<con:reason>Failure while unmarshalling message: Failed to parse XML text</con:reason>
<con:location>
<con:node>PipelinePairNode2</con:node>
<con:pipeline>PipelinePairNode2_request</con:pipeline>
<con:stage>init</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
14. / Attachment lacks binary content / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Missing Attachment binary data</faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>916:6</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
15. / Incorrect authentication data (internal asynchronous messaging) / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Incorrect authentication data </faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>4</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
16. / Message corrupted / <soapenv:Envelope xmlns:soapenv="
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Message has been corrupted</faultstring>
<detail>
<ec:fault ec="ec:services:wsdl:Fault-0.1">
<ec:ResponseCode>6</ec:ResponseCode>
<ec:Description>XML extract</ec:Description>
</ec:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Note: Multiple Header or Body Parts do not raise a SOAP Fault.