# AI on SAP Business One for Chemical Manufacturers: Formulas, Batches and Safety Data in One Place

> Source: https://netray.co/erp-ai/sap-business-one-chemicals-ai
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: AI for ERP

## Short answer

AI for SAP Business One in a chemical company connects a private model to batch, formula and inventory data so formulators, QA and logistics can ask about lot attributes, formula costs, hazard classes and expiry in plain English. It reads Business One through the Service Layer and read-only views, retrieves SDS and REACH documents, and runs on-prem so formulations stay confidential.

## Kind

industry

## Erp Family

sap

## Erp Products

- SAP Business One

## Industries

- Chemicals
- Specialty Chemicals
- Coatings

## Region

Global

## Persona

Plant Manager

## Eyebrow

SAP B1 + chemicals

## Intro

Chemical blenders, coatings makers and specialty formulators often choose Business One because it is affordable and covers finance, inventory and production for a mid-sized operation. But chemistry adds demands that general ERP screens handle only partly: formulas expressed in percentages, dual units of measure (kilograms and litres through density), potency or concentration adjustments, shelf-life dates and hazard classifications that drive how a drum can be stored or shipped.

Business One provides a production BOM (OITT, ITT1), batch master data with two free attribute fields plus manufacturing and expiry dates (OBTN), and warehouse-level quantities. What it lacks natively is a process-manufacturing layer: potency-based substitution, formula versioning with approvals, laboratory results against specification, and hazardous goods data. Companies close the gap with UDFs, add-ons, LIMS exports and spreadsheets.

The consequence is that crucial answers sit in different places. The formulator has the recipe in one file, QA has the certificate of analysis as a PDF, regulatory affairs holds the safety data sheet, and logistics has the dangerous goods classification in a freight forwarder portal. Anyone asking a cross-cutting question, such as which finished lots used a raw material whose SDS was just revised, has to assemble the picture manually.

This page explains how a private, read-only AI layer can connect those sources around Business One, where it genuinely saves time, and where it should stay out. Formulations are the core intellectual property of a chemical company, so keeping model and data on your own hardware is not a luxury here.

## Pain Points

### Formula cost is stale the day after you set it

**Detail:** Raw material prices change often, and the BOM cost in Business One is only as current as the last roll-up. Controllers rebuild margin views in Excel to see what a price change does to each formula.

### Lab results and ERP batches are separate worlds

**Detail:** Certificates of analysis, assay values and viscosity or pH results live in a LIMS, PDFs or spreadsheets. Linking a result to the Business One batch (OBTN) and checking it against specification is manual.

### SDS, REACH and CLP data is document-bound

**Detail:** Safety data sheets and registration information sit as files per supplier and product. Finding which products contain a substance of concern or an outdated SDS version means searching folders.

### Unit of measure and density conversions cause errors

**Detail:** Buying in kilograms, blending in litres and selling in drums creates conversion risk. Wrong density assumptions produce inventory variances that are hard to trace after the fact.

### Hazard and shipping data is not where planners look

**Detail:** UN numbers, packing groups and ADR or IMDG classes are held outside the item master or in UDFs of varying quality, so order release and carrier booking depend on tribal knowledge.

## Use Cases

### Formula where-used and impact analysis

**Description:** Ask which active formulas contain a raw material and what the cost impact is if its price rises. The agent walks multi-level BOMs and calculates impact per finished item.

**Erp Objects:** OITT, ITT1, OITM, OITW, OPCH/PCH1 latest prices, OPLN

**Outcome:** Price-change impact reviews take minutes; the controller still decides about repricing.

### Batch-to-lot genealogy

**Description:** From a finished lot, list the raw material lots, suppliers and production order. In reverse, from a supplier lot with a quality problem, list affected finished lots and customers.

**Erp Objects:** OBTN, OIBT, OITL/ITL1, OWOR, WOR1, ODLN, OCRD

**Outcome:** Faster containment decisions with a documented trace instead of manual reconstruction.

### Certificate of analysis matching

