Está en la página 1de 123

Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach

Unit 1: Getting Started


Getting Started
Recap: SAP S/4HANA migration cockpit

▪ is designed for a
▪ is part of the SAP S/4HANA standard delivery, included in the licenses
▪ resides in the SAP S/4HANA system
▪ has an execution environment – migration cockpit – and a modeling
environment – migration object modeler –
▪ comprises three migration approaches: file, staging, direct transfer
▪ provides guidance through the migration process
▪ contains preconfigured migration objects and rules
▪ includes automatized cross-object value mapping
▪ uses SAP standard APIs to create the data in the target

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


Getting Started
Three migration approaches

Transfer data using files


▪ Download template file for relevant migration object
▪ Populate file with relevant business data
▪ Upload file to the SAP S/4HANA migration cockpit SAP S/4HANA Cloud SAP S/4HANA

Transfer data using staging tables


▪ Staging tables are created automatically (in an SAP HANA DB schema)
▪ Populate staging tables with business data
▪ Transfer data from staging tables to target SAP S/4HANA system SAP S/4HANA Cloud SAP S/4HANA

Transfer data directly from SAP system (new with SAP S/4HANA 1909)
▪ Transfer data from SAP ERP source system to target SAP S/4HANA system
▪ Access source system via RFC connection
▪ Supports data migration scenarios from other applications, e.g. from SAP Apparel and Footwear (SAP AFS) SAP S/4HANA
to SAP S/4HANA for fashion and vertical business, SAP Extended Warehouse Management (SAP EWM) to
decentralized EWM
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Getting Started
SAP EWM to decentralized EWM based on SAP S/4HANA

Migrate data directly from SAP system


Selection of data from SAP source system
via RFC

SAP S/4HANA
Preconfigured migration objects
▪ Warehouse Stock
▪ Warehouse Product SAP Decentral EWM
▪ Storage Bin Business Suite EWM* based on SAP S/4HANA
▪ Storage Bin Sorting
▪ Fixed Bin Assignment

*Prerequisite for transfer of data directly from SAP system: DMIS installation in source
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Getting Started
SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA

Migrate data directly from SAP system


Selection of data from SAP source system
via RFC
AFS
ERP S/4 Fashion

70+ Any DB SAP HANA


70 Predefined AFS-specific
DB
migration objects are supported
AFS standalone system* SAP S/4HANA 1909 with
Fashion module integrated
Capability to derive complex selection
criteria automatically from company code

*Prerequisite for transfer of data directly from SAP system: DMIS installation in source
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Getting Started
Technical preconditions and preparations

Technical preconditions
▪ SAP ERP to SAP S/4HANA, the lowest supported ERP release is ERP 6.0 (SAP NetWeaver 7.0), SAP Note 2836748
▪ SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA, the lowest supported release is AFS 6.0, SAP Note 2836840
▪ SAP EWM to decentralized EWM, the lowest supported EWM release is EWM 5.1 (SAP NetWeaver 7.0)

Necessary preparations in the system landscape


▪ The add-on DMIS_2011 SP17 or higher needs to be installed in the source system (included in the license for
SAP S/4HANA 1909)
▪ RFC connection from the source to SAP S/4HANA target system
▪ Set up SAP Fiori
▪ Apply necessary Notes. Start with Composite SAP Note 2747566
▪ Check Customizing: Relevant Customizing in the target must be available (for example, organizational units, define
document type for migration, define accounts for migration, remove account blocks)
▪ Ensure availability of required authorizations
▪ For required roles, please check the installation guide Installation Guide (check chapter 7)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Getting Started
Process-related preparations

Define a mapping strategy between SAP source and SAP S/4HANA target
▪ Standard APIs are used to load the data into SAP S/4HANA target system
▪ Where configuration in the source deviates from the configuration in the target, adequate mappings have to
be defined upfront, such as rename of organizational units, cost centers, document types, ….
▪ In case of questions carefully check the object-related documentation

Test and productive migration


▪ Test migration
− The data transfer process is client-specific, so you create your project in the client on the receiver system
that should receive the data to be migrated.
− You execute several test data migrations before you run the data migration in the production systems.
▪ Mapping value download and upload
− You can download mapping values of your previous test and upload them into your new project. This
functionality is available in the migration object modeler.

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


Getting Started
Migration objects – Delivered by SAP

Data provisioning Process & content Data load

Transfer data directly


from SAP system

API-based

SAP S/4HANA

SAP S/4HANA

Examples, full list in the appendix

SAP S/4HANA1909: 100+


Migration objects

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


Getting Started
Migration object modeler

▪ Create user-defined migration objects using a wizard


SAP S/4HANA
▪ Add customer tables or fields to a standard migration object or to a new migration object
▪ Add or change selection criteria of standard migration objects or user-defined migration objects
▪ Edit transformation rules
▪ Use standard APIs or code your function module
▪ Mapping download and upload
▪ Debug the transformation and/or the posting process by using the “Test" button in the modeler screen

Transaction:
LTMOM

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Getting Started
More information on help.sap.com

Application Help SAP S/4HANA Migration Cockpit SAP S/4HANA 1909

Migration object list in SAP Help Portal


Filter for migration approach:

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


Getting Started
More deep-dive information on the Data Migration landing page

Data Migration Landing Page SAP S/4HANA 1909

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


Getting Started
Appendix

APPENDIX

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12


Getting Started
Preconfigured migration objects I (SAP ERP to SAP S/4HANA)

Controlling Financials – General Ledger Treasury and Risk Management


