oms.trade-summary¶
Gathers the trades for one piece of equipment. deal-ledger is the per-shipment ledger and trade-summary is its roll-up, and the same equipment has to be readable from both sides.
4 endpoints - system oms - module gate applies
What this module covers - Equipment and the trades that touched it.
Endpoints¶
| Method | Path | What it does | Evidence |
|---|---|---|---|
| GET | /oms/deal-ledger |
List the deal ledger - the trades gathered per piece of equipment | handled by an inline closure in the route table |
| GET | /oms/deal-ledger/(?P<equipmentId>\d+) |
Read the deal ledger of one piece of equipment in detail | handled by an inline closure in the route table |
| GET | /oms/trade-summary |
List the trade summaries | handled by an inline closure in the route table · calls api_catalog.php, mk-trade-summary.php |
| GET | /oms/trade-summary/(?P<equipmentId>\d+) |
Read the trade summary of one piece of equipment in detail | handled by an inline closure in the route table |
The description is a summary read off the route path, the handler, the tables it reaches and the screens that call it. Nothing is guessed without evidence: where the handler has to be read, it says so. The full evidence is on each endpoint page.