HOT NEWS (18.02.2022):
SAP S/4HANA Migration Cockpit – Direct Transfer: Top 5 FAQs (as of Feb 2022) | SAP Blogs
HOT NEWS (18.05.2021):
We have released new material on the following topics:
HOT NEWS (23.03.2021):
We have released a new video. It demonstrates the
enhanced error analysis capabilities which come with 2020
FPS1 for file/staging and direct transfer.
Different views on messages are possible:
Activity – which messages occurred?
Message – which instances are concerned? NEW WITH 2020 FPS1
Migration object instance – which messages occurred?
https://sapvideoa35699dc5.hana.ondemand.com/?entry_id=1_yqbyc0ze
If you are interested in more deep dive material on the Migration Cockpit, pls. visit our landing page!
LINK
HOT NEWS (02.02.2021):
We have released a video: How to create an own mapping rule (OnPrem 2020): LINK
Enjoy
🙂
HOT NEWS (11.11.2020):
We have released a lot of material (PDF, videos, click-troughs) on our Migration Cockpit landing page:
landing page
Click on
News => get to the development news for Onprem 2020
Click on
Training and Education => some examples:
Deep dive Direct Transfer LTMOM => get real deep insights on how to use the modelling environment
Customer/Vendor integration in Direct Transfer
... take your time to surf all the material!
The SAP S/4HANA Migration Cockpit offers different approaches. Since 1909 there is a third approach available: transfer data directly from an SAP system.
In this blog and the linked blog posts I will provide
deep dive material on the Direct Transfer approach.
If you are looking for
more general or
overview information pls. go to the SAP S/4HANA Migration Cockpit starter blog:
LINK
There is an
openSAP Course available which gives insight into all three approaches - on a very detailed level! It also treats the topic how to create own migration objects. You can download and/or view a huge amount of PPTs & videos. The hands-on experience is still possible for another 2 months, afterwards you can use the so-called "Fully activated appliance" in order to practice.
Migrating Your Business Data to SAP S/4HANA – New Implementation Scenario
With this course, you’ll get an introduction to data migration with SAP S/4HANA, and where it fits in with respect to the different transition scenarios. The course will focus on the new implementation scenario, with a deep dive into the SAP S/4HANA migration cockpit and the migration object modeler.
Week 3 (of 4 in sum) treats exclusively the "Direct Transfer" approach - including an example how to create an own migration object. We’ll also offer optional hands-on exercises so you can better familiarize yourself with the different migration approaches. For these exercises, you can use a system image from the SAP Cloud Appliance Library.
For the Direct Transfer there is one E2E exercise where you migrate "Activity Types". In a second exercise you adapt the selection from the source system.
http://open.sap.com/courses/s4h16
Table of contents
1. General: Can a non-unicode SAP system be the source system for the Direct Transfer?
2. LTMOM: Can I create all kinds/types of transfer rules (1909)?
3. MC & LTMOM: SAP S/4HANA Migration Cockpit – Direct Transfer – Value mapping (1909) - see LINK
4. MC: Can I repeat the selection (1909)? See LINK
5. LTMOM: How can I influence the selection (1909)? See LINK
6. LTMOM: How to create an own migration object (1909)?
7. LTMOM: How to exclude a field from being migrated in (1909)?
8. LTMOM: How to add a Z-field to a Migration Object?
9. LTMOM: How can I transfer completely self-defined custom developments, for example a Z table?
ANSWERS
1. General: Can a non-unicode SAP system be the source system for the Direct Transfer?
Yes, a non-unicode should also work as source system. The MC uses RFC to connect the two systems, the RFC should do the converting automatically.
This blog post might be of use:
https://answers.sap.com/questions/4556198/rfc-from-non-unicode-to-unicode-.html . Some of the mentioned notes might be of interest.
2. LTMOM: Can I create all kinds/types of transfer rules (1909)?
In 1909 you can create:
- transfer rules of type “move” – means, you move the content of this field unchanged from the source field to the target field
- transfer rules of type” fixed value” – examples: posting date; a migration account as offset account for initial postings in the target
- transfer rules of type “value mapping” – map a source value 1:1 to a new value in the target system. Pls. note that the automatic creation of mapping proposal does not work in 1909, means you have some manual steps to do in addition (see next question).
In 1909 it is
not possible to create own source code rules.
6. LTMOM: How to create an own migration object (1909)?
This video shows how to create an own migration object.
I use the example: new migration object "Cost Center Texts".
Video (37 min):
LINK
Slides shown in the video:
LINK
7. LTMOM: How to exclude a field from being migrated in (1909)?
To exclude fields from the transfer you have to
remove the field level mapping of data
for the respective field that you do not want to migrate. It
depends on the respective API used for this migration object if this approach works. It only works if the API supports migration
without the respective fields being mapped.
Starting 27:08 you see how to maintain the "field mapping" in the Direct Transfer approach for a migration object.
Link demo video create own migration object (Direct Transfer)
8. LTMOM: How to add a Z-field to a Migration Object?
If there exist z fields (SAP standard table is enhanced by a custom-own field) in the source system, the Migration Cockpit, Direct Transfer, recognizes it and these fields are automatically shown in LTMOM as source fields. In case there exist target fields which match, the Z source fields can be mapped in LTMOM in the field mapping to the target fields.
Pls. note: only primary structures (parent and child tables) of the data model can be adapted.
There may be single cases where Z fields are not covered by the API which is used in the migration object. In this case pls. open a ticket on component CA-DT-MIG.
9. LTMOM: How can I transfer completely self-defined custom developments, for example a Z table?
Create your own API and use it in your own migration object. The pre-requisites for an own API are quite the same as the
BAPI definitions in the
BAPI Programming Guide (
Implementing the Function Module). The API must not execute 'COMMIT WORK' commands.
Heike Jensen
Product Management SAP S/4HANA Migration Cockpit
