9A. Serialized identities, physical containers and governed lot data
Keep serialized units, divisible handling units and category-specific batch facts distinct, immutable and searchable throughout custody.
Purpose
Keep serialized units, divisible handling units and category-specific batch facts distinct, immutable and searchable throughout custody.
Materials Planner, Quality Inspector, QA Head, Project / Contract Manager, Stores Officer, Stores Supervisor, Auditor
Serialized actuator stock serial ACT-0001 / OEM SN-OEM-774 / internal KSH-2026-000042; cable roll ROLL-2026-0042 opened at 100.000000 M; batch heat HEAT-42A.
Before you begin
- Approved serialized or batch-controlled catalogue items exist
- A divisible receipt balance exists before container registration
- Different named authors and checkers are available
- Only fictitious acceptance data is used
Identity and quantity boundaries
The immutable serial carried by stock ledger and current balance. OEM, internal and asset identities are aliases of its physical instance and cannot create duplicate usable stock.
A maker-checker-controlled tenant, site, category or item scope with prefix, optional UTC year, sequence width and atomically allocated next value.
Changes the current OEM, internal or asset identity while keeping prior values searchable with actor, reason and history; it never rewrites the canonical stock serial.
Adopts quantity from an eligible receipt/bulk balance into one persistent container without changing total stock. Container identity then follows issue, transfer, return, count, subcontractor and disposition transactions.
A proposed observed remaining quantity. The measurer cannot approve it; only an independent decision posts the exact adjustment and updates the reconciliation.
An immutable typed value snapshot for one item and batch. Identity-defining values freeze after custody history; corrections create a new independently approved version.
Procedure
- 1
Create a scoped internal-serial numbering profile, submit it and have a different item approver activate it. Preview and allocate values concurrently; confirm no duplicate value is produced.
- 2
Receive or complete one serialized unit with OEM and/or governed internal identity. Search the physical-instance register by canonical, OEM, internal and asset value and confirm every identity resolves to one record.
- 3
Correct one alias with a detailed reason and prove both the current and historical value remain searchable while the canonical stock serial is unchanged.
- 4
Register an eligible divisible receipt balance as a named physical container. Confirm bulk quantity decreases by exactly the opening amount, container quantity increases by the same amount and total stock is unchanged.
- 5
Issue a partial quantity from the exact container and reconcile opening + adjustments − issues = remaining. Submit a measured variance and have a different supervisor approve or reject it.
- 6
Define a typed category lot field with field classification, submit it and have a different checker approve it. Capture batch values as another immutable revision, independently approve them, then search and export the assigned-site/clearance-scoped register.
- 7
As Auditor, verify container events, serial alias history, lot revision history and the related stock/traceability records without changing inventory.
Expected result
- OEM serial, internal serial, asset code, batch and container remain distinct identities
- One physical instance cannot produce duplicate positive serialized stock
- Internal serial allocation is scope-aware, collision-safe and independently approved
- Container adoption and all downstream movements preserve total quantity and exact container identity
- Only an independent variance decision changes remaining content
- Lot definitions and revisions enforce type, required/enum rules, maker-checker and field-level classification
- Search, register and CSV results are filtered by permission, assigned site and clearance before values are returned