cXML PO Collaboration Errors and Resolution
Understand error messages that you may receive on cXML Purchase Orders (PO) Collaboration
This topic helps you understand transmission failure messages that you may receive on cXML PO Collaboration:
| Error | Root Cause and Fix | Action required |
|---|---|---|
<Status text="Expectation Failed" code="417"> |
PO is missing need-by-date. PO Confirmation is not required. |
Include missing need-by-date. |
<Status text="Expectation Failed" code="417"> |
PO need-by-date is before order-creation. cXML will not work. |
|
<Status text="Expectation Failed" code="417"> |
PO need-by-date is before order-creation. cXML will not work. |
|
<Status text="Expectation Failed" code="417"> |
Supplier is under confirming the PO line quantity (qty). Suppliers can do split shipments but ConfirmationStatus quantity must equal the PO line qty. |
Send the cXML again with <ConfirmationStatus quantity> equal to the PO line quantity. |
<Status text="Expectation Failed" code="417"> |
Supplier is over confirming the PO line qty. | Send the cXML again with <ConfirmationStatus quantity> equal to the PO line quantity. |
<Response> |
shipmentDate and deliveryDate cannot be backdated | Update shipmentDate and deliveryDate to current date or future. |
<Status text="Expectation Failed" code="417"> |
Line has already been confirmed, or missing Comment value. | Review details of the PO line. |
<Status text="Bad Request" code="400"> |
Line type should be 'detail' with <Comments>, or line type is 'reject' but missing <Comments> | Review details of the PO line. |