Solution · Dynamics NAV / BC → S/4HANA
From Dynamics NAV or Business Central to S/4HANA, with the mapping drafted by AI and approved by you.
Business Central keeps one database per company, tells customers and vendors apart by table, derives accounts from Posting Groups and carries analytics in Dimensions. S/4HANA wants one client with company codes, Business Partners with roles, explicit account determination and cost objects. The eight steps of vise DMW close that gap — and this is the direction our first production FieldMap customer is taking today.
- Since 2017
- in production at a global brewing group
- 8 steps
- extract to report, one platform
- 0
- direct database writes into S/4HANA
01
What usually goes wrong.
02 · How it runs in vise DMW
The same discipline at every step.
- Steps 1–4 · Extract, scope, validate, profile
Extract per company, validate against the S/4 rule set.
Customer, Vendor, Contact, Item, Item Variant, Unit of Measure, Dimension and Posting Group tables extracted per company — from the SQL database, from the API or from Excel exports — and scoped to the wave. Validation rules check what S/4HANA will reject: missing countries and VAT numbers, units without conversion, duplicates across Customer, Vendor and Contact, Posting Groups with no target account. A DQ scorecard per company shows the readiness trend.
Readiness by dimension and object - Step 5 · Field Map
AI drafts Customer + Vendor + Contact → Business Partner. Your consultant approves every line.
vise FieldMap reads the Business Central table metadata and the S/4 target structure and proposes field pairs with transformation rules and a confidence score: No. to BP number range, Posting Group to reconciliation account, Dimension values to cost objects, Item category and Base Unit to material type and base UoM. The target-driven view shows every mandatory S/4 field as mapped, defaulted, manual-load or unresolved. This is the work running at our first FieldMap production customer.
Target-driven view — every mandatory S/4 field accounted for (demo data) - Step 6 · Value Map
Code tables become S/4 value lists — once, by the people who own them.
Payment Terms, Countries/Regions, Units of Measure, Item Categories, Salesperson codes, Shipment Methods, Posting Groups: each list is loaded into vise LoV-MAP and mapped to the S/4 value list by its business owner, approved once and reused for every company. Dictionaries feed validation, so an unmapped code is caught before the load.
Value mapping in vise LoV-MAP (demo data) - Step 7 · Load simulation
Dry-run through the real S/4 interfaces.
Business Partner through the BP APIs and CVI, materials through the standard BAPIs, finance through IDoc or OData — the same path the real load takes. Errors come back per record with the S/4 message; they go to the correction queue; the simulation is repeated until clean. Change mode updates what already exists instead of reloading everything, which matters when deliveries run across DEV, QA, UAT and PROD.
Screens for this step come from the migration demo. Ask for a walkthrough, or see it on your own object in the 30-day PoC. - Step 8 · Report
Reconciliation from BC record to S/4 record.
What was extracted from which company, what was transformed by which rule, what was posted, what failed and why — per object, per company, per run. Plus the weekly summary the programme manager has been sending since step 1.
Cleansing progress per company
03 · 30-day proof of concept
What you have after 30 days.
- One object — Customer + Vendor into Business Partner, or Item into Material — extracted, profiled, validated, field-mapped and value-mapped to S/4HANA
- A load simulation against your S/4 system (or your load tool) with the error list and the fixes
- The decision record: Posting Groups, Dimensions and No. Series mapped to S/4 structures, with owner and date
- An effort estimate for the full move, by object and company
In production
SAP → Navision, now Business Central → S/4HANA Karlsberg Customer and BOM data cleansed, deduplicated and transformed for the Navision move by one specialist instead of five; rules from the German entity reused for the French one. Today: the first production customer of vise FieldMap, mapping material data for the move to S/4HANA. Read more Rollout waves since 2017 Global brewing group vise DMW as the data readiness gate in front of every SAP rollout across the group’s operating companies, and vise Data Run for the everyday changes after go-live. Read more- 01NAV 2009, NAV 2018 or Business Central online — does it matter?
- For the data, no: Customer, Vendor, Contact, Item, Dimension and Posting Group structures have been stable across versions. For extraction, slightly: on-premise versions we read from SQL or from exports; Business Central online through its API or Excel exports. No agent inside Business Central is needed.
- 02How do you get one Business Partner out of a customer, a vendor and a contact?
- DMW profiles the three tables on VAT number, name and address, proposes one BP per match with the customer and vendor roles, and flags the disagreements (different names, countries, VAT numbers) for a decision. The rule is recorded with an owner — not applied silently.
- 03We are going the other way, SAP to Business Central.
- Same steps, target structure of Business Central. That was the original Karlsberg project; see the SAP ↔ Business Central page.
- 04What about SAP Migration Cockpit?
- Use it if it fits. DMW adds change mode, load simulation, rule-based validation and a correction loop for business users — and can feed the Cockpit or BODS with the mapped, validated data instead of loading itself.
Start with Customer and Vendor, in 30 days.
We extract them from one Business Central company, validate against S/4 rules, draft the Business Partner mapping with FieldMap and simulate the load — and you see what the full move will take.