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.