PATCH /tms/transloads/(?P\d+)/load-label/warehouse-location¶
What it does¶
#^/tms/transloads/(?P<id>\d+)/load-label/warehouse-location$# accepts PATCH and is declared in app/systems/TMS/transload/api_routes.php:735 as a regex pattern.
The route handler delegates to tmsTransloadApiUpdateLoadLabelWarehouse(). That function is the owner of
this behaviour; the route entry is only dispatch.
Call chain:
- →
tmsTransloadApiUpdateLoadLabelWarehouse()—app/systems/TMS/transload/planning_query_api_helper.php:64 - ↳
shouldUseForkliftReadOnlyLabelPrint()—config/config.php:585 - ↳
isForkliftOperationalRoleSet()—config/config.php:564
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 |
WAREHOUSE_LOCATION |
Request bodies must not use TYPE, ACTION or USERNAME as contract fields.
Output¶
| Key |
|---|
PLACEMENT_ID |
TRANSLOAD_ID |
WAREHOUSE_LOCATION |
Success is { "data": …, "requestId": "…" }.
Failure is { "error": { "code", "message" }, "requestId": "…" }.
Data¶
No table reference is visible in the owner function body.
Access¶
- module-gated on
tms.transload, so tenant module access applies
Validation and failure messages¶
- Forklift loader label print access is read-only.
- TRANSLOAD_ID is required.
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.