These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Supply Chain Analytics
- Features
- Activity and Evidence
Activity and Evidence
Keep evidence files on each request and a receipt of every guarded action and its outcome.
OverviewOperation Exceptions×
Supply Chain Analytics · Activity and Evidence
New
Operation Exceptions
Operation receipts
| Parent | Action | Operation key | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| PR-32960 | ACT-110 | OK-372 | Pending | 14 Oct | Cut to length | |
| PR-71649 | ACT-429 | OK-118 | Failed | 20 Oct | Weld frame | |
| PR-80076 | ACT-720 | OK-326 | Needs review | 10 Oct | Drill and tap | |
| PR-54150 | ACT-569 | OK-351 | Pending | 11 Oct | Deburr | |
| PR-14547 | ACT-367 | OK-846 | Failed | 09 Oct | Assemble |
6 of 6 records
ACT-110Operation receipts · OR-38447
PendingParentPR-32960
Operation keyOK-372
Occurred at14 Oct
Failure reasonCut to length
What you can do
Keep the proof with the request
Quotes, demand forecasts, delivery notes and inspection reports are attached to the purchase request they support, with a title, evidence type, uploader, time and visibility of Internal or Shared.
Every guarded action, such as a submission, a commitment, an acceptance or a snapshot lock, leaves an operation receipt: the action, a unique operation key, the version it expected, the outcome, the time, any external reference and the failure reason. Outcomes are Pending, Completed, Failed or needs review. A repeated action with the same key returns the original result, so a retry never issues a commitment twice.
How the work is organized
- Evidence where the approver looks. Files sit on the request.
- Receipts for guarded actions. Each receipt shows what was expected and what happened.
- Daily reconciliation. Pending and Failed receipts are checked every day against the request’s lines, snapshots and decisions.
What to agree during setup
Agree the evidence types you attach and which may be shared with suppliers. Decide who reviews operation exceptions and how quickly. Set the time of the daily reconciliation.
Check the handoff on an actual case
A buyer issues a commitment just as the network drops. The receipt stays Pending. When the buyer retries, the same operation key returns the original result and no second order reference is created. The daily reconciliation finds the order reference and the Ordered status recorded and marks the receipt Completed.
A receiving action fails halfway because one line’s quantity would have exceeded the request. Its receipt shows Failed with that reason, and the analyst sends it back to the clerk.
During the pilot, interrupt one submission, one commitment and one acceptance on purpose and confirm each is resolved by the daily reconciliation without a second effect.
What your team sees
- Operation Exceptions — Receipts waiting for review with action, outcome and failure reason.
- Evidence Files — Files attached to each request, with type, visibility and uploader.
Follow the work through
- Correction and receipt reconciliation: Resolve receipts and correct scope.
- Demand to receipt: Where receipts are left.
Map the source records before importing history.
What it keeps track of
Data model- Record attachments
- Evidence files attached to a purchase request.
- Operation receipts
- Idempotent operation receipts recording guarded action outcomes.
- Purchase requests
- Purchase demand records with lifecycle, owner, counterparty and approved commitment.
- Team members
- Named team members with organization membership and platform identity.
Who uses it
Permissions- Supply Chain Analyst
- , Buyer, Procurement Approver, Admin.
- Buyer
- S attach evidence.
- The analyst resolves receipts.
- Approvers read evidence when deciding.
Set up Supply Chain Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.