Business Consolidation (SEM-BCS) PDF

4/20/2019
Business Consolidation (SEM-BCS)

Generated on: 2019-04-20
SAP ERP | 6.16.13
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
This is custom documentation. For more information, please visit the SAP Help Portal 1
4/20/2019
Business Consolidation (SEM-BCS)

Purpose
You can use the SEM component Business Consolidation (Consolidation) to determine the resources of a group(or a similar
enterprise or organizational unit), the claims by others to those resources, and the changes to those resources. Consolidation
also provides the means for internal and external enterprise reporting.
You can consolidate on the basis of customer-de ned consolidation units. Consolidation units can represent, for example,
companies, plants, business areas, pro t centers, and cost centers. You can also portray matrix organizations (for example,
using a combination of companies and pro t centers).
You can standardize the nancial data reportedby individual consolidation units to adhere to the accounting and valuation
standards of the group. You then translate the standardized nancial data from the various local currencies into the group
currencies. Finally, you can eliminate the effects of group-internal relationships (for example, from interunit trade and services).
Thus, you calculate the consolidated nancial statements as if the group were a single entity.
You can use the analysis functions of SAP Strategic Enterprise Management (SEM) and those of SAP NetWeaver Business
Intelligence (BI) to analyze and report on your consolidated nancial statement data.
Integration
The Consolidation component provides functions to collect master data and individual nancial statement data from data les
from non-SAP systems as well as SAP systems.
All SEM components are based on the BI system. The transaction data processed by Consolidation is written to the BI system,
which means that the BI system represents the primary data basis for all SEM components. This enables you to directly
exchange data between individual SEM components without the need for interim steps or for special objects for exchanging
data in BI. For example, you can:
Collect SEM-BPS planning data for use as reported nancial data in consolidation
Use consolidated actual data as the basis for further planning in SEM-BPS
Data from transactional SAP systems (for example, FI-GL) that has been loaded into a BI system can be transferred as
reported nancial data to the Consolidation component.
Furthermore, you can load reported nancial data from transactional SAP systems directly into SEM-BCS without extracting
them to BI storage rst.
And, nally, you can automatically transfer master data and hierarchies from other SAP systems.
Features
Versions
You can use versionsto execute parallel consolidations with different categories of data (for example, actual data, planning
data, forecasting data), using different accounting principles (for example, US GAAP, IAS, German HGB), using different
valuations, and/or for simulations.
Hierarchies
4/20/2019
You can create hierarchies for almost all characteristics (for example, consolidation units and nancial statement items), where
some hierarchies have special, consolidation-speci c properties.
Consolidation Charts of Accounts
You can use different charts of accountsfor consolidation. For example, this allows you to generate several consolidated
nancial statements in parallel to accommodate different accounting principles.
Collection and Standardization of Reported Data
The following methods are available for collecting individual nancial statements and other relevant data into the consolidation
system:
Online data entry using data entry layouts in the consolidation system or using BI queries in the BI system
Flexible upload from a data le
Load from an InfoProvider (from the BI system or connected SAP systems)
Copy within the consolidation system
You can post manual entries, for example, to standardize the reported data to meet the accounting and valuation requirements
of the group. You can make manual postings dependent on a work ow approval process.
For transferring master data and hierarchies (for example, of consolidation units or nancial statement items), you can use a
exible upload to upload les or InfoObjects from the BI system or connected SAP systems.
Consolidation Tasks
Below are some of the consolidation tasks you can execute automatically:
Currency translation (which translates the nancial data into the currency of the consolidation group) and rounding
Validation
Capitalization and valuation allowances of assets and liabilities (such as fair value surpluses)
Preparations for consolidation group changes
Interunit eliminations (for example, for payables and receivables, revenue and expense, or investment income) and
reconciliations
Elimination of interunit pro t/loss in transferred inventory
Elimination of interunit pro t/loss in transferred assets
Consolidation of investments
Reclassi cation
Allocation
Balance carryforward
The automated postings are controlled by the task settings you de ne once beforehand in Customizing.
You can use multiperiod consolidation to execute tasks and task groups (for instance, for planning purposes) for timeframes
that encompass multiple periods.
Reporting
4/20/2019
After performing the consolidation tasks, you can use BI reports to analyze your data. SAP provides pre-de ned business
content (InfoCubes, queries, etc.) for this purpose.
You can use XBRL to create individual or consolidated nancial statements.
You can use the restatement function to make retroactive adjustments arising from a (voluntary) change in nancial reporting
or to correct errors in nancial reports already published.
Execution and Monitoring of the Consolidation Process
You use the consolidation monitor to execute the consolidation tasks and to monitor the entire consolidation process.
User Interface
All Consolidation functions are available in the SAP GUI. In addition, there are two Web Dynpro applications that run in a Web
browser:
Web Dynpro-Based Consolidation Monitor for Local Accountants including all functions for data transfer and validation
Web Dynpro-Based Consolidation Monitor for Corporate Accountants with all consolidation functions
Constraints
The automated execution of consolidation of investments presently only covers the purchase method and the equity method, as
well as the mutual stock method.
You can use manual posting or, in some cases, the reclassi cation function to perform the consolidation tasks that are not yet
automated to meet your statutory requirements for creating consolidated nancial statements. For more information on
proportionate consolidation with reclassi cations, see Proportionate Consolidation .
Execution of Consolidation with the

Consolidation Monitor
Purpose
You can use consolidation with SEM-BCS for various purposes. The purpose determines how you con gure the data model and
how you use the consolidation tasks:
Statutory consolidation requires that reported data from the group's consolidation units be aggregated into a single set
of consolidated nancial statements. This requires that the reported nancial data:
is standardized to agree with the group's standard accounting policies
is translated into the currency of the consolidation group
cleansed of effects that are the result of group-internal relationships
Consolidation by internal demand (for example, pro t center consolidation) is used to control enterprise areas. The main
focus of the consolidation tasks is on the elimination of the effects of the delivery of goods and services within such
enterprise areas. For example, "interunit sales" are to be eliminated.
Prerequisites
4/20/2019
The consolidation units must report their nancial data so that it can be copied to the consolidation system.
Note the following important prerequisites needed for error-free data collection.
Subassignments
The consolidation system needs account assignments, such as partner units, transaction types, transaction currencies, and so
on, in order to perform the consolidation tasks. For example, automated elimination of IU revenue and expense is only possible if
the system knows which partner units caused the revenues and expenses.
In item customizing, you de ne which subassignments each item requires. These subassignments must be included in the
reported nancial data.
Creating an Initial Data Set
Legacy data for your consolidation units usually already exists when you implement consolidation with SEM-BCS.
There is basically no difference between transferring legacy data and transferring the data of the current period. When
collecting data in SAP Consolidation for the rst time, you enter the cumulative value for the legacy data.
Process Flow
A. Customizing
In the workbench, you make the Customizing settings to suit your speci c requirements.
SAP provides standard settings for many consolidation methods. For each of them, check whether you can use the standard
delivery unchanged or modi ed. The system can support you in this with copy functions.
B. Execution of Consolidation Tasks
You execute the tasks in the consolidation monitor. There are
Tasks for the collection and preparation of reported nancial data
Tasks for the actual consolidation entries
The following gure shows an example of the sequence of tasks in the consolidation monitor:
4/20/2019
1. You carry forward the data from the previous scal year into the current scal year. You also run a period initialization to
invert documents generated manually and automatically for earlier periods.
These tasks are necessary only if data from the prior year exists in the totals database.
2. You transfer the reported nancial data of the consolidation units.
The system stores this reported nancial data in the InfoCube for the totals data.
3. You validate the reported nancial data.
4/20/2019
Unlike the validation of standardized nancial data in group currency, this task is not mandatory.
Recommendation
Nevertheless, we recommend validating the reported nancial data at this point if you have not otherwise ensured
that the reported nancial data is consistent.
4. You post standardizing entries to the reported nancial data, if needed. You can post these entries manually or
automatically, as "reclassi cations".
Note
Alternatively, you can execute this task after currency translation.
5. Prior to running interunit eliminations, you can use reconciliations to determine any elimination differences without
having the system post elimination entries. By doing this, you can manually correct erroneous entries in the reported
nancial data, or manually post standardizing entries.
6. If the reported nancial data is valued in different local currencies, you translate the data into the currency of the
consolidation group.
This is usually the currency of the parent company when company consolidation is involved.
7. You can use an allocation task, for example, to assess or distribute standardized data to multiple account assignments.
8. You validate the standardized nancial data.
9. You use interunit elimination tasks to eliminate intercompany receivables and payables, as well as income and expenses.
10. Sales of current assets within a consolidation group result in interunit pro ts/losses. You use the Elimination of Interunit
Pro t/Loss in Transferred Inventory task to eliminate these interunit pro ts/losses automatically.
11. You use Elimination of Interunit Pro t/Loss in Transferred Assets to eliminate those interunit pro ts/losses that
resulted from sales of noncurrent assets within a consolidation group.
12. You use Consolidation of Investments to eliminate the group-internal equity relationships. In doing so, the investment(s)
of the investor units are eliminated with the proportionate equity of the investee units included in the consolidation
group.
13. You can use a reclassi cation task to reclassify the consolidated data.
 Example
Often, the retained earnings or losses of the parent unit are to be reported in the consolidated nancial statements.
You can use reclassi cations to reclassify the retained earnings or losses of the subsidiaries to the reserves.
14. In isolated cases, manual postings may be necessary to make corrections to the consolidated data.
15. After the consolidation tasks have been performed, validate the consolidated data.
Result
You can create BW reports for the consolidated data. You can also forward the data to other SEM components, for example, to
the Business Planning and Simulation (SEM-BPS) component.
4/20/2019
Use
The consolidation monitor provides a graphic overview of consolidation units and consolidation groups, as well as tasks and task
groups.
It provides a central work environment for:
Executing tasks (for collecting, standardizing, and consolidating all reported nancial data)
Monitoring the progress of the tasks for each individual consolidation unit or group
Prerequisites
Customizing of consolidation has been completed except for the settings concerning the consolidation monitor. In particular,
you have de ned the following settings:
The consolidation units and consolidation groups with their hierarchies
The tasks with their task hierarchies (including task groups)
Features
Layout of the Consolidation Monitor
The consolidation monitor has a matrix-like structure. By default, the hierarchies of organizational units and the hierarchies of
tasks are arranged as follows:
The rows of the consolidation monitor display the hierarchies of the organizational units.
The columns of the consolidation monitor show the task hierarchy (which includes task groups and tasks ).
The status for the task groups and the tasks is shown for each node of the organizational unit hierarchy.
A legend (located in the menu of the monitor) explains symbols and texts.
4/20/2019
You have the option of changing the layout of the consolidation monitor to display the hierarchies of organizational units in the
columns and the hierarchy of tasks in the rows. To do this:
Call up the context menu for the header row and choose:
Swap Characteristic with… Consolidation Group/Consolidation Unit or
Call up the context menu for the header column and choose:
Swap Characteristic with… Task/Task Group
Consolidation Unit Hierarchies
The consolidation monitor displays all status-relevant consolidationunithierarchiesdown to the level of consolidation units (the
end nodes of the hierarchy). For more information about status-relevant hierarchies, see the “Status-Relevant Hierarchies”
section in Status Management in the Consolidation Monitor .
For a better overview of the organizational units to be processed, the consolidation monitor provides the following functions
(listed in the menu and the standard function bar):
You can show or hide the columns for lower-level hierarchy nodes of the task hierarchy.
You can search for organizational units in the displayed portion of the hierarchy.
You can set the focus on a hierarchy, a consolidation group, or a consolidation unit. The consolidation monitor then only
displays those particular organizational units with their lower-level units .
4/20/2019
You can remove the focus by choosing the appropriate menu options in the Edit menu, or in the context menu for a
given node.
From the consolidation monitor you can go to master data maintenance for organizational units. To do this, you place the cursor
on the node for the master data object in the hierarchy of the consolidation monitor, and then choose Goto Master Data ; or
you can double-click the object.
Task Hierarchy
You can display all tasks you de ned in Customizing. In particular, how the tasks are displayed depends on the following factors:
The task hierarchy or task sequence you de ned
The task hierarchy determines the sequence of the tasks executed by the consolidation monitor. The system ensures
that certain tasks are executed in a required sequence.
The permanent parameters you selected
Make sure that:
The task hierarchy is time and version dependent.
You assigned a consolidation frequency to a task in your Customizing settings.
Accordingly, the task is only displayed in consolidation periods. Thus, if you chose yearly consolidation for a given
task, the consolidation monitor only shows this task for period 012.
For the balance carryforward task: The consolidation frequency you assigned in customizing for the version combinations
The monitor only shows the balance carryforward task in the rst period of the consolidation interval.
For information about processing the tasks depending on their status, see Status Management in the Consolidation Monitor .
Layout of the Consolidation Monitor
The matrix in the consolidation monitor can become very large and somewhat unwieldy, depending on your corporate structure
and consolidation requirements. Therefore, the consolidation monitor includes the following functions to modify the layout of
the monitor:
In the hierarchy of the organizational units you can:
Set a focus
Hide the names of the organizational units (the consolidation monitor displays only the keys)
With the columns for the task hierarchy, you can:
Partially or completely expand or compress the columns
Manually set or automatically optimize the width
You can set lters to
Display only certain statuses, such as all tasks with errors
Hide the end nodes of a hierarchy
In the status display area you can display either symbols or texts that re ect each status.
You can save your user layout (see the menu Layout or the corresponding symbol in the standard function bar). Then
your layout settings remain intact even after ending and restarting the consolidation monitor.
4/20/2019
The following settings in particular are saved:
Focus
Hierarchy display
Status display
Task display
Names on/off
The user layout is not dependent on time or version.
To display the default layout , and no longer your user layout, choose Layout Default Layout .
Recommendation
You should choose the default layout after you have made changes in hierarchies of organizational units or
changes in the task hierarchy.
When you change the sequence of tasks, the system performs a check for the layout.
Note
For more information, see SAP Note 699111. This extensive consulting note offers support in your day-to-day
use of the consolidation monitor.
Performing the Tasks
Conditions for Processing Tasks
The following applies when processing the tasks:
All tasks that belong to the task hierarchy apply for each and every consolidation unit. Only these tasks are excluded:
Data collection tasks
Manual posting tasks
Tasks that are irrelevant for a consolidation unit
There is a required sequence for certain tasks. For more information, see Task Sequence .
Selection of the Organizational Units
In the consolidation monitor you can execute tasks for a single consolidation unit or for a consolidation group. However, some
tasks can only be executed for consolidation groups – for example, tasks for the consolidation of investments.
Start Mode
You can run the tasks in the following ways:
Test run ( Test pushbutton)
You can execute test runs regardless of a task's status at any time.
Update mode ( Post pushbutton)
You can run a task in update mode if the task has been opened and the preceding tasks have been blocked (see Status
Management ).
4/20/2019
Update mode without blocking ( Task Update without Blocking) )Same as Update Run except that the system does not
automatically block successive tasks after a successful update run. This is useful in multilevel corporate groups when you
want to post on the group parent level but still allow for adjustments in the lower levels of the corporate hierarchy.
Update mode with pendent tasks
When you run a task in update mode and preceding tasks are still pending (that is, not yet blocked), the system runs the
task only tentatively (see Status Management ).
With selection screen ( Tasks Execute with Selection Screen )
This lets you enter the selection conditions and technical settings (update/test mode) in a dialog box prior to executing
the task.
Run successive tasks without stop
This lets you execute the tasks of a task group in succession without stopping in between, as long as they can be
executed automatically. This feature speeds up the creation of your consolidated statements.
When you run a task group or a task, the system indicates the task in process in the status bar of the consolidation monitor.
For more information on running task groups and tasks in multiperiod consolidation, see Multiperiod Consolidation .
Status Management in the Consolidation

Monitor
Use
You use this function to monitor the progress of the tasks for each individual consolidation unit or consolidation group.
Note
Using Status Reporting, you can create reports on the progress of task processing and task group processing in the
consolidation monitor.
Prerequisites
Status management is activated by default.
Recommendation
You should deactivate status management in exceptional cases only. You can do this in the process view of the workbench
under Consolidation Area, on the Settings tab.
The other prerequisites are the same as those described in Consolidation Monitor.
Features
Status-Relevant Hierarchies
Whenever status management is activated, a consolidation unit hierarchy is status-relevant by default, which means that the
consolidation monitor shows the status of the hierarchy.
4/20/2019
In the consolidation area settings, you can use the Hierarchy-dependent Status Management is Active in Monitor indicator to
have the consolidation monitor hide the hierarchies that are not status-relevant.
If this indicator is selected, for each hierarchy you can specify whether it is not status-relevant or not displayed in the
Consolidation Monitor. (Go to the process view of the workbench and choose Consolidation Monitor Status-Bearing
Hierarchies ).
Status Display per Organizational Unit
The consolidation monitor displays the status by organizational unit for each status-relevant hierarchy: for each task and
summarized for task groups.
Legend of Symbols for the Status Display
Explanations of each task status:
Status Explanation/Example System Sets Status User Sets Status
Initial state The task has not yet been X

executed in update mode.
4/20/2019
Incomplete The task has been executed in X

update mode but is still
incomplete, for example, due to
the following:
The task has not yet

been executed for all
subordinate
consolidation units.
A preceding task was

executed again.
Errors Errors occurred while the task X

was being executed in update
mode.
Pending completion of X
One or more preceding
preceding task
tasks are not yet
blocked.
The copy task has the

pending status when the
source task(s) are not
yet blocked.
No errors, with warnings No errors occurred in update X

mode, but warning messages
did arise.
No errors, no warnings The task was executed in X

update mode without any errors
or warnings.
Blocked The task is blocked against Optional

(another) execution.
The user can block the task only

if it has been executed without
errors and the preceding tasks
are blocked.
Exceptions: Data collection and

manual standardizing tasks.
These can be blocked without
having been run (however, the
preceding tasks must rst be
blocked).
You can block a copy task after

it has been executed without
errors if its source task or tasks
have been blocked.
Blocked, pending approval A user wants to block the task. Optional

A work ow for approving status
changes is assigned to the task.
The status change has not yet
been approved.
4/20/2019
Blocked by user intervention Users can block tasks at any Optional

time (regardless of the status of
preceding tasks).
However, you should use this

option only when there is
justi cation to do so, and only in
exceptional circumstances.
Blocked by user intervention, A user wants to block the task, Optional

pending approval regardless of the status of the
task (for example, Errors) or of
the status of the preceding task.
A work ow for approving status
been approved.
Unblocked After a task has been blocked, Optional

you can unblock it if it needs to
be re-executed.
Unblocked, pending approval A user wants to unblock the Optional

task. A work ow for approving
status changes is assigned to
the task. The status change has
not yet been approved.
Not applicable X
Currency translation is
not applicable for a
consolidation unit if its
local currency is the
same as the group
currency, or its reported
nancial data is
recorded in group
currency.
A copy task is not

applicable if the
assignment of the
method to the copy task
is dependent on the
consolidation units, and
you have deselected the
Relevant indicator for
those consolidation
units (instead of
specifying a method).
Reset When the source task of a copy X Optional

task is reset, the system resets
(for the copy task)
the status of the copy task and
the tasks that follow.
You should Reset the status only

when this is justi ed, and only
in exceptional circumstances
(see below).
4/20/2019
Reset, pending approval A user wants to reset the task. A X Optional

work ow for approving status
(for the copy task)
been approved.
You should set the status to

Reset, Pending Approval only
when this is justi ed, and only
in exceptional circumstances
(see below).
To display the details of the status of an organizational unit and a task (or task group), go to the context menu of the header
row or header column and choose Swap Characteristic with... Status Details .
The details include the user name, date, and time of the last change.
Details About Status Updating
When you run a task in update mode, the system updates the status for the relevant organizational units.
You can execute task "B" even if its preceding task, "A", has not been blocked yet. In this case, task "B" is set to status
Pending Completion of Preceding Task.
A task can only be blocked (in the menu) if it was executed without any errors and all preceding tasks have been blocked.
Exceptions to this are the data collection and manual standardizing entries tasks. These can be blocked without having
been run.
You can block the tasks of a task group as a bundle.
If you block a task for a consolidation group (in the menu: Task Block Block ), the system simultaneously blocks the
subordinate consolidation groups and units.
Once a task has been blocked, it must be unblocked before it can be run again. Note that this also automatically unblocks
all downstream tasks. For example, if you unblock the task for data collection, the system simultaneously unblocks the
tasks for currency translation and so on.
You can unblock the tasks of a task group as a bundle.
If you unblock a task for a consolidation group (in the menu: Task Unblock Unblock ), the system simultaneously
unblocks the subordinate consolidation groups and units. However, you can also unblock individual consolidation groups
for tasks that are executed at the consolidation group level without also unblocking subordinate consolidation groups (in
the menu: Task Unblock Unblock Group ). You can use this option, for example, to unblock a copy task at a speci c
hierarchy level.
The system uses the same update logic for higher-level and lower-level organizational units, and for the overall status.
Only in exceptional cases should you Reset the status (in the menu: Task Reset ). Here is an example: Suppose the
system sets the status of currency translation to Not Applicable because the local currency is the same as the group
currency. At a later date, a local currency change takes place. In this case, you need to manually reset the status of
currency translation.
The system then resets the following statuses of the organizational units for the selected task:
The status of the selected consolidation unit or group
The statuses of the lower-level consolidation units and groups
4/20/2019
The statuses of the higher level consolidation groups
The system also resets the downstream tasks.
Furthermore, when a source task of a copy task is reset, the system resets the status of the copy task and the tasks that
follow.
Another function for exceptional cases is the function for deactivating status management (see Customizing for the
consolidation area on the Settings tab).
Opening and Closing Task Processing for a Period
In general, periods are always initially open for task processing.
You can open and close the periods of a scal year for all tasks to ensure that documents are always posted in the correct
period. This is always done for a selected consolidation group (including its lower-level organizational units) or for a single
consolidation unit.
You can also close the processing of consolidation units only. In this case, only the tasks at consolidation group level can be
executed. To do this, choose Edit Period Close Processing of Consolidation Units .
If the period (including all tasks) is already closed, you can reopen task processing for the consolidation groups by choosing
Edit Period Open Processing of Consolidation Groups .
Note
You require special authorization to open and close periods.
The following gure shows which colors are used to highlight the nodes of the organizational units when periods are open or
closed.
Color legend for opening and closing periods
Conditional Status Update

Use
This function allows you to suppress the status update when tasks that post automatically are repeated in the update run, if
there have been no changes since the previous update run.
If the task is a preceding task of additional tasks, the system also suppresses the status information update for these
succeeding tasks.
Prerequisites
4/20/2019
You have activated the Financials, Group Close, Restatement Monitor business function.
Features
If you repeat execution of a task that posts automatically in the update run, the system checks whether there have been
changes since the previous update run. If this is not the case, the system does not post documents for this task in the repetition
run. If you activate the Conditional Status Update function, the system also suppresses status information updates if the
following requirements are ful lled:
The task execution does not contain errors.
The status of the task has one of the following values prior to the current execution:
Without Errors, Without Warnings
Without Errors, but with Warnings
Pending
For tasks that do not generate documents (such as validation, reconciliation, or custom tasks), the system only checks whether
the current execution of the task generates error messages. Based on the criteria listed, the system also determines whether
the status information is to be updated.
The system can not only determine whether the status information update is to be suppressed for each individual
organizational unit (consolidation unit or consolidation group) but also for multiple organizational units, if necessary. This
depends on the posting level to which the task posts.
For consolidation-unit-based tasks (posting levels 01 and 10), consolidation units to be processed are packaged
internally during task execution. If the conditions listed above are ful lled for all consolidation units in a package, the
system suppresses the status update for the relevant package.
For tasks with two-sided elimination (posting level 20), the system suppresses the status update if the conditions listed
above are ful lled for all consolidation unit pairs that are being processed in the current task execution.
For tasks with consolidation group-dependent postings (posting level 30), the system suppresses the status update if
the conditions listed above are ful lled for all consolidation groups that are being processed in the current task
execution.
Activities
To activate this function, in Customizing for the consolidation group, navigate to the Settings tab page and select the
Conditional Status Update checkbox.
Task Sequence
Use
You use this function to specify the sequence of tasks that are to be executed in the consolidation monitor.
The task sequence is version-dependent and time-dependent.
Integration
4/20/2019
The sequence of tasks is dependent on the consolidation area: Each consolidation area can have only one task hierarchy and,
therefore, only one sequence of tasks.
The exception to this rule are restatements, which have a separate task hierarchy. For more information, see Restatement.
The consolidation monitor displays the executable tasks of a task hierarchy. If the speci ed period is a consolidation period in
the relevant consolidation frequency, the task is executable. For more information, see the Time Dependency of Tasks and Task
Groups section in Tasks.
Prerequisites
You have de ned the tasks to be used in the task sequence and inserted them in the task hierarchy.
Features
Required Sequence
The system enforces a required sequence of certain tasks, thereby creating an initial, raw structure of tasks. This ensures that
these tasks are executed in the correct sequence as required by the system or accounting rules.
Internally, the tasks are divided into several blocks. The numbers of these blocks dictate the required sequence. The tasks
belonging to any given block can appear in any order within the block.
The internal blocks indicate at which point within the consolidation process the system expects to execute tasks of certain
categories. These blocks are part of rules from which the system derives the implicit preceding task relationships. The system
uses these rules when the consolidation monitor is called and when changes are made to the task status in status
management.
 Example
Task A is only an implicit preceding task of task B if the task category of task A is in a lower block than the task category of
task B.
If task B belongs to a lower block than task A, or both tasks belong to the same block, task A cannot be an implicit preceding
task of task B.
If, upon applying these rules, the system determines that task A is a preceding task of task B, status changes in task A have
an impact on the status of task B.
You can also specify explicit preceding task relationships in the consolidation workbench. The system always takes the explicit
preceding task relationships into account.
 Example
If you explicitly specify that task A is a preceding task of task B, status changes made in task A have an impact on the status
of task B. This also applies if the system does not identify any implicit preceding task relationships as the preceding task for
A and the succeeding task for B based on the rules outlined above.
The following table illustrates the internal blocks and their tasks:
Block Task
1 Balance carryforward
4/20/2019
Block Task
Custom task
2 Period initialization
Custom task
3 Data collection (on consolidation unit level)
Copy task (on consolidation unit level)
Validation of nancial data and standardized nancial data
Custom task
4 Data collection of additional nancial data for consolidation of investments
Capitalization and valuation allowances
Currency translation
Reconciliations
Manual postings
Reclassi cation
Allocation
Custom task
Capitalization and valuation allowances
Manual postings
Reclassi cation
Allocation
Custom task
Manual postings (in group currency)
Validation of nancial data and standardized nancial data (in group currency)
Reclassi cation (in group currency)
4/20/2019
Block Task
Allocation (in group currency)
Custom task
Validation of nancial data and standardized nancial data (in group currency)
Reclassi cation (in group currency)
Allocation (in group currency)
Custom task
Custom task
9 Data collection of additional nancial data for consolidation of investments (only goodwill or sequence of
activities)
Data collection (on consolidation group level)
Copy task (on consolidation group level)
Manual postings (in group currency)
Interunit elimination
Posting of group shares
Reclassi cation
Allocation
Custom task
Validation of consolidated nancial data
10 Custom task
Sign-off task
Only a sign-off task is permitted in the task hierarchy.
Note
The collection of reported nancial data must be complete before you can translate the (standardized) data into group
currency.
Blocks can have multiple occurrences of certain tasks (for example, tasks for manual posting, reclassi cation, and allocation).
Multiple tasks are distinguished by their document types.
Tasks with the following categories are allowed to occur once only:
4/20/2019
If you use only one currency translation task in the task sequence, posting in local currency is no longer possible once the
currency translation task is executed.
Custom tasks can reside anywhere in the task sequence. For more information, see Custom Task.
Individual Sequence
For accounting or organizational reasons, you may want to determine a sequence of tasks within a block. You can specify the
required sequence at this deeper level in Customizing for the task hierarchy.
Preceding Tasks
If a second task is to fully depend on the results of a rst task, you can assign the rst task as the preceding task to the second
task. If you do this, keep in mind that the task sequence is version-dependent and time-dependent.
 Example
If you want to standardize the reported nancial data to meet corporate policy, you can decide whether a given task is to be
run before or after currency translation.
You can de ne tasks with two preceding tasks. The system then runs the preceding tasks in parallel.
 Example
Also compare the example shown later.
Conditions for the Task Sequence
The following conditions must be met when you de ne the task sequence:
You need to adhere to the required sequence.
Each document type you use can occur only once within a task hierarchy. However, there is an exception: The same
document type can be used by the reconciliation task and its associated task for interunit elimination.
Recursions of tasks are not allowed in the task sequence – that is, multiple tasks may not reference each other. This can
happen if the rst task is de ned (directly or indirectly) as the preceding task of the second task, and the second task is
de ned as the preceding task of the rst task.
4/20/2019
 Example
The following task de nition is not permitted:
List of Preceding Task Relationships
If you have activated the Financials, Group Close, Restatement Monitor function, you can display a list of the task hierarchy as
well as the preceding relationships between the tasks in the task hierarchy. The system indicates whether the preceding task
relationships are explicit or implicit.
In the process view of the consolidation workbench, choose Consolidation Workbench List Settings .
Activities
To con gure the Customizing settings for the task sequence, proceed as follows:
1. To specify the individual task sequence, go to the process view of the consolidation workbench and choose Consolidation
Monitor Task Hierarchy .
2. Modify the task hierarchy to meet your requirements. To structure the tasks, you can group them into task groups (which
are nodes in the hierarchy). You can then use the task groups in the consolidation monitor (for example, to display them
in columns and for summarizing the tasks for the task status display).
Save your changes.
The system uses this sequence for the de nition of preceding tasks.
3. To de ne preceding tasks, go to the process view of the consolidation workbench and choose Consolidation
Monitor Preceding Task Relationships .
The work area of the consolidation workbench shows the task sequence that you de ned in the task hierarchy.
4. In the hierarchy, select the task that is the preceding task and drag it to the task it precedes.
Save your changes.
If the task sequence meets the conditions previously mentioned, the system inserts the preceding task. If a condition is
not met, an error message is displayed.
4/20/2019
The task sequence is re ected in the display of the tasks and in the status management in the consolidation monitor.
Recommendation
Once you have started the consolidation process for a period, you should no longer modify the underlying sequence of tasks.
Example
The example below shows a possible sequence of tasks.
The symbols have the following meanings:
- at the top level: Consolidation area
- at the second level: task without a preceding task
- task with a preceding task
- preceding task
Tasks Name
XY Consolidation area
.. CF Balance carryforward
.. DE 1 Data entry task 1
.... CF Balance carryforward (precedes data entry task 1)
.. DE 2 Data entry task 2
.... CF Balance carryforward
.. Val RFD Validation of reported nancial data
.... DE 1 Data entry task 1
.... DE 2 Data entry task 2
.. Recl CU Reclassi cation on consolidation unit level
.. SE Man Manual standardizing entries
.... Recl CU Reclassi cation on consolidation unit level
.. CT Currency translation
.. Val SFD Validation of standardized nancial data
.. Pay/Rec Elimination of interunit payables and receivables
.. Rev/Exp Elimination of interunit revenue and expense
.. EII Elimination of investment income
.. P/L Inv Elimination of interunit pro t/loss in transferred inventory
.. C/I Consolidation of investments
.. C/I Man Manual consolidation of investments
4/20/2019
Tasks Name
.. Recl CG Reclassi cations for consolidation groups
.... C/I Man Manual consolidation of investments
.. Recl CG Man Manual reclassi cations for consolidation groups
.. Val CFD Validation of consolidated nancial data
.... Recl CG Man Manual reclassi cations for consolidation groups
Cutoff Task
Use
This function enables a user (or a role) to have a restricted view of a task group. When you designate a cutoff task, the task
group in the consolidation monitor only shows the tasks of the task sequence from the rst task to the cutoff task. The system
then executes only these tasks.
This kind of restricted (or personalized) view of the task group can be useful for staff, such as the accountants of the group’s
subsidiaries.
 Example
