Start from facts, not workshops
OnCoor IDN catalogs every source system and file, then builds the program scope, object inventory and field-level lineage from that metadata. Plans and budgets come from what the systems contain, not from workshop estimates, and nothing is rebuilt for the next mock cycle.
| The project way | Scope and mappings built in workshops and kept in spreadsheets. |
| The IDN way | Every source cataloged; scope, inventory and lineage built from metadata and reused every cycle. |
The problem
Most migrations start with workshops. Teams list the systems, tables and files they remember, put them in spreadsheets, and estimate from there. Something is always missed, and a source found late means new mapping work and a re-plan with the implementation partner.
How IDN does it
- Catalog: connect ECC, legacy systems and files; IDN reads their metadata and builds a searchable catalog.
- Profile: see the size and condition of each object before anyone maps a field.
- Scope and inventory: build the program scope and object inventory from the catalog, with an owner for each object.
- Lineage: every target field can be traced back to its source field and the rule that changed it.
- Reuse: the catalog, scope and lineage carry into every mock cycle instead of being rebuilt.
What it means for the program
Plans and budgets are based on evidence. Fewer surprises reach the test cycles, and the knowledge stays in the platform when people move on.
Questions
How do you build a source data inventory for S/4HANA?
Connect the source systems (SAP ECC, legacy databases and files) to IDN's catalog. IDN reads their metadata and lists every table, field and object, so the inventory comes from the systems themselves rather than from memory. Each object is then given an owner in the object inventory.
What is metadata-driven data migration?
It means the migration is planned and run from a catalog of what the source and target systems contain. Scope, mappings, rules and lineage are all tied to that catalog, so they can be traced, reviewed and reused in every cycle.
How much historical data should we migrate?
Only what the business needs. IDN lets you set relevancy rules in the scope, such as open items and a fixed number of years of history, and records the rule so the decision is visible and repeatable.