Skip to main content
Solved

IFS Cloud 22R1: Data Migration Manager Legacy data files structures

G
Sidekick (Partner)
Forum|alt.badge.img+9
  • GaSoGB
  • Sidekick (Partner)
  • 85 replies

Hi All,

When we do Data Migration using old Data Migration tool, we create legacy data file structure based on the Migration job we write.

For example assume we need to migrate Customers.

In the csv file we define headers as CUSTOMER_ID, NAME,CUSTOMER_CATEGORY,DEFAULT_LANGUAGE etc. based on the DM job column order  and then fill data in csv file  accordingly.

Based on new tool ‘Data Migration Manager’ documentation, it looks like we do not need to do this anymore. Instead we can export legacy data into csv files as it is in the legacy system  and then import them into IFS Data Migration manager. After the import it looks like we can map legacy data into target tables as we require.

We can also use dblink in order to map legacy data tables into target tables as well.

 

Could someone explain and confirm if my understanding is correct?

 

 

 

Best answer by mmol

Hi @GaSoGB ,

In the old migration tool we indeed defined the headers like CUSTOMER_ID, NAME etc. as these were the column names for the IC table.

 

In the new data migration manager these headers are indeed less important. In the back IFS stores the legacy data in one big table. This table holds columns like C1, C2, C3 etc. This is fixed. That means that if you have CUSTOMER_ID and NAME columns, these end up in the columns C1 and C2 of this legacy data table.

 

So when you are going to do the mapping of your legacy data you see two columns. On with the more functional column name and one column with the technical column name, which is C1, C2 etc. Eventually IFS uses only the C1, C2 column names. That is why the column names you provide in the CSV doesn't matter anymore.

 

Please note that when you add a column in your legacy data, do it at the end as otherwise you have to redo the complete mapping. We can no longer add columns in between like we could do in the old migration tool.

 

Hopefully this information will help you a bit.

 

Kind regards,

Michael

 

 

View original
Did this topic help you find an answer to your question?

2 replies

M
Hero (Partner)
Forum|alt.badge.img+7
  • mmol
  • Hero (Partner)
  • 17 replies
  • Answer
  • August 25, 2022

Hi @GaSoGB ,

In the old migration tool we indeed defined the headers like CUSTOMER_ID, NAME etc. as these were the column names for the IC table.

 

In the new data migration manager these headers are indeed less important. In the back IFS stores the legacy data in one big table. This table holds columns like C1, C2, C3 etc. This is fixed. That means that if you have CUSTOMER_ID and NAME columns, these end up in the columns C1 and C2 of this legacy data table.

 

So when you are going to do the mapping of your legacy data you see two columns. On with the more functional column name and one column with the technical column name, which is C1, C2 etc. Eventually IFS uses only the C1, C2 column names. That is why the column names you provide in the CSV doesn't matter anymore.

 

Please note that when you add a column in your legacy data, do it at the end as otherwise you have to redo the complete mapping. We can no longer add columns in between like we could do in the old migration tool.

 

Hopefully this information will help you a bit.

 

Kind regards,

Michael

 

 

G
Sidekick (Partner)
Forum|alt.badge.img+9
  • GaSoGB
  • Author
  • Sidekick (Partner)
  • 85 replies
  • August 25, 2022

@mmol ,

 

Thanks a lot Michael for your clarification and tips.
I would have thought so but it is not that clear in the IFS Documentation. :(

 

Best regards

Gayan S

 

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings