Legal Consolidation Guide SAP BusinessObjects Planning and Consolidation 7.

5
version for the Microsoft platform version for SAP NetWeaver
Target Audience
ADDONX.BPC_SHARED_CONSOL_CURRCONV

Technical Consultants System Administrators

Release 720
PUBLIC Document version: 1.0 11/23/2010

Copyright
Copyright 2010 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C 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, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer 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. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

2010-23-11

PUBLIC

2/41

Icons in Body Text

Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions
Type Style Example text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Example text EXAMPLE TEXT

Example text

Example text <Example text>

EXAMPLE TEXT

2010-23-11

PUBLIC

3/41

Table of Contents
Application Set Creation .............................................................................................................. 7 Dimension Library Setup ............................................................................................................ 11 Dimension Properties Setup ...................................................................................................... 14 Application Setup ....................................................................................................................... 22 Application Types ....................................................................................................................... 24 Application Parameter Settings .................................................................................................. 30 Business Rule Settings .............................................................................................................. 33 Consolidation Task Execution .................................................................................................... 35 Loading Data .............................................................................................................................. 37 Work Status Settings ................................................................................................................. 38 Journal Templates and Validation Settings ............................................................................... 40 Example ..................................................................................................................................... 41

2010-23-11

PUBLIC

4/41

Legal Consolidation
Business rules provide the mathematical foundation for Planning and Consolidation applications by allowing users to manage both management and legal consolidation reporting. For example, the finance department uses legal consolidation to consolidate numbers and produce consolidated financial statements of a group of legal entities at the end of a financial period. This guide provides the configuration of business rules required for legal consolidation reporting, setup of dimension properties, and the settings required for the various dimension, application, and tasks that are required to successfully perform legal consolidation activities. The guide also describes the following tasks: How to set up currency translations, intercompany eliminations, copyopening tasks, and other business rules using the business rules tables and script logic How to set up the data manager packages required to run the legal consolidation tasks

Features
The following are common activities used to achieve a consolidated financial view: Initializing beginning balances when a new reporting cycle starts Uploading financial data for each entity Validating data Matching intercompany transactions (for example, AR/AP reconciliation) Converting local currency data to the desired group reporting currencies Generating all the consolidation entries for the desired groups of entities such as: o Ultimate ownership calculation o Elimination entries for intercompany revenue, investments and profit in inventory o Adjusting entries o Reclassifications o Minority calculations and other calculations Making the final validation Generating the report

Activities
To enable users to generate consolidated financial statements for a group of legal entities, you must configure the legal application and the legal and statutory consolidation business rules. Setting up your consolidation environment involves the following activities: Create the consolidation (legal) application set and set the necessary parameters See Application Set Creation. Set up master data (dimensions)

2010-23-11

PUBLIC

5/41

See Dimension Library Setup and Dimension Properties Setup. Create the application See Application Setup and Application Types Set the application parameters See Application Parameter Settings. Maintain data manager packages, script logic, and business rules See Business Rule Settings. Update rate data and ownership data See Consolidation Task Execution and Loading Data. Set the work status See Work Status Setting. Set the journal template and validation criteria See Journal Template and Validation Settings.

2010-23-11

PUBLIC

6/41

Application Set Creation

This function describes how to create and set up an application set for legal consolidation.

Features
Application set parameters allow you to customize your application sets within Planning and Consolidation. The following table describes the parameters that are available when setting up the application set (many of these parameters are not specifically required for consolidation, but are generic system requirements for an application set): Parameter ALLOWEXTENSIONS (For the SAP NetWeaver version only) Description Defines the file extensions the system permits users to upload to the application, data manager files, content library files, Web ready files, and library files. When set to ALL, Planning and Consolidation allows all extensions. The default value is ALL. (Required) ALLOW_FILE_SIZE The maximum file size Planning and Consolidation permits users to upload. The default value is 100 MB. (Required for the SAP NetWeaver version) (Optional for the Microsoft version) AVAILABLEFLAG Controls whether the system is offline or not. Yes means the system is online and available for sending data to the database. You can take the system offline by changing the value to No. (Required) AVAILABLEMSG The message that displays to users who try to access an application that is offline (AVAILABLEFLAG is No). For example, the message could be Planning and Consolidation is temporarily unavailable due to scheduled maintenance. Please try again later.. (Required) AVAILABLEURL (For the SAP NetWeaver version only) The name of the Web page to display to users who try to access an application that is offline (AVAILABLEFLAG is No). For example, the URL could be /osoft/NotAvailable.asp. (Required)

2010-23-11

PUBLIC

7/41

Parameter DEFAULT_EXTENSIONS

Description The file extensions that Planning and Consolidation allows users to upload. By default, the following are allowed: .XLS, .XLT, .DOC, .DOT, .PPT, .POT, .XML, .MHT, .MHTML, .HTM, .HTML, .XLSX, .XLSM, .XLSB, .ZIP, .PDF, .PPTX, .PPTM, .POTX, .POTM, .DOCX, .DOCM, .DOTX, .DOTM, .CDM, .TDM, .PNG, .GIF, .JPG, .CSS, .MRC. See ALLOWEXTENSIONS above.

LANDINGPAGEITEM

To customize the Getting Started page in Planning and Consolidation Interface for the Web, contact your system administrator. Used by an application set to control the level of the ABAP log, which you view by the transaction SLG1. LOGLEVEL has the following possible values: 0 None: Log is off. 1 Error: Log only the error, abort, and exit messages. 2 Warn: Log the warning, error, abort, and exit messages. 3 Info: Log the info, status, error, abort, and exit messages. (Optional)

LOGLEVEL (For the SAP NetWeaver version only)

MAXLRCOLUMNS

The maximum number of columns to display in a live report in Planning and Consolidation Interface for the Web. The value includes header and data columns. For example, if you specify a value of 5, one heading column and four data columns are displayed.

MAXLRROWS

The maximum number of rows to display in a live report in Planning and Consolidation Interface for the Web. The value includes header and data rows. For example, if you specify a value of 5, one heading row and four data rows are displayed.

2010-23-11

PUBLIC

8/41

Parameter SMTPAUTH (For the Microsoft version only)

Description The authentication method of the SMTP server. 0 Anonymous 1 Basic 2 NTLM This setting does not change the method on the SMTP server, but must match the type of authentication enabled on it. Failure to set this appropriately can result in errors from the e-mail server. (Required)

