bms.scale-ticket

Records a weight measured at the scale as a ticket and carries it into the yard close. Inbound and outbound weight is recorded here exactly once.

8 endpoints - system bms - module gate applies

What this module covers - Scale tickets, inventory lots and the lot ledger. Spare state is held separately on the inventory side (lot) and the scale side (ticket), so the two have to be reconciled.

Endpoints

Method	Path	What it does	Evidence
POST	/bms/scale-tickets/closing	Close the scale tickets - confirms unprocessed scale records at the yard close	handler bmsScaleTicketWrite() · calls yard-closing.js
GET	/bms/scale-tickets/history	Read the processing history of the scale tickets	handler bmsScaleTicketHistoryValue() · tables T_SCALE_TICKET
POST	/bms/scale-tickets/outbound-weight-apply	Apply the outbound weight to a scale ticket	handler bmsScaleTicketWrite() · calls container.php
POST	/bms/scale-tickets	Register a scale ticket	handler bmsScaleTicketApiCreate() · calls api_catalog.php, history_helper.php
DELETE	/bms/scale-tickets/(?P<id>\d+)	Delete a scale ticket	handler bmsScaleTicketWrite()
GET	/bms/scale-tickets/(?P<id>\d+)	Read a scale ticket in detail	handler prepare()
PATCH	/bms/scale-tickets/(?P<id>\d+)	Edit a scale ticket	handler bmsScaleTicketWrite()
GET	/bms/scale-tickets/(?P<id>\d+)/spare-context	Read the spare inventory state behind a scale ticket - which lots are held as spare	handler bmsScaleTicketSpareContextValue() · tables T_INVENTORY_LOT, T_INVENTORY_LOT_LEDGER, T_SCALE_TICKET +1 more

Topics this module shares with other modules

• Scale - this topic is spread across 3 modules and 17 endpoints.

Tables this module reads

T_SCALE_TICKET (2x) · T_INVENTORY_LOT · T_INVENTORY_LOT_LEDGER · T_TRANSLOAD

---

The description is a summary read off the route path, the handler, the tables it reaches and the screens that call it. Nothing is guessed without evidence: where the handler has to be read, it says so. The full evidence is on each endpoint page.