002 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
Data Collection
Purpose
You use this component to collect the following types of data into the consolidation system from SAP systems and non-SAP
systems:
Reported nancial data
Documents
Additional nancial data(AFD)
Master data
Features
You have the following options for collecting data:
Data Collection Repd Fin. Data Documents Addl Fin. Data Master Data
Procedure
Manual Data Entry with X (X) X (X)

data entry layouts
Flexible Upload X X X X
Load from Data Stream X X X X
Copy, Periodic X X X
Delete, Periodic X X X
Copy, Nonperiodic X X X
Delete, Nonperiodic X X X
Remarks:
Manual data entry only allows for:
Adjustments to reported nancial data (documents with posting level 01)
Posting of standardizing entries to (adjusted) reported nancial data (documents with posting level 10)
Creation of master data for capitalization and valuation allowances and elimination of interunit pro t/loss in
transferred assets
Tasks
To periodically run data collection in the Consolidation Monitor , you use either the data collection task or the copy task. You can
execute tasks for a single consolidation unit or for an entire consolidation group.
You can use the data collection task for all data collection procedures. In the Customizing settings for the data collection task,
you assign a data collection method to each organizational unit. You can combine different data collection procedures in a data
collection method.
4/20/2019
You use the copy task only for periodic copying of transaction data. In the Customizing settings for the copy task, you assign a
copy method to each organizational unit.
Different processes are available for integrating transactional SAP applications with the consolidation system .
Manual Data Entry

Purpose
This component enables you to manually enter the following data:
Reported nancialdata
Additional nancialdata
Master data for noncurrent assets (for Capitalization and Valuation Allowances and Elimination of Interunit Pro t/Loss
in Transferred Assets )
Implementation Considerations
Apply this component if you want to manually enter data for one or more consolidation units or for a combination of
consolidation units (for example, combinations of company and pro t center) into the consolidation system.
Whether you deploy manual data entry or a method of automatic data collection depends on the organization of your corporate
group and the systems it uses.
Integration
Manual data entry is linked to status tracking in the consolidation monitor .
Features
Manual data entry has the following features:
You record reported nancial data with the aid of ( exible) data entry layouts into the totals database.
You record additional nancial data and the master data for noncurrent assets with the aid of xed layouts
And you have the option to record data by means of manual posting .
Manual Data Entry of Reported Financial

Data
Use
You use this function to manually record reported nancial data into the consolidation system by means of exible (that is,
freely-de nable) data entry layouts.
Features
4/20/2019
Data entry layout
The data entry layout plays the most prominent role in manual data entry. The data entry layout de nes the user interface you
will later use to manually enter the data.
De nition of data entry layouts for reported nancial data is exible: You can determine whether the structures of the data
entry layout are prede ned and xed, or are dynamically generated according to the transaction data or the master data. You
can use hierarchies of characteristics when de ning a layout.
The layout de nition adheres to the WYSIWYG principle.
All elements of a data entry layout can be reused in other data entry layouts.
Data collection method
When de ning a data collection method , you choose manual data entry and assign a data entry group with one or more data
entry layouts. You assign the data collection method to a consolidation unit. The data entry layout then appears when you run
the data entry task for the consolidation unit.
Periodic and cumulative data entry
For each form, which belongs to a data entry layout, you decide whether the recorded data is period-speci c or cumulative
(year-to-date).
Customizing Settings for Manual Entry of

Reported Financial Data
Purpose
You make the Customizing settings for manual data entry to enable the execution of that activity in the consolidation monitor.
Prerequisites
If you want to be able to enter data on hierarchy nodes, you must have selected the corresponding indicator in the de nition of
version combinations. See also the section Customizing of Versions .
Process Flow
1. De ne a data entry layout within a data entry group.
2. De ne a data collection method and assign a data entry group to that data collection method.
3. De ne a task for manual entry of reported nancial data and assign the data collection method to that task.
Customizing Interface for Manual Data Entry

De nition
A user interface for de ning data entry layouts.
4/20/2019
Use
You use this customizing interface to de ne the objects needed for manual data entry: data entry groups, data entry layouts,
forms, and so forth.
Structure
The customizing interface for manual data entry has the following composition:
Hierarchies with data entry groups and data entry layouts (1)
You can create and display the following objects in the lower left section of the workbench screen:
Hierarchies for data entry groups
Data entry groups for grouping data entry layouts from an accounting perspective (for example, data entry groups for
the balance sheet and others for the income statement)
Data entry layouts
Object tree (2)
The object tree displays the structure of your data entry layout along with:
Form
Row structure
Column layout
4/20/2019
Data entry layout, preview (3)
See the sections that follow.
Data Entry Layout

De nition
A user interface for entering nancial data reported by consolidation units and combinations of consolidation units.
Use
You use data entry layouts for the manual entry of reported nancial data in the Consolidation system. You can de ne and use
different data entry layouts, depending on which type of data and which level of detail is involved.
Structure
This illustration shows the relationships between the objects in manual data entry:
4/20/2019
Form
Each data entry layout has a form. (At present, the form is the same as the data entry layout.)
Once a form has a name, it can be used in other data entry layouts.
A form consists of the following elements:
Header
Row structures
Column layouts
When you create a form, the system automatically creates nodes for the row and column structures in the object tree.
You need these row and column structures to create a data entry grid with data rows and data columns (see the following
illustration).
Header
In the header of the form you can de ne which characteristics should appear when executing manual data entry.
The header is optional when de ning a form. If you do not de ne a header, manual data entry then displays the characteristics
that are permanent parameters and are not used in the data entry layout.
4/20/2019
The header is a selection condition. If a selection condition is de ned for the characteristics you can choose from, you are able
to navigate among the characteristic values.
Row structures (for data rows)
Under a node for a structure, you can perform the following actions:
Create new row or column structures
Allocate existing row and column structures
You establish data rows by de ning the lead columns. Each lead column establishes a set of rows. This set of rows is determined
by selection conditions, which you specify with one or more characteristics.
A form must have at least one lead column along with its row structure.
The following types of row structures are available:
Data-driven structure
Prede ned xed structure
Combined structure
Data-Driven Structure
When you specify a characteristic for a data-driven structure, the system automatically selects all of the characteristic’s
breakdowns.
You de ne the data-driven structure as follows:
You enter one or more characteristics (for example, item).
You specify the selection conditions for these characteristics.
You determine how the characteristic values are listed:
According to master data . (For example, if transaction types 100-999 are speci ed, the system selects the
existing values 100, 120, 140, 200, 220, and 240.)
According to transaction data . The system only selects the values that exist in the records of the totals
database. (For example, if transaction types 100-999 are speci ed, the system only selects 100, 120, 140, and 200
as well as those from the default selection .)
You determine how the subtotals are arranged.
You determine how the characteristic values are presented – text and/or keys.
You decide whether the data for the characteristic values are merely displayed, or whether data can be entered for the
characteristic. Display-only columns are shown directly next to lead column.
You determine how the characteristic values are arranged in the hierarchy. If you select the respective indicator, you can
choose which hierarchy nodes are displayed in the data entry layout.
Prede ned Fixed Structure
You explicitly specify all data rows for this type.
Each data row must have at least one characteristic (for example, a nancial statement item).
4/20/2019
You specify the selection condition for each characteristic (for example, for selecting subassignments).
Combined Structure
This type consists of two or more columns. Each column’s structure can be either prede ned xed, data-driven, or combined.
There are two ways you can portray hierarchies:
You can show each column (contained in the structure) separately as a lead column.
You can show the columns as a combined structure. This means that the characteristics contained herein are combined
in the hierarchy. The rst level of this hierarchy represents the rst column of the combined structure; and the second
level re ects the second column.
The following illustration compares these two presentation methods:
Column structures (for data columns)
You de ne data columns in the same way you de ne data rows:
4/20/2019
You establish the data columns by de ning the lead rows. Each lead row establishes a set of columns. This set of columns is
determined by selection conditions, which you specify with one or more characteristics.
A form must have at least one lead row along with its row structure.
The following types of column structures are available:
Prede ned xed structure
Data-driven structure
Lead rows typically have the prede ned xed structure.
For prede ned xed structures you can choose whether to only display the columns.
Note
Hierarchies cannot be displayed in column structures. Even though you can select the indicator for hierarchies in
customizing, this indicator is disregarded when display data columns. However, the hierarchy is displayed if you reuse the
column structure as a row structure somewhere else.
Formulas
You can create formulas for prede ned xed structures.
 Example
You can use formulas to make annual comparisons. For example, you can have two columns with annual values, and a third
column for the variance, which is computed with a formula.
To de ne a formula you use the Formula Editor , which you also use in validation. All rows and columns from the prede ned
structure are available for selection in the Formula Editor. (However, you cannot use key gures.)
You build the formula by choosing the selections, constants (if applicable), functions, and operators.
You save the formula along with the other objects of the data entry layout.
The Relationship Between Rows and Columns
A data cell (and the value it re ects) is determined by the selection condition of the characteristic. How a characteristic is
selected is determined by all of the following:
The permanent parameters
The selection condition for the data rows.
The selection condition for the data columns
The other characteristic values you need to specify in the header of the data entry layout when running manual data
entry
The consolidation units or groups on which the cursor was placed when the task was started
When you run manual data entry in the consolidation monitor while the cursor is placed on a consolidation group, then
you must specify (in the header of the data entry layout) the consolidation unit for which you want to record the data
(assuming that the system cannot provide the consolidation unit itself – for example, from the permanent parameters).
4/20/2019
Note
When de ning the rows and columns, keep the following in mind: If you have de ned the data rows using a
combination of leading columns, you can use a characteristic in only one of these columns.
Integration
A data entry layout is only valid in the consolidation area you created it in.
Once you have created forms and structures for a data entry layout, you can reuse them in other data entry layouts, as well. A
precondition is that you have given the form or structure a name. You assign a name by placing the cursor in the name column
for the eld at hand. Then you enter the name when the eld is ready for input.
If a change occurs to the breakdowns of items you used in a data entry layout, you may need to adjust the layout accordingly.
To be able to execute a data entry layout, you assign the associated data entry group to a data collection method . And you
assign the data collection method to a task.
Example
See the detailed example of an asset history sheet .
De nition of a Data Entry Layout

Purpose
You use this process to create a data entry layout .
Prerequisites
You have nished customizing your nancial statement items and subassignments.
You have made your preliminary considerations regarding the structure of the data entry layout.
Process Flow
This ow discusses how you rst create a data entry hierarchy, and then create a data entry group and a data entry layout.
Alternatively, you can create a data entry layout rst, and then assign it to a hierarchy and a data entry group later on.
Run the customizing environment for manual data entry by going to the process view in the workbench and choosing
Consolidation Functions Data Collection Manual Data Entry
Go to the lower left section of the screen and create a hierarchy for the data entry groups by choosing Create in the context
menu.
Create a data entry group by choosing Create in the context menu.
4/20/2019
Create a data entry layout by selecting the data entry group and choosing Create in the context menu.
In the work area, assign a name for the data entry layout.
Create a form for the data entry layout by selecting the data entry layout in the object tree of the work area, and choosing
Create in the context menu.
The form can be reused in other layouts if you give it a name.
Use existing row structures by selecting the Row Structure entry, choosing Allocate in the context menu, and selecting an
existing structure.
Alternatively, create one or more new row structures by selecting Row Structure in the object tree of the work area and
choosing one of the following three options in the context menu:
Create Prede ned Fixed Structure
Create Data-Driven Structure
Create Combined Structure
The structure can be reused in other forms if you give it a name.
De ne the structure. (For more details on de ning structures, see

Example: Statement of Changes in Property, Plant, and Equipment .)
If applicable, create a formula for a prede ned xed structure. To do this, proceed as follows:
Select the prede ned xed structure and choose Formula in the context menu.
In the formula editor, choose whether the result of the formula is a monetary amount, a quantity, or a percentage rate.
Create a formula in the formula editor by choosing the selections (that is, the rows of the prede ned xed structure), constants
(if applicable), functions, and operators.
For more information on building formulas, see the documentation on validation, sections Execution of Validations and Example:
Execution of Validation of Reported Financial Data .
To de ne the column structures, proceed as you did for the row structures.
Save your entries.
Result
You can preview the data entry layout by double-clicking the data entry layout in the object tree and going to the Preview tab.
The preview only uses dummy data.
You can reuse the following elements of the data entry layout when de ning other data entry layouts:
Forms
Column layouts
Row structures
4/20/2019
Now you can de ne a Data Collection Method . You assign the data collection method to a task for data entry. You execute the
task in the consolidation monitor.
Example: Statement of Changes in Property,

Plant, and Equipment
Initial Situation
You want to create a data entry layout for a statement of changes in property, plant, and equipment (asset history sheet).
Prerequisites
You have nished customizing your nancial statement items and subassignments.
If applicable, you have created a hierarchy for data entry groups and you have created a data entry group.
Preliminary Considerations
The asset statement should look like this:
You need the following rows:
Fixed asset items
Transaction type for original acquisition cost
Transaction type for accumulated depreciation
Transaction type for book value
You need the following columns:
Opening balance
4/20/2019
Additions
Divestitures
Closing balance
You need the local currency as the key gure in these columns.
Thus, you can create a data entry layout with the following structure:
Object Name
Changes in Property, Plant, and Equipment [data entry layout] Changes in P,P&E
Changes in P, P & E [form] Changes in P,P&E
Row structure
Data-driven Item
Prede ned xed
Column/Row Acq. Cost
Column/Row Acc. Dpr.
Column/Row Book Value
Column structure
Prede ned xed
Column/Row Open.
Column/Row Add.
Column/Row Divest.
Column/Row Close
Prede ned xed
Column/Row LC
Explanations:
The row structure for the xed asset items should be data-driven and be based on the master data of the items.
The remaining row and column structures are prede ned and xed.
Activities
If you already created a data entry group, now de ne a data entry layout for the statement.
Call up the customizing environment for manual data entry by going to the process view in the workbench and choosing
Consolidation Functions → Data Collection → Manual Data Entry .
Create a data entry layout by selecting the data entry group and choosing Create in the context menu.
In the work area in the Name column, assign the nameChanges in Property, Plant, and Equipmentfor the data entry layout.
4/20/2019
Create a form for the data entry layout by selecting the data entry layout in the object tree of the work area, and choosing
Create in the context menu.
The form can be reused in other layouts if you give it a name. Call this formChanges in Property, Plant, and Equipment,as well.
Create the row structures:
Create a data-driven row structure for the xed asset items by selecting the Row Structure entry and choosing Data-driven
Structure in the context menu.
If applicable, assign a name for the structure.
De ne the structure on the Structure tab page.
Select the characteristic Item.
De ne the range of values for xed assets.
List the values according to the master data.
Do not select a hierarchy.
Do not display totals.
Display keys and long texts.
Do not select the indicator for "Display Only".
Sort by keys in ascending order.
Create a prede ned xed row structure by selecting the Row Structure entry and choosing Prede ned Fixed Structure in the
context menu.
Name the structure Transaction Type .
De ne one row each for the acquisition cost, accumulated depreciation, and book value.
When doing this, select the entry Prede ned Fixed and choose Create in the context menu.
Assign the suitable name for each row (Acq. Cost, Acm.Dpr., Book Value).
Do not select the indicator Display Only.
Select the characteristic Transaction Type .
Specify the range of values for each transaction type.
Create the column structures:
Create a prede ned xed structure.
In the structure, create one column each for the opening balance, additions, divestitures, and the closing balance. (Follow the
same steps as for creating the prede ned xed row structures.)
Create another prede ned xed structure.
4/20/2019
Select the characteristic Key Figure and select the single value Periodic Value in Local Currency .
Save your entries.
Result
To preview the results, go to the Preview tab.
You can assign the data entry group that contains the data entry layoutChanges in Property, Plant, and Equipmentto a data
collection method.
In turn, you can assign the data collection method to a data collection task.
You execute the task for each separate consolidation unit in the consolidation monitor.
Execution of Manual Entry of Reported

Financial Data
Purpose
4/20/2019
You use this process to execute manual data entry in the consolidation monitor.
Prerequisites
You have made your customizing settings for manual entry of reported nancial data .
Process Flow
1. Launch the consolidation monitor.
2. Start the data entry task in update mode for one consolidation unit or for one consolidation group.
3. In the overview screen of data collection , choose the data entry layout you want to use for entering the reported data by
choosing the corresponding execution symbol.
4. On the next screen, enter the reported nancial data.
You can create subassignments while entering data in the data entry layout. To do this, choose the Create symbol and
select a subassignment (for example, transaction type). You can also insert new rows .
5. Save the data.
Cells Not Ready for Input in a Data Entry

Layout
Sometimes a cell in a data entry layout is not ready for input.
This can have the following causes:
The relevant structure in the layout is in display mode.
The cell contains a formula.
The cell belongs to a cell representing a hierarchy node with a total value and is therefore not displayed.
A prede ned xed structure contains multiple characteristic values (due to aggregation).
A prede ned xed structure contains nodes, which are not ready for input (also due to aggregation).
The cell re ects an invalid characteristic value.
The breakdown check discovered an error. Some examples are:
Item 1000 has no breakdown by characteristic value 2000.
Item 1000 has a breakdown by characteristic value 2000, but the value of characteristic value 2000 is missing.
Item 1000 has a breakdown by characteristic value 2000, but the default value 3000 of characteristic value 2000
is not permitted.
The characteristic value is not contained in the maximum set.
An item has a required breakdown, but the breakdown is missing in the data entry layout.
The xed values in the breakdown of an item do not appear in the data entry layout.
The values are in con ict with the layout de nition.
4/20/2019
The de nitions of the prede ned xed structures are inconsistent.
The cell belongs to a combination of consolidation units, but that combination is invalid.
Several characteristics for the cell are not restricted to single values.
Several characteristic values are in con ict with the parameters used in the task execution.
A value cannot be entered because the current period is prior to the rst period of data entry.
The currency key does not exist.
The row is a dummy row, which however can be copied.
To see what the cause is (or causes are), call up the context menu for the cell and choose Why is the cell not ready for input?
Inserting a New Row in a Data Entry Layout

Use
You use this procedure to insert new rows in a data entry layout during manual data entry.
Prerequisites
The data entry layout has one or more transaction data-driven structures. (If all structures were master data driven,
then all conceivable cells would already be contained in the layout.)
The transaction data-driven structure must have at least one characteristic designated for data entry.
Procedure
When inserting a new row, rst you copy an existing row and then you overwrite the contents of the new row.
Inserting New Rows in a Nonhierarchical Structure
1. Select the row you want to copy.
2. Choose Copy Row in the application toolbar.
3. In the new row, overwrite the characteristic values with the new values.
4. To check the new row, choose Enter .
5. To add more new rows, repeat steps 1 through 4.
6. To rearrange the rows, choose Assort New Entries in the application toolbar.
Inserting New Rows in a Combined (Hierarchical) Structure
1. Select the row you want to copy.
2. Choose Copy Row in the application toolbar.
3. In the Copy Row dialog box, enter the values for the rows.
4. To check and rearrange the new rows, choose Enter .
4/20/2019
Dummy Row
De nition
This is a row that serves as a placeholder in the data entry layout. The system automatically inserts this row if you have a data-
driven structure based on transaction data and the system is unable to locate the corresponding transaction data.
Use
You can copy the row to insert new transaction data.
Manual Data Entry of Additional Financial

Data
Use
Additional nancial data is required either as an alternative or in addition to the data in the totals database (that is, in addition
to, or instead of, the balance sheet, the income statement, and similar data).
The following table lists which additional nancial data is required for each function:
Function Additional Financial Data
Capitalization and valuation allowances Assets and liabilities
Historical currency translation Investment and equity data
Elimination of interunit pro t and loss in transferred inventory Data concerning the group-internal sales of goods and services:
Inventory data
Supplier data
Supplier share
Elimination of interunit pro t and loss in transferred assets Noncurrent assets
Asset transfers
Asset matching(*)
Consolidation of investments Investments
Equity
Equity holdings adjustments
Goodwill
Goodwill inheritance(*)
Sequence of activities(*)
Activity number matching for investment and equity data(*)
Activity number matching for equity and equity holdings

adjustment data(*)
4/20/2019
*) This is not true additional nancial data, but rather an auxiliary function in manual data entry.
Integration
With validation of additional nancial data you can compare the monetary values of the additional nancial data to the values in
the totals database (when respective totals data exists).
Prerequisites
In the data basis , you have created (or had the system automatically generate) InfoProviders for the data streams to be used
to record additional nancial data (for example, InfoProviders for supplier data, inventory data, supplier shares, investments,
equity, and goodwill).
You have completed all customizing settings for all consolidation functions you will use for recording additional nancial data
(for example, for elimination of interunit pro t/loss in transferred inventory and for consolidation of investments).
Features
For the functions listed above, you can manually enter the respective additional nancial data using xed data entry layouts.
You need to enter the additional nancial data directly after you have entered the reported nancial data.
You execute the task for entering additional nancial data in the Consolidation Monitor (along with the other data entry tasks).
You can collect additional nancial data for a single consolidation unit or for an entire consolidation group. Since goodwill is
group-dependent, you run goodwill entry for a consolidation group.
Activities
A. Customizing Manual Entry of Additional Financial Data
De ning a Data Collection Method
In a data collection method you specify which additional nancial data you want to record with the data entry task.
In the process view of the workbench, choose Consolidation Functions Data Collection Data Collection Method . Choose Display
in the context menu.
In the lower left area of the workbench, create a new data collection method or change an existing one.
On the screen of data collection methods, specify which additional nancial data is to be recorded:
Choose the Insert symbol to add a new row to the table.
Choose a data stream for the additional nancial data (for example, for inventory data and supplier data).
Choose Manual Data Entry as the data collection procedure for these data streams.
Save the data collection method.
See also Data Collection Method .
De ning a Task
4/20/2019
In the process view of the workbench, choose Consolidation Functions Data Collection Task . Choose Display in the context
menu.
In the lower left area of the workbench, create a new task or change an existing one.
Specify the required data on the task screen. When doing this, go to the Assign Methods group box and choose the existing data
collection method that provides for entry of additional nancial data.
Save the task.
See also:
Task
Task Sequence
B. Entry of Additional Financial Data
Run the Consolidation Monitor.
Execute (in update mode) the task for entering additional nancial data either for one consolidation unit or one consolidation
group.
On the data entry overview screen, choose which additional nancial data you want to enter (for example, supplier data). Then
choose the Execute symbol.
Now, proceed as described in the following sections that discuss each type of additional nancial data.
You can also enter comments for additional nancial data .
Entering Inventory Data

Use
You follow this procedure to enter the inventory data required for the elimination of interunit pro t/loss in inventory (IPI) .
Alternatively, the system can read inventory data from the totals data. This saves the effort of entering the inventory data as
additional reporting data as well as the validation. For more information, see Location of Inventory Data .
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for inventory data.
Procedure
1. Start manual data entry of additional nancial data using the dedicated task in the Consolidation Monitor.
2. In the overview screen , choose the Execute symbol under Additional Financial Data for manual entry of inventory data.
4/20/2019
3. The navigation screen lists the product groups by consolidation unit or combination thereof (if data records exist for
those product groups).
If there is more than one inventory data record for a product group, the hierarchy shows the product group as a
node, and the data records as end nodes below that product group.
If there is only one inventory data record for a product group and no partner unit has been speci ed, this data
record is listed as an end node on the product group level.
4. You can create or change entries for a consolidation unit (or combination thereof) or for a product group.
To create a new entry, double-click the consolidation unit or product group, or choose the corresponding item in the
context menu.
5. Enter the necessary data for a supplier relationship (that is, for a consolidation unit and its partner unit).
For more information, see also the eld help and the section Additional Financial Data .
Note
The entry of the supplying consolidation unit (that is, the partner unit) is optional if you use posting level 30 in the
elimination of interunit pro t/loss in transferred inventory, or if you have set up a data stream for the supplier
shares.
If you do not specify a supplying consolidation unit, the system determines it from the supplier share data record.
If you specify a supplying consolidation unit, this means that this unit supplies 100% of the inventory.
6. Save your entries.
To add more entries, repeat steps 3 through 6.
Result
After the data has been entered, you can verify its consistency with the Validation of Additional Financial Data function.
Entering Supplier Data

Use
You use this procedure to enter supplier data. This additional nancial data is needed for elimination of interunit pro t/loss in
transferred inventory .
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for supplier data.
Procedure
2. In the overview screen , choose the Execute symbol under Additional Financial Data for manual entry of supplier data.
4/20/2019
4. You can create or change entries for a consolidation unit (or combination thereof) or for a product group.
context menu.
Entry of the inventory-managing unit is optional. If you do not specify it, the system uses the data record for all inventory-
managing units that explicitly have not been speci ed.
Note
Supplier data is not validated.
Entering Supplier Shares