While the tasks data collection and currency translation are often performed at the subsidiaries of a corporate group, the
group itself performs consolidation tasks such as elimination of interunit pro t/loss in inventory and consolidation of
investments.
You may want subsidiary staff to see only a range of the tasks that are relevant and for which they are responsible.
You can select the respective subsidiary in the permanent parameters.
In addition, you can de ne which tasks are relevant by designating a cutoff task.
Integration
The following factors in uence how tasks and organizational units are displayed in the consolidation monitor:
To perform consolidation, you need two types of hierarchies: (a) hierarchies of your organizational units (that is,
hierarchies of consolidation units and consolidation groups), and (b) a task hierarchy . The task hierarchy contains all of
the tasks needed for the consolidation process.
The hierarchies are dependent on time and version. If not all tasks need to be executed in each consolidation period, you
can de ne which tasks are displayed in each period by assigning consolidation frequencies to each task.
You can set the permanent parameters to have the system only show a speci c consolidation group or consolidation unit
along with its respective tasks.
A cutoff task further restricts the view of the tasks according to a user or role. The consolidation monitor shows a limited
task group, as determined by the cutoff task.
Prerequisites
Before you can de ne a cutoff task in Customizing, you need to have:
4/20/2019
De ned one or more hierarchies of consolidation units and consolidation groups
De ned a task hierarchy and the task sequence
Assigned a consolidation frequency to each task
Speci ed the permanent parameters
Features
You use a cutoff task to de ne a subset of tasks from the task hierarchy that is based on a user or a role; this is called a limited
task group . When this is done, the user only sees the limited task group in the consolidation monitor.
Since a task sequence is required and this sequence cannot have any gaps, a limited task group contains all of the tasks of the
task sequence from the rst task up to (and including) the cutoff task.
 Example
Suppose the task sequence is de ned as T1, T2, T3, T4, T5, T6, T7.
You want the limited task group to look like this: T1, T2, T3.
In this case, you designate T3 as the cutoff task.
To be able to personalize Role Maintenance (PFCG) or User Maintenance (SU01) , you can employ the personalization object
R_BCS_LIMITED_TASKGROUP .
Activities
Limited task groups can be user-speci c or role-speci c:
To make them user -speci c, make the Customizing settings in User Maintenance or in the Consolidation Workbench .
To make them role -speci c, make the Customizing settings in Role Maintenance .
User-speci c Customizing inUser Maintenance(transaction SU01) or in theWorkbench
1. Start User Maintenance in your local system.
2. Specify an existing user or create a new one.
3. In the maintenance screen, go to the Personalization tab.
4. From the list of personalization objects, select R_BCS_LIMITED_TASKGROUP .
5. In the detail screen of the personalization object, specify a cutoff task for each consolidation area and task hierarchy.
6. Save the cutoff task(s).
7. Save the user.
You can display the cutoff task in the Workbench by going to Consolidation Monitor Cutoff Task Personal Cutoff Task.
There you can change the cutoff task for the current consolidation area.
Role-speci c Customizing inRole Maintenance(transaction PFCG)
1. In your local system, start Role Maintenance in the SAP menu by choosing Tools System Administration User
Maintenance Roles .
4/20/2019
2. Specify an existing role or create a new one.
3. In the maintenance screen, go to the Personalization tab.
4. From the list of personalization objects, select R_BCS_LIMITED_TASKGROUP .
5. In the detail screen of the personalization object, specify a cutoff task for each consolidation area and task hierarchy.
6. Save the cutoff task(s).
7. Save the role.
You can display the cutoff task in the Workbench by going to Consolidation Monitor Cutoff Task Cutoff Task of Role. The cutoff
task cannot be changed here.
Note
User-speci c settings take precedence over role-speci c settings.
Authorizations for Tasks

Use
You use this function to grant various privileges for accessing consolidation tasks to persons who work with the Consolidation
system.
Note
To assign authorizations for customizing tasks, follow the steps described in the documentation on
authorizations for master data.
Integration
The authorization concept of consolidation is embedded in the SAP authorization concept.
Prerequisites
In the consolidation workbench, you have created the consolidation areas for which you want to customize the authorizations
for tasks. You have completed the Customizing settings for the consolidation tasks:
You have customized the individual tasks
You have set up the task hierarchy and sequence as well as the hierarchy of consolidation units to be able to execute the
tasks in update mode
For more information, see Consolidation Area and Task Sequence.
Features
You can assign authorizations for:
Executing tasks in both update mode and test mode
Blocking and unblocking tasks
4/20/2019
Changing the status of tasks
Displaying the last log
Deleting task logs
The consolidation monitor checks the authorizations of the user for each activity. If the user has the necessary authorization,
the system carries out the activity. Otherwise, the system issues an error message.
Authorization Assignment
The authorizations apply to each separate consolidation area.
You can restrict authorizations to the following, status-relevant characteristics:
Speci c versions
Speci c group currencies
Speci c consolidation groups
Speci c consolidation units
Speci c restatements
You assign authorizations using authorization object R_UC_TASK. This authorization object has the following elds:
Activity, which has the following attributes:
Block task
Unblock task
Execute task in update mode
Execute task in test mode (simulation)
Change status of task
Display last log
Delete own extracts
You use the Delete own extracts activity to assign authorizations for deleting task logs.
Consolidation area
Task
All tasks within the consolidation area are available.
Fields 1 through 7
All characteristics with the following roles are available:
Version
Group currency
Consolidation group
Consolidation unit
4/20/2019
If there are more than seven elds for restricting the authorization, enter all characteristics that you want to use for
restricting the authorization in Customizing for the consolidation area. These characteristics are then available
automatically when you maintain the roles.
Authorizations for Consolidation Groups and Units
The authorizations you set up for consolidation groups also apply to that group’s lower-level consolidation groups and units (see
Example 2 below).
To execute the following tasks, a user requires authorization for the consolidation units involved:
Postings to posting levels 00, 01, or 10
Validations of reported nancial data
Validations of standardized nancial data
Reconciliations
To execute all other tasks, a user requires authorization for the respective consolidation group. A user also requires
authorizations for lower-level consolidation groups to execute the following tasks:
Postings to posting levels 02, 12, 22, and 30
Validations of consolidated nancial data
Activities
To assign authorizations for tasks, you make the following Customizing settings:
A. Customizing for the Consolidation Area
If you have more than seven elds for restricting task authorizations, specify which characteristics you want to use to restrict
authorizations as follows:
1. Navigate to the process view of the Consolidation Workbench and choose Data Model Consolidation Area .
2. Open the required consolidation area in change mode.
3. On the Fields tab page, in the Auth.Check column (with the quick info text Char. Used in Auth.Check of Tasks), select the
indicator for those characteristics you want to use to restrict authorizations. (You can do this for up to seven
characteristics.)
4. Save the consolidation area.
B. Customizing in Role Maintenance (Transaction PFCG)
1. In the local system, start role maintenance from the SAP Easy Access screen by choosing Tools Administration User
Maintenance Role Administration Roles .
2. Specify an existing role or create a new role.
3. In role maintenance, navigate to the Authorizations tab page and choose Change Authorization Data.
4. Go to Strategic Enterprise Management SEM-BCS: Authorization Check for Task and de ne the authorizations for the
following:
Consolidation area
4/20/2019
Activity (or combination thereof; wildcard (*) possible)
Task (or multiple tasks; wildcard (*) possible)
If applicable, other characteristics with the following roles (combination and wildcard (*) possible):
Version
Group currency
Consolidation group
Consolidation unit
Caution
Until Release 3.1B, space characters (' ') and asterisks (*) were used as wildcards for all values. As of Release
3.2, entering an asterisk (*) for the consolidation unit grants the authorization to all existing consolidation
units for posting levels 01-10.
5. Save the authorizations.
6. Generate the role.
D. Checking Authorizations (System Activity)
Once you have completed the Customizing settings, the system can run an authorization check for the activities in the
consolidation monitor based on your de nitions.
Example
Example 1
You want to grant the following authorizations to a group of users in consolidation area 01 in all versions:
For data collection tasks and for consolidation groups A–C, you assign the following authorizations:
Block task
Unblock task
Execute task in update mode (execution)
Change task status
Display last log
For all other tasks and all other consolidation groups (D–H), you assign the following authorization:
You can achieve the authorization assignments by con guring the following Customizing settings: In role maintenance, you
specify the following parameters for the required role (under Strategic Enterprise Management SEM-BCS: Authorization
Check for Task ):
Manual: Authorization check for task
Activity
Block
4/20/2019
Unblock
Simulate
Execute
Change status
Display
Consolidation area 01
Task Collection of reported nancial data, collection of additional nancial data
1. Characteristic Consolidation group A–C
2. Characteristic Consolidation unit: company ' ' (space)
3. Characteristic Version *
4. Characteristic Group currency *
5. Characteristic *
6. Characteristic *
7. Characteristic *
Manual: Authorization check for task
Activity Simulate
Consolidation area 01
Task
Validation of reported nancial data
Standardization of reported nancial data
Reconciliations
Rounding
Validation of standardized nancial data
Elimination of interunit payables and receivables
Elimination of IU pro t and loss in transferred inventory
Reclassi cations
Allocation
Validations of consolidated nancial data
1. Characteristic Consolidation group D–H
2. Characteristic Consolidation unit: company ' ' (space)
3. Characteristic Version *
4. Characteristic Group Currency *
4/20/2019
5. Characteristic *
6. Characteristic *
7. Characteristic *
Example 2
This example demonstrates how authorizations you set up for consolidation groups affect the authorizations of that group’s
lower-level consolidation groups and units.
The following gure illustrates the initial situation:
Consolidation group CG1 contains consolidation group CG2 and consolidation unit C2000. Consolidation group CG2 contains
consolidation unit C1000.
Settings affect the authorizations as follows:
Post. Level Task Consol. Group Consol. Unit Result
00-10 M1 CG2 ' ' (space) Authorization to execute

task T1 for consolidation
unit C1000
00-10 T1 CG1 '' Authorization to execute

units C1000 and C2000
00-10 T1 '' C1000, C2000 Authorization to execute

units C1000 and C2000
02,12,22,30 M2 CG2 '' Authorization to execute

group CG2
4/20/2019
Post. Level Task Consol. Group Consol. Unit Result
02,12,22,30 T2 CG1 '' Authorization to execute

groups CG1 and CG2
More Information
Authorizations for Master Data
AS ABAP Authorization Concept
Locking Concept for Task Execution

Use
When you run a task in update mode, the system locks the transaction data that might be changed to prevent simultaneous
access.
No locks are set in tasks that do not change transaction data. No locks are set in test runs since test runs do not change
transaction data.
Locking Logic
Data is locked according to the posting level and the document type being processed.
Entries with Posting Levels 00–10
Tasks that post entries with posting levels 00 through 10 lock the consolidation units that are processed.
When you run currency translation or balance carryforward in update mode, the system locks all document types.
 Example
When a currency translation is executed in update mode, the system does not allow the simultaneous execution in update
mode of other tasks that post with posting levels 00–10 for the same consolidation units in the same version, group
currency, scal year, and period. The system also disallows reversals of manual documents with posting levels 01 or 10.
However, simultaneous changes to additional nancial data are allowed.
 Example
When a data collection task is executed in update mode, the system does not allow the simultaneous execution in update
mode of functions such as those listed below for the same consolidation units in the same version, group currency, scal
year, and period:
–Totals data entry layout
–Flexible upload
–Currency translation
4/20/2019
However, simultaneous changes to additional nancial data are allowed and it is possible to post any tasks in update mode
that post with a document type.
Entries with Posting Level 20
Tasks that post with posting level 20 lock all consolidation groups that contain the pairs of consolidation units and partner units
being processed.
 Example
The following gure shows a hierarchy of consolidation units with the consolidation groups CGTOP, CG1, and CG2, and the
consolidation units C1000, C2000, and C3000:
If you run an interunit elimination in consolidation group CG2 in update mode, the system locks all consolidation groups that
contain any of the unit pairs C1000/C2000, C1000/C3000, or C2000/C3000. In the example hierarchy, both consolidation
groups CG2 and CG1 are locked.
Entries with Posting Level 30
Tasks that post with posting level 30 lock the consolidation group being processed including any lower-level consolidation
groups.
Manual Posting
No locks are set during manual posting.
When you reverse or invert a document, the system sets the locks according to the posting level (see earlier). The document
number is also locked.
Mass Reversal
Mass reversals set the locks according to the posting levels used (see earlier). Therefore, you cannot simultaneously execute
tasks in update mode with the same document types for the organizational units being processed in the same version, group
4/20/2019
currency, scal year, and period.
Data Entry for Additional Financial Data
Starting in SAP SEM Release 4.0, you can enter reported nancial data and additional nancial data simultaneously.
Period Initialization
When you use period initialization to invert documents, the system sets the locks for each document type being processed
according to the posting level (see earlier). Therefore, you cannot simultaneously execute tasks in update mode with the same
document types for the organizational units being processed in the same version, group currency, scal year, and period. Each
document type is locked in the speci ed period and in the period in which the inverted documents are posted.
Sign-off Task
Use
Financial Compliance rules require one sign-off process to enable the CEO, CFO and other members of the management team
to certify the accuracy of nancial documents. You use this function to enable members of the organization to sign-off nancial
statements and meet compliance requirements.
Integration
This function integrates with SAP Business Work ow.
Features
This function has the following features:
Feature Description
Sign-off Assigned members of an organization can initiate a work ow to

request the review and approval of the nancial results.
List of work ows You can open the list of sign-off work ows to review the status and
determine if actions are required.
Noti cation You can receive the Sign-off Task noti cations in your E-mail,
Universal Work List in the SAP EP, or SAP Business Workplace. For
more information, see SEM-BCS Work ow Inbox..
Attachment You can attach comments and BI queries that display nancial
results. For more information, see Customizing the Sign-off Task.
Comment You can add comments to the sign-off work ow. For more
information, see Attaching Comments to the Status Work ow.
Example
CEOs and CFOs need to certify the accuracy of the nancial statements and other disclosures about the nancial condition and
operations of the company.
More Information
4/20/2019
Executing the Sign-off Task
Customizing the Sign-off Task
SEM-BCS Work ow Inbox
Executing the Sign-off Task

Use
You use the Sign-off Task to certify the information in the consolidated nancial statements are accurate. The two steps for the
Sign-off Task are:
1. Initiate the Sign-off Task. You can initiate the task and request that other members of the organization review and sign-
off on the nancial statements. You can initiate the Sign-off Task on a consolidation unit or group.
Note
When executing Sign-off Task on a consolidation group, the system rst processes the sign-off for the lowest level
consolidation units, then the next level up. When sign-off for all the units and subgroups are completed, then the
system processes the sign-off for the consolidation group. For more information, see Example: Executing Sign-off Task
on Consolidation Group.
2. Approve or reject the request. You can receive a request to review and sign-off the nancial statements. You have the
option to either approve or reject the accuracy of the information in the nancial statements.
Prerequisites
Use Work ow Variant Type 4.
Process
You can be both an initiator and approver for different Sign-off Tasks. You are an initiator when you begin a Sign-off Task request.
You are an approver when you receive a Sign-off Task request that has been initiated by someone else.
A. Initiate the Sign-off Task
1. From the Consolidation Monitor screen, select a consolidation unit or consolidation group.
2. Open the Context Menu and select Update-run. The Execution screen displays.
3. Select the execution parameters: Version, Fiscal Year, Period.
4. Click the Sign-off Info tab. Select the available BI queries or add additional prede ned queries. You can also attach
comments. reviewer views these queries and comments during the approval process.
B. Approve or Reject the Sign-off Task
The approver receives the request in the following locations:
SAP Workplace Inbox
UWL (Universal Work List) of the Enterprise Portal
SEM—BCS Inbox
4/20/2019
The approver performs do the following activities:
Access the list of execution parameters
Access the list of consolidation units or groups associated with the Sign-off Task
Access all the attached BI queries and comments
Attach more BI queries and comments
Approve or reject the sign-off request
If the approver approves the sign-off request, the sign-off moves to the next approve on the list. If all approvers have approved
the Sign-off Task, the task is complete. If the approver rejects the Sign-off Task, the task is returned to the initiator.
More Information
Sign-off Task in Consolidation Monitor
Attaching Comments to the Status Work ow
Customizing the Sign-off Task
Example: Executing Sign-off Task on

Consolidation Group
When you execute the sign-off task on a consolidation group, the system rst processes the task for the lowest level
consolidation units, then processes the task for the next level up. It continues processing in ascending levels until all the units
and subgroups are nished, then processes the parent consolidation group.
The following illustrates how this process works.
In this example, you want to initiate sign-off from Consolidation Group CG1. Before the sign-off is triggered, the consolidation
monitor looks like this.
Group hierarchy Sign-off Task Status Does Sign-off Work ow exist?
CG1 Initial No
CU 9000 Blocked No
CG2 Initial No
CU 1000 Initial No
CU 2000 Blocked No
CG3 Blocked No
CU 3000 Blocked No
CU 4000 Blocked No
CG — Consolidation Group
CU — Consolidation Unit
4/20/2019
When you execute the sign-off task for group CG1 the status changes. The following status shows the system has started the
sign-off process for CU 1000 and its status is set to Blocked, Pending Approval.
CG1 Incomplete No
CU 9000 Blocked No
CG2 Incomplete No
CU 1000 Blocked, Pending Approval Yes
CU 2000 Blocked No
CG3 Blocked No
CU 3000 Blocked No
CU 4000 Blocked No
The following status shows the sign-off is nished for CU 1000 and its status is set to Completed.
All the consolidated units below CG2 are complete. The system begins processing for CG2 and its status changes from
Incomplete to Blocked, Pending Approval. For more information, see Sign-off Task in Consolidation Monitor.
CG1 Incomplete No
CU 9000 Blocked No
CG2 Blocked, Pending Approval Yes
CU 1000 Blocked Completed
CU 2000 Blocked No
CG3 Blocked No
CU 3000 Blocked No
CU 4000 Blocked No
The following status shows the sign-off is nished for CG2 and its status is set to Completed.
All the consolidated units and groups below CG1 are complete. The system begins processing for CG1 and its status changes
from Incomplete to Blocked, Pending Approval.
CG1 Blocked, Pending Approval Yes
CU 9000 Blocked No
CG2 Blocked Completed
CU 2000 Blocked No
CG3 Blocked No
4/20/2019
CU 3000 Blocked No
CU 4000 Blocked No
This is the status when the sign-off process for CG1 is complete.
CU 9000 Blocked No
CU 2000 Blocked No
CG3 Blocked No
CU 3000 Blocked No
CU 4000 Blocked No
Customizing for the Sign-Off Task

Use
Use the following steps to set up and customize the sign-off task.
Prerequisites
The Work ow for Status Changes option is activated in the consolidation area.
Process
You must perform the following four steps to con gure and customize the sign-off task.
A. Con gure Work ow Variant
The sign-off task uses the SAP Business Work ow. Go to the SEM-BCS Customizing workbench and choose Consolidation
Functions Sign-Off Work ow Variant . Create a work ow variant.
Specify one or more approval agents for the sign-off task. You have two options:
Select speci c users by name.
Select the Approval Agent attribute of the consolidation units or groups by means of cross-characteristic selection. The
approval agent is determined when you initiate the sign-off task based on the attributes of the consolidation units or
groups. Since you can initiate the sign-off task for both consolidation groups and consolidation units, specify the Approval
Agent attribute for both groups and units.
B. De ne Task
4/20/2019
Go to the Customizing workbench and choose Consolidation Functions Sign-Off .
Create a sign-off task and con gure the following settings:
If you are using a data model for matrix consolidation, select the matrix dimension for which the sign-off task is relevant.
De ne the executability of the successor tasks. We recommend that you use the default settings: these settings specify
that successor tasks are indicated as executable provided they are not Sign-Off tasks.
Select the consolidation units or groups to include in the sign-off task. Deselect the units or groups you want to exclude.
Select one or more BI queries. The BI queries provide nancial results and can be viewed by the initiator and approvers.
Select one or more work ow variants. You can select different work ow variants for different consolidation units and
groups.
Note
To select more than one work ow variant, you need to implement BAdI UC_WFV_STAT and method
CHECK_IF_START. For more information, see BAdI UC_WFV_STAT.
C. Assign Sign-Off to Task Hierarchy
You can de ne one or more sign-off tasks. You can assign exactly one sign-off task to each task group; this must be the last task
of the task group.
You can also assign an additional sign-off task as the last task of the entire task hierarchy.
If the sign-off task is not the last task in a task group or the last task in the task hierarchy, a warning message is displayed.
D. Assign Authorizations for Sign-Off Task to Roles
The system administrator must use the authorization object R_UC_TASK and assign the following authorizations to the roles
used in the sign-off task:
The person who initiates the sign-off task (the initiator) is authorized to execute sign-off for selected consolidation
groups and units.
The initiator is authorized to block all preceding tasks and the sign-off task for consolidation groups and units for which
he or she is responsible.
The authorization to reset the sign-off task is assigned to a restricted set of users. This is a compliance requirement.
Sign-Off Task in Consolidation Monitor

Use
You use the consolidation monitor to review the status of the sign-off task work ow and determine whether you need to take
any action.
Different functions are available in the context menu depending on the status.
Features
Sign-off Task Status and Context Menu Functions
4/20/2019
Status Applies to Description Context Menu Function
Initial Consolidation group or unit The sign-off task has not been Update Run
triggered. (Default)
Execute the sign-off task and
trigger the work ow.
Incomplete Consolidation group only There are pending tasks for the Reset
consolidation group's
Reset the status of the current
subgroups and units.
unit or group only.
Blocked, Pending Approval Consolidation group or unit Sign-off is waiting for approval. Reset
Cancel the work ow. Reset the

status of the current and parent
group.
Blocked Consolidation group or unit Sign-off approved and Reset

successfully completed.
and parent group.
Unblocked Consolidation group or unit Approval is rejected by one of Update Run

the approvers.
Reset

unit or group only.
Reset Consolidation group or unit Sign-off is reset. All pending Update Run
processes are canceled.
Not Applicable Consolidation group or unit Do not execute sign-off task for
the consolidation group or unit.
You con gure this setting on the
Sign-off Task Customizing
screen. For more information,
see Customizing for the Sign-
Off Task.
Note
The group level status does not represent the status of the subordinate units. The subgroups and units each have a
separate sign-off status.
Note
The Reset action has different results, depending on the status. For more information, see the Context Menu Function
column in the table above.
Guidelines
You can trigger the sign-off task at unit level and group level. When you execute the sign-off task at group level, it only
affects the current consolidation group and its subordinate subgroups and units.
4/20/2019
In matrix mode, you can only trigger the sign-off task for the consolidation units and consolidation group of the matrix
dimension for which you have de ned the sign-off task.
When you trigger a sign-off task that is at the end of a task group, the system sets the status of all tasks of this task
group to “Blocked”. The tasks of the task group cannot be unblocked by any user until the sign-off task has been
unblocked or reset.
When you trigger a sign-off task that is at the end of the entire task hierarchy, the system sets the status of all preceding
tasks to “Blocked”. The preceding tasks cannot be unblocked by any user until the sign-off task has been unblocked or
reset.
Once a sign-off task has been triggered, only an authorized user can reset it.
The sign-off task is not executed automatically as part of a task group: you need to execute the sign-off task manually.
The sign-off task in the multi-period consolidation monitor is also not executed automatically with the task group for the
remaining period.
Attaching Comments to the Status Work ow

You can attach comments to the Status Change Work ow for the next person in the work ow to view.
The system accepts comments in these four formats:
Plain text
Word
Excel
PowerPoint
Restrictions to Editing Comments in Work ows

Compliance requires that saved comments in SEM-BCS cannot be modi ed, even by the original author. This is changed from
the previous function, which allowed any one who has access to the document in the approval process to modify the existing
comment
This new restriction applies to all SEM-BCS work ow functions:
Document Approval Work ow
Status Change Work ow
Sign-off Task Work ow
Note
Comments outside of SEM-BCS work ows are not affected. You can still modify comments for documents in the Journal
Entry List.
Task Log
Use
4/20/2019
By default, after you execute a task the system displays a log, which shows the postings that took place. (Note: Logs are
sometimes called audit trails .) Logs for certain task categories have specially-designed layouts.
The data collection task creates a separate log for each method, data stream type, le name, and document type.
Note
The task log lets you choose between total documents and delta documents if you use one of the following, posting-level-30
task categories in multilevel hierarchies of consolidation groups:
Consolidation group change
Posting of group shares
Reclassi cation (document type assigned to posting level 30)
The task log displays the delta documents by default. To switch the display, choose Other Layout .
Con guration of Task Logs

Use
You use this function to copy the layout of a standard log to custom layouts and modify them to suit your requirements.
Key Features
You cannot change the layout of the standard logs. However, you can copy the layout of a standard log as often as you like,
name the copy, and modify it to suit your requirements.
The layout can be con gured in the following respect:
You can show or hide a characteristic or key gure.
You can allow breakdowns for a characteristic. In the log, you can then expand the characteristic accordingly.
You can show or hide the description of a characteristic value.
In some partial lists of a log, you can change the sequence of characteristics and key gures (for example, using drag and drop).
Note
Active layouts are assigned to a task depending on the version, time, and period category.
The task logs of data collection tasks cannot be con gured.
Activities
A. Customizing of the Layout
Create a task and de ne a custom log layout in task Customizing in the group box Log.
1. Create a custom log layout:
4/20/2019
a. Enter the name of the new layout in a free row of the log table.
b. To access the layout de nition, choose the navigation arrow.
c. In the de nition area, select the standard log, which is to be used as a template for the new layout.
Or
a. Select the standard log in the log table and choose the Copy pushbutton.
b. Overwrite the layout name of the row that appears.
c. To access the layout de nition, choose the navigation arrow.
2. Modify the log layout to suit your requirements:
a. On the left-hand overview screen, select the partial list to be changed.
b. Modify the layout characteristics of the features and key gures:
Default: The showing/hiding of characteristics and key gures, setting/deleting of breakdowns, and
showing/hiding of descriptions are each performed in the optimum way for the task.
Yes: Characteristics and key gures are de nitely shown, breakdowns are de nitely set, and descriptions
are de nitely shown.
No: Characteristics and key gures are de nitely hidden, breakdowns are de nitely deleted, and
descriptions are de nitely hidden.
3. Activate the logs that you want to see after the task has been executed.
4. Where necessary change the sequence of the active logs, since by default the rst active log is displayed after the
execution of the task.
B. Navigation Between Multiple Active Layouts
The rst active log appears immediately after the task has been executed. To navigate to the other logs, choose the Select
Other Layout pushbutton in the toolbar.
Saving Task Logs

Use
By default, a task appears in the log as soon as it has been performed. You can specify that this log is saved and/or that this log
is not displayed directly after a task has been performed.
It is useful to save a task log in the following situations in particular:
Performing multiple tasks successively
Performing a task in background mode
Prerequisites
The task log in accordance with Customizing is saved or suppressed only when the task is performed in update mode.
Features
4/20/2019
Saving a Log
The system saves the log most recently executed for a consolidation unit or a consolidation group.
If you use multiple layouts for the task log, all active layouts are saved.
If you execute multiple methods of a data collection task successively (for example, exible upload or copy method), all logs for
these methods are saved.
Calling a Log
When calling the most recently saved log for a consolidation unit or a consolidation group in the consolidation monitor, the
system uses the following logic:
The system searches for all saved logs for consolidation units or consolidation groups that compared with the calling
consolidation unit or the calling consolidation group are on the same or lower level.
The system searches for the rst saved log for a consolidation unit or a consolidation group by starting at the level of the calling
consolidation unit or the calling consolidation area searching the higher levels from bottom to top.
If more than one saved log is found for a consolidation unit or a consolidation group, the system displays the following
information for the logs found, which you can use to select the log of your choice:
Consolidation unit or group for which the log was created
Date on which the log was saved
Time at which the log was saved
If the task is a data collection task, the following information can also be displayed:
Data stream type
Method name
File name
File storage
Document type
Activities
Customizing for Saving or Displaying a Log
You de ne whether the log for a task is saved and/or not displayed in Customizing for the relevant task.
The indicators Save Log and Do Not Display Log in the log section of task Customizing are not set as standard.
You can set these indicators independently for each version.
Calling a Log
You can call the saved log at a later point in time, by positioning the cursor on the status symbol in the consolidation monitor
and choosing the Last Log option from the menu or the context menu.
4/20/2019
Deleting a Log
In the process view of the workbench, you can delete saved logs by choosing Consolidation Monitor → Delete Logs.
On the selection screen, you enter the logs that the system is to search for.
In the resulting list of saved logs that appears, you can delete the log entries to be deleted from the list line-by-line.
Multiperiod Consolidation
Use
You use multiperiod consolidation to execute tasks and task groups for a timeframe that spans more than one scal period.
Multiperiod consolidation is especially bene cial for planning and forecasting:
You can process task groups in multiple periods without having to change parameters when switching to the next period.
(This applies to tasks of all task categories.) You can use the exible upload function, for example, to upload your
reported nancial data of multiple periods in a single run.
You can execute task groups in background mode.
Integration
A consolidation cycle (the timeframe for multiperiod consolidation) applies to a particular version combination.
Execution of tasks in multiple periods is also used in restatements: The restatement function is executed in multiple periods in
the past.
Prerequisites
The prerequisites are discussed in the section Customizing for Multiperiod Consolidation .
Features
Multiperiod consolidation has the following features:
In the consolidation monitor, you can execute a task group in multiple periods (to be more exact, in the remaining
periods of a consolidation cycle).
When executing individual tasks, you also can do the following functions in the consolidation monitor:
Block the task in the remaining periods of a consolidation cycle
Unblock the task in the remaining periods of a consolidation cycle
Reset the status of the task in the remaining periods of a consolidation cycle
You can schedule a task group for background execution - for a single period or for multiple periods.
In the consolidation monitor, you can use buttons for easy navigation from one period to another within a consolidation
cycle.
From within the consolidation workbench, you can execute task groups with a selection screen - for a single period or for
multiple periods.
4/20/2019
You can assign multiple balance carryforward tasks to a task hierarchy. These tasks can have different posting levels. You
need this feature if you want to execute only a subset of the consolidation tasks using multiperiod consolidation. (For
example, if you run two-sided eliminations, you need a balance carryforward task with posting level 20.)
Example
You use version combination 100 for consolidating every scal quarter, using actual data as a basis, hereby adhering to IFRS
(International Financial Reporting Standards).
You use version combination 200 for consolidating yearly, using planning data as a basis, hereby adhering to IFRS. Every year
you do a rolling forecast for the next ve years. To do this, you use multiperiod consolidation. You set each starting year to the
year that follows the current year; and you set the consolidation cycle to ve years.
Execution of Task Groups and Status

Changes
Use
You use this function of multiperiod consolidation to execute a task group in multiple periods and to make status changes to
task groups and tasks.
Prerequisites
You have made all Customizing settings for consolidation. In particular, you have de ned the task hierarchy you want to use in
multiperiod consolidation.
You have carried out Customizing for multiperiod consolidation.
Features
Monitor and Workbench: Execute Task Groups in Remaining Periods of a Consolidation Cycle
Multiperiod consolidation allows you to execute a task group in multiple periods at once - in the consolidation monitor and in the
consolidation workbench. This is possible for the remaining periods of a consolidation cycle, which are all valid periods of the
consolidation cycle that are greater than or equal to the current period. These periods are determined by the consolidation
cycle you have assigned to the version combination as time dependent.
(In the workbench, you also can execute the task group for a single period.)
The system executes the task group one period at a time, starting with the current period. The system processes the periods
successively in ascending order.
Note
If you use parallel processing of tasks in the consolidation monitor, the system executes the independent task packages
asynchronously, taking into consideration the order you de ned in Customizing.
For more information on parallel processing, see SAP Note 761274.
At the end of task processing, the monitor switches the period: If errors occurred, the status display switches to the rst period
in which an error occurred. Otherwise, the status display switches to the last period of the consolidation cycle.
4/20/2019
Monitor: Execute Tasks and Task Groups and Make Status Changes
The following table shows which functions are available in the monitor for executing tasks and task groups and for changing the
status of tasks and task groups.
You can call most of these functions in the context menu as well as in the Tasks menu of the monitor.
Monitor: Execution and Status Changes for Tasks and Task Groups
Task Group/ Task Function Explanation
Task Block by user intervention in the remaining Prerequisite: The task status must be
periods of a consolidation cycle changeable.
If a task is to be blocked in a period, status

