ERP Integrator · for desktop applications
Connect your own Windows application to SAP Business One. Hand ERP Integrator your rows and it creates or updates the items and the bills of materials through the Service Layer, with the field mapping, company rules and status window our CAD and PDM integrations use.
One engine, every application
Every integration on this site, from Autodesk Vault and SOLIDWORKS PDM to Excel, runs on the same engine: ERP Integrator. It connects to SAP Business One, maps each property to its field, applies your company rules, creates or updates the items and bills of materials and reports the result of every one.
Your own desktop application can use it the same way. A product configurator, a quoting tool, an in-house engineering program or a simple import from a file: the application reads its data as it always has and hands it to ERP Integrator. What goes where in SAP Business One is kept in settings, so it can change without a new release of your program.
A .NET 8 program references the engine and calls one send with its rows.
Items and the bill of materials of each parent, through the Service Layer.
Send again: changed items are updated, unchanged ones skipped, no duplicates.
Business Central, Dynamics 365 F&O, SAP S/4HANA, SAP Business One and Odoo.
Video
The demo application reads items from a CSV file. ERP Integrator does the rest: it creates the items and the bill of materials in SAP Business One, and when the file changes, it updates only what changed.
How it works
Your application
The demo is a small Windows application that reads items from a CSV file: the item number, the description, the parent item and the quantity. The blue columns are the ones that go to SAP Business One; the material stays in the file.
Send
Send to SAP Business One hands the rows to ERP Integrator. It connects to the Service Layer, checks which items already exist, creates the six items and builds the bill of materials of the pump assembly with its five lines. Every item is reported in the status window, and the result comes back to the application's own grid.
// 1. The engine, for SAP Business One, with the ERP Integrator settings
var engine = new ERPIntegrator.Class1("SAP Business One", "sb1",
WriteLog, null, UpdateStatus, null, dependencies,
settings, GetProperty, logfile, SaveSettings, ...);
// 2. Your data: one row per item, and the BOM lines of each parent
items["CSV-SB1-3004"] = new() { ["No"] = "CSV-SB1-3004",
["Description"] = "Shaft seal kit" };
bom["CSV-SB1-3000"].Add(new() { ["No"] = "CSV-SB1-3004",
["Quantity_per"] = "2" });
// 3. Send: ERP Integrator maps, creates or updates, and reports each item
engine.SendtoERP(ref message, ref ok, ..., ref items, ref bom,
..., ref keyColumn, null);For developers
Create the engine for SAP Business One with your settings, hand it the rows and the bill of materials lines, and call send on a worker thread. The engine calls back for a property of an item, for the result of each item and for the log.
Send again
When the data changes, just send again. In the demo's second file one description and one quantity have changed: only the pump housing is updated, the unchanged items are reported as Update skipped, and the bill of materials gets the new quantity. No duplicates.
Result in SAP Business One
In SAP Business One the six items are there with their descriptions, and the bill of materials of the pump assembly lists its five lines, with four seal kits, exactly as in the file.
Rules and AI
The field mapping decides which property fills which SAP Business One field and holds fixed values such as the item group. Rules that go further, such as Buy or Make depending on the description, live in a macro that ERP Integrator runs before every send. The AI Macro Generator writes that macro from a plain-language request, checks that it compiles and previews the result before anything is sent. The picture shows it in Autodesk Vault; the macro works the same for every application on the engine.
Related integrations
If your data lives in one of these applications, the SAP Business One integration already exists. The engine also sends to Business Central, Dynamics 365 Finance and Operations, SAP S/4HANA and Odoo.
FAQ
Any 64-bit Windows application on .NET 8, written in C#, VB.NET or C++/CLI. It references the ERP Integrator assemblies, gives the engine its data as rows of property names and values, and calls the send. The CAD and PDM integrations on this site are built the same way, for example Autodesk Vault, SOLIDWORKS PDM and Excel to SAP Business One.
Through the SAP Business One Service Layer. The connection, the company and the field mapping are kept in the ERP Integrator settings, the same settings the other integrations use.
Yes. Besides the items, the application passes the bill of materials lines of each parent item, and ERP Integrator creates or updates the bill of materials in SAP Business One. On a resend, unchanged items are skipped and changed lines are updated, without duplicates.
The settings, not your code. The field mapping says which property of your data fills which field and holds fixed values; rules that go further are written in a macro, which the AI Macro Generator can write from a plain-language request.
Yes. The same engine and the same calls send to Business Central, Dynamics 365 Finance and Operations, SAP S/4HANA and Odoo; the ERP is named when the engine is created. See also ERP Integrator for Business Central and ERP Integrator for SAP S/4HANA Cloud.
Tell us what your application holds and which SAP Business One records it should create. We will show ERP Integrator sending your own data and help you set up the first integration. Or write to us with your SAP Business One version and the fields you fill by hand today.