How to… Configure the Consolidation Business...

How to Configure the Consolidation Business Scenario

SEM-BCS

01.February 2005

SEM-BCS_4.0_Configuration_Validation.doc

-Page 1 of 37 -

HOW TO CONFIGURE THE CONSOLIDATION BUSINESS SCENARIO


Page 2 of 37

Copyright

Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners.



Page 3 of 37

Table of Contents

Introduction to System Landscape .................................................................................................................. 4 Purpose............................................................................................................................................................... 4

Business Scenario ......................................................................................................................................... 4 Contents .......................................................................................................................................................... 4 Target Group................................................................................................................................................... 4 User Management........................................................................................................................................... 5 System Connections ...................................................................................................................................... 5

Overview of Business Customizing ................................................................................................................. 7 Business Warehouse Data Extraction....................................................................................................... 9 Consolidation Workbench........................................................................................................................... 13 Business Warehouse Report to Report Interface .................................................................................. 28 Appendix - Read from Data Stream ............................................................................................................ 31



Page 4 of 37

Introduction to System Landscape

Solution Components Used in this Process

mySAP ERP Core Component (ECC)

mySAP ERP Business Information Warehouse (BW)

mySAP ERP Strategic Enterprise Management (SEM)

Purpose

Business Scenario This business scenario configuration guide applies to the Business Consolidation (BW-based SEM-BCS) Business Scenario 4.0 with the corresponding release of the relevant mySAP ERP application components.

Business Scenario and mySAP ERP Application Components

Business Scenario mySAP ERP Application Components with Minimum Release

Business Consolidation (BW-based SEM-BCS) Business Scenario - 4.0

SAP Strategic Enterprise Management 4.0

SAP Business Information Warehouse 3.5

SAP ERP Core Component 5.0

Contents The business scenario configuration guide contains all necessary steps for implementing the business scenario. The guide sets out the sequence of the individual configuration activities and describes any dependencies between them.

It provides information on the following topics:

Connections between the systems

Business customizing

Setting up the component-specific master data (included in the section Business Customizing)

You can also use R/3 or R/3 Enterprise as a backend operational system instead of ECC. This configuration guide applies to all the following backend functions:

Financial Accounting (FI)

Profit Center Accounting (PCA)

Special Ledger (SL)

New General Ledger (NGL)

For demonstration purposes in this guide we use the Profit Center Accounting to illustrate the step-by-step customizing necessary for setting up the integration between SEM-BCS and ECC.

Target Group Technical consultants

Application consultants

Members of the project team during the implementation phase of a mySAP ERP solution



Page 5 of 37

IT department at the SAP customer site

The section System Connections is aimed in particular at technical consultants whereas the sections Business Customizing and Setting Up the Component-Specific Master Data are aimed at application consultants. For other target groups, the importance of the sections depends on the tasks performed.

User Management SEM-BCS uses the user management delivered for SAP NetWeaver. You can find information on user management in the SAP NetWeaver Security Guide in SAP Help Portal (help.sap.com). In addition see also SEM-BCS on-line documentation for authorization topics specific to SEM-BCS.

System Connections SAP SEM and SAP BW mySAP ERP 2004 consists of ERP Core Components (ECC), Business Information Warehouse (BW), Strategic Enterprise Management (SEM), and other application components in one system.

From the technical point of view, SAP SEM is delivered as an AddOn to the SAP Business Information Warehouse (SAP BW). This means that there is a special kind of system connection between SAP SEM and SAP BW, since a SEM system always contains SAP BW by default.

Therefore, you do not have to set up a connection between SAP SEM and SAP BW using an RFC destination to connect the two physically separated systems, although you can still set up such a connection if necessary. This type of connection might be required if one or more external BW systems are to be used alongside or in place of the SAP BW contained in the SEM system. You normally choose a connection to an external BW system if SAP BW has already been implemented in your company.

Activation of BW Business Contents This section contains information about the BW business contents delivered for SEM-BCS. We suggest that you refer to these business contents to build your own data model. You can use the business contents as delivered or copy them and build your own data model. To display or use them, you need to activate the business contents using the following path:

Business Information Warehouse BW Administration Administration Workbench

Choose the Business Content tab page.

For more information on how to activate business contents, see the BW online documentation in the SAP Help Portal: http://helpportal.wdf.sap.corp:1080/

Info Objects Characteristics in Info Object Category 0SEM_BCS_CHA01

Info Objects Key Figures in Info Object Category 0SEM_BCS_KYF01

InfoSource

0EC_PCA_1 (optional, only used here to demonstrate the integration with ECC, R/3, or R/3 Enterprise)

Basic InfoCube

0PCA_C01 (optional, only used here to demonstrate the integration with ECC, R/3, or R/3 Enterprise)

Transactional InfoCube

0BCS_BC11

Virtual InfoCube for Reporting on the Totals Records

0BCS_VC11

ODS Object for Document Postings

http://www for more details on how to activate business contents.helpportal.com/



Page 6 of 37

0BCS_DS12

Virtual InfoCube for Reporting on Documents

0BCS_VC12

BW Queries Delivered in Role SAP_BW_SEM_BCS_CORP_ACCOUNTANT:

Technical names Descriptions

0BCS_C11_Q000 List of totals records

0BCS_VC11_Q001 Current year with structure percentage balance sheet

0BCS_VC11_Q002 Prior year comparison with variances

0BCS_VC11_Q003 Multi-year comparison

0BCS_VC11_Q004_BS Quarterly comparison of balance sheet

0BCS_VC11_Q004_PL Quarterly comparison of income statement

0BCS_VC11_Q005 Month comparison

0BCS_VC11_Q006 Comparison of local and group currencies

0BCS_VC11_Q007 Version comparison

0BCS_VC11_Q008 Comparison of companies

0BCS_VC11_Q009 Comparison of consolidation groups

0BCS_VC11_Q010 Comparison of consolidation group and companies

0BCS_VC11_Q011 Changes in values from reported to consolidated financial data

0BCS_VC11_Q012 Income statement by regions

0BCS_VC11_Q013 Income statement by functional area

0BCS_VC11_Q014 Asset history sheet

0BCS_VC11_Q021 Comparison of profit centers

0BCS_VC11_Q022 Comparison of profit center groups

0BCS_VC11_Q051_CR Balance Sheet Current Year Crystal

0BCS_VC11_Q052_CR Prior Year Comparison with Variance Crystal

0BCS_VC11_Q053_CR Balance Sheet with Multi-Year Comparison _Crystal

0BCS_VC11_Q054_CR Income Statement Prior Year Comparison with Variances Crystal

0BCS_VC11_Q055_CR Income Statement Quarterly Comparison Crystal

0BCS_VC11_Q056_CR Operating Expense by Functional Areas - Crystal

0BCS_VC11_Q057_CR Income Statement by Segments Crystal

0BCS_VC11_Q058_CR Revenue by Country Crystal

0BCS_VC11_Q059_CR Changes in Stockholders' Equity Crystal

0BCS_VC11_Q060_CR Cash Flow Statement Crystal

0BCS_VC12_Q001 List of journal entries



Page 7 of 37

Crystal reports delivered in role SAP_BW_SEM_BCS_CORP_ACCOUNTANT:

11QE4B9L7OQOF3PK14CSNFNJW Development of Fixed Assets (Portrait Format)

4H2MNHLEUNDD3ADXQT7U9VXFG Development of Fixed Assets (Landscape Format)

6KJIDB0DKEG71H9G9Z1IR468I Crystal Report: Balance Sheet - Current Year

