BPC Preso2 Consolidation Framework

SAP BPC 10 NW MEGA ELITE Enablement
Consolidation Framework
Legal Consolidation Requirements
In SAP BPC, a consolidation environment requires at least 3 models:

Legal Consolidation
Main model containing all financial data
Also contains non-financial data like headcounts, …
Ownership
Used to manage the organization structure (scopes and sub-scopes)
Rate
Contains all currency exchange rates
Intercompany (optional)
Used for Intercompany Matching process (balance level)
Note : Models names are not mandatory
© 2011 SAP AG. All rights reserved. 2

Application Types
To create a consolidation environment, add the following minimum models for

Consolidation, Rate, and Ownership. Select model options to expose the
delivered consolidation relevant functions:

Business Rules and Script Logic Content
To activate business rules :

Go to Administration / Rules / Business Rules
Select the appropriate model
Click on Add/Remove Rule Types
Check the appropriate Rule Types

Business Rules and Script Logic Content
As specific model options are activated, business rules and script logic files are made
available in each of the applications. A list of all delivered functionality is as follows:
Consolidation Task Process Chain Name Script Logic File Name Business Rule Name
/CPMB/OPENING_BA
Balance Carry Forward COPY_OPENING.LGF Carry-Forward rules
LANCES
Currency Conversion /CPMB/FX_RESTATM ENT FXTRANS.LGF Currency Conversion rules
Intercompany Reconciliation /CPMB/ICDATA ICDATA.LGF No rules needed
Intercompany Balance
/CPMB/ICBOOKING ICBOOKING.LGF Intercompany booking rules
Booking
/CPMB/LEGAL_CONS Eliminations and

Legal Consolidation CONSOLIDATION.LGF
OLIDATION Adjustments rules
Account Calculation (Cash /CPMB/RUNCALCAC Account Transformation

CALCACCOUNT.LGF
Flow functioned) COUNT rules
US widely used
/CPMB/IC_ELIMINAT ION ICELIM.LGF US Eliminations rules
Intercompany Elimination
Note : Script logic files names are not mandatory, you can adjust the relevant packages in
the Data Manager module
Environment Parameters
The following parameters must be set after creating an environment. Most of

them are not required for a consolidation, but are a generic system
requirement for any new environment. In the Administration console, select
Manage All Environments :
Set Template Version => defines

the current version number of the
dynamic templates in your
application set
Change Status = controls

whether the system is offline or
not ; you can also type in the
message displayed to users who
try to access an model that is
offline

Legal Consolidation Model
Purpose of the LEGAL CONSOLIDATION Model:

defines journal template
stores the initial (pre-consolidated) trial balance records
launches balance carry forward processes
ensures data consistency with controls
launches currency conversion and consolidation processes
reporting for pre/post consolidation financial reports

Legal Consolidation Model - Dimensions
A minimum of 9 dimensions are required for the Legal Consolidation model:
1.C_Account (A) – Chart of accounts

2.Category (C) - Typical categories would be Budget, Actual, Forecast
3.AuditTrail (D) - Tracks the source of data (input, journal adjustments, eliminations…)
4.Flow (S) - identifies balance sheet movements (opening, additions, decreases, transfers
… and ending balances)
5.RptCurrency (R) - Identifies Transaction Currency and Local Currency.
6.Scope(G) - Consolidation groups / scopes
7.Entity (E)
8.Interco (I) - Provides partner information for intercompany eliminations
9.Time (T)
Note : Dimensions names are not mandatory

Rates Model - Dimensions
The RATES model contains currency exchange rates. A minimum of 5 dimensions are
required for a Rate-Type model :
1.R_Account (A): This details the different types of rate (Average, End-of-Period, Historical,
etc.)
2.R_Entity(E): This stores multiple tables of rates, if required; otherwise the R_Entity dimension
may just be limited to a unique member, typically named GLOBAL
3.InputCurrency (R): This stores each applicable local currency (CAN, USD, EUR, etc)
4.Category (C): – same as Legal Consolidation model
5.Time (T) : – same as Legal Consolidation model

Ownership Model
Purpose of the OWNERSHIP model:

