Intercompany with MultiBranch

Use Intercompany with SAP Business One's multi-branch companies.

Find a partner Back to Administration and health check

What it does

Set-up and allocation for branch-enabled companies; the receiver branch is chosen on the document.

When you need it: A company with branches trades with a sister company.

How it works

In a company that should use branches, open Administration › System Initialization › Company Details, tick "Enable Multiple Branches" on the "Basic Initialization" tab and press "Update". If Intercompany is already running there, first give the user who does this the right entries in "Global Data Authorizations".
Create the branches under Administration › Setup › Financials › Branches.
When the branches exist in every company that needs them, deploy again from the console (Setup › Landscape, "Deploy"). The deployment gives the B1i user every active branch.
Give each user at least one branch; without one, a user cannot create documents.
On intercompany documents the sender picks its own branch in the header and, when the other company also uses branches, the branch that should receive: the "Receiver Branch" field on sales and purchasing documents, the receiver branch code in the lower table of G/L allocations and A/P service invoice allocations, and the delegation branch on centralised payments. The receiving draft takes that branch and it cannot be changed there.

Set it up

Companies that already used branches before Intercompany came in skip steps 1 to 3 and follow the usual set-up. Every later addition or change in the "Branches - Setup" window needs a new deployment. The user guide also advises giving the business partners that stand for sister companies all the branches.

Since: Patch level 26 of Intercompany 2.0: Intercompany works with companies that use SAP Business One's branches.

Good to know

In consolidation, the branch and branch name of each journal entry are carried into the fields U_CTX_BRCID and U_CTX_BRCNM of the consolidation company, and passed up through further consolidation levels, so financial reports there can be filtered by branch.
G/L allocations need a branch code in each top row in a company that uses branches.
From 2.0 patch level 30, the lower table of G/L branch allocations, allocation posting templates, recurring allocation postings and G/L-type A/P service invoice allocations can also take branches of the company itself.