C2R257DL4WCKEG7O27Z73705U Crystal Report: Balance Sheet Current Year Transaction

9LMMD1MVTL817FRN6LG6AQKFW Crystal Report: Balance Sheet - Current Year with Percentages

9HYGOFC4AQBM8FGJWUEKTF9PU Crystal Report: Prior Year Comparison with Variances

BOL8U6V4705BLFJOBE1VNBTA4 Crystal Report: Balance Sheet with Multi-Year Comparison

AVRN9PP03V5AULLXXXBC3RSHE Crystal Report: Income Statement PY Comparison with Variance

6BKXO71M40IHWODYK1KWRNG Crystal Report: Income Statement - Quarterly Comparison

F2BP4BPC7PSWMX2X50JELFCVW Crystal Report: Income Statement by Segments

386WDDT1RUV6K2QWNDA6M9GUQ Crystal Report: Revenue by Country

AQEDT0882EHSN4BISC3SLNTV6 Crystal Report: Changes in Stockholders' Equity

EXHU78HLG9Q5GG9BX25ICD7NG Crystal Report: Operating Expense by Functional Areas

Activation of SEM-BCS Business Contents We deliver standard contents for SEM-BCS, including the following:

Data basis

Consolidation areas

Chart of accounts

Tasks

Methods

Method layouts

We suggest that you refer to these standard contents to facilitate the project implementation. You can run report UC_CONTENT_AC TIVATE to activate SEM-BCS contents for both the new installation and the upgrade project. For more information, see SAP Note 645753 and related notes.

Overview of Business Customizing The following flowchart displays an overview of the key customizing activities to set up the integration between SEM-BCS and Profit Center Accounting in ECC.



Page 8 of 37

Integration Customizing of ECC 5.0 and SEM-BCS 4.0 forProfit Center Ledger

Check standard datasoruce (0EC_PCA_1)

for table GLPCT

Activate content cube0PCA_C01 and

update rule

Activate content infosource

0EC_PCA_1

Customize datamapping rules in BCS

Create FS item as anavigational attribute

of GL account

ECC component BW Component SEM-BCS Component

Create Company as anavigational attribute

of Compny Code

Customize Report toReport Interface to

jump fromConsolidated reports

to PCA reports

Check if IDES dataexists in GLPCT

Customize Task of"Read from Data

Stream"

Customize Data Basis,Consolidaiton Area,

Master Data

Customize otherconsolidation tasks

Customize Report toReport Interface to

jump from PCAreports to R/3

transactional code2KEE and KE5Z



Page 9 of 37

Business Warehouse Data Extraction

This is an excerpt of the extraction technique in the Business Warehouse.

For more information on Business Warehouse, see the BW online documentation at: http://helpportal.wdf.sap.corp:1080/

Procedure: Extracting Master Data Mapping Here we discuss the mapping between the master data (not the master data itself, which you need to maintain in SEM-BCS).

There are two kinds of master data relevant to setting up the integrated data mode for ECC and SEM-BCS:

General Ledger (GL) Account

Company Entity

Both kinds of master data have their local and group fields.

For example, in ECC a company code posts transactional data to its operation GL accounts. This information needs to be translated into the FS items of its company entity later on when the subsidiary submits the operational data into the consolidation system.

Therefore, both the mapping between the operational GL account and FS items and the mapping between the company code and the company need to be established and visible in SEM-BCS. You can store the mapping information in various places, such as in ECC, flat files, BW, or in SEM-BCS. Regardless of where the mapping is stored initially, it should always be recognized in SEM-BCS in one way or the other.

If your subsidiary uses ECC (old R/3) as the operational financial system, we suggest that you store the initial mapping in ECC. We suggest that you use table SKA1 for the GL accounts and table T001 for the company entities.

If your subsidiary does not use ECC, you can store the initial mapping in a flat file.

GL Account Mapping:

Extract Mapping to the Business Warehouse Standard Approach

You are going to load GL account mapping stored in ECC table SKA1 into the master data of InfoObject for the GL Account. Note that BW master data for GL account varies across different components. For example 0ACCOUNT denotes the operational GL account in the function of Profit Center Accounting while 0GL_ACCOUNT denotes the operational GL account in the function of General Ledger Accounting. Here we use 0ACCOUNT for illustration purpose. 0ACCOUNT should have a navigational attribute 0CS_Item, which is analogous to the group GL accounts.

The use of navigational attribute has two advantages:

To facilitate BCS to retrieve the mapping at a later stage

To allow you to jump back from the consolidation reports to the operational reports

Here are the steps:

1. Go to transaction code RSD1 (InfoObject maintenance screen), create 0CS_ITEM as a navigational attribute of info object 0ACCOUNT. Activate info object 0ACCOUNT.

2. Go to BW administration workbench, create InfoSource and assign DataSource for master data extraction for 0ACCOUNT. Make sure to include 0FS_ITEM in your extractor.

3. Extract master data from ECC into InfoObject 0ACCOUNT.

After performing the above steps you successfully replicate the GL account mapping in the BW master data table. This table will be read into SEM-BCS at a later stage during the task run of Read from Data Stream.

http://helpportal.wdf.sap.corp:1080/



Page 10 of 37

Extract Mapping to the Business Warehouse Alternative used for Solution Validation

Since the mapping between the operational chart of accounts INT and the group chart of accounts 20 is not yet available in the current release of the ECC component, for the ease of testing during the Solution Validation we are going to store the mapping initially in a flat file instead of in the standard ECC table SKA1. In this flat file we map each GL account in chart of accounts INT into the FS items in chart of account 20.

Here are the steps:

1. Store flat files GLACCOUNT_KEY_QE2_SS and GLACCOUNT_TEXT_QE2_SS in your local PC:

The first file has the mapping between the GL account keys and the FS item keys.

The second file stores the texts for the GL accounts.

2. Go to transaction code RSD1 (InfoObject maintenance screen), create 0CS_ITEM as a navigational attribute of info object 0ACCOUNT. Activate info object 0ACCOUNT.

3. Go to BW administration workbench, create InfoSource and assign DataSource for master data extraction for 0ACCOUNT. Make sure to include 0FS_ITEM in your extractor.

4. Extract both flat files from the first step into InfoObject 0ACCOUNT.

After performing the above steps you successfully replicate the GL account mapping in the BW master data table. This table will be read into SEM-BCS at a later stage during the task run of Read from Data Stream.

Customize Load from Data Stream in Consolidation Workbench.

The purpose of this setting is to allow the system to access the mapping relationship in BW during the task run of Read from Data Stream and transform the PCA data into BCS format.

How you customize the BCS depends on how you performed Extract Mapping to the Business Warehouse. According to our approach in this scenario use of navigational attribute to store the corresponding group account you will then use the rule of Moving the navigational attribute in BCS customizing.

Different BCS mapping rules might apply if you store the initial mapping differently from what you use above.

? For more information, see the BCS customizing.

Company Mapping

You apply the similar steps of GL mapping above to the company mapping.

Extract Mapping to the Business Warehouse Standard Approach

Apply the same procedure as in the above section of Extract Mapping to the Business Warehouse Standard Approach for the GL account mapping to the company mapping.

Here are the steps:

1. Go to transaction code RSD1 (InfoObject maintenance screen), assign info object Company 0COMPANY as a navigational attribute of Company Code 0COMP_CODE. Activate info object 0COMP_CODE.

2. Go to BW administration workbench, create InfoSource and assign DataSource for master data extraction for 0COMP_CODE. Make sure to include 0COMPANY in your extractor