management only checks the respective
status of preceding tasks in the current
period. It does not, however, check the
status in prior periods.
Task Unblock in the remaining periods of a The system unblocks the selected task and
consolidation cycle all successor tasks in the remaining
periods.
Task Reset status in the remaining periods of a The system resets the status of the
consolidation cycle selected task and all successor tasks in the
remaining periods.
Task group Update in the remaining periods of a The following applies in update mode:
consolidation cycle
All tasks that are updated manually are
automatically blocked.
Once the system has successfully executed

automatic tasks, it blocks these tasks
automatically.
Task group Update (without blocking) in the remaining The following applies in update mode:
periods of a consolidation cycle
The system skips all tasks that are
updated manually.
Once the system has successfully executed

automatic tasks, it does not block these
tasks.
Task group Block by user intervention in the remaining None

periods of a consolidation cycle
Task group Unblock in the remaining periods of a The system unblocks only the blocked
consolidation cycle tasks in the remaining periods of the
consolidation cycle.
Task group Reset status in the remaining periods of a The system resets the status of the task
consolidation cycle group and all successor tasks in the
remaining periods.
Monitor: Navigation Among Periods of a Consolidation Cycle
In the consolidation monitor, you can use the following buttons for easy navigation from one period to another within a
consolidation cycle:
: First Period
4/20/2019
: Previous Period
: Next Period
: Last Period
 Example
Version: P02; consolidation cycle: "5-Year Cycle" (starting period/year: 001/2004); consolidation frequency: quarterly
consolidation; current period: 006/2005
: scrolls to the rst period of the consolidation cycle (001/2004)
: scrolls to the previous period of the consolidation cycle (003/2004)
: scrolls to the next period of the consolidation cycle (009/2005)
: scrolls to the last period of the consolidation cycle (012/2008)
Workbench and Monitor: Execute Task Groups in the Remaining Periods with Selection Screen
To execute a task group in the remaining periods with a selection screen, you need to assign a consolidation cycle to the present
version combination. Only then is the Execute in Remaining Periods indicator on the selection screen ready for input.
If you select this indicator and then execute the task group, the system executes the task group for all remaining periods of the
consolidation cycle, starting with the period and scal year you entered on the selection screen. Therefore, the period and year
you enter must valid for the consolidation cycle.
If you do not select the indicator, the system executes the task group only for the period you specify.
You can execute a task group with selection screen only in update mode.
On the selection screen for task groups, you can specify whether the system is to automatically block successfully executed
tasks once it has executed the task group.
Background Processing of Tasks and Task Groups
You can also schedule task groups for background execution. This can be useful for task groups that require a long time to
execute.
Activities
When you execute a task group, the following activities are performed either by you or the system:
Monitor: Execute Task Group in Remaining Periods
To start the function in the context menu, proceed as follows:
1. In the monitor, position the cursor on the eld for the consolidation group and the task group.
2. Call the context menu and choose Multiperiod Consolidation Update in Remaining Periods .
To start the function in the menu, proceed as follows:
1. In the monitor, position the cursor on the eld for the consolidation group and the task group.
4/20/2019
2. In the menu, choose Tasks Update Update in Remaining Periods .
Monitor: Execute Task Group with Selection Screen
To execute a task group in the remaining periods of a consolidation cycle, proceed as follows:
1. In the monitor, position the cursor on the desired combination of task group and organizational unit.
In the menu, choose Tasks Execute with Selection Screen .
The Workbench: User Restrictions for Task Group <name of task group> screen appears.
2. Enter the required parameters. Make sure that the period is valid for the consolidation cycle.
Select the Execute in Remaining Periods indicator.
3. Click the Execute button.
Workbench: Execute Task Group with Selection Screen
To execute a task group in the remaining periods of a consolidation cycle, proceed as follows:
1. In the process view of the workbench, choose Consolidation Monitor Task Hierarchy , and in the context menu choose
Display.
The task hierarchy is displayed.
2. Select the task group you want to execute and in the context menu choose Execute with Selection Screen.
The Workbench: User Restrictions for Task Group <name of task group> screen appears.
3. Enter the required parameters. Make sure that the period is valid for the consolidation cycle.
Select the Execute in Remaining Periods indicator.
System Activities when Executing a Task Group
The system proceeds as follows when you execute a task group:
It determines which periods are relevant.
It processes all periods successively in ascending order.
It executes these tasks in their de ned sequence for each period.
It skips tasks that require user interaction and executes in update mode all tasks in the task group that post
automatically.
In doing so, the system automatically locks all manual tasks as well as all automatic tasks that have been executed
without errors.
It checks each task that is executed for errors:
If you have not chosen Update Without Blocking, it blocks all tasks that do not contain errors.
It executes all other tasks in the remaining periods of the consolidation cycle that are de ned as successor tasks
of the tasks executed without errors.
If errors occur when executing a task, the system only executes this task in the remaining periods if the task is a
non-posting task (for example, a validation task).
4/20/2019
It changes the screen in the monitor as follows at the end of processing:
If no errors occurred, the monitor shows the last period of the consolidation cycle.
If errors occurred, the monitor switches to the rst period in which an error occurred.
Status Management in Multiperiod

Consolidation
Use
You use this function in multiperiod consolidation to monitor the progress of the tasks for each individual consolidation unit or
consolidation group.
Prerequisites
You have activated status management (in the process view of the Workbench, under Consolidation Area on the Settings tab
page you have set the indicator for status management).
You have set the indicator for multiperiod consolidation (in the process view of the Workbench, under Consolidation Area on the
Settings tab page).
Features
When processing a single period of a consolidation cycle, status management works the same as when consolidating a single
period (see the section Status Management in the Consolidation Monitor ).
However, to avoid performance bottlenecks due to status updates, status management is not supported across different
periods of a consolidation cycle. This has the following consequences:
Unblocking a task or executing a task in a speci c period has no effect on the tasks in subsequent periods.
However, instead of using the Unblock option, you can use the Unblock in Remaining Periods of the Consolidation Cycle
option.
When you block a task, the system does not check the status of tasks in the preceding periods.
As when consolidating a single period, the system still takes into consideration the relationships between the tasks by taking
preceding tasks into account and by resetting successor tasks.
For more information on manual status changes in multiperiod consolidation, see Execution of Task Groups and Status Changes
).
Balance Carryforward Tasks for Multiperiod

Consolidation
Use
You can assign multiple balance carryforward tasks to a task hierarchy. These tasks can have different posting levels . You need
this feature if you want to execute only a subset of the consolidation tasks using multiperiod consolidation.
4/20/2019
 Example
You want to perform only all of your two-sided eliminations in a planning version.
In this case, you need a balance carryforward task with posting level 20.
Features
One or More Balance Carryforward Tasks with Different Posting Levels
In multiperiod consolidation you can use balance carryforward tasks for speci c posting levels to carry forward only the
necessary data records when executing a task group across a scal year boundary.
You choose one of the following options in a balance carryforward task:
Posting Levels Data to be Carried Forward
All posting levels Data with all posting levels, except data records posted in
consolidation group changes, but including additional nancial data
for investments and equity
Reported nancial data, adjustment and standardizing entries Data with posting levels 00, 01, and 10, including additional
nancial data for investments and equity
Two-sided elimination entries Data with posting level 20
Consolidation group-dependent entries Data with posting levels 02, 12, 22, and 30, except data records
posted in consolidation group changes
Note
An All Posting Levels option also exists in the period initialization task . In contrast to here, period initializations process data
at the consolidation group level.
How the system updates the task status depends on the posting levels to be carried forward.
 Example
When carrying forward consolidation group-dependent data records, you do not need to unblock tasks on the consolidation
unit level as long as you use a balance carryforward task of the category Consolidation Group-dependent Entries .
You need to de ne the task hierarchy so that the balance carryforward tasks used in that hierarchy (as a whole) cover all
posting levels. This is the only way to ensure that the opening balances of the new scal year are consistent.
You need to arrange the balance carryforward task in the task hierarchy according to the posting levels assigned to it (see also
the example below). You can add balance carryforward tasks to the task hierarchy in the following ways:
One balance carryforward task with the category All Posting Levels ;
This must be the rst task in the task hierarchy.
Three or more balance carryforward tasks, including:
One task with category Reported Financial Data, Adjustment and Standardizing Entries
4/20/2019
Tasks with this category can be located in the task hierarchy anywhere prior to the consolidation group-
dependent tasks.
One task with category Two-sided Elimination Entries
Tasks with this category must not be at the beginning of the task hierarchy, but must be prior to the consolidation
group-dependent tasks.
One task with category Consolidation Group-dependent Entries
Tasks with this category must not be at the beginning of the task hierarchy, but must be prior to the consolidation
group-dependent tasks.
You can have multiple tasks in the task hierarchy for each of these three task categories.
When you assign the tasks to the task hierarchy, the system checks whether these tasks are in the correct sequence.
Integrate Copy Method in a Balance Carryforward Task
To have a balance carryforward task include data from another version, or even from another consolidation area, you can assign
a copy method to the balance carryforward task. If you do this, the system rst executes the copy method, which processes the
complete prior-year data from the source. After this preparation, the data ows into the balance carryforward logic.
The system applies the copy method only when the balance carryforward is executed for the rst year of a consolidation cycle.
The copy method must have the following Customizing settings:
The copy method might require a speci c data type depending on which posting levels are processed in the balance
carryforward task:
If the task carries forward additional nancial data for investments or equity, the copy method needs the data
type All Data Types .
In all other cases, the data type Reported Financial Data suffices.
The copy method must have the input type Cumulative because all of the prior year data needs to be carried forward.
You can use the settings of the copy method (in particular, the settings for eld mapping and the source selection). When
doing this, make sure you manipulate the data in a way in which the opening balances resulting from the balance
carryforward remain consistent.
Example
A task hierarchy with multiple balance carryforward tasks might look like this. As you can see, the balance carryforward tasks
cover all posting levels and are arranged in the hierarchy according to their posting level.
Hierarchy "Monitor"
Data collection task 1
Balance carryforward, all posting levels
Period Initialization
Balance carryforward, posting levels 00-10
Data collection
Copy totals data (from version 100 to 200)
4/20/2019
Data collection for multiperiod consolidation
Manual posting
Reclassi cation
Validation of reported nancial data
Data collection task 2
Currency Translation
Validation of standardized nancial data
Consolidation 1
Balance carryforward, posting level 20
Elimination of interunit receivables and payables
Consolidation 2
Balance carryforward, posting level 30
Reclassi cation, posting level 30
Manual posting, posting level 30
Additions to consolidation group
Divestitures from consolidation group
Validation of consolidated nancial data
See also:
Balance Carryforward
Customizing for Multiperiod Consolidation

Purpose
You perform these Customizing steps to enable the use of multiperiod consolidation.
Process Flow
A. Activate Multiperiod Consolidation
1. Go to the process view of the Consolidation Workbench and select the appropriate consolidation area.
2. On the Settings tab page in the Consolidation Monitor group box, select the indicator for multiperiod consolidation.
3. Save the consolidation area.
The entry Consolidation Cycle now appears under Data Model Periodicity in the process view of the workbench.
B. De ne the Consolidation Cycle
4/20/2019
1. Choose the entry Consolidation Cycle under Data Model Periodicity in the process view of the workbench.
2. Create a new consolidation cycle and give it a name.
3. De ne the delta year 00 as the starting year (this is mandatory), and assign a consolidation frequency.
4. If needed, de ne additional delta years and assign a consolidation frequency to each delta year.
Note
The delta years must be consecutive (they must not have gaps).
An example of valid delta years of a consolidation cycle is: 00, 01, 02, 03.
5. Save the consolidation cycle.
C. Assign Consolidation Cycles to a Version Combination
Now you need to assign all of the consolidation cycles you want to use to a version combination. The assignment is time-
dependent.
1. Go to the process view of the workbench, choose Master Data Versions , and choose Customizing for version
combinations.
2. Specify the consolidation cycle and the starting period and year for each version combination you want to use in
multiperiod consolidation.
(If you do not want to use a version combination for multiperiod consolidation, specify only a consolidation frequency.)
For multiperiod consolidation, a starting period is required, but a starting year is optional. For the starting period, select
a period that is valid for the consolidation frequency you have assigned to delta year 00 in the consolidation cycle
Customizing settings.
If you do not specify a starting year, the consolidation cycle must span only one year. This means that the Customizing
settings for the consolidation cycle must have an entry for delta year 00 only.
If you do not specify a starting year, the system uses the year presently set in the permanent parameters. In this case,
you can use the version combination in the subsequent years without needing to manually adjust the starting year.
3. Save the version combination.
See also the example below.
Result
Now you are able to use the functions of multiperiod consolidation in the consolidation monitor and in the consolidation
workbench.
The title bar of the consolidation monitor now displays Monitor for Multiperiod Consolidation , and the buttons for navigating
among the periods of the consolidation cycle appear on the screen.
In the consolidation workbench, the Execute in Remaining Periods indicator now appears on the selection screen for executing
task groups. (You can select this option only in update mode.) The indicator is ready for input only if a consolidation cycle is
assigned to the current version combination.
Example
4/20/2019
The following table illustrates an example of the assignment of consolidation cycles and (alternatively) consolidation
frequencies to version combinations.
DataSlice VersionNumber AccountingStandards DataCategory ConsolidationFrequency ConsolidationCycle Start Start …

period year
92 100 US GAAP actual Yearly …
92 200 US GAAP Plan U.S. Annual Cycle 001 2006 …
92 001 IFRS actual Monthly …
92 002 IFRS Target IFRS Semi-Annual 001 2007 …

Target
92 010 German GAAP actual Quarterly …
Background Processing of Tasks and Task

Groups
Use
You use this function to execute tasks and task groups in the background. You can shift performance-intensive tasks to times of
the day at which your system has more capacity.
In multiperiod consolidation, you can execute a task group for remaining periods of a consolidation cycle in background mode.
Features
You can use background processing in the following ways:
When consolidating a single period:
Execute individual tasks
Execute task groups
You can access these functions in the menu of both the consolidation monitor and the consolidation workbench by
choosing Environment Schedule Task or Schedule Task Group.
When consolidating multiple periods:
Execute task groups
In each case, you can use variants. The variant contains all other relevant parameters (organizational unit, version, time, and
currency, as well as speci cation of whether the system is to block the tasks automatically once it has executed the task group).
You create variants on the selection screen of the report; these are not variants from the consolidation workbench.
The variants for executing task groups in background mode also include the Execute in Remaining Periods indicator. You select
this indicator when consolidating multiple periods. For more information about this indicator, see Execution of Task Groups and
Status Changes.
Activities
In multiperiod consolidation, to call up or schedule a task group in background mode, proceed as follows:
4/20/2019
1. In the monitor for multiperiod consolidation (or in the workbench), go to the menu and choose Environment Schedule
Task Group .
The Execute Task Group or Schedule Task Group in Background screen appears.
2. Specify a task group and a variant.
Make sure that you select the Execute in Remaining Periods indicator in the variant.
The system executes in the background the task group with the parameters stored in the variant.
It issues messages about the progress of processing in the job log.
More Information
Background Processing
Parallel Execution of Tasks

Use
If you start the execution of a task group, the system executes the tasks sequentially by default. To reduce the runtime, you can
activate the function to execute the tasks in parallel.
Features
Parallel Execution of Tasks in a Task Group
The system can execute tasks in a task group in parallel if there are no preceding or succeeding task relationships.
To activate this function, you must de ne the UC_SERVER_GROUP parameter in the user parameters.
Parallel Execution of Tasks in a Task Group in Multiperiod Consolidation
If you have activated the business function Financials, Group Close from Enhancement Package 2 and you execute a task group
in the remaining periods in multiperiod consolidation, the system can also execute tasks in various periods in parallel. As before,
the system only executes tasks in parallel between which there are no preceding or succeeding relationships.
To activate this function, you must de ne the UC_SERVER_GROUP parameter in the user parameters.
Packaging Unit-Based Tasks
If you have activated the Financials, Group Close business function from Enhancement Package 2, you can also package unit-
based tasks. In doing so, the system puts consolidation units into packages and executes the same task in parallel for multiple
packages.
 Example
For example, the system can execute balance carryforward tasks, currency translation tasks, and unit-based validation tasks
for various consolidation units at the same time.
To activate this function, you must de ne the UC_SERVER_GROUP and UC_PACKAGE_SIZE parameters in the user parameters.
4/20/2019
Activities
To activate the parallel execution of tasks, enter the following parameters in your user pro le (transaction SU03):
Parameter ID Parameter Value (Example) Description
UC_SERVER_GROUP parallel_generators If you enter this parameter, the function for

the parallel execution of tasks is active. You
can nd the permitted values in transaction
RZ12.
UC_PACKAGE_SIZE 20 Number of Consolidation Units Per Package
The higher the value, the higher the degree

of parallel processing.
The optimum value depends on the

available hardware.
Data Model
De nition
De nes the prerequisites for consolidation.
In the data model you de ne the master data and Customizing data, for example, tasks, method layouts, methods and
document types.
Use
Before you can use the Consolidation functions, you must de ne the data model in Customizing.
Structure
The data model is characterized by
Its data basis , which is based on the InfoProviders in BI that are relevant to Consolidation
The consolidation area
The following graphic shows the dependencies between data streams, the data basis and the consolidation area:
4/20/2019
The data model is further characterized by:
Currencies
Versions
Tasks , document types , and methods
Financial statement items , and – if desired – the consolidation chart of accounts , subassignments , and breakdown
categories
Organizational units ( consolidation units and consolidation groups )
Data Basis
4/20/2019
De nition
De nes the data model for consolidation, which consists of the characteristics and key gures with their respective roles for
consolidation.
Structure
Data bases have numerous properties and settings, which you con gure on the following tab pages:
Field Catalog
The consolidation system (SEM–BCS) uses precisely one RFC destination to the BI system (SAP NetWeaver Business
Intelligence). This RFC destination is used to transmit the transaction data to the consolidation system. If you do not specify an
RFC destination, the system uses the BI system located in the SEM system.
After specifying the RFC destination, as the next primary setting you specify the InfoCube that contains the totals records used
in the consolidation system. You can use one of the InfoCubes 0BCS_C10, 0BCS_C11, or 0BCS_C50 as a template. These objects
are part of standard Business Content.
You also make the following settings:
You can assign one InfoObject catalog for characteristics, and another for key gures, to access other elds that reside in
the BI system but are not assigned to any of the data targets used (see Additional Financial Data). You use this option to
add more elds for attributes or to add a layout of assets and liabilities. This option also lets you de ne an external eld
catalog for a source data basis.
SAP Business Content includes the InfoObject catalogs 0BCS_CHA01 (characteristics) and 0BCS_KYF01 (key gures)
for this purpose.
You can assign one or more source data bases to a data basis.
Data Model
The settings on this tab page involve:
Role assignments for totals record elds
Characteristics with the role consolidation unit
Assets/liabilities
Role Assignments for Totals Record Fields
In the data model, at least one eld needs to be assigned to each of the following roles:
Version
Group currency key
Consolidation unit
Consolidation group
Partner unit
Item
Document type
4/20/2019
Posting level
Time characteristics ( scal year and period)
Value in group currency
Each characteristic with the role consolidation unit also requires one or more additional characteristics with one of the following
roles:
Partner unit
Consolidation group
You may need other characteristics and key gures depending on which consolidation functions you want to use.
Additional Characteristics and Key Figures Required Depending on Consolidation Function
Consolidation Function Characteristics and Key Figures Required
In general: the local currency and/or transaction currency
(in addition to the group currency)
For recording temporal translation differences: the

translation indicator
Interunit eliminations and reconciliations

For splitting the transaction currency: key gure
transaction currency
For eliminating quantities: key gure quantity
Allocation
For reporting sender and receiver objects: the clearing
characteristic
Unit of measure
Quantity
For each characteristic with the role consolidation unit, you

need one or more characteristics with the role investee unit
Investor unit – if applicable (for each characteristic with the

role consolidation unit, you need one or more
characteristics with the role investor unit)
Characteristics with the Role Consolidation Unit
If a data model has more than one characteristic with the role consolidation unit, you need to determine which characteristic
should be used as the currency-bearing consolidation unit.
If you use two characteristics with the role consolidation unit, you also can de ne a DataStore object (DS object) for custom
attributes of combinations of consolidation units in the data model.
Assets/Liabilities
On this tab page you make various settings concerning capitalization and valuation allowances, elimination of interunit
pro t/loss in transferred assets, and elimination of interunit pro t/loss in transferred inventory:
4/20/2019
For detailed information, see F1 Help for the various elds under Assets/Liabilities.
Goodwill
In the Goodwill area, you can specify for characteristics with role Goodwill-Creating Investee Unit those elds in the Goodwill
data stream to which the system is to persistently store the investee unit for the goodwill-creating activity. For more
information, see Separation of Goodwill from Investment.
Data Streams
The data streams identify the location for storing the transaction data in Consolidation. Data can be read from, and written to,
all data streams.
On the Data Streams tab page, you specify a data target for each data stream you want to use. You can have the system
generate the data targets, as well.
As an option, for each data stream you can also assign or allow the system to generate a virtual InfoProvider for reporting
purposes. For the data stream Totals Records, in particular, you can make further settings for reporting based on a
MultiProvider.
For more information, see De nition of Data Streams.
Data Stream Fields
Here you choose additional subassignments and other custom elds (without roles) for the data streams of additional nancial
data and documents. The assignments depend on the data stream:
Investment, equity: You can select optional elds. Available are all elds with the role subassignment, plus those elds
that are contained in the additionally connected InfoObject catalogs. The system adds these elds to the respectively
assigned DS objects when the data streams are generated.
Goodwill: You can select Goodwill in Local Currency on the Settings tab page of the Customizing screen for a
consolidation area that belongs to the data basis. After you set this indicator and generate the goodwill DS object, the
system automatically adds further elds to the DS object that are required for the Goodwill in Local Currency function.
Furthermore, here you can choose additional elds for the DS objects for documents, noncurrent assets, and assets/liabilities,
and for other objects. You choose these elds in addition to the elds that are provided in the system and displayed here.
Attributes
The system lists the eld attributes that exist in the data basis, sorted by elds. You can de ne whether each individual
attribute is to be made available as a selection attribute for single selections. For elds with multiple attributes you can de ne
the sequence of those attributes using the arrow keys. The following factors affect whether you can modify the setting of the
Selection Attribute indicator, or whether the system uses a certain presetting.
Factors That Affect Settings of Selection Attributes
Cause Effect Example
The attribute is a characteristic created in a) The attribute that references another The partner pro t center eld is based on
the BI system with reference to another characteristic is set as a selection attribute: the reference characteristic pro t center. If
characteristic. The attribute referencing the derived you use pro t center as a selection
characteristic can be used as a selection attribute, this also enables the use of
attribute. partner pro t center as a selection
attribute.
b) The attribute that references another
characteristic is not set as a selection
attribute: The attribute referencing the
4/20/2019
derived characteristic cannot be used as a
selection attribute.
The attribute is a characteristic that is used The attribute that references the derived
in the InfoCube as a navigation attribute. characteristic is preset as a selection
attribute. This setting cannot be changed.
Mapping
Here, the system lists those BI attributes of the characteristics with the roles consolidation unit, item, transaction type,
document type, and restatement (and any combinations of consolidation units) that you can map to a local attribute in the
consolidation system. (In general, these are the BI attributes that you have not de ned as selection attributes on the Attributes
tab page.) The system lists all local attributes that are technically feasible. You need to decide which links are suitable from an
accounting standpoint.
If a local attribute is dependent on the consolidation area, you need to specify (in the CA column) a consolidation area in which
the mapping should take place.
If a local attribute is dependent on the special version, you need to specify (in the Special Version column) for the prede ned
special version type a special version in which the mapping should take place.
For more information, see Linking of Local Attributes to BI Attributes.
Authorization Check and Validity Check
On this tab page, you can de ne how the system should access the characteristics of your data basis and how to process the
entry of values.
Authorization Check for Characteristic Values: Select this indicator to automatically check the authorization for the
characteristic at the level of characteristic values. For example, this lets you specify that a user is allowed to display or
enter data for a speci c consolidation unit only. If you do not select this indicator, you can grant or deny authorizations
only for all values of the characteristic. You can set the authorization check at the characteristic level for all
characteristics contained in the data basis. You use SAP authorization management to de ne the actual values to be
checked during an access (see Users and Roles). For more information, see Authorizations for Master Data.
Validity Check: You use this to de ne whether the system is to check the validity of the values that are entered for a
given characteristic. You can specify that the check is to be dependent on version, time, or combinations of version and
time. When you request a validity check, the system only displays and evaluates the data records of the data basis for a
given characteristic if they match the permanent parameters of the Consolidation Workbench. For more information, see
Validity of Master Data.
Column Headings
This is where you de ne the texts for the elds in the data basis to be used as column headings in logs, audit trails, and output
lists. You can use this function to modify the names of individual elds to better suit the terminology used in your organization
or to adjust the lengths of the names.
You have a great degree of freedom in your choice of names. In particular, there are no length restrictions for the names of
elds. However, it is not bene cial for the name of a eld to exceed the output length of its values by more than a few
characters. The output length is also displayed to help you determine the name length.
If you make no entries here, the system uses the eld names delivered by SAP.
Special Considerations for Alternating Logon Languages
4/20/2019
You can run SEM-BCS with different logon languages. Note that you need to translate the column headings into all languages
you use. Otherwise, the system will use internal logic to display the column headings in a language that comes as close as
possible to the logon language. However, the logic applied is not always satisfactory.
Depending on the functional area and utilization, the system decides whether to use the column heading you have de ned or to
directly access the name of the respective InfoObject for the eld name. In multilingual environments, you therefore need to
translate not only the column headings, but also the names of the InfoObjects that those headings are based on. To do this, you
need to use the general translation function of the BI system in which the InfoObjects are located – not the translation function
of SEM-BCS. You can access the translation function in the SAP menu at Tools ABAP Workbench Extras Translation Short and
Long Texts . For more information about translating system texts, see Translation Tools for Translators.
Source Data Basis

De nition
De nes all source data streams for an RFC destination in a central place.
Use
You can assign one or more source data bases to a data basis in order to use this as the source of data (read access only) for
methods of the type Load from Data Stream or Flexible Upload .
Structure
The Customizing settings of a source data basis is a subset of the customizing settings of a data basis : You de ne data streams
and make settings on the attributes, authorization check, and column headings for the elds of the data streams.
Data Streams
The RFC Destination in SAP NetWeaver Business Intelligence (BI) speci es from which system the source data is to be read. If
you do not specify an RFC destination, the system uses the BI system that resides in the SEM system.
You can specify one InfoObject Catalog for characteristics and key gures. You can use the elds of this InfoObject catalog in a
method of the type Flexible Upload as a (external) eld catalog. By de ning suitable mapping rules of the exible upload, you
can map the elds on the eld structure of the data basis to which you assigned the source data basis. In this way you can also
include data from les with different eld structures in the data basis.
You can also assign one or more InfoProviders . You can use these in a method of the type Load from Data Stream as source
data streams.
Example
You have an InfoCube in system A, which contains nancial planning data. You want to use this planning data in system B for
consolidation. To do this, proceed as follows:
1. Create a source data basis. Enter system A as the RFC Destination . Then under InfoProvider enter your InfoCube with
the planning data.
2. Assign this new source data basis to your data basis.
3. Create a Load from Data Stream method and select your system A as the RFC Destination and your InfoCube with the
planning data as the InfoProvider . If the structure of the planning data does not match the corresponding elds of your
data model, de ne suitable mapping rules.
4/20/2019
4. Execute the new method.
See also:
Data Basis
Role (Characteristic Role and Key Figure

Role)
De nition
The semantics of characteristics or key gures that are used as the basis for consolidation functions.
The characteristics and key gures you use in consolidation have a speci c role. For example, consolidation has a characteristic
with the role Item.
Note
For the sake of simplicity, we often refer to a “characteristic with the role Item ” simply as an “Item”.
Structure
On the Data Model tab page, you assign exactly one role to each and every characteristic and key gure that you use in the data
basis. Since these assignments are data basis speci c, you can assign different roles to the same characteristics and key
gures when editing a different data basis. Thus, the relationship between a characteristic or key gure and its role is not
unique for the entire system.
 Example
The characteristic Company has the role Consolidation Unit in data basis DATA_BASIS_1. At the same time, the same
characteristic has the role Partner Unit in data basis DATA_BASIS_2.
Note
You can only assign the role version to those characteristics that are not linked with a higher-level characteristic.
The following roles are available for characteristics and key gures in consolidation totals records:
Roles in Consolidation
Role Number of Fields with this Value Is Never Initialized (the Explanation
Role in the Data Basis characteristic always has a
value in the transaction data)
Version between 1 and n X See detailed documentation on

the version
Group currency key 1 X You can insert the group

currency key as a variable into
the data model.
Local currency key 1 X Even if you copy the data to the

group currency, the local
4/20/2019
currency key needs to be in the
data basis (for example, as an
unused characteristic in the
data model of the data basis).
Currency-bearing consolidation 1 X See detailed documentation on

unit the consolidation unit
Consolidation unit 1 or 2 X
Consolidation group 1 or 2
Item 1 X See detailed documentation on

the item
Subassignment between 0 and n See detailed documentation on

the subassignment
Partner unit 1 or 2
Investor unit 0, 1, or 2
Investee unit 0, 1, or 2
Transaction type 0 or 1
Acquisition year/period 0 or 1
Transaction currency key 0 or 1 X
Unit of measure 0 or 1
Document type 1
Posting level 1
Translation indicator 0 or 1
Clearing characteristic (for between 0 and n Allocations require the

allocations) characteristic with the role
clearing characteristic. It
contains either the sender
object or the receiver object.
Each clearing characteristic
needs a corresponding
characteristic that is cleared.
Fiscal year 1 X
Period 1 (X)
Value in group currency 1
Value in local currency 0 or 1
Value in transaction currency 0 or 1
Quantity 0 or 1
Fixed in consolidation area between 1 and n X You must assign at least the
characteristic scal year
variant to this role. You must
then de ne a xed value in the
consolidation area for each
characteristic that uses this
role.
Product group 0 or 1 Required for Elimination of
4/20/2019
Interunit Pro t/Loss in
Transferred Inventory
Field type, transaction type 0 or 1 Higher-level characteristic of

the transaction type (if this is
compounded)
Restatement 0 or 1 See Creating Restatement

Characteristics
Data Model: Assets/Liabilities

De nition
Entity in the consolidation data model.
Use
The following functions are available for the Assets/Liabilities entity:
You can maintain master data speci c to Assets/Liabilities (by means of manual data entry of master data, or automatic
data collection).
You can enter additional nancial data for Assets/Liabilities (by means of manual data entry or automatic data
collection).
You can extend the document database (journal entries) by the Assets/Liabilities entity.
You can have the Assets/Liabilities entity be posted when documents are posted manually.
The Assets/Liabilities entity is used in the following consolidation functions:
Capitalization and Valuation Allowances
This function creates automatic posting documents that are managed by the master data and the additional nancial
data. This comprises the following posting documents:
Capitalization of new assets/liabilities with an option to record deferred taxes in the balance sheet
Valuation allowances (writeups and depreciation) of assets/liabilities
Retirements of assets/liabilities
The entries can be posted in local currency, group currency, or both.
Fair value surpluses and fair value de cits (also known as hidden reserves and hidden contingencies) is a typical
application for Assets/Liabilities.
For more information, see Capitalization and Valuation Allowances .
Elimination of Interunit Pro t/Loss in Transferred Assets
For more information, see Elimination of Interunit Pro t/Loss in Transferred Assets .
Structure
You de ne the InfoObjects for Assets/Liabilites that you require for the aforementioned functions in SAP NetWeaver Business
Intelligence (BI) or you use the Business Content delivered by SAP.
4/20/2019
In the process view of the Consolidation Workbench, you select the InfoObjects to be used by consolidation by choosing Data
Model Data Basis Data Modeltab page Assets/Liabilities pushbutton.
The following table shows:
The InfoObjects that are available for Assets/Liabilities,
The consolidation functions for which these InfoObjects are available,
The data streams in which the InfoObjects are contained, and
How the corresponding elds must be de ned in BI
InfoObjects InfoObjects Required for InfoObject is included Field De nition in BI

Function automatically in following
(for more information, see
data streams
the eld help)
Asset/Liability-managing Documents Reference characteristic:

Elimination of Interunit
Consolidation Unit , for consolidation unit;
Pro t/Loss in
example:
Transferred Inventory InfoObjects ≠ InfoObjects for
Company and/or consolidation unit, partner
unit, investee unit, and
Pro t Center Elimination of Interunit
investor unit
Pro t/Loss in
Transferred Assets
Elimination of interunit Elimination of Interunit Typical cases

