Professional Documents
Culture Documents
02 ECC Config Defining Parallel Ledgers
02 ECC Config Defining Parallel Ledgers
In General Ledger Accounting, you can use several ledgers in parallel. This allows you to
produce financial statements according to different accounting principles, for example. A
ledger uses several dimensions from the totals table it is based on. Each dimension of the
totals table represents a subset of the coding block. As was shown in the previous
document, you can also include customer fields in your ledgers.
When defining ledgers, one must be designated as the Leading Ledger. The leading
ledger is based on the same accounting principle as that of the consolidated financial
statements. It is integrated with all subsidiary ledgers and is updated in all Company
Codes. This means that it is automatically assigned to all Company Codes. In each
Company Code, the leading ledger receives exactly the same settings that apply to that
Company Code: the currencies, the fiscal year variant, and the variant of the posting
periods.
Ao definir livros, um deve ser designado como o Leading
Ledger. O principal livro é baseado no mesmo princípio que a
contabilização das demonstrações financeiras consolidadas. É
integrado com todos os livros e filial é atualizado em todos
os Códigos Companhia. Isto significa que é atribuído
automaticamente a todos os Códigos Companhia. Em cada
Empresa Código, a principal razão recebe exactamente as
mesmas definições que se aplicam à Companhia Código: as
moedas, o ano fiscal de variante, bem como a variante do
destacamento períodos.
Non-Leading Ledgers are parallel ledgers to the leading ledger. They can be based on a
local accounting principle, for example. You have to activate a non-leading ledger for the
individual Company Codes. Non-leading ledgers can have different fiscal year variants
and different posting period variants per company code to the leading ledger of this
company code. The second and third currency of the non-leading ledger must be a
SAP delivers the configuration settings for one leading ledger – this is the minimum
requirement even if no business need for parallel ledgers is identified.
For illustrative purposes, 2 additional ledgers will be created. The leading ledger 0L will
be reserved, as per the documentation, for consolidated financial reporting.
Ledger L1 – will apply to US companies (GAAP)
Ledger L2 – will apply to German companies (HGB)
Note: you cannot assign ledgers with keys beginning with ‘0’ – not in the allowed
Customer name space.
A ledger group is automatically created for each ledger – more on ledger groups later.
Acknowledging the messages saves the new ledgers.
Yes: Janessa
As mentioned above, the leading ledger applies to all Company Codes. The currency
settings from every Company Code (e.g. parallel currencies) automatically apply to this
ledger. As such, this menu path is simply an alternative entry point to company code
“Additional currency” configuration. Had this step already been completed, there would
be nothing new to do here:
In our example, the German company had been configured previously for an additional
group currency:
Therefore, the leading ledger will be denominated in both US dollars and Euros.
The additional ledgers were already “defined” previously. In this step, they are
“activated” through assign nment to FI Company Codes.
Repeating these steps for the German company (which has the additional currency
defined, as shown above):
The primary currency defaults in. Assuming that the need to report against this ledger in
group currency exists, it can be added in C2 by invoking the drop down:
Note: as can be seen from the table, it is possible to define Fiscal Year Variants and
Posting Period Variants that differ from the Company Code settings in these ledgers.
The scenario combines Customizing settings from different business views. Each
business view specifies which posting data is transferred from different application
components in General Ledger Accounting, such as cost center update or profit center
update. You assign the desired scenarios to your ledgers. For each ledger, you define
which fields are filled with posting data from other application components.
SAP delivers a number of scenarios in the standard system. It is not possible to create
additional scenarios. These scenarios can be viewed under this IMG path:
Highlighting an item and double clicking on the Scenario Fields folder will reveal what
will be updated, e.g. for Segment:
Highlight each in turn then double click the Scenarios folder to begin the assignment:
If there is a need to transfer CO plan data from CCA or CO-PA to a ledger, a plan version
must be assigned by double clicking on the Versions tab and clicking on New Entries.
Manual planning – activate to allow for manual planning against this ledger/version.
Integrated planning – activate to allow plan data to be transferred from CO.
In addition, the Integrated Planning indicator must be activated for that version in CO
(Controlling ® General Controlling ® Organization ® Maintain Versions ® General
Version Definition ® Controlling Area Settings ® Settings For Each Fiscal Year)
As was seen above, one delivered scenario updated Cost of Sales accounting. However,
this setting will not fill the Functional area field unless Cost of Sales accounting is
activated in this step. Similar to segment reporting, the new GL supports Cost of sales
The required steps in Customizing for Financial Accounting (New), under Financial
Accounting Global Settings (New) would include:
...
1. Assign the scenario Cost of Sales Accounting to all ledgers in which you want to use it.
Choose Ledgers ® Ledgers ® Assign Scenarios and Customer Fields to Ledgers.
If you do not use parallel ledgers, assign the scenario Cost of Sales Accounting to
the leading ledger.
You can combine any number of ledgers into a ledger group. In this way, you simplify
the tasks in the individual functions and processes of General Ledger Accounting. For
example, you can make a posting simultaneously in several ledgers.
In some General Ledger Accounting functions, you can only specify a ledger group and
not individual ledgers. This explains why a ledger group was automatically created when
each ledger was created earlier.
Design point – You only need to create additional ledger groups when you want to
process multiple ledgers using the same function. If no ledger group is entered for a
function, processing is performed for all ledgers. Therefore, it is not necessary to
create a ledger group that contains all ledgers.
Took this opportunity to provide a description to the SAP-delivered leading ledger group.
For illustrative purposes, a group comprising both non-leading ledgers will be created.
Assign both ledgers to the group. One ledger must be designated as “Representative”.
What purpose does this serve? The system uses the representative ledger to determine
the posting period during posting and to check whether the posting period is open. The
Design points –
If the leading ledger is part of the ledger group, it must be designated the
representative ledger
If all ledgers have a different fiscal year variant to that of the Company Code, any
ledger can be the representative ledger. However, should one of the ledgers have the
same fiscal year variant as the that of the Company Code, this ledger must be
designated the representative ledger
One of the justifications for creating additional ledgers in the New GL is to support the
needs of parallel valuation. This enables you to perform valuations and closing
preparations for a company code according to the accounting principles of the group as
well as other accounting principles, such as local accounting principles. While SAP also
supports accomplishing this via additional GL accounts, they recommend using parallel
ledgers when the number of required accounts would be unmanageable. (The downside
of this approach: increased data volumes.)
IMG path:
Design point - an accounting principle can be assigned to only one ledger group!
In this example, the GAAP rules will be applied to all Company Codes (USA, Germany).
Therefore, the inability to assign the GAAP rules to the ledger associated with the US
Company Code (L1) is not an issue.
At this point, accounting principles have been tied to ledgers. The final prerequisite step
involves linking the principles to Valuation Areas. It is the valuation area that will be
referenced at various points in the FI application when valuations will be performed
differently, depending on the accounting principle (examples to follow).
IMG path:
Once the valuation areas have been defined, enter the next section of the IMG to assign
them to the accounting principles:
While detailed configuration settings have not been made here, this document will
explain where additional settings could be made should the need to configure parallel
accounting valuations be required:
Click here and enter the Valuation area in the ensuing pop up window:
Note: once the new GL has been activated, an error message is returned when attempting
to use the old transaction F101:
Upon entering the new transaction, the Valuation area is available as a selection criterion:
As above, when configuring the account determination in this area, it is now possible to
specify different Valuation Areas when prompted for a Chart of Accounts. A new
transaction exists on the application side which must be used once the new GL has been
activated:
= F.05