Skip to content
Tutorials Center
My learning

Topics

Lesson 13 of 36 ยท ERP Modules

Manufacturing and MRP in Practice

See how the ERP manufacturing module is used day to day: maintaining BOMs and routings, running MRP, scheduling capacity, reporting production, handling scrap and measuring OEE.

The lesson on plan to produce described the process. This lesson looks at the manufacturing module as a tool: what master data you maintain, what the planner does each day, how capacity enters the picture and which numbers tell you whether the shop floor is healthy.

The product itself cannot run here, so we describe the typical functions and model them with Python stand-ins.

Master data you maintain

  • Item master (manufacturing view): make or buy, lead time, lot size, scrap factor, planning policy.
  • Bill of materials: with versions and effective dates so engineering changes apply from a date. Variants: production BOM, engineering BOM, phantom assemblies (grouped without being stocked).
  • Routing: operations, work centres, setup and run times.
  • Work centres: capacity per day, shifts, calendar, hourly cost rate.
Python BOM versions with effective dates

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The planner's day

MRP runs (often nightly) and produces planned orders and exception messages. A planner:

  1. Reviews messages: orders to expedite, delay, cancel or reschedule.
  2. Converts planned orders into production orders or purchase requisitions.
  3. Checks capacity and shifts work between machines or days.
  4. Releases orders to the floor and watches shortages (a component missing for an order).

Planner routine

Read messages Expedite, cancel
Convert Planned to real orders
Check capacity Load versus available
Release Watch shortages
1 / 2

Capacity: load versus availability

MRP assumes infinite capacity. Capacity requirements planning (CRP) then compares the hours that orders need with the hours each work centre has.

Python Work-centre load check

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

When a day is overloaded the planner moves an order, adds overtime or subcontracts.

Reporting production

Operators confirm operations (quantity good, scrap, time). Confirmations trigger backflushing: components are consumed automatically in proportion to the quantity reported rather than issued by hand. Finished goods are then received into stock. Variances arise when actual material, time or price differs from standard.

Python Backflush with scrap

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Scrap, yield and rework

Scrap is material lost; yield is good output divided by input. Planning adds a scrap factor so you start slightly more than you need. Rework sends faulty items through extra operations and is costed separately.

Overall equipment effectiveness (OEE)

OEE is a standard shop-floor KPI: Availability x Performance x Quality.

  • Availability: running time divided by planned time.
  • Performance: actual speed divided by ideal speed.
  • Quality: good units divided by total units.
Python Calculating OEE

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Integration points

Manufacturing links to inventory (components and goods), purchasing (requisitions from MRP), sales (demand), finance (work-in-progress valuation and variances) and quality management (inspections). Shop-floor machines may connect through a manufacturing execution system (MES) that feeds confirmations to the ERP.

Common pitfalls

  • Out-of-date BOMs after engineering changes.
  • Lead times set once and never reviewed.
  • Operators confirming late, so stock looks wrong.
  • Planners overriding MRP without recording why.

Many of these are people and process issues rather than software, which is why implementation and change management matter.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why have BOM effective dates?

    Effective dates select which BOM version is valid for production on a date.
  2. 2. What is backflushing?

    Components are deducted in proportion to the confirmed quantity instead of being issued manually.
  3. 3. OEE equals

    OEE multiplies the three loss factors.
  4. 4. Why check capacity after MRP?

    MRP calculates materials, not whether machines have enough hours.

Summary

  • Manufacturing master data: item planning data, versioned BOMs, routings and work centres.
  • Planners work from exception messages and convert planned orders into real ones.
  • Capacity checks catch overloads MRP cannot see.
  • Confirmations, backflushing, scrap and yield keep stock and cost accurate; OEE measures shop-floor performance.

Next: HR and Payroll Module