Using multiple databases

Intercompany can be used by companies that keep their accounts in a single database, but also by companies that each use different databases. In the latter case, the data must be transferred.

If you are using more than one database, you need to manually keep the contents of Company details and Relationships between companies identical in all databases. The company codes, customer codes and supplier codes must be the same in all databases.

Use the Relationships between companies form to specify for each company the database that holds their accounts. In the Transaction database field, set the database that is used for exchanging data. Below are examples of scenarios that may occur.

Multiple companies keep their accounts in a single database

In addition to Intercompany, you also need Multicompany. When setting up Intercompany, you have the following options when specifying the control policy for purchase accounts (Financial module, Reports and scripts folder, Additional central data folder, Assign methods):

  • CIO

Isah resolves the purchasing company by referring to the company that is linked to the purchase order.

  • LEV

Isah resolves the purchasing company by referring to the supplier group that is linked to the supplier listed on the purchase order.

Intercompany uses your selection for journal entry category 420 and journal entry type 30.

All companies keep their accounts in one shared database

Leave the Transaction database field empty.

The companies are using multiple databases on different servers

Leave the Transaction database field empty. You need the replication server. The replication server ensures that the contents of the tables ST_MFPurchaseTransactions, ST_MFShippingTransactions and ST_MFInvoiceTransactions are replicated.

The companies are using multiple databases on the same server

In the Transaction database field, set the database that is used for exchanging data between the companies. In this case, you do not need a replication server, and synchronization of the tables ST_MFPurchaseTransactions, ST_MFShippingTransactions and ST_MFInvoiceTransactions is not required.