FI-CO Activity group FI-AA Fixed asset – including balance FI-TRM Additional flow
FI-CO Activity type FI-GL Account balance – classic G/L FI-TRM Commercial paper
FI-CO Activity type – price planning FI-GL Account balance – new G/L FI-TRM Condition details
FI-CO Business process FI-GL Bank account FI-TRM Foreign exchange collar contract
FI-CO Business process group FI-GL Bank key FI-TRM Foreign exchange option
FI-CO Cost center FI-GL Customer open item – classic G/L FI-TRM Foreign exchange spot/forward
FI-CO Cost center standard hierarchy and groups FI-GL Customer open item – new G/L contract

FI-CO Cost element group FI-GL Exchange rate FI-TRM Foreign exchange swap contract

FI-CO Internal order FI-GL General ledger account FI-TRM Interest rate instrument

FI-CO Profit center FI-GL House bank FI-TRM OTC interest rate derivative swap

FI-CO Profit center standard hierarchy and groups FI-GL Open item – classic G/L FI-TRM Payment details

FI-CO Secondary cost element FI-GL Open item – ledger group specific FI-TRM Settlement

FI-CO Statistical key figure FI-GL Open item – new G/L


FI-GL Vendor open item – classic G/L
FI-GL Vendor open item – new G/L

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


Getting Started
Preconfigured migration objects II (SAP ERP to SAP S/4HANA)

Logistics Materials Management Plant Maintenance


Batch (if batch is unique at material level) Material inventory balance Equipment
Batch (if batch is unique at plant level) Purchasing contract Equipment BOM
Material Purchasing info record Equipment task list
Material commodity Purchase order (only open PO) Functional location
Material MRP area Purchase requisition (only open PR) Functional location BOM
Production version Pricing condition (Purchasing and Sales) Functional location task list
Sales order BOM Scheduling agreement General task list
VC – Configuration profile Service entry sheet Maintenance item
VC – Material variant Service master Maintenance plan
VC – Object dependency & dependency net Source list Measuring point
Vendor Production Planning
Work center Material BOM
Material consumption
Material classification
Planned independent requirement
Production order
Routing
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14
Getting Started
Preconfigured migration objects III (SAP ERP to SAP S/4HANA)

Sales and Distribution Quality Management


Customer Inspection catalog selected set code
Customer material info record Inspection catalog selected sets
Customer quotation Inspection method
Pricing condition (purchasing and sales) Inspection plan
Sales order (only open SO) Inspection setup
Sales contract Master inspection characteristics
Quality info record

Cross Application Project Systems


Business partner Project
Characteristic Project system – Network
Class
Engineering change number

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


Getting Started
Preconfigured migration objects I (SAP AFS to SAP S/4HANA)

Controlling Financials – General Ledger Application Platform


FI-CO Activity group FI-GL Account balance – classic G/L Purchase grid article
FI-CO Activity type FI-GL Account balance – new G/L Purchase grid for plants and articles
FI-CO Activity type – price planning FI-GL Bank account Purchase grid for pur. org., vendor & articles
FI-CO Business process FI-GL Bank key Purchase grid for purchasing org and articles
FI-CO Business process group FI-GL Customer open item – classic G/L Purchasing contract
FI-CO Cost center FI-GL Customer open item – new G/L Sales grid for articles
FI-CO Cost center standard hierarchy & group FI-GL Exchange rate Sales grid: s. org, dist. ch, cust. grp & article
FI-CO Cost element group FI-GL General ledger account Sales grid: s. org, dist. ch, customer & article
FI-CO Internal order FI-GL Open item – classic G/L Sales Grid: sales org, dist. channel & article
FI-CO Profit center FI-GL Open item – ledger group-specific Segmentation default values
FI-CO Profit center standard hierarchy & group FI-GL Open item – new G/L Segmentation structure
FI-CO Secondary cost element FI-GL Vendor open item – classic G/L Segmentation strategy
FI-CO Statistical key figure FI-GL Vendor open item – new G/L
House bank

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16


Getting Started
Preconfigured migration objects II (SAP AFS to SAP S/4HANA)

Logistics Production Planning Cross Application


Batch at plant level Planned indep. requirement at material level Characteristics for dimensions
Configuration class for material grid Planned indep. requirement at SKU level Characteristics for non-dimensions
Customer Planned independent requirement Classification for batches
Equipment Routing – task list Engineering change numbers
Quantity distribution profile Work center
VAS (sales area and customer) Source list
VAS (sales area, customer group and material)
VAS (sales area, customer and material)
Vendor

Materials Management Sales and Distribution Industry-Specific


Article Customer Distribution curve
Material BOM Pricing condition (purchasing and sales) Distribution curve condition
Material inventory balance Sales contract Season
Purchase order (only open PO) Sales order (only open SO)
Purchasing info record Sales order BOM
Scheduling agreement
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17
Getting Started
Preconfigured migration objects (SAP EWM to SAP S/4HANA)

Decentralized Extended Warehouse Management


Warehouse fixed bin assignments
Warehouse product
Warehouse stock
Warehouse storage bin
Warehouse storage bin sorting

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18


Getting Started
Outlook

Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach


Unit 2: Project Creation and Selection
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 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/copyright for additional trademark information and notices.
Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach
Unit 2: Project Creation and Selection
Project Creation and Selection
Landscape used in the example

SAP ERP SAP S/4HANA


(on-premise)
RFC
System “ABA” Migration Cockpit

System “S4H”
SAP ERP 6.0 with EHP 8 / An RFC connection connects
NetWeaver 7.50 the SAP S/4HANA migration
cockpit to the SAP ERP SAP S/4HANA
source system 1909 FPS00

