New options when transitioning to S/4 HANA through the collaboration between DMLT and Syniti – Part 1
Are you an SAP customer currently in the exploration phase for transitioning to SAP S/4HANA?
Have you read the 101+ blogs and all the various portals on the scenarios available for transitioning to SAP S/4HANA?
Based on the information collected, do you believe that transitioning to SAP S/4HANA via New Implementation or System Conversion does not fit to you or your companies’ individual and specific requirements?
Do you think that selective data transition scenario is an option that fits for your requirements to transition to SAP S/4HANA?
There is a new service offering available to customers who will utilise the Selective Data Transition approach for transitioning to SAP S/4HANA via a collaboration between the Data Management and Landscape Transformation (DMLT) team in SAP and Syniti’s SAP Advanced Data Migration (ADM). This collaboration offers SAP customers a trusted, flexible, and fast way to migrate to SAP S/4HANA, whether on premise or in the cloud. The selective data transition offer strengthens SAP’s already successful partnership with Syniti by offering a high level of customer success, best-in-class software, and extensive services through DMLT and their tools and methodologies.
The DMLT tools and methodologies and SAP ADM by Syniti combine the best practices of greenfield (new implementation), and brownfield (system conversion) for SAP S/4HANA projects as a comprehensive method for accelerating and reducing risk in SAP S/4HANA implementations. The DMLT tools and methodologies allows customers to migrate selected historical data, open transactions, configuration, programs etc to SAP S/4HANA whilst being supported by SAP ADM by Syniti.
How is this done?
Selective data transition from DMLT with SAP ADM by Syniti is achieved via a 8 Step Migration approach:
- Prepare – Defining team roles, systems in scope and schedules including milestones.
- Extract – Automated collection and staging of data from all sources involved in the transition.
- Profile – Analysing and cleansing of the data, providing clarity on the data cleansing, mapping and transformation activities.
- Design – Defining your system blueprint, providing reusability across transitions and ability to reuse rules in a business as usual scenario post go live.
- Map – Alignment of sources to target blueprint. Clear audit trail of all decisions made including change control. Support for both onshore and offshore resourcing models with fully managed metrics and dashboards to track progression.
- Construct – Manual enrichment of your data, fully controlled and auditable, allowing for business user involvement in data capture, review and sign off.
- Transform – Simulation and validation of the loading procedures. Full validated to ensure successful loading and support for regulatory reporting.
- Load – Automation of the movement of data to the target. Minimal business disruptions with data accepted by the business and signed off.
There are 3 main scenarios identified that the new collaboration will focus on:
- Greenfield+ (Extension of a typical New Implementation scenario)
- Client Transfer+ (Extension of a typical System Conversion scenario)
- Consolidation (Consolidation of multiple source systems into S/4HANA)
Scenario 1 – Greenfield+
This scenario describes a new implementation scenario where processes will be predominantly implemented using Model Company, SAP Best Practice or the customers own new Implementation plan as a target template. Data Migration is focused on master data and mainly open transactional data using SAP ADM and standard SAP tools. For selected areas, e.g. Plant Maintenance – master and transactional data including history will be migrated into the target system.
Scenario 2 – Client Transfer+
In this scenario a template is built from the source system (often referred to as a Shell Approach) and then re-worked e.g. to be able to realize process and data harmonization including potential redesign of financial structures including controlling structure and central chart of accounts.
Scenario 3 – Consolidation
This scenario describes building a new S/4 HANA system by consolidating several source systems into one. An example of this would be switching from a regional based landscape into a single global instance, replacing obsolete and split architectures (e.g. financials and logistics in disparate systems) or reducing the number of instances arising from M&A activities.
Under scenario 3 there are a wide variety of “consolidation flavors” with regards to the process and data migration options. These range from technical consolidations through to a Greenfield approach. On the more technical consolidation side, features like system comparisons, shell creations, harmonization, restructuring and historical data migration will be supported under the new collaboration and combination of solutions.
For more information on the new solution offering please contact SAP DMLT at email@example.com
Further blog posts will follow going into more details on each of the three scenarios described above.
Fantastic article Jon Green, I look forward to the next in the series!
Question about historic data migration. is it possible to get historic data migration using ADM tool. We are going for Greenfield implementation, one requirement is to get two years data from existing environment to S/4 for reporting and analytics purpose. Any recommended solution to get historic data migration (including complete, posted record).
Would it be possible to migrate data (master data and transactional data) from an existing S/4HANA Public Cloud system to Private cloud (PCE) S/4HANA system?