Excel Mass Data Import and Update Workbench

A supplier sends a new price file with four thousand lines. A category manager needs three hundred items reclassified before month end. An acquisition brings in nine hundred business partners with their own payment terms and tax codes. In SAP Business One all of this is technically possible, and in practice it consumes days: someone maps columns by hand, runs a load, watches it fail on row 1,742 because a tax code does not exist, and then has to work out which of the preceding 1,741 rows actually went in. The standard data transfer tooling and the import-from-Excel option are adequate for a clean, one-off load. They are a poor fit for the messy, repeated, partially-correct spreadsheets that real operations produce every week.

This workbench is built for that reality: bulk create and bulk update, with validation before anything touches the database, a dry run that reports exactly what would change, and a rollback path when a load goes wrong anyway.

What ECOSIRE builds for you

This is a build-to-order engagement. We build the workbench against your company database, your document series, your user-defined fields and your approval procedures, then install it for you. There is nothing to download and nothing pre-built waiting on a shelf.

During scoping we agree the object set you need. Typical scope covers Items (OITM) with warehouse rows (OITW), unit of measure groups and item properties; Business Partners (OCRD) with addresses (CRD1) and contact persons (OCPR); price lists and price list lines, special prices for business partners and period and volume discounts; and marketing documents such as Sales Orders (ORDR/RDR1), A/R Invoices (OINV/INV1), Purchase Orders and A/P Invoices, along with Journal Entries (OJDT/JDT1) where opening balances or recurring postings are in scope. User-defined fields on any of those objects, and rows in user-defined tables (UDTs), are handled as first-class columns rather than as an afterthought.

All writes go through the DI API or the Service Layer, never through direct SQL inserts into SAP Business One tables. That matters: it means system numbering, document series, tax determination, stock posting and your approval procedures all behave exactly as they do when a user keys the document by hand. A workbench that writes rows directly would be faster and would quietly corrupt your ledger.

Validation before anything is written

Each import profile you define carries a validation ruleset. Before a load runs, every row is checked against your live master data: does the item code exist for an update, or does it collide for a create; is the business partner group valid; does the tax code exist and is it allowed for that partner; is the warehouse active; is the price list line consistent with its currency; are mandatory UDFs populated; do dates fall inside an open posting period.

The dry run produces a per-row report that separates rows into create, update, unchanged and error, and for update rows it shows the before and after value of each field that would change. Nothing is written during a dry run. Users fix the spreadsheet, re-run, and only commit when the report is clean — or deliberately commit a partial load with the failing rows excluded and exported to a correction file.

Rollback, batching and audit

Committed loads are recorded as a batch with its own identifier, the source file name, the user, the timestamp and the row-level outcome. For master data updates the workbench captures the prior field values so a batch can be reversed, restoring the previous state where no other change has intervened. For marketing documents, reversal follows SAP Business One rules — cancellation or credit memo as appropriate — rather than pretending a posted document can be deleted, and the workbench tells you which is which before you commit.

Large files are processed in configurable batches with a progress indicator and a resumable position, so a ten-thousand-row price update does not have to succeed or fail as a single all-or-nothing operation. Every batch report exports to Excel for your audit file.

Who it is for

Operations and master data teams who maintain item and partner data as a routine job rather than a project. Purchasing and pricing teams who receive supplier price files on a fixed cycle. Finance teams loading opening balances or recurring journals. Implementation consultants who need repeatable, reviewable loads during a go-live rather than a one-shot migration.

How delivery works

1. Scoping call. We review the objects you load, sample spreadsheets you actually receive, your UDFs, your document series and numbering, your approval procedures and your posting period rules. We confirm your SAP Business One version, database platform and hosting. 2. Fixed quote. You receive a written scope and fixed price before any build work starts. Additional objects or profiles later are requoted openly. 3. Build. We develop the import profiles, the validation rulesets, the dry-run reporting and the rollback capture against a copy of your data or a representative test company. 4. Install into test. The workbench is installed into your test company database and run against your real spreadsheets until the validation rules match how your team actually works. 5. Production. After sign-off we install into production, configure user permissions on the workbench itself, and hand over documentation. 6. Support window. A defined support period follows go-live for defect fixes and profile adjustments, with an optional ongoing agreement afterwards.

Typical lead time from signed quote to production install is one working week, depending on how many objects and profiles are in scope.

What this workbench is not

It is not a data cleansing service — it validates and reports, it does not decide what your correct data should be. It is not a replacement for a full migration project when you are moving from another system, though it is frequently used alongside one. And it does not bypass SAP Business One business logic to make a load succeed: if a document would not post when keyed by hand, the workbench will not force it in.