Supply Planning / MPS is where ERP discipline either begins or breaks.
Master Production Schedule (MPS) Generation and Firm-Zone Management looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Schedule attainment above 92%; unplanned MPS changes within firm zone below 5%; action message resolution rate above 85% within 48 hours
The control flow a finance team actually needs.
Step 1
Generate MPS For Up To 10,000...
Step 2
Enforce Configurable Firm And Trade-Off...
Step 3
Generate Action Messages With Financial...
Step 4
Maintain Side-By-Side Comparison Of...
Step 5
Require Senior-Planner Approval For...
The ERP surface involved.
Module
Supply Planning / MPS
Actors
Supply Planner, Production Scheduler, MPS Engine
Tier
Tier 2
Finance area
Supply Chain, Demand Planning & Logistics
Region lens
US and UK finance teams
Publication date
May 14, 2026
Generate MPS for up to 10,000 finished-good SKUs within 30 minutes; enforce configurable firm and trade-off zones; generate action messages with financial impact quantification; maintain side-by-side comparison of current vs. prior MPS version; require senior-planner approval for changes within the firm zone; auto-cascade accepted actions to MRP within 15 minutes
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Generate MPS for up to 10,000 finished-good SKUs within 30 minutes | Given an approved S&OP consensus plan, open customer orders, safety stock targets, and resource constraints |
| Control 2 | enforce configurable firm and trade-off zones | when the MPS engine generates a time-phased plan for finished-goods SKUs |
| Control 3 | generate action messages with financial impact quantification | then the firm zone (default 4 weeks) blocks automatic changes without senior-planner approval, action messages include financial impact, and accepted actions cascade to MRP within 15 minutes |
| Control 4 | maintain side-by-side comparison of current vs. prior MPS version | negative) when a planner attempts to change an MPS order within the firm zone without required approval then the system must return 403 FIRM_ZONE_CHANGE_REQUIRES_APPROVAL. |
| Control 5 | require senior-planner approval for changes within the firm zone | Schedule attainment above 92%; unplanned MPS changes within firm zone below 5%; action message resolution rate above 85% within 48 hours |
| Control 6 | auto-cascade accepted actions to MRP within 15 minutes | Schedule attainment above 92%; unplanned MPS changes within firm zone below 5%; action message resolution rate above 85% within 48 hours |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | The MPS engine reads the approved S&OP consensus plan, open customer orders, safety stock targets, and resource constraints to generate a time-phased production plan at finished-goods level. It respects a configurable firm zone (typically 4 weeks) during which no automatic changes are made without planner approval, and a trade-off zone where the system may suggest but not execute changes. Planners review MPS action messages (expedite, defer, cancel) and accept or reject each. Accepted actions update planned orders, which cascade to MRP for component requirements. The frozen MPS is published to the shop floor. |
| Control rules | Generate MPS for up to 10,000 finished-good SKUs within 30 minutes; enforce configurable firm and trade-off zones; generate action messages with financial impact quantification; maintain side-by-side comparison of current vs. prior MPS version; require senior-planner approval for changes within the firm zone; auto-cascade accepted actions to MRP within 15 minutes |
| Acceptance proof | Given an approved S&OP consensus plan, open customer orders, safety stock targets, and resource constraints; when the MPS engine generates a time-phased plan for finished-goods SKUs; then the firm zone (default 4 weeks) blocks automatic changes without senior-planner approval, action messages include financial impact, and accepted actions cascade to MRP within 15 minutes; (negative) when a planner attempts to change an MPS order within the firm zone without required approval then the system must return 403 FIRM_ZONE_CHANGE_REQUIRES_APPROVAL. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`mps_plan` { plan_id: string, generated_at: timestamp, horizon_end: date, status: enum(DRAFT/PUBLISHED/FROZEN), firm_zone_weeks: int, external_id: string }; `mps_order` { order_id: string, plan_id: string, sku_id: string, planned_date: date, quantity: int64, zone: enum(FIRM/TRADE_OFF/OPEN), status: enum(PLANNED/ACCEPTED/REJECTED/CHANGED) }; `mps_action_message` { message_id: string, order_id: string, action: enum(EXPEDITE/DEFER/CANCEL), financial_impact_minor: int64, financial_impact_currency_code: char(3) }; (reference, product may differ).API and events
`POST /v1/mps/runs` { consensus_plan_id, firm_zone_weeks } -> 202 { run_id }; `GET /v1/mps/runs/{run_id}/action-messages`; `PUT /v1/mps/orders/{order_id}/accept` -> 200; `PUT /v1/mps/orders/{order_id}/reject` { reason } -> 200; emits `mps.published` and `mps.order.accepted` events; idempotent via `external_id`.State transitions
`DRAFT -> PUBLISHED -> FROZEN`; order-level `PLANNED -> ACCEPTED | REJECTED`; firm-zone orders require senior-planner approval token before ACCEPTED; terminal `SUPERSEDED` when new MPS run publishes.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.