SupplyOn async callback request schema and branches
On this page
SupplyOn async callback request schema and branches
The request schema of the async status callback, the correlation contract, the processing branches, and sample payloads.
The async callback endpoint is POST /api/sn_supplyon_po/supplyon_outbound_po_async_callback. The request body follows the SupplyOn status notification schema, a pure status acknowledgment:
-
uuid (required): The correlation key. Equals the synchronous 201 transaction ID.
-
status (required): Strictly OK or ERROR.
-
Errors (optional): A list of items, each with a Code and Text.
No line-level positions ride the callback. Supplier confirmations come only from the confirmation pull.
Correlation contract. The send subflow stamps SON-TXN:<TransactionID> into the outbound header message at status 20. The callback uuid is that transaction ID, so the subflow looks up the row by message and then overwrites the message with the outcome text. The subflow does not use erp_number for correlation. On the success branch only, the subflow stamps erp_number with the order number so the framework Handle Status Change business rule fires on status 30.
Header and lines move in lockstep in both branches. A duplicate or re-delivered callback re-applies the same status (idempotent). An unexpected error in the subflow is caught by the native Error Handler.
Sample callback payloads
// Success
{ "uuid": "2491C8AF4F962D2CCB87CC102AFCXXXX", "status": "OK", "Errors": [] }
// Failure
{
"uuid": "2491C8AF4F962D2CCB87CC102AFCXXXX",
"status": "ERROR",
"Errors": [{ "Code": "BOOK_017", "Text": "Order rejected: unknown supplier for routing triple." }]
}
Keep exploring.
Find another answer, or bring this documentation into your own tools.