Skip to main content

Is there any documentation on the Place Merge functionality for FSM 6 that details the scope of the data that it touches?  We need to better understand all of the data that is impacted if we were to merge Place records via Place Merge or determine if we need to take a custom/hybrid approach.

Our company is currently going through a major ERP consolidation/modernization project.  All existing customer #s sourced from the old ERP system will be converted into the new ERP system which will result in brand new customer #s (there will be a reference to the old customer#) which will be integrated back down to our FSM 6 (update 25) platform.  Because of this, we will need to update all of our existing data (open Requests, some historical Request data, Contracts, Product records, customer pricing data, etc) so that they are using the new customer #s sourced by our new ERP system. 

Is the Place Merge an appropriate process to perform this mass conversion of 130k+ PLACE records? Any other suggestions from companies that have had a similar challenge?

 

Hi @TNCBSNYDER,

I believe the placemerge MPM should work for your scenario.

From what I recall, it essentially replaces all instances of the old place_id with the new one, affecting attachments, new tasks, old tasks, requests, and more.

However, to get a precise list of entities impacted by MPM, it would be best to contact IFS support.

I have worked with a customer on this MPM before, but it was for replacing one place at a time, so I'm unsure how well it will handle a bulk update.

Reply


Terms & ConditionsCookie settings