3. Extract both flat files from the first step into InfoObject 0COMP_CODE

After performing the above steps you successfully replicate the Company mapping in the BW master data table. This table will be read into SEM-BCS at a later stage during the task run of Read from Data Stream.

Extract Mapping to the Business Warehouse Alternative used for Solution Validation

For the ease of testing during the Solution Validation you are going to load data from only one company code rather than extracting the complete mapping in the ECC table or flat file. So you are going to enter one row of mapping entry directly in the BW master data.



Page 11 of 37

Enter Mapping in the Business Warehouse

1. Go to transaction code RSD1 (InfoObject maintenance screen), assign info object Company 0COMPANY as a navigational attribute of Company Code 0COMP_CODE. Activate info object 0COMP_CODE.

2. Enter a Company value as a navigational attribute of Company Code. Activate info object 0COMP_CODE.

Example: Enter Company C1100 as a navigational attribute of Company Code 1000.

Customize Load from Data Stream in Consolidation Workbench

The purpose of this setting is to allow the system to access the mapping relationship in BW during the task run of Read from Data Stream and transform the PCA data into BCS format.

How you customize the BCS depends on how you performed Extract Mapping to the Business Warehouse. According to our approach in this scenario use of navigational attribute to store the corresponding group company you will then use the rule of Moving the navigational attribute in SEM-BCS customizing.

Different BCS mapping rules might apply if you do it differently in the first step.

? For more information, see the BCS customizing.

Procedure: Customizing of Extracting Transactional Data from ECC 1. Any external (FI) or internal (PCA) accounting data in ECC required for consolidation can be extracted to

BW. We deliver standard extractors and InfoCubes for some while for the others such as special ledger tables you can create your own extractor and InfoCube easily with the standard BW technique. The table below summarizes different techniques for different table/ledger combinations:

Types of Consolidation

ECC Table/Ledger BW Contents Methods to Pull the Data into BW

Management consolidation with profit center

GLPCT/8A DataSource 0EC_PCA_1

InfoSource 0EC_PCA_1

Update rule 0EC_PCA_1

InfoCube 0PCA_C01

1. Activate contents

2. Load data

Legal consolidation with company

GLT3/09 NA 1.Generate data source in ECC for special ledger tables with transaction codes BW01 and BW03MAST (CSS note 600425)

2. Create own BW InfoSource and cube

3. Load data

Legal consolidation with cost of sales accounting

GLFUNCT/0F NA 1. Generate data source in ECC for special ledger tables with transaction



Page 12 of 37

codes BW01 and BW03MAST (CSS note 600425)

2. Create own BW InfoSource and cube

3. Load data

All the above in the new General Ledger

FAGLFLEXT DataSource: 0FI_Gl_10

InfoSource 0FI_GL_10

Update rule: 0FI_GL_10

InfoCube: 0FI_GL_10

1. Activate contents

2. Load data

In this scenario we use the first case of loading profit center data to the standard BW contents. Here are the steps:

1. Go to Business Information Warehouse BW Administration Administration Workbench and choose the Business Content tab page.

2. For more information on how to activate business contents, see the BW online documentation

3. Create one ECC source system for BW.

4. Check if data source 0EC_PCA_1 exists. If not, replicate this data source from the source system.

5. Activate InfoSource 0EC_PCA_1, update rule 0EC_PCA_1, and InfoCube 0PCA_C01.

6. Assign data source to InfoSource 0EC_PCA_1.

7. Assign update rule to the InfoCube.

8. Create InfoPackage for the assigned DataSource under InfoSouce 0EC_PCA_1.

9. Load data

After performing the above steps the profit center data in ECC is replicated in the PCA InfoCube with fields such as company code, account, profit center, movement type, currency type, one currency key, fiscal year/period, and so on.

In contrast the consolidation InfoCube has fields such as consolidation unit, FS items, consolidation profit center, fiscal year, period, and three separate currency keys.

Due to the different data structures between the PCA cube and the consolidation cube you need to transform the PCA cube data into the format recognized by the consolidation cube before they can be replicated in the consolidation cube and continue the consolidation functions. This data transformation is enabled by using the mapping customizing in the consolidation workbench, as described in the ollowing section: in the Section Consolidation Workbench. Method: Load from data stream



Page 13 of 37

Consolidation Workbench Use

The Consolidation Workbench is the central work environment for configuring the consolidation system. There are two different types of views, both of which contain the same customizing objects:

Process view

This is arranged in a hierarchical structure that provides a logical sequence for your customizing steps.

Technical view

This represents the types of customizing objects (characteristics, methods, tasks, and so on).

The process view is the best view for customizing.

Procedure

In the SEM system, choose Strategic Enterprise Management Business Consolidation Consolidation Workbench. Open up the Process View by clicking on the black arrow. Below we look at each of the configuration components.

Note that as you work through each step of the configuration screens you can see on the bottom portion of each screen a section called Activities. This is helpful information to assist you in your configuration setup.



Page 14 of 37

Data Model

Click on the folder Data Model to expand the hierarchy

1. Data Basis: The data basis defines the data model for consolidation. Every data basis consists of the following sections:

Data Streams Tab > Data Streams identify the location (info-provider) for the storage of consolidation data. The key data stream is the InfoCube for the storage of totals records. This represents a BW InfoCube, which must be defined in such a way as to meet the company-specific consolidated reporting requirements. Subsequently all other data streams can be automatically generated by the system based on the definition of this primary infoCube. Therefore, it is not necessary for the customers to have to specifically define these other data streams. This applies both to the actual and virtual info providers.

The RFC destination identifies the BW system to be used. You can use a local BW system that is the same SEM system in use or you can specify a BW system that is physically separate from the SEM system.

You then define the InfoCube in BW to hold the totals consolidation data records. Based on this cube, the other required info providers can be automatically generated, including the virtual InfoCubes, which will be used for the reporting functionality.

Customers can use the delivered BW content cube 0BCS_C11. Or they can use it as an example for the development of customized data basis for consolidation. In this example we are using the standard delivered InfoCubes. The Totals Records data stream is what primarily defines the data basis by defining what characteristics and key figures are available in the data model. The other data streams are optional.

For more information, see the SEM-BCS 4.0 documentation.

Data Model Tab > Here you define how a particular characteristic available from the BW InfoCube will be used in consolidation and what role the characteristic plays when posting data from consolidation to BW. Here you are linking the consolidation application with the BW application.

Role concepts provide for significantly enhanced flexibility in terms of the data model as all consolidation functions are based on the role an info object plays as opposed to the info object itself. Each characteristic and each key figure in a data model has exactly one role. In more than one data basis, a characteristic or key figure can have more than one role. The same role can be used by more than one characteristic in a data basis.

Authorizations Tab > Here you can determine how the authorization is to be assigned and checked: per characteristic (for example, across all cons units) or per characteristic value (for example, for each consolidation unit). Where authorization should be restricted by value, you need to select the characteristics used to restrict authorization on this screen.


2. Cons Area > Select Cons Area. The consolidation area is a subset of the characteristics and key figures available in the data basis. It represents a unique set of data. You can create one or more cons areas within a single data basis by selecting the specific characteristics and key figures available in the data basis. Tasks and methods are attached to each cons area. Each cons area has a unique chart of accounts.

Implementation Considerations: In many cases only one consolidation area per data basis is required but the flexibility exists to create numerous consolidation areas under one data basis.

For example, where methods, tasks and breakdown categories vary significantly for management consolidation purposes as opposed to legal consolidation, and yet a single data basis can support both views, it might be most effective to create two consolidation areas, one for legal and one for management, as opposed to trying to



