Article published on · Updated on · By DAWAP, the publisher of CIAMA
Understand why an order is missing
Your ERP has sent an order, but your sales team cannot find it in CIAMA. To investigate, a developer needs to locate the exchange and establish whether processing is complete, waiting for a reference or in error.
Following the order, fulfillment and stock workflow introduced in R021, this edition explains how to follow those operations. Execution logs and API receipts give business and technical teams shared references when investigating an incident.
What changes in daily work
- Find executions by capability and status.
- Track API writes using receipts and error codes.
- Prepare recovery from the actual processing state.
Features in detail
Core · Shared platform
Find an execution in context
Execution logs support search and filtering by mode, business area, status and capability within the account. The detail links an execution to its child processing steps so an operation can be followed.
API: track the outcome, not just acceptance
GET /api/pim/products/receipts/{receiptId} and GET /api/b2b/orders/receipts/{receiptId} expose receipts within the authenticated source’s scope. They include processing state, external reference and an error code when present.
Your integration can retain the receipt alongside its operation reference. An initial 202 Accepted response is a step in the journey; the receipt lets you follow its outcome.
Prepare targeted recovery
Operational tooling can redispatch integration events that remain pending, using a minimum age and a processing limit. Idempotency keys and source revisions govern writes: preserve and use them according to the contract rather than randomly replacing them on retries.
This foundation does not mean every error fixes itself. It gives teams references to investigate, correct the cause and verify the result. The CIAMA API documentation and overview of system integration extend this workflow.
Diagnose a missing product dependency
A sales colleague reports a B2B order missing from the cockpit and shares its reference with the technical team. The developer finds the receipt kept when sending the order: processing is waiting for a product referenced in its lines.
The developer first checks the product write and its own receipt, then follows order recovery using the procedure for that flow. The team verifies the applied result before closing the incident. This provides a specific diagnosis without resending every order or arbitrarily changing their identifiers.
This edition looks back at CIAMA’s evolution. The month is an editorial milestone in the product story, not a production deployment date.