Hi,
We are currently structured with 1 company and 3 sites/plant. We are running Kinetic 2023.2.8 on prem.
I’ve been asked to split the company in 2 independent entities running on 2 instances (not multi company). We want to prepare for a potential future acquisition of one of the plant by another company.
Since the buyer would most likely be a competitor, we want to purge all records associated to the plant.
To preserve all the history on each side my approach was to pick a cuttoff date, similar to a go live, duplicate the database and then purge one plant and all associated records from one instance, then purge the other 2 plants from the other instance. It seemed easier than to recreate all the history in a brand new site.
However i’m not sure how to purge those records. I opened a case on EpicCare and the answer was to open a case with professionnal services. Before i do that, i wanted to know your thought on this ? Did any of you went through a similar process in the past ? Do you think it would be easier to recreate the history than to delete the one we don’t need ?
Any feedback is welcome
If you are trying to get rid of all past transactions, I would recommend starting fresh and using DMT to upload the Customers, Vendors, Parts, MOM’s, Resource Groups/Resources, Site Employees, Site Operations, Inventory, Equipment, Assets, current PO’s, Current Orders, outstanding invoices, and then restructure the GL accounts to match what the new company wants it to look like. Most of the financial and NCR records are going to be really tough to wipe without doing a direct SQL row delete, which Epicor forbids.
Since the companies will be completely separated and not communicate with each other i don’t think we will restructure the GL accounts, we will keep it as is so we can keep using similar financial reporting on both sides.
I don’t mind importing all the static data but we would like to preserve the history on both side, so that we can pull financial information at will without having to run a parallel version just to access history. The solution you offer does not seem to allow that since we can not (or can we?) import all GL transactions and the associated transaction history.
We are located in Canada and per law we have to preserve 7 years of history on all transactions for audit purposes. We converted to Epicor 4 years ago and already have another system running for the next 3 years to pull data from, we’d like to avoid having a third one.
Since we are on Prem we are willing to use SQL Delete if needed. We already did it a few times for corrupted data in the past, Epicor can’t prevent this even if we it’s not recommended without extended knowledge of what we are doing. However we don’t know yet how to approach this much larger issue. the plant column is not referenced in every subtable (example: PartRev carries the plant, but PartOpr, PartMtl etc… dont) and cleaning every single table from records related to a specific plant seems really complicated without knowing the complete Database Schema…
we had to do this years ago with one of our customers, and after very deep analysis, they decided it was better and cleaner to simply “start over” with the new company… exporting the necessary data and use DMT to import the proper data into the new instance. This guaranteed that the new instance was totally clean before they split it off. Negative on this was that the new company looses some historical records. but again, this was a decision they made that it was best going forward.