Page 15 of 37

handle both within the same consolidation area or creating two entirely separate data basis. This is generally a design and implementation issue.

Fields Tab > Here you select which fields from the underlying data basis definition are applicable to this particular consolidation area. In addition you can define whether a characteristic is to act as a permanent parameter and whether the value can be selected or remains fixed when assigning the permanent parameters under Environment>Parameters ??? should be bold?. The characteristics version, group currency, fiscal year, and period are permanent parameters by default. You also decide here which parameters you want to display in the page header

Settings Tab > Here you define certain global parameters and settings for the consolidation area, including whether you want to activate status management used for consolidation monitor, whether you want to display the cons area as a parameter in the page header, whether you want to use maximum sets in breakdown categories, how to handle the appropriation of retained earnings, consolidation functions to be used, and length of value fields in the task log.

3. Fixed Characteristics > Here you define what characteristics are fixed in value, such as chart of accounts and controlling area.

4. Periodicity > The periodicity is determined by the following three items:

Fiscal Year Variant: links the calendar year with the fiscal year and defines how many periods and special periods comprise a fiscal year. It also assigns the accounting periods in which the system can make postings. It should be noted that with BW-based consolidation there is no limitation to only 16 periods in the determination of a fiscal year variant. Fiscal year variants based on weeks or even days can also be established.

Period Category: defines what periods are affected for a given consolidation task for a given consolidation unit. For example, assume that you are performing a currency translation task for cons unit A using translation method T1 but only in periods 006 and 012. In this case you assign a period category that includes only period 006 and 012.

Consolidation Frequency: determines the number of consolidated financial statements to be generated during a fiscal year. You can perform annual, semi-annual, quarterly, monthly consolidation or any other combination.

Fore more information on periodicity, see the SEM-BCS 4.0 documentation.

5. Currency Key > This is a table that identifies all the currencies available for posting/translation. Local currency is defined for a particular consolidation unit. If the local currency is not the same as the group currency, translation from the local to group currency is required. The group currency is a separate characteristic in the data basis. You can have multiple group currencies in a single version. The group currency key is set as a permanent parameter and you must always use it when defining your BW reports.

6. Units of Measurement > This takes you to another transaction where you maintain the units of measurement you are using if you want to bring into consolidation quantity-based data in addition to value information.

Master Data

1. Versions > these enable parallel consolidation for different data categories (ex. Actual, Plan, Target), alternate accounting principles (ex. US GAAP, German HGB), valuations, and simulations (exchange rate effects or effects of a divestiture).

In addition system design can in many areas be made version-specific. A consolidation area can have more than one characteristic with the role version. If multiple characteristics have the role version, you can choose the version combination to be used in consolidation.

An example is where you have monthly rolling forecasts but instead of having to define each month as a separate version you create a primary version characteristic denoted as Rolling Forecast (as opposed to Budget or Actual) and then a secondary version indicator which



Page 16 of 37

identifies the specific period to which the primary version relates (for example, March rolling forecast as opposed to April Rolling Forecast).

A second example might be:

Characteristic Values

Data Category Actual/Plan/Target

Valuation Corporate Group/Profit Center

GAAP US GAAP/HGB

Various customizing settings depend on the version. These settings are stored internally in special versions. Special versions summarize the customizing settings according to specific topics for example data collection and currency translation. When you define versions, you can assign the customizing settings of one version to several other versions. This lets you copy the customizing settings easily across different versions without having to repeat the same customizing activities.

For more information on the version management capabilities, see the SEM-BCS 4.0 documentation.

2. Consolidation Groups > a consolidation group is a grouping of multiple consolidation units or other lower-level groups, created for the purpose of generating consolidated reports across the units or lower-level groups that make up the overall consolidated group.

You can group consolidation units into one group or create multiple groups and arrange them in a hierarchy. You can also build multiple hierarchies, in parallel, to structure the organizational units according to different perspectives (for example management that is, regional or product line views as opposed to legal views).

3. Consolidation Units > the consolidation unit is the lowest level in the corporate structure that is used as the basis for consolidation. You can use the role consolidation unit for characteristics Company, Profit Center, Business Area, Plant, and so on. A data basis can have one or two characteristics with the role consolidation unit, such as company and profit center. You can also join consolidation units (such as company and profit center) in a matrix organization. In customizing you define the valid combinations of companies and profit centers for posting consolidation entries.


Suppose a reorganization took place in the third quarter of the year. You need to reflect this organizational change in your consolidation process. Suppose one company was now part of a new consolidation group for reporting purposes instead of belonging to the old group. We will account for this change by using the correct parameter settings (version/period/year) to reflect the change:

o Hold your cursor down on this specific company and drag it over to the new cons group in the hierarchy.

o If you save this change the system time stamps the date of the change in the base version in which you save the change. In BW reporting you can then build a report using variables to view the consolidated results both before and after the reorganization took place. This functionality emphasizes the dynamic interface between SEM-BCS and BW.

o This same type of changes to the hierarchy structure can be done with the consolidation groups as well.

4. Items > the financial statement item is the central account assignment object in consolidation. It is equivalent at the consolidated group level to the account in the general ledger. A



Page 17 of 37

financial statement item is only valid for the consolidation chart of accounts in which it was created. You can use financial statement items to post statistical amounts as well.

Let us use the delivered chart of accounts 01 as an example. Double-click on Item under the Items folder. In the left lower panel you see three FS item hierarchies delivered in the business content. Click on the full screen icon (last icon on right) in the Item menu.

Expand the income statement hierarchy and choose any FS item such as 30110000.You can use the search function (binoculars icon) to find a particular FS item in the hierarchy. Use the green arrow in the right corner to display the FS item. The master data record of an FS item identifies the short/long description, the normal debit/credit sign for this item, the type of FS item, and the breakdown category (discussed below). This FS item has assigned breakdown category 4200.

Use the yellow arrow in the left hand corner to return to the hierarchy. Click on the full screen icon to return to the workbench.

Selected Items > If you double-click on the Selected Items you will see the table where you maintain the accounts for the closing of postings affecting the income statement to the balance sheet. In the chart of accounts 01, account 25712000 is the current year retained earnings account used to close the profit/loss to the balance sheet with the offset posting to the income statement clearing account 39000000.

Integration; Master Data Hierarchies

You use master data (consolidation units, consolidation groups, FS Items) to portray your corporate structure in the consolidation system. In SEM, the storage of the master data for a characteristic is distributed. Depending on the type of master data alternate scenarios exist. :

A. Master data is stored in BW.

B. Master data is stored in SEM.

C. Master data is stored partially in BW and partially in SEM.

You can maintain the master data and hierarchies for consolidation centrally in SEM. Once this is saved then SEM is updated the moment it writes the master data directly into BW.

