Skip to Content
Product Information

Data Scope Engine – Identify relevant Data for SAP S/4HANA Transition Scenarios Greenfield & Selective Data Transition (SDT)

Many articles and blog posts have been dedicated to the importance of moving from SAP ERP Central Component to SAP S/4HANA. This blog post is covering the important question of data scoping, providing an insight on how you can derive the right data scope to be moved to S/4HANA.

The question which data to be migrated is relevant for Greenfield and Selective Data Transition Scenarios. But how do you determine the data scope? What is the right set of master data and how much historical data is necessary to be migrated? You need to manage the challenge to take as much data as relevant, but travel as light as possible

There are plenty of options how to determine the right data scope. Most customers slice their source system via active organizational units in combination with a time-slice. Others don’t exactly know their actual active organizational structures in their system and want to select active data in all organizational units – determining their active organizational structure via the active data in the system using Data Scope Engine.

Possible data scoping criteria for your SAP S/4HANA transition are:

 

 

But what is this Data Scope Engine thing and how can it be of help?

The Data Scope Engine is a tool developed by SAP Data Management & Landscape Transformation team to support customers to “rightscope” their data in their SAP ERP Central Component environments. It gives support to determine relevant master and transactional data and can even read from archives. It’s a consulting solution especially developed for SAP S/4HANA Transition Scenarios.

It allows to derive master data from transactional data that was used in a specific timeframe in the system plus it allows further filtering of organizational units. On top of it, it also selects master data that was recently created. Different time steps can be set for different business objects in order to allow maximum flexible data scoping:

 

 

Below you can find a common example how the relevant master & transactional data is being derived based on a customer example requirement:

 

The data scoping run is repeatable, means parameters can be adopted and data scoping can be executed again based on new parameters. his gives maximum flexibility and transparency.

The result of the data scope engine actually generates selection tables with relevant data across all SAP ERP Central Component business objects. The output can be observed and you can sign off the selection prior migration – this allows to validate the data scope and then use it for your migration activity. Furthermore the output of the data scope engine can be utilized for data migration.

 

Which input does the Data Scope Engine run require?

The Data Scope Engine doesn’t necessarily require any input but it offers filtering parameters. If no parameters are provided, the Data Scope Engine would simply select all master & transactional data in your system. Since you decided to go for a selective migration approach, this might not be what you really need. Therefore the Data Scope Engine offers the following parameters that can be utilized to further filter your data needed:

 

Key Advantages for utilizing Data Scope Engine

The Data Scope Engine can boost your SAP S/4HANA Transition project by being able to show the business what they can expect if they ask for “last 5 years of data in the system”. It’s best practice in doing the right selection based on flexible selection parameters makes long lasting data selection blueprint workshops and data scope design discussions obsolete. It also helps to avoid issues in migration, as the master data and transactional objects are being selected dependent from each other, given a consistent selection result. The data scope engine provides the results in table form and it’s result can be picked up from data migration tools to populate it’s data load input. Data Scope Engine can be combined in a Selective Data Transition project is be offered as a standalone solution as well.

 

If you want to learn more about SAP Data Management and Landscape Transformation Selective Data Transition Approach, please review this blog post. For more information about SAP Data Management and Landscape Transformation please see this page https://www.sap.com/services/implementation/data-mgmt-landscape-transformation.html or read the solution brief and the SAPPI Success Story. You can contact the global SAP Data Management and Landscape Transformation team by email mailto:sap_dmlt_gce@sap.com. They provides services for Selective Data Transition or New Implementation Scenarios that can also be delivered remotely.

 

Make data scoping a strategic priority for your S/4HANA MOVEMENT!

If you want to learn more, please reach out to me directly.

Wish you a good journey!

Best,

Matthias

1 Comment
You must be Logged on to comment or reply to a post.
  • I am creating a spring-based web application that is set up on Google App Engine. I have a supervisor that store data in the application scope. I’m using a spring bean (singleton) that hold a map and just perform get and remove from the map, however, GAE is a distributed environment and this layout has a problem since every application instance will have its own boss and ask aren’t guaranteed to be made to the same program instance.

    By: Pay Someone To Write My Essay