Skip to content

GET /oms/inbound-orders/options

OMS > oms.inbound-order

What it does

/oms/inbound-orders/options accepts GET and is declared in app/systems/OMS/inbound-order/api_routes.php:112 as a path.

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

Call chain:

  1. → purchase_order_options() — app/systems/OMS/inbound-order/query_helper.php:428
  2. ↳ commercial_order_options_for_type() — app/systems/OMS/inbound-order/query_helper.php:66

Who calls it

Called from:

  • public/assets/js/modules/shared/mk-inbound-order-editor.js
  • public/assets/js/modules/yms/scale-portal.js

A caller is the strongest available evidence of the intended use.

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
COMMERCIAL_ORDERS
COMPANIES
ITEM_STATUSES
ORDER_CLOSE_STATUSES
ORDER_STATUSES
PURCHASE_ITEM_OPERATIONAL_STATUSES
PURCHASE_OPERATIONAL_STATUSES

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

Data

Tables reached from the owner function:

  • T_COMPANY

Access

  • module-gated on oms.inbound-order, so tenant module access applies