SMTPPASSWORD (For the Microsoft version only) SMTPPORT (For the Microsoft version only) SMTPSERVER (For the Microsoft version only) SMTPUSER (For the Microsoft version only) TEMPLATEVERSION

The password for the user name defined as the SMTPUSER. (Required) Port number for your SMTP e-mail server. Default is port 25, which is the default SMTP server port number. (Required) The name or TCP/IP address of the SMTP e-mail server the system uses to send e-mail. (Required) The user name, from which e-mail from the system originates. (Required) Current version number of the dynamic templates in your application set. Whenever you add to or change your input schedule or report dynamic templates, you should increment this version number so that the system automatically downloads the new templates when they log on to this application set. You can also reset the template version from the Administration Console. (Required)

SYSTEM MESSAGE STATUS

This is Planning and Consolidation 7.0 internal application set parameter. the default value is 1. This is a Planning and Consolidation 7.0 internal application set parameter. the default value is blank. This is a Planning and Consolidation 7.0 internal application set parameter. the default value is 1.

2010-23-11

PUBLIC

9/41

Note In the back end of the SAP NetWeaver version, all the above parameters are stored in the ABAP DDIC table UJA_USER_DEF.

Activities
Create an application set. If you already have an existing application set (for example, for planning or reporting), you can use this application set to host your legal consolidation. Using the application set for planning or reporting as a basis to build consolidations allows you to share the relevant dimensions such as account with your consolidation environment. Set application set parameters (see the above table for details).

2010-23-11

PUBLIC

10/41

Dimension Library Setup

This function allows you to set up dimensions used in legal consolidation reporting.

Features
For the consolidation application, the dimensions listed in the tables below are mandatory requirements. Therefore, we recommend that you confirm that all the dimensions are available in the dimension library of your consolidation application set created from ApShell, as described in Application Set Creation.

Note You can choose any names for the dimensions. However, it is mandatory that the dimension types match the ones described below for the corresponding applications. The main legal consolidation application requires the following dimensions: Dimension Description Account Category Members of this dimension are, for example, Revenue, or Salaries. Contains the types of data you are going to track, such as Actual, Budget, and Forecast. You can also set up categories to store versions, such as BudgetV1, and BudgetV2. Used in the business rules of a reporting consolidation application to segregate input data. Breaks down account activity or flow into subunits. Contains the business units that are used to drive the business process. Depending on your application design, the Entity type can be an operating unit, a cost center, a geographic entity, and so on. Intco Time Currency Group Contains the intercompany codes for the entities. Contains the time periods for which you store data. The currency-type dimension is required if you report on local currency and translated values. The group-type dimension is used for storing the group component of legal consolidation. The group represents the relationship of entities for a given consolidation result. Note If the requirement is to have consolidated results in multiple group currencies within a single entity structure, you can continue to use the currency type dimension for this purpose or create a separate dimension for the group. The group provides multiple currencies for a group member.

Data Source Subtable Entity

2010-23-11

PUBLIC

11/41

The rate application containing exchange rates requires the following dimensions: Dimension Description Account Category Members of this dimension are used to detail the different types of rate (for example, Average, or End-of-period). Contains the types of data you are going to track, such as Actual, Budget, and Forecast. You can also set up categories to store versions, such as BudgetV1, and BudgetV2. This is used to store multiple tables of rates, if desired, otherwise the R_Entity dimension may just be limited to one dummy member, typically named Global. Contains the time periods for which you store data. This dimension is used to store each applicable local currency. Note The Time and Category dimensions must be shared by all the applications involved in consolidation. The ownership application storing the ownership details requires the following dimensions: Dimension Description Account Category Members of this dimension are for example Method (consolidation method),POWN (ownership percentage), and PCON (control percentage). Contains the types of data you are going to track, such as Actual, Budget, and Forecast. You can also set up categories to store versions, such as BudgetV1, and BudgetV2. Contains the business units that are used to drive the business process. Depending on your application design, the Entity type can be an operating unit, a cost center, a geographic entity, and so on. Contains the intercompany codes for the entities. Contains the time periods for which you store data. Here, the group-type dimension is used for storing the group component of legal consolidation. The group represents the relationship of entities for a given consolidation result. Note If the requirement is to have consolidated results in multiple group currencies within a single entity structure, users can continue to use the currency type dimension for this purpose or create a separate dimension for the group. The group provides multiple currencies for a group member. In this case, it is necessary to use the group type dimension in the ownership application, which is available as of Planning and Consolidation 7.5 for the NetWeaver platform.

Entity Time Currency

Entity

Intco Time Group

2010-23-11

PUBLIC

12/41

The following table gives a summary of which dimension is required in which application: Dimension Name C_Acct IC_Acct O_Acct R_Acct Flow C_Category Entity R_Entity Intco Time RptCurrency InputCurrency C_DataSrc Group A A A A S C E E I T R R D G X X X X X X X X X X X X X X X X X X X Type X Main Ownership Rate

Note The IC_Acct dimension is used when a separate application is created for Intercompany Matching. For more information, see the application help on Intercompany Matching.

Activities
In the action pane of the dimension library, click Add a new dimension to create a new dimension.

2010-23-11

PUBLIC

13/41

Dimension Properties Setup

When you create a new dimension, all the required properties are included automatically based on the dimension type. However, to ensure the correct operation of consolidation and related processes (such as currency conversion, simulation, and automatic adjustment), additional dimension properties are needed for the appropriate filter, flagging, and calculation of the target data. You should ensure that these properties are maintained with the expected values for the consolidation process according to your business requirements.

Features
Account Dimensions The Account dimension defines the chart of accounts for the application, and how these accounts are calculated and aggregated. Any dimension that is assigned the type A is considered an Account dimension. Each application can have only one account-type dimension. The following table details the account dimension properties: Property Name ACCTYPE Length Description of Appropriate Property Value 3 This property can have the following values: INC for income EXP for expense AST for asset LEQ for liabilities and equity

Note signed Data = signed Data when ACCTYPE isINC or LEQ. End of the note. DIMLIST 20 Used to group the accounts for use in business rules. For example, using the DIMLIST property value can help reduce the size of the FXTRANS table. Used by the currency conversion business rules. This property determines the business rules to be applied when translating any given account from local currency to reporting or group currency. A value is optional. The following special values of RATETYPE are possible: blank All accounts are translated with a factor of 1 NOTRANS All accounts are not translated

RATETYPE 10

2010-23-11

PUBLIC

14/41