Use
You use this procedure to enter supplier shares. This additional nancial data is needed for elimination of interunit pro t/loss in
transferred inventory with posting level 30, which uses supply chains .
You do not need to enter supplier shares if your elimination of interunit pro t/loss in transferred inventory processes two-sided
supplier relationships only and therefore posts entries with posting level 20.
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for supplier shares.
Procedure
2. In the overview screen , choose the Execute symbol under Additional Financial Data for manual entry of supplier shares.
4. You can create or change supplier shares for a consolidation unit (or combination thereof) or for a product group.
context menu.
If you enter supplier shares for a consolidation unit, the consolidation unit is recorded in the supplier share data
record.
If you enter supplier shares for a product group, both the consolidation unit and the product group are recorded in
the supplier share data record.
4/20/2019
If desired, enter a comment .
The current year and period are stored as the starting year and starting period.
Note
Changes to existing data records in a subsequent period is the same as creating a new data record the takes effect in that
period. (This accommodates the system’s starting date logic.)
Result
You can list the supplier shares. To do this, in the process view of the Consolidation Workbench choose Analysis List Data and
run the report by double-clicking the supplier share entry. In the selection screen that appears, make any restrictions to the
characteristic values and execute the report.
The validation of additional nancial data checks that the sum of supplier shares does not exceed 100% for each combination of
consolidation unit and product group.
Entering Investment Data

Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for investment data.
In the customizing settings for consolidation of investments, you have speci ed (under Location of Values on the General tab
page) that you want the system to read investment data from the additional nancial data.
Procedure
Launch the consolidation monitor.
group.
In the data entry overview screen, choose which additional nancial data you want to enter (in this case, investment data) by
You see a navigation screen that lists all consolidation units for which you can enter investment data.
You can either change investment data for existing activities, or enter investment data for a new activity.
To change investment data for an existing activity, choose the activity for the desired consolidation unit (or combination of
consolidation units).
To create a new activity, right-click a consolidation unit (or combination of consolidation units) and choose Create Activity in the
context menu. Then select the type of activity (for example, rst consolidation ).
The Additional Fin. Data: Investment screen appears.
4/20/2019
Enter the required data for the investee unit on the Additional Fin. Data: Investment screen.
If you have activated goodwill in local currency in the consolidation area settings, you also need to specify the investment book
value in local currency.
If you have activated organizational change in the consolidation area settings, and you are entering a partial or total transfer,
you can activate logic for organizational changes in this activity by selecting the Organizational Change indicator. You can
specify the location of the sender data by also specifying an organizational change number. (See the section
Organizational Change Number .)
To enter details for a consolidation unit, either double-click the consolidation unit on the Overview tab page, or select the
consolidation unit and choose the Details tab page.
You can enter a comment for the investment data on the Comment tab page.
Save the data.
Repeat the same procedure for other consolidation units.
When you enter investment data and equity data separately, the system assigns different activity numbers for each type of
data. After data entry, you need to run Matching of Activity Numbers .
As an alternative, you can enter investment and equity data in combined entry . Combined entry automatically assigns a single
activity number for each pair of investment and equity data records.
Entering Equity Data

Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for equity data.
In the customizing settings for consolidation of investments, you have chosen one of the following options (located under
Location of Values on the General tab page):
Read Equity Data from Additional Financial Data
Read Equity Data from Totals Database and Additional Financial Data
Procedure
group.
In the data entry overview screen, choose which additional nancial data you want to enter (in this case, equity data) by
You see a navigation screen that lists all consolidation units for which you can enter equity data.
4/20/2019
You can either change equity data for existing activities, or enter equity data for a new activity.
To change equity data for an existing activity, choose the activity for the desired consolidation unit (or combination of
The Additional Fin. Data: Equity screen appears.
Enter the required data for the investee unit on the Additional Fin. Data: Equity screen.
To enter details for a consolidation unit, either double-click the consolidation unit on the Overview tab page, or select the
consolidation unit and choose the Details tab page.
You can enter a comment for the equity data on the Comment tab page.
Save the data.
Repeat the same procedure for other consolidation units.
When you enter investment data and equity data separately, the system assigns different activity numbers for each type of
data. After data entry, you need to run Matching of Activity Numbers .
As an alternative, you can enter investment and equity data in combined entry . Combined entry automatically assigns a single
activity number for each pair of investment and equity data records.
Entering Investment and Equity Data in

Combined Entry
Use
This procedure describes how to use the combined entry function to enter investment and equity data on a single screen. You
can do this for the activities First Consolidation , Increase in Capitalization, and Reduction in Capitalization . (This feature was
formerly known as integrated entry .) Combined entry automatically generates a single activity number for each pair of
investment and equity data records.
If you instead enter investment data and equity data separately, the system assigns different activity numbers. You then need
to run matching of activity numbers afterwards.
Prerequisites
You have enabled combined entry by selecting the Combined Entry of Investment/Equity Data option in the process view of the
workbench at Consolidation Functions Consolidation of Investments Settings Activities .
For other prerequisites, see the sections:
Entering Investment Data
4/20/2019
Entering Equity Data
Procedure
Use the same procedure as described for the separate entry of investment data or equity data .
Entering Equity Holdings Adjustment Data

Use
You can enter additional nancial data for equity holdings adjustments to adjust the investment valuations of consolidation
units that are consolidated using the equitymethod.
Alternatively, you can read equity holdings adjustment data from reported equity data .
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for equity holdings adjustments
You have assigned the equity method accounting technique to each of the consolidation units concerned. (You do this in
the process view of the workbench under Master Data Consolidation Units Accounting Techniques .)
You have activated the equity method in Customizing for consolidation of investments under System Utilization .
You have determined that equity holdings adjustment data is read from additional nancial data. (This is done in C/I
Customizing under Location of Values . In the process view of the workbench, choose Consolidation
Functions Consolidation of Investments Settings Location of Values, and go to the General tab page.)
On the Equity Holdings Adjustments tab page, you have speci ed the items and subassignments needed for reporting
equity holdings adjustments.
Procedure
1. First, follow the procedure described for the entry of investment data or equity data .
2. Now, enter the data for each scope of reported data.
Note
If the equity method is used and you perform a step acquisition at a later date, the system will calculate a new
goodwill entry. In this case, a background process writes a new equity entry in the table of additional nancial data as
an aid for the correct calculation of goodwill.
Entering Goodwill Data

Use
Typically, the system automatically computes and amortizes goodwill. Consolidation of investments automatically writes these
goodwill entries to the additional nancial data table.
You can also add manual goodwill entries to the additional nancial data. Manual goodwill entries are also amortized
automatically by the system.
4/20/2019
The entry of manual goodwill is particularly useful for legacy data transfers .
See also the section Goodwill .
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for goodwill.
If you want to use the goodwill in local currency feature, you will have activated the feature in the settings for the
consolidation area .
Procedure
In contrast to the additional nancial data for investments, equity, and equity holdings adjustments, goodwill entries explicitly
contain the consolidation group. This means that a goodwill entry is only valid in the one consolidation group it is associated
with.
Therefore, execute (in update mode) the task for entering additional nancial data for a speci c consolidation group.
In the data entry overview screen, choose which additional nancial data you want to enter (in this case, goodwill) by choosing
the corresponding execution symbol.
You see a navigation screen that lists all consolidation units for which you can enter goodwill data.
You can either change goodwill data for existing activities, or enter goodwill data for a new activity.
To change goodwill data for an existing activity, choose the activity for the desired consolidation unit (or combination of
The Additional Fin. Data: Goodwill screen appears.
Enter the required data on the Additional Fin. Data: Goodwill screen.
If you have activated goodwill in local currency for the consolidation area, additional input elds appear on the screen. However,
to remove these additional elds for a speci c goodwill entry, you can deselect Carried in Local Currency and choose Continue .
You can enter a comment for the goodwill data, if desired.
Save the data.
Repeat the same procedure for other consolidation units (or combinations of consolidation units).
Goodwill Inheritance
Use
You use goodwill inheritance to copy manual goodwill entries upwards in the hierarchy of consolidation groups – that is, from
lower-level consolidation groups to higher-level consolidation groups.
4/20/2019
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for goodwill.
Features
Postings at posting level 30 generally apply internal logic called delta logic . When delta logic is used, all documents and totals
records that are posted at a lower level in the hierarchy of consolidation groups also apply to the higher levels of the hierarchy.
At the higher levels, the system merely posts delta entries . The delta is the difference between (a) the (hypothetical) total
document that would normally be posted for the given consolidation group if no lower-level groups existed, and (b) the (actual)
documents posted for the lower-level groups.
In contrast to documents and totals records, InfoProviders have no delta logic for goodwill entries. In cases where consolidation
of investments computes goodwill for an investee unit and its upper unit, and this pair of units belongs to two different
consolidation groups that are located over each other in the hierarchy, the system writes two goodwill entries to the
InfoProvider. The reason for this is that goodwill entries also contain data about the consolidation group. (This is not the case in
investment or equity data.) In general, the system automatically creates a separate goodwill entry for each consolidation group
involved.
However, there are two exceptions: extraordinary amortization of goodwill and manual goodwill entries. These only apply to the
consolidation group in which the entry for extraordinary amortization or manual goodwill is created.
In many cases you want the goodwill entries you create or change to be identical in all of the consolidation groups involved.
When you use goodwill inheritance, you only need to enter manual goodwill once.
Goodwill inheritance depends on how treatment for acquisitions is set: When group shares (as opposed to direct shares) are
used to calculate acquisitions, it does not suffice to merely copy the goodwill entries from the lower-level consolidation groups
to the higher-level groups. Instead, the goodwill entries must be adjusted to the group share of the upper unit in each individual
consolidation group. The system accesses the investment data to obtain these group shares.
Activities
To perform goodwill inheritance, proceed as follows:
2. In contrast to the additional nancial data for investments, equity, and equity holdings adjustments, goodwill entries
explicitly contain the consolidation group. This means that a goodwill entry is only valid in the one consolidation group it
is associated with.
Therefore, execute (in update mode) the task for entering additional nancial data for a speci c consolidation group.
3. In the data entry overview screen, choose which additional nancial data you want to enter (in this case, goodwill
inheritance) by choosing the corresponding execution symbol.
4. On the User Restrictions for Task: <task> screen, specify the organizational units for which goodwill is to be inherited.
5. Also specify whether to overwrite any data that already exists in the higher-level consolidation groups.
6. Choose Execute .
The system lists all goodwill entries.
7. To save the new goodwill entries, choose Save . Otherwise, choose Cancel .
Changing the Sequence of Activities

4/20/2019
Use
The sequence of activities is derived from the sequence you set up in the customizing settings for consolidation of investments
at Settings Activities
When necessary, you can manually change this sequence as described below.
See also:
For general information on activities, see the section Activities .
For information on the customizing settings for activities (including the de nition of the sequence of activities), see the other
section titled Activities .
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for the sequence of activities.
In a data collection method , you have chosen the Sequence of Activities data stream with the data collection procedure
Manual Data Entry .
You have created multiple activities that are triggered by totals data or additional nancial data, and now you want to change
the sequence of those activities.
Procedure
Start the data entry task in update mode for one consolidation unit or one consolidation group.
In the data entry overview screen, choose an entry for changing the sequence of activities by choosing its respective execution
symbol.
The Additional Financial Data: Sequence of Activities screen appears with the activities, the sequence of which you want to
change.
To determine the new sequence:
Select the activity you want to move. (The sequence of activities is shown in the sequence number column.)
Choose Move Activities .
If you choose Default Sequence , the system restores the sequence that is derived from the customizing settings for
consolidation of investments (at Settings Activities ) and from the hierarchy structure of the organizational units.
Save the new sequence of activities.
Matching Activity Numbers

4/20/2019
Use
When additional nancial data is entered separately for investment data and investee equity data, the two types of data end up
with different activity numbers even though they belong to the same activity.
You should match activity numbers in the following cases:
If both of the following conditions are given when entering investment and investee equity data:
The activity involved is rst consolidation, increase in capitalization, or reduction in capitalization.
Multiple activity numbers exist for an activity with a given combination of year/period/activity/investee unit.
If both of the following conditions are given when entering investee equity and equity holdings adjustment data:
The activity involved is subsequent consolidation.
Multiple activity numbers exist for an activity with a given combination of year/period/activity/consolidation unit.
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for investment data and equity data or for equity data
and equity holdings adjustments.
Activity Number Matching for Investment and Investee Equity Data
You have chosen the following location of values (in the process view of the workbench under Consolidation
Functions Consolidation of Investments Settings Location of Values ):
For investment data: additional nancial data
For investee equity data: additional nancial data or totals database and additional nancial data
In the data collection method, you have chosen the data streams for investment and investee equity data.
Activity Number Matching for Investee Equity and Equity Holdings Adjustments Data
You have chosen the following location of values (in the workbench):
For investee equity data: additional nancial data or totals database and additional nancial data
For equity holdings adjustment data: additional nancial data
In the data collection method, you have chosen the data streams for investee equity and equity holdings adjustment
data.
Procedure
2. Start the data entry task in update mode for one consolidation unit or one consolidation group.
3. In the data entry overview screen, choose an entry for matching activity numbers by choosing its respective execution
symbol.
The activity numbers are displayed for each activity on the Additional Financial Data: Activity Number Matching screen.
(For example, different activity numbers may be listed for investment data and equity data.)
4. Select the activity numbers to be matched and choose Save .
4/20/2019
Result
Now each activity has unique activity numbers for investment and equity data or for equity and equity holdings adjustment
data. The result of activity number matching appears in a log.
Entering Assets/Liabilities
Use
You use this procedure to enter assets and liabilities. This master data and additional nancial data is needed for the
Capitalization and Valuation Allowances process.
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for assets/liabilities.
Procedure
2. In the overview screen of data collection , choose the Execute symbol under Additional Financial Data for assets and
liabilities.
3. The navigation screen lists the master data and additional nancial data you have entered for each consolidation unit.
The symbol indicates that you have entered both the master data and the additional nancial data. The symbol
indicates that you have entered only the master data, but no additional nancial data.
If master data already exists, you enter the additional nancial data by placing the cursor on the corresponding
asset and choosing Create in the context menu. Likewise, the same applies when only additional nancial data
has been entered.
To create a new entry, place the cursor on a consolidation unit and choose Create in the context menu.
4. Enter the data as required.
5. Save the data.
Entering Asset Transfers

Use
You use this procedure to enter asset transfers. The associated master data and additional nancial data is needed for
Elimination of Interunit Pro t/Loss in Transferred Assets .
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for noncurrent assets and asset transfers.
Procedure
4/20/2019
2. In the overview screen of data collection , choose the Asset Transfer entry.
3. The navigation screen lists the asset sales and purchases you have entered for each consolidation unit.
To create a new entry, double-click on Sales at the selling consolidation unit. (Do likewise for purchases.)
4. Enter the data as required, which includes master data (such as the consolidation unit and the useful life of the asset)
and additional nancial data (such as the original cost).
To a certain degree, your entries can be incomplete. For example, the seller can omit the buyer’s name of the asset.
Depending on the type of asset transfer, certain elds need to be entered and other elds need to be blank:
Transfer:
Selling consolidation unit: <required>
Buying consolidation unit: <required>
Self-constructed asset:
Asset sold: <blank>
Buying consolidation unit: <required>
Sale to third party:
Asset sold: <required>
Buying consolidation unit: <blank>
Asset bought: <blank>
Note
If your user has authorization for the data entry for the buying consolidation unit (“buyer”) but not for the selling
consolidation unit (“seller”), the original cost and depreciation elds of the selling unit do not appear on the screen.
Similarly, if you have no authorization for the buying unit, the respective elds for the buying unit do not appear on
the screen.
5. Save the data.
Result
After the data has been entered, you can verify its consistency with the Validation of Additional Financial Data function.
Matching Assets
Use
You use this procedure in combination with Elimination of Interunit Pro t/Loss in Transferred Assets in the following scenario:
4/20/2019
The seller and the buyer separately enter the master data and the additional nancial data (for example, using manual entry or
exible uploads). This results in two incomplete data records for the same asset transfer, and the system has no link
whatsoever between these two records.
Prerequisites
In the data basis , you have (or the system has) created the InfoProvider for noncurrent assets and asset transfers.
Procedure
Follow these steps to link the data records using asset matching:
2. In the overview screen of data collection , choose the Asset Matching entry.
3. The system lists all incomplete asset transfers. Potential matches are grouped together and their matching indicator is
selected. (Matching assets are those where the revenue equals the original cost of the buyer less the incidental costs of
the buyer.)
Such “matches” are merely proposed by the system. You can change the matches by deselecting the indicator.
To go to the detail screen of the record, highlight the name of the asset and choose Change in the context menu.
4. Select all of the records you deem as being matched; then choose Save .
5. The system performs a consistency check. (For example, this checks whether the revenue is equal to zero or equal to the
original cost of the buyer less the incidental costs of the buyer.) If the system discovers inconsistencies, the link between
the two data records cannot be saved.
6. Where applicable, correct any faulty data records and save again.
7. Repeat the same procedure for other pairs of data records.
Online Data Entry with Interactive Excel

Use
You can use Interactive Excel for data entry within a subsidiary in different scenarios. Each scenario is determined by decisions
taken within a subsidiary concerning the technical organization and procedures for data entry.
Prerequisites
You have installed Microsoft Excel 2010 or later and SAP Interactive Excel, version 3.0.
You have set up a connection to an SAP ERP backend system on which Enterprise Controlling Consolidation (EC-CS) or
Business Consolidation (SEM-BCS) is installed.
The source database in the backend system for report data is accessed through your local area network. Therefore, you
must have access to the appropriate database tables.
Features
You can connect Interactive Excel to a database by logging on to an SAP system.
4/20/2019
For information, see Interactive Database Connection.
You can make different formatting settings and general de nitions for your work with Interactive Excel.
For information, see Interactive Excel Settings.
You can create a data matrix as a data entry form or report and used the data matrix to enter nancial data in the
consolidation backend system.
For information, see Data Matrix.
You can export nancial data entered in a data matrix into a backend system.
For information, see Saving of Financial Data to a Database.
You can view important information about the status and the origin of data in a data matrix, a pivot table, or an individual
cell on a worksheet.
For information, see Information about the Origin of Data.
As a security measure or for test or presentation purposes, you can create a copy of a worksheet or a workbook.
For information, see Creating a Snapshot of a Worksheet or Workbook.
After the completion of data entry in Interactive Excel, you can continue processing the data in the SAP system. In
particular, you can perform consolidation tasks that use the reported nancial data maintained in Interactive Excel as
input data.
Scenario Example
1. You must assign the Interactive Excel data collection procedure to the data collection method that you assign to one
data collection task for the consolidation units, for example, companies, which will enter their reported nancial data by
using Interactive Excel.
2. A subsidiary creates its own data entry matrices in Interactive Excel based on the master data and the control
parameters in the consolidation backend system. It may also run a preparation for data entry for the matrices.
3. The subsidiary enters its nancial data in the matrices and saves the data to the totals InfoCube of Business
Consolidation (SEM-BCS) or to the totals database table of Enterprise Controlling Consolidation (EC-CS).
Note
The parent company does one of the following:
Allows its subsidiaries to de ne their own matrices
Creates templates for matrices centrally and distributes them to its subsidiaries
More Information
Interactive Excel
Reporting with Interactive Excel
Quick Guide to Using Interactive Excel

Use
4/20/2019
You can use Interactive Excel to enter reported nancial data to the backend consolidation component. You can also read the
backend data and display it in Microsoft Excel spreadsheet.
Prerequisites
You have installed Interactive Excel and have set up a connection to an SAP ERP backend system on which Enterprise
Controlling Consolidation (EC-CS) or Business Consolidation (SEM-BCS) is installed.
For information about connection Interactive Excel to a database of an SAP system, see Interactive Database
Connection.
For EC-CS only: You can also connect Interactive Excel to an offline data entry database in Microsoft Access.
For information, see Data Entry with MS Access.
Activities
Logging On to a System
De ning Global Parameters (Optional)
Reporting
Posting Data
Opening a New Workbook with Interactive

Excel
Prerequisites
Note
If you have enabled the Interactive Excel add-in, the SAP Interactive Excel tab is automatically added to the ribbon. You can
use this tab to log on to a database connected to an SAP system.
For more information about logging on to a database, see Interactive Database Connection.
Procedure
1. Open Microsoft Excel.
2. Enable macros.
3. On the SAP Interactive Excel tab, click Log On
4. Log on to the backend consolidation system.
For information, see Logging On to a System.
Next Steps
4/20/2019
Interactive Database Connection

Use
You connect Interactive Excel to a database by logging on to an SAP system.
Prerequisites
You have set up a connection to an SAP ERP backend system on which Enterprise Controlling Consolidation (EC-CS) or
Business Consolidation (SEM-BCS) is installed.
The source database in the backend system for report data is accessed through your local area network. Therefore, you
must have access to the appropriate database tables.
Features
Simple Connection of Interactive Excel to a Database
You connect Interactive Excel to a database by logging on to an SAP system from the SAP Interactive Excel tab in Microsoft
Excel.
1. Open an empty le or prede ned a le that you created using the Interactive Excel add-in.
2. Open the delivered template (SAPExcelWorkbook.xltm) or another le that was created by using Interactive Excel
earlier.
3. Click SAP Interactive Excel Log On .
4. In the SAP Logon dialog box, log on to the Business Consolidation (SEM-BCS) or Enterprise Controlling Consolidation
(EC-CS) system.
Interactive Excel is connected to the database and the Data Matrix tab is added to standard Microsoft Excel ribbon.
Additional functions are available on the SAP Interactive Excel tab.
Note
You can connect a workbook to only one database in the backend system at a time.
Communication Between Interactive Excel and the Database
Data can be transferred between Interactive Excel and a database as follows:
You can save data entered in an Interactive Excel form to a totals InfoCube for SEM-BCS in SAP Business Warehouse or
to a totals database table in an EC-CS system.
You can import data from a totals InfoCube for SEM-BCS in SAP Business Warehouse or from a totals database table for
EC-CS into an Interactive Excel report.
You can use the master data and control parameters stored in the database as value proposals when de ning data entry
forms and reports.
Loading of Interface Texts for Interactive Excel
4/20/2019
The language that you specify when logging on to the SAP system determines the language that appears on the user interface
of Interactive Excel.
Interactive Excel Settings

Use
You can make different formatting settings and general de nitions for your work with Interactive Excel.
Features
Formats for Hierarchies
You can change the color of the individual levels and their indent level. Your settings are saved locally on your computer.
Formats for Matrix Cells
You can de ne different formats for the following cells:
Locked cells (cannot be used for data entry, for example, totals items or invalid characteristics)
Cells that can be used for data entry
Output cells in reports (into which data is imported)
These settings are applied to the entire workbook.
If you choose Change for the relevant cells, a standard Microsoft Excel dialog box opens. In this dialog box, you de ne the
formats that you want to use.
The default format template for Interactive Excel is applied and should be sufficient for your needs. However, you can choose a
different template if required.
Settings
Shortcut Key for Possible Entries
When you insert a single value or set aggregation into a cell, a possible entries function is applied to the cell. You can use the
button to the right of the cell to display a list of possible values.
The default key combination for this function is STRG + h . If required, you can set a different key combination.
Only read the values manually
Interactive Excel reads changed matrix data from the SAP system by default. Choose this setting if you want to prevent data
from being automatically updated, for example, if you want to create varied valuations on the basis of data from a key date.
If you activate this option, only manual update is allowed and every time you log on to Interactive Excel, a system message
prompts you that the automatic update feature is deactivated.
De ne Font
You can change the font of user interface texts, such as the texts displayed in Interactive Excel dialog boxes.
4/20/2019
You can choose either a xed-width font or a proportional font, for which further options are available. You can also display
sample texts.
Global Settings
You can display and change the global parameters that you work with in the SAP system.
Default Settings
You can use the SAP defaults function to restore the standard settings for Interactive Excel.
Activities
You can make your settings by clicking SAP Interactive Excel Settings .
SAP Interactive Excel Converter

Use
Interactive Excel, version 3.0 replaces version 2.1, which was delivered as part of SAP GUI (up to SAP GUI 7.30). Version 2.1 could
be used for reporting and posting of ERP data. Versions 2.1 and 3.0 store data in different formats; therefore, a conversion tool
for converting existing les from version 2.1 to version 3.0 is available.
Prerequisites
You have used SAP Interactive Excel version 2.1 and you want to convert existing workbooks to the new format.
Features
The converter (SAPExcelWorkbookConverter.exe) is located in the installation folder of SAP Interactive Excel 3.0.
You can select single workbook les for conversion or a folder to convert all les in the folder.
You can specify the target folder where you want to save converted les.
Caution
If a source le is locked, an error is displayed and conversion is not possible.
Activities
You open the converter from the Windows Start menu by selecting All Programs SAP Front End SAP Interactive Excel
Converter .
You can de ne that log les are created in Settings.
Data Matrix
De nition
4/20/2019
User-de ned table in Interactive Excel that can function either as a data entry form or as a report.
Use
You can use data matrices for:
Data entry
Enter nancial data in the consolidation backend system
The parent in a consolidation group usually decides whether it will de ne the data entry matrices for all subsidiaries
using Interactive Excel or whether it will allow the subsidiaries to de ne their own matrices.
For more information, see Online Data Entry with Interactive Excel.
Reporting
Report on the basis of current nancial data in an SAP system
For more information, see Reporting with Interactive Excel.
Structure
Note
If you have created a complex matrix and want to identify the various elements in the matrix de nition, you can click SAP
Interactive Excel Origin of data Active matrix Matrix de nition .
This function marks the row and column layout and the header data on a worksheet.
A data matrix consists of the following elements:
Header Data
Characteristics are valid for a data matrix as a whole and appear outside the row and column layout of the matrix. Single values
(for example, scal year or version) or set aggregations (represented as Single Selections in the Business Consolidation (SEM-
BCS) component) can be used for these characteristics. Each characteristic value that is de ned as header data lls exactly one
cell. The values that you select are inserted in the worksheet in a block, but you can subsequently move them to a different
position.
Constants
Characteristics are xed for a matrix as a whole. You specify these characteristics during matrix de nition, after which they are
hidden in the matrix and can no longer be selected during further de nition.
Data Matrix Layout
Column Layout
Multiple values or set aggregations for a characteristic, which extend across several columns. A column layout in a matrix can
consist of several rows. You do not necessarily have to position these rows directly beneath each other.
For more information, see De nition of a Column and Row Layout.
Row Layout
4/20/2019
Multiple values or set aggregations for a characteristic, or one or more hierarchies, which extend across several rows. A row
layout in a matrix can consist of several columns. You do not necessarily have to position these columns directly beside each
other.
For more information, see De nition of a Column and Row Layout.
User-De ned Entries
Empty rows or columns are inserted into a column/row layout, that is, where no characteristics are speci ed for a whole
column/row. In reporting, you can use these cells for your own functions, for example, you can use an Excel formula.
Data Area
Area directly adjacent to the row and column layouts, in which nancial data is entered or reported data is displayed.
Caution
Interactive Excel must be able to identify the row and column layout before it can identify a data area. The program cannot
distinguish a layout that only covers one row/column from header data and, therefore cannot identify it as a row/column
layout. If your layout cannot be identi ed, a message appears prompting you to indicate the data area explicitly.
Creation of a Data Matrix

Use
You can create a new data matrix as a data entry form or report by de ning the settings that are valid for the whole matrix. You
can create more than one matrix in a single worksheet. For an example of how to create a data matrix, see Data
Reporting/Data Entry Matrix.
Prerequisites
You have created an Interactive Excel workbook based on the delivered SAPExcelWorkbook.xltm template.
If you want to use master data and control parameters from the target or source environment, that is, the consolidation
area in Business Consolidation (SEM-BCS), as proposals for the de nition of characteristic values, you must log on to the
appropriate SAP system.
Note
You can de ne a matrix without using proposals originating from that existing master data and control parameters.
However, you must specify additional de nitions; therefore, this manual procedure is more complex.
You have selected an aspect for the matrix.
An aspect determines the source or target environment for the matrix data. In the context of Business Consolidation
(SEM-BCS), this means the consolidation area from which you want to import data into reports (source environment) or
the consolidation area to which you want to store the data entered in the data matrix (target environment), and whose
master data and control parameters you want to use for the matrix de nition.
If Enterprise Controlling Consolidation (EC-CS) is used as the backend system, the CS aspect is always used.
Note
You cannot change an aspect after it has been selected for a matrix.
4/20/2019
Your selected aspect is used as the default for further matrices, which you process with Interactive Excel, until you
change the aspect.
Process
1. You create an initial matrix.
To do this, click Data Matrix New .
2. You specify the global settings.
For information, see, Making Global Settings for a New Data Matrix.
3. You specify global characteristic values.
You can specify single values or set aggregations as characteristic values for a matrix header. To do this, you can
use master data and control parameters in the source/target environment (that is, the consolidation area) as
proposals.
If a characteristic value is valid for an entire matrix, you can mark it as a constant. The value is set in the
background, and the characteristic is no longer available for de nition, thereby reducing the number of
characteristics that are listed.
You can nd out which characteristics are set as a constant and undo this setting at any time. For more
information, see Making Global Settings for a New Data Matrix.
If a particular characteristic is irrelevant for your matrix, you can mark it as a constant without assigning a value.
It will then be inactive and no longer offered for selection.
If you subsequently change a characteristic value in a report matrix when Interactive Excel is connected to a
database, the matrix is automatically refreshed with the appropriate database data.
4. You create further matrices.
You create further matrices in the same way as you create the initial matrix. When you create further matrices, the
global characteristic values set for the initial matrix are automatically proposed for the header data of the new matrix.
This minimizes the effort required for de ning two or more matrices with similar or identical header data.
You select the values that you want to copy. A value is selected when the eld to its left is selected. After you con rm
your selections, a dialog box opens where you de ne other global settings.
Debit/Credit Sign Logic

Use
The logic that you de ne when you create a data matrix determines the debit and credit signing used for entering data or for
displaying data that is imported from the totals InfoCube.
The following table gives an overview of the sign logic that is supported.
Debit/credit sign logic Description
4/20/2019
Debit/credit sign logic Description
Database values In data entry, the system stores the values to the database with the
same sign that you specify when entering the data on the user
interface.
In reporting, the system displays the values on the user interface

with the same sign that is stored on the database.
 Example
Assets items as positive (without a sign) and
liabilities/stockholders’ equity items as negative (with a minus
sign).
Values as per item sign In data entry, the system takes into account both the sign that you
specify on the user interface and the debit/credit sign set in the
master data of the item/subitem concerned. When storing the value
to the database, the system stores the product of the user-
speci ed sign and the signs in the master data of the item/subitem
concerned.
In reporting, the system takes into account both the sign that is
stored on the database and the debit/credit sign set in the master
data of the item/subitem concerned. When displaying the value on
the user interface, the system displays the product of the sign on
the database and the signs in the master data of the item/subitem
concerned.
 Example
The balance of a liabilities/stockholders’ equity item is usually
a credit. The subitem for acquisition is a debit. Therefore, when
you maintain acquisition data on a liabilities/stockholders’
equity item, you do not explicitly specify a sign on user
interface. Nevertheless, the system stores the value with a
minus sign to the database
Inverse database values In data entry, the system stores the values to the database with the
opposite sign as compared to the sign that you specify when
entering the data on the user interface.
In reporting, the system displays the values on the user interface

with the opposite sign as compared to the sign that is stored on the
database.
 Example
You can use this logic for an income statement item, if you want
to show expenses as negative (with a minus sign) and revenue
as positive (without a sign). This relationship between positive
and negative values enables you to calculate nancial results
using standard Microsoft Excel formulas.
More Information
4/20/2019
Making Global Settings for a New Data

Matrix
Prerequisites
You have opened a workbook that was created using the Interactive Excel template.
Context
Before you create a new data matrix, you make the global settings.
Procedure
1. Place the cursor on a cell that you want to form the upper left corner of the matrix header data.
2. Click Data Matrix New .
The settings of existing matrices are copied into your matrix as default values.
A dialog box opens that displays the preset characteristics, that is, the global parameters.
You can prede ne the global parameters by clicking SAP Interactive Excel Settings Global Parameters . You can
deactivate certain parameters.
3. On the Settings tab, enter a name for your matrix and specify the following parameters:
Matrix name
If you de ne several matrices for a single worksheet, you can give them different names.
Note
You cannot change the name of a matrix later.
Debit/credit sign logic
For information, see Debit/Credit Sign Logic.
Scaling
When you create a matrix, you can specify a scaling factor of one (1) to one million (1,000,000) to apply when you
enter or display data. You can change the scaling factor later if required.
Return units indicator
Select this indicator to display values with a unit in Interactive Excel reports, for example, currency or unit of
measure.
Data entry matrix indicator
Select this indicator to use a matrix to enter data and prepare a data matrix for the entry of nancial data. For
information, see Preparation for Data Entry.
Display blank lines indicator
By default, this indicator is selected and blank lines are displayed in a data matrix. To suppress the display of blank
lines, for example, to improve clarity, deselect this indicator.
4/20/2019
Display blank columns indicator
By default, this indicator is selected and blank columns are also displayed in a data matrix. To suppress the display
of blank columns, for example, to improve clarity, deselect this indicator.
Post 0 for blank cells indicator
Select this indicator if you want to write zero (0) for blank cells. You can use this setting to enter a numerical
value in all items.
Update mode
The update mode speci es how the system is to process the values of data records that were posted earlier. You
have the following options:
Delete (all FS items, all subassignments)
All existing data for each object is reset to zero
Delete (entered items, all subassignments)
All existing data for each object in posted items is deleted before writing the entered data.
Delete (FS items in the matrix, all subassignments)
All existing data for each object in the matrix is deleted with all subassignments, before writing the
entered data.
Note
This option is available for Enterprise Controlling Consolidation (EC-CS) only.
Overwrite (entered items and subassignments)
The existing entries are overwritten by the entered ones (when identical to the item and all subassignments),
other entered data is written; otherwise, existing settings remain unchanged
Allocate (overwrite, but total per item remains unchanged)
The value, which already exists in an item, is divided onto the uploaded subassignments the total per item
remains unchanged. To achieve this, an automatic offsetting entry is generated on the respective default
subassignment.
Note
This option is available for Enterprise Controlling Consolidation (EC-CS) only.
No Modi cation: all data in the target system remains unchanged; the new data is posted only if it does not exist
in the target system yet; otherwise, an error message is displayed.
Note
This option is available for Business Consolidation (SEM-BCS) only.
Note
The Divide function is currently restricted to the Partner subassignment.
4. On the Characteristics tab, specify values for characteristics that are valid for the whole matrix as follows:
a. Select a characteristic in the dialog box.
4/20/2019
b. Determine the characteristic type for the value.
You can de ne the value as either a single value or a set aggregation.
c. Use the arrow button next to the Value ID eld to display a list of possible values and select one of these values
d. If a characteristic is valid for the whole matrix and you do not want it to appear on the worksheet, select Fix.
Note
If you want to change the value selected for a characteristic, position the cursor on the characteristic
and select a new value from the list of possible values using the arrow button; then select the correct
value.
If you want to remove the value selected for a characteristic, position the cursor on the characteristic,
and select the empty entry at the top of the list of possible values.
5. Repeat step 4 until you have speci ed all the characteristic values that you require and then click OK.
Results
The relevant characteristic values are inserted as a block at the cursor position, unless you speci ed them as constants,
in which case they are invisible. General information, for example, user, scaling factor, and aspect is also inserted.
You can format, move, or delete header data after it is inserted into a worksheet. You can change all global settings
except for the matrix name and the aspect after insertion.
You can check your settings and make changes at any time by clicking Data Matrix Change Settings .
Note
In this way, you can nd out which characteristic values are de ned as constants on the Constant tab and therefore
do not appear on the worksheet. You can also deselect the Constant indicator for a characteristic value.
For more information about changing values, see Changing Characteristic Values.
You can prede ne the settings for new data matrices. To do this, click SAP Interactive Excel Settings Global
Parameters .
Global parameters are saved for every single aspect. In exactly the same way, you can copy the settings of existing
matrices as default values.
De nition of a Column and Row Layout

Use
You can de ne the row and column layout of a data entry form or report matrix by arranging characteristics and characteristic
values on a worksheet.
Prerequisites
You have created a matrix and de ned the basic settings for your matrix. For more information, see Creation of a Data Matrix.
Features
4/20/2019
Row and Column Layout
You de ne characteristic values and insert them into the worksheet as a row and column layout. You can specify characteristics
and their values in the following ways:
By manually inserting the characteristic values in the matrix
By selecting the characteristic values from proposal lists that are generated from master data and control parameters
in the database
Note
The advantage of selecting values from lists of proposals is that Interactive Excel recognizes the reference of the cell
in which a characteristic value is located and you do not need specify it explicitly. For more information, see
Determination of Values for Characteristics.
If you use proposals, you can display the key and/or the short text or long text in the matrix. If, in addition to the key, you use the
long text, the long text automatically changes if you select a different characteristic value by entering a new key.
You can use the following types of characteristics to de ne the matrix layout:
Single values
You can arrange single values in sequence, either horizontally or vertically.
For more information, see Specifying Single Values.
Set list
Series of single values arranged in sequence, either horizontally or vertically. The use of sets in Business Consolidation
(SEM-BCS) is enabled when single selections are de ned in the master data in the backend system.
For more information, see Specifying Sets.
Set aggregation
A single entry in the matrix de nition summarizes data for all entries of a named single selection.
Hierarchy
A series of single values arranged vertically with a structure of up to eight (8) levels. This feature is determined by the
native grouping options provided by Microsoft Excel.
You can insert an unlimited number of single values, sets, and hierarchies into your data matrix, and subsequently delete,
move, format, or change them.
For more information, see Specifying Hierarchies.
Caution
A large number of different characteristics can have a negative impact on the performance of the created report.
Recommendation
If you use more hierarchies for columns/rows, the display can combine both together. We recommend that you use
one hierarchy for one direction (column/rows).
When you insert a single value or set aggregation into a cell on the worksheet, a help function for values is automatically set for
this cell. You can display a list of possible values for the characteristic by positioning the cursor on the cell and using the function
4/20/2019
button that appears. This function enables you to change a characteristic value quickly and easily.
Caution
If you subsequently change a characteristic value in a report matrix when connected to a database, the matrix is
automatically refreshed with the appropriate database data. You can suppress automatic update by deselecting Refresh
values automatically on the Data matrix tab.
Caution
When you de ne characteristics, take this into account that certain characteristics are dependent on others. The value you
set for one characteristic could determine the values that Interactive Excel proposes for a second characteristic.
When you use the Data matrix tab in Interactive Excel to specify values for characteristics that you want to insert into a matrix,
you need to de ne any delimiting characteristics before generating a proposal list .
Characteristic Roles
Before you prepare a matrix for data entry, you need to de ne all required characteristics. Required characteristics are de ned
roles of a consolidation model, which are required for valid data selection. The following table shows the characteristic roles
that are supported by Interactive Excel. Their dependencies are de ned by the roles of the consolidation data model.
The following table shows the characteristic roles that are supported by Interactive Excel. Their dependencies are de ned by
the roles of the consolidation data model.
Role Characteristic Required Dependent On
Fixed in consolidation area No
FS item Yes Cons chart of accounts
Version Yes
Restatement Characteristic required, if restatement is

part of data model
Fiscal year Yes
Period Yes
Consolidation group Characteristic required if reporting model is

different from data model
Single value
Attributes “None”
Dimension
Hierarchy or: -
Version
no consolidation unit is speci ed
Fiscal year
or: -
Dimension
consolidated data (posting level 30)
Version
Fiscal year
Period
4/20/2019
Role Characteristic Required Dependent On
Consolidation unit Characteristic required, if no consolidation Dimension Dimension Fiscal year

group is speci ed Dimension Fiscal year Period Version
Single value
Dimension Fiscal year Period Version
Attributes
Set
Hierarchy
Partner unit No Dimension
Single value/Set Dimension
Attributes Fiscal year
Key gure Yes
Subassignment No
Unit of measure No
Year of acquisition No
Period of acquisition No
Custom characteristic No
Transaction currency No
Document type No Dimension
Reference scal year No
Reference period No
Posting level No Key gure
Note
Data is aggregated for characteristics without a de ned value. For example, if a receivables item has a breakdown by trading
partner and transaction currency and you do not specify a value for the trading partner breakdown, the sum of all data
records with a trading partner assignment is calculated (reporting) by the system or must be entered (data entry) by the
user, for this item. If a row or a column contains no speci ed characteristics, it can be used for a user-de ned entry, for
example, in an Excel formula.
Note
The value context help of some characteristics displays a restricted value list only. This feature is deliberate to improve
performance. If you need to specify a value that is not displayed in the list box, rst select any value and then write the
required value directly into the respective cell of the worksheet.
For example, it would be extremely time consuming to preselect and display all possible scal years from 0000 to 9999. Only
twenty years around the current scal year are offered in the context value help for Business Consolidation (SEM-BCS). The
years are displayed in EC-CS are the years for which transactional data has already been posted to the database.
Display of Additional Information
You can display additional information for certain characteristics in any cell in the form of an attribute.
4/20/2019
Note
You can display the debit/credit sign of a nancial statement item or the currency, text, or language of a company. This
additional information is irrelevant for the import (reporting) and export (entry) of data because it has no in uence on the
matrix de nition.
Activities
You make sure that values or value references are set for all the characteristics that you have de ned, so that data can
be saved correctly to or imported correctly from the database.
You specify any remaining required characteristics and check your global settings.
To check the data structure of the data matrix, on the Data matrix tab, click Check.
Specifying Single Values

Context
You can use a list of proposed values to de ne a characteristic as a single value and insert it into the matrix.
Procedure
1. Place the cursor on the cell in which you want to insert a characteristic value.
2. On the Data Matrix tab, click Single values and then select a characteristic
A dialog box opens with a list of values for the characteristic. Depending on the characteristic that you are de ning,
values for other characteristics that you have already speci ed, and on which the values in the proposal list are
dependent, may appear in the elds at the top of the box.
Note
You may want to specify a value for a characteristic that is dependent on the values of characteristics that you have
not yet speci ed. To generate a list of valid proposals, you need to specify these delimiting characteristic values. An
example of a delimiting characteristic value is the consolidation chart of accounts, which represents a compound of
the characteristic FS item. A value list for FS items is displayed only after you have speci ed the chart of accounts.
Note
If a list is very long, rst, a condensed form of the list is displayed, which you can selectively expand as required.
3. Select one or more values.
You can use Windows selection functions to select multiple values ( CTRL + click) or blocks of values ( SHIFT + click).
You can also use the search function by ID values or long texts to go to its position in the list. In addition, you can position
on a value using the Position button.
4. Optional: To insert more than one single value, specify how you want the values to be arranged on the worksheet:
Vertically: multiple values in a single column. This option is useful when you are de ning rows of a matrix.
Horizontally: multiple values in a single row. This option is useful when you are de ning columns of a matrix.
5. Click OK.
4/20/2019
Results
The values are inserted at the cursor position, either vertically or horizontally (depending on the arrangement selected).
If you select multiple values, these values are inserted in the sequence in which they are listed in the database.
You can format, move, delete or change single values after insertion into a worksheet.
Note
You can de ne multiple single values in a single step.
Specifying Sets
Context
You can use a list of proposed values to de ne a characteristic as a set and insert it into the matrix. Sets are de ned as named
single selections in the consolidation workbench. A set consists of characteristics such as consolidation unit and FS item.
Procedure
1. Place the cursor on the cell in which you want to insert the rst entry in the set.
2. On the Data Matrix tab, click Sets and then select a characteristic.
A dialog box opens with a list of values for the characteristic. Depending on the characteristic that you are de ning,
values for other characteristics that you have already speci ed, and on which the values in the proposal list are
dependent, may appear in the elds at the top of the box.
Note
You may want to specify a value for a characteristic that is dependent on the values of characteristics that you have
not yet speci ed. In order to generate a list of valid proposals, you need to specify these delimiting characteristic
values. A value list displayed only after you have made this speci cation.
Note
3. Select one or more sets.
You can use Windows selection functions to select multiple values ( CTRL + click) or blocks of values ( SHIFT + click).
You can enter a value ID (in the form of the eld name) to go to its position in the list. You can also use the search
function by ID values or long texts to go to their position in the list. In addition, you can position on a value using the
Position button.
4. Determine the following:
How the set entries should be arranged on the worksheet (in the case of a set list or multiple set aggregations)
Whether the ID and/or short text and/or long text of the characteristic should be displayed
Whether the set is a list set or a set aggregation
5. Click OK.
Results
4/20/2019
Set list
The relevant set entries are inserted at the cursor position, either vertically or horizontally (depending on the arrangement
selected).
Set entries are inserted in the sequence in which they are entered in the set.
Set aggregation
Only one entry is inserted into the worksheet. This entry represents the sum of all entries in the set.
You can format, move, delete or change sets in a worksheet.
Specifying Hierarchies
Context
You can use a list of proposed values to de ne a characteristic as a hierarchy and insert it into the matrix. You can specify
hierarchies for the following characteristics:
Consolidation group
Consolidation unit
Partner unit
FS item
Other characteristic, if the corresponding InfoObject has a hierarchy and the hierarchy is not disabled by role de nition
Procedure
1. 1. Place the cursor on the cell in which you want to insert the rst entry in the hierarchy.
2. Click Data Matrix Hierarchies and select a characteristic.
A dialog box opens with a list of values for the characteristic. For example, you can select a consolidation unit.
Note
3. Select one or more hierarchies.
You can use the standard Windows commands to select multiple values ( CTRL + click) or blocks of values ( SHIFT +
click). You can enter a value ID to go to its position in the list.
4. Click Settings and determine the following:
Whether you want hierarchy levels to be indented when inserted into the worksheet (Format checkbox)
How many hierarchy levels (up to eight levels) should be expanded when the hierarchy is inserted into the
worksheet
Whether a color should be applied to the hierarchy
Whether the ID and/or short text and/or long text of the characteristic should be displayed, check box ID and
combobox for text types
4/20/2019
5. Click OK.
Results
The relevant hierarchy is inserted at the cursor position, with the speci ed formatting. All hierarchy entries are inserted,
regardless of the number of levels that are expanded.
You can change the color format and indent of the individual levels by clicking SAP Interactive Excel Settings . Your settings are
saved locally on your computer.
Specifying Attributes
Prerequisites
You have speci ed the header data for your matrix. You may have also de ned the matrix layout.
Context
You can insert an attribute into a matrix to provide additional information about a single value, a set entry or a hierarchy entry.
An attribute is not part of the information required for communication between SAP Interactive Excel and the database. SAP
provides possible attributes as well as further custom characteristics. The information that can be provided by an attribute
depends on the characteristic, for example, a debit/credit sign or a short text can be inserted for a nancial statement item.
Note
You cannot insert attributes for a set aggregation because this characteristic has multiple values.
Procedure
1. Place the cursor on the cell in which you want to insert an attribute.
2. Click Data Matrix Attribute and then the relevant characteristic.
A modeless dialog box appears in which you specify the relevant characteristic value.
3. Place the cursor on the cell in which the ID or long text for the value is located.
The cell reference is displayed in the eld. Click OK.
By entering an area, you can also display the attributes for all of the elds within the area.
In the next dialog box, select an attribute and click OK
Note
You may want to specify an attribute for a characteristic that is dependent on the values of characteristics that you
have not yet speci ed. In order to generate a list of valid attributes, you need to specify these delimiting
characteristic values. A list of attributes displayed only after you have made this speci cation.
Results
The attribute is inserted at the cursor position, and can be subsequently formatted, moved, deleted, or changed.
4/20/2019
You can use the procedure described above to change an attribute that you have already de ned. When you change an
attribute, you need to con rm that you want to overwrite it with new data.
Changing Characteristic Values

Use
You can change some or all of the values that you have already speci ed for characteristics in a matrix by doing the following:
Changing values manually in a matrix
Changing the existing values by typing over them in the worksheet directly
Changing values by means of proposal lists
Procedure
You can change values by means of proposal lists by doing one of the following:
Changing characteristic values from a selection list
1. Place the cursor on the cell you want to change.
2. For sets and/or single values, select a value from the dropdown listbox.
You cannot change hierarchies by using the listbox because there is no dropdown for cells with hierarchies.
3. When the value listbox appears, click the required value, for example, the name of a speci c consolidation unit, and then
click OK.
Changing characteristic values by overwriting existing values
1. Place the cursor on the cell in which the characteristic you want to change is located.
2. On the Data Matrix tab, select the relevant characteristic type and the characteristic.
3. When prompted, con rm that you want to overwrite the existing value.
A dialog box appears with a list of values for the characteristic.
4. Select a value, check that the display format is correct, and then click OK.
More Information
Determination of Values for Characteristics

Use
The link between the database characteristics (that is, the elds in the totals InfoCube for Business Consolidation (SEM-BCS)
or the elds in the totals database table of Enterprise Controlling Consolidation (EC-CS)) and the characteristics available in
Interactive Excel is preprogrammed. Your assignment of characteristic values in a data matrix to the preset Interactive Excel
characteristics enables data to be transferred between the correct database elds and matrix elds.
4/20/2019
You can identify a characteristic value by entering one of the following:
A cell reference
A single value
If you use master data and control parameters from a database as proposals when de ning characteristics, the value reference
of characteristic is automatically set. This reference is automatically adjusted when a characteristic is moved to a different
location on a worksheet.
However, you need to specify the value or value reference for characteristics that you have de ned as follows:
By manual insertion in a matrix, outside a list of set entries or a hierarchy
By copying and pasting from another matrix
It is helpful to specify missing values or missing value references after you have completed the de nition of a matrix. To do this,
on the SAP Interactive Excel tab, click Data Matrix Change and then specify the missing values.
More Information
Specifying a Value/Value Reference for Characteristics
Identifying the Area for Data Input/Output -- Import and Export
Entry of Speci c Data Categories
Specifying a Value/Value Reference for

Characteristics
Prerequisites
You have not yet speci ed a characteristic value or the cell reference of a characteristic value, for example, if you manually
inserted a characteristic into your matrix.
Procedure
Using the Data Matrix tab
1. On the Data Matrix tab, click Change.
The Change data matrix dialog box opens.
2. In the Change data matrix dialog box, on the Optional characteristics tab, select a characteristic.
3. In the Value/Value reference eld, enter one of the following:
A single value
If the ID of the single value is identical to a possible cell coordinate, for example a transaction type with the ID
B10, you need to enter the value preceded by an apostrophe ('), for example, ‘B10.
A cell reference, for example, B3
4/20/2019
A cell reference, by clicking the button to the right of the entry eld
A dialog box opens. When you drag the cursor over the appropriate matrix area on the worksheet, its coordinates appear
in the dialog box eld. Use the function button next to the coordinate eld to con rm your entry.
4. Click Con rm to complete your selection.
5. After you have speci ed all values and value references click Save.
If you have not yet de ned a required characteristic, a warning message appears. In this case, click Data Matrix Change
and de ne the appropriate characteristics on the Req. char. tab; then click OK.
Using the Context Menu
1. Select one or more elds by marking it/them, for example, the FS item, and then right-click.
2. Click SAP Interactive Excel Allocate/Allocate globally and select the item or a characteristic that you have chosen
instead.
Result
Cell Reference
An assignment is created between a characteristic on the worksheet and a characteristic preset in SAP Interactive Excel. The
cell reference of a characteristic is automatically adjusted if you move the characteristic to a different location on the
worksheet.
Single Value
The characteristic is invisible on the worksheet, as is the case for all constants.
Identifying the Area for Data Input/Output

Context
Before Interactive Excel can import data into or export data from a matrix, Interactive Excel must be able to identify the data
area in the matrix. The data area in a matrix is adjacent to the column and row layout, and consists of cells relating to these
layouts.
If you de ne a matrix in which the row and column layouts and their respective cells are unique, Interactive Excel automatically
recognizes the data area.
If a layout only occupies a single row or column, it can be confused with the header data and therefore Interactive Excel cannot
identify the layout as a row or column layout. In this case, you are prompted to explicitly specify the data area at the following
events:
After you have saved a matrix de nition that you have changed by clicking Data Matrix Change .
Click Data Matrix Import data to ll a matrix with data.
 Example
You have inserted a hierarchy of consolidation items in the row layout of a matrix and a version in the column layout.
Interactive Excel cannot identify the data area because it does not recognize a layout that only contains one characteristic
value.
4/20/2019
Procedure
1. Select the data area by dragging the cursor over the worksheet.
2. Select Choose to the right of the coordinate eld to con rm your entry.
3. Click Con rm.
Next Steps
Data Matrix
Entry of Speci c Data Categories

Use
You can enter cumulative nancial data for a combination of the following parameters by specifying an appropriate key gure:
Valuation
Local requirements (reported nancial data)
Currency or quantity
Local currency
Transaction currency
Quantity
 Example
You select the key gure LV LC CD (reported nancial data, local currency, cumulative).
Activities
When you de ne a data matrix, you specify the data category for your nancial data by setting the appropriate key gure as a
global characteristic value. For information about the de nition of global characteristic values, see Making Global Settings for a
New Data Matrix.
Creation of Further Data Matrices

Use
When you create an additional matrix, global characteristic values set for the initial matrix are automatically proposed for the
header data. This minimizes the effort required for de ning two or more matrices with similar or identical header data.
Activities
You create an additional matrix in the same way as the initial matrix, by clicking Data Matrix New . For more information, see
Creation of a Data Matrix.
4/20/2019
You select the values that you want to copy. A value is selected when the eld to its left is selected. After you con rm your
selections, a dialog box opens where you de ne other global settings.
Preparation for Data Entry

Use
This function enables you to prepare a data matrix for the entry of nancial data. During preparation, Interactive Excel blocks
certain cells in the matrix and makes other automatic settings, as described below. It then imports existing nancial data from
the database as a reference for data entry.
Preparation for data entry ensures that data is entered correctly. It can be carried out by a parent before distribution of
matrices to subsidiaries, or it can be performed by the subsidiaries themselves.
Prerequisites
You have de ned a matrix locally or received a prede ned matrix from a parent, for which the Data entry matrix
indicator is set. For more information, see De nition of a Column and Row Layout.
You have access to the backend system in which you want to save the data.
Features
Blocking of Cells Against Data Entry
Interactive Excel checks all cells in the data area to determine whether they are valid for data entry. Cells that are not valid for
data entry (for example those in which totals items or invalid characteristics are located) are locked and their content cannot
be saved to the database.
Caution
If you enter data in invalid cells and try to export it to the database, a warning message is issued and you can then
correct the error. Once you have corrected an error, data can be exported to the database. You do not need to rerun
the preparation.
If you do not correct a recognized error and you try to export data to the database again, data is transferred;
however, the data with errors is not saved in the database, and an entry is made in the error log. This procedure
enables you to save correct data to the database without having to rst correct any data with errors.
You can use the Information about the Origin of Data function to display cells that are blocked for data entry.
For more information, see Information about the Origin of Data.
Insertion of Totals Formulas for Hierarchy Nodes
Values for hierarchy nodes are replaced by totals formulas, which automatically calculate the sum of data entered for all items
below the nodes.
Caution
Due to the insertion of totals formulas, preparation for data entry is not suitable in the following cases:
4/20/2019
If you use hierarchies of companies/consolidation units in the matrix:
Only summarization within a hierarchy of consolidation items can produce a value that is valid for consolidation
purposes.
If you have speci ed that you want to use the Values as per item sign debit/credit sign logic:
Since the majority of values are entered/displayed as positive using this logic, the total calculated at the hierarchy
nodes will be incorrect.
A cell comment contains information from the SAP system about the reason why the update cannot take place. Some
reasons might be:
Subassignments were not transferred from the SAP system.
The company addressed does not exist.
The item is a totals item.
A matrix was deactivated.
After a matrix has been prepared for data entry, it is deactivated. The connection to the database is not terminated, but if you
subsequently change the de nition of the matrix, data is not automatically refreshed. However, you can manually trigger a
refresh of data.
 Example
You prepare a matrix with actual data for the year 2014. You then rede ne the matrix for the entry of 2015 plan data and use
the actual data for 2014 as a reference for data entry. When you change the year to 2015, the data is not refreshed
automatically.
Data Import
Any data that exists in the database for the combination of characteristic values in your matrix de nition is inserted into the
matrix and serves as a reference that can simply be typed over.
Activities
You can run the preparation function as follows:
When you save a matrix de nition, click Data matrix Change Import data .
Click Data Matrix Import data and then the relevant work area.
Entry of Data in a Matrix

Use
You can enter nancial data in a data matrix and save it to a backend system.
Prerequisites
The matrix in which you want to enter data is already de ned, and you have access to the system in which the data is to be
saved. You have de ned a matrix or a parent company/unit has provided you with a prede ned matrix in which you can enter
4/20/2019
data. For more information, see De nition of a Column and Row Layout.
Process
1. Optional: You run the preparation for data entry function.
During the preparation, the system imports current data from a backend database into the matrix, certain cells in the
matrix and other automatic settings are blocked. For more information, see Preparation for Data Entry.
Note
A parent company can run the preparation for data entry function on a matrix before sending it to a subsidiary. If this
is the case, the subsidiary does not have to run the preparation function when it receives the matrix.
2. You enter your nancial data for the period in the data area of the matrix, either in empty elds or by typing over the
reference data from the preparation for data entry.
3. You save the data to the database.
When you save data to the database, the system checks the characteristic values in your matrix de nition for
consistency. You can also trigger a validation of data using prede ned rules.
4. Optional: You export data in test mode to nd and remove any errors before you update the database.
Deleting a Data Matrix

Context
You can completely remove a data matrix de nition from a worksheet and reset all settings made for the matrix.
Procedure
1. Click Data Matrix Delete matrix .
A dialog box opens.
2. Specify the data to be deleted by doing one of the following:
Enter the name of the matrix to be deleted.
Select the area to be deleted by dragging the cursor over the appropriate matrix area on the worksheet. When its
coordinates appear in the dialog box eld, use the function to the right of the eld to con rm the coordinates of
the elds to be deleted.
3. Click OK to delete the selected area.
Saving of Financial Data to a Database

Use
You can export nancial data entered in a data matrix into a backend system.
Prerequisites
You have entered nancial data in a matrix, possibly after preparing your matrix for data entry.
4/20/2019
For information, see Preparation for Data Entry.
Features
Consistency Checks
When you save data to the database, the system checks the characteristic values in your matrix de nition for consistency.
A warning message appears if characteristic values in a matrix are inconsistent with those in the database, for example,
if they are invalid or have an incorrect breakdown. You can correct any errors and restart the database update.
Data in rows or columns without a de nition is not saved to the database.
The value 0 (zero) is saved for empty cells.
Error Log
Errors that are detected during the export are written in an error log in a text editor window. You can delete errors in the text
editor once you have corrected them in the matrix, and you can copy the log to other applications for printing or archiving
purposes.
Test Run
You can save data in test mode. The system checks characteristics, validates data if speci ed, and generate a log of any errors,
without updating the database. The test run enables you to remove any errors before saving in update mode.
Activities
To save data to the backend system, you click Data Matrix Update Data . You specify whether you want to run the update in test
mode and whether the system should validate the data.
You can save data from all matrices in a worksheet or all matrices in a workbook to the database.
Note
If status management is switched on in the settings of the consolidation area, the status of that data collection task in the
SAP backend system, to which you have assigned a data collection method with the Active Excel data collection procedure is
updated by the exported data.
Information about the Origin of Data

Use
You can view important information about the status and the origin of data in a data matrix, a pivot table, or an individual cell on
a worksheet.
Features
Origin of Data in a Matrix
You can display and, if required, insert the following information into the worksheet at the cursor position:
Characteristics used in the matrix and their values

4/20/2019
Logon user name with which data was imported
System/Database from which data was imported
Date on which report data was refreshed most recently
Scaling factor
Further technical information such as add-on version on the Version tab
The following functions are also available in the documentation dialog box:
Locked Cells button: for highlighting of cells blocked for data entry
The blocked cells are marked with a color.
Matrix De nition button: for demarcation of the data matrix de nition
All active cells belonging to the matrix de nition are highlighted on the worksheet.
Insert Data
You can insert this technical information into the active worksheet at the cursor position.
Caution
Only insert technical information into the empty range of a worksheet; otherwise, you can overwrite your processing
data.
The relevant cells are marked until you choose another function. However, you can print out a copy of the worksheet with this
information displayed before you continue.
Origin of Data in a Cell
You can display and, if required, print information about the parameters for the data in a cell. You may want to do this, for
example, if you cannot establish the origin of data in a cell from the characteristic values that appear on the worksheet.
If data has been calculated using an Excel formula, the formula is displayed. Data that has been typed directly into the
worksheet is identi ed as a constant.
Activities
To display information about the origin of data, position your cursor on the data in the worksheet and click SAP Interactive
Excel Origin of data and then Active Matrix or Cell. Alternatively, you can get information about the origin of data by using the
context menu SAP Interactive Excel Origin of data .
Creating a Snapshot of a Worksheet or

Workbook
Context
As a security measure or for test or presentation purposes, you can create a copy of a worksheet or a workbook.
Note
4/20/2019
You cannot refresh the data in a copy of a worksheet or a workbook by importing data from a database.
Procedure
1. Click Data Matrix Snapshot and then Workbook or Worksheet.
A dialog box opens
2. Enter the name of the workbook for which you want to create a snapshot or leave the eld empty if you want to create
the snapshot in a new workbook.
3. Click OK.
Results
An identical copy of the workbook or worksheet is created in the speci ed workbook.
Note
This copy cannot be connected to a database.
Automatic Data Collection

Purpose
Automatic data collection is an overall term for those methods the consolidation system uses to collect data that is either
ready for transfer from other systems or is delivered as data les. In comparison to manual data entry, the methods for
automatic data collection are bene cial when dealing with large volumes of data or when you want to efficiently process
recurring period tasks for data collection.
Features
The following methods are available for automatic data collection:
Flexible upload
Load from data stream
Copy
The following gure illustrates the general principle behind the methods for automatic data collection:
4/20/2019
The system reads the data from either a data le (the exible upload method) or a data stream. Data streams can be
processed as follows:
In the load from data stream method, the data comes from a data stream you specify, and is written to the InfoCube of
Consolidation.
In the copy method, the data also comes from a data stream you specify, but is written to a different selection of
characteristics in the same data stream.
After determining the method, you de ne mapping rules for mapping the source data elds to the elds of the consolidation
data basis. The system uses these rules to transform the data into a format required for Consolidation and then writes the data
to the data basis. You can specify a target selection, for example, to write data only for certain consolidation units or certain
versions.
A common feature shared by all methods for automatic data collection is that the system's behavior is dependent on the
method's update mode setting, which is a property all methods have. For more details, see Control of Data Collection Using
Update Mode .
You can choose different types of data to be collected. The following table shows which speci c objects are collected when a
data type is chosen:
Type of Data Objects Collected
Master data, customizing settings The master data and settings speci ed in the method
Changes in investment Characteristics with the roles version, group currency, scal year,
period, and investee unit (each with their independent compound
characteristics) and also the characteristics that are xed in the
consolidation area
Changes in investee equity Characteristics with the roles version, group currency, scal year,
period, investee unit, and (cost center) activity type (each with
their independent compound characteristics) and also the
characteristics that are xed in the consolidation area
Equity holdings adjustments Characteristics with the roles version, group currency, scal year,
4/20/2019
period, consolidation unit, and (cost center) activity type (each
with their independent compound characteristics) and also the
characteristic that is compounded with the role item
Goodwill Characteristics with the roles version, group currency, scal year,
period, consolidation unit, investee unit, (cost center) activity
type, year of addition, and period of addition (each with their
independent compound characteristics) and also the
characteristics that are xed in the consolidation area
Inventory data Characteristics with the roles version, group currency, scal year,
period, consolidation unit, partner unit, and product group
(each with their independent compound characteristics) and also
the characteristics that are xed in the consolidation area
Supplier data Characteristics with the roles version, group currency, scal year,
period, consolidation unit, partner unit, and product group
(each with their independent compound characteristics)
Constraints
You should ensure that the format of the collected data exactly matches the data structure in the consolidation system.
Otherwise, the system assumes there is an error and does not completely execute the data collection, or does so only partially.
This can also happen even if the data at rst glance appears to be correct. For example, the system behaves like this in the
following situations:
You want to collect transaction data that has a currency without decimal places. However, the monetary values in the
data include decimal places. In this case, the system terminates the collection run. The system still terminates the run
even if the decimal places are all lled with zeroes.
In the customizing settings for the data collection method, you de ned elds for monetary values in local currency and in
group currency. Although the collected data contains the amounts in group currency, it does not contain the currency key
for the group currency. In this case, the system collects only the amounts in local currency and sets all amounts in group
currency to zero. In this situation, the fact that the method contains a eld for the group currency prevents the loading
process from implicitly translating the local currency amounts to group currency.
Example
For detailed examples of data collection, see Data Collection: Examples .
Control of Data Collection Using Update

Mode
Use
The update mode you select for data collection determines how the system treats existing data in the target system. Both the
type of data and the data collection procedure also affect the behavior of data collection.
Integration
The update mode controls the function of the data collection procedures exible upload, copy, delete, and load from data
stream.
4/20/2019
Features
Determination of Data to Be Changed
The update mode you choose only applies to the data records that match the selection. Data beyond the selection range is not
changed by any data collection procedure. The type of data to be collected affects the scope of the selected data as well as the
data's composition:
The data to be changed can be selected based on the characteristics with the roles version, group currency, scal year,
period, and consolidation unit along with their independent compound characteristics, and the characteristics that are
xed in the consolidation area.
Documents
The same characteristics as for reported nancial data (listed above) are used for selecting the data to be changed. In
addition, the system uses the characteristic with the role document type.
Changes in investment
period, and investee unit along with their independent compound characteristics, and the characteristics that are xed
in the consolidation area.
Other data: changes in investee equity, goodwill, equity holdings adjustments, inventory data, and supplier data
period, and consolidation unit along with their independent compound characteristics, and the characteristics that are
xed in the consolidation area.
Master data and Customizing settings
When selecting this type of data, the system normally uses the independent characteristic of the characteristic for which
data is being collected. For more details about these characteristics, see the properties of each characteristic in the
Data Warehousing Workbench of SAP NetWeaver Business Intelligence (BI).
Here is the selection behavior for several Customizing settings and special types of master data:
Combinations of consolidation units: The selection uses the independent compound characteristic of the
characteristic with the role consolidation unit.
Version combination: The selection uses the independent compound characteristic of the characteristic with the
role version.
Breakdown category: The selection uses the characteristic consolidation area.
Treatment of Existing Data
The application of the update modes treats the various types of data in different ways. These different effects are described
below.
Recommendation
Some differences in system behavior are very subtle and only concern narrowly-de ned focal areas of data collection. We
therefore recommend that you closely examine the effects of the update mode on the type of data you want to collect to
avoid drawing any false conclusions about one data type over another.
Reported Financial Data
4/20/2019
Delete All: All data within the selection is reset to zero.
By default, the system also reads any data records from the source environment in which all key gures are zero. If you
have activated the business function FIN_ACC_GC_ASTHFS, you can specify that the system is to ignore these data
records by selecting data type Reported Financial Data or All Data Types in the Customizing settings for a collection
method of type Load from Data Stream or Copy.
Delete Uploaded Data: The system resets to zero all data within the selection whose combination of characteristics also
appears in the data to be collected. However, data that lies within the selection but has no corresponding data in the
data to be collected is not changed.
Overwrite: Existing data is overwritten with the imported data that has the same combination of characteristics. Data
for which there is no corresponding data to be collected remains unchanged.
No Modi cation: All data in the target system remains unchanged.
Note
The system creates new data records in the target system for collected data records whose keys do not match the
keys of the data in the target system. Exception: If update mode No Modi cation is used, no new reported nancial
data is created.
All four update modes are available for the exible upload method. Only the modes Delete All and Overwrite are
available for the other data collection methods.
Documents
Delete All: System behavior depends on the input type.
Periodic: All documents of the period are reversed. The system also creates a new document that eliminates the
effects of all existing inverting and inverted documents within the period.
Cumulative: All documents of the period are reversed. The system also creates a new document for the period.
This document eliminates the effects of all documents that were posted in the prior periods of the scal year. This
document also eliminates all inverting and inverted documents that were posted in the current period of the
scal year.
Delete Uploaded Data: The same as for Delete All.
Overwrite: All existing documents in the target system remain unchanged. If the input type is cumulative, the system
creates a new document that eliminates the effects of all documents that were posted in the prior periods of the scal
year.
No Modi cation: The same as for Overwrite.
Note
The system always posts documents that are imported from a data le.
Whether data collection deletes or reverses existing documents depends on the settings for version combinations.
Master Data, Customizing Settings, and Additional Financial Data
Delete All: The system deletes all data records within the selection. Then, the system transfers the collected data
records to the target system.
4/20/2019
Delete Uploaded Data: The system deletes all data within the selection whose combination of characteristics also
appears in the data to be collected. Then, the system transfers the collected data records to the target system.
However, data that lies within the selection but has no corresponding data in the data to be collected is not changed.
Overwrite: All collected data records are written to the target system. Any existing records with matching keys are
overwritten. New records are created for collected data records that have no matching keys in the target system. All
other settings remain unchanged.
No Modi cation: The system does not write data records that belong to objects that already exist. New records are
created for data records that belong to objects that do not exist yet.
Note
Hierarchies and Attributes of Hierarchy Relationships
Delete All: First, the system deletes all existing hierarchy relationships within the selection. Then, the system transfers
the collected data records to the target system.
Delete Uploaded Data: The system deletes all existing hierarchy relationships in the target system whose higher-level
object appears in the collected data, regardless of whether the object is a higher-level node or lower-level node in the
collected data. Then, the system transfers the collected data records to the target system.
Overwrite: The system transfers the collected hierarchies to the target system. Hierarchies that already exist in the
target system are overwritten. New hierarchies are created if they do not exist in the target system.
No Modi cation: The same as for Overwrite.
See also:
Flexible Upload
Data Collection: Examples
Examples: Update Mode for Automatic Data

Collection
The following tables and gures illustrate how the update mode you choose affects the various types of data. The following
types of data are illustrated:
Documents
Consolidation unit
Item hierarchy
Each data type is broken down into:
Data that already exists in the target system
Data to be collected
4/20/2019
Results of data collection for each update mode

Item Partner Value in local currency
1000 A 100
2000 B 200
3000 C 300
1000 A 400
1000 B 500
2000 A 600
4000 A 800
Result after data collection with update mode Delete All
1000 A 400
1000 B 500
2000 A 600
2000 B 0
3000 C 0
4000 A 800
Result after data collection with update mode Delete Changed Data
1000 A 400
1000 B 500
2000 A 600
2000 B 0
3000 C 300
4000 A 800
Result after data collection with update mode Overwrite
1000 A 400
1000 B 500
4/20/2019
2000 A 600
2000 B 200
3000 C 300
4000 A 800
Result after data collection with update mode No Modification
1000 A 100
2000 B 200
3000 C 300
Documents
Doc. Number Item Posting Value in LC Reversing Reversed Inverting Inverted

Period Document Document Document Document
1001 1000 6 100 1003
1001 2000 6 -100 1003
1002 3000 6 200
1002 4000 6 -200
1003 1000 12 -100 1001
1003 2000 12 100 1001
1004 3000 12 400
1004 4000 12 -400
Data to be collected (input type Cumulative)
Item Posting period Value in local currency
4000 12 500
5000 12 -500
Result after data collection with update modes Delete All and Delete Changed Data

1001 1000 6 100 1003
1001 2000 6 -100 1003
1002 3000 6 200
1002 4000 6 -200
4/20/2019

1003 1000 12 -100 1001
1003 2000 12 100 1001
1004 3000 12 400 1005
1004 4000 12 -400 1005
1005 3000 12 -400 1004
1005 4000 12 400 1004
1006 3000 12 -200
1006 4000 12 200
1007 4000 12 500
1007 5000 12 -500
Result after data collection with update modes Overwrite and No Modification

1001 1000 6 100 1003
1001 2000 6 -100 1003
1002 3000 6 200
1002 4000 6 -200
1003 1000 12 -100 1001
1003 2000 12 100 1001
1004 3000 12 400
1004 4000 12 -400
1005 3000 12 -600
1005 4000 12 600
1006 4000 12 500
1006 5000 12 -500
Consolidation unit
Company Description Version Year of Initial Period of Initial Tax rate

Consolidation Consolidation
C1000 Old 1 100 2003 12 8
C1000 Old 1 200 2004 12 5
C3000 Old 3 200 2005 12 10
4/20/2019

C1000 New 1 100 2004 12 9
C2000 New 2 100 2005 12 15

C1000 New 1 100 2004 12 9
C2000 New 2 100 2005 12 15

C1000 New 1 100 2004 12 9
C2000 New 2 100 2005 12 15
C3000 Old 3 200 2005 12 10
Result after data collection with update mode Overwrite

C1000 New 1 100 2003 12 9
C1000 New 1 200 2004 12 5
C2000 New 2 100 2005 12 15
C3000 Old 3 200 2005 12 10
Result after data collection with update mode No Modification

C1000 Old 1 100 2003 12 8
C1000 Old 1 200 2004 12 5
C3000 Old 3 200 2005 12 10
C2000 New 2 100 2005 12 15
Item hierarchy
4/20/2019
4/20/2019
Hierarchy Text Node Item From To
H1 1000
1000 1100
1000 1200
H1 2000
2000 2100
2000 2200
4/20/2019
4/20/2019
Result after data collection with update modes Overwrite and No Modification
4/20/2019
Mapping
Use
You use this function to transform a source data structure into a target data structure. You use the mapping function for the
following data collection methods:
Flexible upload (mapping is optional; requires an InfoObject catalog, which is speci ed in the data basis)
Copy (mapping is optional)
Integration
If you have de ned mapping rules in a BAdI for data collection (in addition to this set of mapping rules) and you have speci ed
the BAdI lter value in the settings for the method, the task rst executes the mapping rules de ned in the method and then it
executes the mapping rules de ned in the BAdI implementation.
Prerequisites
In Customizing for methods, you have made the settings listed on tab page Settings (including the update mode and the input
type).
Features
Overview of Subfunctions
Mapping has subfunctions that allow you to:
Set a constant for a target characteristic value.
Assemble a target characteristic value from the value of one or more source characteristics.
Split a source characteristic value into several elements and map each individual element to a different target characteristic
value.
Populate a target key gure from a source key gure.
Reassign characteristic values.
Derive a target characteristic from the attribute values of a source characteristic.
Have any mapping rule listed earlier be executed on a certain condition, which means that the rule is executed only if the values
of the source characteristics meet a condition you have de ned. You can create multiple conditional mapping rules for a target
characteristic.
Assign a name to a mapping rule for a characteristic and, thereby, enable it to be reused for another, master data-equivalent
characteristic (that is, for a characteristic with the same basis characteristic) in the same, or another mapping.
User Interface for Customizing
4/20/2019
The user interface has the following layout (when you call up mapping rule details):
List of Target Fields
The system displays a list of the target elds (characteristics and key gures) that exist in the target data basis.
The symbols preceding the target elds have the following meanings:
Symbol Meaning
Characteristic
Key gure
No mapping rule de ned
Mapping rule exists
In process
Operator (condition, move, reassignment, apply existing rule)
Mapping Rules
With the help of operators, you can create mapping rules, which control how source data is mapped to the target area. The
mapping rules of a method are dependent only on the consolidation area.
4/20/2019
The following operators are available:
Condition
Move
Reassignment
Apply existing rule
Condition
You can draft a mapping rule with or without a condition. A condition must always be followed by another operator (for example,
move or reassign ).
In the details of a condition you specify the characteristic values to which the condition applies. You also can use single
selections. A condition has the effect of a lter on the source data records.
You can create multiple conditions per target characteristic.
Move
The move operator maps one or more source elds to a single target eld.
If some of the eld names in the source and target structures are identical, you can choose Create Proposal . Then the system
automatically creates the moves for each of those elds and displays the moves in the list of target elds beneath each eld.
(This also applies to the permanent parameters.)
To move a single source eld to a single target eld, you specify the source eld in the move details.
Furthermore, in the details you can specify an offset and a length to reference the technical key of the source eld.
Suppose your source system has a source eld for characteristic item with a length of 18 characters, where the leading eight
characters are used to describe the item in the hierarchy.
The consolidation area in SEM-BCS has a target eld with a length of ten characters.
In the details for the move, you would enter:
Length = 10
Offset = 8
When mapping is executed, the system would copy the last ten characters (positions 9-18) of the source characteristic to the
target characteristic.
To cut out portions of a source eld value, you can use separators and indexes.
4/20/2019
Suppose the source eld has a length of 18 characters. It has the following composition: <pro t center>-<company>.
In the target data basis you have de ned a matrix organization with companies and pro t centers.
You choose the character "-" as the separator. For index 1 you specify <pro t center> and for index 2 you specify <company>.
In this way, the source eld is used twice.
To move multiple source elds to a single target eld, you specify a concatenation rule in the move details (table). Then the
system concatenates the contents of the source elds you specify.
Here you also can specify offsets and lengths, and/or separators and indexes.
Suppose, your source structure includes the elds company and pro t center .
You want to ll a target eld for the characteristic consolidation unit with a length of 18 characters. You want to compose the
target eld as follows:
Character 1 = "C"
Characters 2–7 = the content of the eld "company"
Character 8 = "P"
Characters 9–18 = the content of the eld "pro t center"
In the details for the move, you would enter the following in the table:
Line 1: Constant = C
Line 2: Move eld "company"
Line 3: Constant = P
Line 4: Move eld "pro t center"
To prevent excess spaces between the components of the target eld, you can choose Trim Marginal Spaces .
You can de ne one or more constants for the target characteristic value regardless of whether you move a single or multiple
source elds. Constants are always set as you de ne them, regardless of what the source characteristic value looks like. For
example, you can de ne that the scal year variant is always set to "FY4".
You can populate a target characteristic value with one or more attribute values of a source characteristic (for example, the
attribute country of characteristic pro t center ). You specify attributes within the table in the details for the move.
Reassignment
When you want to assign multiple source elds to a single target eld, you can use the reassignment operator as an alternative.
Here, the value of the target eld is determined by the values of the source elds.
4/20/2019
Suppose the values of the source elds are PC1000 (for the pro t center) and C1000 (for the company). In this case, the value
of the target eld consolidation unit is reassigned with CU0001.
You can use single selections in reassignments, as well.
Applying Existing Rules
If you assign a name to a mapping rule, that rule can be reused. (To do this, double-click the target eld and assign a name for
the mapping rule in the dialog box that appears.)
Now you can use this mapping rule for master data-equivalent characteristics in the same or a different set of mapping rules.
Examples of master data-equivalent characteristics are consolidation unit , partner unit , and investee unit .
Activities
Proceed as follows to de ne a set of mapping rules:
You can create move operation proposals for source and target elds by choosing Create Proposal (see earlier).
Examine the proposed moves.
You can create your own mapping rules for all target elds that have no proposed moves.
To do this, select the target eld in the list and choose one of the following commands in the context menu:
Create Condition
Create Move
Create Reassignment
Apply Existing Rule
Create Condition
In the details of the condition, specify the characteristic values to which the condition applies.
Create a move or a reassignment for the condition, or apply an existing rule.
Create Move
To move a single source eld to a single target eld, specify in the move details, if applicable, an offset and length for the source
eld and/or a constant and an attribute.
To move a multiple source elds to a single target eld, specify in the move details the concatenation rule (and, if applicable,
specify an offset and length or a separator and indexes, with or without constants and attributes).
Create Reassignment
To display the source characteristics in the respective table columns, choose the corresponding symbol in the toolbar above the
table and select the desired source characteristics in the list.
4/20/2019
Apply Existing Rule
To apply an existing rule, call up input help in the details of the mapping rule eld and choose a rule.
Specify the substitution eld.
Continue customizing the data collection method.
Selection
Use
You use this function to restrict the scope of data to be collected and to restrict the area in which posting is to be possible.
As in mapping , you can use selections in the following data collection methods:
Copy (for target selections)
Flexible upload (for target selections)
Load from data stream (for source and target selections)
Source Selections
You use source selections in Load from Data Stream to limit the data volume that is read in order to improve the performance
of the system.
Limitations of Source Selections
Source selections have the following limitations:
Single selections are possible, but single selections cannot be reused. For more information, see the “Reusability of a Single
Selection” section in Single Selection .
A single selection lets you also select the Hierarchy Name characteristic, which you can use in a hierarchical selection.
If the hierarchy is dependent on the version, you can enter the hierarchy version after you open the selection screen.
Source Selections for Loading Hierarchies of Master Data
If you use Load from Data Stream to load a master data hierarchy, you can perform a source selection by deploying the
selection conditions listed below. (You need to have set the indicators Load Master Data and Load Hierarchy on the Settings
tab page in the Customizing settings for the method.)
Selection of Single Values and Ranges
If you specify single values or ranges, the system selects not only the nodes of the source hierarchy, but also their higher-
level nodes including the root node. (See also the example below.)
If you use the update mode Delete Uploaded Data or Delete All , this source selection has the following effect on the
target hierarchy: The system deletes the related root node – including the assigned hierarchy – from the target
hierarchy, and loads the selected source hierarchy in its place.
Selection of Hierarchy Nodes
4/20/2019
If you select hierarchy nodes, the system selects only the selected hierarchy nodes of the source hierarchy, including all
of their lower-level nodes. (See also the example below.)
By using update mode Delete Uploaded Data , you can transfer an entire sub-hierarchy.
If you use update mode Delete All , this source selection can have the following effect on the target hierarchy: Once the
existing target hierarchy is deleted, the system is unable to assign the selected hierarchy nodes to a root node. However,
the assignment of the lower-level nodes remains intact and is restored once you assign the selected hierarchy nodes to
a root node or a hierarchy.
For more information about selection conditions, see the “Selection Conditions” section in Single Selection .
For more information about update modes, see Control of Data Collection Using Update Mode .
Activities
1. De ne the source area from which data is to be loaded.
This involves specifying the desired characteristics and characteristic values. You can also use Complex Selections (see
Single Selection ).
The system attempts an inversion for the status-relevant characteristics. When doing this, the system takes into
account the execution parameters and inversely interprets your mapping rules. This means that it derives the source
selection from the mapping rules between the source and the target.
Recommendation
If the automatic inversion does not produce a result or is too complex, this can cause too many data records to be
read in BI. Therefore, in advance, make sure you restrict the volume of data to be read in the source selection.
2. De ne the target area in the data basis, into which data is to be loaded.
When loading transaction data , you can use a target selection to control which data of a consolidation unit is modi ed.
To do this, you can restrict the items and subassignments in the target selection. You also can use complex selections for
the target selection of transaction data.
When loading master data , customers typically restrict the characteristic itself.
Note
You also can use complex selections for the target selection of master data; however, these only select single values
and ranges.
Use of target selections protects the areas of the data basis that do not belong to the target area. If you use the update
mode Delete All , the system deletes only the data records in the target area of the data basis before the selected data
is loaded.
Example
This example uses a hierarchy of account numbers to illustrate the effects of the source selection of a master data hierarchy,
depending on which selection conditions are deployed:
Selection of a range
Selection of a hierarchy node
Master Data Hierarchy Before the Selection
4/20/2019
The following gure shows the hierarchy of account numbers prior to the selection:
After Selection of a Range
The following gure shows the hierarchy after a source selection with the selection condition Account Number 120000 –
129999 (inclusive range from 120000 through 129999).
4/20/2019
After Selection of a Hierarchy Node
The following gure shows the hierarchy after a source selection with the selection condition Account Number 120000
(inclusive hierarchy node with the account number 120000).
4/20/2019
Flexible Upload
Use
You use this function to import transaction data or master data and hierarchies from a data le into the consolidation system
(SEM-BCS).
Integration
You can use the Flexible Upload component as an alternative, or in addition, to the other data collection procedures.
Within the Flexible Upload method you can use the Business Add-In (BAdI) for data collection ( UC_DATATRANSFER) to perform
mapping activities that the method does not directly support - such as mapping source elds to target elds with a 1:n
relationship). For more detailed information, see the system documentation of the BAdI UC_DATATRANSFER and the
documentation of its methods.
Features
In the Customizing settings for the Flexible Upload method, you specify the format of the data in an upload le. Furthermore,
you specify how the system is to map the characteristics and key gures of the source data to the consolidation system. You
also have the option to de ne target selections. For more information, see Customizing for Flexible Upload.
When the system executes the method, it writes the values to the target area of the data basis in accordance with the settings
you have made in Customizing. In doing so, the system derives the values for consolidation-speci c characteristics (for example,
the posting level and the default values for subassignments when loading transaction data).
Loading of Transaction Data
You can upload the following transaction data from a text le into the consolidation system:
Reported nancial data ( posting level 00)
Documents (posting levels 01, 02, 10, 12, 20, 22, and 30)
Additional nancial data
Note
The data streams Sequence of Activities, Activity Sorting, and Activity Numbers are not available for exible
uploads. When uploading the data streams Equity, Investments, Equity Holdings Adjustments, and Goodwill, you
cannot copy over the activity numbers from the source data. However, you can do this in the data collection
procedure Load from Data Stream.
To be able to periodically execute exible uploads of transaction data in the consolidation monitor, you de ne an upload method,
assign this method to a data collection method, and then assign this data collection method to a data collection task (see
De ning a Flexible Upload).
Loading of Documents
The system uses the standard rules for writing uploaded documents to the target data. For more information, see Automatic
Data Collection of Documents.
4/20/2019
You can improve the differentiation of the documents by inserting header rows in the upload le that indicate the positions at
which the system is to create a new document. To do this, you use row type indicators (see Customizing for Flexible Upload).
Loading of Master Data and Hierarchies
You can upload the following master data and hierarchies from a text le into the consolidation system:
Consolidation groups and their hierarchies
Consolidation units and their hierarchies
Combinations of consolidation units
Items and their hierarchies
Transaction types
Breakdown categories
Other master data (such as functional areas)
To upload master data and hierarchies, you only need to de ne an upload method, execute the method in the consolidation
workbench, and save your changes.
Integrated Upload of Superordinate Fields
If you choose data type Assets/Liabilities - Master Data, you can specify that, in the case of a compound of characteristics, the
system is also to upload independent (that is, superordinate) elds. Using this function you can, for example, upload the asset
main number together with the asset subnumber.
Integration with SAP Applications
Processes are available for integrating SAP applications with the consolidation system (SEM-BCS). These are primarily
intended for customers who have previously used the consolidation component EC-CS, and who now want to migrate to
SEM-BCS. For more information, see Integration with SAP Systems.
Customizing for Flexible Upload

Use
In Customizing for the Flexible Upload method, you specify which upload functions you want to use. You also specify the format
of the data in the le. This information is required to correctly interpret the imported data.
Features
Many of the settings discussed below depend on which data type you choose for the method. For example, the setting for
debit/credit signs does not apply when you upload a consolidation chart of accounts.
Customizing Settings
Data Type
4/20/2019
You use exible uploads to import transaction data and master data. For details about which objects are involved, see
Flexible Upload .
Column Width
You can choose between xed and variable column widths:
Fixed column width: The elds are determined by their horizontal position, not by a separation character. The elds need to be
positioned according to their respective lengths as de ned in the eld catalog of the method.
Variable column width: The elds are separated by a designated separation character. Typical separators are the tab character,
semicolon, comma, or the space character. However, other characters can be designated as well.
Row Types
You can select one of the following types of rows:
A header row, followed by data rows
Row type indicators
A row type indicator is a character at the beginning of a data row that determines the type of the row. The following are valid
indicators and supported row types:
1: Header row
2: Data row
3: Row with hierarchy information
When row type indicators are used, every row (except for comment rows) must begin with a valid indicator. If the data has a
variable column width and eld separators are used, the indicator must also be separated from the rst data eld using the
same separation character.
If the upload le contains comment rows, a unique character is needed in the rst column to identify such a row. You specify the
character for identifying comments at the Comment Row prompt.
If no row type indicators are used, the function interprets the rst non-comment row as the header row, and all subsequent
rows as data rows.
Digit Separation
Here you specify which format is used for numbers and currencies in the data (such as the symbols used to indicate thousands
and the decimal place).
Update Mode
The update mode determines how existing data records are treated during an upload.
You can choose one of the following update modes:
Delete all existing data
Deletes all existing data. Only the uploaded data (from the last upload) remains in the system.
Delete existing uploaded data
4/20/2019
Deletes only the existing data related to the objects (such as the consolidation unit) contained in the uploaded le. The data of
these objects is fully replaced by the data that is uploaded.
Overwrite existing data
Overwrites existing data and adds new data.
Do not change existing data
Does not upload data that belongs to objects that already exist in the system. Only adds new data.
For detailed documentation on update modes (including examples), see Control of Data Collection Using Update Mode .
Treatment of Debit/Credit Sign Attributes
You can determine whether the system should consider the debit/credit sign attributes that are de ned in Customizing for
nancial statement items and/or transaction types. If you choose this option, the system reads the debit/credit signs for
characteristic values prior to posting these values.
Input Type
You can specify whether the consolidation system should interpret the reported transaction data as cumulative (year to date)
or periodic :
Period values re ect the values of the accounting period speci ed in the data record. They represent the changes since the last
collection of data.
Cumulative values re ect the accumulated (year-to-date) values as of the current date. Internally, the system stores the values
as period values after automatically calculating the differences to the prior period balance.
BAdI Filter
After the data is uploaded, you can have the data undergo special processing by implementing the BAdI UC_DATATRANSFER . If
you do this, this is where you specify the BAdI lter value used to request the desired BAdI implementation. For more detailed
information, see the system documentation of the BAdI UC_DATATRANSFER and the documentation of its methods.
Field Catalog
You include in the eld catalog for the upload all elds you want to use in the upload le.
You also have the option of using a free eld . You can assign free elds to all eld catalogs as often as desired. Columns in the
upload le that are allocated to the free eld are read, but not interpreted, during the exible upload. This enables the system
to process les that contain additional information not related to consolidation.
In uploads from a eld catalog, you also have the option to use the mapping feature. If mapping is used, the structure of the
upload le does not need to coincide with the structure of the data basis. Instead, you can allocate an InfoObject catalog of BI,
which then serves as a data structure description. You specify the InfoObject catalog in Customizing of the data basis .
Mapping ( optional)
If you use an external eld catalog, you need to specify in mapping how the data structure of the le relates to the structure of
the data basis.
Selection ( optional)
4/20/2019
If you use an external eld catalog (and thus de ne mapping settings), you can use the selection to restrict which data is
selected and to which area of the data basis the data is written.
De ning a Flexible Upload

Use
You de ne a exible upload in the Consolidation Workbench to import data from a le into the consolidation system. This
speci es which data format the le has.
You use this procedure to de ne your Customizing settings for loading transaction data into your system.
For exible uploading of master data and hierarchies , you only need to de ne the upload method and execute it in the
Consolidation Workbench.
Procedure
A. De ne the Task
De ne a task for data collection to enable you to execute the exible upload of transaction data in the Consolidation Monitor.
B. De ne the Upload Method
1. In the process view of the Consolidation Workbench, choose Consolidation Functions Data Collection Flexible Upload .
2. Create an upload method and give it a name.
3. Choose a data type (for example, reported nancial data).
4. If more than one characteristic is available for the selected data type, select the characteristic to be uploaded.
5. De ne the settings for exible uploads on the Settings tab page. For the details on these settings, see Customizing for
Flexible Upload .
6. On the Field Catalog tab page, determine whether you want to use an external eld catalog.
List the data columns in the upload le and the order they are in. To do this, drag the desired elds from Remaining
Fields to the eld catalog.
You can also use free elds to skip over data that is contained in the le, but is not relevant for consolidation. For more
information on free elds, see Customizing for Flexible Upload .
7. If you want to use an external eld catalog, de ne the mapping settings on the Mapping tab page.
8. If you use an external eld catalog, on the Selection tab page you can restrict the source data and the scope of data to
be written (see Selection ).
C. Assign a Method
To upload the transaction data, proceed as follows:
1. Assign the upload method to a data collection method.
2. In the data collection task, assign the data collection method to the respective consolidation unit.
4/20/2019
For more information, see Data Collection Method and Customizing for the Data Collection Task .
D. Prepare the Upload File
Make sure that the upload le possesses the attributes you speci ed in method customizing.
The upload must have the le type Text .
As an alternative, you can rst create the le in a Microsoft Excel spreadsheet. Then you can save the spreadsheet as a text le
by saving the workbook with the le extension *.TXT or *.CSV.
Recommendation
Before you upload the data, examine both the Microsoft Excel le and the text le.
Executing a Flexible Upload

Use
You use this procedure to execute a exible upload in the consolidation monitor.
Prerequisites
You have de ned the upload method in customizing of data collection.
4/20/2019
If data is to be entered on hierarchy nodes (that is, to totals items), you have selected the respective indicator in Customizing
for Version Combinations .
Procedure
Starting an Upload
1. Execute a le upload by running the data collection task in the consolidation monitor.
2. In the data collection screen, run the upload method.
3. If necessary, specify the name of the upload le.
Note
You can also execute the exible upload method from within the consolidation workbench.
Uploading Data for Combinations of Consolidation Units
If you are modeling a matrix organization, the consolidation system makes sure that the upload method is run for all valid
combinations of consolidation units when the task is executed. The system collects the data for the combinations that are
currently being processed from each respective le that was speci ed. The following applies, for example, when processing
combinations of companies and pro t centers:
If you have selected the upload mode Delete All , and your le does not contain any data for a given combination (such
as, company 1/pro t center 1 ), then the system resets the data for this combination.
If data for versions, scal years/periods, companies or pro t centers is contained in the le but has not been selected for
processing, the system simply ignores this data.
For example, if the upload le contains data for the combination company 2/pro t center 1 , the system ignores this
data record when company 1 is processed.
This logic allows the use of large les (for example, les that contain for all consolidation units or les with data for
multiple periods) without the need to split up the data for processing at the consolidation unit level. When such a le is
uploaded, the system only reads the desired records.
Treatment of Currencies when Uploading Reported Financial Data
The system writes the values it collects for all key gures that have been assigned to a data row in the customizing settings for
the upload method. Under certain conditions, when uploading reported nancial data the system can also write values for key
gures that have not been explicitly de ned in the method.
This applies, in particular, to the ability to automatically write reported nancial data in group currency, in addition to local
currency. For this to occur, the following conditions need to be given:
The local currency and the group currency are the same.
The upload method has an assignment for values in local currency, but does not have an assignment for values in group
currency.
In other words, the system interprets the absence of values in group currency and the fact that both currencies are the same as
an implicit instruction to automatically ll the values in group currency with those in local currency.
The system always writes the values in transaction currency.
Con guring Data Collection Tasks and Methods for Flexible Treatment of Currencies
4/20/2019
You can have data collection tasks support both automatic writing of reported nancial data in group currency and the
collection of reported values in group currency, depending on the structure of the reported data. You can do this by creating two
methods with the category “ exible upload”:
The method for the explicit collection of reported values in group currency contains a eld for values in group currency.
The method for automatic writing of values of group currency contains the placeholder eld “Free Field” at the same
location.
Customizing settings let you set the degree of automation the data collection task uses for choosing the appropriate currency
treatment:
Users manually choose the upload method: You assign both upload methods to the same data collection method. When
the task is executed, the user decides which of the two methods is used. This has the disadvantage that choosing the
wrong upload method would either set the group currency values to zero or retain the group currency values without
change. However, you could use follow-up validation steps to detect such a problem.
System automatically chooses the upload method: You assign each of the two upload methods to separate data
collection methods. In the customizing settings for the data collection task, you choose “depending on consolidation
unit” as the means for assigning the data collection method. Afterwards, you specify which of the two data collection
methods is used for each individual consolidation unit. Although this involves more customizing effort, this fully
automated approach protects the data collection process from accidental selection of an unsuitable method.
Writing of Data is Suppressed if Errors Occur
The data records are only written if no errors occur. This is necessary to prevent follow-up errors. (For example, inconsistent
reported nancial data can lead to erroneous results in currency translation and rounding.)
Possible Errors Caused by Existing Data Records
In addition to uploaded records, the system also checks the records to be written. Thus, the system also checks existing records
in prior periods which are to be changed. Consequently, the following applies:
If data records exist for master data that does not exist (or no longer exists), the system does not change or delete
these records.
If data records exist which are not (or no longer are) permitted to be written, the system cannot change or delete these
records. For example, this can be the case if a required breakdown (without a default) by transaction type was added.
Writing Data to BI
When an upload method is run in update mode and does not produce any errors, the data is not yet written to SAP NetWeaver
Business Intelligence (BI). This takes place when you exit the screen of the data collection task. The system shows which record
is currently being written on the status line of the screen.
Result
The system generates a log of the upload run.
Recommendation
In the log, always check which upload method was actually used. Keep the following in mind:
The task hierarchy is time and version dependent.
The assignment of the data collection method to the task is time, version, and period category dependent.
4/20/2019
Once the records are written to BI, you can display the uploaded data in the list of totals records. To display the cumulative
values for cross-checking the upload, restrict the period to the range from “000” to the desired period.
Examples: Uploading Master Data

Hierarchies
You want to use exible upload to import hierarchies of master data.
If a characteristic is intended to have hierarchies, Customizing of upload methods offers you a eld catalog Hierarchy
Information and – if applicable – the eld Hierarchy Level . This applies to all characteristics, regardless of whether they are
delivered by SAP or de ned by the customer.
The available procedures are described below using examples. It is intended as an aid for choosing the most suitable option and
for avoiding typical error situations.
In general, you have two possibilities:
You can explicitly specify the hierarchy information in separate rows.
See Example 1: Collecting a Consolidation Unit Hierarchy.
You can implicitly specify the hierarchy information via the hierarchy level.
See Example 2: Collecting an Item Hierarchy.
Example 1: Collecting a consolidation unit hierarchy, explicitly specifying the

hierarchy information in separate rows
Procedure
In the settings of the upload method, select Use Row Type Indicators and go to the eld catalogs.
The eld catalog Hierarchy Information is listed. This eld catalog contains a set of elds. You cannot add or delete elds in this
catalog, but you can freely determine the order of the elds within the catalog using Drag&Drop. The catalog always contains
the following elds:
Hierarchy The name of the hierarchy (represented on the screen by a green tree symbol)
Description Short/Medium/Long
The descriptions of the hierarchy. You specify these only if the upload should simultaneously create a new hierarchy.
Characteristic The values of the characteristic are the nodes of the hierarchy; for example, items in item hierarchies,
consolidation groups in consolidation group hierarchies, or consolidation units in consolidation unit hierarchies.
From Value
The characteristic value for lower-level nodes or end nodes, or the beginning of a range of end nodes of the hierarchy.
The leaves of the hierarchy are generally the values of the characteristic being uploaded; for example, items in item
hierarchies, consolidation groups in consolidation group hierarchies, consolidation units in consolidation unit hierarchies.
To Value
4/20/2019
The end of a range of end nodes in the hierarchy. This entry is optional. If speci ed, all of the characteristic values within
the range are consecutively inserted into the hierarchy.
Attributes of hierarchy entries
If the hierarchy has attributes that are allocated to individual hierarchy entries, the system lists these attributes, as well.
In particular, hierarchies of consolidation groups and consolidation units contain attributes for rst consolidation and
divestiture accounting.
How to specify hierarchy information in the le

Precede each hierarchy entry in the le with the row type indicator 3 .
Make sure that each data row only contains data for one hierarchy entry – that is, for the higher-level node and the
lower-level node or end node. (Exception: You can enter a range of multiple end nodes.)
You should specify the hierarchy name only for assigning the top node.
Always specify nodes of the hierarchy in the eld that re ects the corresponding characteristic.
Always specify end nodes of the hierarchy in the From Value eld.
Arrange the sequence of the hierarchy exactly the way you want it displayed later on. Envision the desired result before
you start de ning the upload le.
Make sure that the characteristic values contained in the hierarchy indeed exist. (You can make sure this is the case by
uploading the values along with the hierarchy information.)
The desired result:
Example 1: Collecting a consolidation unit hierarchy
4/20/2019
To achieve this result, the upload le needs to be lled as follows. (Note that the remarks in parentheses are only intended to
relate the entry to the hierarchy drawing above, and are not a part of the le content.)
Example 1: Upload le
4/20/2019
(Note that instead of the single entry for (3->4-6) you could list each consolidation unit separately. Conversely, you could join
the last two entries into a single entry (7->8-9).)
Example 2: Collecting an item hierarchy, implicitly specifying the hierarchy

information via the hierarchy level
If each characteristic value occurs only once in the hierarchy and if no other characteristic besides the characteristic being
uploaded can appear in the hierarchy, then you use an easier way to specify the hierarchy information:
Add the characteristic Hierarchy Level to the eld catalog of the data rows.
List the data rows in the le in the sequence in which they should appear in the hierarchy later on.
Specify the hierarchy level for each row. Numbering starts with 1 for the top node that appears directly underneath the
hierarchy name (green symbol).
Caution
Hierarchy levels cannot be used to assign a top node to the hierarchy name. Either assign the top node manually in
the system or upload the assignment information separately as described beforehand (using row type indicator 3 ).
The desired result:
Example 2: Collecting an item hierarchy
4/20/2019
The upload le needs to have the following structure (assuming the use of no row type indicators, “*” (asterisks) as a comment
character, and only data rows):
4/20/2019
Example 2: Upload le
After the upload, you need to make the following assignments manually: B/S 10000000, B/S 20000000, I/S 37000000,
I/S 39000000.
Note
To see an example of how data collection of an item hierarchy affects an existing hierarchy in the system, read
Data Collection: Examples .
Enabling Approval Work ow for Flexible

Upload of Document
You can trigger an Approval Work ow within the Flexible Upload of Document function.
Con gure the following settings in Flexible Upload to enable it:
1. Set Input Type to Periodic
2. Set Update Mode to Overwrite or Do Not Modify
3. Assign Work ow Variant to the document type
4/20/2019
Load from Data Stream

Use
You can use this function to collect transaction data or master data and hierarchies from the BI system (SAP NetWeaver
Business Intelligence) or from connected SAP source systems to the consolidation system (SEM-BCS).
Integration
You can use the Load from Data Stream function as an alternative or in addition to the other data collection procedures.
Within the Load from Data Stream method you can use the Business Add-In ( BAdI) for data collection ( UC_DATATRANSFER) to
perform mapping activities that the method does not directly support - such as mapping source elds to target elds with a 1:n
relationship) . For more detailed information, see the system documentation of the BAdI UC_DATATRANSFER and the
documentation of its methods.
Prerequisites
To be able to load data from the BI system into the consolidation system, this data needs to be available in an InfoProvider
(transaction data) or an InfoObject (master data and hierarchies). For example, rst you need to have uploaded the EC-CS data
into the InfoProvider using an SAP BI upload procedure.
You need to create a source data basis to be used for loading from the data stream, and then specify that source data basis in
the data basis currently in use. You specify the following data in the source data basis:
InfoProvider from which you want to load the transaction data
InfoObject catalog that contains the InfoObjects from which you want to load master data and hierarchies
Features
When you customize the Load from Data Stream method, specify the InfoProvider for the transaction data, or the InfoObject for
the master data and hierarchies. Furthermore, you specify how the system is to map the characteristics and key gures of the
source data to the consolidation system. Finally, you can de ne source and target selections by specifying the source area (with
its characteristics and key gures) and the target area to be posted to in the data basis.
When the system executes the method, it writes the values to the target area of the data basis in accordance with the settings
you have made in Customizing. In doing so, it derives the values for consolidation-speci c characteristics (for example, the
posting level and the default values for subassignments when loading transaction data).
Loading of Transaction Data
You can load the following data from an InfoProvider (for example, an InfoCube or DataStore object) into the consolidation
system:
Note
4/20/2019
The data type Sequence of Activities includes the data streams Sequence of Activities and Activity Sorting. For more
information, see Automatic Data Collection of Activities.
Here are examples of SAP components you can load data from:
FI-GL, FI-SL, CO-PCA, and CO-PA
EC-CS
SEM-BPS
You can load data that is stored in an InfoProvider from a local or a non-local SAP BI system.
You are not restricted to accessing data that is stored directly in an InfoProvider. You can also access data which the BI system
merely references, without the data being physically stored in the BI system. For example, you can specify an InfoProvider that
obtains its data from a transactional SAP source system.
The structure of the InfoProvider that provides the source data may be different from the data structures of the data basis in
the consolidation system.
To load transaction data, assign the Load from Data Stream method to a data collection method that you then assign to a data
collection task (see Customizing for Load from Data Stream).
Loading of Documents
Whether the system can transfer the source documents 1:1 when loading documents depends on the structure of the source
InfoProvider and on the mapping. The system generates a new document number for the target document in every case. If the
source InfoProvider contains the Document Number characteristic and a mapping rule is de ned in the Load from Data Stream
method that assigns the source document numbers to the target document numbers, the system can transfer the documents
1:1. In this case, the system writes the source document number in the Reference Document Number characteristic in the
target document. Otherwise, the system uses the standard rules for posting documents (see also Automatic Data Collection of
Documents).
Loading of Master Data and Hierarchies
You load master data and hierarchies from individual InfoObjects. You are not restricted to accessing data that is stored directly
in an InfoObject of the BI system. You can also access data which the InfoObject merely references, without the data being
physically stored in the BI system (virtual InfoObject). For example, you can load the master data and hierarchies of
consolidation units from a transactional SAP source system.
For additional information, see Loading of Master Data from Connected SAP Systems.
Integrated Loading of Superordinate Fields
If you choose data type Assets/Liabilities (Master Data), you can specify that, in the case of a compound of characteristics, the
system is also to load independent (that is, superordinate) elds from the data stream. Using this function you can, for
example, load the asset main number together with the asset subnumber from the data stream.
Example
You have a decentralized corporation in which the transactional charts of accounts of the subsidiaries (FI-GL) differ to a limited
extent from the consolidation chart of accounts of corporate headquarters (SEM-BCS).
Each subsidiary runs an SAP BI upload into an InfoProvider.
4/20/2019
In the Mapping section of the method Load from Data Stream you can map the characteristics and key gures of a subsidiary to
the characteristics and key gures in SEM-BCS.
Mappings created in this way can be reused - either in part or in their entirety - for other subsidiaries.
You use a dedicated data collection task to transfer the data from the InfoProvider of the subsidiary to the consolidation area of
corporate headquarters.
Customizing for Load from Data Stream

Purpose
You use this process to de ne your Customizing settings for loading transaction data into the system.
To upload master data and hierarchies, you only need to de ne a method upload from data stream , execute the method in the
Consolidation Workbench, and save your changes. For additional information, see Loading of Master Data from Connected SAP
Systems .
Prerequisites
You have made your Customizing settings for the data basis and for the consolidation area that will accommodate the reporting
data, documents, and/or additional nancial data.
The data to be loaded is available in an InfoProvider.
You have created a source data basis and speci ed it in the data basis.
Process Flow
A. De ne the Task
De ne a task for data collection , or use an existing task.
B. De ning a Method
1. To create an upload from data stream method, go to the process view of the Consolidation Workbench and choose
Consolidation Functions Data Collection Upload from Datastream . In the lower left screen area, choose Create from
the context menu.
2. Assign a name and description for the method.
3. Specify the data type for the data to be loaded (for example, whether the data re ects documents or additional nancial
data).
4. Go to the Settings tab page.
a. Specify the source data basis and the InfoProvider.
The InfoProvider is a required entry in the source data basis.
b. Specify update mode. For more information, see Control of Data Collection Using Update Mode .
c. Specify whether the system should consider the debit/credit sign attributes that are de ned in Customizing for
nancial statement items and/or transaction types.
d. If you would like to upload reporting data or documents, set the input type.
4/20/2019
Choose the input type periodic if you want the system to post key gures periodically and the key gures from the
source InfoProvider contain period values.
Choose the input type cumulative if for the key gures in the current period you want the system to post only the
difference from the cumulative value of the previous period. If you choose the cumulative input type, the system
activates the indicator Also Read Data of Prior Periods .
Note
With the Also Read Data of Prior Periods indicator, you determine whether the key gures from the source
InfoProvider contain periodic or cumulative values.
Do not set this indicator if the key gures from the source InfoProvider contain cumulative values . In this
case, the system posts for the key gures in the current period only the difference from the cumulative
value from the prior periods.
Do set this indicator if the key gures from the source InfoProvider contain period values . In this case, the
system reads not only the period value for a key gure in the current period but also the period values
from previous periods of the scal year. This generates the cumulative value for all the prior periods. The
system needs this to post the difference between the key gures for the current period from the
cumulative value of the prior periods.
When you set the indicator, make sure that in mapping or using a Business Add-In (BAdI) the source
selections for the scal year and period can be derived from the target selection (through inverse
mapping).
e. If you want to use a BAdI implementation for data collection, specify the BAdI lter value.
5. Go to the Mapping tab page to de ne the mapping .
6. Choose the Selection tab page to adjust your settings for selection .
7. Save the method Load from Data Stream .
C. Assigning the Method
Assign the method Load from Data Stream to a data collection method .
If you select documents as the data stream in the data collection method, you also need to specify the document type.
Then assign the data collection method to the data collection task.
Result
Execute the method Load from Data Stream by running the data collection task in the consolidation monitor.
Check the log.
Periodic and Nonperiodic Copying

Use
You use this component when you want to copy the following data from the same consolidation area, a different consolidation
area, another version combination, or another group currency:
Reported nancial data (posting level 00)
4/20/2019
Features
You use one of the options listed below depending on whether you want to copy data periodically or nonperiodically (that is,
regularly or not):
Overview of Copying Options
Periodic/Nonperiodic Customizing Data Source/Data Target Status of Source Data Is Taken

into Account
Periodic Copy method, assigned to a Copies within the same Yes

copy task consolidation area, the same
consolidation unit or
combination of consolidation
units, and the same posting
period and scal year
Periodic Copy method, assigned to a Copies within the same No

data collection method, which is consolidation area or from
assigned to a data collection another consolidation area if
task necessary, across consolidation
units or combinations of
consolidation units, posting
periods, and scal years
Nonperiodic Copy function Copies within the same No

consolidation area
Copying to Another Group Currency
To copy to another group currency, in Customizing for the copy method or copy function, enter a currency translation method
that is to use a rounding method.
When copying documents, the system translates currency according to the mapping before posting documents in the target
data for each organizational unit and document type (see Automatic Data Collection of Documents). When posting documents
that are posted at group level, the system generally assigns any differences in rounding in a summary to the consolidation unit
(or combination of consolidation units). These differences are posted in the rst line of the document.
For more information, see the "Copying to Another Group Currency" section in Copy Task or see Consolidation in Multiple Group
Currencies.
Copying Documents in Consolidation of Investments
If, when documents are copied, there are differences between documents and totals records in the cumulative values in the
target environment, the system posts the difference values in correction documents and adjusts the cumulative values in the
documents to the cumulative values in the totals records.
If you have activated the business function Financials, Group Close, Restatement Monitor, the system posts these correction
documents with consolidation of investments activity 84 (Correction During Copy) when consolidation of investment
documents are copied.
Constraints
4/20/2019
Cumulative Copying of Documents
When copying documents cumulatively (the Cumulative checkbox is selected), the copy function reads the source data for the
current period from the documents data stream and the source data for previous periods in the same scal year from the
totals records data stream. If you only use the copy function for the last period, the target data for the previous periods are only
available as totals records. To fully map the documents from the previous periods in the target data, you must run the copy
function individually for each consolidation period of the scal year in chronological order.
Handling Canceled and Inverted Documents
When copying documents, the copy function does not read any canceled or canceling documents.
Inverted and inverting documents are read and further processed in the same way as other documents. If a currency translation
is to be carried out in the copy function, when dealing with inverted documents, the copy function uses the exchange rate from
the period of the inverted document. This ensures that no currency translation differences are generated.
Fiscal Year Variant
The source and target of the copy function must use the same scal year variant.
De ning a Copy Method

Use
You use this procedure to de ne a copy method.
You use the method to periodically copy reported nancial data, documents, or additional nancial data for all or individual
consolidation units within a consolidation area or from another consolidation area.
You can assign a copy method to a copy task , in which case the system also considers the status of the source data.
If you want to collect data from another consolidation area, you cannot use the copy task. Instead, you need to use a
data collection task.
As an alternative, you can assign the copy method to a data collection method (which you assign to a data collection task
). Then the system does not consider the status of the source data.
Procedure
1. To create a copy method, go to the process view of the Consolidation Workbench and choose Consolidation
Functions Data Collection Copy (Method) .
Alternatively, you can also create the copy method by choosing Consolidation Functions Copy Method .
In the lower left screen area, choose Create from the context menu.
2. Enter a short name and a medium name for the method.
3. Specify the data type (for example, reported nancial data or documents). If you want to use the copy method within a
copy task for copying different data streams, choose All Data Types .
Note
The data type Sequence of Activities includes the data streams Sequence of Activities and Activity Sorting .
The Activity Numbers data stream cannot be copied.
4/20/2019
4. On the Settings tab page, make the following settings:
a. Specify the update mode .
b. Specify whether the system should consider the debit/credit sign attributes that are de ned in Customizing for
nancial statement items and/or transaction types.
c. Specify the input type (cumulative or periodic).
d. If you want to use a BAdI implementation for data collection, specify the BAdI lter value. For more detailed
information, see the system documentation for the UC_DATATRANSFER BAdI and the documentation for its
methods.
5. On the Source/Target Version tab page, make the following settings:
a. Specify the source consolidation area, that is, the consolidation area from which the system reads the data when
executing the copy method.
Note
Copy methods that transfer data from another consolidation area must not be assigned to a copy task. To
execute in the consolidation monitor, you must use a data collection task.
b. Specify the source version (this is the version from which the data is copied).
c. Specify the target version (this is the version to which the data is copied).
d. Specify the source group currency.
e. Specify the target group currency.
f. If you want to perform currency translation for the data being copied, specify a currency translation method .
6. On the Mapping tab page, de ne a mapping if necessary.
Note
If you want to assign the copy method to a copy task, we recommend that you do not create mapping rules for the
consolidation unit, posting period, scal year, and other status-relevant elds.
However, if you want to assign the copy method to a data collection method, and assign the latter to a data collection
task, then you can create mapping rules for status-relevant elds.
7. On the Selection tab page, de ne a selection , if applicable.
8. Save the copy method.
See also:
Consolidation in Multiple Group Currencies
Local Currency Change for a Consolidation Unit
Copying of Restatement Data

Use
This function enables you to use copy tasks in the restatement monitor. The system provides support for status management
with regard to the source tasks of the copy task in the restatement monitor of the source environment.
4/20/2019
Prerequisites
A characteristic with the Restatement role must exist in the data model of the consolidation area used (see Creating
Restatement Characteristics).
Features
Copying Restatement Data Within a Consolidation Area
In Customizing for copy methods, you can specify a characteristic value for the source restatement and for the target
statement on the Source/Target Version tab page. You assign the copy method to a copy task.
When you execute the copy task, the system checks the status of the source tasks that you have speci ed in the Customizing
settings for the copy task. The system treats the source tasks in the source environment (which refers to the source
restatement in this case) as preceding tasks of the copy task.
Note
The restatement period that is de ned in the master data must occur after the execution period of the copy task.
The following possible scenarios exist for copying restatement data within a consolidation area:
Source Restatement Target Restatement Description
R0 R0 The system reads the original data from the source environment and copies it
as original data to the target environment.
R1 R0 The system reads the restatement data from the source environment and
copies it as original data to the target environment.
R1 R1 The system reads the restatement data from the source environment and
copies it as restatement data to the target environment.
Legend for the table:
R0: Original data
This data has already been published. You want to make a restatement for this data.
R1: Restatement data
This data contains corrections to the original data for which the restatement has been triggered. Data with a non-initial
restatement always contains the delta between the complete data and the original data.
R0 + R1: Both original data and restatement data (complete data)
If the characteristic values for the source and target restatement that you speci ed in the copy method are not identical, the
system displays a warning.
Copying Restatement Data Between Consolidation Areas
When you specify a source consolidation area on the Source/Target Version tab page, the system hides the Source
Restatement and Target Restatement columns on the Source/Target Version tab page. You enter the characteristics values
for the source restatement in the source selection on the Selection tab page. If required, you can also de ne mapping rules if a
restatement characteristic exists in the target environment.
4/20/2019
Note
You can assign this type of copy method only to data collection tasks, and not to copy tasks. In this case, you cannot specify
any source tasks. The system therefore cannot perform a status check in the source environment.
The following possible scenarios exist for copying restatement data between consolidation areas:
Source Restatement Target Restatement Description
R0 + R1 R0 The system reads the original data and the restatement data from the source
environment and copies it as original data to the target environment.
Does not exist R0 The system reads the data from a source environment in which no restatement
characteristic exists and copies it as original data to the target environment.
R0 (+ R1) Does not exist The system reads the original data (and restatement data) from the source
environment and copies it to a target environment in which no restatement
characteristic exists.
When the copy is executed, the system issues a warning if you copy data from a source environment in which there is no
restatement characteristic as restatement data (with a non-initial characteristic value for the restatement) to the target
environment (or vice versa).
Copy task
Use
You can use a copy task for the following purposes:
You can create a plan version based on current actual data.
You can translate data into a second group currency (see Consolidation in Multiple Group Currencies).
You can copy data to a different version to generate consolidated statements for other GAAPs (generally accepted accounting
principles), such as US-GAAP.
In a copy task, you cannot use any copy method that copies data from another consolidation area. Instead, use the data
collection method.
Integration
The task hierarchy is version dependent. You add the copy task to the task hierarchy of the target version; either as a
replacement of, or in addition to, a data collection task.
Only data streams that are de ned in the database are displayed in Customizing for the copy task.
If both the Sequence of Activities and Activity Sorting data streams are de ned in the database, the only the Sequence of
Activities data stream is displayed in Customizing for the copy task. Since the two data streams are closely related, when the
system carries out a copy task for the Sequence of Activities data stream, it copies both data streams.
The Activity Numbers data stream cannot be copied.
Prerequisites
4/20/2019
The data streams to be copied are de ned in the database.
The copy method you perform in the copy task has been created.
Features
General
When you assign a copy method to a copy task, you can copy the following data in the consolidation system (SEM-BCS)
periodically:
Documents
In the task's Customizing settings, you can determine which speci c data streams you want to copy (such as reported nancial
data, documents, inventory data, supplier data, investment data, equity data, equity holdings adjustments, goodwill).
How a copy method is carried out depends on the following settings:
Using the consolidation frequency, you determine in which periods the consolidation monitor performs the copy method.
Using the processing type, you determine the type of organizational unit for the copy method and therefore also determine the
usable data streams and posting levels for reporting data and documents. Assign the copy method to the organizational units
depending on your needs.
The following table shows each processing type the usable posting level for reporting data and documents as well as the usable
data streams for additional nancial data.
Processing Type Usable Posting Levels Usable Additional Financial Data
Per Consolidation Unit 00, 01, 10 All additional nancial data, but not data
streams:
Noncurrent assets (consolidated)
Sequence of activities
Activity sorting
Two-Sided 20 –
Per Consolidation Group 02, 12, 22, 30 Noncurrent assets (consolidated)
Independent of consolidation unit/group – Only data streams
Activity sorting
Using the period category, you can assign various copy methods depending on the period category. When performing a copy
method, the system checks which period category applies and performs the copy method assigned to that period category.
You ultimately assign the copy method that is to be processed when carrying out the task for the given period category. You also
determine for which organizational unit the copy task is to be performed. The range of organizational units depends on the
processing type.
4/20/2019
Note
The copy method must be compatible with the processing type. For example, if you choose the per consolidation unit
processing type, the copy method cannot copy reporting data with the posting level 00.
If you have made a target selection for the document type in the copy method, then the posting level for the selected
document type must match the posting level for the processing type.
Status of the Copy Task
When you assign a copy method to a copy task, the system takes the status of the source task into consideration. The
relationship between the status of the copy task and the status of the assigned source tasks is the same as the relationship
between the status of other tasks and their respective preceding tasks.
The following example illustrates the concrete relationships in status management:
 Example
