Zero-Error Data Transfer Workbench (DTW): Migrating Business Partners & Open Balances
Avoid the notorious "Internal Error (-5002)" and currency mapping failures during go-live cutovers. Includes our proven import sequence, CSV column rules, and post-import SQL audit.
SAP B1 Academy Editorial
Published • 11 min read
A clean go-live in SAP Business One depends heavily on how cleanly legacy data is imported through the Data Transfer Workbench (DTW). Even experienced consultants lose hours troubleshooting cryptic DI API error codes when parent-child CSV templates are misaligned.
Mandatory Import Sequence
Never import open A/R or A/P invoices before locking down your master data dependencies in this exact order:
- Chart of Accounts & G/L Account Determination
- Payment Terms, Price Lists & Warehouse Codes
- Business Partner master data (
OCRD+CRD1addresses +OCPRcontacts) - Item master data (
OITM) and opening stock via Inventory Opening Balance - Open A/R and A/P documents, then G/L opening balances
Preparing the CSV Templates
Every DTW template ships with two header rows: the first is the DI API field name (CardCode, CardName), the second is the database column name. DTW reads the first row only, so never delete or rename it.
- Keep
RecordKey(header) andParentKey(lines) aligned. Every address row inBPAddresses.csvmust reference an existingRecordKeyinBusinessPartners.csv. - Save as Unicode Text (tab-delimited) when names contain accented characters; plain CSV exports from Excel silently corrupt them.
- Use the code values, not descriptions, for enumerations —
cCustomer/cSupplierforCardType,bo_ShipTo/bo_BillToforAddressType.
Create a free account to unlock the full step-by-step guide & copy the production SQL script.
Join SAP Business One consultants and key users worldwide. Free forever, no credit card required.