Property Name ELIMACC

Length Description of Appropriate Property Value 20 Used in the elimination process and represents the difference account, to which the accounts to be eliminated are posted.

Category Dimensions All applications require a category-type dimension. The properties required in this dimension as described below are for two business rules currency translation and copyopening balances. For simulation purposes, or to analyze the variances from one set of data to another, it is often necessary to mix-and-match different rates and values of different data categories from different time periods. For example, you might want to compare Actual with Budget values when the system translates both at the Actual rates, or this year's Actuals with last year's Actuals, both being translated using last year rates. This can be done by either creating some additional simulation Category (such as Actual_at_Budget_rate or similar) or adding an extra dimension to the main cube, where all the simulated cases can be stored. There is no need to copy the input values to all applications for all the desired simulations. A few definitions, stored in some specialized properties of the Category (or the FX simulation) dimension informs the translation procedure where to read the input values and where to write the translated results. To minimize the impact of the different simulations on the size of the database, it is also possible to tell the system to store only the difference between the default results and the simulated scenarios. When using the simulation categories in the main application, simulated translations are stored in additional members of the Category dimension. These categories have non blank values for one or more of the following properties:

Note Any dimension that is assigned the type C is considered to be a Category dimension. Property Name Length Description of Appropriate Property Value The category for the source (LC) data. If blank, it is the current category. The category from which the rates are read. The year from which the rates are read. The value can be absolute (such as 2008, or 2009) or a relative value (-1, -2, +1, +2). If blank it is the same as the source. FX_SOURCE_CATEGORY 20 RATE_CATEGORY RATE_YEAR 20 4

2010-23-11

PUBLIC

15/41

Property Name RATE_PERIOD

Length Description of Appropriate Property Value 10 The period from which the rates are read. The value can be absolute (such as DEC, or FEB) or a relative value (-1, -2, +1, +2). If blank, it is the same as the source.

FX_DIFFERENCE_ONLY

If Y, only the difference between the default values and the simulated values is stored.

The business rules for copying opening balances can be controlled by assigning some special properties to the category dimensions. If used, these properties affect the execution and are defined in the following table: Property Name Length Description of Appropriate Property Value Blank The category for the opening balances is the same. Non blank The ID of the category from where to read the opening balances. Blank Read the opening balances from the year before the current year. Non blank Contains the year from which to read the opening balances. It can be an absolute or a relative amount. Blank Read the opening balances from the last period of the year. Non blank Contains the period from which to read the opening balances. It can be an absolute or a relative amount.

CATEGORY_FOR_OPEN 20

OPENING_YEAR

OPENING_PERIOD

10

Data Source Dimension The data source dimension type is an optional application dimension. However, it is a best practice standard dimension. You can customize the name of the dimension, as appropriate. You should also consider the following rules: The type is mandatory for the elimination business rules. The Data Source dimension is required for elimination and consolidation business rules. For example, automatic elimination only works if you have a base level value, and it is a data source type A. The type is optional for the currency business rules. It is not used in the business rules for currency conversion. The type is mandatory for the consolidation business rules. It is required for the results destination. For example, you can define, by source data source, a specific destination data source, in which to post the resultant postings. Any dimension that is assigned the type D is considered to be a Data Source dimension.

2010-23-11

PUBLIC

16/41

The following table details the data source dimension properties: Property Name IS_CONVERTED Length Description of Appropriate Property Value 1 Y The data source is converted. N - The data source is not converted. G Converts the data source from a currency group to a group currency. That is, the members are copied from the reporting currency of the group being translated into the currency member corresponding to the specified group. This only applies if the translation is run for a group and not for a reporting currency. IS_CONSOL 1 Blank It is a management application. Y - It is consolidation. I input M manual journal entry A automatic generated journal L level This is used in consolidation by level to move prior level eliminations into a data source with property DATASRC_LEVEL of Y in the group dimension. COPYOPENING 1 Y (or blank) This member is copied. N This member is not copied. Blank The data source is the same as the source member. Non blank Contains the ID of the desired destination data source for the copy.

DATASRC_TYPE

OPENING_DATASRC 20

Entity Dimension The Entitytype dimension defines the organizational structure of the business units for your application and how the units aggregate. Any dimension that is assigned the type E is an Entity dimension. Each application can have only one entity-type dimension. The following table details the entity dimension properties: Property Name CURRENCY Length Description of appropriate property value 20 Local currency used by the entity. This currency must be defined in the InputCurrency dimension.

2010-23-11

PUBLIC

17/41

Property Name FX_TYPE

Length Description of appropriate property value 20 Special rate for entity used by the currency conversion business rules. Entering a value is optional.

INTCO

20

Used to link intercompany counterpart ID for elimination. It is also known as Trading Partner. This ID must be defined in the IntCo dimension.

OWNER

60

Used for work status.

Currency Dimension The currency-type dimension is required if you report on local currency and translated values. The group-type dimension represents the relationship of entities for a given consolidation result. This group is consolidated in a single currency, so there is no need to have another dimension. As of Planning and Consolidation 7.5, you can continue to use the currency-type dimension for this purpose, or you can split it into a group-type dimension (type G) and use a pure currency-type dimension (type R) to allow reporting in multiple group currencies. The required properties for a separate currency dimension are listed in the following table: Property Name CURRENCY_TYPE Length Description of Appropriate Property Value 1 L local currency R reporting currency T transaction currency G group Used for the currency conversion. REPORTING 10 Used for currency members that are to be used in reporting. This property can only take the values Y, or blank. Group Dimension The group-type dimension is used for storing the group component of legal consolidation. The group-type dimension represents the relationship of entities for a given consolidation result. This group is consolidated in a single currency, so there is no need to have another dimension. As of Planning and Consolidation 7.5, you can continue to use the currency-type dimension for this purpose, or you can split it into a group-type dimension (type G) and use a pure currency-type dimension (type R) to allow reporting in multiple group currencies.

2010-23-11

PUBLIC

18/41

