Unknown outcome and resolving
What "Needs a check" means and how you decide what happens to the order.
When it happens
An order was sent to a partner endpoint and the answer never arrived. Because the integration has no check call, the service cannot find out whether the ERP wrote the document.
There are two possibilities, and from here they look the same:
- The ERP wrote the document and only the answer was lost.
- The ERP never received the order.
If the service sent again blindly, in the first case it would create a duplicate document. So it stops and waits for a person. The order appears as “Needs a check” and on Home, under “Needs you”.
With standard SoftOne (setData), or with a check call, this does not happen: the service checks by itself and carries on.
Resolving
Resolving is done by an owner or an admin.
- Search the ERP for a document with the order’s reference. The reference is shown in the resolve window.
- Under Orders press “Resolve” on the order.
- Choose what you found:
- It is in the ERP. Enter the document number. The order is marked “Sent” and is not sent again.
- It is not there, send again. You confirm that you checked, and the order is sent.
Take care with the second choice. If the ERP already has a document, sending again creates a duplicate and cannot be undone. Really check before you choose it.
Your choice is recorded on the order.
How to keep it from happening again
Set a check call in Order settings. See Partner endpoint. Related code: write_uncertain.