Lesson 3 of 5
Selective data transition
9 min
Selective data transition sits between the other two paths. Instead of converting everything or starting empty, the program builds a target system and moves only what it chooses: some configuration, some custom code, and selected master and transaction data, which can include history for chosen company codes or periods. SAP describes it as finding the right balance between redesign and reuse. It is typically delivered with specialized tools and services, and SAP has published a note on selective data transition and its engagement model (SAP Note 3018442).
Two ways to build the target
| Shell conversion | Mix and match | |
|---|---|---|
| Starting point | A copy of the production ERP system without master and transaction data | A new SAP S/4HANA installation |
| Configuration and code | Kept as the baseline, then converted with the shell; new design built on top | Created new, with selected configuration and repository objects transferred from the source |
| Typical fit | Most processes reused, with targeted changes | Most of the solution redesigned, with some reuse |
| Then | The converted shell becomes the base for development, test and production systems; selected data is migrated in | Selected data is migrated in from the source system |
What can be selected
- By organization: one or more company codes, for example to split or carve out a business.
- By time: open items plus a time slice of closed history, such as the last two or three years.
- By system: several source systems consolidated into one SAP S/4HANA system, or clients moved into an existing system.
- By application: moving particular applications or business areas while the rest follows later.
Selective data transition can also support phased go-lives: one company code or region first, others later, each with its own data transfer. That flexibility is its strength, and also its complexity, because every selection rule must keep business data consistent. A sales order cannot be moved without its customer, its deliveries and its invoices, or the documents in the target will be incomplete.
Tools and delivery
SAP Learning describes selective data transition as enabled by SAP Landscape Transformation technology, which migrates data at table level using preconfigured transformation solutions and keeps data consistent across related tables. Because it works at table level, the transformation logic must be designed and validated carefully. Programs usually engage SAP or a specialized partner for the tooling and expertise; the selection of the provider and approach is a significant decision in its own right.
- Do we want to keep most configuration but not all data?Yes → shell conversion is a candidate · No → next question
- Do we want a new design but some reuse of configuration and code?Yes → mix and match is a candidate · No → next question
- Do we need history for only some company codes or a time slice?Yes → selective data transition fits · No → consider conversion or new implementation
- Are we merging several ERP systems or splitting one?Yes → selective data transition is often the fit · No → compare with the other paths
What would you do?
A manufacturer runs two SAP ERP systems after a merger. It wants one SAP S/4HANA system, with a partially redesigned process model and three years of history for all company codes. Which path is most likely to fit?
- Selective data transition moves chosen configuration, code and data: a balance of reuse and redesign.
- Shell conversion reuses configuration from a data-free copy; mix and match starts new and transfers selected objects.
- Data can be selected by company code, time slice, system or application; phased go-lives are possible.
- It uses table-level transformation tools and usually specialized services; consistency of selected data is critical.
Check your understanding · not graded
Lesson check
1. What is a shell conversion?
2. Which variant starts from a new SAP S/4HANA installation with selected transfers?
3. Which is a typical driver for selective data transition?
4. Why must selection rules keep business data consistent?