In addition to manually maintain the master data you can also upload master data from a file. For example you can download the master data (i.e. a chart of accounts from R/3 into Excel, assign the necessary additional consolidation specific master data attributes (breakdown categories for consolidation) and then upload into SEM-BCS by utilizing flexible upload functionality.

Use of Hierarchies:

In order to create a hierarchy for a characteristic in SEM-BCS the characteristic in BW must support hierarchies (hierarchy indicator is selected).

A change to a node in a hierarchy that is also used in another hierarchy will have the change reflected in all hierarchies where that node is used.

Hierarchy nodes can be time and version dependent. For example, if you add a cons unit to a node in a hierarchy as of a particular period/year, only the node and not the entire hierarchy is time stamped with that change.

A characteristic value can belong to more than one hierarchy .

Consolidation unit and consolidation group hierarchies are always both version and time dependent. FS item and subassignment hierarchies dependency on time or version is optional. In the BW info object maintenance you maintain whether the hierarchy of the characteristics is version dependent and the entire hierarchy structure is time dependent.

This is useful when in BW reporting you want to take a look at the impact a reorganization has had on the consolidated results of operations before and after the reorganization. The virtual cubes used in consolidation reporting will dynamically determine and report the financial results based on the hierarchy structure that was in place as at a given point in time. You can achieve this via your query definition in BW through the use of query reference year and period (reference year and period are set in the query properties generally as variables).



Page 18 of 37

These reference characteristics will then be used to determine the structure of the hierarchy to be used.

5. Subassignments > subassignments are characteristics used to further differentiate or provide additional detail on the values of the characteristic financial statement item. Any characteristic can be used as a subassignment. SAP delivers pre-defined sub-assignments such as partner unit, investee unit, etc. that have associated with them consolidation logic. In the delivered content there are also sample standard subassignments for country and product group that do not require any consolidation logic. Each customer can define within their data model the additional sub-assignments, which they require to meet their specific consolidated reporting requirements. Subassignments are particularly useful where you want to achieve multi-dimensional reporting in consolidation. There is for most customers effectively no practical limit on the number of characteristics you can assign with SAPs consolidation tool, although one must take into consideration the impacts on performance of continuing to add additional sub-assignments

Under the subassignments folder select the breakdown category subassignment. Select breakdown category 4200 that was referred to in item 4 above. Here you will see the rules that are followed when posting to a FS item that is assigned this breakdown category. Note that the characteristic country is a required assignment. In the data model referred to above you can see the role that the characteristic country has been assigned to is type subassignment.

Note above that FS item 30110000 (sales-goods) has this breakdown category. Any posting to 30110000 requires that the country being sold to also be assigned. This way in reporting you can drilldown to view sales by country. It should be noted that the rules as defined within the breakdown category for a particular account(s) are subsequently used both during data loading and direct entry to validate that the data being submitted is complete.

6. Customer Defined Attributes > You can freely define your own attributes for reporting or customizing purposes. For example, an attribute such as plant type may have the values manufacturing, sales or management. The attributes are available in the definition of BW queries as navigational attributes , which you can use for selecting/analyzing data during reporting. This is another way to fulfill multi-dimensional reporting requirements.

Consolidation Functions

Here is where you customize the various consolidation functions that you will use to perform your periodic consolidation process. The definition of consolidation functions is designed to follow the sequence in which they would normally be performed as noted below:

1. Data Collection

a. Define a method of Data Transfer

You have to create a data transfer method to identify the various types of data collection methods we are using for each type of data collected. For example the totals records (unconsolidated data/reported financial data) can be posted to consolidation via load from data stream and flexible upload while additional financial data such as investment, equity, and inventory items are posted using online entry.

b. Method: Load from data stream

You can use this method to load reported financial data from all BW infoprovidor (InfoCube, ODS objects) to the consolidation system. You define the details in three separate tabs:

Settings

You define the source system, the source InfoProvidor, the update mode, input type (periodic v.s cumulative data type), among other features.



Page 19 of 37

If your source InfoProvidor is one of the standard content cubes or its copy, we suggest that you use the cumulative data type. This will ensure that the accumulated data of InfoObect 0Balance of the source InfoCube be converted to the periodic values in consolidation correctly.

Mapping

You define the one to one conversion rule between the fields in the source InfoProvidor and the target cube.

Note: In release 4.0/SP01 the transactional currency amount in the source cube cannot be read correctly into BCS cube due to missing transactional currency key in the data extractor. A CSN note will be delivered soon explaining how to enhance the data structure with the transactional currency key in the customer project. For validation purposes please focus on local currency mapping.

See Appendix - "Read from Data Stream" further details on various features of mapping rules.

c. Method: Flexible Upload You can use the flexible upload to load the following types of data from a text file to the consolidation system: Transaction data:

Reported Financial Data

Additional Financial Data

Investment Equity Equity holding adjustments Goodwill

Documents Master Data:

Consolidation groups, including consolidation group hierarchies

Consolidation units, including consolidation unit hierarchies

Items, including item hierarchies

Breakdown categories

Other master data. For example, transaction types or functional areas.

Features: Here you define the format structure of the file, which contains the data to be loaded to the consolidation system. You also define the row type, the upload mode, and the input type ( to load periodic values or cumulative values). The differences among different upload modes are as follows:

Delete All Existing Data > all existing data records for the period are deleted and the data is reloaded.



Page 20 of 37

Delete Uploaded Records > deletes and reloads only the applicable data for units you are changing

Overwrite > overwrites records to be changed

Do not modify > used when loading master data (if you add additional accounts and want to leave existing accounts alone). Existing records are not modified but new records are added.

d. Method: Data Entry Layout

As an alternative to loading data via flexible upload, you can create layouts for entering financial data reported by consolidation units and combination of consolidation units directly to consolidation. Within this area you define the layouts and group them into layout groups according to their usage. Refer to the SEM-BCS 4.0 documentation for further details regarding how to create data entry layout.

e. Define the task

You have to assign the data transfer method to the task for data collection. This assignment can be consolidation unit dependent different subsidiaries use different methods to collect reported data to the consolidation system. The consolidation frequency and period category are also assigned to determine when this task is to be run. Each function/activity to be performed in the monitor must be assigned to a task, which in turn will be assigned to the definition of the monitor.

2. Manual Posting

Manual postings are another way of getting data posted in to the consolidation system. You first define the document type and then define the task and assign the document type to the task. Normally the reported financial data from the reporting units are entered via the data collection methods noted above. Manual postings tend to be used for activities such as the posting of late adjustments or topside corporate entries. In addition to updating the total balances manual postings also create posting documents providing full audit trail capabilities. In addition manual postings are always stored under a different posting level from the reported data, allowing for the isolation of adjustments as opposed to base amounts submitted by the units.

a. Document type

1. Properties Tab

Here you identify the posting level (type of entry), balance check, whether posting of deferred income taxes is desired, etc.

2. Subassignment Tab

Here you control what the input layout will look like.

3. Selected Items Tab

Identify the applicable clearing accounts.

4. Deferred Income Taxes Tab

Assign FS items for posting deferred income taxes

b. Task

Assign document type(s) and consolidation frequency to the task.

3. Validation of Reported Data

a. Define the method



Page 21 of 37

The customizing of the validation rules is similar to the validation functionality that exists in R3 FI/CO. Two types of validation exist within consolidation. The first are automatic validations delivered by SAP during data collection. These occur at the time data is being loaded/posted and include checks for validity of master data as well as ensuring that data submitted is consistent with the assigned breakdown categories. In addition you can also define customer specific validation checks, which then verify the data according to the customer specific logic upon running the validation task. The second type of validation is what we are going to cover in this configuration guide.

b. Define the task

Validation tasks can be performed at various stages throughout the entire consolidation process. For example, you can validate the reported financial data, validate additional financial data, validate the adjusted data, and validate the consolidated data. You also need to assign the consolidation frequency and period category to determine when validation task is to be run. You can assign different validation methods for different consolidation units to the same validation task.

4. Currency Translation and Rounding

The consolidation system allows for the collection of the reported financial data by the consolidation units in the units local currency. If the local currency differs from the group currency then this data needs to be translated to the group currency before you can produce consolidated financial statements.

SEM-BCS uses the standard exchange rate tables which can, if desired, be extracted from R/3.

Translation to group currency can in certain cases be performed within R/3 and this same data can then be used within SEM-BCS as opposed to performing translation directly in SEM-BCS.

SEM-BPS uses this same currency translation function as well.

Currency translation involves a two-step process. The system first applies a reference rate to the local currency values to arrive at translated values for all accounts. A second translation is then performed to adjust this translated amount to the required translation amount for consolidation. The difference in the amounts between the two rates is booked as the translation difference. This two-step approach allows for the ability to capture the impact of foreign exchange movements needed for cash flow reporting..

a. Settings.

Within this area one maintains the detail as to the valid currency types, relationships between currencies, exchange rate indicators and exchange rate types, and exchange rate, which are subsequently required for purposes of currency translation. In addition you need to maintain the currency translation keys. Various translation keys are available and these control the logic, which is applied in performing the translation for a selected set of accounts. The primary translation keys are:

Cumulative Method > generally applied to the balance sheet Items. This key adds the values across all periods, in order to come to the cumulative closing balance and then applies the applicable exchange rate to this cumulative balance.

Periodic Method > generally for the income statement Items. The system translates the current period movement and then adds this to the balances for the prior periods to come to the overall balance year to date.

You can also create your own translation logic with the user-exit.

b. Method Layout (optional)

Before you define the method, a valid method layout for configuration purposes must exist. Layouts are defined under the technical view of the workbench. Open up the folder Method Layout. SAP delivers layouts which you can use, however, there may be times when you want to create your own layouts for configuration purposes, in



Page 22 of 37

which case you would go to method layout in order to do this. When you create a method it will ask what layout you want to use.

c. Method

1. Reference Translation Tab

Here you define the necessary setting for translating all values using one single exchange rate. You assign the source key figures (normally local currency amount) to be translated, the exchange rate indicator to be used, and the rounding method.

Note: You need to create a rounding method and then assign it to the currency translation method. Refer to the rounding function under the consolidation functions node. Here you create a method to define where any rounding differences that occur should be posted. All rounding differences must balance to zero. There are no tolerance limits available. Currency translation will not update if there are rounding differences. It is recommended you use separate accounts to capture the translation differences for audit purposes.

2. Specific Translation Tab

Here you define the second step of translating individual sets of accounts with different currency translation keys and exchange rate indicators.

3. Differences Tab

Here you assign the FS items to post the currency translation differences. You can differentiate between debit and credit items. Furthermore you can restrict the postings to some attributes such as movement types, allocation units, partner units, etc.

c. Task

Define a task and assign the method to the task. The settings in the task is similar to those in the other tasks mentioned above.

5. Allocation

You can use the allocation function to assess or distribute standardized data.

The allocation function retains the sender/receiver relationship in its postings. This is different from SEM-BPS where this audit trail does not exist at the moment.

In your data model you would assign the characteristic the available sender/receiver relationships. For example the characteristics company and profit center can be defined for use in allocation.

Note: There are two separate characteristics allocation company and allocation cons profit center which reference the characteristics company and cons profit center that means they do not have their own master data. You can also execute the allocation without having those characteristics in your data model. The only reason for these characteristics is if you like to report this information. That means if you are interested in whom the company was that you received the allocation from (sender) or which company was the allocation made to (receiver) then this information would be posted and you can use it in BW reporting for detailed analysis. If you are not interested in capturing this additional detail for reporting you would not need these characteristics defined in the data model.

a. Define the document type




Page 23 of 37

Before you define the method, a valid method layout for configuration purposes must exist. Layouts are defined under the technical view of the workbench. Open up the folder Method Layout. SAP delivers layouts which you can use, however, there may be times when you want to create your own layouts for configuration purposes, in which case you would go to method layout in order to do this. When you create a method it will ask what layout you want to use.

c. Define the method

Use the delivered layout as an example. You should define the following sections in the method:

1. Sender/Receiver Tab

You define the FS items, consolidation units, other selection attributes if necessary for both senders and receivers.

2. Trigger Tab

You select the types of data and the FS items, consolidation units, and other selection attributes if necessary to trigger the allocation process.

3. Distribution Key

You select the types of distribution data and the percentage to be applied for allocation.

4. General

Specify whether iteration is desired or not.

d. Define the task

Assign the method and the document type to the task. The settings in the task is similar to those in the other tasks mentioned above.

6. Inter-unit Elimination and Reconciliation

Inter-unit Reconciliation

Prior to running inter-unit eliminations you can use the task reconciliation to determine any elimination differences without having the system post elimination entries. You would manually correct erroneous entries in the reported financial data or post manual standardizing entries. This task can be placed immediately after data collection so as to allow for immediate comparison of inter-unit balances once the reported data has been submitted from the units. Currency translation is simulated in order to allow for comparison of balances in the common group currency. The reconciliation task leverages the configuration for the corresponding actual inter-unit eliminations. It uses the same methods as inter-unit elimination.

Inter-unit Elimination

You can use this function to eliminate both inter-company receivables/payables and inter-company revenues/expenses. This is for most companies the most widely used and key piece of functionality within the consolidation process.

Inter-unit eliminations within SAP makes use of the concept of a partner unit. The partner unit represents the related party with whom a unit is transacting business. The core R/3 system provides a great deal of functionality designed specifically to capture trading partner detail at the time a transaction occurs. Trading partner detail in R/3 can be captured for company, business area and profit center.

The basic concept behind eliminations within SAP is that inter-unit balances are compared and eliminated for every unique pair of partner units. Subsequently, via the reporting process



Page 24 of 37

(i.e. logic within the virtual cubes) the system checks to determine whether or not both the consolidation unit and its trading partner are included in a particular consolidated group being reported upon. If both units are within the group the elimination is picked up and included in the reported consolidated balances. If one or both are outside the group then the item is excluded. This approach provides for dynamic restatement when consolidation groups are changed.

a. Define a document type.

Click on the folder IU Elimination and Reconciliation. Here you would first define the document type that identifies the FS items for posting, the posting level, key figures affected, etc. You would then define the method. You would then assign the document type and method to a task you would create to execute the reconciliation.

The document type must be set to posting level 20. This allows for the posting to cross units (although it must still be balanced overall) and also allows for the ability to isolate and report on inter-unit eliminations via the use of the posting level.

b. Define a method layout (optional)


c. Define a method:

General: Eliminations can be either one sided or two sided. A two-sided elimination specifically compares the balances between two entities. I.E, inter-unit receivables on one units books with inter-unit payables on the others. An alternate method where it is not always possible to specifically capture and compare both sides is to use the concept of a one-side elimination. In such cases the balances as reported by one entity are used as the basis for the overall elimination (i.e. inter-unit sales as reported by the selling unit where the offsetting inter-unit cost of sales is not readily identifiable).

The ability exists to split inter-unit eliminations between the portion which represents a true out of balance and that which is due to exchange rate differences. In such cases the underlying transaction currency amounts are compared. Any difference in transaction currency is then treated as a true out of balance. This is then translated to the group reporting currency and compared to the overall out of balance. The variance between these two is then treated as being due to exchange rate differences. If you want to try and make this split you must flag the field Per Transaction Currency.

The use of limits allows for the ability to set tolerances on variances which can exist between inter-unit balances. Where this balance is exceeded the system will not automatically generate and post the elimination.

Selection: Within this area one defines the FS items, which are to be matched for purposes of performing the elimination. I.E, inter-unit receivable accounts compared to inter-unit payables accounts.

Differences: If the difference exists between the balances this is where we define the accounts to which differences are to be posted when automatic elimination entries are generated. You can use different FS items for debit and credit posting, respectively. If you decide to split the differences between the true out of balance differences and exchange rate differences, you can use different FS items to account for the split as well.

Limits: If maximum differences are to be set on when inter-unit eliminations will be posted automatically the limits are defined within this area. If the limits are exceed then an error will appear on the Inter-Unit elimination log and no automated entry will be generated.



Page 25 of 37

d. Define a task:

The task controls the document type to be used in posting the eliminations as well as the periods to which the particular elimination are applicable. You need to define separate tasks for elimination and reconciliation, respectively.

7. Elimination of IU profit/loss in inventory

You can use this function to eliminate inter-unit profits/loss on the sale of inventory items within a consolidation group, where the inventory is still held at period end within the consolidated group.

a. Settings

Define the product groups, the inventory items, and the automatic posting items for eliminations.

b. Document types

Follow the same procedures as in other consolidation tasks mentioned above.

c. Task

Apart from the same settings as in the other consolidation tasks mentioned above, you need to indicate from where the system should retrieve the relevant data (totals InfoCube versus additional financial data ODS) to execute elimination. You also need to specify the starting year and period of the elimination. Refer to the SEM-BCS 4.0 documentation for further details regarding this function.

8. Consolidation of Investments

This function is used to eliminate the group-internal equity holdings. This task eliminates the investments of the investor units against their interest in the stockholders equity of the investee units, where both units belong to the same consolidation group. In addition it accounts for minority interest holdings both at time of acquisition and in subsequent periods.

The configuration steps involved to set up the consolidation of investments function are similar to the other consolidation functions above.

a. Settings

In these activities you define the following:

Accounting technique being used - purchase method and/or equity method

Goodwill treatment ordinary amortization or impairment; use of global method or local method

Where to locate the values for investment, equity, and equity holding adjustment (if equity method is used).

FS items for the automatic postings and the activities involved in the consolidation of investments.

Refer to the SEM-BCS 4.0 documentation for further details regarding the other activities under Settings

b. Method

Identifies the accounting technique being used and the postings for goodwill.

c. Methods Assignment:

Go to the master data folder in the Workbench > Consolidation Units > Company or Consolidation Profit Center > right mouse click on Company or Consolidation Profit Center > select Accounting Techniques. Here you receive a hierarchical view of the company codes or profit centers. Expand the hierarchy and double-click on any



Page 26 of 37

company or use the details icon to flag the parent company, select the method, and select the accounting technique that are being used.

d. Document type

You assign the posting level, in this case 30, that identifies the type of posting, balance check, etc. Under selected items you identify the clearing account to be used.

e. Task

Here you set up the task that will be run in the monitor. The document type defined in step d is assigned here. You assign a consolidation frequency that identifies how often this task is to be run.

9. Reclassification

You can use this function to reclassify reported data as well as consolidated data. The configuration steps are similar to the other consolidation functions. Reclassifications can serve many purposes where we want to set up automated postings utilizing existing balances within the reported data to generate new postings. Examples of reclassifications include tax equalization (i.e. reversing out local tax provisions and posting a corporate tax provision applying an effective corporate tax rate) and sales shifts (re-allocation of revenues and related expenses for purposes of management reporting as opposed to legal reporting).

a. Document Type

Assign a posting level that identifies the type of posting, balance check, selected items (clearing accts), deferred income taxes, etc.



c. Method

Identifies the source (trigger) FS items and the target FS item to be posted to. A reclassification transfers the trigger value from the source items to the target items using a reversed debit/credit sign. In addition you can also define a condition and/or apply a percentage rate to the trigger. Refer to the SEM-BCS 4.0 documentation for further details regarding various scenarios and customizing of reclassification.

d. Task

Define the task that is to be run in the monitor. You assign the method and document type you created to the task.

10. Balance Carryforward

a. Define the task

b. Define the Items to be carried forward and the debit/credit item to which the items are to be carried forward. Balances are carried forward to period 000.

Note: Balance sheet and statistical balance items are generally always carried forward. Income statement and statistical flow items are only carried forward if explicitly stated. The task will only appear in the monitor in the first period of the new fiscal year. The period is determined based on the consolidation frequency chosen in the base version and fiscal year variant. For example, if consolidation frequency being used is quarterly based on a calendar year, this task will show up in period 003 of the new fiscal year.

Significance of Posting Levels and Document Types



Page 27 of 37

Posting levels classify journal entries in the consolidation system. The following posting levels are provided in the consolidation system:

Posting Level Use

00 Reported financial data (Data as submitted by reporting units).

01 Adjustments to reported financial data (Adjustments to be made to the locally submitted amounts).

10 Standardizing entries (Normally corporate or late adjustments where the entire entry is to be posted to one consolidation unit and should be reflected in all groups in which the unit is included).

20 Two-sided elimination entries (Normally inter-unit eliminations where one side of the entry is posted in one unit and the other side in another unit).

30 Consolidation of investment entries (These entries are specific to a given Consolidation Group).

In the above tasks, you create a document type and assign a posting level. The system records the posting level in the totals record and the journal entries. In BW reporting, you can create your BW reports and include document type and/or posting level as a characteristic for drill down reporting. This way you can run reports that show data only related to a particular set of postings if you need to focus on these for further analysis.

Note: when collecting reported financial data (the unconsolidated or raw data

), the system posts the data under posting level 00, however no document records are created.

Refer to the SEM-BCS (BW based) Business Consolidation Scenario (Rel. 3.5) to view the use of document types and posting levels in reporting.



Page 28 of 37

Consolidation Monitor

Prerequisites

Once you have configured the consolidation functions and their corresponding tasks as outlined above you can then assign those tasks to create your consolidation monitor that will be used to execute the tasks you created.

Procedure

1. Go to Workbench > Process View > Consolidation Monitor.

2. Double-click on Task.

3. At the bottom of the screen, you can create the task hierarchy and the task groups. You can then assign each task to the task group. You can freely structure own task groups. The task hierarchy and the task assignments are version and time dependent.

4. If necessary, you can use the function of Cutoff Task to create a limited monitor suitable for the users in the subsidiaries.

5. Under the process view of the workbench > Consolidation Monitor > select Preceding Task Relationship. Note that the system automatically determines the sequence of tasks within the hierarchy structure (grouping) you defined above. If you need to define preceding tasks, right mouse click on the Preceding Task Relationship and select change. In the hierarchy select the task that is to become a preceding task and drag it over to the task that it is to precede.

Note: For each version within a consolidation area you can have only one task hierarchy and therefore only one sequence of tasks.

6. If you need to add a task to a task group, proceed as follows:

a. First create the particular task you need as described above for the consolidation function you are using.

b. Go to Workbench > Process View > Consolidation Monitor > Task. In the task section in the lower left hand portion of the screen, determine the node where you want the task inserted.

c. Select the task from the nodes not allocated section below and drag it up/place it in the hierarchy node you selected.

If you need to add another node (task group) to the hierarchy proceed as follows:

a. Right mouse click on the hierarchy

b. Select Create. The node type should be task group.

c. Enter the task group and select the green checkmark.

d. Select Save icon to save your configuration.

e. Add the task you want to the task group you just created using the steps outlined above.

Business Warehouse Report to Report Interface Prerequisites

Once you have executed all the consolidation tasks as outlined above you can then create your consolidation financial statements. You can do this by simply copying the content queries and adapt them to your own reporting requirements. The procedures to create BW reports can be found in BW online documentation. What we highlight here are the essential steps to enable the drill down from BCS to the source operational system, which is ECC in our scenario.



Page 29 of 37

Procedure

1. Business Explorer Analyzer Choose Local BW System Queries Info Areas Strategic Enterprise Management Business Consolidations Choose the cube (Consolidation Company / Cons. Profit Center 0BCS_VC11 (This is a Virtual Cube) Choose the content query Changes from Reported Data to consolidation Data (0BCS_VC11_Q011). Right Click and choose change:

Show the inclusion of the Consolidation Group in the Header (basis for deriving which units to include), method, etc.

Show the addition of Company under the Free Characteristics.

Go to the column structure and display how we use posting level (and potentially document type) to split out into separate columns the build up of the values which we use in the query.

Right click on Reported Financial Data and select Edit to show that Reported Financial Data for example is a Restricted Key-figure using posting level for restriction purposes.

2. The Consolidations Cube uses Consolidation Unit for the reporting unit and FS item for the GL Account. In drilling back to PCA you need to be able to convert/equate these to Company Code and GL Account in PCA in order to make the translation because Consolidation Unit and FS item do not exist in PCA.

Go to BW Administration Administrator Workbench Choose Local BW System InfoObjects Search for and Locate 0Account (This is the standard BW InfoObject for GL account in PCA)

Choose the Tab Attributes. Show that 0CS_CHART and 0CS_ITEM have been created as Navigational Attributes of GL Account after performing steps in in the previous section Business Warehouse Data Extraction. By doing this we will be able to subsequently use these attributes in queries to determine the appropriate accounts to select based on FS Item.

GL Account Mapping:

3. Create a query based on PCA InfoCube 0PCA_C01 as follows: Go to Business Explorer Business Explorer Analyzer Local BW System Queries InfoAreas Financials Management and Controlling Profit Center Accounting Cube 0PCA_C01 Create your own query with the following features in the query designer:

a. Use both Consolidation Chart of Accounts and Local Chart of Accounts. b. Beware that even though they do not physically exist in the PCA InfoCube FS item and

Consolidation Unit can be included in the query as they are navigational attributes. They must actually be used to enable the translation. These items will in fact subsequently be used to determine the corresponding Company Code and GL Accounts which will be picked up upon drill down.

c. Go to transaction code RSBBS and make the assignments to support the jump-back and drill-through capabilities.

4. Go to transaction code RSBBS and make the assignments to support the jump-back and drill through capabilities.

First in the Query Sender enter the following value:

0BCS_VC11/0BCS_VC11_Q011

You should assign the PCA query which you create in step 3 above. Select tab Assignment Details. Note that when an attribute is created as navigational there is an object identifier created for the navigational attribute. Here we assign the Company in the Consolidation cube to the corresponding attribute of the Company Code in PCA. This will give rise to the selection of the appropriate Company Code in PCA. Likewise with FS item and Account.



Page 30 of 37

Proceed to InfoCube and enter the sender 0PCA_C01 and show that we are able to assign specific R/3 transactions to the BW query which can then be called remotely. In order to do this we have to define what the source system is that we want to drill down to as well as the specific InfoSource used to populate the cube. Finally we assign the specific R/3 transactions 2KEE (Document totals display) and KE5Z (Document line item display).



Page 31 of 37

Appendix - Read from Data Stream This section is an excerpt of the SEM-BCS 4.0 on-line documentation on the topic of Read from Data Stream

Load from Data Stream Purpose You can use this component to periodically load the following data from a BW InfoProvider (for example, InfoCube or ODS object) into the Consolidation System:

Totals data (posting level 00)

Documents (posting levels 01 and 10)

Additional financial data

You can load data that already exists in an InfoProvider from a local or a non local BW System.

You can load data that resides in another SAP component and exists in BW InfoProviders, for example, from:

A component such as FI-GL, FI-SL, CO-PCA, or CO-PA

EC-CS

SEM-BPS

The structure of the InfoProvider that contains the source data may be different than the data structures of the data basis in Consolidation.

Implementation Considerations The data to be loaded into the Consolidation System needs to be available in an InfoProvider. For example, you need to have uploaded EC-CS data into an InfoProvider by means of a BW upload.

You need to have created a source data basis to be used for the load from data stream method, and you need to have specified that particular source data basis in a data basis.

Integration You can use the load from data stream component either as an alternative or as an enhancement to other methods of data collection.

Within the load from data stream method, you can use the BAdI for data collection (UC_CONVERSION_UPL) for certain mapping activities that are not supported by the load from data stream component (such as mapping one source field to n target fields).

Features You specify the source InfoProvider (and other information) in Customizing for methods. Furthermore, in the mapping section you determine how the characteristics and key figures of the source InfoProvider are portrayed in the Consolidation System. Finally, you determine the source area in the source InfoProvider (with its characteristics and key figures) along with the target area to be posted in the data basis.

When the corresponding task is executed, the system writes the values to the target area of the data basis according to your Customizing settings. The system derives the values for consolidation-specific characteristics (including, for example, the posting level and the default values for subassignments).

The task status is determined in the same way as in the other data collection tasks.

Example In a decentrally managed corporation, the operational charts of accounts of the subsidiaries (FI-GL) differ to a certain degree from the consolidation chart of accounts of corporate headquarters (SEM-BCS).

Each subsidiary runs an upload into a BW InfoProvider.

In the Mapping section of the method Load from Data Stream you can map the characteristics and key figures of a subsidiary to the characteristics and key figures in SEM-BCS.



Page 32 of 37

"Maps" 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 make the Customizing settings for the data collection method Load from Data Stream.

Prerequisites You have made your Customizing settings for the data basis and for the consolidation area that will accommodate the totals data, documents, and/or additional financial data.

The data to be loaded is available in an InfoProvider.

You have created a source data basis and specified it in the data basis.

Process Flow

A. Defining a Task Define a task for data collection, or use an existing task.

A. Defining a Method ...

1. To create a method for Load from Data Stream, go to the process view of the workbench, choose Consolidation Functions Data Collection Load from Data Stream, call up the context menu, and choose Display. Here you can create a method.

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 reflects documents or additional financial data).

Tab Page "Settings" ...

1. Specify the RFC destination for the source data (only if the source InfoProvider resides in another system), and specify the InfoProvider.

Both the RFC destination and the InfoProvider need to have been specified in the source data basis.

2. Specify the update mode.

3. Specify whether the system should consider the debit/credit sign attributes that are defined in Customizing for financial statement items and/or transaction types.

4. Specify the input type (cumulative or periodic).

5. If you want to use a BAdI implementation for data collection, specify the BAdI filter value.

Tab Page "Mapping"

Define how the fields are mapped. See the section Mapping.

Tab Page "Selection"

Define how data is selected. See the section Selection.

Save the method Load from Data Stream.

C. Assigning the Method Assign the method Load from Data Stream to a data collection method. See the section Data Collection Method.



Page 33 of 37

If you select documents as the data stream in the data collection method, you also need to specify the document type.

Assign the data collection method to the data collection task.

Result Execute the method Load from Data Stream by running the corresponding task in the consolidation monitor.

Check the log.

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 specified in the data basis)

Load from data stream

Copy (mapping is optional)

Integration If you have defined mapping rules in a BAdI for data collection (in addition to this set of mapping rules) and you have specified the BAdI filter value in the settings for the method, the task first executes the mapping rules defined in the method and then it executes the mapping rules defined 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 the following subfunctions:

You can set a constant for a target characteristic value.

You can assemble a target characteristic value from the value of one or more source characteristics.

You can split a source characteristic value into sev

How to… Configure the Consolidation Business...

Documents

Transcript of How to… Configure the Consolidation Business...