Transferred
pro t/loss in transferred Pro t/Loss in Transferred
assets:with Differentiation of
assets Assets
Noncurrent Asset subassets:
Noncurrent asset InfoObject Noncurrent Asset is
compounded with
Acquired asset Transferred assets
Asset Main Number ;
(consolidated):with
Asset Main Number
Retired InfoObjects
is compounded with
asset(optional; if the Noncurrent Asset ,
Currency-Bearing
retired asset is initial, Acquired Asset
Consolidation Unit
the Noncurrent Asset
InfoObject is Asset transfer with No differentiation of
generated in the Asset following subassets:
Transfer data stream InfoObjects:if Noncurrent Asset is
necessary, compounded with
Noncurrent asset -
Noncurrent Asset , Currency-Bearing
document
Acquired Asset , if Consolidation Unit
necessary, Retired only
Asset
Documentswith
Noncurrent Asset -
Document InfoObject
Capitalization and Valuation Capitalization and Valuation Analog to InfoObjects for

Assets/Liabilities and
Allowances Allowances Elimination of Interunit
Documents Pro t/Loss in Transferred
Assets/Liabilities (for
Assets
example, fair value
adjustments)
4/20/2019
InfoObjects InfoObjects Required for InfoObject is included Field De nition in BI

Function automatically in following
(for more information, see
data streams
the eld help)
Elimination of Interunit Elimination of Interunit Documents (together with

Pro t/Loss in Transferred Pro t/Loss in Transferred Product Group InfoObject)
Inventory Inventory
Inventory item
Note
To display the technical names of the InfoObjects in the dropdown list boxes, proceed as follows: Choose Adjustment
of Local Layout (Alt+F12) -> Options… -> Expert tab page. Set the indicator Display Key in All Dropdown Boxes .
Depending on which function you use, you must take the following into account:
Elimination of Interunit Pro t/Loss in Transferred Assets
For this function, you must enter at least InfoObjects for the Noncurrent Asset and the Acquired Asset . Samples for the
Noncurrent Asset from Business Content are the InfoObjects 0BCS_ASTSN and 0BCS_ASSET. Samples for the Acquired Asset
are the InfoObjects 0BCS_AASTSN and 0BCS_AASSET.
You can de ne the InfoObject for the Retired Noncurrent Asset if you desire a speci c text for the Retired Asset eld during
manual entry of asset transfers. If you do not specify an InfoObject, the system uses the Noncurrent Asset InfoObject.
You can specify InfoObjects for the Noncurrent Asset (Document) and the Asset/Liability-managing Consolidation Unit if you
intend to have the Elimination of Interunit Pro t/Loss in Transferred Assets function post one document per consolidation
group, asset, and activity in the elimination of IU pro ts and losses. If you do not specify these InfoObjects, the function posts
one document per consolidation group. These documents can contain many journal entries and can be difficult to analyze;
therefore, we recommend you specify these InfoObjects. Samples for the Noncurrent Asset (Document) are the InfoObjects
0BCS_MASTSN and 0BCS_MASSET. Samples for the Assets/Liability-managing Consolidation Unit are the InfoObjects
0BCS_ALMCOM (for matrix organizations) or 0BCS_ALMPC (for non-matrix organizations) and 0BCS_ALMU.
Recommendation
If the data model has two characteristics for the consolidation unit, we recommend you de ne the characteristic for the non-
currency-bearing consolidation unit as an attribute of the noncurrent asset characteristic.
Capitalization and Valuation Allowances
For this function, you must specify the InfoObject for the Assets/Liabilities . Samples for the Assets/Liabilities are the
InfoObjects 0BCS_FVDSN and 0BCS_FVD.
Recommendation
If the data model has two characteristics for the consolidation unit, we recommend you de ne the characteristic for the non-
currency-bearing consolidation unit as an attribute of the assets/liabilities characteristic.
Elimination of Interunit Pro t/Loss in Transferred Inventory
For this function, you can specify the InfoObject for the Inventory Item . In this case, documents are created for each inventory
item. A sample for the Inventory Item is the InfoObject 0BCS_INITEM.
4/20/2019
Similarly, you can specify InfoObjects for the asset/liability-managing consolidation unit . In this case, documents are created
for each inventory-managing consolidation unit. Samples for the Assets/Liability-managing Consolidation Unit are the
InfoObjects 0BCS_ALMCOM or 0BCS_ALMPC and 0BCS_ALMU.
See also the eld help in the Consolidation Workbench.
Linking of Local Attributes to BW Attributes

Use
You use this function to link local attributes in the consolidation system (SEM-BCS) with attributes in SAP NetWeaver SAP
NetWeaver Business Warehouse (BW).
This lets you map local attributes to the BW system for use there in reporting.
Integration
The system maps the local attributes to the linked attributes in the BW system.
Conversely, you can map the linked BW attributes in the consolidation system by counter-synchronizing the attributes from the
BW system.
In characteristic maintenance, the consolidation system shows the BW attributes of a characteristic on the Other Attributes tab
page. If an existing BW attribute is linked to a local attribute, the system does not show it on this tab page.
Prerequisites
The BW attribute in question needs to have the same technical properties as the local attribute you want to link.
Note
There is one exception: You can link the BW attribute 0SIGN_REV (a key gure with data type INT4) to the local attribute
SIGN (a characteristic with data type CHAR). See also the section "Available Local Attributes".
The local attribute is not linked to another BW attribute, and vice versa.
Features
You can create links for a selection of attributes that belong to characteristics with the following roles in the consolidation
system:
Item
Transaction type
Document type
Consolidation unit
Restatement
You can also create links for a selection of attributes that belong to combinations of consolidation units.
4/20/2019
In the process view of the consolidation Workbench, you can view a list of the BW attributes to which you can link a local
attribute by choosing Data Model Data Basis , and choosing the Mapping tab page. The system displays only those BW
attributes that are not de ned as selection attributes on the Attributes tab page.
For each BW attribute, the system lists all local attributes to which it can be technically linked. You need to decide which links
are suitable from an accounting standpoint.
If the local attribute is dependent on the consolidation area, you also need to specify the consolidation area in which the link is
to apply.
If the local attribute is dependent on a special version, you also need to specify the special version (that has the prede ned
type) in which the link is to apply.
Available Local Attributes
The following local attributes in the consolidation system can be linked to SAP BW attributes:
Attributes of Characteristics with the Role “Item”
Local Attribute Required Properties of the BW Attribute
Dr/Cr sign (SIGN) InfoObject type Characteristic
Data type CHAR - character string
Length 1
Conversion routine -
Dr/Cr sign (SIGN) InfoObject type Key gure
Type Integer
Data type INT4 - 4-byte integer, whole number with

+/- sign
Item type (ITTYPE) InfoObject type Characteristic
Data type NUMC - character string with numerals only
Length 1
Attributes of Characteristics with the Role “Transaction Type”
Dr/Cr sign (SIGN) InfoObject type Characteristic
Length 1
Dr/Cr sign (SIGN) InfoObject type Key gure
Type Integer
Data type INT4 - 4-byte integer, whole number with

+/- sign
Attributes of Characteristics with the Role “Document Type”

4/20/2019
Business application (DOCUSAGE) InfoObject type Characteristic
Length 1
Deferred taxes credit (DTAXCFLG) InfoObject type Characteristic
Length 1
Deferred taxes debit (DTAXDFLG) InfoObject type Characteristic
Length 1
Tax rate for deferred taxes (DTAXRATE) InfoObject type Key gure
Type Number
Data type FLTP - oating point number with 8-byte

precision
Time dependent Yes
Posting level (PLEVEL) InfoObject type Characteristic
Reference characteristic 0CS_PLEVEL
Source of deferred taxes (DTAXSOURCE) InfoObject type Characteristic
Length 1
Attributes of Characteristics with the Role “Consolidation Unit”
Local currency (CURKEY_LC) InfoObject type Characteristic
Reference characteristic 0CURRENCY
Time dependent Yes
Tax rate for deferred taxes (DTAXRATE) InfoObject type Key gure
Type Number
Data type FLTP - oating point number with 8-byte

precision
Time dependent Yes
Period of rst data entry InfoObject type Characteristic

(FISCPERIOD_DE1ST)
4/20/2019
Length 3
Year of rst data entry (FISCYEAR_DE1ST) InfoObject type Characteristic
Length 4
Conversion routine GJAHR
Attribute of Characteristic with the Role “Restatement”
Restatement period InfoObject type Characteristic
Length 7
Conversion routine PERI7
Activities
Follow these steps to link a local attribute in the consolidation system to an SAP BW attribute or to modify an existing link:
1. If the BW attribute does not yet exist, create an InfoObject with the appropriate properties in the Data Warehousing
Workbench.
2. In the process view of the consolidation workbench, choose Data Model Data Basis on the Mapping tab page and
assign a local attribute to the BW attribute. To do so, click on the entry for the BW attribute in the Local Attribute column
and choose the local attribute from the selection list.
If the local attribute is dependent on the consolidation area, the system adds to the CA column a consolidation area in
which the link should apply. You can change the proposed consolidation area.
If the local attribute is dependent on the special version, the system adds a special version in which the link should apply
to the Special Version column. You can change the proposed special version to the prede ned special version type.
Once you save the link, the system maps the local attribute in the BW system. The BW attribute no longer appears on the Other
Attributes tab page in characteristic maintenance in the consolidation workbench.
Example
Task at Hand
In the consolidation system, the attribute Year of First Consolidation is dependent on the special version. For reporting
purposes, you want to map this local attribute in the BW system for the special versions 100 and 200 only.
Solution
You launch the Data Warehousing Workbench and create two InfoObjects (for example, YEAR100 and YEAR200) with the
following properties:
4/20/2019
Required Properties of the BW Attributes
InfoObject Type Characteristic
Length 4
Conversion routine GJAHR
In the consolidation workbench, you link the BW attribute Year100 to the local attribute Year of First Consolidation in special
version 100. You link the BW attribute Year200 to the local attribute Year of First Consolidation in special version 200.
De nition of Data Streams

Use
You use this function to de ne data streams for totals records, documents, and the additional nancial data you want to use in
the consolidation system.
Data can be read from all assigned data streams, and data can be written to all data streams. The following types of data
streams are available:
Data Stream Required/Optional Application
Totals records Required This data stream primarily de nes the data
basis. It de nes the characteristics and key
gures available in the data model.
Documents Optional For the posting documents that are

generated in consolidation
Inventory data Optional Elimination of interunit pro t/loss in

transferred inventory
Supplier data Optional Elimination of interunit pro t/loss in

Supplier share Optional Elimination of interunit pro t/loss in

Assets/liabilities Optional Capitalization and valuation allowances
Noncurrent assets Optional Elimination of interunit pro t/loss in

transferred assets
Noncurrent assets (consolidated) Optional Elimination of interunit pro t/loss in

transferred assets
Asset transfers Optional Elimination of interunit pro t/loss in

transferred assets
Third-party investment Optional Consolidation of investments (business

combinations)
Investments Optional Consolidation of investments
Equity Optional Consolidation of investments
Equity holdings adjustments Optional Consolidation of investments
4/20/2019
Data Stream Required/Optional Application
Goodwill Optional Consolidation of investments
Activity numbers Optional Consolidation of investments
Sequence of activities Optional Consolidation of investments
Activity sorting Optional Consolidation of investments
Integration
The data streams are assigned to the data basis.
Prerequisites
In the data basis, you have assigned the InfoCube for totals records, and (if applicable) the InfoObject catalogs for
characteristics and key gures. (See the "Field Catalog" section in Data Basis.)
Features
For the data streams you want to use, you make the following settings in Customizing for the data basis on the Data Streams
tab page:
For each data stream type you want to use (except for totals records), you need to assign or generate a data target.
As an option, for each data stream you can also assign or generate a virtual InfoProvider for reporting purposes.
As an option, for the data stream Totals Records you can use a MultiProvider to make further settings for reporting.
Assignment of Data Targets
You either assign the data streams to existing data targets, or let the system generate the data targets. (See the section
"Generate Data Targets and Virtual InfoProviders".)
The system uses the following InfoProviders as data targets for the data streams:
InfoCube for totals records
This only adds new data records and updates key gures.
ODS objects for all other data streams (documents, additional nancial data)
This also updates characteristics (which is needed for activities such as posting reversal entries).
You can generate database lists for InfoCubes and ODS objects in the consolidation system. To do this, navigate to the process
view of the consolidation workbench and choose one of the functions under Analysis List Data .
Assignment of Virtual InfoProviders for Reporting
For business reporting, you can also assign or generate a virtual InfoProvider for each type of data stream. (See the section
"Generate Data Targets and Virtual InfoProviders".) This does not apply to the data streams for activity numbers and the
sequence of activities.
For more information, see Data Staging in the Virtual InfoProvider.
Assignments for Reporting with MultiProviders
4/20/2019
For the data stream Totals Records, you can make further settings for reporting based on a MultiProvider.
The consolidation system supports the following scenarios for MultiProvider reporting, in particular:
MultiProvider Reporting with Delta Load
The MultiProvider reads the data from an additional InfoCube (called the reporting InfoCube) and a virtual InfoProvider.
The reporting InfoCube retrieves its data over data mart transfer from the transactional InfoCube for totals records.
Data preparation required for the business report occurs in a Business Add-In (BAdI). The virtual InfoProvider merely
returns the data that has not yet been recorded in the reporting InfoCube since the last data mart transfer.
You can generate the complete delta load scenario on the Data Streams tab page.
For more information, see MultiProvider Reporting in the Delta Load Scenario.
MultiProvider Reporting with an Additional Virtual InfoProvider
The MultiProvider reads the data for closed periods from an additional InfoCube (called the reporting InfoCube) and the
data for open periods from an additional virtual InfoProvider. The reporting InfoCube retrieves its data over data mart
transfer from the virtual InfoProvider. Both the virtual InfoProvider and the additional virtual InfoProvider retrieve their
data for reporting from the transactional InfoCube for totals records, and prepare the data for reporting.
You can generate both the virtual InfoProvider and the additional virtual InfoProvider on the Data Streams tab page.
For more information, see MultiProvider Reporting with an Additional Virtual InfoProvider.
Activities
Generate Data Targets and Virtual InfoProviders
To automatically generate the data targets and virtual InfoProviders, perform the following steps (see also the example below):
1. In the process view of the consolidation workbench, go to Data Model Data Basis , choose your data basis, and go to the
Data Streams tab page.
The InfoCube for totals records appears in the rst row. This setting results from the de nition on the Field Catalog tab
page and is shown here merely for informational purposes.
2. Allow the system to automatically generate the remaining rows for the documents and additional nancial data. To
generate the data target for a data stream, do the following:
a. Either enter the name in the row assigned to the data stream in the Data Target column, or leave the name eld
blank.
b. Select the Generated indicator to the left of the Data Target column.
c. Generation starts when you save the data basis.
You can generate multiple data targets and virtual InfoProviders at the same time.
The system uses the name you speci ed when it generates the ODS objects for the selected data targets. If you left the
name blank, the system also generates the name of the ODS object.
3. You should also allow the system to generate the virtual InfoProviders for reporting (including those for the totals
records). To generate the virtual InfoProvider for a data stream, do the following:
a. Either enter the name in the Virtual InfoProvider column assigned to the data stream, or leave the name eld
blank.
b. Select the Generated indicator to the left of the Virtual InfoProvider column.
4/20/2019
c. Generation starts when you save the data basis.
You can generate multiple data targets and virtual InfoProviders at the same time.
The system uses the name you speci ed when it generates the virtual InfoProviders for the selected virtual
InfoProviders. If you left the name blank, the system also generates the name of the virtual InfoProvider.
Note
You also can use the Generate Data Basis function to start the generation. As compared to the procedure described
earlier, this function has this special feature:
This function allows you to generate the data basis even if you have no change authorization or you are currently in
display mode. This is often the case in live systems. However, it may be necessary to change Customizing settings in
feeder systems. These settings are then transported to the live system. If this merely transports the changes in the
consolidation system (SEM–BCS), but not the referenced objects in SAP NetWeaver Business Intelligence (BI), you
need to synchronize the data model of the consolidation system with BI afterwards. To do this, you use this function.
Once the ODS objects and virtual InfoProviders have been successfully generated, you can use the data streams for the
consolidation functions and the virtual InfoProviders for reporting. You can assign or generate additional data targets and
virtual InfoProviders later on (on the Data Streams tab page).
Example
The gure below depicts a section of the Data Streams tab page. The sequence numbers refer to the steps outlined in the
"Generate Data Targets and Virtual InfoProviders" section.
Analysis and Repair of Data Streams

Use
You can analyze the data streams of a Data Basis with this function and correct any data inconsistencies if necessary. Data
inconsistencies can occur, for example, if you make subsequent changes to Customizing settings – such as, inadvertently
resetting number ranges for documents. In this example, the system would overwrite documents without warning.
4/20/2019
We recommend that you use this function after tests and before the system is used live to identify and remove any
inconsistencies as early as possible.
Prerequisites
You have authorization for authorization object R_UC_RECON ( eld CONS_AREA in connection with ACTVT ).
You have activated the Tools view in the Consolidation Workbench.
Features
The selection screen contains selection parameters for consolidation units, versions, time, and currency. In addition, you can use
other characteristics to restrict the data selection within a consolidation area.
Which other characteristics and data streams are offered for selection depends on the elds contained in the data basis and
the data modeling of the Consolidation Area . The system determines the relevant Customizing settings at runtime and
dynamically forms the screen.
Note that the screen can contain an unusually large amount of elds due to the very extensive data model. This means you
need to scroll down the screen to see all elements.
In the Technical Settings group box you de ne what exactly the function should do when you execute it:
The different subfunctions are used partly for analysis and partly to repair any inconsistencies of the data streams analyzed.
Whereas the analysis functions have read-only access to the data basis, the repair functions also have write access. We
recommend that you use the analysis functions rst and depending on the results of the check implement the repair functions.
Display Records from…/Delete Records from... : You use these options to specify whether the system displays or deletes data
records from the data basis. For both options, you also specify which data streams shown on the screen should be accessed by
the function. Which data streams are shown depends on which data basis is assigned to the current consolidation area.
Compare Journal Entries with Totals Records : You can compare the aggregated totals from journal entries (data stream
documents) and totals records with each other to check whether the aggregated journal entries and the relevant totals records
match. The system checks whether:
Matching documents exist for the totals records.
Matching totals records exist for all documents.
The key gure values of the totals records are equal to the totals aggregated from the documents.
If you post documents in local currency only, differences in group currency are reported for information only and not as errors.
These differences in group currency can be the result of a subsequent currency translation: In this case the document database
contains documents for which no value exists for the key gure for group currency (when the group and local currency is
different).
4/20/2019
The key gures for group currency also do not contain any values in the totals records before currency translation. The key
gures for group currency are written to the totals database after currency translation, which only operates on the totals. Since
currency translation does not generate any documents, there are differences between the documents and totals records for
the key gure group currency . This is not an error.
Amounts in group currency are not included in the comparison in the following cases:
Document type is translated to group currency or document type posts in group currency and additionally in local or transaction
currency
Document type does not post in group currency, but in local or transaction currency and is not translated to group currency
At posting level 00 only totals records are managed and no journal entries. So a comparison is not useful for this posting level. If
you still include the posting level in the comparison, the system warns you with a message.
Create Totals Records from Journal Entries : There is an inconsistency if differences have been established during the
comparison of journal entries and totals records, which are not the result of a subsequently executed method, for example,
currency translation with rounding. Possible causes are incorrect or subsequently changed Customizing settings (for example, a
change to the Customizing of rounding).
At posting level 00 and in period 0, only totals records are managed and no journal entries. Use this option only if you have
excluded posting level 00 and period 0 from the selection. Otherwise you could lose your reported nancial data.
In principle, methods that only work with totals cannot reverse a task that has already been executed. Executing this method
again does not correct the totals. Therefore, you must rebuild the totals records from the journal entries to create a consistent
dataset.
Check Consistency of Document Numbers : You check the documents for the current selection. The system checks whether:
The documents contain sequential document line items.
The key gures in the documents have a zero balance.
The document contains more than one row (exception: statistical documents).
All characteristics that are normally constant for each document, are unchanged (characteristics xed in the consolidation
area, version characteristics, posting level, document type).
An appropriate offsetting line with (inverted) key gures exists for every line of a reversal document or an inverted document.
4/20/2019
This check delivers reliable results only if you do not restrict the selection to speci c nancial statement items. Specifying
certain items can cause document data to be read incompletely. This could result in error messages even if the document
numbers are consistent.
Test Run : If you set this indicator, the system performs the analysis or repair run without saving any changes in the data basis.
This provides you with an overview of the consequences of a repair and you can then decide whether you want to execute the
function in update mode.
Activities
Go to the Tools view of the workbench.
In the navigation area, choose Transaction Data → Analyze and Repair Data Streams
Make the appropriate settings in the detailed area of the screen and choose Execute
Depending on the settings you made, the system analyzes or repairs the selected elements.
Check the results in the log. If the system performed an analysis and found inconsistencies, execute the function again with the
necessary repair options.
Consolidation Area
De nition
A subset of the characteristics and key gures available in the Data Basis .
A consolidation area is characterized by its methods , tasks and breakdown categories .
Use
You can use consolidation areas to:
Consolidate the nancial statements of subsidiaries according to generally accepted accounting principles (for example,
the rst consolidation area)
Consolidate data for management purposes, for example based on pro t centers (for example, the second consolidation
area)
See also the example below.
Structure
Relationship with the Data Basis
In the consolidation workbench, you create one or more consolidation areas for a Data Basis . When doing this, you select a
subset of the characteristics and key gures available in the data basis.
You start generation of the required objects in the data basis with the Generate Consolidation Area function on the Fields
tab page. This function has the following special considerations:
You can generate the consolidation area even if you have no change authorization or are currently in display mode. This is often
the case in live systems. However, it may be necessary to change Customizing settings in feeder systems. These settings are
4/20/2019
then transported to the live system. If only the changes in the Consolidation System (SEM-BCS) are transported, and not the
referenced objects in the SAP NetWeaver Business Intelligence ( BI) system, you need to synchronize the data model of SEM-
BCS and BI afterwards. To do this, you use this function.
Permanent Parameters
You can declare characteristics as Permanent Parameters :
Only the version and the time characteristics – scal year variant, scal year and period – must be used as permanent
parameters.
You can also de ne the consolidation unit and the consolidation group as permanent parameters.
If you use a restatement characteristic, then it automatically counts as a permanent parameter.
Characteristics that are not status relevant cannot be used as permanent parameters (for example, nancial statement
item, subassignment, transaction type).
For each characteristic used as a permanent parameter, you can de ne whether the consolidation system displays it in the
header of all consolidation screens.
Characteristic Values for Permanent Parameters
You de ne a single value for each characteristic of the permanent parameters that requires a unique value. By doing so, the
characteristic cannot be modi ed as a permanent parameter.
The following exceptions apply to the roles nancial statement item and dimension :
If you de ne the characteristic with the role nancial statement item as being dependent on the consolidation chart of
accounts, you must de ne the consolidation chart of accounts in the consolidation area with a unique single value.
If you de ne the characteristic with the role consolidation unit as being dependent on the dimension, you must de ne
the dimension in the consolidation area with a unique single value.
Settings
You make numerous settings on this tab page that affect the system behavior and the functions available within the
consolidation area. This includes the Status Management in the Consolidation Monitor , activating maximum sets for
breakdown categories , the availability of speci c consolidation functions, or the output length for value elds in logs and lists.
Example
You want to perform both of the following types of consolidation:
According to GAAP (statutory consolidation)
For internal purposes (management consolidation)
To do this, you create two consolidation areas, each with its own data model, both of which are based on the same InfoCube. For
both consolidation areas you use the same data stream for the totals records; both consolidation areas also use the following
characteristics:
Dimension
Consolidation chart of accounts
Version
4/20/2019
Fiscal year
Period
Consolidation group
Consolidation unit
Partner unit
Item
Characteristics and key gures for the local currency and group currency
You use the characteristic dimension to segregate the consolidation areas in the same data stream. This is why you specify a
condition for the dimension in the form of a single value when de ning each consolidation area.
Now, the consolidation system shows the consolidation area (not the dimension) in the header of every screen.
You fully segregate the two consolidation areas as follows:
Consolidation Area Dimension Additional Characteristics
Statutory Consolidation Single value LC (legal consolidation)

Transaction Type
Year of Acquisition
Period of Acquisition
Management Consolidation Single value MC (management

Product Group
consolidation)
Customer Group
Sales Region
Permanent Parameters
De nition
Parameters that are de nitive for the subsequent activities for the user in the consolidation system.
Permanent parameters include the version, the scal year, and the period. You can also de ne other permanent parameters.
The permanent parameters are valid for Customizing in the consolidation workbench and for processing in the consolidation
monitor. However, temporary value changes are only valid in the context of the environment in which you make the change.
Structure
De ning Characteristics as Permanent Parameters
In Customizing for the Consolidation Area , you de ne which characteristics act as permanent parameters:
The version, scal year and period are required permanent parameters.
You can de ne additional permanent parameters, for example the consolidation unit and consolidation group.
If you use a restatement characteristic, then it automatically counts as a permanent parameter.
4/20/2019
You can choose whether each permanent parameter is displayed in the screen header.
On the Settings tab page, you can de ne whether the consolidation area is displayed in the permanent parameters.
Characteristics that are not status relevant cannot be used as permanent parameters (for example, nancial statement item
and transaction type).
Use of Permanent and Temporary Parameters
Choose Environment Parameters to de ne the values for the parameters. Make the appropriate settings in the dialog box.
After you have entered the parameter values, you have two options:
To apply the values as temporary parameters for the current session, choose Con rm .
Note
As soon as you exit the session and start a new session, the system resets the parameter values to the values that
are saved permanently.
If you want to make a temporary change only, you can change the relevant values directly in the appropriate elds in
the screen header without having to open the dialog box. The prerequisite for this is that you have activated the
display of parameters in the header.
To apply the values as permanent parameters for all following sessions, choose Save Permanent Parameters .
Authorizations for Permanent Parameters

Use
You can activate an authorization check for permanent parameters for speci c users or roles. When a user sets or changes the
parameters, the system checks whether this user is authorized to execute at least one task with the parameters set. This
function enables you to prevent users from setting parameters (particularly in the consolidation monitor) that they cannot use
to execute tasks.
Prerequisites
Features
You can specify a list of user names (logon names) or user roles (that you created in transaction PFCG, for example). When a
user with one of the user names or roles listed changes parameters in his or her user pro le, the system runs an authorization
check. The system checks whether the user in question is authorized to execute at least one task with the parameters speci ed.
Only if this is the case does the system permit the parameters to be set.
Note
If the system permits parameters to be set as a result of the authorization check, this does not necessarily mean that tasks
can actually be executed. For example, this may be the case if a user is authorized to execute a task, but the period has
already closed.
The system checks the authorizations for all tasks in the task hierarchy for the following parameters:
4/20/2019
Consolidation Area
Version Combination
Posting Period
Fiscal Year
The system checks whether the user is authorized to execute the task in update mode or in test mode. Authorization to execute
the task in test mode is sufficient. The system does not take into account authorizations to block or unblock tasks.
The system runs the authorization check for permanent and temporary parameters in the following cases:
In transaction UCPP
In the consolidation workbench and in the consolidation monitor when permanent or temporary parameters are changed
using the menu or in the header area
In SAP GUI and in the Web Dynpro GUI
The system only runs an authorization check if tasks actually exist in the task hierarchy.
Recommendation
This authorization check should generally not be used for users who need to modify Customizing settings in the consolidation
workbench. We recommend that you use the authorization check for consolidation monitor users only.
Note
The performance of the authorization check largely depends on the SEM-BCS Customizing settings. Since the authorization
check can affect performance when permanent parameters are changed, we recommend that you use this function with
caution.
Activities
In transaction UC00, choose Global Parameters Users with Authorization Check or Roles with Authorization Check.
Enter the names of the users or roles for which you want to restrict the authorizations.
These Customizing settings are client-dependent. When users are copied or deleted, these Customizing settings are not
transported, copied, or deleted due to potential effects on performance.
Local Currency and Group Currency

De nition
Local Currency
Local currency for a consolidation unit.
If the local currency is not the same as the group currency, translation from the local currency to the group currency is required.
Group Currency
4/20/2019
Currency for a consolidation group.
Structure
Local Currency
The local currency is a property of the primary consolidation unit . The local currency is
version in dependent
effective year dependent
Group Currency
The group currency key is a characteristic in the data basis .
You can have multiple group currencies in a version .
You must always enter the group currency key in reporting . This also applies to reports in the local currency .
Note
The group currency is not a property of the consolidation group.
See also
Currency Translation
Local Currency Change for a Consolidation Unit
Consolidation in Multiple Group Currencies
Periodicity
Use
In the consolidation system, you can create consolidated nancial statements on a periodic basis. You use this function to de ne
when and how often this should be done, and to de ne how the system should behave if the consolidated subsidiaries use
different scal year variants.
Prerequisites
In the consolidation area, you have speci ed a single scal year variant. The scal year variant links the calendar year with the
scal year. It de nes how many periods and special periods a scal year comprises. For each calendar time period, the scal year
variant also assigns the accounting periods in which the system normally posts journal entries.
You have de ned a primary scalyearvariant(in the Implementation Guide for Strategic Enterprise Management/Business
Analytics at Financials Basis Master Data Framework Periodicity Specify Primary Fiscal Year Variant for Whole Client ).
Features
Dealing with Mismatching Fiscal Year Variants
4/20/2019
Each subsidiary decides which scal year variant it wants to use. Consolidation is confronted with the problem of how to
consolidate companies that use different scal year variants. The system approaches this problem as follows:
The scal year variant that is most decisive for consolidation is stored in the consolidation area as a eld with the role Fixed in
the Consolidation Area . This particular scal year variant cannot be changed afterwards.
Furthermore, you can specify a scal year variant for each consolidation unit . This scal year variant is used for storing reported
nancial data in local currency when such data is collected or entered manually. The scal year variant of the consolidation unit
is stored in conjunction with the data collection version.
When determining the exchange rate in currency translation , the system uses the scal year variant of the consolidation unit to
obtain the date from the scal year/period eld. If no scal year variant is speci ed for a consolidation unit, the system uses the
scal year variant stored for the consolidation area.
Except for currency translation, all other consolidation functions use the scal year variant that is stored for the consolidation
area.
Miscellaneous
All other details relating to the periodicity of nancial statements are de ned by
The consolidation frequency
The period category
Consolidation Frequency
De nition
The consolidation frequency determines how many consolidated nancial statements are generated per scal year.
In the consolidation system, the period ranges to be included for each set of consolidated statements are assigned to the
consolidation frequencies required.
 Example
Annual consolidation
Semi-annual consolidation
Quarterly consolidation
Monthly consolidation
Structure
Consolidation Interval and Consolidation Period
The consolidation frequency subdivides the periods starting at 001 without gaps into Consolidation Intervals.
 Example
For quarterly consolidation, there are the consolidation intervals 001-003, 004-006, 007-009, and so on.
4/20/2019
Only the ending period of the consolidation intervals can be posted; these periods are called consolidation periods.
 Example
For quarterly consolidation, there are the consolidation periods 003, 006, 009, and so on.
Periodic and Cumulative Processing
The system's periodic and cumulative processing differ as follows:
For periodic processing, the system includes all periods of the consolidation interval that were posted in the
consolidation period in the calculation of the values.
For cumulative processing, the system also includes all previous periods of the consolidation interval in processing.
De nition of Consolidation Frequencies
When de ning the consolidation frequencies, you select the valid consolidation periods.
The user interface for de ning the consolidation frequencies displays the periods that can be posted. If you require additional
periods (for example, because you want to consolidate weekly), you can show additional periods.
Example: Displaying Tasks in the

Additional steps might be necessary to display custom tasks (tasks you have de ned) in the consolidation monitor, depending
on which consolidation frequency you have chosen. This example presents two alternatives for achieving this. Both are based on
this scenario:
4/20/2019
You want to display all tasks (T1, T2, …, Tn) for the periods 3, 6, 9, and 12. But you also want to display tasks T1 and T2 for periods
2 and 5.
Use one of the following approaches:
Solution 1
1. Assign the frequency "Monthly" to the current version combination (making all periods valid).
2. Assign the frequency "Quarterly" to all tasks except T1 and T2 (making periods 3, 6, 9, and 12 valid).
3. Create a new consolidation frequency called "Custom" (making periods 2, 3, 5, 6, 9, and 12 valid), and assign this
frequency to tasks T1 and T2.
4. Make sure that a suitable frequency is assigned to all other tasks.
Note
If no consolidation frequency is assigned to a task, the system executes the task according to the global consolidation
frequency that is set for the version combination. This always applies to balance carryforward tasks because the
system does not permit deviating frequencies for this task category.
When this approach is used, the system shows a balance carryforward task in period 1 (assuming that period 1 is the rst valid
period of consolidation frequency "Monthly").
Solution 2
1. Create a new consolidation frequency called "Custom" (making periods 2, 3, 5, 6, 9, and 12 valid), and assign this
frequency to the version combination.
2. Assign the frequency "Quarterly" to all tasks except T1 and T2 (making periods 3, 6, 9, and 12 valid).
3. Do not assign a frequency to tasks T1 and T2.
When this approach is used, the system shows a balance carryforward task (along with tasks T1 and T2) in period 2. This is
because period 2 is the rst valid period of the global consolidation frequency, which is de ned for the version combination.
Period Category
De nition
Simpli es the period-dependent assignment of attributes to consolidation objects (for example, consolidation units).
Use
 Example
You assign currency translation methods to consolidation units. Consolidation unit A is to be translated with method T1 in
periods 006 and 012, and with method T2 in periods 002, 004, 008, and 010.
To avoid making six assignments, you de ne two period categories: P1 = {006, 012}, and P2 = {002, 004, 008, 010}. You
assign the translation methods to the consolidation unit by period category (rather than by period). This reduces the
number of assignments from 6 to 2.
4/20/2019
Structure
Period categories and period category groups
To avoid overlapping between period categories, there are period category groups .
If you want to assign properties to consolidation units with dependency on the period category, you can use only the period
categories that belong to the same period category group (per version and effective period ).
De nition of the parameter categories
You assign a period category to one period category group. The period categories within a period category group may not
overlap each other.
The work area shows the periods in which you can make postings. You can insert additional periods if required (for example, if
you want to perform weekly consolidation).
Data Model Synchronizer

Use
When you make changes to your data model in the SAP NetWeaver Business Intelligence (BI) (for example, you change the
length of a eld or a data type), these changes are not automatically transferred to the data model in the Consolidation
component. Instead, you need to regenerate the data elements, data structures, and tables affected by the change in the
Consolidation component. The data model synchronizer helps you regenerate the data model in Consolidation.
4/20/2019
When you launch the consolidation workbench, the system checks whether the data model in Consolidation still agrees with the
data model in BI. If these two data models differ, the system automatically runs the data model synchronizer . The
synchronization monitor gives you an overview of the changes to the master data in BI and the changes to objects in the data
model of Consolidation. You can simulate a regeneration of the objects and then perform a real regeneration. Only after both
data models agree with each other are you able to proceed with your work in the consolidation workbench.
Caution
Regeneration of data elements, data structures, and tables can lead to loss of data. Therefore, always check the results of a
regeneration using the simulation before performing an actual regeneration.
This is especially true if you shorten the length of a eld required for the Consolidation system and you have posted data in
the meantime. In such a case, loss of data is almost inevitable.
Furthermore, data certainly will be lost if you remove characteristics in Customizing for Consolidation that are referenced by
other characteristics. Under no circumstances can such encroachments be reversed by the data model synchronizer.
Prerequisites
To execute the data model synchronizer, you require authorization for authorization object FB_SRV_DMS .
Features
You can regenerate the tables for your current data basis or for your current client. Regenerating tables for the current client
also may affect other application components.
The following functions are available in the synchronization monitor :
Display of Changes in BI
The area under Master Data lists the objects of the selected data basis that have changed in BI. The area under
Changes lists what has changed in the master data of the object (for example, the new length of a eld).
The traffic light indicates whether the change necessitates the regeneration of the affected objects. You also can display
the error messages of the changes. To do this, choose Display Messages .
Display of Affected Objects in Consolidation
The objects affected by the changes are listed in the following places:
Master Data lists the changed objects for the selected data basis. Generated Objects lists all data elements,
data structures, and tables affected by the change.
Consolidation Area shows any objects of a consolidation area that have been affected by the change.
Cross Tables shows any client-independent tables that have been affected by the change.
Simulation of a Regeneration
You can simulate a regeneration of the affected tables. The following options are available:
You can simulate a regeneration for each affected object. To do this, choose Preview of Table Conversion for the
object. The system displays an overview of the table, before and after the regeneration.
You can run the simulation in a single series for all affected objects of the data basis, the consolidation area, and
the affected cross-client tables. To do this, choose Check .
4/20/2019
The simulation displays messages in the lower area of the screen. The traffic lights indicate whether the
regeneration of each object was successful.
Execution of a Regeneration
To execute a regeneration of the affected objects, choose Generate Everything . A regeneration can be run only for all
objects in a single run.
The regeneration displays messages for the individual objects in the lower area of the screen. The traffic lights indicate
whether the regeneration of each object was successful.
Activities
Perform the following steps to synchronize your data models:
1. Check if the changes in BI are correct and whether you really want these changes implemented in the Consolidation
system.
2. Simulate the regeneration of the affected tables and examine the results.
3. Execute the regeneration of the affected tables and examine the results.
Workbench for Customizing

De nition
Central work environment for con guring the consolidation system.
Use
You use the workbench at the following times:
During the implementation phase
During live processing for sizeable or critical changes to the Customizing settings
In the workbench, you can change and display Customizing settings for:
The permanent parameters
The databases and consolidation areas with the characteristics and key gures provided
The master data version
The master data that can have hierarchies
Organizational units ( consolidation groups and consolidation units )
Financial statement items and consolidation charts of accounts
Subassignments and their default values
The breakdown categories
The tasks in the consolidation monitor
The method layouts and the methods themselves
4/20/2019
The document types
Furthermore, mainly for testing you can do the following:
Post manual entries
Execute methods
Execute tasks
Without a selection screen (here, the task uses the current parameter settings)
With a selection screen (this lets you restrict the task to speci c consolidation units or groups, versions, and so
forth)
By contrast, when consolidation is run live (in a production environment) you use the Consolidation Monitor to execute tasks.
The system checks your Customizing settings for consistency. If inconsistencies are discovered, the system issues an error
message. You can then access detailed information on the errors.
Structure
Layout of the Workbench Interface
The following illustration shows the layout of the workbench:
Customizing Views: Process View, Technical View, and Tools (where applicable) (1)
4/20/2019
Here you can choose between two views of the Customizing objects: the process view and the technical view. Both views contain
the same Customizing objects, but the objects are displayed in different layouts.
The hierarchical structure of the process view represents a logical sequence for your Customizing steps.
The technical view focuses on the types of Customizing objects (characteristics, methods, tasks, and so on).
The third view is Tools . In this view you can take care of special Customizing duties such as transporting Customizing data or
analyzing and repairing data streams. By default, the Tools view does not appear on the screen. To have it appear, do the
following:
1. Choose Edit Settings .
2. A dialog box appears.Under Settings choose Workbench Main Navigation Views .
3. Select the indicator for Tools and save your settings.
For more information, see Tools .
Navigation Hierarchy: Customizing Objects (2)
In this area, the system displays the navigation hierarchy of the customizing objects in the technical or process view, depending
on which view is selected. For detailed information on a Customizing object, double-click on the object (end node).
 Example
To display all consolidation areas in the technical view, double-click the Consolidation Areas end node. The system then lists
all available consolidation areas in the lower left-hand area of the screen.
Detail: Customizing Objects (3)
This area contains either a at structure or a hierarchical structure with navigation targets. Double-clicking on a navigation
target displays the corresponding object (such as the consolidation area) in the work area. The context menu for the Detail:
Customizing Objects screen area provides functions such as Display, Change, Create, Delete, Transport Customizing, and
Execute .
Work Area (4)
This screen area displays the Customizing object that you previously selected in the Detail: Customizing Objects area.
Here you can access detailed information on the Customizing settings, or change the settings.
Messages (5)
This screen area displays messages (informational messages, warning messages, and error messages).
Documentation (6)
This screen area displays documentation for the Customizing activities for method layouts, methods, and more.
Dependencies Between the Screen Areas of the Workbench
Screen areas 2, 3, and 4 interrelate, which means what you select in screen area 2 controls what is displayed in screen area 3.
Likewise, what you select in screen area 3 controls what is displayed in screen area 4.
Note
4/20/2019
The Customizing object displayed in the work area does not necessarily always match what is displayed in screen areas 2 and
3. For example, if you display an object in the work area (4) and then you select a different Customizing object in screen area
2, the two areas will no longer match.
Settings for the Workbench
You can make settings for the Workbench itself (for example, for the Customizing views) at Edit Settings .
See also:
Transport of a Consolidation Area
Copying Consolidation Area-Dependent Settings
Customizing Comparison
Deletion of Consolidation Area-dependent Settings
Personalization of the Workbench

Use
You use this function to personalize the following in the consolidation workbench:
Displaying of views (process view, technical view, tools)
Displaying of Customizing objects in different views
Value lists in hierarchy maintenance
Various general settings (for example, prompt for transport requests)
Features
Settings
General Settings
You can specify whether to use the following options:
Display help texts for Customizing
Display the welcome screen when the workbench is launched
If you automatically record Customizing changes in the current client: Prompt for the transport request only once per
session
If you have activated automatic recording of transports in the current client and you have selected Prompt Transport
Request Only Once: Prompt for the transport request again the next time you save
You can select this option only if you have started the personalization within the workbench, and not within user
maintenance or role maintenance (see also Activities below).
For more information about these general settings, see the eld help.
Main Navigation: Views
4/20/2019
Here you choose which views are visible in the workbench:
Process view
Technical view
Tools (hidden by default)
Note
All three views cannot be deactivated at the same time – at least one view must be activated. If you need to prevent
a user from using the workbench, this restriction can be con gured in transaction authorizations.
Main Navigation: Process View, Technical View, and Tools
Prerequisite for these settings: You have con gured the Customizing settings for the data model, the master data, and the
consolidation functions. Only then are all related Customizing objects visible.
For each view, you choose which Customizing objects are visible in the workbench. For example, you can hide the Customizing
objects for speci c consolidation functions.
Note
If a Customizing object exists in both the process view and the technical view, and you hide the Customizing object in
one of the two views, the object is still visible in the other view.
In role maintenance (see below), you cannot specify that all Customizing objects are to be hidden.
The settings that determine whether Customizing objects are displayed always apply to the current consolidation area.
Where You Can Personalize Your Settings
You can make the workbench settings listed above at three locations:
In the workbench
In user maintenance
In role maintenance
In the workbench, you con gure the settings for yourself only.
In role maintenance, you de ne the maximum available to the user for the views and for the Customizing objects of each view.
This means that a user in the workbench or in user maintenance cannot select more Customizing objects than were provided in
the role – the user can only select fewer objects than those provided.
If a user is assigned to multiple roles, he or she sees the merged list of the selected Customizing objects of all of these roles.
 Example
User U has the roles A and B. All Customizing objects of the process view are selected in role A, and all Customizing objects
of the technical view are selected in role B.
Consequently, user U sees the Customizing objects of the process view as well as the Customizing objects of the technical
view.
4/20/2019
However, different settings in user maintenance and role maintenance can result in a situation where a user cannot see any
Customizing objects in the workbench.
 Example
User X has the role C. This role is de ned so that the user sees only the Customizing objects of the process view and only
those concerning analysis.
The user record for user X is de ned so that the process view shows only the Customizing objects for the consolidation
monitor.
In role maintenance, you de ne the defaults for all general settings and for the value lists and hierarchies.
The general settings for each user always take precedence over the role defaults.
Note
If access right restrictions have not been speci ed in the personalization settings for a user or role, the system does not take
these settings into account when deriving the access rights.
For example, a user is assigned to roles X, Y, and Z, for which settings have been con gured that restrict access to the
consolidation workbench. The user is also assigned to role A, for which no consolidation workbench settings have been
con gured. In this case, the system does not take into account the personalization settings for role A when deriving the
access rights for the consolidation workbench. The system only takes into account the restrictions speci ed in roles X, Y, and
Z as well as those in the personal settings for the user.
Activities
Workbench
1. To change the settings for the workbench, in the workbench menu choose Edit Settings .
2. Con gure your settings for the workbench.
3. Save your entries.
User Maintenance (Transaction SU01)
1. To change the settings for the workbench, call user maintenance in change mode.
2. Go to the Personalization tab page.
3. Select the object R_BCS_Workbench, and choose Change.
4. The Maintain User dialog box appears.
5. Con gure your settings for the workbench.
Note
To delete the personalized settings for a user and reset them to the default settings, choose Default Values.
Role Maintenance (Transaction PFCG)
4/20/2019
1. To change the settings for the workbench, call role maintenance in change mode.
2. Go to the Personalization tab page.
3. Double-click the personalization object R_BCS_Workbench.
4. Con gure your settings for the workbench in the dialog box that appears.
The personalized settings are transported along with the role.
Note
As in user maintenance, you can delete the personalized settings by choosing Default.
Saving and Locking Concept for the

Workbench
Saving Concept
Differences Between Transaction Data and Master Data
The system writes transaction data directly to the SAP NetWeaver Business Intelligence (BI).
Master data is saved as follows:
Saving Concept for Master Data
Changes you make to the customizing settings are written to the database only after you choose Save .
Saving changes made during all operations
When you perform multiple operations in sequence (for example, you created document type 1, created method 4, and changed
method 3), the system “collects” these changes in a buffer and saves them all at once when you choose Save .
4/20/2019
Reversing changes in the last operation
If you performed multiple operations since the last time you saved, you can reverse the changes made in the last operation by
choosing Cancel .
4/20/2019
However, after performing two or more operations, it is not possible to only reverse the changes made during the rst
operation.
Reversing changes made during all operations
If you performed multiple operations since the last time you saved, you can reverse all of those operations by choosing Cancel
and then exiting the workbench without saving.
Data Synchronization of SEM-BCS and BI
As the master data of consolidation is stored in SEM and BI, the question arises whether and how these datasets can be
synchronized:
The SEM system is always the leading system in the consolidation system landscape. This also applies when parts of master
data are stored in BI and the Consolidation Workbench in the SEM system manipulates this data but does not save it separately.
The reason for the system sequence described is that SEM-BCS places increased formal requirements on master data storage
for business reasons; BI does not meet these requirements. Examples of these requirements are the time-dependent attributes
required for consolidation or the need for unique hierarchy assignments of characteristic values.
The ow logic of consolidation ensures the adherence to the considerably more restrictive approach to data modeling in
consolidation (in comparison to BI) since BI does not support this. This procedure cannot be reversed. Therefore, it is not
possible to trace the master data stored in BI back to consolidation consistently (data retraction).
Locking Concept
All customizing objects you work on while performing a series of operations are locked for other users until you save the
changes of those operations.
4/20/2019
Recommendation
If several people work on the same customizing objects at the same time, they should save their changes at regular
intervals.
Task
De nition
Consolidation step in the system from the accounting perspective
Use
You can de ne tasks for the different business consolidation processes in your company.
 Example
For statutory consolidation, you specify that interunit elimination is to be executed using the following tasks:
Elimination of interunit payables and receivables
Elimination of interunit revenue and expense
Elimination of investment income
Structure
Task Categories
The following task categories are available:
Task Category Name
05 Balance carryforward
07 Period initialization
10 Data collection
20 Copy
25 Reconciliations
35 Manual posting
40 Currency translation
45 Capitalization and valuation allowances
50 Consolidation group changes
55 Interunit elimination
60 elimination of IU pro t/loss in inventory
65 Elimination of interunit pro t/loss in transferred assets
4/20/2019
70 consolidation of investments
73 Posting of group shares
75 Reclassi cation
80 Allocation
85 Validation
90 Custom
95 Sign-off task
Task Groups
You can assign tasks to task groups. You can execute task groups in the Consolidation Monitor.
 Example
You can de ne a task group with the following tasks:
Data collection
Manual standardizing entries
Task Hierarchy
For the characteristic Task, there is only one hierarchy with edges that depend on the version, effective year, and effective
period. That is, there is exactly one root node on which the overall status of the task is managed in the consolidation monitor.
The end nodes of the hierarchy are tasks, while the nodes are task groups.
4/20/2019
You can execute all tasks of a task hierarchy in the consolidation monitor.
For more information, see Task Sequence.
Time Dependency of Tasks and Task Groups
A task can be executed if the speci ed period is a consolidation period in the relevant Consolidation Frequency. When a task is
executed, the system determines the associated method and document type.
You can assign the consolidation frequency for each task individually, or you can assign the consolidation frequency globally by
assigning it to the version combination.
Integration
Relationship between Tasks, Document Types, and Methods
4/20/2019
In Customizing, you can assign one or more document types to a task. A document type can be used in no more than one task.
The following table shows the relationships between:
Tasks and document types
Tasks and methods
Task Task: Document type Task: Method
Balance carryforward – 1 : 0 or 1 : 1
Data collection – 1 : n (n ≠ 0),
Assignment by consolidation unit

possible
Copy task – 1 : n (n ≠ 0),

possible
Manual posting 1 : n (n ≠ 0) –
Currency translation – 1 : n (n ≠ 0),

possible
Validation – a) For reported nancial data and

