Skip to content

PATCH /tms/transloads/(?P\d+)/scale-ticket

TMS > tms.transload

What it does

#^/tms/transloads/(?P<id>\d+)/scale-ticket$# accepts PATCH and is declared in app/systems/TMS/transload/api_routes.php:299 as a regex pattern.

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

Call chain:

  1. → tmsTransloadApiLinkScaleTicket() — app/systems/TMS/transload/form_mutation_api_helper.php:136
  2. ↳ tmsTransloadApiRowNotFoundMessage() — app/systems/TMS/transload/form_mutation_api_helper.php:131

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
body INITIAL_COMMODITY_WEIGHT
body SCALE_TICKET_ID

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

Output

Key
ID
SCALE_TICKET_ID

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

SQL executed

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

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

Data

Tables reached from the owner function:

  • T_SCALE_TICKET
  • T_TRANSLOAD

Access

  • module-gated on tms.transload, so tenant module access applies

Validation and failure messages

  • Transload id is required.
  • Scale ticket id is required.
  • 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.