Hello, we’re in the process of setting up another company in our PILOT environment. We’ve decided to utilize the Global setting for certain tables but I’m having trouble getting it working.
So far I’ve done the following but still do not see any data flowing from Company A to Company B.
- External Company Maintenance
- Set up external company in both locations
- Multi Company Direct
- External Company Configuration
- Set up modules that will be sent over in both locations
- Multi Company Direct
- Send GL Accounts, Global COA, Customers, Part, Supplier, AR, AP
- Global Table Maintenance
- Specified what tables and fields will be sent over in both locations
- Multi Company
- Tables: COA, Part, Vendor, Etc
- Multi-Company Direct Server Process
- Ran it in Company A
- Filter contained Company B
I’ve read through the “Kinetic_techrefMultiSite_2024.2” a couple times but still don’t see what step I may have missed. Is there anything else that needs to be configured for Global tables to work?
Hi Rakesh, I ran Multi-Company Direct server process in Company B and the only thing that flowed over was the COA which is great because that was the first priority but none of the other tables such as Part or Vendor appear in Company B.
I double checked External Company Configuration and Global Table Maintenance to verify I had the module enabled and the fields mapped but is there anything else I can check on my end?
Forgot to mention in my original post that I also enabled the “Global” checkbox on a few parts and vendors in Company A.
Lesson learned: Do the Multi-Company Direct Server Process in both companies in a process set. This will make sure one finishes before the next one starts.
Global data does not typically flow through until the data is linked. You will have to either link an existing part to the global part, or create a new one by running the link.
A couple of warnings. All data must be the same in both companies unless you put in data in the translation tables. UOMs, Class ID, Product Code, etc… Those aren’t global but to prevent errors in the future, keeping that data consistent between companies will make for an easier sharing experience.
Also, the Integrated Table Workbench will be your best friend at the beginning. When data doesn’t flow after it’s linked, it’s there that you will see why.
I’ll plan to do the process set next time I run it but you made some good call outs. I haven’t set up the UOM, Class ID, Product Code, etc in Company B and I bet that’s what’s preventing the parts from flowing over.
I would still think Vendor and the other tables should flow over though right?
As for Integrated Table Workbench, I do see a few items queued up for GLAccount but there isn’t any associated error messages or other tables showing up.
