At a glance
Requirements catalogue, also for public tenders.
SAP side: nothing is installed on the SAP system, only data extracts (DART/GoBD).
Odoo side: the app “SAP Migration” is your team's workbench; accounting approves every account mapping.
Waves reconciled against the trial balance, parallel run, go-live.
What the check looks like in the Odoo app “SAP Migration”
Nothing is installed on the SAP system. The extracts land in the Odoo app “SAP Migration”, your team's workbench: there it sees every delivered table and column before anything is imported.
- 1
Step 1 · SAP extracts
Inside the Odoo app: the SAP tables of a delivery by area, each with source table and meaning in plain language.
Tables by area: accounting, fixed assets, controlling, logistics, business partners.The SAP source table behind each table of the delivery.The meaning of each table in plain language. - 2
Step 2 · Mapping and status
Each table shows its columns with role and meaning and moves through a status: in preparation, ready to import, imported, reconciled or not imported.
Status per table, from preparation to reconciliation.Every column with SAP label, role and meaning.Check status per column. - 3
Step 3 · Column check
Column check: what SAP says about the column, what it means, what it looks like in the last delivery and what it joins in SAP. Then it is marked checked or not needed.
What SAP says and what it means: type, length, role, meaning.How the column joins other SAP tables.Mark the column as checked or not needed.
Screenshots from the Odoo app SAP Migration; delivery data is blurred. Tap the numbers for details, click an image to enlarge.
Simplify-ERP replaces SAP ECC with Odoo: a requirements catalogue (including for public tenders), data transfer from SAP extracts in waves reconciled against the trial balance, a parallel run and go-live. The data transfer uses Slyy Migrate: every account mapping is a proposal an accountant approves, and a reconciliation report sits between the waves.
Details
How the move runs
Requirements catalogue
The requirements for the new ERP are written up as a catalogue, also as the basis for public tenders.
Data transfer in waves
Data from SAP extracts moves in waves: configuration, master data, documents. A reconciliation report sits between the waves.
Parallel run
During the parallel run the SAP data import is reconciled against the trial balance every month.
Tests and go-live
After tests and reconciliation the company continues its work in Odoo.
Tooling from Slyy Migrate
The data transfer runs on Slyy Migrate, a product of our sister brand Slyy. It works from SAP extracts; no access to the running SAP system is needed.
DART/GoBD extracts
SAP asset register, business partners and DART/GoBD extracts are transferred into Odoo 18 over JSON-RPC; nothing is installed on the SAP system.
Approved account mapping
Every account mapping is a proposal an accountant approves; unapproved mappings block the load.
Findings instead of aborts
Defective rows of an extract are collected as findings instead of stopping the run.
One workspace per migration
Extracts, settings, mapping proposals and reports are kept together in one workspace.
Ongoing data from line-of-business systems
Payroll journal
The monthly payroll journal is imported into Odoo from the SAP text export.
Terminals and payment providers
Sales data from ticket terminals and payment-provider settlements are staged and booked in Odoo.
Key facts
- Source system
- SAP ECC
- Data source
- SAP extracts (DART/GoBD)
- Order of waves
- Configuration, master data, documents
- Check
- Reconciliation against the trial balance
FAQ
Frequently asked questions
How does the data get from SAP into Odoo?
Who decides how SAP accounts map to Odoo accounts?
How is it checked that the figures match during the parallel run?
Is the approach suitable for public tenders?
Questions about your project?
Talk your starting point through with us.
Free 30 min -- no obligation