The required properties for a separate group dimension are listed in the following table: Property Name GROUP_CURRENCY Length Description of Appropriate Property Value 20 Can be any valid reporting currency. Used for currency conversion. This property can only be used on Currency members with the property CURRENCY_TYPE of G and, in this case, it must contain a valid ID from the Currency dimension with the property CURRENCY_TYPE value of R. PARENT_GROUP 20 Must be a valid ID from the Groups dimension. If you want to do the consolidation by level, you must indicate here the higher level from the group. If you want to use this property to define the hierarchy, enter the same code as the ID for your top group. If this property is blank, the dynamic hierarchy from the ownership application is used. ENTITY 20 Blank or a valid entity ID. This is used to define the link between the Group and the Entity or to indicate the Entity where the aggregation should be stored. If this property is filled with valid entity ID, and the property STORE_ENTITY is set to Y, the results of the currency conversion for the current Group are also copied into this Entity. STORE_GROUP_CURR 1 Used for currency conversion. Y (or blank) By default the results of the conversion into a Group currency are written in both the Group member and in the Currency member of the currency dimension. N - If only the Group member is to be stored, set this property to N. STORE_ENTITY 1 Y - If you want to store in the ID entered in the Entity property. Blank If you do not want to store in the ID entered in the Entity property.

2010-23-11

PUBLIC

19/41

Property Name CURRENCY_TYPE

Length Description of Appropriate Property Value 1 L local currency R reporting currency T transaction currency G group Used for the currency conversion.

GROUP_CURRENCY

20

Can be a valid reporting currency. Used for currency conversion. Used for currency conversion. Y - When you run the conversion for a group currency, the procedure also stores the results in the corresponding GROUP_CURRENCY. N - The GROUP_CURRENCY is not stored in the database.

STORE_GROUP_CURR 1

STORE_ENTITY

Y Stores the result in the Entity defined by the ID entered in the Entity property. Blank The result is not stored. This property controls the way the converted values must be saved when performing a multilevel conversion of groups. This property can only take the values Y, E, or N (blank).

STAGE_ONLY

FIRST_CONS_DATE

10

Blank t is a management application. YYYYMMM - Indicates the month and year of the consolidation.

Flow Dimension The flow-type dimension is optional but its use is highly recommended. This dimension allows you to track changes within the account activities, such as opening balance, additions, subtractions, and currency translation adjustments. If you do not require this level of detail, you should leave the business rule tables blank for the subtable field. Flow is similar to the movement type in SAP ERP. If Flow is included in the application, it can be used in the following ways: The currency translation procedure can detail the changes in the balance sheet generated by fluctuations in the exchange rates The consolidation procedure can detail the eliminations applied to the movements of the balance sheet accounts Any dimension that is assigned the type S is considered a Flow dimension.

2010-23-11

PUBLIC

20/41

If you choose to use a flow-type dimension, the following properties are required: Property Name FLOW_TYPE Length Description of Appropriate Property Value 12 Opening opening Translope change diff on opening Allocinc allocation Merger merger Income net income from the period Change variation. Transfer transfer Transflow translation change on flow Varscp variation in scope (generic) Varscpmeth variation in scope method Varscpperc variation in scope percentage Varscpnew variation in scope; new company Varscpleav variation in scope sold company Closing closing None no flow Blank all other flows Used to group the flows for several business rules. Y The flow is an input type. N The flow is not an input type.

DIMLIST IS_INPUT

20 1

Activities
To maintain dimension members and their property values, select a dimension in the dimension library and choose Maintain dimension property in the action pane. Modify the properties, as desired, using the above tables for guidance. Recommendation The dimension member values are case sensitive with Planning and Consolidation 7.0 version for SAP NetWeaver. This means that upper and lower case names are recognized as two different members. For the rate application and the ownership cube, we strongly recommend not to set two members with only different cases. For example, in the R_ACCT dimension, AVG, and Avg could be two different members to store the average exchange rate. We do not recommend this as both script logic and the consolidation program could be confused as well as possible incorrect user recognition issues. For consistency reasons, we recommend that you only use upper case for the dimension IDs.

2010-23-11

PUBLIC

21/41

Application Setup
This function creates the application for legal consolidation.

Features
The consolidation engine leverages the following applications to retrieve the information necessary to perform its calculations: The legal or main application This consolidation type application is the application within which the respective consolidation entries for items, such as currency conversion or intercompany eliminations, are written. The rate application The currency conversion process uses a rate application, to look up the appropriate exchange rates for each relevant currency. The ownership application The consolidation process uses an ownership application to store the definitions of each consolidation parameter. In particular, such definitions may include: o o o o o The list of companies being consolidated in each group The consolidation method used in each case The consolidation percentage for each case The ownership percentage (how much each is owned by the group) The control percentage (how much each is controlled by the group)

You can choose any names for the main, rate, and ownership applications. Within the same application set, multiple main applications may exist, each one pointing to its own rate and ownership applications. Multiple main applications can also share the same rate or ownership applications, if appropriate. The rate application, associated with a given application, is defined upon the creation of a new main application. The ownership application associated with a given application is identified using an application parameter as follows: OWNERSHIP_APP = {app name} If this parameter does not exist, the consolidation procedure searches for an application named OWNERSHIP.

2010-23-11

PUBLIC

22/41

Each one of the above applications must contain some required dimensions, while some other dimensions are optional. For more information, see Dimension Properties Setup. The required and optional dimensions are based on the standards used in the business rules. Other dimensions can coexist in a reporting application but do not impact the business rule function. All applications must contain the four required Entity, Category, Time, and Account dimensions (although they can be named as desired). The Category and Time dimensions can be the same across the main, rate, and ownership applications. Alternatively, they must contain the appropriate matching members. The Entity dimension of the main application can be the same as that used in the ownership application or it must contain the appropriate matching members if different. The Group dimension used must be same in the ownership application and the main application. It contains some of the common member requirements between dimensions for the legal consolidation environment setup. In most cases, we recommend that you use the same dimensions across applications, as it is easier to maintain.

Note The rate application is delivered with ApShell. Most dimension properties required for the consolidation setup are delivered with the dimensions. However, we recommend that you verify this before proceeding further.

2010-23-11

PUBLIC

23/41

Application Types
When working with an application, its application type tells the system which properties to associate with the application.

Features
Reporting and Non-reporting Applications In Planning and Consolidation, an application is either Reporting or Non-reporting. Non-reporting applications are designed to support reporting applications or to simply hold data (for example, price or rate information). Reporting Applications Within the same application set, multiple reporting applications may exist, each one pointing to its own rate and ownership applications. Multiple reporting applications can also share the same rate or ownership applications, if appropriate. Currency translation can run on any type of reporting application. Currency conversion applies to both financial and legal consolidation applications to which a corresponding rate application has been referenced and the reporting application contains a currency (type R) dimension. The rate or ownership application associated with a given reporting application is defined when a new consolidation-type application is created.

