Skip to content

GET /tms/bookings/(?P\d+)/packing-list

TMS > tms.booking

What it does

#^/tms/bookings/(?P<id>\d+)/packing-list$# accepts GET and is declared in app/systems/TMS/booking/api_routes.php:1700 as a regex pattern.

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

Call chain:

  1. → packing_list() — app/addons/reports/query_helper.php:476
  2. ↳ reportCommonOrderItemWeightUom() — app/addons/reports/query_helper.php:19
  3. ↳ reportNormalizeWeightUom() — app/addons/reports/query_helper.php:14

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 OI.UOM, COUNT(*) AS ROW_COUNT

Data

Tables reached from the owner function:

  • T_EQUIPMENT
  • T_EQUIPMENT_LOAD
  • T_LOAD

Access

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