|
Go-live does not always mean ECC is switched off straight away. While both systems are live, every change has to be made twice, and the risk is the ones that were not. Step 6 of 6: parallel run. Some teams want proof that S/4HANA gives the same answers, by closing a month in both systems. Some go live in stages, one company code or country at a time, so ECC stays live for the rest. Some want a way back if the first weeks go wrong. Dual running has a cost, because every change has to be made twice. The running example is still the vendor master, reconciled in step 5. This final step keeps the two systems in sync for as long as both are live. This post covers how SAP's own change records make the check possible, how the check can start the moment a record is saved, and how changes can be fed back into the other system. Step 6 of 6: every change checked across both systems as it happens, and the change written back where you choose. Also available on YouTube. The risk of driftWhile both systems are live, every change has to be made in both places. In the video a payment block is set on a vendor in ECC, and the project relies on someone making the same change in S/4HANA manually. This involves duplicate effort and introduces the opportunity for errors and drift between the two systems, and that risk increases over time. SAP already keeps the recordEvery time a vendor is saved, ECC writes a change document: which field, the old value, the new value, who made the change and when. The DVW Flow Tool reads those records for every change since it last ran. For each vendor that changed, it reads the same fields in S/4HANA, using the old vendor number linked in step 5, and the Reconcile tool shows where the two systems now disagree. The payment block set in ECC shows up as a difference S/4HANA does not have. It goes straight to the data owner, with the details of who made the change and when. The same check runs the other way, for changes made in S/4HANA that have not been replicated in ECC. When it happens, not overnightThe Flow can run on a schedule, or SAP can start it automatically. In the video a standard SAP extension point, a Business Transaction Event, calls the Flow whenever a vendor is saved. A change is saved in ECC and the check starts straight away. There is no waiting for the scheduled run. Finding the drift is half the jobThe other half is closing it. The Flow Tool can also write the correction back to SAP. In the video an address is changed in S/4HANA, and the Flow passes that change to a sub-Flow, which updates ECC automatically through a standard SAP BAPI. The two systems stay in step and every update is logged. Which changes sync automatically and which wait for someone to approve them is your decision, made in the Flow, where it is documented. The series, end to endThat is a parallel run where drift is caught when it happens. Across the six steps, the same vendor master has been profiled, cleansed at source, mapped against the new configuration, loaded through SAP's own template, reconciled after every load, and now kept in step while both systems are live, all in documented Flows you can run again at every stage. For the wider picture see the SAP data migration solution page. In this series
Run the series on your own migrationRead and write SAP data from any analytics or data platform. Free 30-day trial, full functionality, no commitment. Trusted by 500+ enterprises. Comments are closed.
|
Guides Reference posts that stay useful. SAP table guides Finance and Controlling Sales and Distribution Purchasing Inventory Management Production Planning Quality Management Plant Maintenance Warehouse Management Human Capital Management Project System SAP finance in KNIME Explore your SAP general ledger Explore SAP financial documents Explore SAP customer line items Explore SAP cost center actuals SAP data by platform Databricks Snowflake Power BI Excel Microsoft Fabric Start here Categories Browse every post by product or by topic. By product By topic |
|
Products
|
Resources
Solutions
|
Company
|
Get started
DVW Analytics gives business users and technical teams direct access to SAP data from Alteryx, KNIME, Dataiku, Power BI, Databricks, Snowflake, and more. Trusted by 500+ enterprises worldwide.
|
|
© COPYRIGHT 2003 - 2026 DE VILLIERS WALTON LIMITED. ALL RIGHTS RESERVED.
|
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Alteryx is a registered trademark of Alteryx, Inc. KNIME is a registered trademark of KNIME AG. Dataiku is a registered trademark of Dataiku SAS. All other product, company, and brand names mentioned herein are the trademarks or registered trademarks of their respective owners and are used for identification purposes only.