**Description:** Retrieval extracts assay and property values from CoA documents, compares them to item specifications held in UDFs or a spec document, and flags out-of-range lots for QA review.

**Erp Objects:** OBTN attributes, UDFs for spec limits, attachments, LIMS export tables

**Outcome:** QA reviews exceptions instead of reading every certificate; release remains a QA decision.

### SDS and substance lookup

**Description:** Natural-language search across safety data sheets for items containing a named substance, with Business One item codes and on-hand quantities returned.

**Erp Objects:** OITM, OITW, SDS document store, UDF CAS number fields

**Outcome:** Regulatory questions answered from a consistent index rather than ad hoc folder searches.

### Expiry and retest-date watchlist

**Description:** Lists batches approaching expiry or retest dates by warehouse, with open orders that could consume them first.

**Erp Objects:** OBTN.ExpDate, OBTQ, ORDR/RDR1, OWOR

**Outcome:** Fewer expired drums and better first-expired-first-out discipline, depending on date capture quality.

### Production variance by formula

**Description:** Compare theoretical formula consumption with actual issues per production order and highlight over-additions and yield loss by line or operator shift.

**Erp Objects:** OWOR, WOR1, OIGE, OIGN, OITT

**Outcome:** Targeted process reviews on the formulas that drift, rather than reviewing everything.

### Dangerous goods readiness check

**Description:** Before a sales order is shipped, check that each item has UN number, class and packing group captured and flag gaps.

**Erp Objects:** ORDR/RDR1, OITM UDFs, ODLN

**Outcome:** Missing shipping data found before the carrier does.

## Architecture

**Overview:** A private model and retrieval layer sit next to Business One. Structured questions go to curated read-only SQL views; document questions go to an index of SDS, CoA and specification files. The two are joined by item code and batch number, and every answer cites its sources.

**Layers:**

#### Structured data access

**Detail:** Read-only views on OITT, ITT1, OBTN, OIBT, OWOR, WOR1 and warehouse tables for SQL Server or SAP HANA; Service Layer for authorized document reads.

#### Document ingestion

**Detail:** Parsers for SDS, CoA and specification PDFs, with extracted fields (CAS number, assay, revision date) stored beside the text and linked to item code and batch.

#### Semantic layer

**Detail:** Plant vocabulary mapped to schema: formula, intermediate, concentrate, potency, retest date, UDF names for hazard and spec data.

#### Model serving

**Detail:** Open-weight model served with vLLM or Ollama on local GPUs, with deterministic calculation tools for cost roll-ups so arithmetic is not left to the model.

#### Governance

**Detail:** Role-based access to formulas, with finer restriction for crown-jewel recipes, full audit logging, and approval for any write.

## Deployment Options

### On-prem server in the plant or HQ

**Fit:** Formulators for whom recipes are the main trade secret

**Detail:** Everything, including document index and model, stays on the corporate network with no inbound or outbound internet requirement.

### Private cloud tenancy

**Fit:** Companies hosting Business One at a regional provider

**Detail:** Dedicated virtual network next to the SAP host; private endpoints only; customer-managed keys for storage.

### Air-gapped deployment

**Fit:** Defense, energetics or contract manufacturers under strict customer terms

**Detail:** Model weights and updates are delivered by controlled media; document ingestion happens inside the enclave.

## Compliance

### Retrieval surfaces substance and classification data from your documents. Registration and classification decisions stay with regulatory staff.

**Framework:** REACH and CLP (EU)

### Helps find inventory status notes and supplier statements already on file; it does not determine compliance status.

**Framework:** TSCA (US)

### Supports locating current SDS revisions and flagging items with missing or old sheets.

**Framework:** OSHA Hazard Communication and GHS

### Checks that required UN data is captured on items, while classification and documentation remain a trained dangerous-goods advisor task.

**Framework:** ADR, IMDG and 49 CFR shipping rules

### Records every answer and source, supporting document control; the AI is not a controlled record itself.

**Framework:** ISO 9001 and customer quality agreements

## Integration Notes

