Best practices
Practical guidance for running clean, auditable S/4HANA migrations with S4Ready.
Treat datasets as staged assets
Keep datasets versioned, stage‑gated, and tied to a clear migration objective instead of ad‑hoc spreadsheets.
- Always upload from controlled ECC/MDG extracts or MC templates.
- Avoid editing raw exports directly; use the Quick Fix Grid as your default workspace.
- Only fall back to Correction Workbooks when the grid cannot express the required bulk change, and re-import them promptly.
- Retain a clean baseline snapshot for every wave to simplify audit.
Use record identity instead of row numbers
Key issues, fixes, and dedupe decisions on stable record identifiers so changes stay traceable across re‑loads.
- Use natural keys per object (e.g., BP number, GL account+company code) where possible.
- Include dataset version/eTag when applying patches to detect conflicts.
- Never rely on spreadsheet row indexes for identity or audit.
Respect RBAC and PII masking
Only expose unmasked bank, tax, and contact details to the right roles, and keep audit trails immutable.
- Use S4Ready's masked views for stewards who do not require full PII.
- Route sensitive exports through controlled staging buckets, not email.
- Avoid copying raw dataset contents into logs or ticket systems.
Make stewardship a team sport
Share a single migration cockpit across stewards, functional leads, and program owners instead of scattered spreadsheets.
- Use stage tracker views in governance reviews and stand‑ups.
- Assign owners to high‑risk objects and rules rather than individual files.
- Capture explain cards and decision logs as part of sign‑off packets.