Skip to content

GET /wms/inventory/bale-sources/(?P[0-9a-fA-F-]{36})/ledger

WMS > wms.inventory

What it does

#^/wms/inventory/bale-sources/(?P<lotUuid>[0-9a-fA-F-]{36})/ledger$# accepts GET and is declared in app/systems/WMS/inventory/api_routes.php:820 as a regex pattern.

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

Call chain:

  1. → wmsInventoryBaleLedger() — app/systems/WMS/inventory/bale_adjustment_helper.php:1503
  2. ↳ wmsInventoryBaleFetchLot() — app/systems/WMS/inventory/bale_adjustment_helper.php:604
  3. ↳ 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

Where Key
path lotUuid

Request bodies must not use TYPE, ACTION or USERNAME as contract fields.

Output

Key
LOT
LOT_UUID

Success is { "data": …, "requestId": "…" }. Failure is { "error": { "code", "message" }, "requestId": "…" }.

Data

Tables reached from the owner function:

  • T_INVENTORY_LOT_LEDGER
  • T_TRANSLOAD

Access

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

Validation and failure messages

  • Lot ID or UUID is required.
  • Inventory lot not found or ID/UUID mismatch.
  • 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.