Every build, planned from one run.
Manufacturing and MRP software plans materials, explodes bills of materials and converts planned orders to purchase orders, transfers and work orders on SAP B1.
- ITEM
- Bread 400g (FG)
- GROSS REQ
- 1,000
- ON-HAND
- 200
- NET
- 800
- PLANNED ORDER
- → WORK ORDER
- ITEM
- Flour (RM)
- GROSS REQ
- 800
- ON-HAND
- 100
- NET
- 700
- PLANNED ORDER
- → PURCHASE
- ITEM
- Yeast (RM)
- GROSS REQ
- 40
- ON-HAND
- 5
- NET
- 35
- PLANNED ORDER
- → PURCHASE
MRP / manufacturing & production
Katana · Fishbowl · MRPeasy · Odoo MRP
A full netting MRP run — gross requirements netted against on-hand, and planned orders converted straight to POs, work orders and transfers — under the same house that runs your inventory and procurement.
| ITEM | GROSS | ON-HAND | NET | ORDER |
|---|---|---|---|---|
| Bread 400g (FG) | 1,000 | 200 | 800 | → work order |
| Flour (RM) | 800 | 100 | 700 | → purchase |
| Yeast (RM) | 40 | 5 | 35 | → purchase |
| 3 items | netted | 3 planned |
Gross to net, in one run.
The runDemand forecasts and orders drive a netting MRP run — low-level-code sequencing, gross requirements, scheduled receipts and planning buckets — that nets each item against on-hand and raises a planned order for the shortfall, nothing more.
planned WO-7701 × 800 raised by the MRP run
released material issued backflush on completion
closed received to stock finished goods on the ledger
BOM to a closed work order.
The buildA planned order becomes a work order that follows the SAP B1 lifecycle — Planned, Released, Closed — issuing components (or backflushing them on completion) and receiving the finished good back to stock, all on the same ledger.
| SIGNAL | TRACE | STATE |
|---|---|---|
| Pegging | WO-7701 → forecast SF-88 | TRACED |
| Exception | Yeast lead-time 7d | FLAGGED |
| Recommendation | planned → PO conversion | READY |
| 3 signals | surfaced |
Pegged, and explained.
TracedEvery planned supply pegs back to the demand it satisfies, and exceptions — a long lead-time, a late receipt — are surfaced as messages, not discovered on the shop floor. The plan explains itself.
Everything in the manufacturing line.
In this line| BOM Management | Live | Multi-level bills of material for explosion. |
| Production / Work Orders | Live | SAP B1 Planned/Released/Closed lifecycle. |
| Material Issue / Backflush | Live | Component consumption to work orders. |
| Receipt from Production | Live | Finished goods back to stock. |
| MRP Engine | Live | Netting, low-level-code, planning buckets. |
| Demand Forecasting | Live | Manual + auto forecasts feeding the run. |
| MRP Recommendations & Conversion | Live | Planned orders to PO/WO/transfer. |
| Pegging & Exception Management | Live | Demand-to-supply pegging, exceptions. |
| Order Policy / Lot-Sizing | Live | Reorder policy per item. |
| Resources & Capacity | Live | Work centres and capacity for the run. |
| Production Reporting | Live | Order and MRP-run reporting. |
| Costing / WIP-variance | Designed | WIP variance wizards. |
| In-process Quality Control | Designed | Shop-floor QC checkpoints. |
The same house that posts 1.66M+ distribution invoices runs manufacturing — the MRP run, the work orders and the receipts all on one ledger discipline, so the plan and the stock never disagree.
Manufacturing is a Leysco100-family product; on Leysco Akili it is on the roadmap.
- run a netting MRP from forecasts and orders, not a manual reorder
- explode multi-level BOMs and raise planned orders for the shortfall
- run work orders on a Planned/Released/Closed lifecycle with backflush
- peg every supply to its demand and surface exceptions early
A production plan on a whiteboard and a shortage found on the line → one netting run, planned orders raised, pegged and explained
Part of the house.
RelatedInventory
Where components and finished goods post.
LiveProcurement
Where the planned POs are raised.
LiveDistribution
Where the finished goods ship.
LiveDelivering live production systems since 2017.