GET /oms/customer-pos/(?P\d+)/items¶
What it does¶
#^/oms/customer-pos/(?P<id>\d+)/items$# accepts GET and is declared in app/systems/OMS/inbound-order/api_routes.php:313 as a regex pattern.
The route handler delegates to omsCustomerPoRow(). That function is the owner of
this behaviour; the route entry is only dispatch.
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 * FROM T_CUSTOMER_PO WHERE CLIENT_ID=? AND ID=? AND DELETED_AT IS NULL{$typeFilter} LIMIT 1
Data¶
Tables reached from the owner function:
T_CUSTOMER_PO
Access¶
- module-gated on
oms.inbound-order, so tenant module access applies
Validation and failure messages¶
- Customer PO not found.
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.