SAP S/4HANA Migration Cockpit – Import/Export Project

[Sybille]

Hi all,

in case you created your project in your DEV sytem and now need to transport it to QAS system, you can use the Import/Export functionality to transfer your project from one system to the other.

1. In DEV system use button EXPORT  


2. A zip file is beeing created.


3. In QAS you create a new migration project with the same Mass Transfer ID – this is prerequisite !!


4. Next use the Button IMPORT CONTENT in this new project.

You find more information also in the Help-Portal help.sap.com - Migration Cockpit.

Sybille

[delonndlovu]

Hello Sybille,

Thank you sharing!

Does the export work for different landscapes, e.g Sandbox to Dev, Dev to QA etc?

I am trying to do some import and I am getting an error.

 

[Sybille]

 

Hi Delon,

the Export/Import functionality is designed to tranport the content of the whole project from one system to another; so yes: Sandbox -> Dev, Dev -> Q, ...

The message you get tells you that there are some migration objects already acitve for the project you want to import. This was done manually - someone did activate a migration object in the "new" project in DEV system.

We recommand:

• Create a project in e.g. Sandbox system.


• Do the tests in this project. Export.


• Create new project in DEV - note: Mass Transfer ID must be identical! Do not manually activate migration objects here!


• Import project in DEV.

If you do have to work in a next cycle to improve your results, use the project in Sandbox, change it, export and import in DEV again. Then you will be asked for overwriting the exsting one.

sybille

[delonndlovu]

Thank you Sybille,

Your reply is correct, I am going to follow the process you recommended when we are moving from Dev to Q.

 

Many Thanks,

Delon

[former_member428300]

Hello Sybille,

When I'm importing the object. I'm getting 500 Internal server error. Please note we have follow note but the issue not resolved.

2536789 - 500 SAP Internal Server Error in LTMC

Could you please help.

Thanks in advance

Surajit

 

[Former Member]

Hi Surajit Kar,

I'm encounter the same issue. Are you managed to resolve it now?

Implemented SAP note below, but the issue not resolved,

2617067 - S/4HANA 1709 FPS00 / FPS01 - Migration - Corrections for Migration Cockpit - Q2P Scenario

Thank you!

 

[former_member428300]

Hello,

I did the below steps to resolve the internal error issue.

1. open se38

2. run program DMC_ANWDG_MWB_ACCESS

3. Select the row which has 'SLO' in it.

4. Click unlock button

 

[Former Member]

Hi Surajit Kar,

It's working now.

Many Thanks!

[Sybille]

Hello,

to solve the issues please check the following note:

https://launchpad.support.sap.com/#/notes/2628948

regards, sybille

[Former Member]

Hi ,

We have implemented the SAP Note 2628948 and 2617067 but we are getting errors after importing the Migration Project from Dev to QAS system.

 

1. Error while generating runtime objects for Z_VENDOR_007


2. Syntax error in function module /1LT/S4QOLC_100000000000007


3. The field "_CP_CTR_VEND_NUMBRG_S" is unknown, but
   there are the following fields with similar names:
   "_CASE_BOL_VEND_NUMBRG_C" and
   "_CASE_EOP_VEND_NUMBRG_C".

Could any one let me know if any one has faced this kind of issue. Please provide your help.

 

Thanks

Satish

 

 

[former_member573134]

Please follow the below steps 

1. Please Implement the SAP Note  2509954
2. Re-create the project in LTMC Transaction 
3. Re-generate the Migration Object in LTMOM Transaction.

[former_member256752]

Hello all,

I am trying to create a new project ftom ltmc in Quality system in order to import the project that i have created in development.
When i create the new project and give the same mass tranfer id as mentioned above,

I receive an error message that this mass tranfer id already exists !
I can see the project (that i have created in dev and uploaded the master data successfully in dev) in ltmc when i open it from quality system but the migration does not upload the file in QA.

Do I have to make the project inactive first and then create again with the same mass tranfer id and import the zip file ?

Thanks

[Sybille]

 

Hello Dimitris,

no - you do not have to deactivate the project.

Which release are you working on? Did you check OSS notes on this issue?

br, sybille

 

[former_member417233]

Hi,
Now MC allows working with STAGING tables.

 

Is the import/export of a project the same?

 

Thanks,

 

Thomas

[Sybille]

 

Hi,

when using staging tables the procedure is the same:

1. Soure System: Export from existing project


2. Target System: Create new project with identical Mass Transfer ID


3. Open this project


4. Import Content


5. Re-enter the project -> staging tables have to be synchronized as the old staging table names are there.


6. Start Synchronization -> that means new staging tables will be created with SYS-Id.

The created staging table get the next free number. There is no linking between objects and numbers.

We are aware that this is an issue when you have own programs for filling the staging tables - especially for go live.

We work on this and in future release we will provide kind of mapping tables.

sybille

[former_member669878]

Hi Delon,



This error itself says that "In the target system where we are importing project, there are some objects which are in other than Not started status ( In Process or Finished ) whereas in the source system, from where you exported project, you have that object in Not Started status".

Solution:

Step1: Just open the project in both source system (Development) and target system (Quality or Prod) and compare every object's status. If some object is in "In Process" status in target system and the same object is in "Not started" status in source system (Development), make it in "In Process" status in source system as well.



Step2: To make status as "In Process", just open the migration object, and come back, status will change to "In Process" from not started.

Step3: Also, in case of staging table, if you get error as“Inconsistency found, synchronize staging tables with the migration object”, 

please synchronise structure through LTMOM for that object ( choose your migration object and click on change mode -> click on Migration object -> synchronize structures ).

Step4: Just export the content again after this is done and try to import.

This will definitely work.

[lincolnsoares]

Dear,

I'm trying to create a QAS project with ID 001 to import the DEV project, but it is reported that there is already an ID 001, but as you can see, there are only ID 005.004 and 010

Thank you

[Sybille]

Hello Lincoln

from the screen shoots - everything looks o.k.

Please open an incident in component CA-LT-MC to get further investigation.

Best regards,

Sybille Lackermeier

SAP S/4HANA Migration Cockpit Product Management

[lincolnsoares]

Sybille,

I checked the TX DMC and noticed that there is a project I don't know about. I will open an incident and when I get the resolution return in this post

Thank you so much

Tx DMC

[jaynarayans]

Hi All,

I have created a custom object using LTMOM using standard Function module. It worked well in Dev.

When I import the object in Q. It worked well.

But when in Prd it imported successfully but cannot prepare.It states prepare failed. Error message unable to generate migration object.

Appreciate you advice on this

Regards

Jay

 

 

 

[Sybille]

Hi Jay,

please open an SAP Incident in component CA-LT-MC.

best regards,

Sybille Lackermeier