List of cXML Status Codes

	English	
Deutsch - Machine Translation Español - Machine Translation Français (France) - Machine Translation Italiano - Machine Translation 日本語 - Machine Translation 한국어 - Machine Translation Português (Brasil) - Machine Translation Русский - Machine Translation 简体中文 - Machine Translation

Support Note KB0402515

Issue

List of cXML Status Codes that are sent as a response.

Resolution

Status	Text	Meaning
200	OK	The server was able to execute the request or deliver it to the final recipient. The returned Response might contain application warnings or errors: the cXML Request itself generated no errors or warnings, however, this status does not reflect any errors or warnings that might be generated afterward by the application itself. You will receive no further status updates, unless an error occurs during later processing.
201	Accepted	The request has been accepted for forwarding by an intermediate hub, or has been accepted by its ultimate destination and not yet been examined. You will receive updates on the status of the request, if a mechanism to deliver them is available. The client should expect later StatusUpdate transactions.
204	No Content	All Request information was valid and recognized. The server has no Response data of the type requested. In a PunchOutOrderMessage, this status indicates that the PunchOut session ended without change to the shopping cart (or client requisition).
211	OK	Buyers can use this status code to send a broadcast message to suppliers to inform them about any events they need to know, such as holiday schedules, production facility closure, or completion of certain activities such as planning run completion.
280		The request has been forwarded by an intermediate hub. You will receive at least one more status update. This status could mean that the request was delivered to another intermediary or to the final recipient with 201 status, or that it was forwarded via a reliable non-cXML transport.
281		The request has been forwarded by an intermediate hub using an unreliable transport (such as email). You might receive status updates; however, if you do not received status updates, there is not necessarily a problem.
400	Bad Request	Request unacceptable to the server, although it parsed correctly.
401	Unauthorized	Credentials provided in the Request (the Sender element) were not recognized by the server.
402	Payment Required	This Request must include a complete Payment element.
403	Forbidden	The user has insufficient privileges to execute this Request.
406	Not Acceptable	Request unacceptable to the server, likely due to a parsing failure.
409	Conflict	The current state of the server or its internal data prevented the (update) operation request. An identical Request is unlikely to succeed in the future, but only after another operation has executed, if at all.
412	Precondition Failed	A precondition of the Request (for example, a PunchOut session appropriate for a PunchOutSetupRequest edit) was not met. This status normally implies the client ignored some portion of a previous transmission from a server (for example, the operationAllowed attribute of a PunchOutOrderMessageHeader).
417	Expectation Failed	Request implied a resource condition that was not met. One example might be a SupplierDataRequest asking for information about a supplier unknown to the server. This status might imply lost information at the client or server.
450	Not Implemented	The server does not implement the particular Request. For example, PunchOutSetupRequest or the requested operation might not be supported. This status normally implies the client has ignored the server’s profile.
475	Signature Required	The receiver is unwilling to accept the document because it does not have a digital signature.
476	Signature Verification Failed	The receiver is unable to validate the signature, possibly because the document was altered in transit, or the receiver does not support one or more algorithms used in the signature.
477	Signature Unacceptable	The signature is technically valid, but is not acceptable to the receiver for some other reason. The signature policies or certificate policies may be unacceptable, the type of certificate used may be unacceptable, or there may be some other problem.
500	Internal Server Error	Server was unable to complete the Request.
550	Unable to reach cXML server	Unable to reach next cXML server to complete a transaction requiring upstream connections. An intermediate hub can return this code when a supplier site is unreachable. If upstream connections complete, intermediate hubs should return errors directly to the client.
551	Unale to forward request	Unable to forward request because of supplier misconfiguration. For example, an intermediate hub failed to authenticate itself to a supplier. Clients cannot rectify this error, but this error might be resolved before the client retries.
560	Temporary server error	For example, a server might be down for maintenance. The client should retry later.

Additional Information

You can also find this list and the list for status codes for catalog-upload requests on the cXML Reference Guide, section 3.1.9.1, available for download at http://cxml.org/.

Applies To

SAP Business Network for Procurement & Supply Chain