The migration cockpit is part of the


standard delivery and resides in the
SAP S/4HANA system

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


Project Creation and Selection
Business scenario

SAP ERP SAP S/4HANA


Business objects

Cost center

Select data by using criteria: Map & transform data Simulate Migrate
▪ Organizational unit:
Company code
Activity type
▪ Migration object:
FI-CO Cost center
▪ Migration object:
FI-CO Activity type

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


Project Creation and Selection
Demo (based on 1909)

Steps shown in the demo:

(1) Create a migration project (in the SAP S/4HANA target system “S4H”)

(2) Select data from the ERP source system “ABA”

(3) Compare data in the ERP source system (“ABA”)

(4) Specify mapping values

(5) Simulate the migration

(6) Correct errors

(7) Migrate the data

(8) Check results in the SAP S/4HANA target system “S4H”

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


Project Creation and Selection
Start the app

Start the “Migrate Your Data” app

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


Project Creation and Selection
Create a migration project
The SAP S/4HANA migration cockpit uses migration
objects to identify and transfer the relevant data. With
1909 FPS0 SAP delivers 97 migration objects for the ERP
scenario. In the migration object modeler, objects can be
adjusted or own objects can be created (units 3.5 ff.).

Selection of relevant scenario:


▪ SAP ERP to SAP S/4HANA
▪ SAP AFS to SAP S/4HANA
▪ SAP EWM to decentralized EWM based on SAP S/4HANA

Preconfigured data selection based on organizational


units e.g. company codes for scenario SAP ERP to
SAP S/4HANA

Preconfigured migration content:


List of available migration objects relevant
for the selected scenario

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Project Creation and Selection
Create a migration project – Dependent migration objects

When saving the project, the systems asks if you want


to add the predecessor objects. Clicking on View
Details provides the list of predecessors for the
migration objects that are selected for this dedicated
project.

In the Dependencies column, all predecessors and


successors are listed.

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


Project Creation and Selection
Migration project screen

When saving the project, numerous programs are generated and the migration objects are copied from
the delivered template into your project. This step takes some time. In case of errors during the copy
process you can restart it (error message with link in the header).

Activity tracking is available


within one project as shown here
on the migration project screen.
It is also available for all projects
on the migration projects screen
(not shown here).

In the project setup phase, you see


which objects are ready for
processing, and which objects are
still in a generation phase and will
be available for processing soon. Message logs are available for
completed activities. For more
details, click the View Log button
in the activity tracking panel of a
project.

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


Project Creation and Selection
Migration project screen

Shows predecessors for this object Click Settings for important


information for the project.

The number of jobs per object is defined


here. Note that the maximum number of jobs
per project is defined in the migration project
setting screen!

Click the migration object to get to the


migration object screen. This is a
central place with very detailed
information, also from a technical point
of view.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Project Creation and Selection
Migration project settings

You find the message logs


for completed activities on
project level here.

After a project is set to finished, a retention


period is defined and can be seen here.

The migration cockpit offers parallelization. It is effective for the actions:


selection, simulation and migration.
The number of background jobs on project level is defined here. It will not
be exceeded by the project even if a higher number of jobs is specified on
migration object level.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


Project Creation and Selection
Migration object screen

To get detailed information about a migration object,


click the migration object name in the Migration The system displays the Migration Object
Object column. screen, where you can view the following
information:
▪ Description
▪ Table structure
▪ History of events, including logs
▪ Dependencies to other migration objects
▪ Data (migration object instances)
▪ Technical information (relevant for support)
BAPI used for this object. The BAPI
determines which functionality the
migration object provides.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


Project Creation and Selection
Migration object screen – Table structure and history

In the Tables section, you see the relevant


source system tables for the migration
object. The system displays the source
system tables in a hierarchy.

In the History section you see the different


actions for the migration object. You can
also view the log for each action regarding
this object.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12


Project Creation and Selection
Start selection

The migration cockpit guides you through the various steps of the data migration. You can also flexibly
choose which steps you want to do next (select, simulate, migrate).

Here you can execute actions for all


migration objects in your project.

The system proposes


“Select Data” as the next
action. Here, you start the
selection for one object
only.

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


Project Creation and Selection
Selection steps

The system lets you confirm Activity tracking shows


the start of selection the progress

Migration project screen after the selection has finished

As soon as the selection has finished, the system


automatically creates the available mapping tasks for each
object.

Number of selected instances per migration object. Click


the number to view the list of migration object instances.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14


Project Creation and Selection
Migration object instances

The system offers


various possibilities to
search, filter, and so on

Use the gear wheel to


select the columns to be
displayed

Click the arrow to view the


migration object instance
details

On the migration object screen in the Data


section, you also find the migration object
instances list.

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


Project Creation and Selection
Compare data in the ERP source system (“ABA”)

Compare the data selected by the SAP S/4HANA migration cockpit with the data in the ERP source system. You can either use the
application transactions as shown below or use transaction SE16 to have a look directly into table CSKS (for cost centers) and CSLA
(for activity types).
With transaction KL13 you see 3 activity
types in the source system in controlling
area 0001

With transaction KS13 None of the cost


you see 6 cost centers in centers has a profit
the source system in center assigned
controlling area 0001 One has an allocation
cost element assigned

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16