Stores a time dependent representation of the organization structure of the parent
company in transactional data records by directly interfacing with the Dynamic Hierarchy
Editor functionality.
Stores the consolidation method (METHOD) to use as well as the percentage of
consolidation (PCON) , percentage of control (PCTRL) for each of the entities.
Stores the percentage of ownership i.e. POWN.

Ownership Model - Dimensions
The OWNERSHIP model stores ownership details. A minimum of 6 dimensions are

required:
1.O_Account (A) – provides information on ownership type such as PGROUP, POWN, PCON,
and PCTRL
2.Category (C) – same as Legal Consolidation model
3.Entity (E) – same as Legal Consolidation model
4.Time (T) – same as Legal Consolidation model
5.Interco (I) – same as Legal Consolidation model
6.Scope (G) – same as Legal Consolidation model

Ownership - Model General Settings
Settings Description
This parameter is used with dynamic hierarchy for legal applications when defining
consolidation hierarchies. The value set here must match the name of property in
GROUPS dimension in the legal consolidation application to store the ownership
Parent/Child property used for
data.
hierarchy of groups
Value should be PARENT_GROUP.
This parameter should be a member ID in the INTERCO dimension in the ownership

Non-interco Member in model if you are using dynamic hierarchies.
Ownership For example: I_NONE or ThirdParty

Dimensions - Summary
The following dimensions are used in the relevant models:
Name Type Consolidation ICMatching Ownership Rate
C_Account A X
IC_Acct A X
O_Account A X
R_Account A X
Flow S X (X)
Category C X X X X
Entity E X X X
R_Entity E X
Interco I X X X
Time T X X X X
Scope G X X X
InputCurrency R X
RptCurrency R X
AuditTrail D X X

Dimension Types
Type Identifier ID example Description
Account A P_Acct in Planning model
C_Account in Consolidation model
O_Acct in Ownership model Contains your chart of accounts and required indicators. This dimension can
R_Acct in Rates model be shared between consolidation and planning models.
Contains the types of data your are going to collect and report on, such as
Actual, Budget, Forecast… You can set up categories to store several
Category C Category versions, such as Budget_V1, Budget_V2…
Contains the business units that are used to drive your business processes.
Depending on your models design, entities can be operational units, cost
Entity E Entity in all models, except centers, geographic or legal entities.
R_Entity in Rates model
Contains the time period / frequency on which you store and analyze the
Time T Time in all models data.
Contains the currencies in which you consolidate and analyze your data. A
specific member "LC" will be used to enter all data in local currency for each
Currency R RptCurrency in all models, except entity.
Contains the currencies in which your company does business (i.e. all local
Input_Currency in Rates model currencies and reporting currencies).
Scope in Consolidation and Contains all the relevant groups for which you want to run consolidations.
Groups G Ownership models This dimension can also be used in Planning models if needed.
Contains the list of intercompany partners (must be corresponding to
InterCo in Consolidation and existing entities). This dimension can also be used in Planning models if
Intercompany I Ownership models needed.
User-Defined U N/A Referred to in the system as U1, U2, U3…
DataSource D P_AuditTrail in Planning model
Used to track data origins and segregate input from adjustments from
AuditTrail in Consolidation model eliminations…
SubTable S rights reserved.

© 2011 SAP AG. All Flow in Consolidation model Breaks down data by flow/movement (typically on Balance Sheet accounts).
14
Dimension – C_Account
Main Properties
Property Name Description

Account type. Can be INC for Income, EXP for Expense, AST for Asset or LEQ for Liability and Equity
ACCTYPE accounts.
A system-generated property. It indicates whether the account is calculated by means of a formula or
is at a parent level. You can view the property values in the Member Selector in the EPM Add-In for
CALC Office.
EVDESCRIPTION A user-defined description for the member.
Stores the hierarchy names associated with the member. We recommend that you use hierarchies
HIR rather than formulas to define subaccounts.
A system-generated property. It denotes the hierarchical level of the member. The property values can
HLEVEL be viewed in the Member Lookup in BPC for Excel.
Used for currency conversion (see corresponding business rules). Value is optional and has to be
RATETYPE avalid account in the R_Account dimension
Scaling options are Y or N. Used by EPM Add-In for Office. Value is optional, but if a value is not
SCALING defined, scaling is unavailable for the associated member ID.
Used to group accounts by type of behavior. The member can be used in the Eliminations and
TYPELIM Adjustments business rules.
Used to identify the counterpart account on which the elimination is performed (plug account for
ELIMACC instance for intercompany balance eliminations). It must be an existing account in the dimension.
A user-defined identifier for denoting whether the account is calculated by means of a formula or is at
STORED_CALC a parent level. Valid entries are Y or N (or blank).
© 2011 SAP AG. All rights reserved. = relevant to consolidation activities 15