Note You can report on non-reporting application data, but you cannot assign work status codes to the data. In addition, you cannot define business rules for these application types. All applications require at least the four main dimension-types: Entity, Account, Time, and Category. These are the types of reporting applications in Planning and Consolidation: Financial A financial reporting application performs management consolidation functions, such as currency conversions and intercompany eliminations. This application must reference a rate-type application. Consolidation A consolidation reporting application performs legal consolidations. This is similar to a financial application, but with legal consolidation rules instead of management consolidation rules. It can be a main or legal application and it contains all financial data. All consolidation postings, such as eliminations and minority interest calculations, are posted in this application.

2010-23-11

PUBLIC

24/41

This application must reference an ownership-type application and a rate-type application. The ownership application manages the organization structure and ownership percentages. The rate-type supporting application contains all currency exchange rates for the different rate types, such as average and spot rate. Generic A generic reporting application has no special requirements (other than to include a minimum of the four required dimensions). A generic application has no out-of-the-box intelligence, so logic must be created using script logic. Non-Reporting Applications Non-reporting applications can only be associated with financial- and consolidation-type applications. The types of non-reporting applications follow: Rate This application stores exchange rates that support currency conversions for reporting applications. The application must include a currency-type dimension to store the exchange rates by currency. Ownership An ownership application stores information such as the consolidation methods, ownership percentages, and group roll-up information used for legal consolidation. Rate Application A rate application is a supporting application for financial and consolidation reporting applications. It is used to store exchange rates that support currency conversion in consolidation applications. Apshell comes with a rate application, so you can leverage this by just modifying the category dimension from Category to C_Category. The Time dimension must be identical to the dimension used by the applications using the rate application to store their foreign currency exchange rates and must have the same category member IDs. This application must include a currency dimension detailing the exchange rates by each input currency. The currency dimension in a rate application does not need to have the REPORTING property. The currency conversion process makes use of a rate application, where the appropriate exchange rates are searched for each relevant currency. This application can be named as desired.

Note The master data (dimensions) can be shared by any application within an application set.

2010-23-11

PUBLIC

25/41

The rate application requires the following dimensions: R_Acct (account dimension for the rate application) This details the different types of rate (Average, End-of-period, and so on). R_Acct is specific to and used only by the rate application. R_Entity (entity dimension for the rate application) This stores multiple tables of rates, if required. Alternatively, the R_Entity dimension can be limited to one dummy member, typically named Global. For example, if there is an entity, C1000, for which a special exchange rate needs to be applied, it is defined here and the special rates are applied. R_Entity is specific to and used only by the rate application. Currency This dimension stores each relevant local currency. Time and Category These dimensions can be shared by all of the applications involved in consolidation. Ownership Application Any consolidation type application must refer to a rate and an ownership application. Apshell is delivered only with planning and rate applications. Therefore, the ownership application needs to be created before it is possible to create the consolidation application. Refer to the application creation wizard to understand the steps of the creation process. The business rule process uses an ownership-type application when calculating the ultimate ownership or during the minority interest calculation. This application must be associated with a consolidation type application. The ownership application contains the values of each consolidation parameter. In particular, such definitions may include: The list of companies being consolidated in each group The consolidation method for each company The consolidation percentage for each company The ownership percentage (how much each company is owned by the group) The control percentage (how much each company is controlled by the group) The ownership application can be named as desired. If the name of the application is other then ownership, you must identify the application by name in an application parameter as follows: ORG_OwnerShipCube = {app name}

2010-23-11

PUBLIC

26/41

If this parameter does not exist, the consolidation procedure searches for an application named OWNERSHIP. The ownership application defines ownership details such as the consolidation scope, method, percentage of the share owned by the holding company or groups. For the ownership application, the only dimension that is specific for the ownership application is the ownership account (O_Acct) that the consolidation engine uses to get the information listed above. To pass the information, several required members need to be defined. These include the following: Method, defines consolidation method Pown, defines the percentage of ownership Pcon, defines the percentage of consolidation Pctrl, defines the percentage of control Consolidation (main) Application Any consolidation-type application must refer to a rate and an ownership application.

Activities
Associating Business Rules with Applications Consolidation business rules allow the automated processing of data to render a consolidated set of financial statements. This is commonly considered to be eliminations of investments in subsidiaries, adjustments of minority interest, reclassifications, and any other postings depending on the nature of the consolidation methodologies required. This functionality is enabled through a combination of ABAP (for the SAP NetWeaver version of the system) and business rule tables.

Note Only when the consolidation-type applications are created and the business rule automatic adjustments are created, the predelivered business rule library tables are activated and shown in the Administration Console. This includes Method Library, Elimination Rule, and Rule formula tables, as only automatic adjustment (such as minority posting, investment adjustment) use these elimination rules and formulas for the calculation of actual postings. Associate the desired rate and ownership applications with the consolidation application and select all the consolidation business rules that need to be implemented. You can select from the following list of business rules: Currency conversion Conversion of local currency data to the desired reporting currencies. Calculations To calculate and store amounts, which are required for purposes of account transformation.

2010-23-11

PUBLIC

27/41

Intercompany bookings Matching intercompany transactions. US Eliminations Specifically designed to address the posting of intercompany eliminations in simpler scenarios where a full legal consolidation application is not required. Opening Balance Initialization of beginning balances when a new fiscal cycle starts. Validation Validation of input data. Intercompany Eliminations Generation of all the consolidation entries for the desired groups of entities (eliminations, adjustments, reclassifications, minority calculations, and so on). Selecting Dimensions Select only the desired dimensions required for legal consolidation. Set dimensions to be included in the consolidation application and also set the secured dimension to control the security through Planning and Consolidation member access profiles. Typically, the Entity and Category dimensions are set to be secured dimension for member access control. The Currency dimension stores the local currency, and the reporting currency. The Group dimension stores the consolidation groups. The main application must contain a Currency dimension to store the translated amounts. The consolidation entries, as generated by the consolidation process, are also stored by Group in the same Group dimension. The reason for this overlapping of dimensions in the previous version of Planning and Consolidation is that, in the great majority of cases, the Currency dimension, and the Group dimension do not intersect. In other words, the Entity details are either in local currency LC or in a reporting currency say USD or are consolidated into a given group say G1 in which case specifying the group is enough to identify its currency. As a result of this, defining the intersections Entity/LC, Entity/USD, and Entity/G1, is sufficient to store all required information.

