Demo Manufacturing Industries LLC: from demand to finished goods

This fictional demonstration shows how a manufacturer uses OSERP to keep material, production, quality, and finance connected. The example is intentionally complex: one legal company, two plants, a central warehouse, batch-controlled components, a multi-level BOM, subcontract processing, and a customer order in a foreign currency. It teaches the difference between a plan, a stock movement, a quality decision, and a posted accounting event.

Manufacturing context

Demo Manufacturing Industries LLC produces commercial refrigeration units. The UAE company has a Dubai plant and an Abu Dhabi assembly plant. Its base currency is AED, but a Kuwait customer orders in KWD. The central warehouse holds compressors, copper tubing, controllers, insulation, fasteners, and packaging. Finished units are serialised; copper and refrigerant are batch-controlled. The leading book is IFRS, with a management book for plant analytics.

The production manager begins with a confirmed sales order for 50 units. The order is a demand signal and may reserve finished stock; it does not consume components. The planning team checks available finished goods, open purchase orders, released production, safety stock, and quality hold. “On hand” alone is not a production plan.

Item and BOM masters

The finished item is RCU-500-S, description “500L commercial refrigeration unit”, UOM PCS, serial tracking enabled, and a default finished-goods warehouse. Its BOM version RCU-500-S-V3 contains:

Component	Quantity per unit	Control
Compressor CMP-500	1	Serial/batch supplier trace
Copper tubing CU-08	4.5 metres	Batch and UOM conversion
Controller CTRL-500	1	Revision compatibility
Insulation kit INS-500	1	Batch expiry
Fastener pack FAST-01	1	Pack-to-piece conversion
Packaging BOX-500	1	Consumption at pack stage

The BOM stores component item, quantity, UOM, scrap allowance, operation, effective dates, substitute policy, and revision. A consultant must ask whether the BOM is a design record, a costing recipe, or both. Changing a BOM version affects future work orders; it must not silently rewrite historical production.

Work order creation

The planner creates work order WO-DXB-260915-004 for 50 units, selects plant, warehouse, BOM version, routing, planned start/end, priority, customer/project reference, and production supervisor. The routing contains cut tubing, assemble cooling circuit, wire controller, insulation, pressure test, final assembly, and pack.

Header field	Example	Impact
Work order number	WO-DXB-260915-004	Traceable production identity
Finished item	RCU-500-S	Determines BOM and serial policy
Quantity planned	50 PCS	Drives component demand
BOM version	V3	Locks the recipe used
Plant / warehouse	Dubai / WH-DXB	Defines physical responsibility
Planned dates	15–20 Sep 2026	Scheduling and late-order reporting
Project / sales order	SO-KW-2201	Connects production to customer demand
Priority	Expedite	Controls queue order
Status	Draft → Released → In process → Complete	Controls allowed actions

The release check compares required components with available, reserved, on-order, and quarantined quantities. It should show shortages before material is issued. A shortage is a planning fact; creating a negative stock adjustment to make release pass destroys the evidence.

Material issue and batch genealogy

The stores user issues components to the work order. Each issue records item, quantity, UOM, source warehouse/bin, batch or serial, date, operator, and work order. If 225 metres of copper are required and 220 are issued, the work order keeps an open component quantity. The user may issue the remaining five later or use an approved substitute with a reason.

Batch genealogy answers two questions: “which supplier lots entered this finished serial?” and “which finished units contain this recalled lot?” The issue must therefore carry the actual batch, not just the item code. A batch in quality hold cannot be issued to production until released. The system’s batch and expiry fields are evidence, not decorative labels.

WIP, labour, and overhead

As operations complete, the supervisor records operation, start/end, good quantity, scrap quantity, rework quantity, labour time, machine time, operator, and reason codes. A time entry without a work order cannot explain the cost of a unit. Scrap must identify whether it was cutting loss, supplier defect, assembly damage, or test failure.

The costing policy may accumulate material, labour, and overhead in WIP and relieve it when finished goods are received. The GL Mapping template and stage matrix decide which events post. A work order reaching “in process” is not automatically a finished-goods receipt or a revenue event.

Quality inspection and quarantine

At pressure test, 48 units pass and two fail. The quality inspector records inspection plan, sample size, measurements, result, defect code, disposition, inspector, date, and attachments. Failed units go to quarantine or rework. They are not available for a customer delivery merely because a production quantity was reported.

The inspection result can trigger rework, scrap, supplier claim, or release. Each route has a different stock and cost effect. A consultant should test all four outcomes and trace the resulting warehouse balance, batch status, work-order quantity, and journal.

Finished-goods receipt

The plant receives 48 accepted units into finished-goods warehouse FG-DXB. Each serial number is recorded against the work order, batch genealogy, inspection result, manufacture date, and storage bin. Two failed units remain WIP/rework. The finished receipt should reconcile:

Planned                 50
Accepted finished       48
Rework                    2
Scrap                     0
Open production           0 (after rework decision)

The exact accounting event depends on configured costing: debit finished inventory and credit WIP, or another approved pattern. Never teach a journal without checking the company’s template and costing policy.

Customer delivery and KWD invoice

The sales order reserves 48 serials. Fulfilment selects the actual serials and confirms packing. Delivery records carrier, vehicle, destination, export evidence, and delivered serials. The invoice is raised in KWD with the approved dated KWD/AED rate and the customer’s payment terms. Revenue and output-tax treatment follow the tax regime; inventory and COGS follow the configured delivery/invoice stage.

The production and sales chains must remain linked: work order → serial → delivery → invoice. If a serial is delivered without an accepted inspection result, the control failed even if the invoice balances.

Variance and month-end close

The plant controller compares standard and actual material, labour, overhead, scrap, rework, and yield. Example:

Measure	Standard	Actual	Interpretation
Copper per unit	4.5 m	4.7 m	Usage variance to investigate
Labour per unit	2.0 h	2.3 h	Training or routing issue
First-pass yield	98%	96%	Quality trend requires action
Scrap value	AED 0	AED 4,200	Reason-coded loss
Finished units	50	48	Two units rework/open decision

At close, finance checks open work orders, unissued material, WIP age, quarantine, serial completeness, purchase accruals, subcontract invoices, production journals, sales delivery, and period status. A period lock prevents late posting; it does not fix an incomplete production close.

Consultant challenge

Repeat this case with: a component shortage, approved substitute, expired batch, failed quality sample, partial finished receipt, subcontract operation, work-order cancellation, production reversal, foreign-currency invoice, and locked-period attempt. For every test capture source document, stage, fields, stock movement, journal, approval, and report result. Label each behavior as product-supported, configured, policy-dependent, or extension-required.

Use this chapter with Inventory, Advanced GL Mapping, Sales lifecycle, and API Library. It is a training scenario, not a claim that every manufacturing capability is enabled in every tenant.