Merging 2 companies with different Chart of Accounts

pfd

Reputable Poster
We are running an instance of JDE Xe. We are planning to bring another company (that also runs on JDE Xe) to our JDE instance. We are thinking that we will bring their data as is without any changes. They will be their own company. We are aware that because we now share the same instance there could be duplicates in item masters, address book, UDC values etc. So we will try to remedy that. But is it possible to bring their Chart of Accounts. How do we handle duplicates in the account structure? Should we try to merge the chart of accounts? The reason we are trying to bring them on without changes is because of resources/funding constraints. If we had resources we would obviously merge the two chart of accounts. Has anybody attempted anything like this? What would be some recommendations? Any suggestions would be appreciated.

Thanks,
Matt
 

jimjung27

Active Member
If you don't need to print consolidated reports and consider the two companies separate entities, then you may consider keeping their data in their own database. You can have one set of objects (screens, reports, tables, Business Views, etc) all in one OMW. And two databases. When you login to E1, you can choose the database that will be used.
 

peterbruce

Legendary Poster
Matt,

Looking at the Chart of Accounts only, your biggest problem is going to be the Account IDs (AID). There are going to be thousands of duplicate AIDs. The AIDs would be a headache to change - there are thousands of them and they are everywhere. Duplicate Business Units can be worked around (P09812/R09812 - Global Business Unit Change; R09806 - Global Update BU/OBJ/SUB to F0902/F0911 from F0901). But duplicate AIDs are probably the game breaker when it comes to merging the Charts of Accounts.

There are two options I can think of:

1) Create a 2nd production environment with the same pathcode as your current production, but different business data and control data datasources. Be careful of your Next Number tables.
You may even wish to treat a 2nd production environment as a history/archive and import data into the existing production as with option 2.

2) Import the data just like it was coming from a different ERP (eg SAP).
 
Last edited:
Top