Dimension – Flow
Main Properties
A system-generated property. It indicates whether the account is calculated by means of

a formula or is at a parent level. You can view the property values in the Member Selector
CALC in the EPM Add-In for Office.
FLOW_TYPE Defines the type of flow of the dimension- Opening, Closing.. (Consolidation)
HIR Stores the hierarchy names associated with the member
A system-generated property. It denotes the hierarchical level of the member. You can
HLEVEL view the property values in the Member Selector in the EPM Add-In for Office.
Scaling options are Y or N. Used by EPM Add-In for Office. Value is optional, but if a
SCALING value is not defined, scaling is unavailable for the associated member ID.
A user-defined identifier for denoting whether the account is calculated by means of a

STORED_CALC formula or is at a parent level. Valid entries are Y or N (or blank).
DIMLIST Used to group the Flows for several Business Rules
= relevant to consolidation activities

Dimension – Entity
A system-generated property. It indicates whether the account is calculated by means of a

formula or is at a parent level. You can view the property values in the Member Selector in
CALC the EPM Add-In for Office.
CURRENCY The currency in which local data are entered (Currency Conversion)
HIR Stores the hierarchy names associated with the member.
OWNER Defines users and managers involved in the workflow.
CTRL_LEVEL Used to identify the level of control for each entity (can be empty, 1, 2, 3 or 4) (Controls)

ELIM Used to identify elimination entities used in US Eliminations (Consolidation)

Link to intercompany counterpart ID ; it must be a valid member in the Interco dimension
INTCO (Consolidation)
FX_TYPE Special currency conversion Rule (Currency Conversion)

Dimension – Interco

A 20 character field that can either be left blank or contain a valid member name of the
Entity dimension associated to the current application. The ENTITY property is validated
ENTITY against the Entity dimension, and blank fields are allowed (Consolidation).

Scaling options are Y or N. Used EPM Add-In for Office. Value is optional, but if a value is
SCALING not defined, scaling is unavailable for the associated member ID.


Dimension – AuditTrail

HIR Stores the hierarchy names associated with the member.
A system-generated property. It denotes the hierarchical level of the member. You can view
HLEVEL the property values in the Member Selector in the EPM Add-In for Office.
Scaling options are Y or N. Used by EPM Add-In for Office. Value is optional, but if a value
SCALING is not defined, scaling is unavailable for the associated member ID.
Y or N. All members of the DATASRC dimension having the property IS_CONVERTED not
IS_CONVERTED set to ‘Y’ will be skipped (Currency Conversion)
IS_CONSOLIDATED Consolidate that Datasrc (Y) (Consolidation)
COPYOPENING Flag to select whether Datasrc is included in Copy Opening (Y) (Copy Opening)
OPENINGDATASRC Datasrc to be used during carry-forward process (Y) (Copy Opening)
DATASRC_TYPE Input (I), Manual (M), or Automatic (A) (Consolidation)
DATASRC_STAGE Special setting for multi-level consolidations (Consolidation)

Dimension – Category

