You’re offline. This is a read only version of the page.
58
Hello,
COntext / architecture:
I Have an OPERATIONS company, which is my parent company and centralizes all the information for all companies in the group.
My goal is to create several distinct subsidiary companies (a French one, a European one, an American one...) that retrieve, via MDM, only the OPERATIONS information that's relevant to them (for example, only France-related data for the French company)
To prepare this rollout, I created a PARAM company, which is a copy of OPERATIONS, set up for MDM: I selected all the synchronization tables I'm interested in, configured match-based coupling by choosing generally two fields per table, with "Synchronize after coupling" and "Create if no match is found" enabled.
I then copied PARAM to create my actual subsidiary companies (for example, a company "AX"). These companies automatically inherit the same MDM settings as PARAM, since they are direct copies of PARAM.
On each subsidiary company (AX), I configured MDM by choosing OPERATIONS as the parent/source company for synchronization — this is a single, active connection to OPERATIONS (PARAM only serves as the initial setup template, with no active synchronization connection).
Problem #1: local modification conflict
For a while, I didn't check the AX company. In the meantime, new vendors were created directly in OPERATIONS. The ongoing synchronization was supposed to automatically bring these new vendors into AX, but it didn't work: I got the following error:
"The data could not be updated due to the following error: Vendor record: V01276 has been modified locally since the last synchronization, and a different value for the field VAT Bus. Posting Group (FR-EXO) is being synchronized from the source record. Before retrying, open the synchronization tables, select Vendor, choose the Fields action, and either disable synchronization of VAT Bus. Posting Group, or set it to overwrite local changes. You can also choose to overwrite local modifications in the table."
I resolved this error by going to Synchronization Tables → Vendor → Fields, and checking "Overwrite local changes" on the VAT Bus. Posting Group field.
Problem #2: "account already exists" errors after resolving problem #1
Once this first conflict was resolved, I ended up with two new errors indicating that the (bank) account for certain vendors already existed. I don't understand the cause of these new errors, which seem to appear right after fixing problem #1.
Question about company-copy best practice:
When I copy PARAM to create a new subsidiary company, should I systematically:
Is this the standard procedure to apply every time a new company is copied from a template that already has "Create if no match is found" enabled, in order to avoid duplicate-record errors at startup?
Additional questions about the job queue
Thank you in advance for your help.
Share
Report
All responses (
Answers (
