Projects and transaction codes for group reporting

Project codes are shared across companies, and transaction codes carried into the consolidation company.

Find a partner Back to Financial consolidation

What it does

Project master data is replicated across the landscape; transaction codes on journal entries and vouchers are copied into the consolidation company, where many localisations build reports on them.

When you need it: Every company books against the same project codes.

How it works

Before the go-live, make sure the project master holds the same records in every branch company and in the consolidation company. The installation prerequisites ask for this.
Projects are among the masters Intercompany replicates. A project added in one company reaches the others in the landscape with its code, name, valid-from and valid-to dates and active flag.
User-defined fields on the project header can be replicated as well.
From version 55, the transaction code master is replicated too, so every company works with the same set of codes.
In each consolidation run, the transaction code on every journal entry and every voucher is copied into the consolidation company. Reports built on transaction codes, common in some localisations, then work for the group.

Set it up

Project replication is part of the company template: in the administration console, Setup › Company Template, then "Receiver Property List" for the Projects object to choose which properties travel. Code and name are mandatory; the dates and the active flag can be switched off. UDFs are registered in the console's UDF replication page, where the "Project Codes" object offers the header fields.

Since: Version 55 (October 2025): the transaction code master is replicated across companies, and the codes on each journal entry and voucher are carried into the consolidation company.

Good to know

Allocation screens use project codes as well: with project replication set in the company template, the codes chosen for each receiving company replicate to it.
Version 49 added SAP Business One Service Layer support for replicating the project master.
Version 55 fixed an error when replicating project codes through the Service Layer, and a gap in the UDF list of three objects: projects, vouchers and entries.