Note The use of separate dimension for currency and group is required mainly when there is a requirement for multiple group currency conversion.

2010-23-11

PUBLIC

28/41

Selecting Additional Dimensions Any additional dimension is optional in the main application, as far as the currency translation is concerned. For consolidation purposes, however, there are some other requirements. These are described below: The application may have an Intco dimension, but it is not required for the consolidation procedure to work, unless an elimination rule makes an explicit reference to this dimension. The application may have a Flow dimension. This dimension is optional, but, if it exists, it can be used by the following procedures: o The currency translation procedure, details the changes in the balance sheet generated by fluctuations in the exchange rates o The consolidation procedure details the eliminations applied to the movements of the balance sheet accounts A Data Source dimension may exist in the main application, but it is not required by the currency translation. If it exists, however, the currency translation can recognize which members of such dimension should be translated and which ones should be just copied as they are into the destination currency. On the other hand, this dimension is required for the consolidation procedure to work. You can add additional (user defined) dimensions to the main application (such as product, market, division, and so on), as desired. The consolidation engine can recognize their existence and take them into account in the process, and even apply some custom behavior to their members.

2010-23-11

PUBLIC

29/41

Application Parameter Settings

Application parameters provide a collection point for properties that affect how applications are used. The legal consolidation application requires some settings, and some of the more important parameters determine how to use organizational information from the ownership application.

Features
When you create a consolidation type application, you should choose the settings of the application parameters in accordance with the intended purpose of the application. The following table details business rule activation during the creation of a consolidation type application: Key ID APPROVALORG (For the SAP NetWeaver version only) Description If you want to use the work status feature, you must use this field to identify the hierarchy level (H1, H2, H3, ..., Hn) for which you want to track the work status of deliverables. You can define only one hierarchy for each application within an application set. For other organizations, No Status displays when viewing these members in the work status screen. If this field is blank, work status tracking is disabled. When set to ON, various Planning and Consolidation modules write detailed runtime statistics to the tables UJ0_STAT_HDR and UJ0_STAT_DTL. You can use this information to monitor system performance. Valid values are ON and OFF. Allows the use of the calculation business rule tables. The default value is 1. Allows the use of the currency conversion business rule tables. The default value is 1. Allows the use of the intercompany booking business rule tables. The default value is 1.

BPC_STATISTICS (For the SAP NetWeaver version only) CALCULATION FXTRANS INTCOBOOKINGS

JRN_REOPEN_PROPERTY A custom journal module assumes that the property UB is in the Account dimension to filter the journals upon reopen. The default is Group. If Group, there is no need to modify the Account dimension. OPENINGBALANCE ORG_ACCOUNTLIST Enables the business rule table for carrying forward the balance from a preceding period. The default value is 1. Member IDs of the ownership account dimension that store methods, percentage consolidation, and percentage ownership. These appear in the dynamic hierarchy editor. The default value is Method,Pown,Pcon. (Required)

2010-23-11

PUBLIC

30/41

Key ID ORG_ACCOUNTOWN

Description Member ID of the ownership account that specifies the position of a consolidation entity within the group. The default value is PGROUP. (Required)

ORG_INTCO

The third party member in the Intercompany dimension to which all ownership calculations are posted. The default value is I_NONE, which should also be a member ID in the Intco dimension in the ownership application if using dynamic hierarchies. (Required)

ORG_OWNERSHIPCUBE (SAP NetWeaver version only) ORG_PARENTPROPERTY

Name of the linked ownership application. The default value is OWNERSHIP.

The property name in the Groups dimension that defines the hierarchy used in the dynamic hierarchy editor. The Group property contains the legal roll-up members. This parameter is used with dynamic hierarchy statutory applications when defining fixed hierarchies. The value must match the value in the PARENTPROPERTY property value of entities in the statutory applications supporting ownership application. The default value is parent_group. (Required)

OWNERSHIP_APP (SAP NetWeaver version only)

The consolidation logic requires the ownership application to be listed here. If the name of the ownership application is not specified, the consolidation procedure searches for an application named ownership. Allows the use of the business rule tables for US eliminations. The default value is 1. Allows the use of the validation business rule tables. The default value is 1. Controls whether the work status is routinely validated. This parameter controls whether data is input in year-to-date format. Valid options are YES, which means YTD format; or NO, which means periodic format. (This parameter is optional)

USELIM VALIDATIONS WORKSTATUSVALIDATE YTDINPUT

2010-23-11

PUBLIC

31/41

The following table lists the relevant application parameters and the recommended values that should be set through Web Administration. (refer to the Administration Application Help for instructions on how to set these values): Key ID APPROVALORG FXTRANS INTERCOMPANY JRN_BALANCE JRN_POST_OVERWRITE OPENINGBALANCE ORG_ACCOUNTLIST ORG_ACCOUNTOWN ORG_INTCO ORG_OWNERSHIPCUBE ORG_PARENTPROPERTY OWNERSHIP_APP VALIDATIONS WORKSTATUSVALIDATE YTDINPUT YTDINPUT Setting One of the most important application parameters in Web administration is YTDINPUT. This defines whether the application type is periodic or YTD (year to date). This parameter plays important role since it controls how the data is stored in the application. Most source systems store balances on a periodic basis (for example, daily, weekly, monthly, or fiscal periods). With this method, periodic data must be accumulated for year-to-date reporting (except for balance sheet accounts, which takes the value from the last period). However, in some business cases, calculations should occur on a year-to-date basis. If YTD is required, applications can store the data on a YTD basis. When data is entered into YTD, its periodic values used for reporting purposes are calculated as the difference between the current period and the last period (balance sheet accounts would simply take the value from the last period). By default, applications are periodic. You can change the YTDINPUT parameter to a value of YES to turn it into a YTD storage type. H1 1 1 1 Y 1 METHOD, PCON, POWN PGROUP I_NONE OWNERSHIP PARENT_GROUP OWNERSHIP 1 YES NO Value

Activities
Refer to the Administration Application Help for information about setting application parameters.

2010-23-11

PUBLIC

32/41

Business Rule Settings

Planning and Consolidation delivers predefined functions designed to calculate and post amounts required supporting common accounting activities such as: Currency translation Matching and elimination of interunit balances.