You de ne the copy task C1 in version 200 and assign the source tasks S1 and S2 to the copy task in version 100.
You execute either task S1 or S2 in version 100. The system resets the status of copy task C1 in version 200.
Tasks S1 and S2 are blocked in version 100, and task C1 is blocked in version 200. Now you unblock either task S1 or S2
in version 100. As a result, the system unblocks copy task C1 in version 200.
To be able to block copy task C1 in version 200, the source tasks S1 and S2 need to be blocked in version 100.
For more information on status management for copy tasks, see Status Management in the Consolidation Monitor.
Copying to Another Group Currency
To copy into another group currency, enter a currency translation method in Customizing for the copy method that is to use a
rounding method. When performing a copy task, the system carries out the currency translation speci ed in the copy method.
The copy task consists of the following steps:
1. Read source data
2. If de ned: Execute mapping
3. If de ned: Execute the BAdI
4. Currency translation and rounding according to the currency translation method
5. Write target data in the target version
When totals data is copied, rounding differences can cause additional data rows. When documents are copied, additional
document line items can be created.
If you periodically copy data (that is not accumulated), you can create the opening balances by copying the associated totals
records one time only using the nonperiodic copy function.
If you copy the totals records cumulatively and copy documents at the same time, the system behaves as follows:
Totals records and documents are translated separately. However, documents are always translated periodically.
4/20/2019
Then the system compares the translated totals records with the sum of the translated documents. Here, the translation of
totals records takes precedence.
If a difference is found, the system creates a correction document. The document text denotes that this is a correction
document. The correction document is also listed in the copy task log.
When data is translated into another group currency, the copy task log shows the following in addition to the ordinary
information:
In the source data section: The group currency key of the source version
Error messages generated during currency translation
In the target data section: Rounding differences
If created: Correction documents
Activities
Customizing for copy tasks can be done in the process view of the consolidation workbench under Consolidation
Functions Copy Task .
Example
See Example: Consolidation in Two Group Currencies
De ning a Copy Task

