GET /tms/loading-planner/(?P\d+)

TMS > tms.transload

What it does

#^/tms/loading-planner/(?P<id>\d+)$# accepts GET and is declared in app/systems/TMS/transload/api_routes.php:389 as a regex pattern.

The route handler delegates to tmsTransloadApiLoadingPlannerRead(). 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

The response is produced by a shared helper, so the key set is not visible at the route. Read the owner function to confirm the shape before writing a client.

SQL executed

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

Data

Tables reached from the owner function:

• T_LOADING_PLANNER

Access

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

Validation and failure messages

• Planner id is required.
• Planner row 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.