Inside a real SAP ECC to S/4HANA conversion
This is OnCoor IDN running on a sample conversion that we move through real Build and Mock cycles in-house. It uses our own reference data (Customer, Product, Material BOM), never client data. Open Ask OnCoor to question it: every answer shows where it came from.
One workspace for the whole conversion
Every module of the migration in one place, with a running data readiness line at the top: what is in design, running, under investigation or resolved, and what needs you next.
Every object, step by step
Each object moves through Design, Run, Investigate and Resolve, with the next action named at the top. Diagnose, root causes and the change trail are one click away, and a preflight check runs before anything is generated.
Ask it anything about the conversion
Ask OnCoor is built into IDN. It answers from the platform’s own facts, shows the source of every line, and reads only what your role allows. The same engine powers Ask OnCoor on this site.
Questions people ask about the sample conversion
Why did the customer load lose rows?
In the sample conversion, a customer master data load wrote 1,603 of the 56,679 customer company-code records it should have. RCA found the cause on its own: dunning data, which most customers never have, had been set up as required, so every customer without it was dropped. RCA proposed one change, making that data optional. After the change and one re-run, all 56,679 records loaded.
What blocks sign-off?
An object can be signed off once it is published, reconciled after its last publish and has no open gaps, or it is marked out of scope with a reason. A phase (for example Build) is signed off when every object in it is, with the reconciliation report stored as evidence. In the sample conversion, sign-off for an object stays blocked until its read-back from S/4HANA has been reconciled.
What happens before an object is loaded?
Each object moves through Design, Run, Investigate and Resolve. Mappings are approved, jobs are generated, a preflight check runs, and the data is validated against S/4HANA reference data. A side-by-side pre-load report is reviewed and approved before the object is published.
Numbers on this page come from our sample conversion on reference data, not from a client project.