Use
You use this procedure to de ne a copy task.
Prerequisites
You have created a copy method.
Procedure
To create a copy task, go to the process view of the Consolidation Workbench and choose Consolidation Functions Copy Task .
Enter a key for the copy task.
Enter a short name and a medium name for the copy task.
You can assign a consolidation frequency to the copy task.
If you do not assign a consolidation frequency, the task is executed in the consolidation monitor in each consolidation period
(according to the consolidation frequency that is de ned for the version combination).
De ne the processing type.
4/20/2019
Using the processing type, you determine the type of organizational unit for the copy method and therefore also determine the
usable data streams and posting levels for reported nancial data and documents. Assign the copy method to the
organizational units depending on your needs.
Specify which data streams you want to copy with this copy task.
Note
The data streams available depend on the processing type (see below).
Optional: Specify one or more source tasks.
When you assign a source task, the system checks the status of the source data. In contrast, a data collection task with a copy
method generally does not check the status of the source data.)
Note
The source tasks must use the same processing type as the copy task.
Assign the method for each relevant period category. To do this, select each period category separately. See also the section
"Assign Methods for Period Categories" in De ning a Data Collection Task.
Note
If you have made a target selection for the document type in the copy method, then the posting levels for the selected
document types must match the posting levels for the processing type.
If you selected the Two-sided or Per Consolidation Group processing type, assign the copy method and, in the Consolidation
Group, select the consolidation groups for which the copy task is to be executed in the consolidation monitor. You can make
complex selections (see Single Selection).
If you selected the Independent of Consolidation Unit/Group processing type, assign the copy method only.
If you add the copy task to the task sequence, it is assigned to the top node of the consolidation units hierarchy in the
consolidation monitor.
If you selected the Per Consolidation Unit processing type and set the Independent of Consolidation Unit(s) option under Assign
Method, the copy task is executed in the consolidation monitor for all consolidation units or combinations of consolidation units.
Otherwise, proceed as follows for the Per Consolidation Unit processing type:
Specify all consolidation units or combinations of consolidation units that are valid in the hierarchy.
By default, the system sets the Relevant indicator for each consolidation unit or combination of consolidation units.
Specify a copy method for each consolidation unit or combination of consolidation units (you can specify different copy
methods) or deselect the Relevant indicator.
Note
At the time of task execution, for each consolidation unit you either need to have speci ed a copy method or may not have
selected the Relevant indicator. If this is not the case (for example, because the consolidation unit was not speci ed at all),
the system displays an error message because of the missing method assignment. Reasoning: You can explicitly exclude
consolidation units from processing. However, typically all consolidation units are always automatically processed.
4/20/2019
Specify your preferences for the task log:
Specify whether you want to save the log of the last task execution in update mode.
Specify whether the log should be displayed when the task is executed.
Save the copy task.
Result
You can add the copy method in the Task Sequence and execute it in the consolidation monitor.
Executing the Copy Task

