InterCompany Administration and Configuration Guide

First published on 12/20/2023/9:09 pm

 

 

Once you've established the InterCompany connectivity (see the installation guide), you can configure the data replication required between your SAP Business One companies.

 

Data replication falls into two categories: 'Master Data Replication' and 'Transaction Replication'. Both are configurable by the administration user.

 

All configuration is done using an add-on form accessible from Main Menu > Intercompany > Intercompany Configuration.

 

 

If this is your first time entering this form, you'll need to add a new header code. As long as it's unique, it can be anything you want.

 

Only a single header record of configuration is required.

 

However, if your business requires many configuration rules, you can break this into multiple header records to easily find rules (e.g., if you have many SAP Business One companies, you might make one header record per company with all the individual configurations below).

 

The InterCompany administration user manages this.

 

 

 

 

The form has two tab configurations, one for 'Master Data' and one for 'Transactional Data'.

 

Master Data Replication Setup Guide

Master data can be replicated from a single source company to any number of other companies.

 

This is a one-to-many scenario, so if changes are made to the data directly in the target company, an update to the object in the parent company will likely override the change if the field updated is included in the InterCompany replication. (See below for what's included and what isn’t.)

 

These master data items are currently supported in terms of this replication:

  • GL accounts/chart of accounts
  • Business partners
  • Item masters
  • Unit of measure (UOM) groups

 

 

Although these objects will replicate, not all fields/data from these objects will replicate to the target company because it's likely that different values will need to be held in some fields in the target companies.

 

What's included in the master data replication and what isn’t?

 

Item master objects included:

  • Item master: add and update
  • Item groups
  • Manufacturers
  • Shipping types
  • UOM
  • UOM groups

 

Item master objects not included:

  • Duty groups
  • VAT/tax settings
  • Item group GL determination
  • Planning data
  • Production data
  • Preferred supplier
  • Attachments
  • Customer-specific UDFs (Implementation documentation will cover how to make these mapping updates.) @james - do we have this piece documented

 

Business partners objects included:

  • Business partner - add and update customers, suppliers, and leads
  • Business partner groups
  • Shipping types
  • Industry

 

Business partners objects not included:

  • Business partner contact
  • Business partner billing and shipping addresses
  • Payment terms
  • Credit limit
  • Bank data
  • Payments run tab
  • Accounting tab
  • Attachments
  • Intrastat data
  • Sales employee
  • Buyer
  • VAT number
  • Territory
  • Customer-specific UDFs (Implementation documentation will cover how to make these mapping updates.)

 

General ledger accounts objects included:

  • Chart of accounts (GL accounts) - add plus update
  • All standard fields except fields related to VAT or tax data projects dimensions

 

General ledger accounts objects not included:

  • Customer-specific UDFs (Implementation documentation will cover how to make these mapping updates.)

 

Parent accounts are also sent when an account is added or updated.

 

Master Data Setup Configuration

 

In the 'Intercompany Configuration' form, select the 'Master Data' tab.

 

Add rows to the form by selecting the master data object from the list and entering the target database you want to replicate the master data to.

 

To replicate an object to multiple companies, enter a record for each company you want to replicate the object to.

 

 

In the above example, the following is configured:

  • Item masters replicate from this database to database Training14 and Training15. 
  • GL accounts replicate from this database to database Training14 and Training15.
  • Business partners and UOM groups replicate to Training14.

 

Master data configuration is only valid in this form WITHIN THE DATABASE YOU HAVE DESIGNATED THE MASTER. Any configuration for master data entered into any other company is ignored and Ensure that the connection in the Saltbox connector configuration for this master company is established as 'MasterB1WebAPI'.

 

 

 

Note: Target company names are requested during the provisioning process. They may or may not match the actual database name depending on what was provided. For example, you may have database names like 'SBODEMOGB' and 'SBODEMOUS'. During provisioning, you may have given these names along with an alias. For example, SBODEMOGB may have the alias 'OEC Computers UK' and SBODEMOUS may have the alias 'OEC Computers US”. Here, you use the alias names you provided.

 

Document Replication Configuration

You configure each company to SEND documents to another company within the 'Intercompany Configuration' form on the 'Transactions' tab.

 

 

This is the sending of documents only from the company you are creating them.

 

To do a complete loop of, for example, a purchase order in Company A becomes a sales order in Company B, and an AR delivery in Company B becomes a goods receipt PO in Company A, you add a configuration line to Company A to send a purchase order to sales order and then in Company B you add a configuration line to send a delivery note to a goods receipt PO in Company A.

 

In the above example, documents are being sent from Company A to Company B.

 

In the below example, the corresponding documents are being sent from Company B back to Company A.

 

 

This would close out the full purchase order to purchase invoice in Company A and the sales order to AR invoice in Company B. Then, an AP credit memo in Company A would create an AR credit memo in Company B.

 

Note: Only valid SAP Business One document posting configurations are supported. For example, you can't add a configuration that sends AR invoices in Company A to purchase orders in Company B.

 

Error Logging

Errors in the InterCompany workflow are added to the 'InterCompany Errors' form in the InterCompany menu.

(Main Menu > Intercompany > Intercompany Errors.)

 

 

 

Here, you find errors related to the attempted creation of either master data or transaction documents along with the object key, object type, source and target companies, time attempted, and the error message received.

 

 

This lets you look at errors, determine the reasons for them, and, if they're data-related, potentially fix them.

 

 

To attempt a message again, simply update the object in the source company and InterCompany will attempt to replicate the object again.

 

 

On this page

-