Operations leadership
Enterprise Operations Home
ERP master data
Vendor Master
Vendor profile, procurement, ledger, transaction, and risk readbacks through canonical trade-core routes.
FRONTEND_APP_ONLY
/erp/master-data/vendor-master
Active root: frontend/app. Forbidden root: frontend/src/app.
TRADE_CORE_READBACKS
0/4 safe responses
HTTP 403/401 is treated as protected readiness, not a broken page.
NO_BACKEND_ROUTE
codex502-master-data-governance-family-v1
No DB schema, helper export, auth, route, payout, or scheduler change.
Vendor list
Vendor identity is read from the existing ERP vendor list route.
PO linked
Procurement evidence remains tied to PR, PO, GRN, invoice, and ledger routes.
360 ready
Vendor 360 readbacks remain protected and read-only.
Governed Commands
Governance Proof
| Guard | Evidence | State |
|---|---|---|
| Frontend route | frontend/app/erp/master-data/vendor-master/page.tsx | ADDED |
| Backend owner | Existing /api/trade-core vendor routes | UNCHANGED |
| Duplicate API | No new vendor API family | PASS |
Smoke Contract
Page HTTP 200 or 307 is accepted. Page HTTP 500 is forbidden. API 403 remains a protected-ready readback state.