formula or is at a parent level. You can view the property values in the Member Selector in the
CALC EPM Add-In for Office.
A system-generated property. It denotes the hierarchical level of the member. You can view the
HLEVEL property values in the Member Selector in the EPM Add-In for Office.
A user-defined identifier for denoting whether the account is calculated by means of a formula or
STORED_CALC is at a parent level. Valid entries are Y or N (or blank).
YEAR Used to assign a YEAR to the category, to be used in reporting.
OPENING_PERIOD Period to use for Copy Opening (Copy Opening)
OPENING_YEAR Year to use for Copy Opening (Copy Opening)
CATEGORY_FOR_OPE Category to use for Copy Opening (Copy Opening)
RATE_CATEGORY The category from which the rates are read(Currency Conversion)
The year from which the rates are read. The value can be absolute (2010) or a relative value (-1, -2,
RATE_YEAR +1, + 2). If blank it is the same as the source (Currency Conversion)
The period from which the rates are read. The value can be absolute (DEC, FEB) or a relative
RATE_PERIOD value (-1, -2, +1, + 2). If blank it is the same as the source (Currency Conversion)
FX_DIFFERENCE_ONLY Only the difference is stored (Y) (Currency Conversion)
The category for the source (LC) data. If blank it is the current category (Currency Conversion
FX_SOURCE_CATEGORY and Consolidation)
© 2011 SAP AG. All rights reserved.

= relevant to consolidation activities 20
Dimension – Category

Contains the name of the category where ownership values will be retrieved
OWN_CATEGORY (Consolidation)
Contains the value of the year to take into account when retrieving Ownership data. The
value can be a relative value : +1 or -1 for example of a specific value : 2010 for example.
The value is optional. In case no value is entered the system will use the Year of the
OWN_YEAR consolidation process (Consolidation)
Contains the value of the year to take into account when retrieving Ownership data. The
value can be a relative value : +1 or -1 for example of a specific value : DEC for example.
The value is optional. In case no value is entered the system will use the Period of the
OWN_PERIOD consolidation process (Consolidation)

Dimension – Groups / Consolidation Scopes
A system-generated property. It indicates whether the account is calculated by means of a formula or is at a

CALC parent level. You can view the property values in the Member Selector in the EPM Add-In for Office.
A 20 character field that can either be left blank or contain a valid member name of the Entity dimension
associated to the current application. The ENTITY property is validated against the Entity dimension, and
ENTITY blank fields are allowed.
A system-generated property. It denotes the hierarchical level of the member. You can view the property
HLEVEL values in the Member Selector in the EPM Add-In for Office.
CONSO_TYPE Consolidation type allows defining specific sets of rules for specific groups
G for Group and N for Non Group (only one member should have the „N“ value, it will be used for data entry
CURRENCY_TYPE only)
DATASRC_LEVEL Datasrc ID to use for sub-consolidation eliminations (Consolidation)
Entity ID to store consolidated results (Consolidation) (audit & compliance purposes, easier creation of
ENTITY reports)
STORE_ENTITY Y to store consolidated results on the specified entity – see Entity property (Consolidation)
FIRST_CONS_DATE Date of first consolidation (Consolidation)
GROUP_CURRENCY Must be a valid reporting currency ; can be a list of several currencies (Consolidation)
PARENT_GROUP ID of parent group (Consolidation)
STAGE_ONLY Storage option for staged consolidations (Consolidation)
STORE_GROUP_CURR Value = Y to store on the Group Currency when running Currency Conversion (Consolidation)
© 2011 SAP AG. All rights reserved.

= relevant to consolidation activities 22
Dimension – Reporting Currency
A system-generated property. It indicates whether the account is calculated by means of a formula

or is at a parent level. You can view the property values in the Member Selector in the EPM Add-In
CALC for Office.
A user-defined identifier for denoting whether the account is calculated by means of a formula or is
STORED_CALC at a parent level. Valid entries are Y or N (or blank).
G for Group and N for Non Group (only one member should have the „N“ value, it will be used for
CURRENCY_TYPE data entry only)
REPORTING Y or Blank. To specify against which currencies the conversion will be executed.

Dimension – Time

formula or is at a parent level. You can view the property values in the Member Selector in the
CALC EPM Add-In for Office.
Time can be a year, quarter, month, week, or day. The LEVEL property is important in defining
your time periods. You must have the correct level for each member. You must follow the
LEVEL chronological format throughout the Time dimension. The correct format
is:YEAR/QUARTER/MONTH/WEEK/DAY
PERIOD The PERIOD property allows you to filter, sort, and report based on the period.
A user-defined identifier for denoting whether the account is calculated by means of a formula
STORED_CALC or is at a parent level. Valid entries are Y or N (or blank).
The YEAR property allows you to filter, sort, and report based on the year. You should place the
YEAR properties in chronological order in the file, in order for the offset function in EPM Add-In
YEAR for Officel to give offsets correctly.
MONTHNUM 1, 2, 3, …
PERIOD Jan, Feb, Mar, …