standardized nancial data:
1 : n (n ≠ 0),

possible
b) For consolidated data:
1 : 1, no assignment possible
Capitalization and valuation allowances 1 : 1 or 1 : 2 –
Consolidation group change 1 : n (1 ≤ n ≤ 6) –
Interunit elimination 1:1 1:1
Reconciliations 1:1 1:1
elimination of IU pro t/loss in inventory 1:1 –
Elimination of interunit pro t/loss in 1:1 –

transferred assets
Reclassi cation 1 : 0 or 1 : 1 1:1
Allocation 1:1 1:1
consolidation of investments 1:1 –
The tasks (and methods) are linked to a speci c consolidation area.
Assignment of Methods to Tasks
4/20/2019
See the section about methods.
Document Type
De nition
This classi es the posting data with various attributes.
You can use document types to assign certain properties to consolidation entries, for example, properties for updating the
database and processing currencies.
Structure
A document type speci es the following attributes required for posting journal entries, translating foreign currency, and
evaluating data:
Posting Level
See Posting Levels for Classifying Journal Entries .
Balance Check
You can determine how balances are checked when posting to statistical items:
Error message if balance not equal to zero
Warning message if balance not equal to zero
No balance check
When one or more balance sheet or income statement items are posted and the balance equals zero, the system always
displays an error message – regardless of which balance check option you have chosen.
Business Application
You can choose one of the following options:
Elimination of investment income (posting level 20)
Elimination of interunit pro t/loss in transferred inventory (posting level 20 or 30)
Elimination of interunit pro t/loss in transferred assets (posting level 30)
Proportionate consolidation (posting levels 02, 12, or 22)
Consolidation of investments (posting level 30)
Other
Automatic or Manual Posting
You need to specify whether journal entries are posted automatically or manually .
Key Figures to be Posted
You can select the following key gures to be posted: transaction currency, local currency, group currency, and/or quantity.
4/20/2019
For more information, see Key Figures to be Posted .
Inversion
You determine whether an automatic document inversion is posted in the subsequent period of consolidation. In this case, a
document that has been posted in a given consolidation period is automatically inverted by the system in the next consolidation
period. This occurs as soon as processing is begun in the subsequent consolidation period.
If the given document is reversed before the begin of processing of the next consolidation period, that document is no longer
inverted.
Two settings are available for documents that are posted in the last consolidation period of a scal year:
If these documents are to be inverted, the inversion takes place in the rst consolidation period of the following scal
year.
You can specify that these documents are not to be inverted.
For example, you may want to automatically invert documents that have been posted in elimination of interunit
payables/receivables – even across scal year boundaries.
You also may want to automatically invert documents that have been posted in elimination of interunit revenue/expense. Since
IU revenue/expense postings only affect the income statement, these are not inverted beyond a scal year.
For more information, see Automatic Inversion Prior Periods .
Repetition Run
When a task that posts documents automatically is repeated, this setting determines how the system treats documents that
have already been created in the previous session. This setting also applies to deletions (periodic and nonperiodic) .
This property appears only if you have chosen Depend on Document Type under “Repetition Run” in the Customizing settings
for version combinations (see also Customizing of Versions ).
NumberRange
See Number Range.
Clearing Items
See Fin. Stmt Imbalances, Deferred Taxes, CU Balancing Adjustments .
Posting of Deferred Income Taxes
See Deferred Taxes .
Method Assignments for Validation
See Validation of Manually-Created Documents .
Control of Subassignments for Manual Postings
See Fixing or Hiding of Subassignments .
Integration
4/20/2019
You can use a particular document type in one task only (with a given version, scal year, and so on).
For information on the relationship between tasks and document types, see also the section about tasks .
Method Layout
De nition
Customizing tool in consolidation. In a method layout, you establish the prerequisites under which all methods can be de ned
that are based on that method layout.
Structure
A method layout determines the following:
The appearance of the step hierarchy for the methods that are based on that particular method layout
Which characteristics and key gures from the consolidation area are used in the methods
At which point in the methods these characteristics are visible and/or ready for input
Activities When De ning a Method Layout
You de ne method layouts in the technical view of the Consolidation Workbench.
Specify which characteristics you want to use for the methods that are based on the method layout you are de ning:
Select the target column.
Drag the characteristics to the desired position in the target column. (You can select multiple characteristics with
Shift or Ctrl .)
Specify whether you want the method to have steps. If you want the method to have steps, drag at least one
characteristic to fast entry . If you want to create substeps, proceed in a similar manner by dragging a characteristic to
fast entry at the step level.
If you want to maintain the values of certain characteristics in the detail screen of the method, drag those
characteristics to detail screen .
You can add additional characteristics in the detail screen of the method.
Specify the level (method level or any step level) from which you want the individual components of the method to be
visible (for example, in allocation: sender and receiver). To do this, move the arrows to the desired position.
Note
To remove a characteristic from the method layout when it is no longer needed, drag the characteristic to the list of
available characteristics or to the trash can symbol.
Example
The following gure shows the de nition of a method layout in an allocation:
4/20/2019
Method
De nition
Customizing tool in consolidation. You use methods to control how the system calculates and posts automatic consolidation
entries.
Most methods are based on method layouts – (see also Creating a Method with Step Hierarchy ).
Integration
To be able to execute the tasks, assign the methods to the appropriate tasks or consolidation units.
The assignments are always based on the version and time: The version dependency is established by task versions. There is a
separate task version for each task category for which version-dependent assignments are required (such as the method or
document type). In customizing, you must assign a task version to the version.
The following types of method assignments are available:
Assignment of methods to tasks
Assignment of methods to tasks dependent on the consolidation unit
4/20/2019
Assignment of methods to consolidation units and consolidation groups
You assign a method to tasks and consolidation units when you create a new task:
Assigning Methods to Tasks
You assign the methods to tasks with the following task categories:
Data collection
Copy task
Validation
Reconciliations
Interunit elimination
Reclassi cation
Allocation
In addition to the version and time dependency mentioned above, there is also a dependency on the period category for the
assignment of methods to tasks (exception: balance carryforward). This means that within the same task, you can assign
methods to different period categories. However, you can only choose period categories that belong to the same period
category group.
You have de ned a period category group that contains the following period categories:
Period Category Description Periods
410 January to November 1, 2, 3, ... , 11
411 December 12
You could make the following assignment between methods and period categories:
Period Category Method
410 METH1
411 METH1
You can choose the possible period categories freely in the customizing of the method. If several period categories are possible,
the system chooses the period category that best suits the current values of the global parameters as a default setting when it
creates the method. In the example above, the system would propose period category 411, if 12 is set as the period in the global
parameters. But you can also choose another period category.
4/20/2019
In the following cases, you indirectly assign a method to a task:
You can assign a copy method to a data collection method, and assign the data collection method to a data collection task (see
De ning a Copy Method ).
You can assign a currency translation method to a copy method, and assign the copy method to a copy task (see
Consolidation in Multiple Group Currencies ).
Assigning Methods to Tasks Dependent on the Consolidation Unit
You can assign methods to the task depending on the consolidation unit with the following task categories:
Validation
Data collection
Special conditions apply to data collection. For more information, see Data Collection Method .
4/20/2019
Creating a new currency translation task
Assigning Methods to Consolidation Units and Consolidation Groups
This type of assignment applies to:
Accounting Techniques for consolidation of investments
Consolidation of investment methods
For more information on this topic, see the section on assigning accounting techniques and consolidation of investment
methods .
Creating a Method with a Step Hierarchy

Use
You use this procedure to de ne methods and method steps based on a method layout that is intended for a step hierarchy.
You can apply this procedure in the following processes:
Execution of a Currency Translation
Execution of a Rounding
4/20/2019
Execution of Reconciliations and IU Eliminations
Execution of a Reclassi cation
Execution of an Allocation
Prerequisites
In the technical view of the Consolidation Workbench, you have created a method layout using a step hierarchy for one of the
consolidation functions (such as currency translation). Step hierarchies can have multiple levels.
Procedure
The procedure shown here is kept general in nature. Keep in mind that the procedures for individual consolidation functions will
vary.
1. Go to the technical view of the Consolidation Workbench and choose Method . Here, choose the consolidation function
(such as currency translation) and create a method.
The Create Value dialog box appears . Under Layout , specify the method layout to be used as the basis for de ning the
method.
2. First, de ne the global parameters, which apply to all steps. (For example, for currency translation this would be the
source key gure and the exchange rate type on the Reference Translation tab page.)
3. Go to the Fast Entry tab page to de ne the individual steps. (For example, for currency translation you create a step for
each combination of currency translation key and exchange rate type.)
When you create a step, the system assigns a dummy number as the name. This number has no effect on the order in
which the steps are executed. (The steps are executed from top to bottom.)
a. Choose the arrow in the Navigation column to go to step maintenance. De ne the selection conditions and
properties of the step, and if desired you can change the name of the step.
b. In step maintenance, use the and buttons to navigate from one step to another within the same step level.
Use the button to navigate up to the higher step level (the method is at the top).
The new step hierarchy is also shown under the method in the screen area for Customizing objects (at the
bottom left of the Consolidation Workbench). Expand the list (if necessary).
4. In the screen area for Customizing objects you can change the sequence of steps using drag and drop.
5. Save the method.
Result
Once you have assigned the method to a task and executed the task in the Consolidation Monitor, the system executes the
method and its steps one at a time (from top to bottom). A con rmation message is displayed after successful execution.
Example
Refer to the following examples when creating method layouts and methods with step hierarchies:
Example: Execution of a Currency Translation
Example: Execution of a Rounding
Example: Elim. of IU Pay./Rec. with Splitting of Differences
4/20/2019
Example: Standardization of Fixed Asset Depreciation
Master Data and Hierarchies

Purpose
You use master data and hierarchies to model your corporate structure in the consolidation system.
Integration
The consolidation system (SEM-BCS) is a distributed system. The storage of the master data and the hierarchies for
characteristics is also distributed. The following options are available for storing master data:
Most of the master data and hierarchies are stored in both the consolidation system and SAPNetWeaver Business
Intelligence (BI) . This approach provides fast access to the data in the consolidation system. At the same time, the
master data and hierarchies are also accessible in BI – for example, for reporting purposes.
Note
Always make changes to the master data and hierarchies in the consolidation system, not in BI. This way, the data is
automatically synchronized. For more information about automatic data synchronization, see Manual Data
Synchronization .
When you make changes to your data model in BI (such as changing the length of a eld), these changes are not
automatically made in the consolidation system. If the consolidation system uncovers differences in the BI data
model, the system issues an error message and prompts you to regenerate the changed objects in the consolidation
system. The data model synchronizer assists you in doing this.
Consolidation-speci c master data and hierarchies reside exclusively in the consolidation system. This includes
breakdown categories, consolidation frequencies, and Customizing objects such as tasks and methods.
Master data and hierarchies used in the source data bases reside exclusively in the BI system.
See also:
Saving and Locking Concept for the Workbench
Features
Master Data
Time- and/or Version-Dependent Validity of Master Data
The validity concept for master data enables you to de ne master data as being time-dependent, version-dependent, or both.
When a characteristic is time or version dependent, the system checks the validity of the single values and processes only those
single values that are valid for the permanent parameters ( scal year, posting period, and/or version) of the current session.
For more information, see Validity of Master Data .
Time-Dependent Attributes of Master Data
Some of the standard attributes for master data are dependent on time. When you change a time-dependent attribute, the
change takes effect starting in the scal year and period that are set in the permanent parameters of the Consolidation
Workbench. For more information, see Con guring Time-Dependent Customizing Settings .
4/20/2019
You can de ne customer attributes as being time-dependent.
You use this function to grant different privileges for accessing the characteristics of consolidation to persons who work with the
consolidation system. For example, you can determine that a user is only allowed to display or change the master data for a
speci c consolidation unit. For more information, see Authorizations for Master Data .
Where-Used List for Master Data
You can use the where-used list to determine whether, and where, a master data item is used in the consolidation system. The
where-used list is available for most master data items. For more information, see Where-Used List for Master Data and
Customizing Objects .
Hierarchies
You can create hierarchies for nearly all characteristics:
Only if a characteristic is set up for hierarchies in BI (meaning that the hierarchy indicator in BI has been selected for the
characteristic), can you create a hierarchy for that characteristic in the consolidation system.
No hierarchies can be created for certain characteristics, such as methods and breakdown categories.
Assignment of Nodes to Hierarchies
Node assignments are valid across different hierarchies: When one node is linked to other nodes and end nodes, this de nition
also applies to other hierarchies in which the one node is used.
Under certain circumstances you are able to use end nodes in a hierarchy multiple times (see Multiple Occurrences of End
Nodes in a Hierarchy ).
A characteristic value can belong to one or more hierarchies (for example, under assets and/or liabilities ), or it is listed under
Nodes Not Allocated .
Item hierarchy
4/20/2019
Time and Version Dependency of Hierarchies
Hierarchies of consolidation units are always de ned as version dependent and time dependent.
Dependency of hierarchies on time or version is optional for other characteristics (for example, hierarchies for nancial
statement items and subassignments).
For more information, see Time and Version Dependency of Hierarchies .
Version
De nition
You can use versions to execute parallel consolidations according to different aspects, such as:
Data categories (for example, Actual, Plan, Target)
· Accounting principles (for example, U.S. GAAP, IAS, German HGB)
Valuations
Simulations (for example, to see how different exchange rates or a divestiture of a consolidation unit affect the consolidated
statements)
Use
A consolidation area can have one or more characteristics with the role version . If multiple characteristics have the role version
, you can choose which version combination is to be used in consolidation.
4/20/2019
The role version can not be assigned to dependent characteristics, which are compounded with independent characteristics.
There are two characteristics with the role version : Accounting Principles and Data Category. These might have the following
characteristic values:
Data category: Actual and Plan
Accounting principles: U.S. GAAP and German HGB
You use both accounting principles for planning, but you use only U.S. GAAP for creating consolidated statements with actual
data. Therefore, you select the following three combinations (out of the four that are available):
Actual / U.S. GAAP
Plan / U.S. GAAP
Plan / German HGB
Structure
Versions and Special Versions
Various Customizing settings are dependent on the version. These settings are stored internally in special versions. Special
versions summarize the Customizing settings according to speci c topics – for example data collection and currency
translation . When you de ne your versions, you can allocate the Customizing settings of one special version to several other
versions. By doing this, you can de ne a number of versions that differ in only one or a few areas, without having to repeat the
same settings for each different version.
In Customizing of versions you assign the desired special versions to the version combinations. When you execute a task in a
version combination, the system reads the assigned special versions and uses them to access the related customizing settings.
The system provides a function to give you an overview of the use of special versions. To see an overview, select a consolidation
area in the workbench. Choose List Field Properties in the context menu of the consolidation area . The system generates a
hierarchical list. In this list expand the Basic Data section and the relevant characteristics. The list displays for each
characteristic in the Special Version Type column whether the characteristic is dependent on a special version, or which one it is
dependent on. In this list you can also see an overview of the version and time dependencies within a consolidation area.
The following gure shows the scheme for accessing the totals data:
4/20/2019
Customizing of Versions
Use
You use this process to assign special versions to valid version combinations. By doing this, de nitions are made once only and
become available to any number of version combinations.
Prerequisites
You have executed the following activities in Customizing for consolidation:
You have created the consolidation area in which you want to customize your versions.
4/20/2019
You have created the version(s).
Process
De ning Valid Version Combinations
You need to de ne the version combinations that you want to use in the consolidation system. To do this, go to Customizing of
versions and choose Version Combinations.
If there is only one characteristic with the role version, this version is identical to the version combination.
If there are two or more characteristics with the role version, you de ne the (appropriate) combinations with which you want to
work. By doing this, you limit the number of valid combinations.
 Example