Project Creation and Selection
Focus topic: repeated selection
Report: CNV_PE_MC_DEL_ITEMS
If you want to delete the selected
The migration cockpit is designed for the migration process. It is not designed for migration object instance to run the
a perpetual loading of data. selection again, you can use the
Nevertheless, especially during test migrations or when migrating parts of data
report: CNV_PE_MC_DEL_ITEMS.
within a phased approach (e.g. already load some master data before the go-live
on the weekend), repeated selection might make sense.
➢ Add new items? Just repeat the selection
➢ Stop processing single items? Use the “exclude” function in the migration
cockpit (in the SAP Fiori app)
➢ Update items (because data changed in the source)? First delete the selected
records, then start selection

In 1909, the deletion function has not yet been implemented in SAP Fiori but
does exist in the back end: report CNV_PE_MC_DEL_ITEMS

SAP Note 2857598

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17


Project Creation and Selection
Steps executed in the systems

(1) Create a migration project (in the SAP S/4HANA target system “S4H”)

(2) Select data from the ERP source system “ABA”

(3) Compare data in the ERP source system (“ABA”)

(4) Specify mapping values

(5) Simulate the migration

(6) Correct errors

(7) Migrate the data

(8) Check results in the SAP S/4HANA target system “S4H”

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18


Project Creation and Selection
Key takeaways

▪ Migration objects available depending on the chosen


scenario
▪ Selection
− Organizational unit is predefined by SAP depending on
the scenario (e.g. company code for ERP scenario)
− Start selection for the whole project or for migration
objects
▪ Repeated selection possible
▪ Parallelization
▪ Activity tracking
▪ Object instances list shows selected instances with status
▪ Mapping tasks and mapping value proposals (1:1) are
created automatically during the selection step

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19


Project Creation and Selection
Outlook

Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach


Unit 3: Value Mapping and Simulation
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 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/copyright for additional trademark information and notices.
Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach
Unit 3: Value Mapping and Simulation
Value Mapping and Simulation
Demo (based on 1909)

Steps shown in the demo:

(1) Create a migration project (in the SAP S/4HANA target system “S4H”)

(2) Select data from the ERP source system “ABA”

(3) Compare data in the ERP source system (“ABA”)

(4) Specify mapping values

(5) Simulate the migration

(6) Correct errors

(7) Migrate the data

(8) Check results in the SAP S/4HANA target system “S4H”

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


Value Mapping and Simulation
Mapping tasks

As soon as the selection has finished, the system automatically creates mapping tasks for each object. For
each source mapping value a target mapping value proposal is created (1:1). The mapping tasks are defined
in the delivered objects.
You can change or create mapping tasks in the migration object modeler.

Leads to all mapping


tasks for this project

Mapping tasks for object FI-CO Cost center.


Click the number to view the mapping tasks
for this dedicated object.

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


Value Mapping and Simulation
Mapping tasks

The sum of mapping In this overview


tasks for this project is screen you can
confirm all mappings
12, as the mapping task at once
Controlling area is used
by both objects. The
mapping tasks work
cross-object, meaning
Mapping type
the values for the
mapping tasks only have Different mapping
to be edited once. They types exist, for
are then used by all example:
▪ value mappings
migration objects within ▪ fixed values (e.g.
this project. posting date, offset
account number)
▪ … and others

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


Value Mapping and Simulation
Specify mapping values

On this screen, you specify mapping values to transform values from the source system to the target system.
In the migration object modeler, you can upload and download mapping values.
Documentation
for mapping
task

Search help available for target values

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


Value Mapping and Simulation
Execute simulation

Simulation means the API used in the migration object is executed in the same way as in real mode. The only difference is
that the data is not created and posted in the target system. The simulation brings up the messages from the migration
cockpit as well as from the application.
A few APIs have no simulation function, e.g. migration object FI-GL House bank. If this is the case, it is mentioned in the
migration object documentation and the simulation action is not offered.

You can simulate for all objects within this project at


once, selecting all instances or only the ones with
errors

You can simulate only for one or for several


objects and then choose all or random simulation

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Value Mapping and Simulation
Actions for dedicated items (simulate, migrate, exclude)

On the migration object screen you can execute actions for items you chose individually.

Simulate the two marked entries

Exclude specific migration object instances


by choosing the Exclude button. The
excluded migration object instances will
not be simulated or migrated.

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


Value Mapping and Simulation
Simulation result

For one instance of migration object FI-CO Activity Type and for six instances of migration object FI-CO Cost
Center the simulation ended with errors.

There are two ways to proceed:


Either click the
▪ number of erroneously
simulated items, or
▪ click the migration object (e.g.
FI-CO Cost center).

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


Value Mapping and Simulation
Simulation result – Messages for single instances

Search, sort, group, or download

Click the number of


instances to get to the
migration object
instances screen

Click one instance in


the left-hand pane

You get the messages


for this instance

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Value Mapping and Simulation
Simulation result – All messages for the migration object

Click the View Log button to


get to the messages screen

Click the migration object


name to get to the migration
object screen

Search, sort, group, or download

You get all messages for


this migration object FI-CO
Cost center

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


Value Mapping and Simulation
Steps executed in the systems

(1) Create a migration project (in the SAP S/4HANA target system “S4H”)

(2) Select data from the ERP source system “ABA”

(3) Compare data in the ERP source system (“ABA”)

(4) Specify mapping values

(5) Simulate the migration

(6) Correct errors

(7) Migrate the data

(8) Check results in the SAP S/4HANA target system “S4H”

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


Value Mapping and Simulation
Key takeaways

▪ Mapping tasks work cross-object


▪ Input help available for mapping target values
▪ In the mapping tasks overview screen, mappings can be
confirmed all at once
▪ Simulation possible for:
− all items within one project or the instances with errors
− items of one or several migration objects – all or
random 500 or 10%
− single items starting from the migration object screen
▪ Exclude function for single instances
▪ Search, sort, group, and download function for
messages

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12