- Check that batch-managed items use the two attribute fields consistently, or move key properties into UDFs the semantic layer can read.
- Formula cost roll-ups should run in deterministic code or SQL, with the model only explaining the result.
- Handle dual UoM carefully: expose the UoM group (OUGP) and density UDF to the semantic layer so conversions are explicit.
- If a LIMS exists, take exports or a read-only API instead of querying its database directly.
- Restrict formula tables to named roles; use separate indexes for confidential formulations.
- Pin SDS documents by revision date so answers state which revision they used.

## Product Fit

### ERPray

**Why:** Grounded Q&A and read-only agents over formulas, batches and inventory with visible queries.

### DataRay

**Why:** Searching SDS, CoA and specification files and joining them to ERP data on-prem.

### Custom build

**Why:** Needed where LIMS integration, potency calculations or approval workflows are specific to your process.

## Engagement

### Assessment

**Duration:** 1-2 weeks

**Deliverables:**

- Formula and batch data review
- Document source inventory
- Confidentiality tiers for recipes
- Use case shortlist

### Pilot on formulas and batches

**Duration:** 4-5 weeks

**Deliverables:**

- Where-used and cost impact agent
- Batch genealogy trace
- Evaluation set with formulator input

### Document retrieval

**Duration:** 3-4 weeks

**Deliverables:**

- SDS and CoA index
- Spec comparison workflow
- Revision-aware citations

### Operate

**Duration:** 2 weeks plus ongoing

**Deliverables:**

- Runbook
- Access review
- Question quality dashboard

## Buyer Questions

- How are formulas isolated so only authorized roles can query them?
- Does cost roll-up use deterministic calculation or does the model do arithmetic?
- How are SDS revisions tracked and cited?
- What does the system do when density or UoM data is missing?
- Can it integrate with our LIMS read-only?
- Does anything leave our network during indexing or inference?
- How are answers evaluated against formulator expectations before go-live?

## Faq

### Can SAP Business One handle chemical formulas?

**Answer:** It supports multi-level production BOMs and batch management, which many blenders use successfully. It does not provide a full process-manufacturing layer with potency adjustment, formula approval or lab integration, so companies use UDFs, add-ons or separate systems. AI can help read across those sources, but it does not replace a missing formula-control process.

### Is it safe to put proprietary formulations in front of an AI model?

**Answer:** Only if the model runs where you control it. A private deployment keeps formulas on your own hardware, with role-based access and logging. Public cloud assistants are a different risk. We recommend separate indexes and tighter roles for crown-jewel recipes, and no use of your data to train shared models.

### Can AI read safety data sheets reliably?

**Answer:** It can extract fields such as CAS numbers, hazard statements and revision dates and answer questions with citations, but SDS formats vary and scanned documents need care. We evaluate extraction accuracy on your own sheets and keep the original document linked so a regulatory person can verify.

### Does this replace a LIMS?

**Answer:** No. A LIMS manages samples, methods and results. AI can read exported results or certificates and compare them to specifications in Business One, flagging exceptions for QA. Release decisions and lab records remain in your quality system.

### How does it deal with density and unit conversions?

**Answer:** Conversions are done by deterministic code using the unit-of-measure groups and density values in your item data, not by the model's own arithmetic. When density is missing, the agent says so instead of guessing, which also gives you a list of data to clean.

### What hardware is required?

**Answer:** A single GPU server with 24 to 48 GB memory handles a small team and a document index for a mid-sized chemical company. Larger document sets or many concurrent users need more. We size using your document count and expected users before you buy anything.

### Is SAP's own AI enough for a chemical company?

**Answer:** For generic assistance, possibly. Vendor AI generally does not know your formula structure, UDFs or document sets, and it runs through vendor cloud services. If your needs are simple and cloud use is acceptable, try it first. If recipe confidentiality or custom data matter, a private layer fits better.

## Search terms

SAP Business One chemicals, SAP B1 chemical industry, SAP Business One formula management, AI for chemical manufacturers ERP, SAP B1 batch attributes, SDS retrieval AI, SAP Business One REACH, on-prem AI chemical formulation, SAP Business One blending, chemical ERP AI private

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json