Example 1
You have two characteristics with the role version:
Data category with the values actual and plan
Accounting principles with the values U.S. GAAP and IAS
You use both accounting principles for planning, but you use only U.S. GAAP to create consolidated statements with actual
data. Therefore, you select the following three combinations (out of the four that are possible):
Actual / U.S. GAAP
Plan / U.S. GAAP
Plan / IAS
 Example
Example 2
There are three characteristics with the role version:
Data category with the values actual, plan, and forecast
Valuation with the values group and pro t center
Accounting principles with the values U.S. GAAP and German HGB
You select the following version combinations:
4/20/2019
Specify the following for each version combination:
Specify the consolidation frequency.
Specify how you want the system to handle documents that have already been created when you have to repeat the
program run. This setting also applies to the deletion function. For more information, see Deletion – Periodic and
Nonperiodic.
You can have the system delete or reverse old documents or any documents to be deleted – either for all documents of a
version combination or depending on the given document type. If you choose document type-dependent, you need to
de ne the system behavior for all document types of the consolidation functions involved. For more information, see
Document Type.
When execution of an automatic-posting task is repeated, the system compares each document to be posted with the
old documents. If a matching old document is found, the system retains the old document and does not create a new
document. The remaining old documents are either deleted or reversed, depending on what you have de ned.
Specify for which hierarchies (for example, item hierarchies) data entry is to be permitted on hierarchy nodes.
For example, if you want to enter plan data onto hierarchy nodes (that is, totals items) to later distribute the data using
an allocation task, you need to select the corresponding indicator in Customizing for version combinations. The indicator
applies to both manual data entry and data collection using exible upload.
Specify a method for the validation of totals data.
Special Versions
You can de ne special versions for each special version type. You can decide for each special version type whether you want to
create a special version or use special version 100 provided by SAP.
Special versions enable you to reuse the same Customizing settings in different version combinations. To do this, you de ne an
explicit dependence of the special version rather than a version combination in Customizing.
Use of Special Version Types
Special Description Examples of Usage

Version Type
05 Balance carryforward Task settings
4/20/2019

Version Type
07 Period initialization Task settings
Posting item for the adjustment of deferred taxes

(business function Financials, Group Close, Adjustment
for Changes of Tax Rates only)
Document type assignment for the adjustment of deferred

taxes (business function Financials, Group Close,
Adjustment for Changes of Tax Rates only)
10 Data collection Task settings
Year and period of the rst data collection
Tax rate
20 Copy task Task settings
25 Reconciliation of elimination data Task settings
35 Manual posting Task settings
40 Currency translation Task settings
45 Capitalization and valuation allowances Task settings
50 Consolidation group changes Task settings
55 Interunit elimination Task settings
60 Elimination of interunit pro t/loss in transferred Task settings

inventory
Inventory items
Data origin of the inventory data (business function

Financials, Group Closing only)
65 Elimination of interunit pro t/loss in transferred assets Task settings
70 Consolidation of investments Task settings
Document types for calculation base
Combined entry of investment and equity data
Goodwill in divestitures and transfers
Posting items for equity method
73 Posting of group shares Task settings
75 Reclassi cation Task settings
80 Allocation Task settings
85 Validation Task settings
90 Custom task Task settings
4/20/2019

Version Type
A0 Attributes Attributes for consolidation unit combinations:
Year and period of rst consolidation
Year and period of nal divestiture
Final divestiture at beginning of period
Properties of document types:
Number range
Automatic document inversion
Repetition run of automatic tasks
Work ow variant (business function Financials,

Group Close, Compliance only)
Validation method
Properties of the Assets/Liabilities role
H0 Hierarchy structure Hierarchies
Preceding task relationships
I0 Account assignment Assignment of breakdown categories to items
Balance carryforward: items to be carried forward
Selected items: global
Selected items: document type-dependent
Selected items: consolidation of investments
Selected items: elimination of IU pro t/loss in inventory
Type of assets/liabilities: posting items
OC Organizational change To year, to period
Sender/receiver relationship
Top node
T0 Tax rates Consolidation unit: tax rate
Document type: tax rate
V0 Validity Validity of master data
X0 Exchange rates Exchange rate indicator: assignment of an exchange rate

type
D3 Inventory data Saving of additional nancial data
D4 Supplier data Saving of additional nancial data
D5 Investments Saving of additional nancial data
D6 Equity Saving of additional nancial data
DD Assets/Liabilities Saving of additional nancial data
DE Noncurrent assets Saving of additional nancial data
4/20/2019

Version Type
95 Sign-off Task settings
Note
To list characteristics and their dependencies to special version types, select List Field Properties in the context menu for
the consolidation area, and choose Details: Basic Data and Dependencies.
Validity of Special Versions
If you want the validity of master data to depend on the version, you need to con gure the validity of the special versions in
Customizing. This Customizing is part of the master data for special versions. For each special version of the type Validity, you
can specify whether the values are to be valid or invalid by default.
In Customizing for the assignment to combinations, you can then assign these special versions of the type validity to the
individual properties that are used in the consolidation area and that are de ned as version-dependent in the data basis.
In the master data for characteristics that are de ned as version-dependent, you can then specify whether the master data
values are valid by selecting a checkbox. If you do not specify a value for the validity in the master data, the system uses a
default value instead. The system determines this default value from the special version that you have speci ed in Customizing
for combination assignments.
 Example
Example 3
You have created a plan version and an actual version.
In the plan version, all companies that are created in the system are to be valid by default. You therefore set the default
value for the validity of the plan version to Values are automatically valid.
In the actual version, you only want to use those companies that you explicitly create for this plan version. You therefore do
not set the default value for the validity of the plan version to Values are automatically valid.
You then assign these special versions of the type validity to speci c characteristics in Customizing for combination
assignment.
Customizing for plan version
1. In the Customizing settings for de ning special versions, create a special version of the type validity, for example,
special version V0 200.
In the master data for this special version, select the Values are automatically valid checkbox.
2. Assign the special version that you created in step 1 to the company characteristic in the relevant version
combination.
a. Choose Master Data Versions Special Versions Assign to Combinations .
b. Select the relevant version combination.
c. Under the Validity node, assign the special version that you created in step 1 (such as 200) to the Company
characteristic.
Customizing for actual version

4/20/2019
1. In the Customizing settings for de ning special versions, create a special version of the type validity, for example,
special version V0 100.
In the master data for this special version, do not select the Values are automatically valid checkbox.
2. Assign the special version that you created in step 1 to the company characteristic in the relevant version
combination as described above.
Result
When you create a company, the default setting for its validity depends on the permanent parameters currently con gured.
If you create the company from the actual version, the company is valid in both the actual version and the plan
version by default.
In the Customizing settings for the company, the Valid checkbox is selected automatically on the Validity Timeframes
tab page.
If you create the company from the plan version, the company is valid in the plan version, but not in the actual version.
In the actual version, the Valid checkbox is by default not selected on the Validity Timeframes tab page.
 Example
Example 4: Rules for special versions of the type Currency Translation Exchange Rates
The following table provides a Customizing example of rules for special versions of the type Currency Translation Exchange
Rates .
Accounting System Data Category Valuation Special Version
All values All values All values 100 — actual
All values FC — forecast All values 300 — forecast
All values PL — plan All values 200 — plan
Result
For the special version type Currency Translation Exchange Rates , the system assigns special version 200 to all version
combinations with data category plan, and special version 300 to all version combinations with data category forecast .
These rules simplify the assignment of special versions to version combinations. When you use these kinds of rules, you do
not have to specify an explicit assignment for each version combination.
Assigning Special Versions to the Valid Version Combinations
You assign the relevant special versions to each version combination.
You can generate default settings that are valid for multiple version combinations. To do this, choose Special Versions Rules .
The system uses a rule to derive the special version that is valid for a version combination.
At least one default rule must be de ned, which always applies when no separate rule is assigned to a version combination. To
de ne the default rule, select All Values for all characteristics with the role Version, and enter the required special version. SAP
delivers special version 100, which is used by default for all version combinations. You can also use your own special versions for
your rules.
4/20/2019
Now you can de ne your own rules for speci c version combinations, which can be used to derive other special versions.
Note
You assign the special versions Validity, Attributes, and Hierarchy Structure to the version combinations separately for each
characteristic of the special versions.
To assign the required special versions to a version combination, choose Special Versions Assign to Combinations . The system
shows for the version combination all of the special versions that were determined by the rules. You can overwrite the
determined special versions with single values. To do this, select the inheritance symbol , choose Single Value in the context
menu, and enter the required special version.
4/20/2019
 Example
You use the two version characteristics Data Category and Accounting Principles. You use the following as permitted
combinations:
Actual / U.S. GAAP
Plan / U.S. GAAP
Plan / IAS
Plan / German HGB
You want to use the value 200 in all plan versions as the special version Data Collection, except for the combination Plan /
U.S. GAAP, for which you want to use the value 210.
Create a rule for special version Data Collection as follows: Plan / All Values -> 200.
Overwrite this rule with the value 210 for the combination Plan / U.S. GAAP.
Reuse of Additional Financial Data

Use
4/20/2019
You use this function to be able to use Additional Financial Data de ned in the context of a Version in other versions. As a result,
you only need to enter the additional nancial data once. This reduces the effort if you work with several version combinations
within a Consolidation Area.
Prerequisites
You can use additional nancial data across different consolidation areas only if the individual consolidation areas have different
version combinations. However, if the Role 'Fixed in Consolidation Area' is assigned to the characteristic dimension and the
characteristic has a different value for each consolidation area, additional nancial data can only be saved cross-version for
each consolidation area (and not across several consolidation areas).
Features
You can read and write to the same additional nancial data with several version combinations. Use the concept of special
versions for additional nancial data for this purpose. This involves the data streams inventory data, supplier data, investments,
equity, assets/liabilities, and noncurrent assets (see also Data Basis).
To reuse additional nancial data, in the process view of the workbench, choose Master Data Versions Special
Version De nition and, (assuming they do not exist), create special versions (for example, for supplier data (D4), investments
(D5), and equity (D6)).
By de ning rules, you specify the standard behavior for objects to which the special version is assigned. For the Version Type:
Additional Financial Data, specify which assignment is to be prede ned between the special version and version for inventory
data, supplier data, investments, equity, assets/liabilities, and noncurrent assets.
Note
If you work with several special versions, you need to make the setting All Values for at least one of the assigned
characteristics.
Using Assign to Combinations, you can de ne for individual version combinations to which special version they should be
assigned (provided that you want an assignment that differs from standard behavior). Using Storage of Additional Financial
Data, you de ne how the special version types should be assigned to the version combinations de ned earlier.
Note
If you delete additional nancial data that is used more than once, this automatically has an effect on all version
combinations in which the additional nancial data is used.
Example
You want to transfer additional nancial data that you want to use for consolidation in different versions (plan vs. actual,
German HGB vs. U.S. GAAP). Your data model contains two characteristics: V1 (consolidation version) and V2 (accounting
principle). In Customizing for the data basis, you have assigned both characteristics to the Version role.
De ne the values 001 (actual) and 002 (plan) for characteristic V1, the values 'U.S. GAAP' and 'German HGB' (Master
Data Versions ) for characteristic V2. You have also created the version combinations (001, U.S. GAAP), (001, German HGB)
and (002, U.S. GAAP) (Master Data Versions Version Combinations ).
Now you create the special version SV1 for supplier data (Master Data Versions Special Versions De nition ). In the lower
left area of the screen, you add an entry with the value SV1 as a subentry of D4 (supplier data). Proceed in the same way for the
special versions D5 (investments) and D6 (equity).
4/20/2019
Now de ne the (standard) rules for the additional nancial data (Master Data Versions Special Versions Rules ). Process
the nodes supplier data, investments, and equity under Additional Financial Data in the lower left area of the screen.
Select All Values for V1 and V2 and assign SV1. As a result, the standard behavior is de ned. All version combinations now refer
to the special version SV1.
Now you can make a special setting (that differs from the standard behavior) for the version combination (001, U.S. GAAP) by
assigning combinations.
Under Storage of Additional Financial Data, you de ne in which version combination from V1 and V2 data is to be saved for
special version 'SV1'. For example, you could choose the version combination (001, German HGB).
If you now use exible upload to transfer supplier data for a version combination into the system, you can check for which
version combinations this data is available using the database list of supplier data.
Note
If you want to use additional nancial data across several version combinations, note the following:
If you specify in Customizing for the location of values for consolidation of investments that the system is to read equity data
from both the totals database and additional nancial data, the system applies a special logic. In accordance with this special
logic, the system takes into account the totals data for the prior year in the balance carryforward for additional nancial
data for equity. For more information, see Balance Carryforward with Different Locations of Equity Data.
If different version combinations use the same additional nancial data for equity, but the totals data is not the same, the
result of the balance carryforward for equity depends on the version combination in which you execute the balance
carryforward task. If the version combination in which you execute the balance carryforward task does not contain totals
data for equity data in the prior year, equity data may be deleted in the balance carryforward as a result.
Organizational Unit
De nition
A superordinate term for consolidation units and consolidation groups .
Consolidation Unit
De nition
The smallest element in a corporate structure that is used as a basis for consolidation.
Use
You can use the characteristic role consolidation unit for the characteristics company, pro t center, business area, plant, and
so forth.
Internal accounting transactions that are to be eliminated by consolidation are processed between the consolidation units. In an
accounting transaction, a consolidation unit can be the triggering consolidation unit or the partner unit.
Structure
4/20/2019
A Data Basis can have one or two characteristics with the role consolidation unit .
To portray a matrix organization in the consolidation system (for example, with companies and pro t centers), you de ne two
characteristics with the role consolidation unit . Then, for example, both the characteristic company and the characteristic
pro t center are assigned to the role consolidation unit .
Note
When assigning the role consolidation unit to several characteristics within a single consolidation area, make sure that all of
these characteristics have been created with reference to the same basiccharacteristic(reference characteristic or
template).
More Characteristics with the RoleConsolidation Unit
If you want to use more characteristics with the role consolidation unit , then, in customizing of the data basis, you must de ne
which consolidation unit is currency bearing (that is, determines the local currency).
The currency-bearing (or primary) consolidation unit and the other consolidation units are distinguished as follows:
Property Currency-Bearing Characteristic with the Non-Currency-Bearing Characteristic with

Role Consolidation Unit the Role Consolidation Unit
The role is not dependent on versions and X X

timeframes.
The characteristic always carries a value in X X

the transaction data (the value is never
initialized).
The characteristic determines the local X

currency (it is currency bearing ).
Methods for currency translation are optional(recommended) optional

assigned to the characteristic.
The characteristic is status relevant. X X
The total of all balance sheet and income X X

statement items must be equal to zero.
The characteristic has a subassignment for X X

partner units .
Transaction data can be summarized for X X

this characteristic – totaled values are
useful.
For each consolidation unit characteristic there is a consolidation group characteristic – see example:
Characteristic for Consolidation Unit Characteristic for Consolidation Group
Company Subgroup
Pro t Center Pro t Center Group
Furthermore, the following characteristics must exist for each characteristic with the role consolidation unit :
Partner unit
4/20/2019
Investee unit (if you are using consolidation of investments)
You can create a hierarchy of consolidation units for the characteristic with the role consolidation unit .
If you assign the consolidation unit role to the characteristics company and pro t center , you need to de ne which pro t
center belongs to which company in Customizing by choosing Master Data Consolidation Units Combinations of Consolidation
Units . Several alternative tools exist in the workbench to help you assign pro t centers to companies. The scope of functions is
the same so that you can use the tool that best corresponds to your way of working:
Table Display : The assignments between the characteristics take place in the table; each existing assignment forms a
data set which is displayed in a separate row. The most important additional attributes of the assignment are also
displayed for each row.
Two-Tree-Display : The values of the characteristics are displayed in a hierarchical structure which also visualizes the
characteristic hierarchies that exist in the system. Assignments between the characteristic values are displayed as
arrows which refer from one structure to the characteristic values of the other structure.
Note
The two-tree-display is only available in the SAP GUI.
Matrix Display : The characteristic values are displayed as matrixes (characteristic 1 in the rows, characteristic 2 in the
columns). You make the assignment between the characteristic values by setting an indicator at the intersection point of
the appropriate column/row.
Note
You can only use the matrix display if the characteristic displayed in the column has no more than 250 characteristic
values.
You can enter additional information for each assignment of characteristic values. This includes:
First consolidation at end of period or divestiture accounting at beginning of period
Period and scal year of rst consolidation and divestiture accounting
Validity period of assignment
Proceed as follows to access these settings in the different views:
Table display a nd two-tree-display : Double-click on a row or on an assignment arrow
Matrix display : Call up the context menu at the intersection point of the row and column which are assigned to each
other
Note
Note that not only the characteristics that you use as the consolidation unit, but also the assignments between the
characteristic values of these characteristics have master data character. This means that you cannot undo this
assignment once the system contains transaction data, which was posted with reference to one (or both)
consolidation unit that is linked by an assignment, exists in the system.
Additional Information about Consolidation Units
You can enter additional information when creating a consolidation unit:
Business partner information
4/20/2019
You can enter Business Partner Data such as the name of the legal entity, address data, and communication data. You
can do this on the Business Partner tab page.
Custom attribute information
If you de ned Custom Attributes , you can enter custom attribute information for each consolidation unit. You can do this
on the Other Attributes tab page.
Parent Unit
De nition
The highest upperunitwithin a consolidation group.
Parent units are the starting points for the paths in the ownership hierarchy, which are used for calculating the group shares.
Parent units are owned 100% by the consolidation group. No other consolidation units can have ownership in the parent units in
the same consolidation group.
In consolidation of investments there are no activities in which a parent unit is processed as an investee unit.
You change an upper unit to a parent unit by setting the corresponding indicator in Customizing.
Use
Setting the parent indicator is only meaningful if you use consolidation of investments.
You set the parent indicator in the process view of the workbench at Master Data Consolidation Units Accounting Techniques
.
Change to the Parent Unit

Use
When you change the parent unit in a consolidation group, the system automatically posts the required entries to adjust the
cumulative values of the balance sheet for all consolidation units of the consolidation group without an effect on earnings.
Prerequisites
You have activated the Organizational Changes function in the settings for the consolidation area.
Features
If the requirements speci ed above are ful lled, the system displays the following indicators in Customizing for accounting
techniques:
Parent, Before: Indicates for which consolidation unit the Parent Unit indicator was set in the previous period.
Change Parent Indicator at Beginning of Period: If the settings for the parent unit indicator are different in the previous
and current periods, you can specify whether the system is to execute the activities to change the Parent Unit indicator
at the start or end of the period.
4/20/2019
Note
Within a consolidation interval, the system allows the Parent Unit indicator to be changed just once for each consolidation
unit. This also applies if the consolidation interval encompasses multiple periods.
Automatic Activities for the Existing and New Parent Unit
If a consolidation unit that was a subsidiary unit in the prior period becomes the parent unit in the current period, the system
executes activity 81 (Investee Unit -> Parent) in the consolidation of investments. This activity increases the group share of the
new parent unit to 100%. The posting logic in this activity is the same as that in activity 11 (Total Divestiture) with posting logic
for organizational changes. This system thereby cumulatively reverses the values previously posted by the consolidation of
investments. This special logic for organizational changes prevents the system from posting entries to the income statement.
If a consolidation unit that was the parent unit in the prior period becomes the subsidiary unit in the current period, the system
executes activity 82 (Parent -> Investee Unit) in the consolidation of investments. This activity reduces the group share of the
new subsidiary unit to a value that is generally less than 100%. The posting logic in this activity is the same as that in activity 01
(First Consolidation) with the exception of the logic for statistical entries. The system therefore eliminates the investment and
equity values reported up to the time of the parent unit change and reports their minority shares.
Indirect Activities for the Investee Units
A change to group shares for the existing and new parent unit generally results in changes to the group shares of all
subordinate units in the hierarchy. The entries for these subordinate investee units therefore also need to be adjusted to re ect
the new group shares. To do this, the system executes the following activities:
Consolidation of investments activity 81 triggers consolidation of investments activity 20 (Increase in Indirect

Investment) for all investee units in the tree that are located beneath the new parent unit.
Consolidation of investments activity 82 triggers consolidation of investments activity 21 (Reduction in Indirect

Investment) with posting logic for organizational changes for all investee units in the tree that are located beneath the
existing parent unit.
Activities
Retention of Goodwill
If the system carries goodwill from the acquisition of the existing subsidiary unit, this goodwill is to be retained after the unit
becomes the parent unit. The reduction of the book value for the goodwill as a result of valuation allowances carried out for the
existing subsidiary unit before the parent unit indicator was changed must be taken into account.
To implement these requirements, you can proceed as follows:
In Customizing for consolidation of investments for activities, choose the Treatment of Goodwill tab page and specify
Direct Elimination as the goodwill treatment for the Step Acquisition activity.
In the period in which the subsidiary unit becomes the parent unit, you need to enter the goodwill previously carried for
this investee unit again. To do this, use consolidation of investments activity 83 (Activation of Goodwill in Parent
Change).
If you enter a value for the beginning book value that is not same as the original value, and you then perform the
consolidation of investments again in the same period, the system posts the difference between the two values as a
valuation allowance.
4/20/2019
Assignment of Accounting Techniques and

C/I Methods
Use
This function enables you to assign the following attributes to consolidation units:
Parent indicator
Consolidation of investments method
Accounting technique
You need to assign an accounting technique to the consolidation group change and reporting .
To use consolidation of investments (C/I), you need to assign the parent indicator and the C/I method.
You can assign the attributes separately for each characteristic with the consolidation unit role, but you need to assign
the attributes to at least one consolidation unit. Typically, you make the assignment for the consolidation unit that is
carried in local currency.
Prerequisites
You need to have at least one hierarchy of consolidation units.
If you want to assign consolidation of investments methods, you must rst de ne these methods in Customizing for
consolidation of investments in the section Method .
Features
Group Dependency
Assignments to consolidation units are dependent on groups, which means that a consolidation unit can have different attribute
values in different consolidation groups. To reduce maintenance effort, the system employs inheritance logic in which attribute
values in hierarchies are passed either up or down:
Bottom-up: If you assign an attribute value to a consolidation unit in a speci c consolidation group, the system passes
the attribute value upwards to all higher-level consolidation groups of that consolidation unit. Exception: The parent
indicator is not passed upwards.
Top-down: If you assign an attribute value to a consolidation group, the system passes the attribute value downwards to
all consolidation units that belong to that consolidation group, regardless of whether the ownership is direct or indirect.
Inheritance uses the following priorities:
Entries made by the user have the highest priority.
If the user makes no entry, the values are passed upwards.
If bottom-up inheritance fails due to a missing value, the values are passed downwards.
Inheritance con icts can occur in cases where a consolidation unit is explicitly assigned to several consolidation groups. If this
happens, a red traffic light is displayed and the user must enter the value.
4/20/2019
A symbol indicates that an attribute has been inherited. The detail screen shows from which consolidation group the attribute
was inherited.
Time Dependency
Attribute assignments can vary from one period to another. If the accounting technique or method changes in a certain period,
you enter a change of accounting technique .
The Change at Beginning of Period indicator determines whether the change occurs at the beginning or at the end (the default
setting) of a period.
The parent indicator cannot be changed in later periods.
Display Options
There are several ways you can display hierarchies:
View Complete: All non-empty hierarchies are shown in their entirety. If a consolidation unit has different attributes in
different consolidation groups, that consolidation unit appears in all of these consolidation groups.
This means that this hierarchy may be displayed differently than in the master data shown in the left section of the
consolidation workbench.
View Consolidation Group: This displays the selected consolidation group with all of its consolidation units (including any
indirect ones). In this view, you can modify the inherited attributes so that they re ect the appropriate values for the
selected consolidation group.
View Consolidation Unit: This displays the selected consolidation unit with all of the consolidation groups and hierarchies
in which it is contained. If the consolidation unit has different attributes in different consolidation groups, that
consolidation unit appears in all of these consolidation groups.
Matrix Consolidation (Multidimensionality)
Consolidation functions work with combinations of consolidation units and consolidation groups, not with individual
characteristics. The system, therefore, internally combines the assignments of all characteristic dimensions using the following
approaches:
The system uses the accounting technique and method of the dimension in which they were de ned by the user. If there
is a con ict between the assignments in different dimensions, the system displays an error message. For this reason, you
should maintain accounting techniques and methods in one dimension only.
If the parent indicator is maintained in one dimension only, then consolidation of investments treats as parents all
combinations in which the parent indicator has been set for one or more consolidation unit characteristics.
If the parent indicator is maintained in both dimensions, then consolidation of investments treats as parents only those
combinations in which the parent indicator has been set for all consolidation unit characteristics.
Accounting Technique
When a consolidation of investments method is assigned, the system automatically uses the accounting technique of that
method. You can only enter an accounting technique explicitly if no method is assigned.
Activities
Decide which consolidation unit dimensions you are going to make the assignments to, especially with regards to the
parent indicator.
4/20/2019
If you do not use consolidation of investments, you only need to specify accounting techniques.
We recommend that you use top-down inheritance for as many assignments as possible.
If you use consolidation of investments, each consolidation group requires at least one parent unit in one or more
consolidation unit dimensions. You can make sure this has been done by using the View Consolidation Group display
option.
De nition of Dates of First Consolidation and

Divestiture
Use
You use this function to de ne the dates on which the rst consolidationand divestiture accountingof consolidation units take
place within a consolidation group.
If an organizational change has been created for a consolidation group, you can specify that the organizational change be
applied to lower-level consolidation units.
Integration
The system takes into account any organizational changes you have created in the Consolidation Workbench. You can create
organizational changes in the process view of the Workbench at Master Data Consolidation Units Organizational Change .
When master data and hierarchies of organizational units are transferred, the system sets default values for the attributes that
determine the dates (see Loading of Master Data from Connected SAP Systems ).
Prerequisites
One or more consolidation unit hierarchies must exist.
Features
The following table lists the attributes you use for determining the dates of rst consolidation and divestiture accounting:
Attribute Use
Year of First Consolidation De nes the year of rst consolidation
Period of First Consolidation De nes the period in the year of rst consolidation
First Consolidation at End of Period Indicator that determines whether the consolidation unit is “ rst-
consolidated” at the end or the beginning of the period
Year of Divestiture Accounting De nes the year of divestiture accounting
Period of Divestiture Accounting De nes the period in the year of divestiture accounting
Divestiture Accounting at Beginning of Period Indicator that determines whether the consolidation unit is divested
at the beginning or the end of the period
The following attributes are available only if an organizational change has been created for one of the higher-level consolidation
groups:
4/20/2019
Attribute Use
First Consolidation Takes Organizational Changes into Account Indicator that determines whether the rst consolidation takes
organizational changes into account
Organizational Change Number for First Consolidation De nes the sending consolidation group
Divestiture Accounting Takes Organizational Changes into Account Indicator that determines whether divestiture accounting takes
organizational changes into account
Group Dependency
The attributes are not directly associated with the consolidation groups, but rather are consolidation group-dependent via the
consolidation units. At the same time, a given consolidation unit can have different attribute values in different consolidation
groups.
Furthermore, if you have a matrix organization, you also can determine the dates of rst consolidation and divestiture
accounting for the combinations of consolidation units.
The attributes that determine the dates of rst consolidation and divestiture accounting are inherited by all higher-level
consolidation groups from both the consolidation units as well as the combinations of consolidation units.
Inheritance Con icts
The system resolves inheritance con icts in which a consolidation unit has different attribute values in different higher-level
consolidation groups as follows:
If the dates of rst consolidation of the consolidation unit are different, the higher-level consolidation groups inherit the
earliest date. If the year and period of rst consolidation are the same, the beginning of the period is regarded as earlier
than the end of the period.
If the dates of divestiture accounting of the consolidation unit are different, the higher-level consolidation groups inherit
the latest date. If the year and period of divestiture accounting are the same, the end of the period is regarded as later
than the beginning of the period.
If the indicator First Consolidation Takes Organizational Changes into Account has different settings, the higher-level
consolidation groups inherit the attribute value as follows:
If the dates of rst consolidation are the same, the indicator is selected and the organizational change number is
transferred.
If the dates of rst consolidation are not the same, the indicator and the organizational change number (if
applicable) of that consolidation group in which the consolidation unit’s date of rst consolidation is the earliest is
inherited by the other consolidation groups.
If the earliest dates of rst consolidation are the same but the organizational change numbers are different, the system
issues an error message when a higher-level consolidation group is consolidated. This is because only one organizational
change number can be assigned to each consolidation unit.
If this occurs, you should examine the intended organizational changes and, if necessary, create a new organizational
change for the higher-level consolidation group.
If the indicator Divestiture Accounting Takes Organizational Changes into Account has different settings, the higher-
level consolidation groups inherit the attribute value as follows:
If the dates of divestiture accounting are the same, the indicator is selected.
If the dates of divestiture accounting are not the same, the indicator of that consolidation group in which the
consolidation unit’s date of divestiture accounting is the latest is inherited by the other consolidation groups.
4/20/2019
Activities
You can display and change the attributes in the process view of the Consolidation Workbench:
To edit the attributes for the consolidation units, choose Master Data Consolidation Units Consolidation Groups .
To edit the attributes for the combinations of consolidation units, choose Master Data Consolidation
Units Combinations of Consolidation Units .
Example
Assume you have the following hierarchy of consolidation units:
The consolidation units have the following dates of rst consolidation and divestiture accounting:
CUA in CG2 CUA in CG3 CUB in CG2 CUB in CG3
Year of First 2003 2002 2002 2002

Consolidation
Period of First 12 6 1 1
Consolidation
First Cons. at End of

Period
Year of Divestiture 2005 2005 2005 2004

Accounting
Period of Divestiture 12 12 3 12
Accounting
4/20/2019
CUA in CG2 CUA in CG3 CUB in CG2 CUB in CG3
Divestiture at Beginning
of Period
First Cons. Takes

Organizational Changes
into Account
Organizational Change 00001 00002

Number
Divestiture Takes
Organizational Changes
into Account
The attributes are inherited as follows:
CUA in CG1 CUB in CG1
Year of First Consolidation 2002 2002
Period of First Consolidation 6 1
First Cons. at End of Period
Year of Divestiture Accounting 2005 2005
Period of Divestiture Accounting 12 3
Divestiture at Beginning of Period
First Cons. Takes Organizational Changes

into Account
Organizational Change Number 00002
Divestiture Takes Organizational Changes

into Account
Business Partner Data

De nition
In Consolidation, the business partner data consists of the administrative data of a consolidation unit. This includes the name of
the legal entity, address data, and contact data such as phone and fax number.
Use
You use the component SAP Business Partner (CA-BP) to de ne the business partner data of a consolidation unit. This means
that the business partner data is stored in the central database of the SAP Business Partner component. This also lets you
access the business partner data of the other SAP application components that employ SAP Business Partner.
In consolidation unit maintenance, the business partner data of a consolidation unit can be found under the Business Partner
tab. To each consolidation unit you can assign an existing business partner or you can create a new business partner for a
consolidation unit.
4/20/2019
Caution
Before you can assign a business partner to a consolidation unit, you must have de ned a number range in the Customizing
settings for the SAP Business Partner . To do this, go to the SAP Reference IMG and choose Cross-
ApplicationComponents SAPBusinessPartner BasicSettings NumberRangesandGroupings De neNumberRanges.
There is also an option to upload business partner data into your SAP System from other systems using a Microsoft Excel le.
See: Uploading Business Partner Data with a Microsoft Excel File .
Structure
The SAP Business Partner has a large number of elds for storing business partner data. Since only a portion of these elds are
relevant for consolidation, the number of elds has been reduced in the Consolidation system. Speci cally, the Consolidation
System features only the organizationally related elds (that is, from the category organization ).
Business partner numbers
Business partners have two numbers, which are used for various assignments:
Business partner number
A business partner number is de ned for each business partner in the central database of the SAP Business Partner.
This number is valid within the SAP System.
When you create a new business partner for a consolidation unit, depending on your de nition of the number range the
system either automatically assigns a number or you need to enter your own number.
External partner number
If a non-SAP system already contains administrative data for the consolidation units, you can use the external partner
number to assign that data to the business partner data in the SAP System. The external partner number is particularly
useful if you want to upload the data from a non-SAP system into the SAP System using a Microsoft Excel le.
Uploading Business Partner Data with a