Features
A table-based logic gives you the flexibility to customize these predefined functions to meet specific requirements. For each predefined data package and script logic, there are one or more Business Rule tables, in which you can configure rules. The consolidation engine uses these table-driven ABAP programs (in the SAP NetWeaver version) to perform all the appropriate calculations on a user-selectable region of data, and write the calculated results into the database. Table-based logic (business rules) provides the flexibility for a business user to customize the delivered logical functions, to meet specific business needs, without having to understand either scripting or programming. SAP NetWeaver Version Packages The consolidation process is supported by SAP NetWeaver Business Warehouse process chains and script files. The following table lists the consolidation process tasks and the corresponding business rules: Consolidation Task Balance carry forward Validation Currency conversion Intercompany reconciliation Intercompany balance booking Legal consolidation (elimination and adjustment) Process Chain Name /CPMB/OPENING_BA LANCES /CPMB/VALIDATIONS /CPMB/FX_RESTATM ENT /CPMB/ICDATA /CPMB/ICBOOKING /CPMB/LEGAL_CONS OLIDATION Script Logic Files Name Business Rule Table Name

COPY_OPENING.LGF Carry-forward rules VALIDATION.LGF FXTRANS.LGF ICDATA.LGF ICBOOKING.LGF Validation rules and validation details Currency conversion rules No rules needed Intercompany booking

CONSOLIDATION.LGF Automatic adjustments and automatic adjustment details

2010-23-11

PUBLIC

33/41

Consolidation Task Account calculation (cash flow function) US widely used Intercompany elimination

Process Chain Name /CPMB/RUNCALCAC COUNT

Script Logic Files Name CALCACCOUNT.LGF

Business Rule Table Name Account transformation

/CPMB/IC_ELIMINATI ON

ICELIM.LGF

US elimination

To run these programs, use the Data Manager packages through SAP NetWeaver Business Warehouse Process Chains to invoke the programs directly from the script logic file and pass the appropriate parameters to the data package. For each process, the predefined Data Manager packages with their associated logic scripts and rule tables are executed, performing the consolidation task according to the business rule customization. Any specific business requirement must be configured in the corresponding business rule tables. Microsoft Version Packages For the Microsoft version of the system, the Data Manager packages are supported by SQL Server Integration Services (SSIS). The following table includes all of the consolidation tasks that Planning and Consolidation supports with each script file, and the corresponding business rules: Consolidation Task Balance Carry Forward Validation Currency Conversion Intercompany Reconciliation Intercompany Balance Booking Legal Consolidation (Elimination and Adjustment) Account Calculation (Cash Flow functioned) US widely used Intercompany Elimination Script Logic File Name VALIDATION.LGF FXTRANS.LGF ICDATA.LGF ICBOOKING.LGF Business Rule Table Name

COPY_OPENING.LGF Carry-forward rules Validation rules and Validation details Currency Conversion Rules No rules needed Intercompany booking

CONSOLIDATION.LGF Automatic Adjustments and Automatic Adjustment Details CALCACCOUNT.LGF ICELIM.LGF Account Transformation US Elimination

You can select and add a predelivered, consolidation task-related, or SSIS package to invoke the programs directly from the script logic file and pass the appropriate parameters to the data package. You can also modify a Data Manager package dynamic script to pass specific parameters, and to reassign the script logic file for a table-driven program.

2010-23-11

PUBLIC

34/41

Consolidation Task Execution

In Planning and Consolidation, version for SAP NetWeaver, Data Manager packages are implemented as process chains. In Planning and Consolidation, version for the Microsoft platform, Data Manager packages are implemented as SQL Server Integration Services (SSIS). Both versions allow common data manipulation activities. The packages that are delivered with Planning and Consolidation are designed to be dynamic so that you do not need to modify the packages for them to work with your applications and dimensions. Data Manager packages allow you to manage data within Planning and Consolidation applications and dimensions. The Financial packages that can be used for the consolidation process, apart from the Standard and Administrative packages, are described in the following table: Financial Package Default Formulas Logical Allocation Calculate Ownership FX Restatement IC Elimination ICBooking ICData Legal Consolidation Run CalcAccount Clear the Journal Tables Description This package executes default formulas stored in your default.xls file. The package runs the allocation logic. The package runs the CalcOwnership logic. Technical Name DEFAULT_FORMULAS ALLOCATION OWNERSHIPCALC

This package is used for currency translation. The FX_RESTATMENT package runs the FXTrans logic. IC_ELIMINATION This package is used to perform intercompany eliminations. The package runs the ICElim logic. ICBOOKING The package runs the ICBooking logic. The package runs the ICData logic. The package runs the LegalConsolidation logic. ICDATA LEGAL_CONSOLIDATION OPENING_BALANCES RUNCALCACCOUNT CLEAR_JOURNALS EXPORT_JOURNAL RESTORE_JOURNALS

Opening Balances The package runs the OpeningBalances logic. The package runs the CalcAccount logic. Clears journal tables and creates an output file.

Export the Journal Exports journal tables to an output file Tables Restore Journal Tables Allows you to load journal tables from a file

Procedure
1. Add the Data Manager packages for consolidation application. You add data manager packages by choosing Interface for Excel eData Organize Data Package List Add a Data Package . Select and add an SAP NetWeaver BW process chain or SSIS package, as appropriate.

2010-23-11

PUBLIC

35/41

You can also modify a data manager package dynamic script to pass specific parameters, and to reassign the script logic file for a table-driven program. You modify a data manager package by choosing Interface for Excel eData Organize Data Package List . Select the package and right-click Modify Package and click View Package in the Modify Package screen. You can edit the script in data manager package Dynamic Script Editor by clicking Advance. 2. Create Script Logic files (LGF). Script Logic allows you to define formulas that perform calculations on Planning and Consolidation members and data. You can create a script logic file for the consolidation engine by choosing Admin Console and expanding Consolidation Application. In Script Logic Editor, you can create a script logic file.

Note o All the examples of logic files required for a consolidation are stored in the File Service directory \Root\Webfolder\ApShell\Systemlibrary\LogicLibrary\. These examples are intended to help you understand the syntax. You can copy and reuse these in an application. The following only applies to the NetWeaver version: The transaction for the File Service UI is UJFS The logic file name must be identical to the string defined in the Data Manager package

3. Maintain the business rule table. The procedure to maintain the business rules is as follows: 1. 2. 3. 4. Log on to the Planning and Consolidation Administration Console. Expand Consolidation Application. Go to Business Rule Editor. Select the rule table to create the content of the rules according business requirements.

2010-23-11

PUBLIC

36/41

