Serial & Lot Control#

For regulated / traceable industries, parts are tracked either per unit (serial) or per batch (lot). Both flavours flow through the same lifecycle — receipt, reservation, issue, ship — but the record granularity differs.

Serial control#

• Every physical unit has a unique serial number.
• Uniqueness is enforced at write to INVTSER.
• Reservations against a WO lock specific serials (IReserveSerialHelper).
• On issue to WO, the serial becomes a child of the assembly’s serial via SerialComponentToAssemblyHelper — this is what allows recall traceability.
• On ship, the serial’s status transitions to shipped and its ownership is recorded on the ship-bill line.

Lot control#

• A lot groups a batch of physical units received together (typical for chemicals, wet solder paste, adhesives).
• Lot metadata: lot number, manufacture date, expiration date, supplier lot reference.
• InvtLotHelper handles create / update; expiration is checked at issue time and by cycle count.
• FIFO / FEFO (first-expired-first-out) issue rules can be configured; the kit allocator respects the configured policy when reserving.

Import#

ImportInvtSerialFieldsHelper and SerialImport handle bulk-import of pre-existing serials during data migration.

Business rules#

• A serial can be in exactly one state: on-hand, reserved, issued-to-WO, consumed, shipped, or RMA. State transitions are recorded on the serial row.
• Reservation is not consumption. A serial reserved by kitting is still on-hand and can be un-reserved (un-kitted) as long as the WO hasn’t consumed it.
• Expired lots must not be issued — InvtLotHelper blocks it and Cycle Count flags them for disposition.

Where it lives#