Value Mapping and Simulation
Outlook

Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach


Unit 4: Issue Handling and Migration
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 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/copyright for additional trademark information and notices.
Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach
Unit 4: Issue Handling and Migration
Issue Handling and Migration
Demo (based on 1909)

Steps shown in the demo:

(1) Create a migration project (in the SAP S/4HANA target system “S4H”)

(2) Select data from the ERP source system “ABA”

(3) Compare data in the ERP source system (“ABA”)

(4) Specify mapping values

(5) Simulate the migration

(6) Correct errors

(7) Migrate the data

(8) Check results in the SAP S/4HANA target system “S4H”

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


Issue Handling and Migration
Overview simulation errors

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


Issue Handling and Migration
Check issues in detail – Activity types

This error message (KS030) comes from


the application, so the application experts
have to look for a solution

In the migration object detail screen, mark the erroneous entry and click Messages

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


Issue Handling and Migration
Check issues in detail – Cost centers

Messages screen – messages sorted by message number, ascending

General subsequent error message – no action required

This error message (KS070)


comes from the application, so
the application experts have to
look for a solution

This warning (KS096)


comes from the
application, so the
application experts
have to look for a
solution

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


Issue Handling and Migration
Possible solutions to solve issues

In case of technical issues or issues which come


from the SAP S/4HANA migration cockpit, the
migration consultant or the system administrator
has to follow up on it.
In case of issues which come from the API, it is the
responsibility of the application consultants and
application experts to investigate the root cause.
How can the application issues be solved?
▪ Change data in the source, repeat selection
▪ Create or change Customizing in the target
▪ Create or change master data in the target
▪ Change mapping to existing/fitting target value
▪ Exclude item from further processing

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Issue Handling and Migration
Possible solutions to solve the issues in this example

Error Concerned instances Change mapping Create data in the Exclude item
target
KS030: Cost element Activity type: ADMIN Change mapping to an Create the cost element Exclude the
does not exist existing / fitting cost element erroneous item
in the SAP S/4HANA target (activity type
system ADMIN)*
KS070 Area Cost center: KSDT2000C1, Change mapping to an Create the cost center group Exclude the
K0001_HIER cannot KSDT2000C2, KSDT9999C3, existing / fitting cost in the standard hierarchy in erroneous items
be used here KSDT9999C4, KSDT9999C5, center group in the SAP the target
KSDTGERMAN S/4HANA target system 
for all 6 cost centers*
Warning
KS096 Profit Center Cost center: KSDT2000C1, Insert target mapping values Exclude the
Accounting active but KSDT2000C2, KSDT9999C3, (currently target is blank as erroneous items
no profit center KSDT9999C4, KSDT9999C5, source profit center is also
specified KSDTGERMAN blank)

Is only a warning – ignore it if application


department agrees  for all 6 cost centers* * solution chosen in this example
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Issue Handling and Migration
Solution: Exclude the erroneous item

Go to the migration object detail screen, mark


the entry, and press the Exclude button

In the project screen, you will now


find one excluded item. The
number of items to be migrated
(not started) has changed to “2”.
The red bar on the left-hand side
has disappeared for object FI-CO
Activity Type.

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


Issue Handling and Migration
Solution: Change mapping to existing target values

Go to the Mapping Tasks screen and change the target


value for CO group K0001_HIER to 0001, a value which
exists in the target system already. Confirm the changed
entry.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Issue Handling and Migration
Simulate again after corrections

Simulate the items for object FI-CO Cost


Center again (FI-CO Activity Type has
already been successfully simulated).
There are now no more errors.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


Issue Handling and Migration
Migrate

Migrate the data. For the migration step, the same possibilities exist as for the simulation: migrate single items (on the
migration object screen), migrate random 10% or random 500 items, migrate only instances with errors, migrate all instances.

You can migrate all objects at once – selecting


all instances or only the ones with errors

You can migrate only one


or several objects and
then choose all or random
migration

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


Issue Handling and Migration
Migration results in the migration cockpit

Results on the project screen

Results on the migration object screens

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12


Issue Handling and Migration
Check results in the target system

Compare the data migrated by the SAP S/4HANA migration cockpit with the data in the SAP S/4HANA target system. You
can either use the application transactions listed below or use transaction SE16 to have a look directly into table CSKS (for
cost centers) and CSLA (for activity types).

Migration Cockpit SAP S/4HANA target system

Transaction SE16, table CSLA

App or transaction In the target system there


are only two activity types
as activity type ADMIN
was excluded during the
process.

Alternatively, transaction KL13 still works


© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13
Issue Handling and Migration
Steps executed in the systems

(1) Create a migration project (in the SAP S/4HANA target system “S4H”)

(2) Select data from the ERP source system “ABA”

(3) Compare data in the ERP source system (“ABA”)

(4) Specify mapping values

(5) Simulate the migration

(6) Correct errors

(7) Migrate the data

(8) Check results in the SAP S/4HANA target system “S4H”

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14


Issue Handling and Migration
Key takeaways

▪ Technical messages may arise as well as messages


from the used API
▪ Technical messages including messages from the
migration cockpit have to be followed up by the
basis/administration department
▪ Messages from the API have to be followed up by the
respective application consultants/departments
▪ For the migration step, the same possibilities exist as for
the simulation:
− all items within one project or the instances with errors
− items of one or several migration objects – all or
random 500 or 10%
− single items starting from the migration object screen

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


Issue Handling and Migration
Outlook

Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach


Unit 5: Migration Object Modeler: Creating Your Own Migration Object (I)
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 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/copyright for additional trademark information and notices.
Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach
Unit 5: Migration Object Modeler: Creating Your Own
Migration Object I
Migration Object Modeler: Creating Your Own Migration Object I
Introduction

Typical Questions:
▪ How can I adapt the delivered content to my customers' needs? SAP S/4HANA
▪ Is it possible to adjust the existing SAP migration objects?
▪ How can I adjust the selection of data for the direct transfer approach?
▪ How can I create my own migration objects to transfer customer-specific data?

Migration object modeler: modeling environment of the SAP S/4HANA migration cockpit

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


Migration Object Modeler: Creating Your Own Migration Object I
Modeling environment of the SAP S/4HANA migration cockpit

Flexible and Extendable


SAP S/4HANA
Easily integrate custom objects and enhancements into the migration project

▪ Integration of newly created objects:


– Custom objects
– SAP standard objects that are not yet in the scope of the SAP S/4HANA migration cockpit
– Use standard APIs or code your function module
▪ Customer-specific enhancements to SAP standard objects delivered with the SAP S/4HANA
migration cockpit
– Add or change migration object selection criteria
– Map structures and fields
▪ Available for SAP S/4HANA Transaction:
LTMOM

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


Migration Object Modeler: Creating Your Own Migration Object I
Business need (initial situation)

Gap: migration object “FI-CO Cost ERP source system Logon language: German
centers” currently (OP1909) only transfers
the master data text in the logon language.
If there are also texts in other languages,
an additional migration object is needed.

ERP source system Logon language: English

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


Migration Object Modeler: Creating Your Own Migration Object I
Demo (based on 1909)

Steps shown in the demo:


▪ LTMOM: create a migration object – this opens the wizard
▪ Migration object wizard
− Edit source structures
− Define unique object ID
− Define target processing
▪ Check project in the migration cockpit (SAP Fiori)
▪ LTMOM: source structures – define selection criteria
▪ LTMOM: target processing
− Simulation details
− Structure mapping including access path to the child table
− Field mapping
▪ Execute the selection in the migration cockpit (SAP Fiori)
▪ Execute the simulation in the migration cockpit (SAP Fiori)
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Migration Object Modeler: Creating Your Own Migration Object I
Start with transaction LTMOM

Start with transaction LTMOM

Choose your project

You see the two standard migration objects that are already assigned to
the project

Click the info button to view


the documentation for the
migration object modeler,
Direct Transfer approach

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Migration Object Modeler: Creating Your Own Migration Object I
Create a migration object – Opens the wizard

If you have specific requirements that are not covered by the migration objects provided by SAP, you can
create user-defined migration objects.
Choose: Project -> Create Migration Object -> User-
Defined -> Migrate Data Directly from SAP System.
This path opens a wizard which supports you in
creating your own object.

The migration object wizard


guides you step by step
through the process of
creating your own object

Pay attention to
the documenation!

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


Migration Object Modeler: Creating Your Own Migration Object I
Migration object wizard – Source structures

In the Source Structures step you define the table(s) from which the selection will read the data. You can also
use customer-own tables here.

Add root table: In this example, the root table


is CSKT – the table for cost center texts

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


Migration Object Modeler: Creating Your Own Migration Object I
Migration object wizard – Source structures

Table CSKT does not contain all the fields that are needed to feed the respective BAPI (field valid-from is
missing), so we need a second table CSKS to fill all fields. CSKS is defined as child table in this data model.
Position the cursor on table CSKT and choose Add Child Table

For this example, define CSKS as child table of CSKT

Parent – child relationship

Now, the foreign key relationship between parent and


child table has to be defined. For each CSKT key field,
assign the respective CSKS field.
Note: SPRAS is not a key field in CSKT, so it is not
assigned!

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Migration Object Modeler: Creating Your Own Migration Object I
Migration object wizard – Unique object ID

In this step, you define which fields determine a migration object instance in a unique way. In this example, the
Language Key, Controlling Area, Cost Center, and Valid To Date fields define one instance unambiguously.

The proposal button gives the correct suggestion

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


Migration Object Modeler: Creating Your Own Migration Object I
Migration object wizard – Target Processing Details – Transfer Info

Assign the function module which will be used to post or create the data in the SAP S/4HANA target system.
You can also assign an own custom API.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


Migration Object Modeler: Creating Your Own Migration Object I
Migration object wizard – Target Processing Details – Return Evaluation

The Return Evaluation step offers all exporting


parameters and table parameters of the function
module you assigned in the previous Transfer Info
step. The proposal function suggests the proper
evaluation method.

Complete the wizard

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12


Migration Object Modeler: Creating Your Own Migration Object I
Look into the migration cockpit

Back in the migration cockpit, you see the newly created migration object. This migration object is processed
in the same way as the migration objects delivered by SAP.

The mappings of type move are not shown under mapping


tasks. This type moves the values as they are from the
source to the target system. By definition, the values
cannot be changed.

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


Migration Object Modeler: Creating Your Own Migration Object I
Steps executed in the systems

▪ LTMOM: create a migration object – this opens the wizard


▪ Migration object wizard
− Edit source structures
− Define unique object ID
− Define target processing
▪ Check project in the migration cockpit (SAP Fiori)
▪ LTMOM: source structures – define selection criteria
▪ LTMOM: target processing
− Simulation details
− Structure mapping including access path to the child table
− Field mapping
▪ Execute the selection in the migration cockpit (SAP Fiori)
▪ Execute the simulation in the migration cockpit (SAP Fiori)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14


Migration Object Modeler: Creating Your Own Migration Object I
Key takeaways