Use
You use this procedure to execute a copy task in the consolidation monitor.
Prerequisites
You have de ned a task in Customizing. You have assigned a task hierarchy to this task.
Procedure
1. Run the Consolidation Monitor.
2. Start the copy task for one consolidation unit or for one consolidation group, in update mode.
The system (not the user) uses the following procedure:
When copying totals data:
1. The system selects the totals data of the relevant consolidation units and posting levels in the source version.
2. The version is set to target version.
3. If applicable, the system translates the totals data into another group currency.
4. In the target version, the system deletes the existing totals data of the relevant consolidation units and posting levels.
5. The system adds the copied totals data into the target version.
When copying documents:
1. The system selects the documents of the relevant organization units and document types in the source version.
3. If applicable, the system translates the documents into another group currency.
4. In the target version, the system deletes the existing documents of the relevant organization units and document types.
5. The system adds the copied documents into the target version.
When copying additional nancial data:
4/20/2019
1. The system selects the additional nancial data of the relevant consolidation units in the source version.
3. This step depends on whether the data was already copied and an activity number was used:
If data was already copied, the activity number is retained.
If data was not yet copied, the system assigns a new activity number.
4. In the target version, the system deletes the existing totals data of the relevant consolidation units.
5. The system adds the copied additional nancial data into the target version.
Nonperiodic Copying
Use
You use this function to copy the following types of data from another version combination or another group currency within the
same physical data stream of a data basis and within a consolidation area:
Integration
After making your Customizing settings for nonperiodic copying in the Consolidation Workbench, you execute the function in the
Consolidation Workbench, as well.
Differences to Periodic Copying
The status management function is not available for nonperiodic copying because you execute nonperiodic copying in the
Consolidation Workbench (in contrast to periodic copying, which you execute in the Consolidation Monitor).
If, instead of nonperiodic copying of data, you want periodic copying, use the copy method . You can also copy data from another
consolidation area if the following applies: You assigned the copy method to a data collection method , and you assign this
method to a data collection task that you execute in the consolidation monitor.
Nonperiodic copying supports simple selections only, whereas periodic copying supports complex selections , as well.
Prerequisites
The data stream you want to copy has been de ned in the data basis.
If you want to copy data to another version, the target version must already be de ned.
Features
The Consolidation Workbench offers a different selection screen for each data stream used in a given consolidation area. You
can save your selection screen settings as a variant, and load the saved variant as desired.
4/20/2019
You enter the source and target parameters for the copy process in the Parameter Changes group box. In the From column, you
enter the source parameters, such as, the version from which you are copying the data. In the To column, you enter the target
parameters, such as, the version to which you want to copy the data. The system shows the permanent parameters of the
consolidation area, both for the source and for the target. Of these parameters, you can use the following for selecting the
source and target:
Version
A common scenario here is copying an actual version to a plan version.
Currency key for group currency
If you want to copy data to a different group currency, enter the translation method in the Currency Translation Method
eld.
Posting period and scal year
You can use a copy process to copy data for a period, for instance from 2005/003 to 2006/003.
To copy data from multiple periods, proceed as follows:
Only for the data streams Reported Data , Documents and Sequence of Activities, you can set the Cumulative
indicator. If you set this indicator, the system selects all data records with the corresponding key up to, and
including, the speci ed period. If it is not set, only the data records of the speci ed period are selected.
For the other data streams, you have to explicitly execute the copy process for each individual source period.
In the Organizational Units group box of the selection screen (for all data streams except sequence of activities), select the
organizational units for which you want to copy data.
The Selection group box on the selection screen offers additional characteristics you can use to limit the data selection.
In the Technical Settings group box on the selection screen, you can specify if the system executes the copy function as a test
run or an update run. You can also specify if the system logs the changes made using nonperiodic copying.
Activities
1. In the process view of the Consolidation Workbench, go to Consolidation Functions Other Functions Copy , and select
the data stream you want to copy.
2. Specify the source and target parameters in the selection screen and make any restrictions to the characteristic values.
3. Choose Execute .
The system executes nonperiodic copying.
Deletion – Periodic and Nonperiodic

