Migration cockpit - different approach shown for s... - SAP Community
source link: https://community.sap.com/t5/enterprise-resource-planning-q-a/migration-cockpit-different-approach-shown-for-same-project-in-same-system/qaq-p/13652442
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Thursday
I am working with a new system S4HANA ON PREMISE 2023 01 (02/2024) FPS. Anyone had similar issue?
1. I create a project in Client 100 (staging) using the fiori app "migrate your data".
2. I look at the project in Client 400 - the approach shown is "Migrate Data Using Staging Tables (old)". Obviously I couldn't create the project with old approach in a new system that has 2023 from beginning.
In client 100 it is correctly showing "Migrate Data Using Staging Tables".
3. I can't edit in 400 (wrong message that created with LTMC) and I can't change the client to 400 (dump with message "Project not found; Use F4 help to select a Project - Character String as Message" -> no message ID.
4. I tried to find a solution and saw that table /LTB/MC_PROJ has an entry in 100 but not in 400. I copied the entry directly to 400 and the approach changed and I could change the client in LTMOM -> the same moment the entry got deleted in client 100 and then had the same "wrong" approach "Migrate Data Using Staging Tables (old)". and the same issues in100 as before in 400.
Anybody having the same issues? I haven't found any note yet or any description of this error but it's doesn't increase my trust in the migration cockpit.
Thanks!
Best regards
Klaus
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK