Académique Documents
Professionnel Documents
Culture Documents
CUSTOMER
Motivation
Agenda
Motivation
▪ Your SAP S/4HANA Migration Requirements
Migrate data from Non-SAP Systems to SAP S/4HANA and from SAP Systems to SAP S/4HANA
Part of SAP S/4HANA and SAP S/4HANA Cloud (included in these licenses)
New On-Premise
Third-party Migration
Implementation System Cockpit
S/4HANA Cloud
ERP System
Region A
Landscape ERP System On-Premise
Transformation Region B
ERP System
Region C
S/4HANA Cloud
Preconfigured content and mapping for each migration object, e.g. G/L Open items
Data migration objects delivered with the SAP S/4HANA Migration Cockpit will be listed in the migration project.
Select the migration objects you need, and generate a migration template for them.
The ‘Simulate Import’ feature checks migration data against the Customizing data in the system.
SAP S/4HANA Migration Object Modeler - Part of the SAP S/4HANA Migration Cockpit
Design functionality to easily integrate custom objects and enhancements
Integration of newly created objects:
▪ Custom objects
▪ SAP standard objects that are not yet in the scope of the SAP S/4HANA Migration Cockpit
Customer-specific enhancements (e.g. add new fields) to SAP standard objects delivered with the SAP S/4
HANA Migration Cockpit
Available for the on-premise SAP S/4HANA and
private option of SAP S/4HANA Cloud
Example: You can add a new field, and specify the relevant information for the field.
Choose ‘Insert Field’
Example: Before you add a new field to the source structure, you can determine which target structure the source field should be mapped to.
As a prerequisite, the source structure must be mapped to a target structure before you can map the fields of the source to
the target structure (see Field Mapping)
If a field from a source structure has been mapped to a target field, the system displays a green icon and a red icon, if it has
not been mapped Filter for mapped/
unmapped fields
1. Tool of choice for migration to 2. Preconfigured migration content 3. Integrated in SAP Activate
SAP S/4HANA specific to SAP S/4HANA methodology
▪ Part of SAP S/4HANA and SAP S/4HANA ▪ Comprehensive set of preconfigured ▪ Proven methodology integrated in
Cloud (included in these licenses) migration objects, such as customers, SAP Activate road map: Transition to
▪ Ready-to-use solution suppliers, and so on SAP S/4HANA
▪ Support for customers with new ▪ Automated mapping between source data ▪ Part of the SAP Model Company service
implementations and SAP S/4HANA target values ▪ Best practices
On-Premise
Migration Cockpit
Third-party Data Process Content Data load
System Provisioning
Single point of entry Preconfigured migration
objects and mapping
Extract Current: Guided procedure
Template API-based
Data selection Generation of migration
File Upload programs
Data transformation
Data validation
Monitoring
ERP System Logs Integration of custom
objects
Documentation
Transfer *
of predefined objects
On-Premise
Migration Cockpit
Third-party Data Process Content Data load
System Provisioning
Single point of entry Preconfigured migration
objects and mapping
Extract Current: Guided procedure
Template API-based
Data selection Generation of migration
File Upload programs
Data transformation
Data validation
Monitoring
Planned:
ERP System Logs Integration of custom
objects
Documentation
Staging
Transfer *
of predefined objects
Direct access
Migration Object Modeler
On-Premise
Migration Cockpit
Third-party Data Process Content Data load
System Provisioning
Single point of entry Preconfigured migration
objects and mapping
Extract Current: Guided procedure
Template API-based
Data selection Generation of migration
File Upload programs
Data transformation
Data validation
Monitoring
Planned:
ERP System Logs Integration of custom
objects
Documentation
Staging
Transfer *
of predefined objects
Direct access Automated
Analyses Data Quality Object Modeler Validation
On-Premise
Migration Cockpit
Third-party Data Process Content Data load
System Provisioning
Single point of entry Preconfigured migration
objects and mapping
Extract Current: Guided procedure
Template API-based
Data selection Generation of migration
File Upload programs
Data transformation
Data validation
Monitoring Table-based
Planned:
ERP System Logs Integration of custom
objects
Documentation
Data model /
Staging
* Object-based
Transfer
of predefined objects
Direct access Automated
Analyses Data Quality Object Modeler Validation
Staging tables will be created natively in the schema of the SAP HANA database depending on the
selected database connection.
For each source structure of a migration object, a separate staging table will be generated.
Staging tables must be filled by customer using extraction tools from SAP or from a third party.
Recent innovations 2018 – Planned innovations 2019 – Product direction 2020 – Product vision
Predefined migration objects for data Data Provisioning Enhanced Content Upgrade Functionality Complete SAP S/4HANA migration
migration from file to SAP S/4HANA ▪ Staging area between SAP or non-SAP to merge modified migration objects with capabilities
support source and SAP S/4HANA target system updates on predefined migration objects
▪ Full Public Cloud scope and on-premise – Staging area must be filled by
Best Practices customer using extraction tools from Automated Validation
SAP or third party ▪ Automated validation of migration
▪ Direct extraction from SAP source
Migration Object Modeler results
▪ Allows users to create their own – Data extraction from SAP source
migration objects – Direct data transfer to SAP S/4HANA Analyses
▪ Allows users to add additional structures target without interim files or staging ▪ Analyze migration data in SAP source
to predefined migration objects – Enhance preconfigured content for systems
data migration from SAP Business
▪ Provides functions to define Suite to SAP S/4HANA
transformation rules and mapping tables Data Quality
Automated field extension of migration ▪ Plausibility checks on imported data
Migration content can be transported objects via extension framework ▪ Data Cleansing
between systems (quality to production) Improved usability of Migration Object
Modeler, also supporting staging solution Auditable Solution
Migration Monitor ▪ Provide information for an audit
▪ Allows parallelization of data transfer
▪ Shows status of migration
Data Migration Overview Page for SAP
S/4HANA Cloud to validate uploaded data
for specific migration objects
This is the current state of planning and may be changed by SAP at any time.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 29
Outlook: 2018 – Planned Innovations
Data Provisioning
▪ Staging
– Staging area between SAP or non-SAP source and SAP S/4HANA target system
– Each SAP or custom migration object is represented as a staging area
– Staging area must be filled by customer using extraction tools from SAP or from a third party
▪ Direct Extraction from SAP source
– Connect SAP source and SAP S/4HANA target system via RFC
– Direct data extraction and transfer to SAP S/4HANA without interim files or staging
– Predefined selection of required source objects
– Automated mapping of selected source objects to SAP S/4HANA target structure
Automated Validation
▪ Automated validation of migration results to facilitate testing
▪ Integration of SAP standard reports into validation
▪ Design and implementation of custom validations
Analyses
▪ Analyses of migration data in SAP source systems
Data Quality
▪ Plausibility checks on imported data
▪ Data Cleansing
▪ Check duplicate entries to improve data quality
Auditable Solution
▪ Provide information for an audit
▪ Keep changes within the cockpit for reviewing and analyzing the migration results
Technical Brief: Migrate our Data to SAP S/4HANA Quickly, Safely and Cost-Effectively
As an SAP customer or potential customer for SAP S/4HANA, you may be wondering how to migrate your data to SAP S/4HANA. In this
2-week course, we’ll give you an introduction to data migration and where it fits in with respect to the different SAP S/4HANA transition
scenarios: ‘New Implementation’, ‘System Conversion’, and ‘Landscape Transformation’. A deep-dive into the SAP S/4HANA migration
cockpit and the migration object modeler will provide you with the skills you need for the latest toolset.
In general, the API must be a function module (FM) - RFC capability is not required. OData and other techniques are
currently not supported by the SAP S/4HANA migration cockpit. The prerequisites are quite the same as the BAPI
definitions in the BAPI Programming Guide:
▪ The function module must not execute the COMMIT WORK command. The SAP S/4HANA migration cockpit handles
the COMMIT control.
▪ The function module must use the ABAP Dictionary structure BAPIRET2 as a structure to return messages to the SAP
S/4HANA migration object modeler.
▪ The function module should provide a test run flag so that it can be run in test mode to simulate the creation of data in the
target system.
Note that if the function module is called in test mode, ensure that the internal buffers are refreshed in order to prevent buffer overflows
and performance issues when calling the function module in a loop.
▪ Regarding consistency checks, write-enabled methods must make all the necessary consistency checks to ensure that the
modified or newly created instance is consistent.
▪ All necessary plausibility checks (for example are all mandatory fields filled, do the values use the correct format, and so
on) must be done by the function module.
▪ If some of the prerequisites are not met, you can develop a wrapper (e.g. for old IDocs).