▪ The Direct Transfer approach also offers a modeling


environment
▪ The migration object wizard supports you in creating a
migration object. Details are added directly in the
transaction LTMOM.
▪ Custom-own tables can be part of your migration
object data model
▪ For assignments, there is often a proposal function
available
▪ Assign a standard SAP API or custom-own API to the
migration object
▪ The new migration object is displayed in the migration
cockpit (SAP Fiori). It is processed in the same way as
the migration objects delivered by SAP.

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


Migration Object Modeler: Creating Your Own Migration Object I
Outlook

Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach


Unit 6: Migration Object Modeler: Creating Your Own Migration Object II
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 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/copyright for additional trademark information and notices.
Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach
Unit 6: Migration Object Modeler: Creating Your
Own Migration Object II
Migration Object Modeler: Creating Your Own Migration Object II
Steps executed in the systems

▪ LTMOM: create a migration object – this opens the wizard


▪ Migration object wizard
− Edit source structures
− Define unique object ID
− Define target processing
▪ Check project in the migration cockpit (SAP Fiori)
▪ LTMOM: source structures – define selection criteria
▪ LTMOM: target processing
− Simulation details
− Structure mapping including access path to the child table
− Field mapping
▪ Execute the selection in the migration cockpit (SAP Fiori)
▪ Execute the simulation in the migration cockpit (SAP Fiori)

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


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Source Structures – Selection Criteria tab

After having finished the steps in the migration object wizard, some more details need to be edited directly in transaction
LTMOM. Then the new migration object is ready to be used. On the Selection Criteria tab you can influence the selection and
define filters.

Go to Source Structures and double-click table


CSKT to open the window below

Choose Selection Criteria

Filters define which


organizational unit is
used to select data from
the source system. A
filter can be for example
company code,
controlling area, plant,
Here, you can define or influence the selection on table level …

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


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Source Structures – Example for filters

Filter is a collection of values of the same type that is stored centrally for your project, and therefore available for all
migration objects assigned to the project. A filter can be for example company code, controlling area, plant, …

For this example, two filters are needed.


For table CSKT, only field KOKRS is possible, for table CSKS,
field BUKRS will be defined as filter.

Logic for selection


Start selection, popup: You will select for BUKRS 0001 SAP S/4HANA
Migration object instances are
created in the SAP S/4HANA
Looks into table TKA02: BUKRS – KOKRS: 0001 – 0001 system
Selects entries from CSKT for KOKRS 0001 ERP
Selects entries from CSKS for BUKRS 0001

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


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Source Structures – Define filter for root table CSKT

Click the button in row CSKT

Click add filter


Expand the field list for table CSKT and assign field
KOKRS from CSKT to the filter KOKRS (drag and drop)

Choose filter KOKRS from the


list of possible filter criteria

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


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Source Structures – Define filter for child table CSKS

Click the button in row CSKS

Click add filter


Expand the field list for table CSKS and assign field
BUKRS from CSKS to the filter BUKRS (drag and drop)

BUKRS

Choose filter BUKRS from the


list of possible filter criteria

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Target Processing – Simulation Details

Simulation Details tab: Define how simulation will work in your customer object. F1 on the input field for Simulation Type
provides detailed documentation about the possible choices.
Check the description of the function
module to get the details about a
possible simulation functionality and
how to fill parameters.

Chose “1”

Choose Add

Double-click the API

Select parameter TESTRUN

Fill the parameters for run types Simulation and


Transfer according to the function module
documentation

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


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Target Processing – Structure Mapping

Structure Mapping tab: What information has to be transferred from the source structure to the structure of the function
module?

Source structure

Structure of the function module

Drag and drop the source structure CSKT to the target structure (to the function
module BAPI_COSTCENTER_CHANGEMULTIPLE)

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


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Target Processing – Access Path

The access path defines how the records of child table CSKS will be selected. In the present data model, for each record in
CSKT there is only one dedicated record in CSKS. So the option “Any Line” is chosen.

Click COSTCENTERLIST

Click Access Path

Choose Any Line


Click Access Path

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Migration Object Modeler: Creating Your Own Migration Object II
LTMOM – Target Processing – Field Mapping

Field Mapping tab: Map the fields of the source structure to the fields of the target structure / the function module
Only the mapped fields are shown. You
can change it to “All Fields” if you want
to get all.

Transformation
type is “Move”. This
means all values are
moved unchanged
1:1 from the source
system to the target
SAP S/4HANA
system

Drag and drop the source fields on the left-hand side (from CSKT and CSKS) to the target fields of the function module
BAPI_COSTCENTER_CHANGEMULTIPLE (on the right-hand side). Field DATAB is moved from table CSKS, all other fields from
CSKT. Be careful to expand the correct table (!) under Source Structures in order to chose the fields from the correct table!

The definition of the migration object is now complete. Save it and leave transaction LTMOM.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Migration Object Modeler: Creating Your Own Migration Object II
Migration cockpit – Execute the selection, execute the simulation

Back in the migration cockpit, execute the selection, then execute the simulation.
Selection result

For transformation type “Move”,


no mapping tasks are displayed

Simulation result

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


Migration Object Modeler: Creating Your Own Migration Object II
Steps executed in the systems

▪ LTMOM: create a migration object – this opens the wizard


▪ Migration object wizard
− Edit source structures
− Define unique object ID
− Define target processing
▪ Check project in the migration cockpit (SAP Fiori)
▪ LTMOM: source structures – define selection criteria
▪ LTMOM: target processing
− Simulation details
− Structure mapping including access path to the child table
− Field mapping
▪ Execute the selection in the migration cockpit (SAP Fiori)
▪ Execute the simulation in the migration cockpit (SAP Fiori)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12


