My name is Heike Jensen and I am a member of SAP’s SAP S/4HANA Migration Cockpit Product Management team.
Today, I want to talk about the topic “selection”.
In the SAP S/4HANA Migration Cockpit – Direct Transfer, the step selection is a crucial step.
On the surface it looks quite “easy” – nevertheless, the logic underneath to derive the right organisational units and to decide which records or parts of records have to be selected is indeed very complex. Just think about objects where you don’t find the org units in the header table.
SAP predefines the selection criteria, e.g. in the case of an SAP ERP source system the company code. So you use one or more company codes to select from the source system.
In addition, the logic defined in the migration objects you added to your project is applied.
So what to do if you get selection results you did not expect?
- Check the migration object documentation – what is in scope and out of scope for this object
Available Migration Objects | SAP Help Portal
Pls. make sure that you choose the right release in the header of the page.
2. Check out background information in the LTMOM Deep dive slide deck
Slides 32 – 43 provide background information. On slide 40 you find an example (which refers to the object product) which illustrates how complex such a selection logic can be.
3. Have a look into the migration object definition (use transaction LTMOM)
4. Check out technical deep dive paper
We recently published KBA 3249988: Details on selection process – SAP S/4HANA Migration Cockpit – Direct Transfer. The PDF attached there explains in very technical details how the selection works. This document might help to find the root cause in case you get selection results you did not expect.
It is not possible to debug the selection as it is executed in batch.
The requirement to provide more capabilities to analyse the selection outcome is known.
I hope these explanations give a better understanding of this complex topic and the tips are of use for you.
