Skip to content

GET /tms/loading-planner/analysis

TMS > tms.transload

What it does

/tms/loading-planner/analysis accepts GET and is declared in app/systems/TMS/transload/api_routes.php:405 as a path.

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

Call chain:

  1. → tmsTransloadApiLoaderAnalysis() — app/systems/TMS/transload/planning_query_api_helper.php:623
  2. ↳ tmsTransloadApiSelectedDate() — app/systems/TMS/transload/planning_query_api_helper.php:412

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

No named input key is visible in the handler or its owner function. The endpoint either takes no parameters or reads them through a shared helper in app/shared/api/.

Output

Key
BREAK_SECONDS
CLOCK_IN_AT
CLOCK_OUT_AT
IDLE_SECONDS
LOADER_NAME
MISSING_CLOCK_IN
MISSING_CLOCK_OUT
MISSING_COMPLETE_COUNT
STAFF_USER_ID
SUGGESTED_CLOCK_IN_AT
SUGGESTED_CLOCK_OUT_AT
TOTAL_JOBS
TOTAL_SHIFT_SECONDS
TRANSLOAD_SECONDS
UNLOAD_SECONDS
UTILIZATION_PCT

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