Loading Data
Procedure
1. Load the exchange rate to the rate application. The rate application stores the exchange rates for currency conversion. There are several ways to upload the data to the rate application, such as using the data manager package import, or using dynamic templates to send data from the input schedule. For more information, see Currency Conversion. If you are using EvDRE, you can set the Rate Account dimension and the Input Currency dimension in rows and the Time dimension in a column. Save the EvDRE as the input schedule to send data to the rate application. Such an input schedule could also be saved as a template in the library for sharing and reuse. 2. Input ownership data and calculate ultimate ownership. Since the consolidation scope (such as ownership percentage, group and unit hierarchy) is time dependent, you can user the dynamic hierarchy editor in Planning and Consolidation for SAP NetWeaver, to update the ownership application with ownership details. 3. Load the financial data. After loading the financial data, use a Planning and Consolidation report to validate that the numbers loaded reconcile with the numbers in the source system. In the Example, the load date is 2008.MAR for the Japanese Entity and the reporting currency is USD. So, it is possible to show the source data loaded through the report.

2010-23-11

PUBLIC

37/41

Work Status Settings

The Work Status feature is a mechanism that allows submitted data to be tracked, approved, and locked using customizable work-state definitions that meet the business needs. The work status serves the need to secure the data in the application in addition to access controls for users.

Features
Work States Setting (application set dependent) The system is capable of providing sufficient control on changing the data to database. Work status such as Unlocked, Submitted, and Locked can be set on a data set, which could be based on dimensions of the data. The term locking is generically used to describe data that is not available for change either on a temporary or permanent basis. During the specific business process, you can use the work status to apply a label to a specific current view intersection for the purpose of locking data so it can be reviewed, or approved, for example. This is actually a common requirement, for example, during month-end close, the business process requires that a specific set of data is locked down so that accurate month-end reports can be created. After a data submission, the owner can set the status of the data to Submitted. This locks the data intersection from subsequent submissions. On the other hand, the locking strategy of the data can be customized to satisfy specific business needs. For example, between bottom up and top down data processing model, you can have the flexibility to work with the system on how the locking logic applies. To customize the work status setting, log on to the Planning and Consolidation Admin Console and choose Work States Setting. Add states according to business needs. Set a different interface for the approval privilege level for each work state just created. Set an appropriate privilege for changing work states. Work Status Setting (application dependent) At a specific application level, a user can configure work status according to specific requirements. At application level, the system provides an interface to define the following settings: Approval organization Work status can be configured by dimensions. You can decide which dimension contains the approval organization. The approval organization is the hierarchy, for which you can track the status of the deliverables. Rules top down or bottom up The default rule for managing work status is bottom up. That is, the status of a parent cannot be higher than the status of its children. You can set work status to top-down. For bottom-up behavior, the maximum state a parent can be set to is the lowest state of its immediate children. The minimum state a child can be set to is the state of its immediate parent. For example, if the parent state is Submitted, the child state must be at least Submitted.

2010-23-11

PUBLIC

38/41

Within the interface of application work status setting, all the dimensions included in the application are also available to be used to track work status setting. If a user decides not to use a certain dimension to track work status, that dimension must contain a member that is included in the validation process of work status to make sure the data is validated before being locked. To configure work status settings, logon to the Planning and Consolidation Administration Console and choose Work Status Setting. Set the lock dimension and owner dimension.

Note The owner dimension must contain the owner property dimension, whose hierarchy controls the work states change hierarchy. If there is a requirement to define a dimension with an owner property, this dimension must also contain a hierarchy to enable the pushing of the work status. The dimension with the owner property drives a parent-child relationship for setting status. In addition to the customizing functionality, the work status combines the above states with specific functionality based on an owner property defined in a specified dimension. A user must define either top down or bottom up rules to apply to an application (currently an application setting).

2010-23-11

PUBLIC

39/41

Journal Templates and Validation Settings

Journals allow you to make adjustments to data in the database, typically as part of the monthend or quarter-end process. During the review and analysis step, journals allow you to capture an audit trail of the changes and adjustments made to the database. The purpose of validation is to prevent incorrect records being saved to the application.

Features
Journal Templates The primary requirement for journals is to track changes to data after the initial source data is input into the application. For example, the general ledger information is loaded into the application through the Data Manager. You can adjust this data and also track and report on the changes by, for example, amount, date, and user. To create the journal template logon to the Planning and Consolidation Administration Console, choose Journals and create a journal template. Once you have created the template, the dimensions in an application cannot be deleted from the application nor can the data. Validation Settings Validations are designed to prevent incorrect records being saved to the application. In Planning and Consolidation for the SAP NetWeaver platform, it is not possible (or supported) to get data into an application without going through the Write-Back module. Therefore, validations are implemented in write-back, to ensure that invalid records cannot get into the application from any source, including journals, Data Manager packages, and manual data input. For example, a specified intercompany account with an empty Trading Partner dimension is blocked from being written into the application. To customize the validation in the SAP NetWeaver version, go to the SAP ABAP system and enter transaction code UJ_VALIDATION to configure the validation framework and customize the validation rules according to business requirement. For more information, see the Breakdown Validation section of the application help. Caution If you have already created a journal template, creating a new template that changes the structure of the journal entries deletes the old template and all journal entries associated with that template. This removes your audit trail, even though changes made to the application data through posted journal entries are maintained. If you re-create the journal template, but do not change the structure of the template keeping all header and detail dimensions the same, you have the option to keep the existing journal entries.

2010-23-11

PUBLIC

40/41

Example
After loading general ledger data into an application using Data Manager, you can review the data and use journal entries to make adjustments if there is any correction or reclassification needed. When journal entries are saved and posted, you can track and report on all adjustments to data. For example, it is possible to run reports on the changes by amount, date, user, and several other properties to review and analyze. Validations, on the other hand, are designed to prevent incorrect records from being saved to the application. You control what is deemed an incorrect record. An example of an incorrect record is one where you have specified an intercompany account, but left the Trading Partner dimension empty.

Note In Planning and Consolidation for the Microsoft platform, validations are implemented, but only journal data is checked for validation. Therefore, it is easy to end up with invalid records in your application, as all other modules are not validated. In Planning and Consolidation for the SAP NetWeaver platform, it is not possible (or supported) to get data into an application without going through the Write-Back module. Therefore, validations are implemented in Write-Back, to ensure that invalid records cannot get into the application from any source including journals, Data Manager packages, and manual data input.

2010-23-11

PUBLIC

41/41