DELETE /oms/outbound-orders/(?P\d+)/costs/(?P\d+)¶
What it does¶
#^/oms/outbound-orders/(?P<id>\d+)/costs/(?P<transactionId>\d+)$# accepts DELETE and is declared in app/systems/OMS/outbound-order/api_routes.php:164 as a regex pattern.
The route handler delegates to omsOutboundCostPostRoute(). That function is the owner of
this behaviour; the route entry is only dispatch.
Call chain:
- →
omsOutboundCostPostRoute()—app/systems/OMS/outbound-order/post_handler.php:104 - ↳
omsOutboundCostPostHandle()—app/systems/OMS/outbound-order/cost_helper.php:314 - ↳
oms_outbound_cost_save()—app/systems/OMS/outbound-order/cost_helper.php:325
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 |
path |
transactionId |
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.
Data¶
No table reference is visible in the owner function body.
Access¶
- module-gated on
oms.outbound-order, so tenant module access applies