The systems FI-LC and EC-CS essentially use the terms listed below for consolidating and reporting. These terms are derived from those of the other operative systems that disclose data:
Consolidation term (FI-LC) |
derived from: |
financial statement item |
account |
company (consolidation unit) |
company code or |
consolidation transaction type |
(in part) fixed asset transaction type |
Consolidation term (EC-CS) |
derived from: |
financial statement item |
account |
consolidation unit |
company code or |
subitem |
(in part) fixed asset transaction type |
Within a remote scenario, the right-hand terms can be developed independently in each system. Each term is assigned, remotely, to the corresponding consolidation term using dedicated tables. The details of each are explained in the topics that follow.
Charts of accounts
The FI system has three types of chart of accounts:
The outline of the assignments between accounts and consolidation items depends on the data transfer procedure used. It is always necessary to distribute (or replicate) the FS chart of accounts from the central Consolidation system onto all remote systems that disclose financial data. This can be done for R/3 systems using the ‘Customized Transport Procedure.’ At present, no corresponding extract function is available for R/2 systems in the standard delivery system (although a function is available if, conversely, the Consolidation system RF-KONS in R/2 is being used).
The FS chart of accounts is transferred via a download for remote PC data entry.
The account assignments (listed according to data transfer procedures) are as follows:
A particular problem can occur when certain balance sheet accounts or account groups must be assigned to either an asset or a liability item, depending on the account balance (such as ‘Receivables or Payables to/from Financial Institutions’). Here you must consider existing net balance prohibitions. The procedures ‘realtime update’ and ‘rollup transfer’ cannot immediately accommodate item substitutions that are balance dependent; only ‘periodic extracts’ do. Therefore, you should ensure that the Consolidation program that follows substitutes the item after the data transfer by defining items appropriately, for example one per financial institution.
Organizational units
The operational organizational units
not only play the role of the ‘assigning’ company, but also that of the group-internal ‘trading partner’. Therefore, a key structure must exist that is valid for the entire corporate group, and not only for the local system. On the other hand, in order to allow independent key assignments for ‘local’ organizational units (company codes, in particular) in any local system, the following assignment relationships are available:
local company code |
1:1 |
global company code |
|
N:1 |
company | |
local business area |
1:1 |
global business area |
|
N:1 |
consolidation business area |
Assignment to a consolidation unit depends on ledger usage:
company ledger : |
company |
consolidation unit |
business area ledger: |
company/ consolidation business area |
consolidation unit |
These assignments make it easier to later add a new company that already uses R/3 to the group, without having to laboriously convert the organizational unit characteristics.