Week 2: Direct Transfer Approach

Unit 1: Direct Transfer – Introduction and

Project Setup
Direct transfer – Introduction and project setup
Weekly learning objectives

Week 1: Staging Tables Approach and Migration Object Modeler

Week 2: Direct Transfer Approach

By the end of this week, learners will be able to

▪ delimit the two approaches within the SAP S/4HANA migration cockpit
▪ execute a direct transfer project
▪ know simple selection capabilities
▪ understand direct transfer scenarios and migration objects
▪ benefit from best practices
Week 3: Migration Object Modeler for Direct Transfer

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Direct transfer – Introduction and project setup
Agenda

Introduction

Comparison of the two migration approaches

Understand direct transfer – It’s not just a 1:1 transfer!

Technical preconditions

How to set up the system for using direct transfer

Avoid release change during the project

Plan your landscape

Test cycles and system refreshes

How many projects?

Transport your projects

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Direct transfer – Introduction and project setup
Introduction

▪ History

Staging Staging
(LTMC) (LTMC) Direct transfer Direct transfer

SAP S/4HANA 1610 1909

SAP S/4HANA Cloud, 1511 2302 (EA program only)
public edition

▪ Since SAP S/4HANA 2020: Direct transfer and staging in one app: “Migrate Your Data”
▪ The process as such is similar to staging – the selection is the big difference
▪ The migration object coverage is not completely identical to staging

For hands-on experience use the fully activated appliance or the click-through demo: link

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Direct transfer – Introduction and project setup
Introduction

SAP Fiori App Process and Content Data Load

Migrate Your Data

API-Based

Direct Transfer SAP S/4HANA Cloud,

private edition

▪ SAP ERP 6.0 SAP S/4HANA

▪ SAP APO +250 Migration Objects
Direct Transfer
▪ SAP AFS
▪ SAP CRM
▪ SAP EWM

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Direct transfer – Introduction and project setup
Comparison of the two migration approaches

Migrate data using staging tables Migrate data directly from SAP system

Availability SAP S/4HANA Cloud, SAP S/4HANA Cloud, SAP S/4HANA Cloud,
public edition private edition SAP S/4HANA private edition SAP S/4HANA

ABAP-based SAP source systems:

Source System Any source system (SAP or non-SAP) ▪ SAP ERP ▪ SAP EWM
▪ SAP APO ▪ SAP CRM
▪ SAP AFS
▪ XML files
▪ CSV files Data selected and extracted directly from SAP system
Data Provisioning
▪ Preferred ETL tool (using for example SAP Data via RFC connection
Services, SDI, ABAP, or any 3rd party ETL tool)
Before starting the migration project.
Before starting the migration project,
Data Cleansing Note that you can always adjust the selection of data
or in the XML template files, or in the staging tables
by using the migration object modeler

No. of Available
210 + 250 +
Objects
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
Direct transfer – Introduction and project setup
Understand direct transfer – It’s not just a 1:1 transfer!

▪ You migrate data to the next generation of SAP

software (SAP S/4HANA) SAP ERP SAP S/4HANA
▪ There will be differences between the source
(e.g. SAP ERP) and the SAP S/4HANA Customizing
▪ Selecting directly from an SAP source system does
not mean: just select and by clicking a button, the
data is migrated

A good understanding of source and target Customizing and application structures is necessary

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Direct transfer – Introduction and project setup
Technical preconditions

Available for
▪ SAP ERP to SAP S/4HANA; the lowest supported ERP release is ERP 6.0 (SAP NetWeaver 7.0)
▪ SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA; the supported release is AFS 6.0
▪ SAP EWM to EWM based on SAP S/4HANA; the lowest supported EWM release is EWM 5.1
(SAP NetWeaver 7.0)
▪ SAP CRM to SAP S/4HANA for customer management; the lowest supported CRM release is SAP CRM 7.0
▪ SAP APO SPP to SAP S/4HANA eSPP; the lowest supported SCM release is SAP SCM 7.14

The SAP S/4HANA migration cockpit currently does not support the migration of data from
SAP S/4HANA systems to other SAP S/4HANA systems. SAP S/4HANA Finance systems
(previously known as SAP Simple Finance) are classified as SAP S/4HANA systems.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Direct transfer – Introduction and project setup
How to set up the system for using direct transfer

Installation Guide
SAP S/4HANA 2022,
Chapter 7 Before You Start | SAP Help Portal

SAP Note for Direct

Also explaining DMIS add- Transfer
on installation (for free) 2747566

Prepare source SAP Note for HotNews SAP

