Section 1 of 10

CO Module Overview

What CO is for, how it differs from and connects to FI, the controlling area as an organisational unit, and how S/4HANA changed the boundary between the two.

Open contents

CO (Controlling) supplies the accounting information used to manage the business and make decisions inside it. Because it is not producing statutory accounts, both the way figures are grouped and the way they are reported can be designed to suit the company.

How CO differs from FI

The differences come down to purpose and perspective.

AspectFI (Financial Accounting)CO (Controlling)
PurposeExternal reporting โ€” shareholders, tax, auditInternal management โ€” plan versus actual, profitability
FormatPrescribed by law and accounting standardsDesigned to suit the company
Main dimensionsG/L account, company codeCost centre, profit centre, order, product
PeriodFixed accounting periodsAny period, including weekly or daily analysis
Nature of amountsOnly what actually occurredActuals plus plan values and allocated amounts

CO is not a second set of books. In most cases its data is generated automatically from FI postings: recording an expense records the same amount as a cost in CO.

Cost elements as the bridge

What links an FI expense account to a CO cost is the cost element. If an expense account is defined as a cost element, posting to it also feeds the same amount into CO.

For that, SAP needs to know where the cost lands โ€” a cost object such as a cost centre or an internal order. Posting to an account defined as a cost element therefore makes a cost object mandatory, which is where the familiar "please enter a cost centre" error comes from.

The controlling area

The controlling area is the top-level organisational unit in CO. It occupies a position analogous to the company code in FI, but behaves differently.

One controlling area can contain several company codes, which allows cost analysis across legal entities. To combine them, though, those company codes must share the same chart of accounts and the same fiscal year variant.

Controlling area to company code
ConfigurationAllowed?Condition
One area : one company codeYesThe simplest arrangement
One area : several company codesYesSame chart of accounts and fiscal year variant
Several areas : one company codeNoA company code belongs to exactly one controlling area

The parts of CO

CodeNameScope
CO-OM-CCACost Center AccountingCollecting and allocating cost by department
CO-OM-OPAInternal OrdersCollecting cost per initiative or event
CO-PCProduct Cost ControllingWhat a unit costs to make, planned and actual
CO-PAProfitability AnalysisMargin by product, customer, region and similar
EC-PCAProfit Center AccountingTreating a unit as a business with its own result

FI and CO in S/4HANA

In ECC, FI line items (BSEG) and CO line items (COEP) sat in separate tables. Holding the same transaction in two places produced FI/CO reconciliation differences and a permanent chore of squaring them.

S/4HANA merges them into ACDOCA, the Universal Journal. One row carries account, cost centre, profit centre, segment and the rest as attributes. FI and CO look at the same data, so the concept of a difference between them disappears.

๐Ÿ“– Unfamiliar term? Look it up in the SAP glossary.

Check your understanding

Test what you just read.

Quiz 1

The primary purpose of the CO module is to produce external financial statements.

Quiz 2

What is primarily managed in the CO module?

Quiz 3

Which is the top-level organizational unit in CO?

Quiz 4

CO and FI are completely independent modules, and costs posted in FI are not automatically transferred to CO.

Quiz 5

Which of the following is NOT a sub-component of the CO module?

Quiz 6

A Controlling Area can span multiple company codes.