Hi, In the SAP Data Migration Cockpit, a project is created with its migration objects, assigned to a package and transport, and then moved to Quality. However, once the transport is released, I am no longer able to use the migration object for loading data in the Development system. Is this expected behaviour? I would assume not.
In our current S/4HANA 2023 system, while the object remains in change mode and is assigned to an open transport, it is available for data loading in the Fiori Migrate Your Data app. But after the transport is released, the object status changes to Not Ready for Processing and all load-related options become greyed out.
This raises a concern — how are we expected to perform test loads in Development (for new requirements or on-demand testing) if the object becomes unusable after a transport release? These projects and objects were already created and moved to Quality before I joined, but the process of creating a project, adding objects, and assigning transports should behave consistently across environments.
Could you please advise what might be missing in our setup, or whether there is a configuration aspect we need to review? Any guidance would be much appreciated.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.