Skip to content

GET /wms/inventory/bale-adjustments

WMS > wms.inventory

What it does

/wms/inventory/bale-adjustments accepts GET and is declared in app/systems/WMS/inventory/api_routes.php:699 as a path.

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

Call chain:

  1. → wmsInventoryBaleQueue() — app/systems/WMS/inventory/bale_adjustment_helper.php:963
  2. ↳ wmsInventoryBaleClientId() — app/systems/WMS/inventory/bale_adjustment_helper.php:7

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

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.

Data

Tables reached from the owner function:

  • T_COMPANY
  • T_TRANSLOAD

Access

  • module-gated on wms.inventory, so tenant module access applies

Validation and failure messages

  • Client context 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.