Microsoft Excel File
Use
You have the option to upload administrative data for consolidation units from a non-SAP system into your SAP System using a
Microsoft Excel le.
Unlike the consolidation-speci c collection of nancial data for consolidation units, this upload is a general function of the SAP
Business Partner component. For our purposes, you restrict the number business partner data elds to those used by the
Consolidation component. If you require other elds in addition to those prede ned by SAP, you need to add these separately to
the eld selection.
To make your settings for the Excel upload of business partner data, go to the SAP Reference IMG and choose Cross-Application
Components SAP Business Partner External Data Transfer .
Then go to General Information to see more information about transferring data from external systems into the SAP Business
Partner component. For more speci c information about the types of data transfers, go to Transfer Categories Transfer
Categories Business Partner .
4/20/2019
De ning a Sender Structure

1. In Customizing of SAP Business Partner, choose External Data Transfer De ne Sender Structure .
2. Choose New Entries .
3. In the eld Sender Structure , enter any name for your structure. Then, go to the Transfer Type and select 015 (central
business partners) using input help.
Under Sender Structure Tables , in the Item column enter 1 , and in the Dictionary Structure column enter RKCT<XXX>
(where XXX can be both numeric and alphabetic).
4. Do not con rm your entries yet. First, double-click the dictionary structure you just entered for item 1.
The screen Maintain Dictionary Structure for Sender Structure <xxx> appears.
5. Choose Sender Structure Include Template .
A list of all elds available in SAP Business Partner is displayed.
6. All elds are automatically selected. To deselect them, choose Deselect All . Then select the elds that are used in the
Consolidation system, as listed below.
Field Name Name Type Length Entered Value Special

Considerations
Header Data
AKTYP Activity type C 2 01
RLTP1 Object part C 6 000000
TYPE Partner category C 1 2 Category of

business partner
data: organization
BPEXT External number C 20
General Data 1 (communication data elds are address- in dependent)
NAME_ORG1 Name 1 C 40
LEGAL_ENTY Type of legal C 2

entity
LEGAL_ORG Legal entity C 2
ICOM_DEFLT_COMM Communication C 3
method
ICOM_CHIND_TEL Type of change C 1 I (insert)

indicator
ICOM_TEL_CNTRY Country C 3
ICOM_TEL_NUMBER Phone number C 30 Phone number of

head office
ICOM_TEL_EXTENS Extension C 10
4/20/2019
Field Name Name Type Length Entered Value Special

Considerations
ICOM_CHIND_FAX Type of change C 1 I (insert)

indicator
ICOM_FAX_CNTRY Country C 3
ICOM_FAX_NUMBER Fax number C 30 Fax number of

head office
ICOM_FAX_EXTENS Extension C 10
ICON_CHIND_SMTP Type of change C 1 I (insert)

indicator
ICOM_SMTP_ADDR E-mail address C 241
Address Data
ADEXT_ADDR External number C 20
CHIND_ADDR Type of change C 1 I (insert)

indicator
CITY1 City C 40
POST_CODE1 Postal code C 10
STREET Street name C 60
HOUSE_NUM1 House number C 10
COUNTRY Country C 3
REGION Region C 3
1. Choose Transfer .
Answer Y (yes) when you are asked whether to use CHAR elds only.
Answer N (no) when you are asked whether to sort the structure alphabetically.
2. Save your new dictionary structure and choose Back .
3. Save your sender structure.
Editing the Local MS Excel le

1. Edit your Excel le so that it corresponds to your sender structure. When doing this, keep the following in mind:
The column sequence must correspond to the eld sequence in your sender structure. You need to enter the
columns manually in the Excel le.
If you want individual cells to be blank, you need to enter two eld separators (for example, you can use a semi-
colon as the eld separator).
Assign the format category Text to all of the cells. This ensures that all cells adhere to the prescribed eld lengths
(for example, so that leading zeros are displayed).
2. Save your Excel le as a .CSV le ( <xxx>.csv ).
Caution
4/20/2019
If you exit the Excel le while in .CSV format and you reopen the le, the cells are no longer formatted as Text . Thus,
make sure that the cells in the Excel le still have the format Text before you transfer the le into the SAP System.
Starting the Transfer

1. In Customizing of SAP Business Partner, choose External Data Transfer Start Transfer .
2. Enter the name of your sender structure in the Transfer Program eld.
3. For the Input File , call up input help for Physical and select your Excel le in .CSV format on your local computer. Do the
same for the Output File .
4. For the File System , select Presentation Server.
5. For the File Type , select CSV Format.
Caution
If you execute the transfer in test mode, you need to format the cells as Text again before you execute the transfer in
update mode.
6. You can leave the default values in the other elds as proposed.
7. Choose Execute .
Result
Your business partners have been transferred into the SAP system. Now you can assign the business partners in the master
data of the consolidation units.
Fiscal Year Variant of a Consolidation Unit

De nition
Determines the scal year variant that is used for currency translation of the reported nancial data of a consolidation unit.
Use
Specifying Time in Consolidation
Consolidation is period-oriented. This means that the Customizing settings and the processing functions are always based on
either (a) the period speci ed in the current context (that is, the workbench or monitor parameters, or the selection screen for
executing tasks), or (b) the consolidation interval that results from the consolidation frequency. Hence, you always specify the
appropriate consolidation period on all selection and entry screens, and in all upload les. This especially applies to uploads of
transaction data and the optional input of the rst data entry period in the master record of the consolidation unit.
Specifying Time in the Consolidation Environment
In addition to its own functions, consolidation also employs various auxiliary functions that require speci c calendar dates. This
includes the currency translation and the time-dependent hierarchies in SAP NetWeaver Business Intelligence (BI). To enable
the system to determine a corresponding date from the consolidation period at all times, the prevailing scal year variant of
(central) consolidation needs to be xed in the consolidation area .
Consolidation Units with Noncalendar Fiscal Years

4/20/2019
Initially, the aforementioned rules also apply to consolidation units that have noncalendar scal years. In particular, the nancial
data of consolidation units always needs to be reported in the central consolidation period as prescribed by the consolidation
area – regardless of the current period in the decentralized nancial statements of the consolidation unit.
However, Consolidation supports one exception: If there are no current individual nancial statements that match the current
consolidation period, but you want to collect a past set of individual nancial statements for consolidation, you can do this by
specifying a different scal year variant in the master record of the consolidation unit . In this case, this information is used in
currency translation to nd the date for determining exchange rates.
Integration
The scal year variant de ned in the master record of the consolidation unit is interpreted exclusively in currency translation.
Its sole purpose is to support the scenario for collecting individual statement data based on noncalendar scal years (which is
described above). The scal year variant of the consolidation unit does not affect any other consolidation functions (such as
data entry and upload), nor does it affect consolidation reporting.
All periods speci ed in consolidation refer to the scal year variant that is xed in the consolidation area.
Example
The parent unit consolidates annually in period 012 as per December 31. The individual nancial statements of a subsidiary are
also annual, but as per September 30. In this case, the unmodi ed statement data needs to be reported according to the scal
year variant and period in the parent's consolidation system.
In the master record of the consolidation unit, you also need to de ne a scal year variant that has September 30 as the last
date of period 012. To determine exchange rates in consolidation period 012 for this consolidation unit, the currency translation
function now uses the date on which the values originally existed in local currency - in this case, September 30, not December
31.
Combinations of Consolidation Units

De nition
The joining of consolidation units (such as company and pro t center) in a matrix organization.
Use
You create a matrix organization by creating two characteristics with the consolidation unit role in the Customizing settings for
the consolidation area.
You make the Customizing settings for combinations of consolidation units in the process view of the Consolidation Workbench
at Master Data Consolidation Units Combinations of Consolidation Units . You de ne the valid combinations of consolidation
units and de ne their attributes. By de ning the valid combinations, you determine which combinations of consolidation units
can be used for posting consolidation entries and for reporting.
Structure
In the matrix display, the customizing screen for combinations of consolidation units lists all hierarchies with the consolidation
unit characteristics (thus, for example, the characteristics pro t center and company ). Speci cally, the system shows the
following:
The hierarchies for the one characteristic are listed vertically.

4/20/2019
A list of characteristic values of the other characteristic (listed in alphabetic order) is displayed horizontally.
To establish a valid combination (for example, of pro t center A and company 1), you select the appropriate indicator in the
matrix.
Company 1 Company 2 Company 3 Company Company 5

4
Pro t Ctr A
Pro t Ctr B
Pro t Ctr C
Pro t Ctr D
Pro t Ctr E
Pro t Ctr F
The following functions are available in the toolbar:
Symbol Meaning Activities the User and the System

Perform
Display all hierarchies The system displays all hierarchies in their

entirety.
Display end nodes only The system only displays the end nodes of
the hierarchies – not the entire hierarchies.
<Name of hierarchy> The system only displays the hierarchy you

selected.
Expand node
Collapse node
Expand all
Collapse all
Create assignments for selection To make assignments for multiple rows in

the matrix, select the rows and choose this
symbol.
Then the system sets the indicator for the

assignments.
Reset assignments for selection To reset assignments for multiple rows in

the matrix, select the rows and choose this
symbol.
The system deselects the assignment.
Reset all assignments
Show/hide description
4/20/2019
Symbol Meaning Activities the User and the System

Perform
Swap axes The system swaps the two axes so that the
horizontal consolidation unit is shown at the
vertical axis, and vice versa.
For example, you can use this function to be

able to run the function Create
Assignments for Selection later on. (It is
not possible to create assignments for
selected columns.)
Attributes of Combinations of Consolidation Units
You can access the following attributes for each valid combination of consolidation units:
On the Detail Display tab page, you de ne the dates for rst consolidation and divestiture accounting. For more
information, see De nition of Dates for First and Final Consolidation .
On the Validity Timeframes tab page, you de ne the time periods in which the settings are valid. These attributes
appear only when de nitions of the combinations of consolidation units in the data basis are time dependent or time and
version dependent. For more information, see Data Basis in the section “Authorization Check and Validity Check”.
On the Other Attributes tab page, you de ne those attributes that exist as data elds in the assigned DataStore
object(s). You assign the DataStore object(s) in the Customizing settings for the data basis, on the Data Model tab page
under Characteristics of "Consolidation Unit" Role .
Consolidation Group
De nition
An arbitrary group of multiple consolidation units and/or consolidation groups created for the purpose of consolidation and
reporting.
Use
You can use the characteristic with the role consolidation group to portray the structure of your corporate group. Depending on
the complexity of your group, you can:
Group the consolidation units into one consolidation group
Create multiple consolidation groups and arrange them in a hierarchy
Build multiple, parallel hierarchies of consolidation groups to structure the organizational units according to different
perspectives (for example, regional or product-speci c perspectives)
Structure
Each consolidation unit characteristic is assigned to a consolidation group characteristic.
Consolidation Unit Characteristics Consolidation Group Characteristics
4/20/2019
Company Subgroup
Pro t center Pro t center group
Posting to a consolidation group
You can not post directly to a consolidation group. If you, nevertheless, want to post values to a consolidation group (for
example, for step consolidation or two-sided elimination), you need to create a dedicated consolidation unit (delta node). Then
you insert the consolidation unit under Assigned End Node in the master data of the consolidation group. You can not assign a
consolidation unit that is already used in the hierarchy.
The system automatically inserts the consolidation unit speci ed under Assigned End Node into the hierarchy as the rst unit
beneath the consolidation group. You should post values that are relevant for the consolidation group only to this consolidation
unit.
Note
To make sure that only group-relevant values are posted to the dedicated consolidation unit, we recommend that you use
the same name for both the consolidation group and its delta node.
Attributes of a consolidation group
The Attributes section in the master data of a consolidation group shows all of the consolidation units that belong to that
consolidation group. In the attributes, you can de ne how each individual consolidation unit is consolidated within that group.
For example, you specify the year and the period of rst consolidation for each consolidation unit.
Inactive Consolidation Units

Use
A consolidation unit is inactive in the following cases:
At a point in time (year, period) before the rst consolidation
At a point in time (year, period) after the nal divestiture
When you manually set the consolidation unit in a consolidation group to inactive
Prerequisites
Features
In the consolidation unit hierarchy, the system displays inactive consolidation units in gray. If all consolidation units in a
consolidation group are inactive, the system also displays the consolidation group in gray.
The system does not take into account assigned end nodes or goodwill-carrying consolidation units. The latter are only available
if you have activated the Financials, Group Close, Business Combinations business function.
Note
To ensure correct display in SAP GUI for windows, see SAP Note 1475966 .
4/20/2019
Activities
To manually set a consolidation unit as inactive, in Customizing for consolidation groups, you select the Inactive Consolidation
Unit checkbox for the consolidation unit in question in the relevant consolidation group.
Item
De nition
Basis for the valuational entry, posting, and evaluation in consolidation.
The item is the central account assignment object in consolidation. It is somewhat similar to the “account” in general ledger
accounting.
The item is dependent on the consolidation chart of accounts, meaning that it applies only for the consolidation chart of
accounts in which it was created.
Use
You can not only use an item for accounting-relevant amounts or quantities in the balance sheet, income statement, or
appropriation of retained earnings. Rather, you can also manage statistical data and key gures in items.
Structure
You de ne items in the process view of the workbench, under Master Data Items Item .
Item Characteristics from Consolidation
You determine the characteristics of an item on the Item tab page using the information on entry, item type, and breakdown
category.
Entry
Debit/credit sign
To be able to enter the item values without a debit/credit sign later (for example, during manual data entry or a exible upload),
enter a xed debit/credit sign here.
 Example
Enter the + sign for asset items and expense items.
Enter the − sign for liability items and revenue items.
You then enter only absolute values when entering item values. When storing the values in the database, the system multiplies
the entered value by the debit/credit sign assigned to the given item (and, if applicable, by the sign of the given
subassignment).
Data entry block
If you set a data entry block, no further values can be entered for the item in periods after the initial entry period. (The initial
entry period is an attribute of the consolidation unit.)
4/20/2019
Item Type
The following item types are available:
Balance sheet
Income statement
Statistical: Balance
Statistical: Flow
Breakdown Category
See Breakdown Category.
Item Characteristics from BI
In BI, you can give the item additional characteristics. These are displayed only in the consolidation system when Customizing
the items on the Other Attributes tab page.
Consolidation Chart of Accounts

De nition
Systematic directory for classifying items.
Use
The use of a consolidation chart of accounts in the data basis is optional. If you do not want to work with the consolidation chart
of accounts, you can work with multiple item hierarchies instead.
For the characteristic Consolidation Chart of Accounts to exist in the data basis, the characteristics must be linked to the role
Item.
To improve performance, we recommend that you use as small a consolidation chart of accounts as possible. You can keep your
consolidation chart of accounts small by creating subassignments to existing items.
Structure
The consolidation chart of accounts is only dependent on the client. However, the items and the breakdown categories are
dependent on the consolidation chart of accounts.
There can be one consolidation chart of accounts per consolidation area. You need to de ne the independent characteristic
Consolidation Chart of Accounts uniquely in the consolidation area.
4/20/2019
In the consolidation chart of accounts, you arrange the items logically in item hierarchies. For example, you de ne a
consolidation chart of accounts with an item hierarchy for balance sheet items and a hierarchy for income statement items.
Example
Legal Framework Industry I/S Procedure Appropriation of Retained

Earnings (ARE)
U.S. GAAP Industry CSA ARE in the balance sheet
EU guidelines Industry PA ARE in the I/S
EU guidelines Industry PA ARE in the balance sheet
EU guidelines Banking ARE in the I/S
JP GAAP Industry CSA ARE in the balance sheet
Selected Items
De nition
Financial statement items that are used in consolidation postings to ensure that the balance:
per consolidation unit equals zero ( balancing item )
across all consolidation units equals zero ( clearing item )
Structure
The following selected items exist :
Clearing - Balance Sheet
This clearing item in the balance sheet enables consolidation entries to produce a total of zero for the balance sheet of a
consolidation unit .
Clearing - Income Statement
This clearing item in the income statement enables consolidation entries to produce a total of zero for the income statement of
a consolidation unit.
Clearing - Consolidation Unit
Consolidation entries use this selected item to ensure that the balance sheets and/or income statements across multiple
consolidation units remain in balance . Its balance is always zero within a document.
See also:
For information on the selected items in Customizing for consolidation of investments, see the section Selected Items .
Subassignment
4/20/2019
De nition
Characteristic used to further differentiate (break down) the values of the characteristic nancial statement item.
Structure
Any characteristic can be used as a subassignment.
Standard Subassignments
SAP delivers standard, prede ned subassignments.
Standard Subassignments with Special Consolidation Logic
The following subassignments use special consolidation logic – that is, these characteristics have roles with special properties:
Partner unit
A partner unit is a consolidation unit that has a business relationship with a (primary) consolidation unit.
Every characteristic with the role consolidation unit must have an identical partner characteristic partner unit.
A nancial statement item (or item) is broken down either by all existing partner characteristics or by no partner
characteristics at all. (Bear in mind that when an item is broken down, this can be an optional breakdown or a required
breakdown.)
The characteristic with the role partner unit is needed, in particular:
for interunit elimination and reconciliation
for the elimination of interunit pro t and loss in transferred inventory
Investee unit
The investee unit is used for recording values at investment holding items.
Transaction type
You can use the transaction type to see the changes to the item balances over time.
Changes to assets – from the opening balance to ending balance
Changes to appropriations
Changes to investee equity
You need the transaction type, for example, to create an asset history sheet.
Transaction currency key
The transaction currency key is stored in the data basis whenever a transaction currency is used.
Unit of measure
The unit of measure is stored in the data basis whenever quantities are used. It must be xed in the breakdown category.
Year and period of acquisition
The year and period of an acquisition are analogous to the scal year and period. The current scal year and period are
used as defaults. The period of acquisition requires that the year of acquisition is contained in the data basis.
Standard Subassignments Without Special Consolidation Logic
4/20/2019
In addition, you can also add the elds country and product group to the data basis of consolidation.
Custom Subassignments De ned by the Customer
Finally, you can use any additional characteristics as subassignments.
Integration
You use the breakdown category to specify which subassignments a nancial statement item has.
Breakdown Category
De nition
Determines which subassignments a given nancial statement item has. The following subassignments are prede ned:
Partner unit
Transaction type
Transaction currency
Unit of measure
Upper unit
Investee unit
Allocation characteristic
Year and period of acquisition
You can de ne other subassignments as well.
Use
 Example
The items for accounts payables and accounts receivables must have the subassignment partner unit to be able to perform
the elimination of interunit payables/receivables.
Structure
Breakdown Types
In customizing of the breakdown category, you specify the breakdown type for each subassignment of every item. The system
uses the breakdown category to allocate the breakdown type to the item.
The breakdown type determines whether or not the item values are broken down by the subassignment when the item value is
entered or posted, and how rigorously the assignment is checked for the given subassignment.
The following breakdown types are available:
Breakdown Type Name Meaning
4/20/2019
0 No breakdown
1 Optional breakdown Initialized value allowed
2 Required breakdown If no entry is made, the default value is set.
3 Required breakdown The value must be entered; the default

value may be entered.
4 Required breakdown The value must be entered; the default

value may not be entered.
In the Data Basis you determine whether a characteristic value is xed in the breakdown category.
Subassignments whose values are xed in the breakdown category only permit breakdown types 0 and 3.
Subassignments that use the role transaction currency only permit breakdown types 0 and 2.
The following applies to subassignments that are part of a compound relationship:
If a breakdown by the dependent characteristic exists, there must also be a breakdown by the independent
characteristic.
If the dependent characteristic has a required breakdown, then the independent characteristic must also have a
required breakdown.
Fixed Value
A xed value determines the value of the subassignment, that is, for all FS items with this breakdown category. You enter a xed
value for the following subassignments:
Unit of measure
For custom subassignments (those not prede ned by SAP) which you have declared as requiring a xed value in the
breakdown category
Default Selection
You can use the default selection of a given characteristic in manual data entry.
If a lead column is de ned as data-driven in a data entry layout, the system accesses the default selection you specify here
during data entry. Thus, the default selection determines the default values for the breakdown of a characteristic for the items
that have this breakdown category.
Maximum Selection
You create a maximum selection for the subassignment in the breakdown category if you want to only allow a subset of all
possible values of that subassignment for the items concerned. The maximum set determines the permitted values for a given
subassignment of those items that use the breakdown category.
The list of possible values (F4) then shows the reduced subset, and the system checks all entries against the maximum
selection.
 Example
By using maximum sets for the characteristic product group , the item cost of goods manufactured, services would only be
postable for service-type products.
4/20/2019
You determine whether maximum selections are used at all in the settings for the Consolidation Area .
The following rules apply when creating maximum sets:
Default selections must re ect a subset of the maximum selection.
You cannot de ne a maximum selection for dependent characteristics whose corresponding independent characteristic
does not have a xed value in the breakdown category.
Breakdown Check and Correction of

Transaction Data
Use
Transaction data can become inconsistent if:
You assign a different breakdown category to an item
You change the breakdown type in the breakdown category; or you add or delete breakdowns
You change the xed value in the breakdown category
You change the maximum selection
You delete characteristic values that are used for subassignments
The validity of a characteristic value for a subassignment expires
This function checks the breakdowns and adjusts the transaction data in a way that resolves inconsistencies within
subassignments.
However, the function does not correct inconsistencies that, for example, are caused by:
Deleting items, consolidation units, and so on
Changing attributes of characteristics that are in use (for example, changing the Local Currency attribute)
Prerequisites
You have con gured all of the Customizing settings for consolidation that are required for posting entries.
The relevant data streams contain data (which means that you have collected reported nancial data or additional nancial
data and possibly posted documents using the old breakdowns); and you have made one of the changes listed above. Relevant
data streams are those that contain the item characteristic and at least one subassignment. The goodwill data stream, for
example, is not relevant.
Features
When you start the breakdown check in the workbench (in the process view, under Master Data Subassignments Breakdown
Check), the system checks that the transaction data for all relevant data streams is consistent.
If you have changed breakdown categories, the following cases are possible:
4/20/2019
Noncritical; no adjustments necessary (symbol in table below: )
Automatic adjustment by the system ( )
Adjustment by the user is required ( )
For the breakdown errors to be corrected, you need to specify how the missing breakdowns or invalid values are to be provided.
The system transfers your adjustments to the affected transaction data.
Adjustment is not possible
If the cause of the inconsistencies is found in characteristics that are not used as subassignments, this function is not able to
make any adjustments. (Such causes might include removal of an item or a missing or invalid local currency.)
When you save, the system does not change the data records. You may need to perform activities in addition to this function to
reestablish data consistency.
The following table shows the possible cases when you change the breakdown type in the breakdown category. Some cases
contain sub-cases.
Changing the breakdown category from 1 ( Optional Breakdown, Initialized Value Permitted) to 0 ( No Breakdown):
If the initialized value was already speci ed before the breakdown was changed, no correction is necessary ( ). If a breakdown
was speci ed, the system automatically resets the breakdown ( ).
Changing the breakdown type in the breakdown category
To 0 1 2 3 4
From
1 / / / /
2 /
3 /
When executing the function for checking breakdowns and correcting transaction data, you can specify one or more scal years
and you can specify individual items or all items.
The User Interface of the Breakdown Check
When the breakdown check is nished, the system lists:
How many data records were checked and how many errors were found
Which data streams are affected
How many of the faulty data records...
Cannot be corrected by the function
Can be corrected by means of user intervention
4/20/2019
Can be corrected automatically by the system
Adjustments Tab
This tab shows all cases in which the user needs to make an adjustment. You need to specify the breakdown characteristics that
are missing and that are required.
The system displays one row per breakdown type and set of subassignments. (For example, the system displays a separate row
per value of the Partner Unit breakdown characteristic.) You need to ll in the missing information in each row.
To display the details for a row, choose More/Less Detail from the toolbar.
To display the messages for one or more rows, select the corresponding rows and choose Display Associated Messages from
the toolbar.
You can input the data one step at a time and intermittently choose Check. The system checks that your input is syntactically
correct. If the check is successful, the system collects your data (but does not yet write it to the InfoCube). At this point, the
data input you checked can no longer be adjusted, unless you choose Cancel and restart the breakdown check.
Only once you have entered all of the data can you choose Save to adjust any incorrect data records (this is because all entries
are required entries).
Statistics Adjustable Tab
For information purposes, this tab shows all cases in which the user or the system is able to make an adjustment.
On this tab, you can also display the messages for one or more rows (see description above for the Adjustments tab).
Statistics Non-Adjustable Tab
For information purposes, this tab shows all cases in which neither the user nor the system is able to make an adjustment using
this function.
On this tab, you can also display the messages for one or more rows (see description above for the Adjustments tab). The
system displays all messages for data records that are not adjustable. These messages may contain adjustable cases that are
related to data records that are otherwise not adjustable.
This tab does not display cases that do not contain required breakdowns by subassignments from the Investments and Equity
data streams.
Breakdown Groups Tab
A breakdown group usually corresponds to the breakdown category. Breakdown groups summarize transaction data that shares
the same breakdown properties:
The data records have the same breakdown types per subassignment characteristic.
All subassignments with a xed value in their breakdown category have identical values.
If the breakdown category uses maximum selections, the data records are subject to the same restrictions of those maximum
selections.
This tab displays the details of the breakdown group. These include the following:
The breakdown type for each subassignment
4/20/2019
The xed value of the characteristic in the breakdown category (if a xed value was chosen)
Activities
You check the breakdowns and adjust transaction data as follows:
In the process view of the workbench, choose Master Data Subassignments Breakdown Check
Enter the following on the selection screen:
The scal year(s)
The items to be checked
Then choose Execute.
The system:
Performs the breakdown check
Displays the summarized text
Shows (on the Adjustments tab) where you still need to specify breakdown information
Displays statistics for adjustable and non-adjustable errors
To display detailed messages, choose Display Associated Messages
For each single value on the Adjustments tab, correct the errors by specifying the missing values for the breakdowns or by
changing existing values.
Choose Check.
The system checks whether your adjustments are syntactically correct.
If the check is successful, choose Save.
The system:
Corrects the errors that did not require any user input
Corrects the errors that required user input
This means that the system modi es the corresponding data records in the InfoProvider(s).
Example
You make the following changes in breakdown categories BC10, BC20, and BC30:
Characteristic Breakdown Type Breakdown Type Type of Change
Before Change After Change (Symbols: see table above)
Country (default = EN) 3 4
(Country England)*
4/20/2019
Currency
Region 4 3
Unit of Measure
Acquisition Year 2 1
Period of First Acquisition
Partner Unit (default = 99999) 1 3
Transaction Type
Allocation Characteristic
Investee Unit
* In this case, the country is England, which means that the country was not posted with the default value. Therefore, the
change is not critical.
Country (default = EN)
Currency 2
Region
Unit of Measure
Acquisition Year 1 2
(record contains the breakdown

value)
Partner Unit (default = 99999) 2
Transaction Type
Investee Unit
Country (default = EN) 2 (record contains the default 4

value)
Currency
Region
Unit of Measure
4/20/2019
Acquisition Year
Partner Unit (default = 99999) 1 (record contains the default 4

value)
Transaction Type 4
Investee Unit
After the change, you execute a breakdown check.
For each single value on the Adjustments tab, make the necessary adjustments:
Tab Adjustments
Legend:
Italics = requires adjustment
Bold = has been adjusted
Breakdown Country InvesteeUnit Partner Unit Trans.Type Currency

Group*
3 CH 99999 →C2000 ..... →140 EUR
3 CH 99999 →C2000 ..... →140 GBP
3 CH C2200 ..... →140 GBP
3 CH C3000 ..... →120 EUR
3 EN →CH 99999 →C2000 ..... →120 EUR
3 EN →CH 99999 →C2000 ..... →120 GBP
* This breakdown group corresponds to breakdown category BC30.
Extract of Messages:
Breakdown of item 11301100 by partner unit: Default value 99999 not permitted
Breakdown of item 12110000 by transaction type: Required breakdown not supplied
Breakdown of item 30100000 by country: Default value EN not permitted
See Also
Consistency Check of Transaction Data
Default Value
4/20/2019
De nition
Characteristic value for the characteristic subassignment . The system automatically sets the default value if assignment
information is missing.
To enable the system to automatically set the characteristic value, the breakdown type of the characteristic must allow the
setting of a default value.
Use
When running a consolidation task, the system supplies the default value if no entry information is available for a given
characteristic.
 Example
You want to run a task to eliminate interunit payables/receivables.
In customizing of default values you speci ed consolidation unit CU1000 as the default partner unit. In customizing of the
method for eliminating IU payables/receivables you selected the Default indicator for the differential accounting object; you
did not specify a characteristic value for the subassignment.
The system automatically lls the accounting object with the default value CU1000 from customizing of default values.
Structure
Subassignments that can have default values
You can specify default values for all subassignments of the consolidation area except for:
Accounting objects that have a xed value in their breakdown category
Transaction Currency
Year of Acquisition
Period of Acquisition
Customizing the Default Values
You de ne the default values in a tree structure.
Each subassignment has a root node in the tree structure. If the subassignment has independent characteristics, the
independent characteristics are shown as a higher-level nodes.
Characteristic (Subassignment) Default Value Description
Country DE Germany
Pro t Center
Controlling Area A Pro t center 1 Books
Controlling Area B Pro t center 2 Magazines
4/20/2019
Transaction Type 120 Additions
Integration
A breakdown must be provided for each characteristic in the breakdown category, and the default value must be allowed.
Example
In general, default values operate the same way for all consolidation tasks that permit default values.
The operation of default values is explained using interunit elimination as an example:
If the IU elimination method provides a breakdown of the differential item by subassignments, the system needs to know which
value is to be posted per subassignment. You can specify one value per each subassignment in method customizing. You can
also select the Default indicator . The system uses the following posting logic:
Default indicator is not selected
If the default indicator is not selected, you must enter a value for the subassignment. The system always posts the difference
with this value.
Exception: If the breakdown is optional, you do not have to enter the value. In this case, the system leaves the subassignment
initialized.
Default indicator is selected
If you select the default indicator, the system attempts to derive the subassignment from the data being eliminated.
If you selected the default indicator and the system is unable to derive the subassignment from the data, the system proceeds
as follows:
If you selected the default indicator and speci ed a value for the subassignment in method customizing, the system
posts this value.
If you did not specify a value, the system posts the general default that was de ned in customizing of Default Values .
If no general default was de ned and the subassignment is a required breakdown, the system displays an error message.
Note
When subassignments belong to a compound of characteristics, keep in mind the following additional constraints for
selecting the default indicator:
You should uniformly select or deselect the default indicator for all characteristics in a compound (for example, country
and region).
The following applies to interunit elimination in particular:
If the independent subassignment has a xed value in the breakdown category, then the default indicator for the dependent
characteristic can only be selected if:
all FS items in both selections are broken down by these subassignments, and
the xed value of the independent subassignment for the items being eliminated, and the xed value of the differential
accounting objects are identical
4/20/2019
Otherwise, errors may occur or useless entries may be posted.
Custom Attributes
De nition
Attributes, which are freely de ned by the customer and used to further describe characteristics.
 Example
Characteristic: Company (with the role consolidation unit )
Attribute of consolidation units: plant type ; Values: manufacturing, sales, management
Use
Custom attributes are used as attributes of characteristics.
When attributes are created, they become available in the de nition of queriesas navigationattributes, which means that they
can be used as criteria for selecting data.
Structure
In Customizing you de ne:
The attributes themselves
The values of each attribute
Integration
You de ne attributes in BI, in InfoObject maintenance.
You create the values for attributes in the consolidation workbench.
See:
Creating a Custom Attribute
Creating a Custom Attribute

