Skip to content

GET /bms/scale-tickets/(?P\d+)/spare-context

BMS > bms.scale-ticket

What it does

#^/bms/scale-tickets/(?P<id>\d+)/spare-context$# accepts GET and is declared in app/systems/BMS/scale-ticket/api_routes.php:79 as a regex pattern.

The route handler delegates to bmsScaleTicketSpareContextValue(). That function is the owner of this behaviour; the route entry is only dispatch.

Who calls it

No literal caller path was found in frontend/, public/ or new-system/. The endpoint may be called through a constructed path, a helper wrapper, or only by an external client. Treat the route table and owner function as the authority.

Input

Where Key
path id

Request bodies must not use TYPE, ACTION or USERNAME as contract fields.

Output

Key
SOURCE_TRANSLOAD_ID
SPARES

Success is { "data": …, "requestId": "…" }. Failure is { "error": { "code", "message" }, "requestId": "…" }.

SQL executed

SELECT ID, REFERENCE_NUMBER FROM T_TRANSLOAD WHERE CLIENT_ID=? AND SCALE_TICKET_ID=? AND DELETED_AT IS NULL ORDER BY ID ASC LIMIT 2

SELECT ST.REFERENCE_NUMBER, ST.INITIAL_COMMODITY_NAME AS COMMODITY_NAME, IL.INBOUND_QUANTITY, IL.INBOUND_NET_WEIGHT

SELECT UUID FROM T_SCALE_TICKET WHERE CLIENT_ID=? AND ID=? AND DELETED_AT IS NULL LIMIT 1

Data

Tables reached from the owner function:

  • T_INVENTORY_LOT
  • T_INVENTORY_LOT_LEDGER
  • T_SCALE_TICKET
  • T_TRANSLOAD

Access

  • module-gated on bms.scale-ticket, so tenant module access applies

Validation and failure messages

  • Scale ticket not found.

These strings come from the owner function and are the messages a client can receive. They are also the cheapest way to tell a rejected request from a broken one.