+4hi folks,
Can someone please advise how you did the data migration for Open projects (Projects in Approved, Started status) from apps 10 to IFS Cloud?
These projects have in progress activities with different types of cost/revenue recorded on them. The same numbers should be visible in IFS Cloud.
Any thoughts on this would be much appreciated.
Thank you,
Ashani
Best answer by desilvasachitha
Hello
This is an interesting topic, since my operating principle has always been to recommend clients to close the open items in legacy system and start afresh in IFS. However, as you’ve highlighted reality is that there will always be leftover projects that needs migrating at the cutover.
An important aspect of migrating WIP projects is that we cannot directly migrate them in “Approved” or “Started” statuses (either via DMM or alternative methods), what typically happens is we first deal with Master Data and then work on the Transactional data.
Hence, we first bring over the Project (Sub Projects, Activities, Activity Estimates, Project Sites - all of these have separate data migration containers). It is important to note that we bring the Project over to IFS in “Initialized” status and then execute migration jobs to promote the status to either ‘approved’ (we need to configure the project group that needs to be brought in when approving the project) or ‘started’.
As the secondary step we bring in Transactional Data (using separate set of data containers) - here I would normally merge the certain direct project related migrated costs and put them in to a project transaction e.g., all the project time/cost reporting can be lumped together to a single project transaction that uses a unique report code called “MIG COSTS ”.
Then comes the tricky question - are you migrating other objects that sends costs to these WIP projects like WOs, POs and SOs. If that is a ‘yes’ then you have to check the feasibility of migrating them with relevant ‘Activity Sequences” if you want to have that level of granularity but you have to tread carefully here as this method could be cumbersome and error prone.
Hope this helps!
Cheers!
Sachitha D
+12Hello
This is an interesting topic, since my operating principle has always been to recommend clients to close the open items in legacy system and start afresh in IFS. However, as you’ve highlighted reality is that there will always be leftover projects that needs migrating at the cutover.
An important aspect of migrating WIP projects is that we cannot directly migrate them in “Approved” or “Started” statuses (either via DMM or alternative methods), what typically happens is we first deal with Master Data and then work on the Transactional data.
Hence, we first bring over the Project (Sub Projects, Activities, Activity Estimates, Project Sites - all of these have separate data migration containers). It is important to note that we bring the Project over to IFS in “Initialized” status and then execute migration jobs to promote the status to either ‘approved’ (we need to configure the project group that needs to be brought in when approving the project) or ‘started’.
As the secondary step we bring in Transactional Data (using separate set of data containers) - here I would normally merge the certain direct project related migrated costs and put them in to a project transaction e.g., all the project time/cost reporting can be lumped together to a single project transaction that uses a unique report code called “MIG COSTS ”.
Then comes the tricky question - are you migrating other objects that sends costs to these WIP projects like WOs, POs and SOs. If that is a ‘yes’ then you have to check the feasibility of migrating them with relevant ‘Activity Sequences” if you want to have that level of granularity but you have to tread carefully here as this method could be cumbersome and error prone.
Hope this helps!
Cheers!
Sachitha D
+4hi
Many thanks for your detailed explanation.
I understand your comments & the approach you have suggested, however the customer’s legacy system is IFS Apps 10. They do have a requirement of migrating “Open Orders” such as POs, SOs etc. This is the challenge we are facing currently. We are not doing this as an Upgrade unfortunately (that would have been an easier approach, I am aware)
Any thoughts on doing this as a migration from your past experiences ? Any lessons learnt/mistakes to avoid ?
Best,
Ashani
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.