Procedure
A. Creating the Attribute (in the BI System)
1. Go to InfoObject maintenance in BI (in the SAP menu choose Modeling Object Maintenance InfoObject ).
2. Select the InfoObject for which you want to add the attribute, and choose Maintain .
3. To create the attribute, follow the procedure described in Tab Page Attributes .
4/20/2019
Note
If you want to be able to select an attribute when executing queries, you need to de ne the attribute as a navigation
attribute.
The new attribute is displayed in the consolidation workbench under Master Data Custom Attributes .
B. Creating Values for the Attribute (in the Consolidation System)
1. Go to the consolidation workbench and choose Master Data Custom Attributes .
2. Double-click the attribute you created.
3. To create values for the attribute, choose Create in the lower left area of the consolidation workbench.
4. Assign a key and a description for each value.
Result
The attribute is now available, for example to de ne more information about consolidation units. (This is done in the
consolidation workbench under Master Data Consolidation Units <name of characteristic> tab pageOther Attributes. )
Single Selection
De nition
You use single selections to de ne selection conditions for one characteristic.
Single selections also include the higher-level characteristics – for example, the higher-level characteristic controlling area for
characteristic pro t center.
The selection logic of single selections enables you to create complex selections.
You can set up a single selection so that it can be reused for the customizing of selections in consolidation functions.
Use
For example, you can use a single selection in the following consolidation functions:
Consolidation Function Use
Manual data entry Data entry layouts
Data collection Source selection
Target selection
Validation Selection condition in check expression
Currency translation Speci c translation
Rounding Selection 1
Selection 2
4/20/2019
Consolidation Function Use
Interunit eliminations and reconciliations Selection
Elimination of interunit pro t/loss in inventory Posting items
Consolidation of investments Location of values
Reclassi cation Trigger
Percentage Rate
Condition
Allocation Sender
Receiver
Trigger
Distribution key
Work ow for Approving Manually-Entered Documents Work ow variant: approval agent
Work ow for Approving Status Changes
Structure
Selection Conditions
Within a single selection you can use the selection conditions as follows:
To select single values and ranges
To select hierarchies and hierarchy nodes
For selections across multiple characteristics
For selections across the attributes of a characteristic
You can use all of the selection conditions listed here simultaneously and more than once within a given single selection.
In selections of single values and ranges, and hierarchies and hierarchy nodes, you specify one range to be included (green
symbols) and one range to be excluded (red symbols). When the single selection is executed, the system combines these two
ranges using the Boolean operatorAND NOT. This means that the selection selects characteristic values in the range to be
included, but eliminates from the selection those characteristic values that are in the range to be excluded. You can then
further restrict the selection with selections across multiple characteristics.
The selection logic is explained in full in the section “Selection Logic” below.
Selection of Single Values and Ranges
In selection conditions for selecting single values and ranges, you de ne which characteristic values are to be included or
excluded. You can select single values, ranges, or patterns:
These are some of the operators you can use for single values: =,≥
You can select closed ranges [ ] and open ranges ] [.
Furthermore, you can use patterns [x] (for example,CU 1*for all consolidation units with the leading characters “CU 1”).
4/20/2019
You can de ne multiple selection conditions for both the including range and the excluding range. When a single selection is
executed, the system makes the following links independently of each other:
The selection conditions for the including range using Boolean operatorOR
The selection conditions for the excluding range using Boolean operatorOR
Selection of Hierarchies and Hierarchy Nodes
In selection conditions for selecting hierarchies and hierarchy nodes, you de ne which hierarchy ranges are included or
excluded. You can select entire hierarchies or hierarchy nodes.
You can de ne multiple selection conditions for both the including range and the excluding hierarchy ranges. When a single
selection is executed, the system makes the following links independently of each other:
The selection conditions for the including range using Boolean operatorOR
The selection conditions for the excluding range using Boolean operatorOR
Selections Across Multiple Characteristics
When dealing with several characteristics that are based on the same basic characteristic, you can de ne selections across
multiple characteristics.
Basic characteristic:company
Characteristics:consolidation unitpartner unitinvestee unit
Selection example 1:company = investee unit
Selection example 2:company→country= partner unit→country
You can de ne multiple selections across characteristics. When the single selection is executed, the system combines the cross-
characteristic selections using the Boolean operatorAND
Selections Across the Attributes of a Characteristic
You can use all of the selection conditions listed above for attributes.
You can use all attributes that you have designated as a selection attribute in the data basis.
The including and excluding ranges are viewed separately for each attribute (see also the section “Selection Logic”).
You can have multiple attributes in the single selection. When the single selection is executed, the system combines the
attribute selections using the Boolean operatorAND
Selection Logic
When a single selection is executed, the system uses the following selection logic:
{ selection conditions for the characteristic AND selection conditions for the attributes }
4/20/2019
The selection conditions for the characteristic are broken downas follows:
( included values OR included hierarchy ranges )
AND NOT ( excluded values OR excluded hierarchy ranges )
AND ( cross-characteristic selection 1 AND cross-characteristic selection 2 AND cross-characteristic selection x )
The selection conditions for the attributes are broken downas follows:
{ selection conditions for attribute 1 AND selection conditions for attribute 2 AND selection conditions for attribute y }
The selection conditions for each individual attribute are broken downas follows:
( included values OR included hierarchy ranges )
AND NOT ( excluded values OR excluded hierarchy ranges )
AND ( cross-characteristic selection 1 AND cross-characteristic selection 2 AND cross-characteristic selection z )
In the consolidation functions you can have multiple characteristics in the selection, and make a single selection for each of
those characteristics. When a selection across multiple characteristics is executed, the system combines the characteristic
selections using the Boolean operatorAND
See Example: Single Selection for Master Data and Example: Single Selection for Transaction Data .
Starting a Single Selection
You can start a single selection in different places:
In the process view of the Consolidation Workbench at Master Data Single Selection
While customizing one of the consolidation functions listed above:
First you add the characteristic on the selection screen of the function. Then, for the characteristic you choose Complex
Selection . Then the system opens the single selection in the lower screen area.
While customizing a breakdown category:
In the process view of the Consolidation Workbench, you choose Master Data Subassignments Breakdown Category , and you
call up a breakdown category to be changed. On the Default and Maximum Selection tab page, you can create a complex
selection for the default selection and/or maximum selection by choosing Complex Selection in the context menu.
The User Interface of a Single Selection
The user interface of a single selection has the following layout:
4/20/2019
(A) Input Area
Here you de ne your selection condition.
(B) Selection Area
This area lists the values of the characteristic – either as a simple list or as a hierarchy (if hierarchies exist).
If the characteristic has attributes, you can use the dropdown box xxx to show a list of attributes for the characteristic.
In cross-characteristic mode , you can select the characteristics that belong to the basic characteristic.
You can drag values from the list to the value columns in the input area.
(1) Name
Here, the system displays the technical name (which cannot be changed on this screen) and you can enter a description for the
single selection. For more information, see the section “Reusability of Single Selections”.
(2) Toolbar for Customizing the Single Selection
Symbol Meaning Activities the User and the System Perform
Insert Initialized Value Inserts a new row, preceded by “=”; all

other cells are blank and not ready for
4/20/2019
input. The initialized value is selected. Only
one row is allowed per characteristic. The
same applies to attributes.
Insert Row
Delete Row
Move Entry Up
Move Entry Down
Sort in Ascending Order Sorts in blocks
Order: higher-level characteristics, the

characteristic, attributes of the
characteristic;
Order for subordinate blocks for an

individual characteristic: inclusive
ranges/hierarchy nodes, exclusive
ranges/hierarchy nodes, characteristics
across characteristics
Sort in Descending Order
Check Checks the consistency of the selection

conditions in the single selection
Test Run Produces a list of all values that are

selected according to the selection
condition
Expand Selection Presents the selection condition as string of

characters, which shows Boolean links AND
andORbetween the rows
Show Name / Hide Name Shows or hides the names for the values in
the “From” and “To” columns
Show Attributes / Hide Attributes Shows an additional column. Here, you can
enter the name of an attribute or select it
using input help. The column can be hidden
only if no attributes have been inserted.
Cross-Characteristic Toggles the mode: You can select only the

characteristics that belong to the same
basic characteristic.
/ Open Selection Screen/ Close Selection Opens/closes the selection area that lists
Screen the individual characteristics, individual
attributes, hierarchies, or hierarchy nodes,
which you can drag into the value columns
xxx <Characteristic> or <Attributes of This Displays a list of the characteristic values

Characteristic> or the characteristic hierarchies of the
leading characteristic; or displays a list of
all attributes or attribute hierarchies
Expand
Filter
Find
Find Next
4/20/2019
(3) Operators
In this column, you can choose the operators for your selection condition using the context menu (for example, for a cross-
characteristic selection, for ranges of a characteristic, or to exclude hierarchies or individual nodes).
(4) Input Area
Here you enter the values for the characteristic or the attribute.
(5) Leading Characteristic / Attributes of the Leading Characteristic
Here, you determine whether to display the hierarchies and values of the leading characteristic or an attribute in the selection
area.
(6) Selection Area
The selection area shows the hierarchies and values of the leading characteristic or an attribute.
Reusability of a Single Selection
In order to reuse a single selection, it needs to have a technical name. A maximum of 10 characters is allowed. You assign the
technical name when you create a single selection at Master Data → Single Selection
You can also create a reusable single selection when customizing a consolidation function by specifying a value for the complex
selection. The value is used as the technical name and shown in the single selection window. The reusable single selection is
then listed in the process view of the Consolidation Workbench under Master Data Single Selection. Reusable single selections
are always created for the basic characteristic. You can use reusable single selections also for each derived characteristic.
When a reusable single selection is used, any restrictions of independent characteristics must be compatible to the selection
condition.
If you want to use a selection condition only once, you do not need a reusable single selection. When de ning selection
conditions in the Customizing settings of a consolidation function, you can create a non-reusable single selection by leaving the
technical name eld blank.
Example
You want a selection condition to select all consolidation units that have manufacturing facilities in Europe, except for those
situated in Italy.
The basic characteristic is the characteristic Company .
Attributes From To
Region Europe
Region Italy
Plant type Manufacturing
Example: Single Selection for Master Data

The following examples illustrate how the system breaks down the selection conditions of a single selection .
4/20/2019
The following items have been de ned:
Item Dr/Cr Sign Item Type
11 – 29 + 1: Balance sheet
31 – 39 – 2: Income statement
91 – 99 + 3: Statistical: balance sheet
Selection Conditions Item 15
Item 35
Included values (all items except 15) OR (all items except 35)
Excluded values (none)
Selection logic (all items except 15) OR (all items except 35)
Result Items: 11 – 99
Item 35
Included values All items
Excluded values Items 15 OR 35
Selection logic (all items) AND NOT (items 15 OR 35)
Result Items: 11 – 14, 16 – 34, 36 – 99
Item 15
Item 35
Included values Item 16
Selection logic (item 16) AND NOT (items 15 OR 35)
Result Items: 16
Item 15
Item 35
Included values Item 15
Selection logic (item 15) AND NOT (items 15 OR 35)
Result Items: (none)
4/20/2019
Selection Conditions Item 11 – 19
Item 31
Item 12 – 13
Item 15
Included values Items (11 – 19) OR 31
Excluded values Items (12 – 13) OR 15
Selection logic Items [(11 – 19) OR 31] AND NOT [(12–13) OR 15]
Result Items: 11, 14, 16 – 19, 31
Item Item type 2–3
Included values For characteristic Item : items 11 – 99
For attribute item type : all items
Excluded values For characteristic Item : (none)
For attribute Item type : items with item type 2 – 3
Selection logic (items 11 – 99) AND [(all items) AND NOT (items with item type 2
– 3)]
Item Item type 1–2
Item Dr/Cr sign +
Included values For characteristic Item : items 11 – 99
For attribute Item type : items with item type 1 – 2
For attribute Dr/Cr sign : items with dr/cr sign +
Excluded values For characteristic Item : (none)
For attribute item type : (none)
For attribute dr/cr sign : (none)
Selection logic (items 11 – 99) AND (items with item type 1 – 2) AND (items with
dr/cr sign +)
Example: Single Selection for Transaction

Data
The following examples illustrate how the system breaks down the selection conditions of a single selection , taking cross-
characteristic selections into consideration.
4/20/2019
The following master data for companies has been de ned:
Company Country Local Currency
1000 Germany EUR
2000 Germany EUR
3000 United States USD
4000 France EUR
5000 France EUR
You want to use the single selection for the following transaction data:
No. Company Partner Value (in Group Currency)
1 1000 2000 100
2 1000 3000 200
3 1000 4000 300
4 2000 3000 400
5 3000 3000 500
6 4000 – 600
Selection Conditions Company Country Partner Country
Included values all transaction data
Excluded values –
Cross-characteristic selection Company Country = Partner Country
Selection logic (all transaction data) AND (Company Country =

Partner Country)
1 1000 2000 100
5 3000 3000 500
Selection Conditions Company Local currency EUR
Company Country Partner Country
Included values For attribute Local Currency : Company Local currency = EUR
Excluded values –
Cross-characteristic selection Company Country ≠ Partner Country
Selection logic (Company Local currency = EUR) AND (Company Country ≠

Partner Country)
4/20/2019
2 1000 3000 200
4 2000 3000 400
6 4000 – 600
Selection Conditions Company Country United States
Company Local currency EUR
Company Partner
Included values For attribute Country : Company Country = United States
For attribute Local Currency : Company Local currency ≠ EUR
Excluded values –
Cross-characteristic selection Company = Partner
Selection logic (Company = Partner) AND (Company Country = United States)

AND (Company Local currency ≠ EUR)
5 3000 3000 500

Use
You use this function to grant various privileges for accessing consolidation characteristics to people who work with the SEM
system.
Integration
The authorization concept of consolidation is embedded in the SAP authorization concept.
Features
Authorization checks are possible for all master data in consolidation.
You can de ne for each characteristic how the authorization is to be assigned and checked:
For each characteristic (for example, across all consolidation units) or
For each characteristic value (for example, for each consolidation unit individually)
There are the following authorization objects for this purpose:
Authorization object R_UGMD_CHA is used for aggregate checking of characteristics in the local system.
Authorization object R_UGMD_SNG is used for checking authorizations for individual characteristic values.
4/20/2019
Authorization object S_TABU_LIN (from SAP Basis) is also used for checking authorizations for individual characteristic
values. This authorization object is still supported to ensure compatibility with Customizing you have made in earlier
versions of SEM-BCS.
Note
The authorization objects R_UGMD_SNG and S_TABU_LIN are functionally the same. However, the use of generic
authorization object S_TABU_LIN can result in some operational restrictions in certain situations (for example, no
input help for characteristic values).
Recommendation
We recommend that you use authorization object R_UGMD_SNG when checking authorizations for individual values.
In Customizing, you need to specify which of the authorization objects the system should use.
In consolidation customizing, when you choose authorization checking for individual characteristic values of a characteristic, the
system generates an organizational criterion when you use the authorization object S_TABU_LIN. This allows you to assign
authorizations per characteristic value.
Master data can be stored in the SEM system and/or in SAP NetWeaver Business Intelligence (BI). A mechanism ensures that
the master data of both systems is kept synchronized. In the same way, the authorization check is extended across all systems
in which the characteristic resides. The BI system uses authorization object S_RS_IOMAD, which serves the same purpose as
authorization object R_UGMD_CHA in the local system.
It is possible that you operate BI and SEM in different physical systems. To allow authorization to be checked across systems, a
user requires the same authorizations in all systems involved.
Activities
To assign authorizations for characteristics, you make the following Customizing settings (steps A-D):
A) Customizing Settings in the Consolidation Workbench
In the workbench, you determine whether authorization checks are performed per characteristic or per characteristic value.
1. Navigate to the process view of the workbench and choose Data Model Data Basis .
2. Open the required data basis in change mode.
3. Go to the Authorizations tab page.
The system displays all of the characteristics for which you can assign authorizations.
4. For each characteristic, determine whether authorization is to be checked per characteristic value.
5. Save the data basis.
For those characteristics whose values are checked individually, the system generates an organizational criterion for
each characteristic value when you use authorization object S_TABU_LIN. The organizational criterion allows you to
assign authorizations per characteristic value in role maintenance.
B) Customizing Settings in Role Maintenance (Transaction PFCG) in the Local System
1. In the local system, start role maintenance from the SAP Easy Access screen by choosing Tools Administration User
Maintenance Role Administration Roles .
2. Specify an existing role or create a new role.
4/20/2019
3. In role maintenance, navigate to the Authorizations tab page and choose Change Authorization Data.
4. In authorization maintenance, activate the authorizations as follows:
De ne the aggregate authorizations for the desired characteristics (authorization object R_UGMD_CHA) under
Strategic Enterprise Management Master Data: Characteristics .
De ne the authorizations for individual characteristic values. Use one of the following authorization objects for
this:
Authorization object R_UGMD_SNG: Financials Basis Characteristic Values: Master Data
Authorization objects S_TABU_LIN: Basis Administration Authorization for Organizational Unit .
5. Save the authorizations.
C) Customizing Settings in the BI System
C 1) Customizing Settings in Characteristic Maintenance
1. In the BI system, activate authorization assignments per characteristic value as follows: Maintain the desired
characteristic, go to the Master Data/Texts tab page and select the indicator Master Data Maintenance with
Authorization Check.
2. Save the characteristic.
C 2) Customizing Settings in Role Maintenance (Transaction PFCG)
Proceed the same way as for the authorization assignments in the local system that is, de ne the following authorizations:
The authorizations for individual characteristic values (authorization object R_UGMD_SNG or S_TABU_LIN)
The aggregate authorizations for characteristics (authorization object S_RS_IOMAD)
D) Final Settings for Checking Characteristic Value Authorizations
If you have opted for an authorization assignment at the level of characteristic values, de ne which of the available
authorization objects should be included in the authorization check:
1. Start transaction UG01.
The Display Area Menu UG01 screen appears.
2. In the menu structure, choose Master Data Settings Parameter Settings .
3. In the table, search for the parameter Use Authorization Object R_UGMD_SNG for All Fields. If no entry exists for this
parameter yet, create an entry and assign the parameters.
4. Decide which authorization object the system should use for checking authorizations for individual characteristic values:
To use authorization object R_UGMD_SNG, under Parameter Value, enter X.
To use authorization object S_TABU_LIN, do not enter anything under Parameter Value.
5. Save your settings.
Note
If you do not perform the settings described above, the system assumes that the generic authorization object
S_TABU_LIN is to be used for checking characteristic authorizations in order to ensure downward compatibility.
4/20/2019
E) Checking Authorizations (System Activity)
Once you have completed the Customizing settings, the system can run an authorization check for characteristics based on
your de nitions. The system uses the following procedure:
4/20/2019
See Also
SAP Authorization Concept
Where-Used List for Master Data and

Customizing Objects
Use
You use the where-used list in the Consolidation Workbench to determine whether, and where, a master data item or
Customizing object (such as a task or method) is used in the consolidation system (SEM–BCS).
Particularly before you delete a single value, we recommend that you rst generate a where-used list and delete the
occurrences of the single value. If you fail to delete existing uses rst, the deletion of a single value can take more time because
the system scans the entire consolidation database and possibly the transaction data in SAP NetWeaver Business Intelligence
(BI), and then abandons the deletion process when it discovers the rst use of the single value.
Integration
When a where-used list is run for characteristic values that can also occur in transaction data, the system also scans the BI
InfoCubes and ODS objects that are referenced in the consolidation data bases.
Features
The where-used list is available for most master data items and Customizing objects.
When you run a where-used list for a single value, the system determines which data records use the single value and lists these
by name. For each data record it nds, the system also displays the parameters you need to specify in the Consolidation
Workbench to change or to delete the occurrence.
The result of the where-used list is displayed in the work area of the Workbench. The uses are arranged in the following lists
according to their type. Each list is shown only if respective uses were found.
The Master Data list contains all occurrences found in the master data and Customizing objects of the consolidation
system, sorted by characteristics and characteristic values.
The list shows whether a use is dependent on the consolidation area, or on the time period or version.
In cases where the current Workbench parameters match the parameters of the use, the system attempts to provide
direct access to the data record. Choose Change to open the data record in change mode.
The Hierarchies list contains all occurrences found in the hierarchies of the consolidation system.
4/20/2019
The system shows each hierarchy name and, if applicable, the version (or special version and version type) and the
period and scal year (starting period/starting year).
The Transaction Data list contains all occurrences found in InfoCubes and ODS objects, in the form of messages.
Choose Messages to display the uses.
The system displays a message for each use. Each message names the InfoCube or ODS object, the data basis, and the
consolidation area in which the use is found.
Activities
To generate a where-used list in the Consolidation Workbench, select a single value and choose Where-Used List in the context
menu.
The system scans the consolidation database and, if applicable, the InfoCubes and ODS objects, and lists all occurrences in the
where-used list. The search can take some time – especially for characteristic values that are used in transaction data.
You can print the list. You can also page through the list if it is lengthy.
Validity of Master Data

Use
You use this function to de ne master data of the consolidation system (SEM-BCS) as time-dependent and version-dependent.
The validity concept for master data supports situations such as the following:
A company has been sold and postings to this company should no longer take place. Or, the consolidation chart of accounts has
been changed and certain items should no longer be posted to. In both cases, you cannot simply delete the single values (the
company or the items) because they were previously posted to.
For planning purposes, you have created a company that should not yet be used in the current consolidation version (for
example, as a partner unit). Or, you have created an item that should only be used for posting from a future period onwards.
Integration
The system adds the following to Customizing for master data when characteristics become time-dependent or version-
dependent:
A list of invalid values that shows the single values that are invalid for the currently set period and/or version. You can also add
invalid values to this list.
You can con gure the Consolidation Workbench to not display the list of invalid values (see the section "Con gure the Display of
Invalid Values).
The system adds the Validity Timeframes tab page to single value maintenance. Here you de ne the timeframes in which a
single value is valid, or for version-dependent characteristics the validity in the currently set version.
In Customizing for special versions, you can de ne that the single values of version-dependent characteristics are valid in the
special version by default (regardless of which version the value is created in).
Features
4/20/2019
On the Authorization/Validity Check tab page in Customizing for the data basis, you can de ne whether each consolidation
characteristic is time-dependent and/or version-dependent.
If a characteristic is time-dependent and/or version-dependent, the system checks the validity of the single values and
processes only those single values that are valid for the permanent parameters ( scal year, posting period, and/or version) of
the current session.
Validity Check Validity
No check (default) The characteristic is not dependent on time or version. The single
values are valid in all versions in all timeframes.
Time-dependent If you add a single value to a hierarchy or create a single value as

an unassigned node, the single value is valid in all timeframes by
default (starting year: ; starting period: ; ending year: 9999; ending
period: 999 ).
If you create a single value as an invalid value, the single value is

invalid in all timeframes by default (starting year: ; starting period:
; ending year: ; ending period: ).
For each single value on the Validity Timeframes tab page, you can
specify the timeframes in which the value is valid.
Version-dependent If you add a single value to a hierarchy or create a single value as

an unassigned node, the single value is valid in the current version.

not valid in the current version.
Irrespective of whether you create valid or invalid values, the single

values are valid in other versions if they are valid in the assigned
special versions by default.
For each single value on the Validity Timeframes tab page you can
de ne that the single value is valid in the current version by
selecting the Valid indicator.
Time-dependent and version-dependent If you add a single value to a hierarchy or create it as a nonassigned
node, the single value is valid in the current version for all
timeframes.

never valid in the current version.
Irrespective of whether you create valid or invalid values, the single

values are valid in other versions if they are valid in the assigned
special versions by default.
For each single value on the Validity Timeframes tab page, you can
restrict the timeframes in which the value is valid in the current
version.
Activities
De ne a Validity Check for a Characteristic
To de ne that a characteristic is time-dependent and/or version-dependent, follow these steps:
In the process view of the Consolidation Workbench, choose Data Model → Data Basis.
Open the required data basis in change mode.
4/20/2019
Choose the tab page Authorization/Validity Check.
For each characteristic, the system lists whether a validity check is performed, and which one is performed.
If desired, change the settings and save your changes.
The new settings are effective immediately.
Con gure the Display of Invalid Values
By default, the system displays a list of the invalid values in Customizing for master data for characteristics that are time-
dependent and/or version-dependent. To change this setting, do the following:
In the Consolidation Workbench menu, choose Edit → Settings, and in the list of settings, choose Workbench → Value List and
Hierarchy Maintenance.
You control the display of the invalid values using the indicators Display List of Invalid Values and Show Both Invalid and Valid
Values.
If neither indicator is selected, the system displays only the valid values.
If only the indicator Display List of Invalid Values is selected, the system also displays the list of invalid values.
If the indicator Show Both Invalid and Valid Values is selected, the system displays the valid and invalid values in a joint list.
Save your changes.
The changes become effective the next time you launch the consolidation workbench.
Display and Change the Validity of a Single Value
There are different ways to display or change the validity of a time-dependent and/or version-dependent single value in
Customizing for master data. Here are some possibilities:
Select a valid or invalid single value and, from the context menu, choose Change. On the Validity Timeframes tab page, you can
explicitly change the settings.
Select an invalid single value and, from the context menu, choose Mark as Valid.
The system then adjusts the settings on the Validity Timeframes tab page accordingly.
Select a valid single value and, from the context menu, choose Mark as Invalid.
The system moves the single value (if applicable) to the list of invalid values (see the section "Con gure the Display of Invalid
Values) and adjusts the settings on the Validity Timeframes tab page accordingly.
Time and Version Dependency of

Hierarchies
Hierarchies of consolidation units are always de ned as version dependent and time dependent.
You can decide whether hierarchies of other characteristics in the consolidation system (SEM–BCS) are dependent on time or
the version (for example, hierarchies for nancial statement items and subassignments).
4/20/2019
The following rules apply when you de ne the dependency on versions and time:
The existence of hierarchies is independent of versions and time periods.
Hierarchies are de ned as version dependent .
The assignments (higher-level nodes lower-level nodes) within a version are time dependent . That is, a starting year
and starting period determine from which point onwards an assignment is valid, and an ending year and ending period
determine up to which point the assignment is valid. The assignment can also be valid in multiple timeframes.
When de ning a hierarchy in SAP NetWeaver Business Intelligence (BI) for a characteristic, you can choose:
Whether hierarchies of this characteristic are version dependent
Whether the entire hierarchy or the hierarchy structure is time dependent
These settings in BI also affect the consolidation system. Hierarchies of consolidation units are the exception: You always de ne
these as time and version dependent – regardless of the settings in BI.
The node assignments in the consolidation system are time dependent (or, more precisely, the edges are time dependent).
 Example
In period 011/200X you have a hierarchy of consolidation units; then in period 012/200X you add the new consolidation unit
CU Z .
In period 012/200X, only the node CG 2 changes, not the entire hierarchy.
4/20/2019
Con guring Time-Dependent Customizing

Settings
Use
You use this procedure to con gure time-dependent Customizing settings, such as the balance carryforward items in the
consolidation function Balance Carryforward .
When making these settings, the changes take effect starting in the scal year and period that are set in the permanent
parameters of the Consolidation Workbench. This has the following effects on the settings already de ned for earlier or later
timeframes:
If settings already exists for an earlier timeframe , the system automatically reduces their validity up to, but excluding,
the time period from which the new setting takes effect.
If settings already exist for later timeframes , the system does not adjust those settings. This can cause parallel settings
in later timeframes, which can lead to unde ned system behavior.
Recommendation
We recommend that you make time-dependent Customizing settings in chronological order only. When you make a
new setting and one or more settings for later timeframes already exist, you need to review the latter settings and
rede ne them if necessary.
See also:
SAP Note 870911
Procedure
General Procedure
To con gure time-dependent Customizing settings, proceed as follows:
1. See if the setting you want to make is indeed time dependent (see the section "Display Time-Dependent Attributes”).
2. If the setting is time dependent, see if settings already exist for later timeframes (see the section "Display Settings of a
Time-Dependent Attribute”).
3. In the permanent parameters of the Consolidation Workbench, set the year and period for which the new setting should
take effect; then make your new setting.
4. If settings for later timeframes already exist, review them and adjust them in chronological order, if necessary.
Display Time-Dependent Attributes
To determine which Customizing settings are time dependent, proceed as follows:
1. Go to the process view of the Consolidation Workbench and choose Data Model Consolidation Area .
2. Select a consolidation area and choose List Field Properties in the context menu.
The system generates a hierarchical list.
4/20/2019
3. In this list, expand the Details: Basic Data and Dependencies section and then expand the characteristics or
consolidation functions of interest.
If time-dependent characteristics or consolidation functions are found, these are listed in the sections Time-Dependent
Attributes and Time and Version-dependent Attributes . If none are found, these sections are not displayed.
Display Settings of a Time-Dependent Attribute
To determine which time-dependent Customizing settings exist, proceed as follows:
1. In the permanent parameters of the Consolidation Workbench, set the year and period from which the change should
take effect.
2. Go to Customizing and display the time-dependent attribute.
The system shows the setting for the time-dependent attribute as per the current year and period.
3. In the permanent parameters of the Consolidation Workbench, systematically proceed with later timeframes to see if,
and when, changes exist for the time-dependent attribute.
Multiple Occurrences of End Nodes in a

Hierarchy
An end node can occur more than once within the same hierarchy if the common, higher-level node of those multiple
occurrences is a nonpostable hierarchy node or the top node of the hierarchy.
This rule applies to all hierarchies except the following:
Hierarchies of consolidation units (these always permit multiple occurrences of end nodes without restriction)
Hierarchies of tasks and data entry layouts (these never permit multiple occurrences).
When you save a hierarchy, the system checks the changes made to the hierarchy. If multiple occurrences of end nodes are not
permitted, the system ignores the changes and issues an error message.
 Example
The following gure shows an example of four item hierarchies in which the end node 111000 occurs more than once.
In hierarchies 1 and 2, the multiple occurrences are permitted because the common higher-level node 100000 (green
checkmark) is a nonpostable hierarchy node.
In hierarchy 3, the multiple occurrences are permitted because the only common higher-level node (green checkmark) is
the top node of the hierarchy.
In hierarchy 4, the multiple occurrences are not permitted because the common higher-level node (red “X”) is a postable
item.

Business Consolidation (SEM-BCS) PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Business Consolidation (SEM-BCS) PDF

Încărcat de

Drepturi de autor:

Formate disponibile

4/20/2019

Business Consolidation (SEM-BCS)

SAP ERP | 6.16.13

For more information, please visit the SAP Help Portal.

Business Consolidation (SEM-BCS)

Consolidation Charts of Accounts

Collection and Standardization of Reported Data

Flexible upload from a data le

Load from an InfoProvider (from the BI system or connected SAP systems)

Copy within the consolidation system

Preparations for consolidation group changes

Elimination of interunit pro t/loss in transferred inventory

Elimination of interunit pro t/loss in transferred assets

You can use XBRL to create individual or consolidated nancial statements.

Execution and Monitoring of the Consolidation Process

Execution of Consolidation with the

is standardized to agree with the group's standard accounting policies

is translated into the currency of the consolidation group

cleansed of eﬀects that are the result of group-internal relationships

Creating an Initial Data Set

B. Execution of Consolidation Tasks

You execute the tasks in the consolidation monitor. There are

Tasks for the collection and preparation of reported nancial data

Tasks for the actual consolidation entries

2. You transfer the reported nancial data of the consolidation units.

3. You validate the reported nancial data.

8. You validate the standardized nancial data.

It provides a central work environment for:

The consolidation units and consolidation groups with their hierarchies

The tasks with their task hierarchies (including task groups)

Swap Characteristic with… Consolidation Group/Consolidation Unit or

Swap Characteristic with… Task/Task Group

Consolidation Unit Hierarchies

The task hierarchy or task sequence you de ned

The permanent parameters you selected

Make sure that:

The task hierarchy is time and version dependent.

You assigned a consolidation frequency to a task in your Customizing settings.

Layout of the Consolidation Monitor

In the hierarchy of the organizational units you can:

With the columns for the task hierarchy, you can:

Partially or completely expand or compress the columns

Manually set or automatically optimize the width

You can set lters to

Display only certain statuses, such as all tasks with errors

Hide the end nodes of a hierarchy

The user layout is not dependent on time or version.

Performing the Tasks

Conditions for Processing Tasks

The following applies when processing the tasks:

Data collection tasks

Manual posting tasks

Tasks that are irrelevant for a consolidation unit

Selection of the Organizational Units

You can run the tasks in the following ways:

Test run ( Test pushbutton)

Update mode ( Post pushbutton)

Update mode with pendent tasks

With selection screen ( Tasks Execute with Selection Screen )

Run successive tasks without stop

Status Management in the Consolidation

Status Display per Organizational Unit

Legend of Symbols for the Status Display