Ownership Manager
Purpose :
Provides a web based interface to allow the business user to set up time dependent relationships
between various subsidiaries and organizational units.
Each hierarchy is keyed to a specific combination of Category and Time dimension member
values.
Provides a convenient table entry to define the consolidation METHOD, PCTRL, POWN and
PCON of each individual unit.
The dynamic hierarchy is stored in the Ownership application as transactional records.

FAQ – Consolidation Framework
How to setup the consolidation framework in order to keep the investment details
like no of shares, investment details also in the BPC system ?
Add the relevant accounts in the O_account dimension : number of issued shares,
number of owned shares, with and without voting rights
Create the corresponding data entry schedule in order to enable users to enter the
number of shares owned (using the interco dimension) – data can also be loaded
using a flat file, BW cube…
Set up the calculation of ownership percentage based on data entered on owned and
issued shares
What is the difference between PCON, PCTRL and POWN ?

Percent control represents the percentage of an entity based on voting shares that
other entities own, directly or indirectly. It is used to determine the consolidation
method
Percent ownership (also known as the interest percetange) represents the
percentage of an entity’s nonvoting shares that other entities own, directly or indirectly
Percent consolidation is the percentage of an entity’s values that consolidate to its
parent
Direct percent ownership is the percentage of regular nonvoting shares of stock
owned by each entity

What is the difference between PCON, PCTRL and POWN ?
• Control percentages : M controls F at 80% ; M controls G at 60%,

through F&G, M controls H at 30%.
• Ownership percentages : M owns F at 80%, M owns G at 48% (80% *
60%), M owns H at 14% (80% * 60% * 30%)
What is the difference between elimination entity and consolidation entity? Are
they the same? Elimination entity will only store eliminations generated by US elimination
business rules while the consolidation entity is the entity storing the consolidated results for
each group/sub-group
What happens when we use different entities in place consolidation entity? It allows
to secure only the entity dimension instead of securing both entity and scope dimensions in
case sub-consolidors need to access sub-consolidated data.

What is the use of the new properties for Entity – Control_Level and
Ctrl_currency_not_LC ?
Thanks to the Control Level property, the administrator can associate a level of
required control for each entity. So when the controls are executed, only the controls
below or equal to the level associated to the entity will be run.
The Ctrl_currency_not_LC enables the controls execution for those entities were
data entry are performed directly on a currency, and not on the LC member in the
currency dimension
Can we execute the controls at the group level ? No, controls can only be launched on
base entities.

Rules: Controls
Summary
You should now be able to:

Identify and create the required models in order to set up a consolidation
environment
Identify and create the required dimensions in each consolidation model
Identify and fill the required properties for each dimension
Identify useful scripts, business rules and data manager packages
Understand the basics of the Ownership Manager

Thank You!
Contact information:
Caroline Stephens
Solution Management – EPM Solutions
Caroline.stephens@sap.com
© 2011 SAP AG. All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
without the express permission of SAP AG. The information contained herein may be Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
changed without prior notice. mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
registered trademarks of Sybase, Inc. Sybase is an SAP company.
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, All other product and service names mentioned are the trademarks of their respective
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, companies. Data contained in this document serves informational purposes only. National
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, product specifications may vary.
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, The information in this document is proprietary to SAP. No part of this document may be
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, reproduced, copied, or transmitted in any form or for any purpose without the express prior
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, written permission of SAP AG.
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
This document is a preliminary version and not subject to your license agreement or any
trademarks of IBM Corporation.
other agreement with SAP. This document contains only intended strategies, developments,
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. and functionalities of the SAP® product and is not intended to be binding upon SAP to any
particular course of business, product strategy, and/or development. Please note that this
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
document is subject to change and may be changed by SAP at any time without notice.
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries. SAP assumes no responsibility for errors or omissions in this document. SAP does not
Oracle is a registered trademark of Oracle Corporation. warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind,
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. either express or implied, including but not limited to the implied warranties of
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are merchantability, fitness for a particular purpose, or non-infringement.
trademarks or registered trademarks of Citrix Systems, Inc. SAP shall have no liability for damages of any kind including without limitation direct,
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World special, indirect, or consequential damages that may result from the use of these materials.
Wide Web Consortium, Massachusetts Institute of Technology. This limitation shall not apply in cases of intent or gross negligence.
Java is a registered trademark of Sun Microsystems, Inc. The statutory liability for personal injury and defective products is not affected. SAP has no
control over the information that you may access through the use of hot links contained in
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for these materials and does not endorse your use of third-party Web pages nor provide any
technology invented and implemented by Netscape. warranty whatsoever relating to third-party Web pages.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, 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 other
countries.

