Migration Cockpit 2020 - Make Project available in Client

[estescholtz]

Hi,

When making a project available in another client, what happens technically behind the scenes?

If I created projects in, example client 100, I can see these projects in the Fiori front-end in client 200. However, I am not able to edit the project or its objects via LTMOM in client 200.

If I make a project available in client 200, I can no longer see it in the Fiori front-end in client 100, but I can see the project and its objects in LTMOM in client 100.

Reason for the question is: if all projects have been created in client 100, and then made available in client 200 and if client 200 gets trashed, would I be able to make the projects available again in client 100? Are the objects still cross-client as with the older LTMC version?

Struggling to understand how this functionality of making projects available in another client works and I cannot find any documentation explaining it in detail.

Regards,

Esté

[estescholtz]

Hi Prithvi,

Thanks for responding.

When you say transport, do you mean using the export/import functionality? According to my understanding, transports for Migration Cockpit are only used when you use the direct transfer option.

We are using staging tables and I am not being asked to create a transport when I either create a new project/object or copy an existing object.

In the documentation, it states the following: "Projects created in Fiori App can only be seen and changed in the client where the project was created."

In our scenario, this is only true for client 100. Even though all projects are "assigned" to client 100, I can see all projects in client 200 via Fiori. When I make a project available in client 200, I can no longer see it in client 100 via Fiori. So I am not understanding why the two clients are behaving differently.

Also, we are not in the QA system yet. We are busy setting things up in DEV and will have multiple clients in the DEV environment. Therefore I am trying to understand how this is supposed to work.

My other question is - if a project is available for client 100, but I can see it in client 200 and it looks like I'll be able to upload a file in client 200, where will it load the data to?

Kind regards,

Esté

[prithvispandana]

Hello,

This is a new feature and works as design.

The purpose of this feature is to transport migration project/object as repository object from development system(editable) to quality/production system(non-editable).

Therefore after closing the changes for a (sandbox)client, creation/deletion migration project/object is not allowed and the Create/Delete button disappear.

Hope this helps you!

Thanks,

Prithvi