Guide for groups with several company databases

Intercompany master data in SAP Business One: who owns what, and in which order it travels

A head office and its branches, a holding with subsidiaries, a partner hosting many customers: one group, several company databases, and master data that should agree across them. The technology comes second. First someone has to say which company owns what.

1. Why there are several databases at all

SAP Business One normally keeps one legal entity per company database. A group with three legal entities has three databases, each with its own chart of accounts, tax set-up, numbering and users. That separation is what makes each company's books its own. It also means that nothing is shared: the item master of company A does not exist in company B until someone puts it there.

Intercompany work therefore has two halves. One is documents: a sales invoice in one company that should become a purchase invoice in another. The other is master data: the items, business partners, prices and set-up tables those documents refer to. The documents cannot flow until the master data agrees, which is why master data is the place to start. This guide is about that half.

2. Decide ownership before anything else

For every kind of master data, one of three answers applies. Writing them down takes an hour and saves the project.

PatternWhat it meansTypical for
One ownerOne company creates and changes the data. The others receive it and do not change the shared fields.Items, item groups, units of measure, price lists, bills of materials, the group's chart of accounts
SharedSeveral companies may change the same record, and the others should see the change.Customers served by more than one company: contact persons, phone numbers, addresses
LocalThe data belongs to one company and must not be copied.Tax groups, payment methods with their house bank, dunning terms, number series, warehouses of one site

"One owner" is one-way replication. "Shared" is two-way replication, and deserves a second look: it is only safe when the tool can tell which company changed a field, so that only a field changed in both is a conflict. "Local" needs no replication, but it does need a mapping, because shared records point at local ones: a customer replicated from head office has to end up with the branch's own tax group.

Ownership can be per field. Head office may own a customer's name, group and payment terms while each company keeps its own credit limit, sales employee and house bank. Decide it per field where it matters, not per object.

3. Codes that differ

In a group that grew by acquisition, the same customer is C20000 in one company and K-4711 in another. Renumbering a live company is rarely an option. There are three workable arrangements:

  • The same code everywhere. The simplest, and worth insisting on for everything created from now on.
  • A rule for the code. Head office's A1000 is HQ-A1000 in the branch. Useful when a company must keep its own numbering apart from the group's.
  • A cross-reference per record. A table that says which record of one company is which record of the other. Unavoidable for legacy data, and for everything SAP Business One numbers itself.

Whichever applies, the pairing has to be stored somewhere and kept when a record is renamed. If it only lives in someone's spreadsheet, the first renamed item group creates a duplicate.

4. The order in which master data has to exist

A record can only be written when everything it points at exists in the target. An item needs its item group, its unit of measure group and its price lists. A business partner needs its group, its payment terms and its price list. That gives a natural order:

WaveMaster dataNeeds first
1Units of measure and their groups, item groups, manufacturers, shipping types, customs groups, warehouses, price listsNothing, or each other
2Business partner groups, payment terms, sales employees, territories, industriesPrice lists (payment terms can name one)
3G/L accounts, projects, cost centres, distribution rules, where the group shares themParent accounts before their children
4Items and business partnersWaves 1 to 3, and the mappings for what is local
5Bills of materials, special prices, discount groups, customer equipment cardsItems and business partners

A tool that can create missing set-up data on the way shortens this: an item then brings its missing item group and manufacturer along. The mappings for local data still have to be made by a person, once.

5. Companies that already hold the data

Most groups do not start from empty companies. The branch already has most of the items, entered by hand over the years, mostly the same, sometimes not. The first replication run must not create a second copy of everything, and it should not blindly overwrite either.

  1. Measure the distance. For each object, compare the two companies: which records are the same, which differ and in which fields, which the target is missing, and which only the target has.
  2. Adopt what is the same. Records with the same code, or for numbered data the same name, are paired without being written.
  3. Decide the differences. Either the owner's values win, or the differing fields are declared local.
  4. Look at what only the target has. It is either local on purpose, or the counterpart of a source record under another code, which needs a pairing by hand.

6. Test and production

Every group has, or should have, test copies of its companies. A replication that is being set up belongs there first. Two rules keep this safe: a replication rule that connects test companies must never be able to reach a production company, and the test companies should be recent copies of the real ones, so that what a trial run shows there is what production will get.

7. Governance that survives the first year

  • New records arrive on hold in the target, where local fields (accounts, tax, warehouse) are completed before they are released
  • Sensitive objects, such as the chart of accounts, need a second person's approval before they are written
  • Someone is told when a record is held or fails, with a sentence that says what to do, not a log file
  • A record removed at the owner is not silently left active everywhere else
  • Every change of a rule is kept with who made it
  • Every write to a company can be looked up later: which fields, from which value to which

8. Where CertiReplica fits

CertiReplica is the master data half. One rule says which object goes from which company to which companies; it can be one-way for "one owner" and two-way for "shared", and its field rules say which fields each company keeps for itself. Local data is paired once under Mappings and never copied. Codes may differ, by a key template or a cross-reference per record. Companies belong to landscapes, and a rule can never cross from Test to Production.

Its Compare screen measures the distance between two companies before the first run, existing records are adopted without being written, and a simulation shows every change before it is made. It reaches each company through the Service Layer only, so the companies can sit on different servers and nothing is installed in any of them. The objects page lists the 32 kinds of master data it knows and which of them are proven on a real system.

Documents between companies are a different job, and CertiReplica does not do them. Request a trial to try the master data half on copies of your own companies.