BPC Preso2 Consolidation Framework

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BPC Preso2 Consolidation Framework

Caricato da

Copyright:

Formati disponibili

SAP BPC 10 NW MEGA ELITE Enablement

In SAP BPC, a consolidation environment requires at least 3 models:

Note : Models names are not mandatory

© 2011 SAP AG. All rights reserved. 2

To create a consolidation environment, add the following minimum models for

© 2011 SAP AG. All rights reserved. 3

To activate business rules :

© 2011 SAP AG. All rights reserved. 4

Currency Conversion /CPMB/FX_RESTATM ENT FXTRANS.LGF Currency Conversion rules

Intercompany Reconciliation /CPMB/ICDATA ICDATA.LGF No rules needed

/CPMB/LEGAL_CONS Eliminations and

Account Calculation (Cash /CPMB/RUNCALCAC Account Transformation

The following parameters must be set after creating an environment. Most of

Set Template Version => defines

Change Status = controls

© 2011 SAP AG. All rights reserved. 6

Purpose of the LEGAL CONSOLIDATION Model:

© 2011 SAP AG. All rights reserved. 7

A minimum of 9 dimensions are required for the Legal Consolidation model:

1.C_Account (A) – Chart of accounts

Note : Dimensions names are not mandatory

© 2011 SAP AG. All rights reserved. 8

© 2011 SAP AG. All rights reserved. 9

Purpose of the OWNERSHIP model:

© 2011 SAP AG. All rights reserved. 10

The OWNERSHIP model stores ownership details. A minimum of 6 dimensions are

2.Category (C) – same as Legal Consolidation model

3.Entity (E) – same as Legal Consolidation model

4.Time (T) – same as Legal Consolidation model

5.Interco (I) – same as Legal Consolidation model

6.Scope (G) – same as Legal Consolidation model

Note : Dimensions names are not mandatory

© 2011 SAP AG. All rights reserved. 11

This parameter should be a member ID in the INTERCO dimension in the ownership

© 2011 SAP AG. All rights reserved. 12

The following dimensions are used in the relevant models:

Name Type Consolidation ICMatching Ownership Rate

© 2011 SAP AG. All rights reserved. 13

SubTable S rights reserved.

Property Name Description

© 2011 SAP AG. All rights reserved. = relevant to consolidation activities 15

Property Name Description

A system-generated property. It indicates whether the account is calculated by means of

EVDESCRIPTION A user-defined description for the member.

HIR Stores the hierarchy names associated with the member

A user-defined identifier for denoting whether the account is calculated by means of a

DIMLIST Used to group the Flows for several Business Rules

= relevant to consolidation activities

Property Name Description

A system-generated property. It indicates whether the account is calculated by means of a

HIR Stores the hierarchy names associated with the member.

OWNER Defines users and managers involved in the workflow.

A user-defined identifier for denoting whether the account is calculated by means of a

ELIM Used to identify elimination entities used in US Eliminations (Consolidation)

FX_TYPE Special currency conversion Rule (Currency Conversion)

= relevant to consolidation activities

Property Name Description

A system-generated property. It indicates whether the account is calculated by means of a

EVDESCRIPTION A user-defined description for the member.

A user-defined identifier for denoting whether the account is calculated by means of a

= relevant to consolidation activities

Property Name Description

A system-generated property. It indicates whether the account is calculated by means of a

= relevant to consolidation activities