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.