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">

Order confirmation is not applicable

</Status>

PO is missing need-by-date.

PO Confirmation is not required.

Include missing need-by-date.
<Status text="Expectation Failed" code="417">

Unable to propose change line 1.
Promised date needs to be set for a future date,

Reason insight events is invalid,
Reason insight events comment A value for "Reason Comment" is missing from the file.
A comment is required when Other is selected as the Reason Code.

</Status>

PO need-by-date is before order-creation.

cXML will not work. 

  1. User needs to change the need-by-date to be same as order-creation or future.
  2. Supplier to resend the payload.
<Status text="Expectation Failed" code="417">

Unable to accept line 1. Promised date needs to be set for a future date

</Status>

PO need-by-date is before order-creation.

cXML will not work. 

  1. User needs to change the need-by-date to be same as order-creation or future.
  2. Supplier to resend the payload.
<Status text="Expectation Failed" code="417">

ConfirmationStatus quantity must sum up to total ConfirmationItem quantity for PO 2197 Line 1

</Status>

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">

Unable to propose change line 1.
Reason insight events is invalid,
Reason insight events comment A value for "Reason Comment" is missing from the file.
A comment is required when Other is selected as the Reason Code.

</Status>
Supplier is over confirming the PO line qty. Send the cXML again with <ConfirmationStatus quantity> equal to the PO line quantity.
  <Response>

<Status text="Expectation Failed" code="417">

Invalid attributes in document.

</Status>

</Response>
shipmentDate and deliveryDate cannot be backdated Update shipmentDate and deliveryDate to current date or future.
    <Status text="Expectation Failed" code="417">

Unable to accept line 1.
Action Supplier is restricted from performing accept on PO 2230 Line 1

</Status>
Line has already been confirmed, or missing Comment value. Review details of the PO line.
<Status text="Bad Request" code="400">

Please provide an update to an existing line in order to submit a change request

</Status>
Line type should be 'detail' with <Comments>, or line type is 'reject' but missing <Comments> Review details of the PO line.

Related Items


Announcements and General Info

Check out the newest announcements for the CSP.

Get Started and Find Help in the CSP

Where to find help if you need assistance in the CSP

Getting Started with the Coupa Supplier Portal

Learn how you can use the Coupa Supplier Portal to manage customers and transactions.

Get Started with the CSP

Register and create your account for the CSP, set your account and notification preferences, and create custom views.