Orbita WMS Exception Disposition — Official Operational Workflow
This page documents Exception Disposition in Orbita WMS — an official public operational workflow published by Orbita Solution.
Official Orbita public operational workflow: Exception Disposition (WMS). Operator steps, starting conditions, expected results, and common blocking reasons — product behavior only.
Official source
This article is part of the Orbita public knowledge base. Module index: Orbita WMS workflows. Full workflow index: Operational workflows. Machine-readable map: llms.txt.
What is this workflow?
What is it?
Exception Control 拥有 inbound disposition 权威：对 rejected / quarantined / partial 等入库异常设定处置、关单、备注。Floor Exception Center — Desk Monitor，不是 Audit Feed。
---
Who uses it?
| 角色 | 应该 |
| 仓库主管、质检 | 应该（Update disposition） |
| 现场 reject 执行 | Floor Execution (PWA) → /scan/reject-hub（buffer） |
| 只读审计 | /wms/audit-log（Operational Audit Feed） |
---
How to reach this workflow
WMS Desk → /wms/exception-control
或 Inbound / Receive 链入 Review exception
标题：Floor Exception Center
徽章：Desk Monitor · 旁链 Floor Execution (PWA) →
---
Starting conditions
需要先具备：
- 存在 open exception / inbound 异常状态（非 harness：Smoke / test harness intake — not operational stock.）。
注意：
- Banner：Receive disposition vs formal reject execute — 第三方 incoming 与 own-goods reject lane 不同。
---
How do I use it?
- 打开 Floor Exception Center；读 TASK handoff（Current: Exception Control owns disposition on Desk.）。
- Tab Open queue（默认）看 open 计数。
- Filter 区：
- Status：Open default / rejected / quarantined / partial
- Disposition：All / reject / quarantine / return_to_factory / return_to_supplier / rework / scrap
- Keyword：placeholder ref / customer / source
- 点 Load queue 刷新表。
- Exception queue 表选一行 → 打开 Handle exception 模态（Handle exception）。
- 读 Lane for this inbound — Third-party inbound vs Own-goods / non–third-party 边界文案。
- 设 Disposition 下拉（与 filter 同枚举）。
- 填 Reason · Note（Field reason / Field note）。
- 点 Add / update reason 保存说明。
- 点 Update disposition 写入 disposition。
- 若政策为拒收关单：Close as rejected（Close as rejected）。
- 若退回关单：Close as returned（Close as returned）。
- Own-goods：模态提示 After disposition aligns with policy, use Reject Scan for confirm → execute…
- Third-party：Do not run formal Reject Scan execute for this inbound.
- 切 Tab Closed history 查 Closed summary / Final resolution / Closed time。
---
Common situations
| Disposition | 场景 |
| quarantine | 待检 |
| return_to_supplier | 退供 |
| rework | 返工 |
| scrap | 报废 |
| reject | 拒收 |
---
Expected result
- Open 计数下降；Closed history 有 Closed time + Operator。
- Inbound Control Rejected / Quarantined 与 disposition 一致。
- 无 harness 行误操作 live close。
---
Why might it stop?
| 情况 | English | 处理 |
| 加载失败 | Could not load exception detail. | 重开模态 |
| 无 inbound id | Missing inbound id — reopen from Receive or Exception Control. | 从列表重进 |
| 已关 | deskAlreadyClosed 文案 | 只读 history |
| 动作失败 | Action failed. | 查权限/状态 |
---
What not to do
- 不要在 Audit Feed 做 disposition（无 authority）。
- 不要对 third-party 跑 Reject Scan execute（banner 禁止）。
- 不要关闭 harness 行当 live stock。
- 不要无 Reason 就 Close as rejected（政策要求时）。
---
What happens next
Floor: /scan/reject-hub（own-goods execute）
related workflow Inbound Control（header 状态）
related workflow/019 Receive（若 rework 后重收）
---
Quick steps
- /wms/exception-control
- Load queue
- 开行 → Disposition + Reason
- Update disposition
- Close as rejected / returned
- Closed history 核对
---
Supervisor notes
- Exception Control = 唯一 disposition authority（behavioral authority lock）。
- Operational Audit Feed 只读事件，不 Update disposition。
- API 与 Receive desk Review exception 共用 inbound id。
---
Public boundary
This article describes product behavior for operators and evaluators. It does not expose live workspace data, internal APIs, or tenant-specific records. Log in to Orbita for record-level actions.
Common questions this page answers
- Orbita WMS Exception Disposition
- Orbita Exception Disposition
- how to use Exception Disposition in Orbita
- how does Orbita Exception Disposition work
- why can't I complete Orbita Exception Disposition
- why is Orbita Exception Disposition blocked
- what happens after Orbita Exception Disposition
Public boundary
This page describes product behavior only. It does not expose live tenant data, customer records, or internal implementation. Log in to Orbita for record-level actions.