Skip to content

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

TMS > tms.transload

What it does

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

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

Call chain:

  1. → tmsTransloadApiLoadingPlannerDelete() — app/systems/TMS/transload/planning_command_api_helper.php:227
  2. ↳ yard_find_entity_location() — app/systems/YMS/yard-move/location_state_helper.php:550

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
path (read in handler) FORCE_DIP_CLEANUP
path (read in handler) forceDipCleanup

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 STATUS, UNLOAD_OUT_TIME, WAREHOUSE_LOCATION

SELECT ID,

SELECT LOCATION_CODE FROM T_YARD_LOCATION

Data

Tables reached from the owner function:

  • T_LOADING_PLANNER
  • T_TRANSLOAD

Access

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

Validation and failure messages

  • Planner id is required.
  • Planner row was not found.
  • This plan cannot be deleted from its current status.
  • Break queue rows cannot be deleted here.
  • This plan already has work time and cannot be deleted.

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.