Skip to content

This page describes a server-side capability that no operator screen uses today. It was written for whoever maintains the system, and its own source records the business applicability as unknown. Do not use it as an operating instruction. The everyday documents are: Procedures and The working day, step by step.

Shared Inventory Lot Correction Capability

Purpose

Process ID: PROC-WMS-INVENTORY-LOT-CORRECTION Contract version: 0.1.0 Lifecycle: draft Owner: WMS inventory

Who does this

Whoever owns this job.

Before you start

  • You have the right account (see Permissions and Access).
  • The record and date you are working on are correct.
  • Words you do not know are in the Glossary.

Process ID: PROC-WMS-INVENTORY-LOT-CORRECTION Contract version: 0.1.0 Lifecycle: draft Owner: WMS inventory

Boundary

This tenant-scoped API capability changes one existing inventory lot and is distinct from transload-variance Bale Adjustment. No active operator UI caller was found in the inspected source. CTC and MK business applicability are therefore UNKNOWN, and the capability is not assigned to either tenant's operator manual/wiki.

Current routes

  • GET /api/wms/inventory/lots
  • GET /api/wms/inventory/lots/{id}
  • PATCH /api/wms/inventory/lots/{id}
  • POST /api/wms/inventory/lots/{id}/adjust

Mutations

  • PATCH may change warehouse location, received date and remark. Lot status is rejected because lifecycle events own it.
  • Warehouse location uses the placement helper and updates the active inventory-lot placement/mirror path.
  • Received date and remark update T_INVENTORY_LOT directly.
  • Legacy adjust requires remaining quantity and net weight and delegates to the same Bale count-check helper, including a COUNT_CHECK ledger event when the ledger schema exists.
  • The route uses the legacy write runner, which supplies the DB transaction boundary around the helper result.

Completion and recovery

  • Reread the exact lot after every PATCH/adjust and compare location, received date, remark, remaining quantity/weight and ledger as applicable.
  • A location/metadata PATCH does not append the Bale ledger in the inspected source. Do not claim complete ledger audit coverage for these fields.
  • On timeout, reread before retrying. A repeated PATCH may repeat a placement transition or overwrite a newer metadata value.

Verification scenarios

  • SCN-010: list and read one current-tenant lot.
  • SCN-020: update an allowed location/received-date/remark field and verify exact read-back.
  • SCN-030: reject direct lot-status mutation.
  • SCN-040: perform legacy count check through /adjust and verify balance plus ledger/fallback result.

Unknowns

  • No active page caller or approved CTC/MK operator role was identified.
  • Location/metadata correction has no inspected reversal or dedicated history model.
  • The route uses the current request/session client ID and wms.inventory; that proves tenant isolation, not business applicability.
  • Operator manual/wiki disposition is NO_WIKI_REQUIRED until an active operator workflow is confirmed.

---

Source: docs/processes/INVENTORY_LOT_CORRECTION_WORKFLOW.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.