Purpose
You use this component to delete transaction data in the consolidation system (SEM-BCS). You can delete the following types of
data:
Documents with posting levels 01, 02, 10, 12, 20, 22, or 30
4/20/2019
Implementation Considerations
There are two methods of deletion: periodic (for regularly scheduled deletions in the Consolidation Monitor) and nonperiodic
(for “ad-hoc” deletions in the Consolidation Workbench).
You can use periodic deletion, for example, to make sure certain kinds of data are deleted prior to data entry.
You typically use nonperiodic deletion to correct unexpected errors discovered during data collection.
Integration
To perform periodic deletion, in the Consolidation Workbench you de ne a deletion method , assign the deletion method to a
data collection method , which, in turn, you assign to a data collection task . You execute the task in the Consolidation Monitor.
To perform nonperiodic deletion, you de ne and execute a function with a selection screen in the Consolidation Workbench (see
Nonperiodic Deletion ).
Features
Deletion of Reported Financial Data
To delete reported nancial data with posting level 00, you choose the data type Reported Financial Data. The function
processes the selected data as follows:
Input Type System Behavior
Periodic The system resets to zero the period value of the selected period
in the InfoCube for totals records. A document is not created.
Cumulative The system overwrites the period value of the selected period in
the InfoCube for totals records so that the cumulative value equals
zero. A document is not created.
Deletion of Documents with Posting Levels 01, 02, 10, 12, 20, 22, or 30
To delete documents that have the posting level 01, 02, 10, 12, 20, 22, or 30, you choose the data type Documents. The function
processes the selected documents as follows:
Reversal or deletion of documents
How documents are processed depends on the setting you have made for repetition runs in Customizing for version
combinations. The version combination or the document type determines whether a document is deleted or reversed.
For more information, see “De nition of Valid Version Combinations” in Customizing of Versions .
For cumulative deletion only: Inversion of Documents of Prior Periods (if applicable)
The document type determines whether documents of prior periods are inverted (see also “Inversion” in Document Type
).
For cumulative deletion only: Creation of correction documents (if applicable)
Resulting adjustments to totals data
The following table shows how the input type and the document type determine how documents are deleted:
Input Type System Behavior
4/20/2019
Periodic The selected document is either deleted or reversed.
As a result, the system resets to zero the period value of the

selected period in the InfoCube for totals records.
Cumulative The selected document is either deleted or reversed.
If automatic inversion is set in the document type, the system

inverts the documents of the prior periods.
When necessary, the system creates a correction document in the

selected period to reset the cumulative value to zero.
As a result, the system overwrites the period value of the selected

period in the InfoCube for totals records so that the cumulative
value equals zero.
Deletion of Additional Financial Data
To delete additional nancial data, you choose the appropriate data type. The system deletes the additional nancial data for
the selected period.
Deletion of additional nancial data has no effect on the totals records or documents.
Activities
If you choose the Sequence of Activities data type, the system deletes the data of the selected period in both the Sequence of
Activities data stream and the Activity Sorting data stream.
You can not delete data in the Activity Numbers data stream.
Constraints
The consolidation system cannot permanently delete data records that reside in an InfoCube. Since totals records are stored in
an InfoCube, the system merely resets the totals data in the InfoCube back to zero. You can use functions in SAPNetWeaver
Business Intelligence (BI) to permanently delete totals records.
Example
This example shows the effects of deletion of entries with posting levels 01, 02, 10, 12, 20, 22, or 30 on the Totals Records and
Documents data streams, how these effects are dependent on the input type, and how cumulative deletion is dependent on
whether automatic inversion has been de ned for the given document type.
Task at Hand
You want to delete the postings with document type D1 for the period 006 . The following totals records and documents
currently have document type D1 :
Period Doc. Type Item Period Value in Local Period Value in Group
Currency Currency
000 D1 (Asset) 300 2,400
003 D1 (Asset) 50 400
006 D1 (Asset) 100 800
Period Doc. Type Doc. Number Item Period Value in Local Period Value in
4/20/2019
Currency Group Currency
003 D1 38000 (Asset) 50 0
006 D1 38001 (Asset) 100 0
Deletion with Input TypePeriodic
Deletion with input type periodic creates a document 38002, which reverses document 38001. As a result, the system resets to
zero the period value of the selected period in the InfoCube for totals records. After the deletion function, the totals records and
documents with document type D1 look as follows:
Currency Currency
000 D1 (Asset) 300 2,400
003 D1 (Asset) 50 400
006 D1 (Asset) 0 0
003 D1 38000 (Asset) 50 0
006 D1 38001 (Asset) 100 0
006 D1 38002 (Asset) –100 0
Documents 38001 and 38002 reference each other.
Deletion with Input TypeCumulativeand Automatic Inversion
When input type cumulative and automatic inversion are set, deletion of data with document type D1 creates the following
documents:
Document 38002 reverses document 38001.
Document 38003 inverts document 38000.
Document 38004 ensures that the cumulative value in the InfoCube for totals records equals zero.
As a result, the system overwrites the period value of the selected period in the InfoCube for totals records so that the
cumulative value equals zero. After the deletion function, the totals records and documents with document type D1 look as
follows:
Currency Currency
000 D1 (Asset) 300 2,400
003 D1 (Asset) 50 400
006 D1 (Asset) –350 –2,800
4/20/2019
003 D1 38000 (Asset) 50 0
006 D1 38001 (Asset) 100 0
006 D1 38002 (Asset) –100 0
006 D1 38003 (Asset) –50 0
006 D1 38004 (Asset) –300 0
Documents 38001 and 38002 reference each other, as do documents 38000 and 38003.
Deletion with Input TypeCumulativeWithout Automatic Inversion
When input type cumulative and no automatic inversion are set, deletion of data with document type D1 creates the following
documents:
Document 38002 reverses document 38001.
Document 38003 ensures that the cumulative value in the InfoCube for totals records equals zero.
As a result, the system overwrites the period value of the selected period in the InfoCube for totals records so that the
cumulative value equals zero. After the deletion function, the totals records and documents with document type D1 look as
follows:
Currency Currency
000 D1 (Asset) 300 2,000
003 D1 (Asset) 50 400
006 D1 (Asset) –350 –2,400
003 D1 38000 (Asset) 50 0
006 D1 38001 (Asset) 100 0
006 D1 38002 (Asset) –100 0
006 D1 38003 (Asset) –350 0
Documents 38001 and 38002 reference each other.
De ning a Deletion Method

Use
You use this procedure to de ne a deletion method.
You use deletion methods to periodically delete transaction data in the consolidation system (SEM-BCS). For more information,
see Deletion – Periodic and Nonperiodic .
Prerequisites
4/20/2019
You can delete consistent data only. To eliminate data inconsistencies, see Analysis and Repair of Data Streams .
Procedure
Create a Deletion Method
1. To create a deletion method, go to the process view of the Consolidation Workbench and choose Consolidation
Functions Data Collection Delete (Method) .
2. Enter a short name and a medium name for the method.
3. Specify the data type.
Note
The data type Sequence of Activities includes the data streams Sequence of Activities and Activity Sorting .
You can not delete data in the Activity Numbers data stream.
4. On the Selection tab page you can de ne a selection for reported nancial data and documents.
If you do not use a selection to restrict the data when executing a periodic deletion in the Consolidation Monitor, the
system deletes all of the data of the current period.
5. On the Settings tab page you can specify the input type for reported nancial data and documents.
6. Save the new deletion method.
To run the deletion method periodically, assign the deletion method to a data collection method . Then assign the data collection
method to a data collection task .
When you delete documents, specify the document type in the data collection method.
Result
When you execute the method in the Consolidation Monitor, the system deletes the selected data in the current period.
When deleting documents, the system creates reversal, inversion, and correction documents (when applicable). For more
information, see Deletion – Periodic and Nonperiodic .
Nonperiodic Deletion
Use
You use this function to delete transaction data in the consolidation system.
For more information, see Deletion – Periodic and Nonperiodic .
Integration
After making your Customizing settings for nonperiodic deletion in the Consolidation Workbench, you execute the function in the
Consolidation Workbench, as well.
4/20/2019
Differences to Periodic Deletion
The Status Management in the Consolidation Monitor function is not available for nonperiodic deletion because you execute
nonperiodic deletion in the Consolidation Workbench (in contrast to periodic deletion, which you execute in the Consolidation
Monitor).
Nonperiodic deletion supports simple selections only, whereas periodic deletion supports complex selections , as well.
Prerequisites
The data stream you want to delete has been de ned in the data basis.
The data you want to delete is consistent. To eliminate inconsistencies, see Analysis and Repair of Data Streams .
Features
The Consolidation Workbench offers a different selection screen for deletions for each data stream used in a given consolidation
area. You can save your selection screen settings as a variant, and load the saved variant as desired.
You can execute the function in test mode and log your changes.
Activities
1. In the process view of the Consolidation Workbench, go to Consolidation Functions Other Functions Delete , and select
the data stream you want to delete.
2. Specify the target selection on the selection screen.
3. Choose Execute .
The system performs the deletion.
Example
See the example in section Deletion – Periodic and Nonperiodic .
Automatic Data Collection of Documents

Overview
You can use the following procedures for automatically collecting documents of all posting levels:
Flexible upload
Copy
In addition to collecting the documents in the data stream Documents , automatic data collection of documents updates the
totals data in the data stream Totals Records .
Note
4/20/2019
You can collect documents even if the data stream Documents is not de ned in the data basis. In this case, the system only
updates the totals data in the data stream Totals Records .
Constraints
Flexible upload of documents with posting level 30 (business application Consolidation of Investments ) does not allow you to
transfer the activity number of the source document. For more information, see Automatic Data Collection of Activities .
Standard Rules for Writing Documents

If the system is not able to replicate the documents of the source data to the documents in the target data with a one-to-one
(1:1) relationship, then which documents are written depends on their posting level and document type . The table that follows
shows which rules the system uses when writing documents:
Posting Level Written in Target Data
01, 10 One document per consolidation unit and document type
20 One document per consolidation unit/partner unit and document

type
02, 12 One document per consolidation group and document type
22 One document per consolidation group/consolidation unit and

document type
30 Depends on the business application de ned in the document

type:
Consolidation of investments: One document per

consolidation group/investee unit and document type
All other business applications:One document per

consolidation group and document type
 Example
In the following example, the source data has the following data records with posting level 20 (two-sided elimination entries
with the key elds Consolidation Unit and Partner Unit ):
Document Number Consolidation Unit Partner Unit …
Not available C1000 C2000 …
Due the missing document numbers, the source data cannot be written to the target data with a one-to-one (1:1) relationship.
Thus, the system writes the documents using the aforementioned rules. The two records with the pair C1000/C2000 are
written as one document. The same applies to the two records with the pair C1000/C3000 .
Document Number Consolidation Unit Partner Unit …
4/20/2019
Generated C1000 C2000 …
Reference Document Number

If the system is able to collect and write the documents with a one-to-one (1:1) relationship (for example, when copying
documents of the current period), the system saves the number of the source document in the target document in
characteristic Reference Document Number (InfoObject 0BCS_DOCNRR). The document number of the target document is
generated by the system. The reference document number allows you to refer back to the source document.
Collect Activity Data Automatically

Overview
The following table shows which automatic data collection procedures are suitable for transferring data for data streams that
use activity numbers for consolidating investments.
Data Stream Flexible Upload Load from Data Stream Copy
Documents (posting level 30, (X) X X

Consolidation of Investments
application)
Investments (X) X X
Equity (X) X X
Result (X) X X
Goodwill (X) X X
Sequence of Activities – X X
Activity sorting – (together with sequence of activities)
Activity numbers – X implicit
Note on (x): The system cannot collect activity numbers from the source data.
If you would only like to load the equity , investments , and/or results data streams, then the source activity number does not
necessarily have to be available. When loading, the system creates new activity numbers which you can match afterwards by
running an activity numbers match .
Note
If the source data contains automatic goodwill entries, then the system ags these entries in the target data as manual
goodwill entries.
Please note the following prerequisites and restrictions for the various data collection procedures.
Flexible Upload
4/20/2019
With the exible upload , you can upload data for data streams that use activity numbers (provided the data streams are
de ned in the database), however, you cannot do this for the activity sequence, activity sorting, and activity numbers data
streams.
When uploading data for the equity, investments, results, goodwill, and documents (posting level 30, Investment Consolidation
application) data streams, you cannot collect the activity numbers from the source data.
It is not possible to upload automatic goodwill entries.
For more information on migrating investment consolidation data from EC-CS, see Migrating Investment Consolidation Data
from EC-CS to SEM-BCS

Load from data stream loads all data streams that use activity numbers, including the data streams Sequence of Activities,
Activity Sorting, and Activity Numbers (provided the data streams are de ned in the data basis).
The data streams Sequence of Activities and Activity Sorting are interconnected. The system loads both data streams when
you choose data type Sequence of Activities in the Customizing settings for the Load from Data Stream method.
General Approach
If you want to use Load from Data Stream to load data streams that use activity numbers, you must load the Activity Numbers
data stream rst. Subsequently, the system generates new activity numbers and saves the source activity number of each new
activity number (along with the logical name of the source system).
The system adopts the logical name of the source system (in which the activity numbers were originally assigned) from the
source data basis. If the logical system is not speci ed, the system checks whether the InfoProvider you speci ed in the Load
from Data Stream method as the source is used as a regular DataStore object in a regular data basis of the local system. If this
is true, the system uses the logical name of the local system. Otherwise, the system issues an error message.
Note
If the activity numbers were not generated in the local system, you specify the logical name of the source system that
generated the activity numbers in the Customizing settings of the source data basis on the Field Catalog tab page. This may
be necessary, for example, when collecting consolidation of investments data from EC-CS or from a separate SEM-BCS
system.
The system requires references to the source activity numbers to be able to match the source activity numbers of the other
data streams to the target activity numbers already assigned.
Note
Mapping of the Load from Data Stream method for all subsequent loads must be consistent with the mapping for loading
the activity numbers. This particularly applies to the mapping of the activity number.
To ensure that the relationship between the data types involved in a given activity is preserved, the source activity numbers
need to be available for the following data streams, and you need to match them with the target activity numbers in the
mapping of the Load from Data Stream method:
Sequence of Activities and Activity Sorting
Documents (posting level 30, Consolidation of Investments application)
Goodwill
4/20/2019
If the source data contains automatic goodwill entries (which are marked as manual goodwill entries), you also need to
load the data streams of the additional nancial data that triggered the generation of the automatic goodwill entries.
The source activity numbers need to be available for these data streams as well, and you need to match them with the
target activity numbers in the mapping of the Load from Data Stream method.
Copy
The copy function copies all data streams that use activity numbers, including the data streams Sequence of Activities and
Activity Sorting (provided the data streams are de ned in the data basis).
The data streams Sequence of Activities and Activity Sorting are interconnected. The function copies both data streams when
you choose data type Sequence of Activities in the Customizing settings for the copy method or for nonperiodic copying . You
also can choose All Data Types in the copy method.
Note
You have the option to map source elds to target elds in the copy method. (By default, the elds are adopted on a one-to-
one (1:1) basis.) Mappings must be consistent for all data streams that you copy and that use activity numbers. This
particularly applies to the mapping of the activity number.
When you copy data streams with activity numbers, the function rst copies the Activity Numbers data stream to be able to
portray the activities in the target data in a consistent manner (as in Load from Data Stream). Whether the function adopts the
activity numbers or assigns new activity numbers depends on the given situation. The following table shows this relationship:
Given Situation Treatment of Activity Numbers
Copy between versions within the same consolidation area The function adopts the activity numbers from the source version.
Copy between group currencies within the same consolidation area The function generates new activity numbers and saves the source
activity number of each new activity number (along with the logical
name of the source system).
Copy from a different consolidation area The function generates new activity numbers and saves the source
activity number of each new activity number (along with the logical
name of the source system).
Data Collection Method

De nition
Grouping of multiple data collection procedures into a data collection method
Use
You use the data collection method to integrate the following data collection procedures for reported nancial data (totals
records), documents, and additional nancial data into a data collection task so that you can execute it periodically in the
consolidation monitor:
Manual Data Entry of Reported Financial Data
Manual Data Entry of Additional Financial Data
4/20/2019
Flexible Upload
De ning a Copy Method
De ning a Deletion Method
Structure
You can combine various data collection procedures to form a data collection method. The table below gives examples of the
grouping of several data collection procedures to form a data collection method.
Example of a data collection method
Data stream Data collection Method/data Doc. type Pres. server Log. le File name
procedure entry group
Totals records Man. entry GRP01
Totals records Flex. upload FLX01 X C:\upl.txt
Inventory data Man. entry -
Supplier data ... ... ...
You must assign a data stream type to each data collection procedure. Further speci cations are required depending on the
data collection procedure in question. The table below indicates which speci cations are required for the individual data
collection procedures.
Data to enter for data collection method
Data collection Method/data entry Doc. type Pres. server Log. le File name
procedure group
Man. entry of Entry group

reported nancial
data
Man. entry of
additional reporting
data
Flexible upload Upload method XD X X X
Load from data Load from data XD

stream stream method
Copy Copy method
Delete Deletion method
Legend: X = required, X D = for document data collection only
No speci cations are required for the manual entry of additional reporting data because the data entry screens are prede ned
and xed.
The following speci cations are required for the exible upload:
You use the Presentation Server eld to de ne whether the File Name eld is for specifying a path on the presentation
server or a path on the application server.
4/20/2019
You use the Logical File eld to de ne whether the File Name eld represents a logical le name or a physical le name.
Logical le names consist of variables whose values are determined by the system during the execution of the upload.
This means that several physical le names can be derived from a single logical le name. You de ne logical le names in
transaction FILE. The consolidation system (SEM-BCS) provides the following parameters for use in logical le names:
PARAM_1: The name of the consolidation unit for which the upload is to be executed (the rst consolidation unit in
the eld list of the consolidation area)
PARAM_2: The name of the consolidation unit for which the upload is to be executed (the second consolidation
unit in the eld list of the consolidation area); this parameter is for matrix organizations only
PARAM_3: The scal year and period in which the upload is to be carried out, for example 200609
In the File Name eld, you specify the logical or physical le name (= path + le name, for example
C:\temp\upload_1.txt).
Note the following for the automatic data collection of documents:
In the case of the data collection procedures Flexible Upload and Load from Data Stream, you must specify the
document type in the data collection method.
In the case of the copy method, you do not specify the document type in the data collection method. Instead, you can
restrict the document type using the target selection in copy method customizing.
Integration
You assign the data collection method to a data collection task. This assignment results in restrictions for grouping together
data collection procedures into a data collection method. For further information, see Processing Type in Data Collection Task.
Example
Use of logical le names for exible upload
You want to load different les for each consolidation unit and each period. With this purpose, you create an entry for the
exible upload in the data collection method. You select the Presentation Server and Logical File indicators and enter the
logical le name SEMBCS_FILE.
SEMBCS_FILE is de ned as follows in the system: <PARAM_1><PARAM_3>.txt. The logical path SEMBCS_PATH is speci ed in
SEMBCS_FILE and points to the physical path c:\temp in Microsoft Windows systems.
When the data collection method for consolidation unit C1000 is executed in the scal year of 2006, period 09, the system
determines the following physical le name on the presentation server for the exible upload: c:\temp\C1000200609.txt.
Data Collection Task

Use
You use data collection tasks to execute data collection methods in the consolidation monitor.
Integration
Data collection tasks are linked to the task hierarchy of the consolidation area.
4/20/2019
To be able to use a data collection task, you have to create a data collection method . You need the data collection method to
link to automatic data collection procedures, such as methods for exible upload or loading from the data stream , or to
manually enter additional nancial data.
Features
How a data collection task is carried out depends on the following settings:
Using the consolidation frequency , you determine in which periods the consolidation monitor performs the data
collection task.
Using the processing type, you determine the type of organizational unit for the data collection and therefore also
determine the usable posting levels for data collection of totals data and documents. Dependent on this setting, you
assign organizational units to the data collection method. For more information, see the section "Processing Type."
Using the period category , you can assign various data collection methods with a dependency on the period category
(see the example in the section "Assign Methods for Period Categories" in De ning a Data Collection Task ). When
executing a data collection task, the system checks which period category applies and executes the data collection
method assigned to that period category.
You assign the data collection method that is to be processed when carrying out the task for the given period category.
For each data collection method, you specify the organizational units on which it should be used. The range of
organizational units depends on the processing type.
Processing Type
The consolidation monitor executes a task either on consolidation groups or on consolidation units. The processing type is
determined by the organizational unit for the data collection. This also affects the method assignment, the posting levels that
can be used for reported nancial data and documents, as well as the additional nancial data.
The following table shows the method assignment and its dependence on the processing type:
Processing Type Method Assignment
Per consolidation unit The data collection task is executed in the consolidation monitor,
either for all consolidation units or combination of consolidation
units, or for those that you entered in the Assignment of Methods
group box. (Prerequisite: You designated that the consolidation unit
or combination of consolidation units are relevant, and assigned a
data collection method to them.)
Two-sided The data collection task, and thereby the data collection method,
that you entered in the Assignment of Methods group box is
executed in the consolidation monitor for the consolidation groups
that you entered in the Consolidation Group group box.
Per consolidation group The data collection task, and thereby the data collection method,
that you entered in the Assignment of Methods group box is
executed in the consolidation monitor for the consolidation groups
that you entered in the Consolidation Group group box.
Independent of consolidation unit/group With this processing type, the data collection method is only
allowed to contain the data streams for Sequence of Activities,
Activity Sorting, and Activity Numbers ( not for the copy method).
The data collection task is executed in the consolidation monitor

for the top nodes of the consolidation unit hierarchy.
4/20/2019
The following table shows, for each processing type, the usable posting levels for data collection of reported nancial data and
documents, as well as the usable data streams for data collection of additional nancial data.
Processing Type Usable Posting Levels Usable Additional Financial Data
Per consolidation unit 00, 01, 10 All additional nancial data, but not data
streams
Noncurrent assets – consolidated
Activity sorting
Note: You can manually enter the

sequence of activities in this
processing type.
Two-sided 20 –
Per consolidation group 02, 12, 22, 30 Noncurrent assets – consolidated
Independent of consolidation unit/group – Only these data streams:
Activity sorting
Activity numbers ( not for the copy

method)
Note
The data collection procedure you use must be compatible with the processing type. Example: If you choose the Per
Consolidation Group processing type, then the data collection procedures are not allowed to copy reported nancial data
with posting level 00 or documents with the posting levels 01, 10 and 20.
Activities
You can make Customizing settings for data collection tasks in the process view of the consolidation workbench by choosing
Consolidation Functions Data Collection Task. For more information, see De ning a Data Collection Task .
De ning a Data Collection Task

Use
You use this procedure to de ne a data collection task.
Prerequisites
You have created a data collection method.
Procedure
Proceed as follows to de ne a data collection task:
4/20/2019
In the process view of the consolidation workbench, choose Consolidation Functions Data Collection Task . In the lower left
screen area, choose Create from the context menu.
Enter a key for the data collection task.
Enter a short name and a medium name for the data collection task.
You can assign a consolidation frequency to the data collection task.
If you do not assign a consolidation frequency, the task is executed in the consolidation monitor in each consolidation period
(according to the consolidation frequency that is de ned for the version combination).
De ne the processing type (see the section "Processing Type" in Data Collection Task).
Assign the method for each relevant period category. To do this, select each period category separately. See the section "Assign
Methods for Period Categories."
If you selected the processing type Two-sided or Per Consolidation Group , assign the data collection method and, in the
Consolidation Group group box, select the consolidation groups for which the data collection task is to be executed in the
consolidation monitor. You can make complex selections (see Single Selection ).
If you selected the Independent of Consolidation Unit/Group processing type, assign the data collection method only.
If you add the data collection task to the task sequence, it is assigned to the top node of the consolidation units hierarchy in the
consolidation monitor.
If you selected the Per Consolidation Unit processing type and set the Independent of Consolidation Unit(s) option under Assign
Method, the data collection task is executed in the consolidation monitor for all consolidation units or combinations of
consolidation units.
Otherwise, proceed as follows for the Per Consolidation Unit processing type:
Specify all consolidation units or combinations of consolidation units that are valid in the hierarchy.
By default, the system sets the Relevant indicator for each consolidation unit or combination of consolidation units.
Specify a data collection method for each consolidation unit or combination of consolidation units (you can specify different
data collection methods) or deselect the Relevant indicator.
Note
At the time of task execution, for each consolidation unit you either need to have speci ed a data collection method or may
not have selected the Relevant indicator. If this is not the case (for example, because the consolidation unit was not speci ed
at all), the system displays an error message because of the missing method assignment. Reasoning: You can explicitly
exclude consolidation units from processing. However, typically all consolidation units are always automatically processed.
Specify your preferences for the task log:
Specify whether you want to save the log of the last task execution in update mode.
Specify whether the log should be displayed when the task is executed.
Save the data collection task.
Result
4/20/2019
You can add the data collection method to the task sequence and execute it in the consolidation monitor.
Example
Assign Methods for Period Categories
In a data collection task, you want to use the consolidation frequency Quarterly (with closing periods 003, 006, 009, 012). For
the last quarter of the scal year, you want to assign a different data collection method than for the rst three quarters.
Proceed as follows:
In the process view of the consolidation workbench, choose Consolidation Functions Data Model Periodicity Period Category .
De ne a period category group with these period categories: First Three Quarters (periods for posting 003, 006 and 009) and
Last Quarter (period for posting 012).
Save your settings.
In the process view of the consolidation workbench, choose Consolidation Functions Data Collection Task .
Create a data collection task. De ne names for it, choose the consolidation frequency Quarterly, and specify the processing
type.
From the dropdown box for the period category, choose the entry Period Category of Other Period Category Groups. Choose
First Three Quarters from the list.
Afterward, the dropdown box Period Category contains not only the entry First Three Quarters, but also the entry Last Quarter
(the dropdown box always displays the period categories that belong to the same period category group).
Choose the period category First Three Quarters and assign the data collection method for the rst three quarters to it.
Select the period category Last Quarter.
The system remembers the method assignment for the rst three quarters, and hides it now in the display, so that you can
make your assignments for the last quarter.
Assign the data collection method for the last quarter.
Note
The system keeps track of your changes for period categories of the same period category group, as long you do not choose
a different period category group.
To display or change your settings for the rst three quarters, choose period category First Three Quarters.
To display or change your settings for the last quarter, choose period category Last Quarter.
Save the data collection task.
When executing a data collection task in the consolidation monitor, the system checks which period category applies and
executes the data collection method assigned to that period category.
Overview Screen for Data Collection

4/20/2019
De nition
This screen provides an overview of all methods and manual procedures that belong to a data collection task. From here you can
execute the methods or manual procedures.
Structure
The data collection overview screen appears when you execute a data collection task in the consolidation monitor for a given
consolidation unit or consolidation group.
The methods and manual procedures that belong to the task are arranged on this overview screen (according to your
customizing settings). You can use these methods and procedures to transfer reported nancial data, adjustment and
standardizing entries, and additional nancial datainto the consolidation system.
You can execute individual methods or manual procedures by choosing the respective symbol in the Execute column. As an
alternative, you can execute several methods successively by selecting the respective bundle indicators.
Successive Execution of Methods
On the overview screen, you can select an indicator in the column labeled Bundle for methods that run automatically without
user interaction. When you execute the task by choosing Run Successively , the system automatically executes all methods
agged with the indicator. The methods are processed in the sequence in which they appear on the overview screen. To change
this sequence, you need to change the customizing settings for the respective data collection method .
You can bundle all methods at once, rather than selecting each method separately. To do this, choose Select All .
Note
4/20/2019
Note that the selection or deselection of methods affects all methods that belong to the task. This includes methods that
might currently be hidden in the hierarchy display of methods.
Methods that rely on user input (such as manual data entry) cannot be run successively. The indicator for these kinds of
methods does not appear on the screen.
The toolbar offers the following functions:
Symbol Text Explanation
Run Successively Executes all methods selected for bundling

in succession.
Select All Selects/deselects all indicators in the

Bundle column.
Deselect All
Expand All Expands/collapses the selected subtree.
Collapse All
Save Layout Saving of screen layouts works the same

way as in the Consolidation Monitor .
Delete Layout
The bundling indicators are also saved in
Default Layout the layout.
User-de ned Layout
Integration with SAP Systems

Purpose
This component offers you processes to integrate transactional SAP applications with the SAP SEM Business Consolidation
(SEM-BCS) system. These processes are primarily intended to support customers who want to migrate from the Consolidation
component of SAP Enterprise Controlling (EC-CS) to SEM-BCS.
The processes assume you have a decentralized business scenario in which the operational business entities run on SAP
systems other than the consolidation system.
Integrated Collection of Transaction Data

The following processes support the le-based types of transaction data integration used in EC-CS:
Rollup : Loading of Rollup Files
You use this process to load rollup les from the Special Purpose Ledger component (FI-SL) into SEM-BCS using exible
upload.
Periodic Extract : Loading of RFBILA00 Files
You use the RFBILA00 program to create a periodic extract from the General Ledger Accounting component (FI-GL).
You then load the RFBILA00 les into SEM-BCS using exible upload.
Migration of C/I Data from EC-CS to SEM-BCS
You use report FICCOIC0 to export the additional nancial data for consolidation of investments from EC-CS into les,
and load these les into SEM-BCS using SAPNetWeaver Business Intelligence (BI) .
4/20/2019
Collection of Master Data and Hierarchies

You can use the following processes to collect master data and hierarchies from other SAP Systems:
Loading of Master Data from Connected SAP Systems
You use this process to collect the master data and hierarchies from InfoObjects in the BI system, or from connected
SAP systems using virtual InfoObjects.
Loading of Organizational Units from Files in EC-CS and EC-PCA
This process supports le-based integration of master data used in EC-CS: First you download les with the master data
and hierarchies of organizational units from the components General Ledger Accounting (FI-GL) and Pro t Center
Accounting (EC-PCA). Then you upload these les into SEM-BCS using exible upload.
The following table shows from which source systems you can collect which types of master data and hierarchies:
Source Systems Function Type of Master Data
Data streams from following SAP systems: Load from Data Stream Various master data and hierarchies,–such
as items and transaction types from FI, or
mySAP ERP, starting in ERP 2004
pro t centers from EC-PCA (see Loading of
BI starting in BI Release 3.0 Master Data from Connected SAP Systems
)
Files from SAP Enterprise Controlling (EC) Flexible Upload Master data of pro t centers and pro t
from SAP systems starting in center groups, pro t center hierarchies,
R/3Release4.6C combinations of consolidation units (see
Loading of Organizational Units from Files
in EC-CS and EC-PCA )
ASCII and CSV les from any system Flexible Upload All master data and hierarchies (see
Uploading Master Data Hierarchies )
Loading of Organizational Units from Files in