system (e.g. SAP migration cockpit S/4HANA 2022 FPS0
ERP) (basis) and FPS1
2973957 2780378 3291483

Before starting a project, use Note Analyzer to ensure all corrections are implemented – SAP Note 3016862

Create RFC connection between SAP S/4HANA and source system

Edit user roles: Roles and Authorizations | SAP Help Portal
SAP Note 3090604 You can run the report in this note to check system setup
Execute program CNV_PE_MC_LOAD_OBJECTS in the target SAP S/4HANA system 
loads the migration objects delivered by SAP from client 000 to the current client
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Direct transfer – Introduction and project setup
Avoid release change during the project

Planning Your Migration Projects | SAP Help Portal

Note: Avoid upgrading to a newer release during a migration project if possible!

What is the impact of upgrading to a newer release during a migration project using the direct transfer approach?

Though SAP tries to avoid incompatible changes between releases, it cannot be guaranteed that migration objects
delivered by SAP work after the upgrade.

Same applies to migration objects adapted or created by the customer.

Recommendation
▪ Projects need to be created and executed within the same release, or in other words:
Do not execute projects which were created before the system was upgraded
▪ If you upgrade your SAP S/4HANA system to a new release, we recommend creating completely new migration projects
▪ Custom MOs or extended MOs need to be created in the higher release again
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Direct transfer – Introduction and project setup
Plan your landscape

The more the data in the test systems resembles the data
in the production systems, the more precise the test

SAP S/4HANA (target)

Customizing DEV TST PRD Same release;
MC DT projects patch level
SAP Notes respectively
(incl. TCI notes) SAP Notes
level required!
RFC

RFC

RFC
SAP ERP (source)
DMIS add-on* DEV TST PRD
SAP Notes
(incl. TCI
notes)

Legend: * Free of charge for the use DEV: Development System transport
case SAP S/4HANA TST: Test System
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC migration cockpit DT PRD: Production System 11
Direct transfer – Introduction and project setup
Test cycles and system refreshes

Basics: Creating Migration Projects | SAP Help Portal

▪ Project creation: objects (for example repository and DDIC
objects) are created in the source system in order to select
data from the source system. Test 1
▪ Each project has a defined source system/client and this
definition must not be changed e.g. by changing the RFC or
RFC
by connecting another source system.
SAP ERP SAP S/4HANA
Refreshes:
Assuming the DEV system is stable, there are three possible generates
constellations:
repository and project
▪ SAP ERP and SAP S/4HANA are refreshed: transport the DDIC objects
same migration project from DEV again to TST
▪ Only SAP S/4HANA is refreshed: transport the same
migration project from DEV again to TST
▪ Only SAP ERP is refreshed: create new project in DEV
and transport to TST
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12
Direct transfer – Introduction and project setup
Transport your projects

Details Direct Transfer Transport Concept

▪ The transport functionality used in the migration cockpit direct transfer approach is designed to transport
from one system to another.
▪ Introduced with SAP S/4HANA 2020.
▪ You assign a development package while creating a project (SAP Fiori app). Note that it is not possible to
change this assignment later.
▪ You have the possibility to add projects, migration objects, and rules to a transport request in transaction
LTMOM.
▪ It is not possible to create or edit projects in non-modifiable systems, they can only be executed. Usually,
non-modifiable systems are quality and production systems. For more information about non-modifiable
systems, see link above.
▪ For information about how to transport from client to client within one system, see link above.

Selected instances and mapping values are not transported!

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Direct transfer – Introduction and project setup
How many projects?
Use only one project
+ ▪ Mapping values valid for all migration objects
▪ Central overview and control of the migration
− For direct transfer:
• If you need different selection criteria for one
migration object (e.g. only material category A,
then material category B), you can add the
same migration object to a project several
times.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Use several projects
It might seem as if one project for each application
may lead to a better progress overview for a
dedicated area but:
- ▪ You must keep mapping in sync between the
projects – additional effort and error-prone
▪ If you use internal numbering for a migration
object, you can only upload this mapping for
the successor after the predecessor object
has been migrated
▪ Distributing migration objects across multiple
projects does not improve performance.
See KBA 3056885 (Direct Transfer).
You need one project per source system
14
Direct transfer – Introduction and project setup
Key takeaways

In this unit you have learned

▪ About the similarities and differences of the two
approaches
▪ That direct transfer is not just a 1:1 transfer
▪ How to set up the system for direct transfer
▪ What you should consider when setting up test
landscapes and test cycles for direct transfer

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
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. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.