Process Manufacturing and Formula Management

The problem with discrete BOMs in a process plant

SAP Business One ships a Bill of Materials that assumes a discrete world: a fixed parent quantity, fixed component quantities, one output per production order. That model works for assembling a pump. It breaks the moment your production is a formula.

A chemical blender buys caustic soda at 48% and 32% assay from different suppliers. The formula calls for 100 kg of caustic on a 100% basis. The standard BOM has no idea that a 32% drum means you must charge 312.5 kg and pull 212.5 kg of water back out of the batch to keep the volume right. Somebody does that arithmetic on paper, keys the corrected quantity into the Production Order, and the standard cost variance report becomes fiction.

A cosmetics manufacturer runs a 500 kg batch of emulsion and gets 487 kg of sellable product, 9 kg of tank heel that is legitimately reworkable, and 4 kg of loss. SAP Business One's production order wants one Item as the output. The heel gets written off or quietly ignored, and the yield the plant manager reports to the board is not the yield in the ledger.

A food processor breaks a carcass, a fruit press run, or a distillation cut into three or four saleable streams from one input. Standard SAP Business One cannot express "this order produces Item A, Item B and Item C, and cost is apportioned across them" — the Receipt from Production posts one parent.

The result is the same in every plant: a spreadsheet becomes the real system of record for the formula, and SAP Business One becomes a place to post the invoice afterwards.

What ECOSIRE builds

ECOSIRE builds a process manufacturing layer as a native SAP Business One add-on. It does not replace the standard production module — it extends it so the objects your accountants and auditors already know (Production Orders, Inventory Transfers, Goods Issues, Goods Receipts, Journal Entries) remain the posting spine.

Formula master with potency and basis

We implement a Formula object as a UDO with header and line UDTs, holding the theoretical formula on a stated basis (100% active, per 1,000 kg, per batch, or per your own unit). Each component line carries an active-basis quantity, a target assay or potency, an allowable range, and a compensating item — the water, solvent or filler that absorbs the difference when the batch material you actually have on hand is stronger or weaker than nominal. Potency is read from a UDF on the Batch Number master, so the scaling uses the assay recorded at goods receipt or by your QC lab, not a guess.

Scaling and batch sizing

When you release a batch, the add-on scales the formula in three passes: size scaling from the theoretical basis to the ordered batch size; potency scaling per component against the specific batches allocated; and compensator rebalancing so the total charge still reconciles to the target mass or volume. The scaled result is written to the Production Order component lines through the DI API so standard issue, backflush and costing behave normally downstream.

Co-products, by-products and cost apportionment

A formula can declare multiple outputs with a type of co-product, by-product or waste. Co-products share the batch cost by a configurable rule — relative sales value, fixed percentage, weight or a manual split you enter at closure. By-products are credited at a standing value and reduce the cost of the main output. Waste streams are recorded in quantity for compliance reporting without carrying inventory value. All of it lands as ordinary Goods Receipts from production plus a balancing Journal Entry, so the General Ledger stays reconcilable line by line.

Yield and variance

The add-on records theoretical yield, actual yield and the difference at both batch and formula level, with reason codes on a UDT you control. Yield below or above a tolerance you configure raises an approval requirement before the order can be closed. Because the calculation is stored per batch, you can trend yield by formula, by line, by shift or by raw-material supplier lot rather than reading it off a monthly cost report.

Lab specifications and certificates of analysis

Specification templates hold the tests, methods, units, target values and pass ranges for a finished or intermediate item. Results are captured against the Batch Number, gate the batch's release status, and feed a Certificate of Analysis produced as a Crystal Report against the delivery or the batch. Retained-sample and shelf-life fields are carried on Batch UDFs so recall traceability follows the standard SAP Business One batch trail.

Where it plugs in

All master data and transaction reads and writes go through the SAP Business One Service Layer where the operation is a service call, and through the DI API where a business object needs the full transaction semantics. Screens are delivered inside the SAP Business One client with a browser-based companion for shop-floor and lab entry. Approval procedures use the standard SAP Business One approval framework so your existing authorisers and delegation rules apply.

Who this is for

Chemical and specialty-chemical blenders, cosmetics and personal-care manufacturers, food and beverage processors, nutraceutical and supplement producers, agrochemical formulators, and paint, coating and adhesive plants. It fits companies running SAP Business One as their financial system that have moved their formulas into spreadsheets because the standard BOM could not hold them.

How delivery works

Nothing here is pre-built. This is a build-to-order engagement.

1. Scoping call. We walk your actual formulas, your unit-of-measure conventions, your assay handling, and how you currently account for co-products. We look at your live SAP Business One configuration — version, patch level, database platform, existing add-ons and any prior UDF or UDO customisation that we must not disturb.

2. Fixed quote. You receive a written specification covering the formula model, the scaling rules, the costing apportionment method, the specification templates and the reports, with a fixed price and a delivery date. The listed price is the starting point; the quote reflects the scope you sign off.

3. Build. ECOSIRE develops the add-on against a copy of your company database so the field names, item groups and UDFs match your environment.

4. Install in test, then production. We install into your test company first, load real formulas, run parallel batches against your current spreadsheet, and reconcile the costing before anything touches production. Production installation happens on a date you choose, with a documented rollback.

5. Support. A support window follows go-live for defect correction and configuration adjustment, with an option to extend.

Typical lead time is one working week from signed quotation, depending on how many formula variants and costing rules are in scope.