Migration Object Modeler: Creating Your Own Migration Object II
Key takeaways

▪ The selection from the source system can be defined


– on table level for each field of the source table and/or
– by using filters, e.g. company code, controlling area,
plant, …
▪ If the chosen API offers a simulation function it can also
be used within the migration cockpit
▪ The customer-own migration object is displayed and
monitored in the migration cockpit (SAP Fiori) in the
same way as the migration objects delivered by SAP

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


Migration Object Modeler: Creating Your Own Migration Object II
Outlook

Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach


Unit 7: Migration Object Modeler: Focus Topics
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 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/copyright for additional trademark information and notices.
Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach
Unit 7: Migration Object Modeler: Focus Topics
Migration Object Modeler: Focus Topics
Focus topics

▪ Download and upload mapping


▪ Adapt the selection (technical selection)
▪ Transformation types
▪ Debugging the simulation

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


Migration Object Modeler: Focus Topics
Download and upload mapping

In transaction LTMOM, you have the possibility to download and upload mapping, either for dedicated migration objects or
for all migration objects within the project. Transformation Rule is called Mapping Task in the migration cockpit (SAP Fiori).

Download/upload mappings

Displays mapping tasks (transformation


rules) for object Activity type

If the selection has not yet been executed, the mapping


icon is white. You can download the mapping template
only (no values contained). As soon as the selection
has happened, the icon goes green. The system
Displays mapping tasks (transformation automatically created 1:1 mapping proposals for all
rules) for all objects within this project selected values. You can now download the mapping
template including the mapping values.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Migration Object Modeler: Focus Topics
Download options

This option downloads documentation,


Download all mappings signature, and the empty Excel template

Download only one mapping task

Mapping
documentation
Original Format: The difference in this option is that the
The program will create a local Excel is filled with values.
XML file. ▪ All values
Compressed: ▪ Created automatically – during the
The program will create a local selection of source items, the Excel is
archive file (.ZIP). filled with 1:1 entries for the fields to be
Signature mapped
▪ Created manually – a user has created
or changed mapping entries

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


Migration Object Modeler: Focus Topics
Upload options

Upload entries as released or


as unreleased

Replace old mapping or modify old mapping:


With the Replace Old Mapping button, all existing
mapping values will be deleted, imported mapping values
Select files: Choose files that Upload mapping values of the will be added.
contain mapping values to be selected rules into the system With the Modify Old Mapping button, existing mapping
uploaded. Each new selection values will stay unchanged unless they are not contained
replaces the previous one, so in your file.
you can only select files from
one local folder at a time.

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


Migration Object Modeler: Focus Topics
Adapt the selection (technical selection)

In transaction LTMOM, you can change the selection for each migration object. Note that it is your responsibility to
care for the consistency of the items to be selected.

Double-click opens
up the section below

Offers the standard select option dialog for


each field of the source table

Double-click

Remember Week 3 Unit 2 on the Here, you can choose/exclude intervals or single
focus topic “Repeated Selection” values for the selection from the source system,
e.g. select only cost centers from 1 to 100

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Migration Object Modeler: Focus Topics
Transformation types

As well as the transformation type MOVE (see example in Week 3 Unit 6), other types are also possible.

It is possible to create rules for


▪ fixed values, as you find for example in migration object FI-GL
Right mouse-click Open items for fields posting date and offset account number
▪ value mappings as, for example, in migration object FI-CO
Cost centers for field Cost center

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


Migration Object Modeler: Focus Topics
Debugging the simulation

With the Simulation button you can test how the source fields are
transferred to the target SAP S/4HANA system. You can specify
whether all the items should be involved or just some items
corresponding to criteria that you provide on the selection screen.

If required, you can debug errors directly in the target system.

Sets a breakpoint where the


migration cockpit starts to
apply the transformations
(e.g. mappings) to the
instances

Sets a breakpoint where the


migration cockpit starts to
feed the API with the
transformed instances

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


Migration Object Modeler: Focus Topics
Key takeaways: direct transfer – migration object modeler

▪ SAP delivers a standard selection based on the chosen scenario


(e.g. ERP source). This standard selection from the source system
can be adjusted
− on table level for each field of the source table
− by using filters, e.g. company code, controlling area, plant, …
▪ Mapping download and upload functionality
▪ The migration object wizard supports you in creating a migration
object. Details are added directly in transaction LTMOM
▪ Custom-own tables can be part of your migration object data model
▪ Assign a standard SAP API or custom-own API to the migration
object. If the chosen API offers a simulation function it can also be
used within the migration cockpit
▪ The customer-own migration object is displayed and monitored in
the migration cockpit (SAP Fiori) in the same way as the migration
objects delivered by SAP

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Migration Object Modeler: Focus Topics
Key takeaways Week 3

SAP S/4HANA migration cockpit: Transfer data directly from SAP system

Available for SAP S/4HANA


SAP S/4HANA

SAP Fiori App: Transaction:


Migrate Your Data LTMOM

Focus migration approach in week 3: direct transfer

Easy, flexible, and extendable:


▪ Contains preconfigured migration objects and rules
▪ Guides you through the migration process
▪ You can upload/download mappings with LTMOM
▪ You can adapt the selection with LTMOM
▪ You can create own migration objects in LTMOM
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Migration Object Modeler: Focus Topics
Outlook

Week 4: Additional Migration Topics


Unit 1: Additional SAP Offerings for Data Migration
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 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/copyright for additional trademark information and notices.

También podría gustarte