Skip to main content

Hi All,

 

Do IFS have a document which has the correct object migration sequence?
In most cases, Data Migration specialists working on IFS data migration using Data Migration Manager do not know about IFS. 
So they do not know for example you have to migrate ‘Master Part’ first before migrating an Inventory Part,
It would be useful ,If we have a simple document which has the correct order of performing migration for at least commonly used Migration Objects.

 

@GaSoGB This is a tough cookie as each company may have a different set of data to migrate. Just giving a sequence that we are thinking about:

  1. Customer
    1. Customer information
    2. Customer Info Address
    3. Identity Invoice Info
    4. Customer Order Info
    5. Communication Methods
    6. Identity Payment Info
    7. Payment way per Identity
    8. Payment Address
  2. Customer contacts
    1. Person Info
    2. Customer Contact Info
    3. Communication Method
  3. Supplier information
    1. More or less the same as for customers
  4. Supplier contact information
    1. More or less the same as for customer contacts
  5. Parts
    1. Master part or part catalog
    2. Engineering part master
    3. Engineering part revision
    4. Non-Inventory sales parts
    5. Inventory part
    6. Inventory sales parts
    7. Purchase Part
    8. Supplier for purchase part
  6. Sales prices
    1. Sales base prices
  7. Projects
  8. Sales contracts
  9. Service contracts
  10. Employees
  11. Employee absences

I've not filled in everything. The most important is that you build in layers. What is mandatory for a table. If that is basic data prepare it, if it is another master file, prepare that first. That is also why you see transaction type of tables at the end, first the base then the rest.

@GaSoGB @eqbstal I also would love this information. Now after some time working with IFS you start to understand the order for example, looking into the entity configuration you can see which columns are referenced so you know what extra tables you need before migrating your view. 

 

I once saw a screenshot like this, but no idea from which applications this comes.

 

@kvbe Image seems to be coming from a product from ETLWorks. I've never seen it. I have the idea that it is the result of scanning all the views and presenting it in a handy way. In this situation, SupplierInfoAddress has key fields. They lead to other LU which have properties (fields). If the scanning is done per view, all the selectable views in the left navigator will show the same form of snowflake. It gives a grasp of how the database is setup. There is nothing about sequence in here I would say.

Reply


Terms & ConditionsCookie settings