EC-CS and EC-PCA
Purpose
With this process, you can transfer the following master data and hierarchies in les from Enterprise Controlling (EC-CS and EC-
PCA) to the consolidation system (SEM-BCS).
Pro t center master data
Pro t center hierarchies
Pro t center groups master data
Combinations of pro t centers and companies
Combinations of consolidation business areas and companies
The system creates or updates the consolidation unit hierarchies that you want to use in the consolidation system from this
data and the Customizing settings that you implement in the consolidation workbench.
4/20/2019
This process is primarily designed to support customers who want to migrate from the Consolidation component of SAP
Enterprise Controlling (EC-CS) to the Business Consolidation component of SAP Strategic Enterprise Management. The
procedure in the sender system remains unchanged (see A Download in Sender System ).
You can also load the organizational units into the consolidation system from Enterprise Controlling with load from data stream
from SAP NetWeaver Business Intelligence (BI)or a connected SAP source system. For additional information, see Loading of
Master Data from Connected SAP Systems .
Prerequisites
In the consolidation workbench, you have made the Customizing settings for the data basis and for the consolidation area in
which you want to use the organizational units. You have created a source data basis and speci ed it in the data basis.
Process Flow
You download the master data and organizational unit hierarchies from Enterprise Controlling in les (see section “A. Download
in the Sender System“).
You make the Customizing settings for uploading the les to the consolidation system in the consolidation workbench (see
section “B. Customizing in the Consolidation System“).
You then load the les into the consolidation system, using the mapping rules that you have de ned in Customizing (see section
“C. Upload into the Consolidation System“).
The graphic outlines the data collection.
A. Download in the Sender System
The downloading procedure varies according to whether you are using pro t center consolidation or business area
consolidation.
Pro t Center Consolidation
For pro t center consolidation create the following les in Customizing for Enterprise Controlling
Organizational unit information (PRCTR_COMP.TXT)
4/20/2019
This le contains the combinations of pro t centers and companies, and also the pro t center master data.
Hierarchy information (PRCGR_HIER.TXT)
This le contains the pro t center hierarchy, and implicitly the pro t center groups master data.
In Customizing for Enterprise Controlling under Consolidation → Integration: Preparation for Consolidation → Preparation in
the Sender System → Enterprise Structure → For Pro t Center Consolidation → Export Combinations of Pro t
Centers/Companies to File (or call up transaction CXNA):
Business Area Consolidation
For business area consolidation create the le Organizational Units Information (CONSBUSAREA_COMP.TXT) in Customizing for
Enterprise Controlling. This le contains the combinations of consolidation business areas and companies.
In Customizing for Enterprise Controlling, choose Consolidation → Integration: Preparation for Consolidation → Preparation in
the Sender System → Enterprise Structure → For Business Area Consolidation → Export Combinations of
Companies/Consolidation Business Areas to File (or call up transaction CXNB):
The le content comes from EC-CS and has to be de ned there. Make sure that the following master data has been de ned in
the sender system, otherwise the le remains empty:
Companies, company codes, business areas and consolidation business areas in Customizing for Enterprise Structure under
De nition → Financial Accounting
Assignment of company codes to companies, and also business areas to consolidation business areas in Customizing for
Enterprise Structure under Assignment → Financial Accounting
Combinations of consolidation business areas and companies in Customizing for Enterprise Controlling under Consolidation →
Integration: Preparation for Consolidation → Preparation in the Sender System → Enterprise Structure → For Business Area
Consolidation → De ne Combinations of Company Codes/Business Areas
B. Customizing in the Consolidation System (SEM-BCS)
How you transfer the les to the consolidation system depends on your system environment. For example, you might be able to
access a network. To upload the les into the consolidation system, use Flexible Upload . You de ne your customizing settings in
the Consolidation Workbench.
In the source data basis, choose the InfoObject catalog delivered 0SEM_BCS_CHA03 as the InfoObject catalog for
characteristics.
When you execute the exible upload, the system initially loads the les to the InfoObjects of the InfoObject catalog. Some
attributes are loaded to internal elds. The InfoObjects and internal elds are used in mapping (see below) as source elds that
you assign to the target elds in consolidation.
For additional information, see Assigning the Files from EC-CS/EC-PCA .
In the settings for the consolidation area, you select File-based Integration with SAP R/3 and SAP ECC
For each characteristic, and the combinations of consolidation units, create a exible upload method. For the data types
consolidation groups consolidation units and other master data (with the characteristic consolidation unit combination ), the
4/20/2019
le types that were created when being downloaded in the sender system are available.
Combination pro t center/company from ECC (PRCTR_COMP.TXT)
Pro t center hierarchy from ECC (PRCGR_HIER.TXT)
Combination PC/company and PC hierarchy from ECC (PRCTR_COMP.TXT and PRCGR_HIER.TXT)
Combination business area/company from ECC (CONSBUSAREA_COMP.TXT)
On the tab page Field Catalog for the upload method assign the source data basis.
On the tab page Mapping of the upload method, assign the InfoObjects of InfoObject catalog 0SEM_BCS_CHA03 used to the
characteristics and attributes in the consolidation system. If required, you also assign values to the other attributes in the
consolidation system. For more information, see Mapping .
You can summarize the source hierarchy for the data collection by making the relevant settings in mapping. For additional
information, see Aggregating Master Data and Hierarchies for Transfer to SEM-BCS .
Some of the attributes of the characteristics in the consolidation system are set by the system automatically for the data
collection (see the section Result ) should you not have assigned values in mapping.
For additional information on Customizing and using the upload methods, see Notes on Downloading Organizational Units from
EC-CS/EC-PCA .
C. Upload into the Consolidation System
You upload the master data and hierarchies of the organizational units by executing the upload methods in the consolidation
workbench direct.
You can do test runs by executing an upload method but without saving.
Result
You have transferred the master data and organizational unit hierarchies from an SAP source system to the consolidation
system.
Default Values for Attributes
The system has set the following attributes for consolidation units that have been newly assigned to a consolidation group (if
you have not assigned any other values in mapping):
Year of rst consolidation: current year
Period of rst consolidation: current period
First consolidation at end of period: blank
Year of divestiture accounting: 9999 as initial value
Period of divestiture accounting: 012 as initial value
4/20/2019
First consolidation at beginning of period: blank as initial value
Notes on Loading Organizational Units from

EC-CS and EC-PCA
Supplementing the process description Loading of Organizational Units from Files in EC-CS and EC-PCA in the following sections
you can nd information on using and Customizing the upload method.
Aggregating the Pro t Hierarchy

You can use one of the following procedures for the aggregation of a pro t center hierarchy from Enterprise Controlling (EC-
PCA).
You aggregate the pro t center hierarchy during the data transfer to the consolidation system. For additional information, see
Aggregating Master Data and Hierarchies for Transfer to SEM-BCS .
You aggregate the pro t center hierarchy in the SAP source system prior to the data transfer to the consolidation
system by creating an alternative hierarchy with representative pro t centers. By doing this, the representative pro t
centers replace the nodes (including all subnodes) on which you want to aggregate. You can use the descriptions (both
short and medium) of the representative pro t centers to document the aggregation.
Loading the Master Data of Consolidation Groups

You load the consolidation groups master data for pro t center consolidation from a le of type Pro t Center Hierarchy from
ECC (PRCGR_HIER.TXT).
If the combination of pro t center and company has been de ned as one characteristic with the role consolidation unit in the
consolidation system, you can specify that the pro t centers also become consolidation groups during the data transfer (see
End Nodes in Source Hierarchy Become Consolidation Groups ). In this case, the system also loads the combinations of pro t
centers and companies from a le of type Combination Pro t Center/Company from ECC (PRCTR_COMP.TXT).
Loading the Master Data of Consolidation Units
Note
Note that the master data of companies and consolidation business areas in the les from EC-CS and EC-PCA is not mapped
in its entirety. For details of which master data the consolidation system collects see Assignments of the Files from EC-CS
and EC-PCA .
If you need to, you can supplement missing information from the sender system by Flexible Upload of a simple le or by Load
from Data Stream .
For pro t center consolidation you load the consolidation unit master data from a le of type Combination Pro t
Center/Company from ECC (PRCTR_COMP.TXT).
consolidation system, you can create in mapping a reusable mapping rule for the combination of pro t center and company for
a consolidation unit. You will require these mapping rules again when loading the consolidation unit hierarchy. For more
information, see Mapping in the section Mapping Rules.
4/20/2019
For business area consolidation you load the master data from a le of type Combination Business Area/Company from ECC
(PRCTR_COMP.TXT).
If the combination of consolidation business area and company has been de ned as one characteristic with the role
consolidation unit in the consolidation system, you can create in mapping a reusable mapping rule for the combination of
consolidation business area and company for a consolidation unit. For more information, see Mapping in the section Mapping
Rules.
Loading the Consolidation Unit Hierarchy

You load the consolidation unit hierarchy data for pro t center consolidation from a le of type Pro t Center Hierarchy from
ECC (PRCGR_HIER.TXT).
consolidation system, you load the consolidation units hierarchy from the les of type Combinations PC/Company and PC
Hierarchy from ECC (PRCTR_COMP.TXT and PRCGR_HIER.TXT) You can specify that for the data transfer the pro t centers also
become consolidation groups (see End Nodes in Source Hierarchy Become Consolidation Groups ).
Loading the Combinations of Consolidation Units

You load combinations of pro t centers and companies from a le of type Combination Business Area/Company from ECC
(PRCTR_COMP.TXT).
You load the combinations of consolidation business areas and companies from a le of type Combination Business
Area/Company from ECC (CONSBUSAREA_COMP.TXT).
Zuordnung der Dateien aus EC-CS/EC-PCA

Beim exiblen Upload von Organisationseinheiten aus dem Unternehmenscontrolling (EC-CS/EC-PCA) lädt das System die
Dateien zunächst in folgende InfoObjects und internen Felder des Konsolidierungssystems (SEM-BCS):
InfoObject Beschreibung lang Beschreibung kurz
0COMPANY Gesellschaft Gesellschaft
0COMP_CODE Buchungskreis Buchungskreis
0CONS_BA Geschäftsbereich der Konsolidierung KonsGschBereich
0COUNTRY Länderschlüssel Land
0CO_AREA Kostenrechnungskreis KostRechKreis
0PROFIT_CTR Pro t Center Pro t Center
0SEM_CGPRCT Pro t Center Kreis PrCtrKreis
Internes Feld Beschreibung lang Beschreibung kurz
FISCVARNT GeschJahresvariante GJVariante
TXTMI Mitteltext Mitteltext
TXTSH Kurztext Kurztext
4/20/2019
Die verwendeten InfoObjects und internen Felder dienen im Mapping der Uploadmethode als Quellfelder, welche Sie den
Zielfeldern in der Konsolidierung zuordnen.
Weitere Informationen nden Sie unter Laden von Organisationseinheiten aus Dateien von EC-CS/EC-PCA .
InfoObjectCatalog 0SEM_BCS_CHA03
Die InfoObjects müssen dem InfoObjectCatalog für Merkmale zugeordnet sein, den Sie in der Quelldatenbasis angegeben
haben. Für diesen Zweck steht Ihnen der InfoObjectCatalog für Merkmale 0SEM_BCS_CHA03 als SAP Business Content im
SAPNetWeaver Business Intelligence (BI) zur Verfügung.
Sie können auch einen anderen InfoObjectCatalog verwenden, wenn dieser alle InfoObjects aus 0SEM_BCS_CHA03 enthält.
Zuordnung der Dateien aus EC-CS/EC-PCA zu den Quellfeldern

Die InfoObjects und internen Felder des Konsolidierungssystems werden abhängig von dem Dateityp und dem Datentyp, den
Sie im Customizing des exiblen Uploads de niert haben, verwendet.
Die folgenden Tabellen zeigen die feste Zuordnung der Felder in den Dateien zu den InfoObjects und internen Feldern der
Konsolidierung:
Die Kombinationen aus Pro tcentern und Gesellschaften sowie die Stammdaten der Pro tcenter laden Sie aus einer
Datei vom Typ Kombination Pro t-Center/Gesellschaft aus ECC (PRCTR_COMP.TXT). Das System ordnet die Felder der
Datei folgendermaßen zu:
Feld in PRCTR_COMP.TXT InfoObject/ internes Feld
Pro tcenter (PRCTR) 0PROFIT_CTR
Gesellschaft (RCOMP) 0COMPANY
Kostenrechnungskreis (KOKRS) 0CO_AREA
Länderschlüssel (LAND1) 0COUNTRY
Geschäftsjahresvariante (PERIV) FISCVARNT
Beschreibung mittel des Pro tcenters (LTEXT) TXTMI
Beschreibung kurz des Pro tcenters (KTEXT) TXTSH
Die Stammdaten der Pro tcenter-Gruppen laden Sie aus einer Datei vom Typ Pro t-Center-Hierarchie aus ECC
(PRCGR_HIER.TXT). Das System ordnet die Felder der Datei folgendermaßen zu:
Feld in PRCGR_HIER.TXT InfoObject/ internes Feld
Pro tcenter-Gruppe (SETID) 0SEM_CGPRCT
Beschreibung mittel der Pro tcenter-Gruppe (DESCRIPT) TXTMI
Die Konsolidierungseinheitenhierarchie für die Pro tcenter-Konsolidierung laden Sie aus einer Datei vom Typ Pro t-
Center-Hierarchie aus ECC (PRCGR_HIER.TXT). Das System ordnet die Felder der Datei folgendermaßen zu:
4/20/2019
Feld in PRCGR_HIER.TXT InfoObject
Pro tcenter (PRCTR) 0PROFIT_CTR
Pro tcenter-Gruppe (SETID) 0SEM_CGPRCT
Die Kombinationen aus Konsolidierungsgeschäftsbereichen und Gesellschaften laden Sie aus einer Datei vom Typ
Kombination Geschäftsbereich/Gesellschaft aus ECC (CONSBUSAREA_COMP.TXT). Das System ordnet die Felder der
Datei folgendermaßen zu:
Feld in CONSBUSAREA_COMP.TXT InfoObject
Buchungskreis (BUKRS) 0COMP_CODE
Gesellschaft (RCOMP) 0COMPANY
Konsolidierungsgeschäftsbereich (GSBER_KONS) 0CONS_BA
End Nodes in Source Hierarchy Become

Consolidation Groups
The indicator End Nodes Become Consolidation Groups is used when loading organizational units to the consolidation system
(SEM-BCS). The following explains its function, using pro t center consolidation as a basis.
In the consolidation system, the combination of pro t center and company can be de ned as a characteristic of the
Consolidation Unit role. In this case, during the data collection, the system determines the consolidation unit hierarchy from the
pro t center hierarchy, and the valid combinations from the pro t centers and companies. There are two possible cases:
Only the pro t center groups become consolidation groups.
The pro t center groups and pro t centers (end nodes in the source hierarchy) become consolidation groups.
When copying the pro t center hierarchy, you can specify how the system determines the consolidation unit hierarchy. If you set
the End Nodes Become Consolidation Groups indicator, the pro t centers also become consolidation groups.
 Example
In this example, the pro t center hierarchy consists of the pro t center groups PG0, PG1, and PG2, and the pro t centers
PC11, PC12, PC21, and PC22. The companies C1 and C2 are used for consolidation. The consolidation system uses the
combinations of pro t centers and companies to form the consolidation units.
4/20/2019
Case 1: Only the pro t center groups become consolidation groups, meaning that you have not set the End Nodes Become
Consolidation Groups indicator.
Case 2: The pro t center groups and the pro t centers become consolidation groups, meaning that you have set the End
Nodes Become Consolidation Groups indicator. The gure shows the initial structure of the consolidation unit hierarchy.
4/20/2019
Pro t center PC22 with only one consolidation unit PC22-C1 is useless as a consolidation group. Therefore, the system
deletes pro t center PC22 from the consolidation unit hierarchy.
The following gure shows the nal consolidation unit hierarchy for Case 2 (you have set the End Nodes Become
Consolidation Groups indicator).
4/20/2019
Aggregating Master Data and Hierarchies for

Transfer to SEM-BCS
Use
You use this procedure to aggregate hierarchies for automatic data collection into the consolidation system (SEM-BCS).
The hierarchies in operational systems can be structured at a deeper level than is supported in the consolidation system. You
aggregate a source hierarchy by grouping several subordinate hierarchy nodes in one higher-level node. This summarization
process is called aggregation.
The tool you use for aggregation is Mapping as it exists in the following data collection methods:
Flexible Upload
For data collection using exible upload or load from data stream, the system initially maps the source hierarchy in an internal
structure. The system transfers this by using the mapping rules that you have de ned in Customizing the data collection
method, line for line to the internal structure of the target hierarchy.
4/20/2019
To aggregate a hierarchy you employ the following mapping principles:
The system deletes the edges that have higher-level and subordinate nodes with the same name in the mapping result (internal
structure of the target hierarchy).
The system deletes redundant edges in the mapping result.
To assign the master data to the nodes on which you have summarized the hierarchy, you use the following mapping principle:
The system deletes redundant edges in the mapping result (by rst sorting the nodes in ascending order and then deleting all
nodes that have the same name up to the rst node).
Prerequisites
In the consolidation workbench, you have made the Customizing settings for the Data Basis and for the Consolidation Area in
which you want to use the hierarchy. You have created a Source Data Basis and entered it in the data basis. In the source data
basis you have entered the InfoObject catalog containing the InfoObjects to be loaded.
If you use Load from Data Stream: the InfoObjects or virtual InfoObjects that supply the source hierarchy are already in SAP
NetWeaver Business Intelligence (BI).
If you use Flexible Upload: you have created the les to be uploaded in the sender system.
Procedure
Visualize the internal structures for the source hierarchy and the target hierarchy. Formulate mapping that is suitable for
creating redundant entries in the target hierarchy on the edges on which you want to summarize.
In the consolidation workbench, create a data collection method and de ne mapping. For additional information on Customizing,
see Customizing for Flexible Upload or Customizing for Load from Data Stream .
Execute the method in the consolidation workbench.
Result
4/20/2019
You have uploaded the source hierarchy to the consolidation system. The system has created the target hierarchy, and
summarized it based on the speci cations in mapping.
Example
The example illustrates how mapping can be used for:
Aggregation when loading a pro t center hierarchy
Assignment when loading the related pro t center master data
Aggregation when Loading aPro tCenterHierarchy
Pro t centers P111, P113 and P118 are to be summarized on pro t center group P11, and pro t centers P122 and P125 on pro t
center group P12. The pro t centers are assigned to controlling area (CO area) 9000.
The following table sets out the internal structure of the source hierarchy:
Higher-level Object Lower-level Object
Hierarchy Name Text Node Text Node CO Area Pro tCenter Seq. No.
H1 P1 0
P1 P11 0
P11 9000 P111 0
P11 9000 P113 1
P11 9000 P118 2
P1 P12 1
P12 9000 P122 0
4/20/2019
Higher-level Object Lower-level Object
Hierarchy Name Text Node Text Node CO Area Pro tCenter Seq. No.
P12 9000 P125 1
The following table sets out the internal structure of the target hierarchy: This assumes the consolidation pro t center
(ConsPC) and consolidation pro t center groups (ConsPCG) are assigned to controlling area (Co area) 9000:
Higher-level Object Lower-level

Object
Hier.Name CO Area ConsPCG CO Area ConsPCG ConsPC SeqNo.
The following mapping rules are suitable for implementing the intended summarization in the target hierarchy:
Target Field Mapping Rule
Hierarchy name (Hier.Name) Transfer hierarchy name from source hierarchy.
Controlling area (CO Area) Assign constant 9000.
Consolidation pro t center group (ConsPCG) Transfer the rst two characters of the text node from the source
hierarchy.
Consolidation pro t center (ConsPC) Transfer the rst three characters of the pro t center from the
source hierarchy.
The following table sets out the internal structure of the target hierarchy once the system has transferred the internal
structure of the source hierarchy using the mapping rules line for line:

Object
H1 9000 P1 0
9000 P1 9000 P1 0
9000 P1 9000 P11 0
9000 P1 9000 P11 1
9000 P1 9000 P11 2
9000 P1 9000 P1 1
9000 P1 9000 P12 0
9000 P1 9000 P12 1
The following table sets out the internal structure of the target hierarchy once the system has deleted the edges that have
higher-level and subordinate nodes with the same name.
H1 9000 P1
4/20/2019
9000 P1 9000 P11
9000 P1 9000 P11
9000 P1 9000 P11
9000 P1 9000 P12
9000 P1 9000 P12
The following table sets out the internal structure of the target hierarchy once the system has deleted the redundant edges:

Object
H1 9000 P1 0
9000 P1 9000 P11 0
9000 P1 9000 P12 1
The graphic shows the resulting target hierarchy:
Assignment of thePro tCenterMaster Data
In the same way as for the pro t center hierarchy, the pro t center master data is to be assigned to the consolidation pro t
centers P11 and P12. Consolidation pro t center P11 is to transfer the master data of pro t center P111, P12 the master data of
P122. The master data has been de ned as follows:
Pro tCenter User-De ned Attribute Short Description Medium Description
P111 USER111 TXT111 TXT111
4/20/2019
The internal structure for the master data of the consolidation pro t center is de ned in the following way:
CO area ConsPC User-de ned attribute Short description Medium description
The following mapping rules are suitable for implementing the intended assignment in the target hierarchy:
Target Field Mapping Rule
Controlling area (CO area) Assign constant 9000.
Consolidation pro t center (ConsPC) Transfer the rst three characters of the pro t center.
User-De ned Attribute Transfer user-de ned attribute from the pro t center master data.
Short description Transfer short description from the pro t center master data.
Medium description Transfer long description from the pro t center master data.
The following table sets out the internal structure of the target master data once the system has transferred the source
master data using the mapping rules line for line:
CO Area ConsPC User-De ned Attribute Short Description Medium Description
9000 P11 USER111 TXT111 TXT111
9000 P11 USER113 TXT113 TXT113
9000 P11 USER118 TXT118 TXT118
9000 P12 USER122 TXT122 TXT122
9000 P12 USER125 TXT125 TXT125
The following table sets out the internal structure of the target master data once the system has sorted the nodes and deleted
the nodes with the same name up to and including the rst node:
CO Area ConsPC User-De ned Attribute Short Description Medium Description
9000 P11 USER111 TXT111 TXT111
9000 P12 USER122 TXT122 TXT122
Loading of Master Data from Connected

SAP Systems
Purpose
You can use this process to copy master data and hierarchies from connected SAP systems to the consolidation system (SEM-
BCS).
In particular, the process considers the loading of organizational units and combinations of consolidation units.
Loading Master Data and Hierarchies
4/20/2019
You load the master data and hierarchies from individual InfoObjects in the BI system (SAP NetWeaver Business Intelligence).
The following two cases are possible:
You use virtual InfoObjects from the SAP source system (mySAP ERP) to load the master data and hierarchies.
The SAP source system provides the master data and hierarchies in a DataSource, which you assign to an InfoSource in
the Data Warehousing Workbench of the BI system. You use the consolidation function Load from Data Stream to copy
the master data and hierarchies to the consolidation system.
Note
The procedure for loading hierarchies will change in the next release.
You load the master data and hierarchies from InfoObjects that already exist in the BI system.
You use Load from Data Stream to copy the master data and hierarchies to the consolidation system.
Loading Combinations of Consolidation Units
You use Load from Data Stream to load the combinations of consolidation units, for example, combinations of pro t centers and
companies, of an InfoProvider (InfoCube or DataStore object) from the BI system. The consolidation system determines the
valid combinations from the transaction data.
You can also load the combinations directly from a DataSource of the SAP source system.
Prerequisites
4/20/2019
In the consolidation workbench, you have made the Customizing settings for the data basis and for the consolidation area in
which you want to use the master data and hierarchies. You have created a source data basis and speci ed it in the data basis.
Depending on the sources from which you want to copy the master data, hierarchies, or combinations of consolidation units, the
following prerequisites must be ful lled:
If you copy the master data and hierarchies directly from an SAP source system:
DataSources, which provide the attributes and texts for master data, have the following prerequisites:
They must be .
The DataSource you use needs to support direct access to the data. You have set the indicator Direct
Access in DataSource maintenance of the SAP source system.
If you use hierarchies, the source eld and target eld in the transfer rule of the InfoSource need to be technically
compatible. This means that the elds have the same type, length, and conversion exit.
If you use a PSA DataSource for hierarchies, the transfer rule of the InfoSource must consist of simple moves
from source elds to target elds only.
If you copy the master data and hierarchies of InfoObjects from the BI system:
The master data and hierarchies exist in the InfoObjects.
If you copy the combinations from consolidation units of an InfoProvider (InfoCube or DataStore object):
The transaction data from which the system determines the combinations is in the InfoProvider. For example, this means
that you need to have used a BI upload to the InfoProvider to upload the data from Enterprise Controlling (EC-CS/EC-
PCA).
Process Flow
The following explains the process ow for copying master data and hierarchies from virtual InfoObjects. The gure shows an
overview of the components for which you make Customizing settings.
In the Data Warehousing Workbench, you activate the DataSource of the SAP source system. You assign an InfoSource to the
DataSource and link the elds of the DataSource to the InfoObjects of the InfoSource. See section "A. Customizing in the Data
Warehousing Workbench".
In the consolidation workbench, you create a Load from Data Stream method for each InfoObject that you want to copy. In this,
you de ne the mapping rules and optional source and target selections for copying the data from the InfoObject to the
consolidation system. See section "B. Customizing in the Consolidation Workbench".
When you run the methods for loading from data stream in the consolidation workbench, the consolidation system loads the
master data and hierarchies from the DataSource of the SAP source system into the internal data structures of consolidation.
4/20/2019
See section "C. Execution in the Consolidation Workbench".
A. Customizing in the Data Warehousing Workbench
1. If you use a DataSource from SAP Business Content, you copy this to the active version (see Copying Business Content
DataSources).
Otherwise, you create a DataSource in the SAP source system. For more information, see Data Extraction from SAP
Source Systems.
The system then performs a metadata upload automatically. This replicates the DataSource to the BI system (see
Metadata Upload for SAP Systems ).
2. You create the InfoObjects, which copy the master data and hierarchies from the SAP source system, and de ne the
InfoObjects as mediums of virtual master data (master data access: remote).
3. You create an InfoSource and in this, assign the DataSource of the SAP source system. You assign the InfoObjects
created previously to the elds of the DataSource (see Creating an InfoSource).
4. You create an InfoObject catalog for characteristics and add the InfoObjects created previously (see Creating an
InfoObject Catalog).
Note
When you load the master data and hierarchies of InfoObjects from the BI system, in the Data Warehousing
Workbench, you create only an InfoObject catalog for characteristics, which contains the InfoObjects from which you
want to load.
In the consolidation workbench, you make the same settings as for loading from SAP source systems.
B. Customizing in the Consolidation Workbench
1. In the source data basis, you enter the InfoObject catalog for characteristics.
If you use an InfoProvider, for example, for copying the combinations of pro t centers and companies, enter this in the
source data basis.
2. For each characteristic that you want to copy to the consolidation system, and for the combinations of consolidation
units, create a method for loading from the data stream. You choose the data type, the characteristic (if more than
characteristic exists for the data type), and enter the source data.
For the data types Consolidation Units, Consolidation Groups, and Other Master Data (with the characteristic
ConsUnitCombination), make additional settings for loading master data and hierarchies on the Settings tab page. You
can choose whether to load master data, hierarchies, and/or hierarchy relationship attributes (for example, accounting
technique). You can also con gure that the system is to load the master data from the text nodes of the hierarchy, for
example, the master data of pro t center groups. Depending on which options you choose, the corresponding target
elds of the consolidation system are available on the Mapping tab page.
3. On the Mapping tab page of the method, you assign the elds of the InfoObject to the target elds in the consolidation
system. If required, you also assign values to the other attributes in the consolidation system. For more information, see
Mapping.
The system sets some of the attributes of the characteristics in the consolidation system automatically for the data
collection (see the section Result) if no values have been assigned in mapping.
Note
You can summarize the source hierarchy for the data collection by making the relevant settings in mapping. For more
information, see Summarization for Copying Data to the Consolidation System.
4/20/2019
4. On the Selection tab page, you can restrict the source data to be copied and the target data. For example, when copying
pro t centers, you load only the pro t centers of a particular controlling area, or when copying combinations of pro t
centers and companies, you load only the combinations for the current scal year. For more information, see Selection.
Notes on Data Collection from EC-CS/EC-PCA
If you copy a pro t center hierarchy from Enterprise Controlling (EC-CS/EC-PCA) and have de ned the combination of pro t
center and company as a characteristic with the role Consolidation Unit in the consolidation system, the system determines
the consolidation unit hierarchy from the pro t center hierarchy and the combinations of pro t centers and companies. In this
case, you make the following additional settings for the method Load from Data Stream in the consolidation workbench:
As source data, you enter both the pro t center InfoObject and the InfoProvider that provides the combinations of pro t
centers and companies.
To copy the consolidation unit hierarchy and to copy the master data of the consolidation groups, you can specify that
pro t centers also become consolidation groups (see End Nodes in Source Hierarchy Become Consolidation Groups).
C. Execution in the Consolidation Workbench
You run the methods for loading from the data stream in the consolidation workbench directly.
You can perform test runs by executing a method but without saving.
Result
You have copied the master data and organizational unit hierarchies from the SAP source system to the consolidation system.
Default Values for Attributes of Consolidation Units
The system has set the following attributes for consolidation units that have been newly assigned to a consolidation group (if
you have not assigned any other values in mapping):
Year of First Consolidation: Current year
Period of First Consolidation: Current period
First Consolidation at End of Period: Space as initial value
Year of Divestiture Accounting: 9999 as initial value
Period of Divestiture Accounting: 012 as initial value
Divestiture Accounting at Start of Period: Space as initial value
Example
The following examples of loading master data and hierarchies show Customizing for the method Load from Data Stream in
detail:
Example: Loading Master Data and Hierarchies of Cons. Units
Example: Loading Master Data of Consolidation Groups
Example: Loading Master Data and Hierarchies of Items
4/20/2019
Example: Loading Master Data and

Hierarchies of Cons. Units
This example shows you the details for customizing the method Load from Data Stream .
Task at Hand
You want to load the master data of the characteristic consolidation pro t center from the InfoObject 0PROFIT_CTR into the
consolidation system (SEM-BCS).
Note
You rst have to load the master data of the consolidation groups (see Example: Loading Master Data of Consolidation
Groups ). Only then can you load the master data and hierarchies of consolidation units.
You are only interested in pro t center hierarchy H1 (source selection).
The consolidation pro t centers you select are to be allocated to controlling area 1000 . You also want to set the following
attributes:
Fiscal year variant: K4
Year of First Data Entry: 2005
Period of First Data Entry: 012
Customizing the Method

The method uses the data type consolidation units with the characteristic consolidation pro t center .
The following table shows the settings on the Settings tab page:
Group Box Checkbox Value
Source Data Source Data Basis Q1
InfoObject 0PROFIT_CTR
InfoProvider –
Options for Master Data and Hierarchies Load Master Data (selected)
Use Text Nodes from Hierarchy –
Load Hierarchy (selected)
Load Hierarchy Relationship Attributes –
Update Mode Existing Settings Overwrite
BAdI Filter BAdI Filter Value –
The following table shows how the method is mapped:
Target Field Operator Value/Source Field
4/20/2019
Controlling Area Move ’1000’
Consolidation Pro t Center Move Pro t center
Period of First Data Entry Move ’012’
Fiscal Year Variant Move ’K4’
Year of First Data Entry Move ’2005’
Medium Description Move Medium Description
Short Description Move Short Description
Consolidation Pro t Center Group Move Hierarchy Node
Hierarchy Move Hierarchy
On the Selection tab page, you make a source selection so that only the pro t center hierarchy H1 is loaded:
Characteristic Selection Condition
Selection for Source Pro t center H1 (include pro t center hierarchy H1)
Selection for Target – –
For more information about selection conditions, see Single Selection .
See also:
Loading of Organizational Units from Connected SAP Systems
Example: Loading Master Data of Consolidation Groups
Example: Loading Master Data of

Consolidation Groups
Task at Hand
You want to load the master data of the characteristic consolidation pro t center group (consolidation group) from the
InfoObject 0PROFIT_CTR into the consolidation system (SEM-BCS). This data is located on the text nodes of the pro t center
hierarchy.
You are only interested in pro t center hierarchy H1 (source selection).
The consolidation pro t center groups you select are to be allocated to controlling area 1000 .

The method uses the data type consolidation groups with the characteristic consolidation pro t center group .
4/20/2019
InfoObject 0PROFIT_CTR
InfoProvider –
Use Text Nodes from Hierarchy (selected)
Load Hierarchy –
The following table shows how the method is mapped:
Target Field Operator Value/Source Field
Controlling Area Move ’1000’
Consolidation Pro t Center Group Move Hierarchy Node
Medium Description Move Medium Description
Short Description Move Short Description
On the Selection tab page, you make a source selection so that only the pro t center groups of controlling area 1000 are
loaded:
Characteristic Selection Condition
Selection for Source Pro t Center H1 (include pro t center hierarchy H1)
Selection for Target – –
For more information about selection conditions, see Single Selection .
See also:
Loading of Organizational Units from Connected SAP Systems
Example: Loading Master Data and Hierarchies of Cons. Units
Example: Loading Master Data and

Hierarchies of Items
Task at Hand
You want to load the master data and hierarchies of the characteristic nancial statement item from the InfoObject
0ACCOUNT into the consolidation system (SEM-BCS).
4/20/2019
And you want to assign the account numbers of chart of accounts 100 to consolidation chart of accounts 01 .
You want to create a hierarchy of items only.
You want to assign the item type balance sheet to the account numbers 1 – 199999 , and the item type income statement to
the account numbers 200000 – 999999 .
You have no intention of explicitly specifying source or target selections.

The method uses the data type items with the characteristic item .
InfoObject 0ACCOUNT
InfoProvider –
Use Text Nodes from Hierarchy –
Load Hierarchy (selected)
The following table shows how the method is mapped. For more information about selection conditions and selection logic, see
Single Selection .
Target Field Operator Value/Source Field/Selection Condition
Cons Chart of Accounts Move ’01’
Item Condition Hierarchy node ’Initialized’(exclude

blank hierarchy nodes)
⇒ Move Hierarchy Node
Condition Chart of accounts ’100’(include account

numbers of chart of accounts 100 )
Account number ’Initialized’(exclude

unde ned account numbers)
⇒ Move Account number
Item Type Condition Chart of accounts ’100’(include account

Account number 1 – 199999(include

account numbers within the range)
⇒ Move ʻ1’ (balance sheet)
Condition Chart of accounts ’100’(include account
4/20/2019
Account number 200000 –

999999(include account numbers within
the range)
⇒ Move ʻ2’ (income statement)
Dr/Cr Sign Move ’+’
Long Description Move Medium description
Short Description Move Short description
Hierarchy Move Hierarchy
The Selection tab page has no entries because no explicit source or target selections are being made.
Loading of FI-SL Rollup Files

Purpose
You use this process to transfer rollup les from the Special Purpose Ledger (FI-SL) component to the SAP SEM Business
Consolidation (SEM-BCS) component.
Note
Enterprise Controlling (EC-CS) to the Business Consolidation component of SAP Strategic Enterprise Management.
You can use rollups for the following integrated types of consolidation:
Company consolidation
Business area consolidation
Pro t center consolidation
The gure below illustrates a decentralized scenario in which one or more operational SAP systems (sender systems) export
FI-SL rollup les to the consolidation system. But rst, the sender systems import the relevant customizing settings from the
consolidation system.
4/20/2019
Prerequisites
The sender system runs SAP R/3 Release 4.6A or later.
Prerequisites in the Sender System
In the sender system, you have performed the preparations for consolidation in Customizing for Enterprise Controlling at
Consolidation Integration:Preparation for Consolidation Preparations in the Sender System .
You have de ned the subitem categoriesin Customizing for Enterprise Controlling at Consolidation Master Data Financial
Statement Items Subassignments De ne Subitem Categories and Subitems .
You have made the following de nitions and assignments in Customizing for Enterprise Controlling at
Consolidation Integration: Preparation for Consolidation Preparations in the Consolidation System :
Assignments of integrated consolidation types to dimensionsat Preparations in the Consolidation System Assign
Integrated Consolidation Types to the Dimensions
Rules for ID combinations for each consolidation type and consolidation unitat Preparations in the Consolidation
System Copy Organizational Units De ne ID Combination Rules
Values of independent characteristics for each integrated consolidation typeat Preparations in the Consolidation
System Collection of Data De ne Data Streams
Mapping of transaction charts of accounts and consolidation charts of accountsat Preparations in the Consolidation
System Collection of Data Assign Transaction Charts of Accts to Cons Charts of Accts
Mapping of secondary cost elements to nancial statement itemsat Preparations in the Consolidation
System Collection of Data For Pro t Center Cons: Cost Elements Assignment Allocate Cost Element Ranges to FS
Items
Prerequisites in the Consolidation System (SEM-BCS)
4/20/2019
In the consolidation workbench, you have made the customizing settings for the data basis and the consolidation area where
you want to employ rollups. You have created a source data basis and speci ed it in the data basis.
The master data and the hierarchies of organizational units are current.
Process Flow
In the consolidation workbench, you de ne a method for the exible upload of FI-SL rollup les. Then you export the customizing
settings to a data le. See “A. Preparations in the Consolidation System (SEM-BCS).”
In the sender systems, you import the customizing settings from the data le and create the FI-SL rollup les. See “B. Activities
in the Sender System.”
You load the FI-SL rollup les into the consolidation system by running the upload method for each FI-SL rollup le. See “C.
Execution in the Consolidation System (SEM-BCS).”
A. Preparations in the Consolidation System (SEM-BCS)
You use the exible upload data transfer method to upload an FI-SL rollup le into the consolidation system and to export the
customizing settings. You de ne your customizing settings in the consolidation workbench.
1. In the source data basis, you choose the delivered InfoObject catalog 0ECCS_CHA01 for the characteristics, and the
delivered InfoObject catalog 0ECCS_KYF01 for the key gures.
When you execute the exible upload, the system initially loads the FI-SL rollup le into the external eld catalog. The
assignments of the elds in the le to the InfoObjects in the eld catalog are xed. The InfoObjects are used in mapping
as the source elds, which you assign to the target elds in consolidation.
For more information, see Assignment of FI-SL Rollup Files in SEM-BCS .
2. In the consolidation area settings, you select File-based Integration with SAP R/3 and SAP ECC .
3. You create a method for exible uploads with the data type Reported Financial Data and the le type FI-SL Rollup File.
a. On the Field Catalog tab page, you assign the source data basis.
You can transfer your custom subassignments from the FI-SL rollup le by assigning the elds on the Field
Catalog tab page. For more information, see Transferring Custom Subassignments from FI-SL Rollups .
b. On the Mapping tab page, you assign the InfoObjects to the key gures, characteristics, and attributes in the
consolidation system. If required, you also assign values to the other attributes in the consolidation system. For
more information, see Mapping .
c. On the Settings tab page, you de ne the update mode. If you want to use a Business Add-In (BAdI) for mapping,
you need to specify the BAdI lter value. For more information, see Customizing for Flexible Upload .
d. Optional: On the Selection tab page, you can de ne a target selection. For more information, see Selection .
After you have de ned and saved the upload method, the consolidation system will be able to export the
customizing settings.
4. You choose Export in the customizing settings for the upload method to export the settings from the consolidation
system to a data le. For more information, see Exporting Customizing Files for FI-SL Rollups .
For more information about customization and use of upload methods, see Notes on Loading of FI-SL Rollup Files .
B. Activities in the Sender System
4/20/2019
How the customizing le is transferred from the consolidation system to the sender system(s) and how FI-SL rollup les are
transferred to the consolidation system depends on your system landscape. For example, you might be able to access a
network.
1. You import the customizing le from SEM-BCS: In Customizing for Enterprise Controlling choose
Consolidation Integration: Preparation for Consolidation Preparations in the Sender System Preparation and
Activation of Data Transfer Rollup Upload Customizing Settings from File.
Note
Make sure you de ne the customizing settings that cannot be imported into the sender system rst (see the
“Prerequisites in the Sender System” section). See also Exporting Customizing Files for FI-SL Rollups .
After your import of the customizing settings is successful, the system is ready to create an FI-SL rollup le.
2. To execute a rollup, on the SAP Easy Access screen you choose Accounting Financial Accounting Special Purpose
Ledger Periodic Processing Rollup Execute .
A rollup le is created.
C. Execution in the Consolidation System (SEM-BCS)
You load an FI-SL rollup le into the consolidation system by running the upload method in the consolidation monitor as follows:
1. You go to the consolidation workbench, de ne a task for data collection, and assign the upload method to the task (see
De ning a Flexible Upload ).
2. You go to the consolidation monitor and start uploading the FI-SL rollup le by running the data collection task (see
Executing a Flexible Upload ).
The upload writes data records only when no errors occur.
Result
You have loaded one or more FI-SL rollup les into the consolidation system.
Now you can prepare and consolidate the integrated data in the consolidation system.
Notes on Loading of FI-SL Rollup Files

As a supplement to the process description Loading of FI-SL Rollup Files , these sections provide more information about the
customization and use of the upload method.
Use of a BAdI
You have the option of using a Business-Add-In (BAdI) for mapping the accounting objects. If you map subitems to custom
subassignments in a BAdI, the system is not able to export the master data for subitems and custom subassignments. For more
information, see Exporting Customizing Files for FI-SL Rollups .
Transfer of Subassignments
The EC Consolidation (EC-CS) component maps certain subassignments, such as the transaction type, as subitems of a speci c
subitem categoryand exports these to the FI-SL rollup le in the same format.
4/20/2019
If the SEM consolidation system (SEM-BCS) uses the same data model as EC-CS, go to the mapping section of the upload
method and assign the source elds Subitem and Subitem Category to their respective target elds.
You can use the characteristics available in SEM-BCS, such as the transaction type, as subassignments . If you do this, create a
mapping rule in the upload method that expresses the following: If the source eld Subitem Category identi es the
subassignment <characteristic> , then move the source eld Subitem to the target eld <characteristic> . (Here,
<characteristic> might represent the transaction type. )
Shifted Fiscal Years

When creating the FI-SL rollup le, the sender system uses the scal year variant you have de ned in Customizing for SAP
Enterprise Controlling at Consolidation Integration: Preparation for Consolidation Preparations in the Sender
System Preparation and Activation of Data Transfer Activate Data Transfer .
If the companies to be consolidated use a different scal year variant, when creating the FI-SL rollup le the sender system
automatically converts the periods of the reported nancial data to suit the scal year variant of the consolidation system.
You can use the automatic conversion in the sender system if you specify the scal year variant used in SEM-BCS when you run
Activate Data Transfer .
Assignment of FI-SL Rollup Files in SEM-

BCS
Use
The exible upload of a rollup le from the Special Purpose Ledger (FI-SL) component to the SAP SEM Business Consolidation
(SEM-BCS) component initially loads the elds of the rollup le into the assigned InfoObjects in SAP NetWeaver Business
Intelligence (BI).
The elds of the FI-SL rollup le are de ned in the ECMCT table of the SAP EC Consolidation (EC-CS) component.
In the mapping area of the upload method, the InfoObjects are used as the source elds, which you assign to the target elds in
the consolidation system on the Mapping tab page.
For more information, see Loading of FI-SL Rollup Files .
Assignment of FI-SL Rollup Files to the InfoObjects
By default, the consolidation system transfers the following elds from the FI-SL rollup le and assigns them to the InfoObjects
as follows:
Field inRollup File Long Description InfoObject InfoObject Type
PRACQ Period in which the rst 0ACQ_PER Characteristic

acquisition is posted
RBUNIT Consolidation unit 0CS_UNIT
RBUPTR Partner unit 0CS_PARTNER
RDIMEN Dimension 0CS_DIMEN
RITCLG Consolidation chart of accounts 0CS_CHART
4/20/2019
Field inRollup File Long Description InfoObject InfoObject Type
RITEM Item 0CS_ITEM
RVERS Consolidation version 0CS_VERSION
SITYP Subitem category 0CS_SITEMCT
SUBIT Subitem 0CS_SITEM
YRACQ Fiscal year in which the rst 0ACQ_YEAR

acquisition is posted
HSL0x Period value in local currency 0CS_TRN_LC Key gure
KSL0x Period value in group currency 0CS_TRN_GC
MSL0x Cumulative quantity 0CS_TRN_QTY
TSL0x Period value in transaction 0CS_TRN_TC

currency
RYEAR Fiscal year 0FISCYEAR Time Characteristic
RTCUR Currency key of transaction 0CURKEY_TC Unit

currency
Note
In addition to the elds listed above, you can also transfer your own custom subassignments from an FI-SL rollup le. For
more information, see Transferring Custom Subassignments from FI-SL Rollups .
Integration
InfoObjects, Type “Characteristic”
The InfoObjects with the type “Characteristic” must be contained in the InfoObject catalog for characteristics, which you have
speci ed in the source data basis used for the exible upload.
The InfoObject catalog 0ECCS_CHA01 is available as SAP Business Content in SAP NetWeaver Business Intelligence (BI) for this
purpose.
You can also use a different InfoObject catalog for characteristics, provided it includes all of the InfoObjects contained in
0ECCS_CHA01.
InfoObjects, Type “Key Figure”
The InfoObjects with the type “Key Figure” must be contained in the InfoObject catalog for key gures, which you have speci ed
in the source data basis used for the exible upload.
The InfoObject catalog 0ECCS_KYF01 is available as SAP Business Content in SAP NetWeaver Business Intelligence (BI) for this
purpose.
You can also use a different InfoObject catalog for key gures, provided it includes all of the InfoObjects contained in
0ECCS_KYF01.
InfoObjects, Other Types
4/20/2019
The system assigns InfoObjects such as the scal year (0FISCYEAR), which have a type other than “characteristic” or “key
gure”, internally. This means that you do not have to specify these InfoObjects in the source data basis.
Transferring Custom Subassignments from

FI-SL Rollups
Use
You use this procedure to transfer custom subassignments from a rollup le created in the Special Purpose Ledger (FI-SL)
component to the SAP SEM Business Consolidation (SEM-BCS) component.
In the sender system, custom subassignments are de ned in table ECMCT of the SAP EC Consolidation (EC-CS) component.
Prerequisites
You have created a source data basis in the consolidation workbench. There you have speci ed the InfoObject catalogs for the
characteristics and key gures required for the exible upload of FI-SL rollup les. For more information, see Assignment of FI-
SL Rollup Files in SEM-BCS .
You have created an executable method for the exible upload of FI-SL rollup les. For more information, see Loading of FI-SL
Rollup Files .
The InfoObject that will accommodate the custom subassignment from the FI-SL rollup le has been activated in SAP
NetWeaver Business Intelligence (BI).
Procedure
Perform the following steps in the Data Warehousing Workbench :
1. Open the InfoObject catalog for characteristics that you use in the method for the exible upload of FI-SL rollup les.
2. Add the InfoObject you want to use to transfer the custom subassignment from the FI-SL rollup le.
After you save the InfoObject catalog, the new InfoObject is available in Customizing for the method for the exible
upload of FI-SL rollup les.
Perform the following steps in the Consolidation Workbench :
1. Open the method for the exible upload of FI-SL rollup les.
2. Choose the Field Catalog tab page and add a new line to the custom subassignments table as follows:
a. In the Field Name of Custom Subassignment column, enter the eld name of the custom subassignment used in
the FI-SL rollup le (or the ECMCT table).
b. In the Field Name column, choose the InfoObject you want to use for the custom subassignment from the FI-SL
rollup le.
c. In the Name of Check Table column, enter the check table from the sender system that is assigned to the custom
subassignment.
d. In the Name of Text Table column, enter the associated text table of the sender system.
4/20/2019
The check and text tables are needed for exporting the customizing settings and for importing and assigning
those settings in the sender system.
Note
You can display the eld names and their check and text tables in the sender system: In Customizing for
Enterprise Controlling choose Consolidation Add Characteristics .
3. Choose the Mapping tab page and assign the InfoObject (source eld) for the custom subassignment to a target eld in
the consolidation system.
4. Save the changes made to the upload method.
Result
You have extended the upload method by one or more custom subassignments.
After you have exported the customizing le and imported it into the sender system, FI-SL rollup les created in the sender
system will contain the custom subassignments.
Then the consolidation system also accepts the custom subassignments when the rollup le is uploaded.
Example
You want to transfer the Distribution Channel as a custom subassignment to the consolidation system.
The distribution channel has the eld name ZZDCH in the ECMCT table. The associated check table is the TDCH table and the
associated text table is the TDCHT table.
The InfoObject 0DISTR_CHAN is available in BI.
In this example, the entry in the table of custom subassignments looks like this:
Field Name of Custom Field Name Name of Entity Table Name of Text Table
Subassignment
ZZDCH 0DISTR_CHAN TDCH TDCHT
Exporting Customizing Files for FI-SL Rollups

Use
You use this procedure to export your customizing settings from the consolidation system (SEM-BCS) to a data le. These
settings are required in the sender system for rollups of transaction data from the Special Purpose Ledger (FI-SL) component.
You create the customizing le in the consolidation workbench under upload method customizing and you use this le to load FI-
SL rollup les. For more information, see Loading of FI-SL Rollup Files .
The operational applications of the sender system require knowledge of the customizing settings to be able to convert the
transaction data to the accounting objects used in the consolidation system.
Export-Capable Customizing Settings
4/20/2019
The following customizing settings exported from the consolidation system (SEM-BCS) are imported into the following
respective tables in the sender system:
Global settings (table in sender system: TF001)
Default values for subassignments (TF040)
Financial statement items (TF100, TF101)
Subitems (TF115, TF116)
Breakdown categories (TF103, TF103A, TF104)
Consolidation chart of accounts (TF120, TF121)
Dimensions (TF150)
Custom subassignments (check and text tables)
After the rst time you export the customizing settings and import these into the sender system, you should always repeat this
process after making subsequent changes to the settings in the consolidation system.
Customizing Settings in the Sender System
The consolidation system (SEM-BCS) does not export the following customizing settings related to FI-SL rollups. These settings
need to be made in the sender system. (See “Prerequisites in the Sender System” in Loading of FI-SL Rollup Files .)
Independent characteristic values for each type of consolidation (TFIN000)
Master data for subitem categories (TF110, TF111)
Rules for ID combinations for each type of consolidation and consolidation unit (TFIN001)
Allocations of consolidation types and dimensions (TFIN002)
Mapping of transaction charts of accounts to consolidation charts of accounts (TFIN200)
Mapping of secondary cost elements to nancial statement items (TFIN201)
Note
If you use a Business Add-In (BAdI) in the method for the exible upload of FI-SL rollup les to map subitems with
custom subassignments, the consolidation system does not export the master data of subitems and custom
subassignments.
You need to de ne this master data in the sender system.
Prerequisites
You have created and saved an executable method in the consolidation workbench for the exible upload of FI-SL rollup les.
Procedure
1. In the consolidation workbench, open the method for the exible upload of FI-SL rollup les.
2. Choose Export .
If the method contains a custom subassignment and its check and text tables do not exist in the consolidation system,
the system displays a dialog box in which you specify the RFC destination of the sender system (where you want to
import the customizing le).
4/20/2019
The SAP Custom – File Save As dialog box appears.
3. Specify the le’s path, name, and the extension .TXT Save the customizing le.
The system exports the customizing settings to the speci ed le.
Result
You have exported the customizing settings of the consolidation system to a data le.
Once you have imported the customizing settings into the sender system, you will be able to create FI-SL rollup les in the
sender system with transaction data that is converted for use in the consolidation system (SEM-BCS).
Loading of RFBILA00 Files (Periodic Extract)

Purpose
You use this process to transfer reported nancial data from les you create with the RFBILA00 program in the General Ledger
Accounting (FI-GL) component to the SAP SEM Business Consolidation (SEM-BCS) component.
Enterprise Controlling (EC-CS) to the Business Consolidation component of SAP Strategic Enterprise Management. The
procedure in the sender system remains almost unchanged (see Data Transfer Method 'Periodic Extract' ).
You can use the reported nancial data from the RFBILA00 les for the following integrated types of consolidation:
Company consolidation
Business area consolidation
The gure below illustrates a decentralized scenario in which one or more operational SAP systems (sender systems) export
reported nancial data to the consolidation system:
4/20/2019
Prerequisites
Prerequisites in the Sender System
You have built a nancial statement version with the same item keys as in your primary consolidation chart of accounts. (This is
located in Customizing for Enterprise Controlling at Consolidation → Integration: Preparation for Consolidation → Preparations
in the Consolidation System → Tools: Cons Chart, Group Chart, Financial Statement Version → Build and Transport Financial
Statement Version for the Group. )
In the sender system, you have performed the preparations for consolidation in Customizing for Enterprise Controlling at
Consolidation → Integration: Preparation for Consolidation → Preparations in the Sender System
You have activated the Periodic Extract data transfer method. (You do this in Customizing for Enterprise Controlling at
Consolidation → Integration: Preparation for Consolidation → Preparations in the Sender System → Preparation and Activation
of Data Transfer → Activate Data Transfer. )
Prerequisites in the Consolidation System (SEM-BCS)
In the consolidation workbench, you have made the customizing settings for the data basis and the consolidation area where
you want to collect the reported nancial data. You have created a source data basis and speci ed it in the data basis.
The master data and the hierarchies of the organizational units are current.
Process Flow
In the sender system, you use the RFBILA00 program to create a periodic extract of the reported nancial data from general
ledger accounting. See “A. Activities in the Sender System.”
In the consolidation workbench, you de ne a method for the upload of RFBILA00 les. See “B. Customizing in the Consolidation
System (SEM-BCS).”
You load the RFBILA00 les into the consolidation system by running the upload method for each RFBILA00 le. See “C.
Execution in the Consolidation System (SEM-BCS).”
4/20/2019
A. Activities in the Sender System
To create the RFBILA00 le, you go to the SAP Easy Access screen and choose Accounting → Financial Accounting → General
Ledger → Information System . Then you choose either General Ledger Reports (New) → Financial Statement / Cash Flow →
General → Actual/Actual Comparisons → Financial Statement or General Ledger Reports → Balance Sheet/Pro t and Loss
Statement/Cash Flow → General → Actual/Actual Comparisons → Balance Sheet/Pro t and Loss Statement.
On the Special Evaluations tab page, you enter one of the following values in the Extract to Consolidation eld, depending on
which consolidation type is involved:
1 Extraction of postings at the company code level
2 Extraction of postings at the business area level
On the Further Selections tab page, you select Classic List under List Output .
After you enter your settings in Balance Sheet/P+L Statement (Financial Statement) and choose Execute , the File Name for
Extract File dialog box appears.
In the dialog box, choose a logical le name and select Receiver is SEM-BCS .
After you choose Execute, the system creates the RFBILA00 le in a format that can be loaded by the consolidation system.
The transfer of the le to the consolidation system is dependent on your system landscape. For example, you might be able to
access a network.
For more information, see Creating Financial Statements .
B. Customizing in the Consolidation System (SEM-BCS)
You use the exible upload data transfer method to upload an RFBILA00 le into the consolidation system. You de ne your
customizing settings in the Consolidation Workbench.
In the source data basis, you choose the delivered InfoObject catalog 0SEM_BCS_CHA02 for the characteristics, and the
delivered InfoObject catalog 0SEM_BCS_KYF02 for the key gures.
When you execute the exible upload, the system initially loads the RFBILA00 le into the external eld catalog. The
assignments of the elds in the le to the InfoObjects in the eld catalog are xed. The InfoObjects are used in mapping as the
source elds, which you assign to the target elds in consolidation.
The InfoObject catalogs 0SEM_BCS_CHA02 and 0SEM_BCS_KYF02 are available as SAP Business Content in the BI system(
SAP NetWeaver Business Intelligence ) for this purpose. You can also use other InfoObject catalogs for characteristics and key
gures, provided they include all of the InfoObjects contained in 0SEM_BCS_CHA02 and 0SEM_BCS_KYF02.
You create an upload method for the exible uploads with the data type Reported Financial Data and the le type File for
Normal Flexible Upload.
On the Field Catalog tab page, you select Use External Field Catalog and assign the source data basis.
The eld catalog should have the same eld sequence as the RFBILA00 le. Therefore, the data rows in the eld catalog should
contain the following elds in the speci ed sequence:
Indicator, Flag (InfoObject 0Flag); Company (0COMPANY); Business Area (0BUS_AREA); Fiscal Year (0FISCYEAR); Record Type
(0RECTYPE); Version (0VERSION); Posting Period (0FISCPER3); G/L Account (0GL_ACCOUNT); Account Number (0ACCOUNT);
Transaction Type (0MOVE_TYPE); Partner Company Number (0PCOMPANY); Partner Business Area of Business Partner
(0PBUS_AREA) ; Fiscal Year in Which First Acquisition Is Posted (0ACQ_YEAR); Period in Which First Acquisition Is Posted
(0ACQ_PER); Currency Key of Transaction Currency (0CURKEY_TC); Period Value in Transaction Currency (0CS_TRN_TC);
4/20/2019
Currency Key for Local Currency (0CURKEY_LC); Period Value in Local Currency (0CS_TRN_LC); Currency Key for Group
Currency (0CURKEY_GC); Period Value in Group Currency (0CS_TRN_GC).
The RFBILA00 elds FLEVL, RRCTY, and HKONT have no corresponding elds in the consolidation system. If you want to use one
of these elds in the consolidation system, you need to assign a Free Field
On the Mapping tab page, you assign the source elds to the key gures, characteristics, and attributes in the consolidation
system. If required, you also assign values to the other attributes in the consolidation system. For more information, see
Mapping .
On the Settings tab page, you make the following settings:
Column Width: Variable
Column Separator Tabulator
Row Types: Header Row and Data Rows
Digit Separation: Decimal Point
You set no indicator for the Treatment of Dr/Cr Sign Attributes.
You also specify the update mode. If you want to use a Business Add-In (BAdI) for mapping, you need to specify the BAdI lter
value. For more information, see Customizing for Flexible Upload .
Optional: On the Selection tab page, you can de ne a target selection. For more information, see Selection .
C. Execution in the Consolidation System (SEM-BCS)
You load an RFBILA00 le into the consolidation system by running the upload method in the consolidation monitor as follows:
You go to the consolidation workbench, de ne a data collection method, and assign the upload method (see Data Collection
Method ).
In the consolidation workbench, you de ne a task for data collection and assign the data collection method (see De ning a
Flexible Upload ).
You go to the consolidation monitor and start uploading the RFBILA00 le by running the data collection task (see Executing a
Flexible Upload ).
The upload writes data records only when no errors occur.
Result
You have loaded one or more RFBILA00 les into the consolidation system.
Now you can prepare and consolidate the integrated data in the consolidation system.

002 Business Consolidation (SEM-BCS) PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

002 Business Consolidation (SEM-BCS) PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

4/20/2019

Business Consolidation (SEM-BCS)

SAP ERP | 6.16.13

For more information, please visit the SAP Help Portal.

Reported nancial data

Additional nancial data(AFD)

Manual Data Entry with X (X) X (X)

Load from Data Stream X X X X

Manual data entry only allows for:

Adjustments to reported nancial data (documents with posting level 01)

Manual Data Entry

Manual Data Entry of Reported Financial

The layout de nition adheres to the WYSIWYG principle.

Data collection method

Periodic and cumulative data entry

Customizing Settings for Manual Entry of

Customizing Interface for Manual Data Entry

Hierarchies for data entry groups

Data entry layouts

Object tree (2)

See the sections that follow.

Data Entry Layout

A form consists of the following elements:

Row structures (for data rows)

Create new row or column structures

Allocate existing row and column structures

The following types of row structures are available:

Prede ned xed structure

You de ne the data-driven structure as follows:

You enter one or more characteristics (for example, item).

You specify the selection conditions for these characteristics.

You determine how the characteristic values are listed:

You determine how the subtotals are arranged.

Prede ned Fixed Structure

You explicitly specify all data rows for this type.

There are two ways you can portray hierarchies:

The following illustration compares these two presentation methods:

Column structures (for data columns)

You de ne data columns in the same way you de ne data rows:

The following types of column structures are available:

Prede ned xed structure

Lead rows typically have the prede ned xed structure.

You can create formulas for prede ned xed structures.

The Relationship Between Rows and Columns

The permanent parameters

The selection condition for the data rows.

The selection condition for the data columns

De nition of a Data Entry Layout

Create a data entry group by choosing Create in the context menu.

The form can be reused in other layouts if you give it a name.

Create Prede ned Fixed Structure

Create Data-Driven Structure

Create Combined Structure

The structure can be reused in other forms if you give it a name.

De ne the structure. (For more details on de ning structures, see

Save your entries.

Example: Statement of Changes in Property,

You need the following rows:

Fixed asset items

Transaction type for original acquisition cost

Transaction type for accumulated depreciation

Transaction type for book value

You need the following columns: