SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer

SAP S/4HANA 2020 - Migration Cockpit
Migration Object Modeler

Migrate data directly from SAP system
October, 2020
Version 1.0
PUBLIC
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
a e e b f e e e a , e ce f c da age e e ca ed b SAP e al or gross
negligence.
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, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. PUBLIC 2
Document History
Revision Date Change
1.0 03.11.2020 Release for customer
Agenda
Creating migration objects - the basics
Create an own migration object E2E example (& link to video)
Copy and delete migration objects
Adapt the selection
Transformation rules
Migrate custom-own fields and tables
How to deal with changes in objects or structures
Transport
Debugging capabilities
Further information
Organizational units and their derivation
Each SAP application uses its organizational units to structure the data. Organizational units are assigned to each other in
order to be able to process the data in an integrated way.
For each MC scenario, SAP predefines the most suitable unit to be used as
selection unit, e.g. for SAP ERP to SAP S/4HANA the company code.
Company code
Open items
When starting the selection, an
integrated selection engine
Materials derives the related organizational
units.
Plant As longs as you use SAP
Customers delivered migration objects, the
Sales organization engine ensures that all data
which belong to the selected
Cost centers migration objects of this
Controlling area company code(s) is selected.
Components of a migration object
Migration object
Data model Define selection Migration object Transformation rule / Function module
Define derivation of instance mapping
organizational unit
Components of a migration object
Migration object
Data model Define selection Migration object Transformation rule / Function module
Define derivation of instance mapping
organizational unit
3. Defines from 4. Filters derive 2. Contains the data 5. When starting the 1. Expects 6. Data is created
which tables in the relevant which is necessary to simulation or migration, dedicated fields in respectively
the source organizational feed the function the transformation rules order to be able to posted in SAP
system the units from which module. are applied to the fields create a record in S/4HANA
data is read in the data is of the instance. The the target system
order to create selected. More transformed instance is
a migration selection options passed to the API.
object instance exist.
Migration object instance
Migration object Migration object instance
Cost center ID: 123489123 SAP S/4HANA
Root table CSKS
Company code: 0001 Company code: 0001
Cost center
Cost center: 0815 Cost center: 0815 0111
Valid to: 31122099 Valid to: 31122099
API
Cost center category: A Cost center category: A
. .
Root table CSKT
KTEXT: Administration KTEXT: Administration
LTEXT: Administration DE LTEXT: Administration DE
As long as you use the delivered Migration Objects, SAP ensures that all relevant records (chosen organizational units and
chosen migration objects) are selected. The derivation of the dependent organizational units is also already part of the
delivered objects.
As soon as you start adapting the selection, adapting delivered objects or creating own
objects, it lies in your responsibility to take care for a consistent selection and a
successful migration.
Pls. refer to SAP note 2481235 for more details.
Create an own migration object E2E
example (& link to video)
Create an own migration object E2E example
Business example
Scenario SAP ERP to SAP S/4HANA is used. Gap: migration object CO Cost ce e currently (OP2020) only transfers
the master data text in the logon language. If there are also texts in other languages, an additional migration object is
needed.
In the example below, cost center KSDTGERMAN has texts in three languages: D, E and F.
SAP ERP source system
Steps in the system
Find the full demo (30 min)
Steps to be executed in the system: here:
Transaction LTMOM: create a migration object this opens the wizard
Migration object wizard
Edit the settings for all steps in the wizard
Check project in the migration cockpit (SAP Fiori)
LTMOM: source tables define selection criteria
LTMOM: target processing
Structure mapping including access path to the child table
Field mapping
Execute the selection and simulation in the migration cockpit (SAP Fiori)
Wizard for basic settings
Transaction LTMOM (in the SAP S/4HANA backend)
Here you find the COMPLETE documentation for the modeler
functionality of the Direct Transfer!
Create a new migration object
Opens the migration object wizard
Wizard - define source tables
In this example, CSKT is the root
table, CSKS the child table
The guided procedure
Often, a proposal
leads you through all
function is available
basic steps
Docu for each step
Wizard - define source tables
These three table types are possible:
Database table
Database tables exist in the ABAP Dictionary in your source system.
Manually defined table
This table is freely defined and does not exist in the ABAP Dictionary in your source system. The data
for this table is selected according to provided ABAP source code that exists in your source system.
Extension table
This table is freely defined and does not exist in ABAP Dictionary in your source system. It is
generated automatically in your control system. The system fills it with data during selection with
ABAP source code that exists in your control system.
Pls. note!
You can create or adjust tables of the first two types only. Extension tables are a specific
functionality that is rarely required in a standard case. It is used in a few SAP migration objects
created by SAP content developers, but its modification is currently not supported in the
Migration Object Modeler.
Wizard data selection
Pls. note: he i ard onl pro ides eas selec ion possibili ies. The wizard covers especially the case that you
want to define the selection by using one filter only. More advanced possibilities are provided directly in transaction
LTMOM compare slides 16 ff.
Use a filter to select the data, e.g. company code,
controlling area. The filters are delivered by SAP.
In this step you will
define the API which Use a table field to filter the records
is used for this object
Select all data from the tables defined in your
Define selection logic later, directly data model
in LTMOM. We chose this option.
LTMOM for detailed settings: source tables set filters
After you have finished all steps in the wizard, the new migration object is visible in the Migration Cockpit. Some detailed
settings have to be made in LTMOM before you can use the object.
I a ac LTMOM, g ga b ec a d c c ce ab e .
Chose the table for
which you want to
define the selection
A click on the arrow opens the popup for detailed
selection settings referring to the respective field
Which filters are needed for the current example?
T e ce a SAP ERP SAP S/4HANA edef e ec a c de a e ec c e a.
Root table CSKT does not contain the company code. Child table CSKS contains the company code. We
Therefor e chose controlling area (KOKRS) as selection chose field company code (BUKRS) as selection criteria
criteria instead. We will assign the filter for controlling area and we will assign the filter for company code. This filter
which derives the controlling area from the company code. gets its value directly from the input field of the migration
project.
Assign filter
KOKRS
Assign filter
BUKRS
LTMOM for detailed settings: assign filters
Go to the popup for selection details and assign
the necessary filters.
Assign filter KOKRS to field CSKT-KOKRS
filter BUKRS to field CSKS-BUKRS
1 Click on the arrow to
define the selection
using field KOKRS
Assign filter, e.g. filter KOKRS
3
Show available filters
2
How does the selection work for the current example?
SAP S/4HANA Popup: You select for BUKRS 0001 Start the selection in the
Migration Cockpit
Instance ID 1001 D Verwaltung 01011995 31129999
Instance ID 1002 E Administration EN 01012000 31129999
Reads Migration object definition
CSKT-KOKRS CSKS-BUKRS
SAP ERP Table TKA02: BUKRS KOKRS: 0001 0001 Applies logic of the assigned filters
Logic is delivered by SAP!
Entries from CSKT for KOKRS 0001
Selects entries from relevant tables
Entries from CSKS for BUKRS 0001
Creates migration object instances
LTMOM for detailed settings: structure mapping
After you have assigned the filters, you now map source to target structures.
2 Position cursor on cost
center list & click
assignment
1
Drag & drop structure
CSKT to structures
language and cost
center list
LTMOM for detailed settings: structure mapping, foreign table data access
In this example, we have a child table (CSKS). We have to define how the corresponding lines in table CSKS are found
this is called: foreign table data access. Each line in CSKT (root table) has exactly one corresponding line in table CSKS
ec e a e.
We c e ead
2 a e
Click this link
1
LTMOM for detailed settings: field mapping
The last step is to define the field mapping from source to target fields. Assign the fields by drag & drop. One field from
CSKS, the other 6 fields from CSKT. This creates simple MOVE rules. Find information on other rules in slides xxx.
For a better overview, display only
the fields with assignment
Drag & drop the 7 source fields to assign
them to the target fields
Check function in LTMOM
After you finished the creation of your own object, it makes sense to use the check function in order to see if the new object
is consistently defined.
Check function
Example for one of the checks:
Check options
Migration object ready to use
The new migration object is now ready to be used. As we have created simple MOVE rules there are no mapping tasks
. I ca e f f ed e a g e , d ee e ec a g a a d d be be
to edit them in the mapping task detail screen.
With release 2020, you can copy migration objects from template (from the objects delivered by SAP) and you can copy
migration objects within the same project. Also the deletion of objects is possible
1 Copy migration object from template
2 Copy migration object within the same project 2 1
3 Delete migration object (right mouse-click)
Planned for FPS01:
copy project (in the
Migration Cockpit)
3
Adapt the selection
Adapt the selection
As long as you use the delivered Migration Objects with their delivered selection settings (especially filters and inheritance
of restrictions), SAP ensures that all relevant records (chosen organizational units and chosen migration objects) are
selected.
As soon as you start adapting the selection, it lies in your responsibility to take care for a
consistent selection which fulfills the need for a successful migration.
Adapt the selection
Possibilities to influence the selection
SAP S/4HANA SAP ERP SAP S/4HANA
Filter Table field Skip rule*
Project Selection result
Records belonging to respective organizational
units are selected from the source tables. Records are transferred to the
target system.
Company Company code Restrictions on table field level are applied if Instances
codes maintained. Skip rules are applied if
Controlling area
maintained.
Migration Plant
objects
CSKS CSKT Internal tables
How can you influence the selection?
Set a filter which is Define selection criteria Write coding to skip
delivered by SAP on table field level items from selection
Define inheritance of restriction within the data model of the
migration object (affected tables)*
Restrictions => see slide 36 *new with 2020
Adapt the selection
Filters
Definition: a 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 f e a ec a c de, c g a ea, a , c a f acc ,
Filters are defined by SAP per scenario (e.g. SAP ERP to SAP S/4HANA, SAP CRM to
SAP S/4HANA Se ce, ). T e f a a ab e f e ca be ee b ec : source
tables, column selection for the respective field click on the input help of field filtering
logic (see slide 18).
The filters take care that the related organizational units or criterion are derived correctly
based on the values which have been defined in the respective Migration Cockpit project.
The rules behind the filters are not visible to customers
Derived filter values, e.g. the plants which have been derived by the company codes are
not visible to customers. Nor is it possible to change, add or delete the derived values. Pls.
check if table field restrictions can solve your requirement.
New filters cannot be created by customers
Slides 16 to 19 show an E2E example and how to assign filters
Adapt the selection
Table fields
In your migration object, under source tables, you can change the selection for this object. The standard select option dialog is
offered for each table field of the source tables.
In this example, only the texts for cost centers
1 to DE will be selected
A click on the arrow opens the
standard select option dialog
Click on the arrow to open the popup for
detailed selection settings for field CSKT-
KOSTL
Adapt the selection
Inherit restrictions (affected tables)
If you use filters and/or a restrictions on table fields, you have also to define how the selection for each source table at
level >=2 impacts other tables.
You find this setting on the same popup as the settings for filters and selection on table fields (see path on the previous
slide).
The selection result is aggregated level by level
upwards until it reaches the root table
The selection criteria are only restricted to the current
table. There is no impact on the selection result from the
root table. But in this case, all its child tables are also
restrictive.
If you choose Selection only affects this table and any descendants, the dropdown list of
Affected Tables for all child tables will automatically not be editable.
If you choose Selection affects the entire migration object instance, the dropdown list of
Affected Tables for the first level child tables will be editable.
Adapt the selection
Inherit restrictions (affected tables) example
The below example for migration object product explains the logic of this setting. This example does not represent the
complete data model, it is a reduced and schematic representation!
Detailled view on tables MARA contains no field which is suitable for an
MARA organizational derivation.
MATNR MARC In order to migrate only the material numbers which belong
MATNR WERKS to the relevant company codes, the filter WERKS is set on
AAA
subordinated table MARC. The filter WERKS finds in
AAA 1000
BBB MARC all MATNR which are assigned to plants belonging to
AAA 2000 the chosen company codes.
CCC BBB 2000 The setting Selection affects the entire migration object
Source tables and filters
BBB 3000 instance has to be set. This means only when a MARC-
DDD
MATNR record is relevant, also the MARA-MATNR record
CCC 4000
MARA will be selected.
DDD 5000
Will the settting Selection only affects this table and any
descendants be set, all MARA-MATNR would be selected,
WERKS_FILTER no matter if a suitable MARC-MATNR is found. This will lead
MARC WERKS WERKS BUKRS: 1000 to errors during simulation/migration in case of MARA
records without corresponding MARC records.
1000
2000
Adapt the selection
Skip rule
In your migration object, under source tables, using button Advanced selection settings, you can access the so-called skip
e. Y f ge e a e e e. I f e ce c de a d be d a ed de ec b ec . W the
pen button you access the source code. Here, you write your individual coding to skip items from the selection. As the skip
rule consumes more runtime in comparison to other possibilities, only use this rule if necessary.
First, click on
generate. The
button changes
then to the pen
The rule is called from the target system after receiving corresponding data button.
for an instance from the source system and before creating a new instance
and adding it to the instance list. The selected data is passed to the rule by
its import parameters, so you can apply your criteria to the data and provide Here you put in your
your decision in the export parameter _EV_SKIP_RECORD. coding
Adapt the selection
Restrictions
These three types of selection criteria (filters, table fields, affected tables) can only be
applied at data base table level.
If you add some manual definition tables or extension tables, you cannot set these
selection criteria.
In addition, if your data base table is a cluster or pool table, you also cannot set these
selection criteria.
If the header table is a cluster or pool table, the selection criteria cannot be applied to
all the tables.
Skip rules can be applied for any kind of tables.
Basics & rule types
The Migration Cockpit uses transformation rules to change values that are migrated from source fields to target fields. You
can use existing rules or create your own rules and assign them to the target fields in the Field Mapping.
In the Migration Cockpit, transformation rules are called mapping tasks.
The delivered Migration Objects already contain predefined mapping tasks.
The following rule types exist:
Fixed Values
Value Mappings
Source Code*
*new with 2020
Basics & rule types
After you executed the selection from the source system, the mapping values are
visible
In the Migration Cockpit, only the mapping tasks which have values after the selection
are displayed. If you go to download mapping templates, all mappings which are
basically available for this object are offered. In transaction LTMOM, you also see all
mapping tasks.
You can only upload mapping values using transaction LTMOM as long as the object
has not been migrated. In the Migration Cockpit (Fiori), value editing is always
possible. Besides the blocking of upload after migration, there is currently no locking
functionality for mapping values.
Source code rules and MOVE rules are not displayed in the Migration Cockpit (under
mapping tasks), only in transaction LTMOM
The SKIP rule (influence selection) is a source code rule
Transformation rules can be transported. Values are never transported, they can be
downloaded and uploaded.
Download / upload of mapping values
Mapping values can be downloaded / uploaded in the Migration Cockpit (with 2020) as well as in transaction LTMOM (since
1909).
LTMOM
Upload/download all templates Upload / download
and / or mappings for your Upload / download functionality
project! mapping values
Upload / download
mapping templates
Migration Cockpit
Create an own transformation rule of type mapping E2E example
In the following example, a custom-own transformation rule of type mapping is created. It will map long texts for cost
centers. This new mapping task will be assigned to the migration object Z_KOSTL_DT_TEXT. Back in the Migration
Cockpit, selection will be executed (again) and mapping will be edited.
Right mouse-click on the rule type and Decide if you create a rule which is valid in the whole project or
choose Create. In this example, the rule is only for a dedicated migration object.
only valid for object Z_KOSTL_DT_TEXT.
Define the name of the rule
E2E example create mapping rule
Define suitable import and export parameters for the rule. In this example, import parameters are: KOKRS, SPRAS, LTEXT,
export parameter is: LTETXT. Activate and release the new rule.
Activate the rule
Import / export parameter
Release the rule
E2E example assign mapping rule
G efed a g, f e d DESCRIPT currently, a simple MOVE rule from the previous example is assigned.
Double-click on the line and assign the newly created rule MAP_KOSTL_LTEXT (type mapping). In case it is a rule only
valid for the current object change the rule list display to the object.
Use F4 help
Assign new rule
MOVE rule assigned from
previous example
E2E example assign field mapping
Define the import parameters for the rule. Use F4 for choosing import parameters: IV_KOKRS => CSKT-KOKRS,
IV_LTEXT => CSKT-LTEXT and IV_SPRAS => CSKT-SPRAS. Export parameter EV_LTEXT is set automatically.
After you closed the popup, you see the newly
assigned transformation rule of type mapping
Move rules
Newly assigned
mapping rule
Also fixed value or system variable
© 2020 SAP SE or an SAP affiliate company. All rights reserved. PUBLIC
are possible here 45
Excursus: assign rules for documents (multiple lines)
For migration objects which create postings (e.g.
open items), an open item line (OI) and an offset
line (OL) is created by the API. This means, the
rule assignment has to be made for each of the
lines.
In the example below, the open item line is filled
with a cost center by using mapping rule
KOKRS_KOSTL. For the offset line, the cost
center is initialized.
Open item line and offset line
for the object FI G/L open
items Rule assigned to open item
line, offset line is initialized
E2E example create mapping proposals during the selection
The last step is to define that this mapping rule automatically creates mapping values. You see these mapping entries
in the Migration Cockpit as well as in LTMOM after the selection has been executed. Go to target API and click your
transfer step.
In 1909, the feature to fill
source and target mapping
values for custom-own rules
automatically is not yet
available. You have to
download the mapping
template, fill it with source
and target values. Then
upload it in LTMOM.
Click the plus button, this opens
a popup
E2E example create mapping proposals during the selection popup with details
Entries with import parameters are
inactive, they are for your information only
(that means showing you source values of
your value mappings). Define how the
The export parameter defines how generated mapping should look like
the mapping values are filled (that means which target value the system
automatically. In this example, the should set). You have several options:
source value shall be proposed as Fill with a fixed value
target value. Fill with a system variable
Leave the target value blank
Import parameter or source value
Detailed docu!
E2E example create mapping proposals during the selection return transfer results
In case of internal numbering or if your object has multiple transfer steps (as e.g. in migration object fixed asset), the
target mapping values have to be returned back (after the mappings have been applied/created).
Assign the parameter which will
store the target mapping value
After you edited the transfer result entry, you can
then chose the update from transfer result and
assign the right step
Go to the details
Use F4 help to find
the parameter
E2E example use check function
After the creation of the mapping rule, the screen looks like shown below. Use the check function before you go ahead.
Use the check function
The new mapping rule is
ready to be used now
E2E example result in the Migration Cockpit
Go back to the Migration Cockpit and execute the selection (again). After that you see the mapping task
MAP_KOSTL_LTEXT. You can go into the detail screen and edit the mapping values.
E2E example all standard functionality available
The system automatically creates the according mapping templates. You can use all standard functionality for mapping
tasks for your customer-own rule, too.
Download template
Mapping template
Migrate custom-own fields and tables
Migrate custom-own fields
If there are field extensions (custom-own fields resp. Z-fields) the Migration Cockpit recognizes it.
Ta ac LTMOM d a e efed eMg a Ob ec de ce ab e a ce f e d .
If and how the custom-own field can be migrated to the target system depends on how the BAPI used in the Migration
Object is designed.
For function modules, three different concepts exist:
Function modules which contain includes or append fields
BAPI function modules with extension fields type 1 (e.g. BAPI_MATERIAL_SAVEREPLICA)
BAPI function modules with extension fields type 2: with or without X-fields
In all cases, the includes and append structures have to be edited by the customer (transaction SE11).
The user needs deep DDIC knowledge and ABAP development authorization.
If you want to create an own function module, see SAP Note 2590165.
Migrate custom-own tables
The SAP S/4HANA Migration Cockpit is able to migrate custom developments such as
additional Z-fields in standard objects or
completely individual custom objects
Design of the Migration Cockpit
Instance based processing => each(!) line of the root table in the source structure definition is treated as instance
Each sender record becomes an instance and is treated as single instance while transferring the data
This makes sense for processing of an instance as a whole entity (usually an instance consists of several source
tables, which entries have a relation to each other via foreign key relations)
The target API is doing plausibility checks f eac a ce bef e c ea g e a ce DB e e . A g
principle per instance to create/update only logically consistent instances.
If a simple 1:1 table transfer without the need for any transformations,
plausibility and consistency checks, the development of an own RFC-
enabled function module (currently used API just RFC-enabled) and a Z
program which is retrieving the data from the Z table and transfers it 1:1 from
sender to target should be considered.
How to deal with changes in objects or
source structures
How to deal with changes in objects or structures
Updates in ABAP Dictionary objects
Migration objects refer to ABAP Dictionary objects (for example database
tables) and repository objects (for example function modules). The
migration cockpit can compare the available definitions in the migration
objects with the structures of the ABAP Dictionary objects. The
synchronize function checks if there are changes (e.g. additional
importing fields) and adapts the migration objects accordingly.
Updates in Migration Objects
Your might have updates regarding the content of a Migration Object,
e.g. because you implemented a TCI content note or implemented a
feature pack (FPS).
If you now want to use the updated Migration Object, with release 2020
FPS1, you can use the create from template function to copy the updated
migration object into your project. In release 1909, you have to create a
new project manually and assign the updated migration object.
Transport
Transport
Migration Cockpit
Since on-prem version 2020 the approach Direct Transfer is connected to the SAP transport management. Projects in non-
editable systems (e.g. quality and production) are accessible in display mode only.
Note that it will not be possible to change
the scenario or the development package
after you create the project.
When creating a project, you have to
assign a development package. If you
use $TMP, the project will not be
transported.
Transport
LTMOM
In transaction LTMOM, you can add projects, migration objects, and rules to a transport request. If you add a project to a
transport request, then all migration objects and rules in the project will also be added to the transport request.
Rule values, for example mapping values are not included in the
transport. They have to be brought by download/upload into the
system.
If you add a migration object to a transport
request, then all rules that are used by the
migration object will also be added to the
transport.
Only the definition of a rule is added to a transport
request.
Already since release 1909 there are debugging capabilities for transformation and simulation. Go to transaction LTMOM
and change to the edit mode. After you clicked on a migration object, you see the simulation function. This opens a
program.
Select the instances you
want to debug
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
Further information
SAP S/4HANA migration cockpit
Migration object modeler for file/staging
Migration Object Modeler File/Staging
SAP S/4HANA migration cockpit
Complete overview presentation
SAP S/4HANA Migration Cockpit 2020 / CE2008
Data Migration Landing Page on SAP S/4HANA SAP Help Portal
SAP S/4HANA migration cockpit further training material
*
* openSAP Course based on 1909
SAP S/4HANA migration cockpit community
One-stop shop free access
Latest news
Blogs
Q&A section
https://community.sap.com/topics/
s4hana-migration-cockpit
FAQ
Preconfigured SAP S/4HANA sandbox system
Demo scripts for SAP S/4HANA migration cockpit available
SAP S/4HANA trial system (external link):
https://www.sap.com/cmp/oth/crm-s4hana/s4hana-on-premise-trial.html
Demo scripts for SAP S/4HANA migration cockpit
File approach (bank)
File approach (material) LTMOM - file approach (cost center
texts)
Staging approach (G/L accounts)
Direct Transfer approach (cost centers and activity types)
LTMOM Direct Transfer approach (cost center texts)
Direct Transfer approach (material)
Direct Transfer approach (vendor, CVI)
https://blogs.sap.com/2019/04/23/sap-s4hana-fully-activated-
appliance-demo-guides/
System access for externals
External CAL: https://cal.sap.com/catalog#/solutions/52c66f34-9174-4692-b64d-4c34b955d9bc
Follow us
www.sap.com/contactsap
© 2020 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,
a d SAP SE aff a ed c a e a eg a d bef e de e e , d c , a d/ af , d ec , 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.

SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer

Uploaded by

Copyright:

Available Formats

You might also like

SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer

Uploaded by

Copyright:

Available Formats

SAP S/4HANA 2020 - Migration Cockpit

Migration Object Modeler

You might also like