Week 2: Migration Object Modeler (File/Staging)

Unit 5: Simulating and Debugging a Migration Object

Simulating and Debugging a Migration Object
As of 1809
Simulate import of file migration objects

Simulate Import in LTMOM Save First Erroneous Record for

Debugging

Only available in change mode

Debug Saved Record Delete Saved Record

Program: DMC_MC_MIGOBJ_EXEC_SINGLE_OLO Program: DMC_MC_MIGOBJ_EXEC_OLO_DELETE

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

Simulating and Debugging a Migration Object
Prerequisites for debugging – File approach
You need to download a file template using
either transaction LTMC or transaction LTMOM
(possible as of 1909). You can then enter
values in the file that you want to simulate or
debug.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
As of 1809
▪ The migration object was generated successfully
▪ A simulation parameter is defined in activity
Target Structures API
▪ The migration object is not locked by any other
user
▪ If the migration object is copied from a template, it
must not have any outdated objects (Update
Available  No)
3
Simulating and Debugging a Migration Object
As of 1809
Steps to execute a simulation run for debugging – File approach

Documentation on Simulation / Debugging

1. Choose the migration object

2. Select the filled template Excel-XML file
3. Choose Execute (F8)

The file that you upload is only stored

temporarily for the duration of the
simulation, and is then deleted from
the system.

Program: DMC_MC_MIGOBJ_EXEC_FILE

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

Simulating and Debugging a Migration Object
As of 1809
Breakpoints for debugging – File approach

You can choose two breakpoint options

▪ Before the conversion takes place
▪ Before the data is written to the target
system
Note: This option will not be visible for
productive systems

Program: DMC_MC_MIGOBJ_EXEC_FILE

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

Simulating and Debugging a Migration Object
As of 1809
Debug in target system – File approach

Option to save data if error occurs

If you choose this option the system will
save the relevant information about the first
erroneous record that was encountered in
the file.

As of 1909 you can view the simulated

records
▪ You can view these records before they
are converted
▪ or after they are converted
Program: DMC_MC_MIGOBJ_EXEC_FILE

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

Simulating and Debugging a Migration Object
As of 1809
Debug and delete debugging run – File approach

To debug the saved record in the target system, you can choose
Goto → Debug Error (program DMC_MC_MIGOBJ_EXEC_SINGLE_OLO)
To delete the saved simulation run choose
Goto → Delete Run (program DMC_MC_MIGOBJ_EXEC_OLO_DELETE)

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

Simulating and Debugging a Migration Object As of 1809
Simulate import of staging migration objects FPS01

Simulate Import in LTMOM Save First Erroneous Record for

Debugging

Debug Saved Record Delete Saved Record

Program: DMC_MC_MIGOBJ_EXEC_SINGLE_OLO Program: DMC_MC_MIGOBJ_EXEC_OLO_DELETE

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

Simulating and Debugging a Migration Object As of 1809
Simulate import of staging migration objects II FPS01

Additional information available

You can choose one of the following options

to decide which entries should be taken for
the simulation:
▪ Select All Records
▪ Select Max. Number of Records (random)
▪ Select Specific Records (there is currently
a technical restriction that the specific
selection is not case-sensitive)

Program: DMC_MC_MIGOBJ_EXEC_STAGING
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Simulating and Debugging a Migration Object
Migration object modeler – Simulate import / downport for lower releases

SAP Note 2665339 contains program DMC_MC_SIMULATE_IMPORT_STAGING to perform an

import simulation for a staging migration object for 1709 FPS01 and FPS02 and for 1809.

SAP Note 2630183 contains program DMC_MC_SIMULATE_IMPORT_FILE to perform an import

simulation for a file migration object for 1709 FPS01 or FPS02.

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

Simulating and Debugging a Migration Object
Key takeaways

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

Available for SAP S/4HANA

SAP S/4HANA

Transaction:
LTMOM

Flexible and extendable

Easily integrate custom objects and enhancements into the migration project
▪ Adapt the delivered content (SAP migration objects) to your needs
▪ Add a field in the Excel template or staging table
▪ Create your own migration objects to transfer customer-specific data
▪ Create your own rules to add customer-specific messages or masking/pattern rules
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11
Simulating and Debugging a Migration Object
Outlook

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

Unit 1: Getting Started
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12
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.