Bpc440 en Col95

BPC440 SAP Business Objects Planning and Consolidation - Consolidation SAP CPM - Business Planning Consolidation

Date Training Center Instructors Education Website

Participant Handbook Course Version: 95 Course Duration: 5 Day(s) Material Number: 50098731

An SAP course - use it to learn, reference it for work

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.

Trademarks •

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

•

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

•

ORACLE® is a registered trademark of ORACLE Corporation.

•

INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

•

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

•

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

•

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

•

JAVA® is a registered trademark of Sun Microsystems, Inc.

•

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

•

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

g201057101553

About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.

2010

Example text

Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© 2010 SAP AG. All rights reserved.

iii

About This Handbook

BPC440

Icons in Body Text The following icons are used in this handbook. Icon

Meaning For more information, tips, or background

Note or further explanation of previous point Exception or caution Procedures

Indicates that the item is displayed in the instructor's presentation.

iv


2010

Contents Course Overview ......................................................... vii Course Goals ...........................................................vii Course Objectives .....................................................vii

Unit 1: Introduction to SAP BusinessObjects Planning and Consolidation ............................................................... 1 SAP BusinessObjects Planning and Consolidation Overview ....2 SAP NetWeaver BW Overview...................................... 20

Unit 2: SAP BusinessObjects Planning and Consolidation Framework................................................................. 39 Appsets and Applications ............................................ 40 Dimensions, Properties, and Loading Master Data .............. 86 Consolidation Logic..................................................125

Unit 3: Data Collection and Preparation ........................... 161 Transaction Data Collection .......................................163 Journal Entries and Balance Carry Forward .....................207 Account Transformation, Allocation, and Validation .............241

Unit 4: Currency Translation ......................................... 293 Currency Translation ................................................294

Unit 5: Consolidation of Investments .............................. 325 Consolidation of Investment Concepts............................326 Consolidation of Investments Architecture .......................333

Unit 6: Inter Company Eliminations ................................ 397 Inter Company Matching ............................................398 Inter Unit Elimination and US Elimination.........................420

Unit 7: COI - Equity and Proportional Methods .................. 455 COI Equity and Proportional Methods ............................456

Unit 8: Business Process Flow for Consolidation .............. 481 Business Process Flows for Consolidation .......................482

2010


v

Contents

BPC440

Unit 9: Optional: Reporting........................................... 535 Reporting for SAP BusinessObjects Planning and Consolidation .....................................................536

Unit 10: Appendix....................................................... 591 COI Example .........................................................592 Currency Translation Example .....................................596 More on Delivered Content .........................................600 AppSet and Application Parameters ..............................608 Technical Content on Connectivity, Performance, Transports, Traces..............................................................618 List of How To Papers ...............................................632 Sample Logic for the Microsoft Platform Version ................635

Glossary................................................................... 645 Index ....................................................................... 649

vi


2010

Course Overview SAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver is a robust planning and consolidation application that can meet all of your budgeting, planning, consolidation, and reporting requirements. It supports the full array of top-down and bottom-up financial and operational planning needs as well as consolidation processes necessary to ensure the smoothest, most timely financial close possible — all through a single system. As a result, you gain the confidence to meet increasingly stringent regulations and reporting requirements across the globe.

Target Audience This course is intended for the following audiences: •

Project team members and consultants with a basic knowledge of Business Warehouse, SAP BusinessObjects Planning and Consolidation, and consolidation within accounting.

Course Prerequisites Required Knowledge •

BW310

Recommended Knowledge •

Practical knowledge of consolidation accounting

Course Goals This course will prepare you to: •

Set up and perform legal and managerial consolidation using SAP BusinessObjects Planning and Consolidation for NetWeaver.

Course Objectives After completing this course, you will be able to: • • • •

2010

Set up the Appset and Applications; Prepare the dimensions, properties, logic and business rules. Collect the transaction data, Create reports. Perform consolidation activities such as balance carry forward, journal entries, currency translation, validation, and eliminations. Report and analyze the data during and after the process.


vii

Course Overview

viii

BPC440


2010

Unit 1 Introduction to SAP BusinessObjects Planning and Consolidation Unit Overview This unit deals with the primary features for SAP BusinessObjects Planning and Consolidation, the delivered content, the course scenario, and a few of the basics of BW.

Unit Objectives After completing this unit, you will be able to: • • • • • •

Understand the key steps in the consolidation process. Identify the most important Business Planning and Consolidation features. Know what delivered ApShell components you can leverage. Discuss the course scenario. Understand the key components of Business Intelligence. Discuss how InfoCubes are written to.

Unit Contents Lesson: SAP BusinessObjects Planning and Consolidation Overview .....2 Lesson: SAP NetWeaver BW Overview ...................................... 20

2010


1

Unit 1: Introduction to SAP BusinessObjects Planning and Consolidation

BPC440

Lesson: SAP BusinessObjects Planning and Consolidation Overview Lesson Overview This is an introduction to the application's key features and delivered content.

Lesson Objectives After completing this lesson, you will be able to: • • • •

Understand the key steps in the consolidation process. Identify the most important Business Planning and Consolidation features. Know what delivered ApShell components you can leverage. Discuss the course scenario.

Business Example You need an understanding of what is involved in the consolidation process and what features and delivered content can be used to meet your consolidation requirements.

BPC 440 Contents - SAP BusinessObjects Planning and Consolidation Overview - Course Scenario - SAP NetWeaver BW Overview - Appsets and Applications - Dimensions, Properties, Hierarchies, and BW Characteristic Master Data Imports - Consolidation Logic and Business Rules - Data Collection via Flat Files, System to System, and InfoCube to InfoCube Loads. - Journal Entries and Balance Carry Forward. - Account Transformations, Allocations, and Validations. - Currency Translation. - Consolidation of Investment Concepts. - Application web parameter settings for Consolidation - Manage ownership data with the Dynamic Hierarchy Editor - Consolidation of Investment with the Purchase method.

2


2010

BPC440

Lesson: SAP BusinessObjects Planning and Consolidation Overview

- Inter Company Booking. - Inter Company Elimination (including easy to set up 'US' Elimination) - COI Equity and Proportional ownership elimination methods. - Business Process Flow for Consolidation tasks - Optional: Reporting on consolidation data. - Appendix: COI Example. - Appendix: Currency Translation example. - Appendix: More on delivered content. - Appendix: Appset and Application Parameters. - Appendix: Technical content on Connectivity, Performance, and Transports. - Appendix: List of How To Papers - Glossary - Index

Consolidation in General The consolidation process includes the collection of data from the underlying systems which will usually include ECC. (ERP Central Component). After the data is collected, it is prepared by carrying out manual adjustments, reclassifications, and currency translations. Validation can be run at any time in the overall process. Eliminations are the last part of the process where inter unit activities as well as consolidation of investments are performed.

2010


3


BPC440

Figure 1: What consolidation systems do

Note: Validations can be carried out at several points in the process. Statutory consolidation requires that the reported data of the group's consolidation units be aggregated into a single set of consolidated financial statements. This requires that the reported financial data is standardized to agree with the group's balance sheet valuations, is translated into the currency of the consolidation group and is purged of the effects from interunit activities. Internal or managerial consolidation (such as profit center consolidation) are used for controlling divisions of corporate enterprises. The main focus of the consolidation tasks is on the elimination of the effects of the delivery of goods and services within such enterprise areas. For example, you may want to eliminate interunit sales, accounts payable and accounts receivables.

4


2010

BPC440


Figure 2: The Application's Core Consolidation Functionality

The Application's Account Transformation business rules are used to carry out reclassifications. There are a few examples of when companies want to perform reclassifications. One example is when a subsidiary reports their inventory as finished goods. However, from a Group perspective the inventory is actually in process if it is not saleable and therefore it needs to be 'reclassified' as work in process. Another example is when you need to calculate and store cash flow values. Note: XBRL has been mandated by the US Securities and Exchange Commission. It stands for 'Extensible Business Reporting Language'. The SAP BusinessObjects Planning and Consolidation applications possible solutions include exporting data to a 3rd party tool called UBMatrix. Or, exporting the data to a BW InfoCube and have the XBRL application access the data via a BW Query.

2010


5


BPC440

Figure 3: The Value of Business Planning and Consolidation

Whatever software you use to do consolidations, it must be somewhat flexible. For example, how will we meet the new IFRS reporting requirements? The IFRS starter kit will help. There is a starter kit for both the BW and Microsoft platforms. Below, you will find some information regarding the IFRS changes. First known as International Accounting Standards (IAS), International Financial Reporting Standards (IFRS) was developed by the International Accounting Standards (IAS) Committee beginning in 1973. In 2001, the standards were certified by the International Accounting Standards Board (IASB) and formally adopted by the European Union as its single financial reporting standard Board to promote internationally comparable financial statements. The 2002 “Norwalk Agreement between the IASB and the U.S. Financial Accounting Standards (FASB) has led to a commitment that FASB rules and IFRS standards will be made fully compatible. The Canadian Accounting Standards Board has already adopted a timetable for convergence Board, and Canadian companies will be required to comply by 2011. Based on continuing convergence,

6


2010

BPC440


the U.S. SEC has announced that U.S. companies will be allowed to report under these new standards as early as 2009, and compliance for all U.S. companies could be required by 2014 assuming certain project milestones are met, such as: • • • • •

•

•

Improvements in accounting standards (such as IFRS). Funding and accountability of the International Accounting Standards Committee Foundation. Improvement in the ability to use interactive data (such as Extensible Business Reporting Language, or XBRL) for IFRS reporting. Education and training on IFRS in the United States. Limited early use by eligible entities. This milestone would give certain U.S. issuers the option of using IFRS for fiscal years ending on or after December 15, 2009. Anticipated timing of future rule making by the SEC . On the basis of the progress of milestones 1 through 4 and the experience gained from milestone 5, the SEC will determine in 2011 whether to require mandatory adoption of IFRS for all U.S. issuers. If so, the SEC will determine the date and approach for a mandatory transition to IFRS. Potentially, the option to use IFRS when filing could be expanded to other issuers before 2014. Potential implementation of mandatory use. The proposed road map will raise many questions, including whether the 2014 transition date to IFRS should be sequenced. The road map envisions a transition approach, where large accelerated filers could be required to comply in 2014, then accelerated filers in 2015, and non accelerated filers in 2016. Note: In the back of this unit, there is a display of the sub steps included in the 3 steps shown below.

2010


7


BPC440

Figure 4: Process-Centric

Note: Business Process Flows are available in all releases except the SAP BusinessObjects Planning and Consolidation version 7 for NetWeaver. They are included in version 7.5 however.

Figure 5: SAP BusinessObjects Planning and Consolidation Features

Note: This slide is not in the presentation.

8


2010

BPC440


Figure 6: SAP BusinessObjects Planning and Consolidation Functionality

Note: This slide is not in the presentation.

Figure 7: Setup by IT - Owned and Maintained by Business Users

The Version for the Microsoft Platform as well as NetWeaver has an IFRS Starter Kit with delivered methods, applications, and reports. ApShell

2010


9


BPC440

Figure 8: ApShell - The Delivered AppSet

Note: This slide is not in the presentation. You use the ApShell application set to build your own application sets. It contains sample applications, system information and defaults, and report and input schedule templates. Because it is a shell, it needs to be filled in with publications and reports in order to become a fully functioning application set. The dimension master data is included and that means it is ready to run. Caution: You must not modify ApShell. It is highly recommended that the delivered ApShell not be modified. Instead, ApShell should be utilized as a template for all customized Application Sets. ApShell contains the correct formatted property values required for many of SAP Business Planning and Consolidation’s delivered functionality. Recreating these property based interrelationships is highly complex and is likely to fail without deep technical knowledge of the requirements. What comes with Apshell?

Figure 9: ApShell - Delivered Content

10


2010

BPC440


The figure above is a summary list of what is included in the 'Version for SAP NetWeaver' ApShell application set. Note: There is more on delivered content in the appendix. Applications for Consolidation

Figure 10: SAP Business Planning and Consolidation Version for NetWeaver Delivered Applications

Note: See the public website at 'help.sap.com' Go to SAP Business User → EPM Solutions → Business Planning and Consolidations. Also, see the BPC how to papers on the Software Developers Network (SDN.SAP.COM). This site requires an on line system support id (OSS).

Figure 11: Delivered Consolidation Business Rules

Business rules are highly flexible functions within Business Planning and Consolidation applications for calculating and posting monetary amounts in support of common accounting activities, such as intercompany booking and currency translation. You can customize the business rules within BPC to meet your specific business requirements, for example, to indicate which balances to read before calculating an amount or under which account and data source to post the calculated amount. In addition to customizing default business rules, you can define new rules for various types of business processes and add them to an application. (much more on business rules coming right up!) BPC440 Course Scenario

2010


11


BPC440

Our goal in the BPC440 labs is to add the tables, data, logic, and reports to carry out legal consolidation. We will start with a copy of Apshell called BPC440_## which is your group number. This intended to be a very high level conceptual discussion. At the appset level, you have applications to store transaction data, dimensions to store master data, and other meta data tables. Note: The planning application is not a required application for legal consolidation but is included here as a context for our discussion on allocations.

Figure 12: Course Scenario: BPC440 Appset

In our labs, we will use these applications and these dimensions. This should be viewed as an example of how you could implement this software. Your approach will vary to some extent especially on the naming convention.

12


2010

BPC440


Figure 13: Course Scenario: Dimensions by Application

These are the logic files and business rules that you will be working with. The logic is delivered with Apshell and then modified for the course scenario.

Figure 14: Course Scenario: Logic files and business rules

2010


13


BPC440

Below, you can start to see how the pieces start to come together. Note: Process chains are event based 'jobs' that BW uses for background processing. Here they are used to pass parameter values.

Figure 15: Course Scenario: Legal Consolidation Architecture

The month end close process can be carried out with BPF's. A BPF is a user interface that serves as a launchpad and monitoring device.

14


2010

BPC440


Figure 16: Course Scenario: Business Process Flow - Consolidation Example

The BPF step takes the user to a report in this case with a hypertext link to a package.

Figure 17: Course Scenario: Launch a package via hypertext.

Here, the user inputs their data region and runs the job.

2010


15


BPC440

Figure 18: Course Scenario: The Consolidation Package

After the package is complete, the data is available for analysis.

Figure 19: Course Scenario: The End Result

16


2010

BPC440


Figure 20: Course scenario: Investment Structure

This is some of the master data we'll be using in the labs: Course Scenario: Master Data

2010

Dimension

Key Members

Comment

Entity

C9000

Corporate holding company

Entity

C1000-5000, C5100

Subsidiaries

Entity

CG1-4

Consolidation groups

Flow

F_100 and F_999

Opening balance and closing balance

C_Category

C_100

Actual (version)

Intco

I_C1000-5000, I_C5100, Trading partners I_C9000

C_Acct

11112000

Cash account (we'll see the rest in a moment)

C_Acct

Groups: 1, A, LOE, 2

1 - Balance Sheet accounts, A Assets, LOE - Liabilities and Owners Equity, 2 - Income Statement accounts

O_Acct

POWN, PCON, METHOD

Percent ownership, Percent consolidation, Method as in the Purchase or Equity method


17


18

BPC440

R_Acct

AVG, END

Average or End of month exchange rate

Time

2008.JAN

The first fiscal period

Time

2008.TOTAL

The year roll up member


2010

BPC440


Lesson Summary You should now be able to: • Understand the key steps in the consolidation process. • Identify the most important Business Planning and Consolidation features. • Know what delivered ApShell components you can leverage. • Discuss the course scenario.

2010


19


BPC440

Lesson: SAP NetWeaver BW Overview Lesson Overview This is a high level overview of BW.

Lesson Objectives After completing this lesson, you will be able to: • •

Understand the key components of Business Intelligence. Discuss how InfoCubes are written to.

Business Example You are the project lead for implementing SAP BusinessObjects Planning and Consolidation and you need to attain a high level understanding of how BW works.

Figure 21: BW and SAP BusinessObjects Planning and Consolidation Key Terms

20


2010

BPC440

Lesson: SAP NetWeaver BW Overview

The following comparison is primarily for those with a Business Consolidation System(BCS) background: • • • • • • • • • • • • • • • • • • • • • • • • •

Applications hold transaction data. Applications are InfoCubes in BW. Applications have multiple dimensions and they have multiple properties. The dimensions are characteristics and the attributes are navigational. The Legal application is equivalent to the InfoCube we define in the databasis. The Rate application would equal the TCURR table. The Ownership application is equivalent to the investment / equity data store object. Account Dimension = Item. Category = Version. Datasource Dimension = Posting level and document type. Entity Dimension= consolidation unit. Group Dimension= consolidations groups Intercompany Dimension = Trading Partner. Additional user defined dimensions = additional sub assignments. Business Rules = Methods. Account transformations = Reclassifications. Automatic Adjustments = Inter Unit Eliminations and COI Entries. Work status = Blocked tasks. BPF's relate to the Monitor. Input and Report Currency Dimension= currency key. In the Rate App: Account = Exchange Rate Type (Avg, End, etc) InfoProvider data manager package = Load Data Stream Balancing logic = Selected Items BPC for Excel = Business Explorer Analyzer BPC allows periodic or YTD data storage while BCS is always periodic. Note: Dimensions in Business Planning and Consolidation are the same as characteristics in BW. Dimensions in BW however are tables in an InfoCube. BW Dimensions may contain one or more characteristics.

2010


21


BPC440

Figure 22: ECCS BCS BPC Comparison

As a point of reference, here are all of the SAP solutions for consolidation: • • • •

Business Planning and Consoldiation - Microsoft and NetWeaver(BW) based. EC-CS: Enterprise Controlling Consolidation Systems in ECC BCS - Business Consolidation Systems - BW based. FC - Financial Consolidation (BusinessObjects) Note: This graphic is not part of the presentation. Note: ECCS stands for 'Enterprise Controlling Consolidation Systems (ECC Based), BCS stands for Business Consolidations System(BW Based). A 'Dimension' in ECCS context is the same as a BCS Consolidations Area. BPC in this context is the NW version. The Microsoft versions have a soft limit of 20 dimensions per Application.

Below you see the BW Architecture. From a consolidation perspective, BW offers an incredible data staging and transformation engine.

22


2010

BPC440


Figure 23: BW Architecture: Platform and Data Warehouse

Remember, the goal of BW is easy: Online Analytical Processing (OLAP) against large amounts of operative and historical data. OLAP technology permits multidimensional analyses according to various business perspectives. The BW server allows you to examine the relationships of data across all of your organizations. BW provides targeted information to companies, divided into roles. This information helps your employees to carry out their tasks, and it is visualized with the Web or Microsoft Excel (BEx Analyzer). To support these goals, the architecture of BW in general - and the warehouse component specifically - must be very technically robust. From a high level, InfoObjects are Fields and InfoCubes are tables.

2010


23


BPC440

Figure 24: InfoObjects (Fields)

Note: InfoCubes used for Business Planning and Consolidation only contain one key figure. From a modeling perspective, keep in mind that every record in the Cube requires a member for every dimension. Business evaluation objects are known in BW as InfoObjects. They are divided into characteristics (for example, customers), key figures (for example, revenue), units (for example, currency, amount unit), time characteristics (for example, fiscal year) and technical characteristics (for example, data request number). As components of the Metadata Repository (the storage area for all BW objects), InfoObjects contain technical and business analyst information for master and transaction data in BW. InfoObjects are used throughout the system to create structures and tables where data is stored. They enable information to be modeled in a structured form. They are also used to define reports and to evaluate master and transaction data. Attributes are InfoObjects (characteristics or key figures) that are used to describe characteristics in greater detail. For example, the characteristic cost center can be described in more detail with the profit center and person responsible information about the cost center. In this context, these two InfoObjects are used as attributes. If the 'with master data' (attributes) indicator was set on the Master Data/Texts tab, you are able to specify attributes and properties for these attributes on the Attributes tab page. Please be aware that the attributes themselves are also characteristics.

24


2010

BPC440


BW objects have a unique name space when generated from Business Planning and Consolidation. In the example above, the 'YY' is a unique prefix associated with the Appset. So, characteristics are Appset specific. This master data is time independent.

Figure 25: Master Data Bearing Characteristics

BW master data is stored outside of the InfoCube. However, from a Business Planning and Consolidation perspective, all three types of BW master data (texts, attributes, and hierarchies) are in the dimension tables. A characteristic is master data bearing if it specifies that tables of attributes, texts, or hierarchies are linked to it to provide additional information about the characteristic. It is up to your business process and the characteristic involved to decide if these master data tables should be enabled or not. They do provide a significant source of information for your reporting needs in many situations. One special aspect of 'normal BW' master data is that is shared (linked) with all InfoCubes that have the associated characteristic InfoObject as part of a dimension. This was made possible by removal of master data from the dimension tables using SID (surrogate ID) technology to create the links. The result is that you to use the master data with different BW InfoCubes. In other words, the master data is InfoCube independent, and can be used by several queries off several different InfoCubes simultaneously. Note: Business Planning and Consolidationmaster data is Appset specific except for a few attributes.

2010


25


BPC440

Hierarchies are used in analysis to describe alternative views of the data. They serve as a grouping function just as they do in other SAP products, like ECC. A hierarchy consists of several nodes and leaves, forming a parent-child relationship. The nodes represent any grouping you desire, for example, ‘west region’. The hierarchy leaves are represented by the characteristic values, perhaps a salesperson. On the Hierarchy tab page, you determine whether or not the characteristic can have hierarchies and, if so, what properties these hierarchies are allowed to have. If the 'with hierarchies' indicator is set, hierarchies can be created manually for this characteristic (transaction RSH1). Alternately, they can be loaded from the SAP system or other source systems. 'Normal BW' hierarchy structures (a hierarchy node) can be time-dependent. The hierarchy is then constructed for the current key date or for the key date specified in the query. Hierarchies used for Business Planning and Consolidation purposes are time independent as is all Business Planning and Consolidation master data. Example: During restructuring of an organization's sales districts, it was found that an employee is assigned to different cost centers at different times.

Figure 26: InfoCube: A Schema of Tables to Store Summary Information

InfoCubes are the primary objects used to support BW queries. They are designed to store summarized and aggregated data for long periods of time. The figure above is a simplified illustration. The industry standard name that correlates to SAP's InfoCubes is a Star Schema.

26


2010

BPC440


Figure 27: BW Extended Star Schema Illustration

Fact tables in BW do not contain any characteristic values, but they do store integers that are referenced to them. Thus, the joins of the transaction data inside the InfoCube to the master data outside of the InfoCube is optimized. Multidimensional data models are needed for the creation of Enterprise Data Warehousing or OLAP applications, in other words, for analytical applications. The problems with OLTP's normalized design preclude it from being used to support complex, ad hoc data analysis. The classic star schema, is the most frequently used multidimensional model for relational databases. This database schema classifies two groups of data: facts (sales amount or quantity, for example) and dimension attributes (customer, material, or time, for example). Facts, sometimes called measures, are the focus of the analysis for a business process. The fact data (values for the facts) is stored in a highly normalized fact table. The values of the dimension attributes are stored from a technical perspective, in various de-normalized dimension tables. From a business perspective, these tables are collectively referred to as dimensions of the business process, or for short, dimensions. Here, logically related dimension attributes are stored as a hierarchy (parent-child relationships) within the dimension table. The dimension tables are linked with the central fact table by way of key relationships. In the star schema design shown, the key of the dimension tables is a machine-generated dimension key (DIM ID) that uniquely defines a comBWnation of dimension attribute values. The DIM ID (a sequentially assigned number) is a foreign key in the fact table. In this way, all data records in the fact table can be uniquely identified.

2010


27


BPC440

Figure 28: Real Time InfoCubes (Input data is available right away)

Request id's stay 'open' until a threshold of 50,000 records is reached. However, they can be closed by turning the request id green, switching from plan to load mode, or by running the 'close trans request' function module. Closing the request id is required if you want to load the data from the BPC Infocube to another let's say 'reporting' InfoCube. Also, it is a useful technique for testing execution of a consolidations job since you can isolate the effect of currency translation for example in a separate request id for validation purposes. Here's a summary of the differences: Type of InfoCube >

Standard

Real Time

Optimized For

Read

Write

Data Mode

BW data loads

BW data loads OR Writing

Request ID

Closes(green) after data Stays open(yellow) up to loads 50k records

Real-time InfoCubes differ from standard InfoCubes in their ability to support parallel write accesses. Standard InfoCubes are technically optimized for read access. The data is simultaneously written to the InfoCube by multiple users. Standard InfoCubes are not suitable for this. You should use standard InfoCubes for read-only access (for example, when reading reference data).

28


2010

BPC440


Real-time InfoCubes can be filled with data from BPC via manual iput, journal entries, and data imports while the Infocube is in Plan mode. If the Infocube is switched to Load mode then BW can be used to load the Infocube. You have the option to change the 'data mode' of a real-time InfoCube. To do this, in the context menu of your real-time InfoCube in the InfoProvider tree, choose 'Change Real Time Load Behavior'. By default, 'Real-Time Cubes Can Be Planned, Data Loading Not Permitted' is selected. Switch this setting to 'Real-Time Cube Can Be Loaded With Data; Planning Not Permitted' if you want to fill the cube with data using BW staging. When you enter planning data, the data is written to a data request of the real-time InfoCube. As soon as the number of records in a data request exceeds a 50,000 records, the request is closed and a roll up is carried out for this request in defined aggregates (asynchronously). You can still roll up and define aggregates, collapse/compress, and so on, as before. Depending on the database on which they are based, real-time InfoCubes differ from standard InfoCubes in the way they are indexed and partitioned. For an Oracle DBMS, this means, for example, no BWtmap indexes for the fact table and no partitioning (initiated by BW) of the fact table according to the time dimension. Reduced read-only performance is accepted as a drawback of real-time InfoCubes, in favor of the option of parallel (transactional) writing and improved write performance. The BW F Fact table is similar to the Microsoft based Write Back and Fac2 table. The BW 'E' Fact table is like the Microsoft Fact table.

Figure 29: Writing into a Real-Time InfoCube

The Real-time InfoCube is heavily used in applications like Business Consolidations Systems, Business Planning and Simulation, and Integrated Planning. The idea behind a Real-time InfoCube is that in some applications only

2010


29


BPC440

small amounts of data need to be written to an InfoCube. The point about this requirement is that a standard InfoCube is designed for mass data loads. Hence, SAP needed a technology to deal with lots of small updates in an efficient way. The Real-time InfoCube does not create a new Request ID for each data input. All users share the same request in an InfoCube. On this graphic, you can a see a typical scenario where a Real-time InfoCube is used. There are two types of data entries for this application: (1) user enters the data manually, (2) run automatic planning functions which might copy or revaluate data from existing records. An F-Fact table consists of different requests. In the example above, the InfoCube consists of three requests, the first two requests are closed requests, but the third request is an open request. All users write into the same (open) request, it can also happen that one User writes multiple times into that request. The open request in the Data Warehousing Workbench is displayed with a yellow status information. The short text for all the InfoPackages which were or are a open request just indicates that the request was created by the Real Time interface. The closed requests do have status information, but they do not have any data monitor entries.

Figure 30: Optimizing Applications

When users input and save data or when they run a package that generates data, it goes into the F Fact table of the InfoCube. This table stores delta records that represent changes to the net values.

30


2010

BPC440


Figure 31: InfoProviders

An InfoProvider is a BW object that can be queried. These include InfoCubes which contain data as well as multiproviders which do not. InfoProviders are physical objects or sometimes just logical views. That are relevant for reporting. The definition correctly infers that an InfoProvider can be either a physical storage of data in real database tables, or a virtual collection of data (like a view) that only collects data temporarily to feed it to a query, but does not permanently store it.

2010


31


BPC440

Figure 32: Business Planning and Consolidation generated Multiproviders

32


2010

BPC440


Lesson Summary You should now be able to: • Understand the key components of Business Intelligence. • Discuss how InfoCubes are written to.

2010


33

Unit Summary

BPC440

Unit Summary You should now be able to: • Understand the key steps in the consolidation process. • Identify the most important Business Planning and Consolidation features. • Know what delivered ApShell components you can leverage. • Discuss the course scenario. • Understand the key components of Business Intelligence. • Discuss how InfoCubes are written to.

34


2010

BPC440

Test Your Knowledge

Test Your Knowledge 1.

The most important BPC Consolidations Features include: Choose the correct answer(s).

2.

□ □ □ □

A B C D

□ □

E F

The ability to load data from multiple source systems. Push back of data to ECC. Flexible multidimensional data model. Automated consolidation functions such as balance carry forward and eliminations. Full support of all the major accounting standards. The ability to run BW Queries on Business Planning and Consolidation data.

Which of the following ApShell components can be used for Legal Consolidations? Choose the correct answer(s).

3.

□ □ □ □

A B C D

□

E

□

F

The account, flow, entity and intercompany dimensions. The delivered legal application. The master data in the delivered dimensions. The delivered logic files for the consolidations functions such as consolidation, balance carry forward, and currency translation. The delivered process chains that go with the consolidation functions. The delivered packages for each of the consolidation functions.

Which of the following are correct statements regarding what is delivered or available with the NetWeaver release? Choose the correct answer(s).

2010

□

A

□

B

□

C

□

D

□ □

E F

Business Process Flows are not in the NW 7.0 but are in the 7.5 release. The Dynamic Hierarchy Editor is not in the 7.0 release but is in the 7.5 realease. The data can also be entered very easily via input templates. The NW release features the availability of various data bases and also the use of the BW Accelerator. Time dependent hierarchies in Business Planning and Consolidation are not supported in 7.0. Transports are only available with Microsoft releases. NW features debug capability of script logic.


35

Test Your Knowledge

4.

BPC440

Which of the following statements are true regarding Business Planning and Consolidation vs. BW terms? Choose the correct answer(s).

5.

□

A

□

B

□

C

□ □

D E

□

F

An SAP BusinessObjects Planning and Consolidation dimension is like a BW Characteristic. An SAP BusinessObjects Planning and Consolidation property is like an Attribute in BW. The SAP BusinessObjects Planning and Consolidation 'signed data' column is like a key figure in an InfoCube. An AppSet is like a BW InfoArea. An SAP BusinessObjects Planning and Consolidation team folder is equivalent to a BW Role. An SAP BusinessObjects Planning and Consolidation InfoCube is just like an Application in BW.

Which of the statements below are correct in regards to BW? Choose the correct answer(s).

6.

□ □

A B

□ □

C D

InfoCubes are made up of Fact and Dimension tables. A BW Dimension table is exactly the same as an Business Planning and Consolidation Dimension. BW Characteristics have three potential types of master data. There are two main types of InfoObjects: Catalogs and InfoAreas.

Which of the following are true regarding Real Time InfoCubes? Choose the correct answer(s).

36

□

A

□

B

□

C

□

D

□

E

□

F

Real Time InfoCubes are write optimized but Standard InfoCubes are read optimized. Real Time InfoCubes are write optimized because the request id stays open until a threshold is reached for example. Request id's in real time cubes can be closed by switching the cube to the Standard type. A Real Time InfoCube has two 'data' modes, but only one will ever be used by Business Planning and Consolidation. As data comes in to the Real Time InfoCube, it arrives in the 'F' table and remains there until it is compressed into the 'E' table. SAP BusinessObjects Planning and Consolidation can also be set up against Data Store Objects.


2010

BPC440

Test Your Knowledge

Answers 1.

The most important BPC Consolidations Features include: Answer: A, C, D, E B. SAP Business Planning and Consolidation Version for NetWeaver does not support pushing data back to ECC. If you need that functionality, you may want to consider using the open hub. F. Running BW Queries on Business Planning and Consolidation data is not an 'out of the box' solution because it would not use the SAP Business Planning and Consolidation logic to read the correct signs to apply to the data for example.

2.

Which of the following ApShell components can be used for Legal Consolidations? Answer: A, C, D, E, F B. ApShell does not come with a delivered legal application in NetWeaver.

3.

Which of the following are correct statements regarding what is delivered or available with the NetWeaver release? Answer: A, B, C, D, F E. Transports are only possible with the NW release.

4.

Which of the following statements are true regarding Business Planning and Consolidation vs. BW terms? Answer: A, B, C, D E. A SAP BusinessObjects Planning and Consolidation team folder is a folder with controlled access for team members. A BW Role can have a menu which is like a folder but it can also have security attached to it as well. F. SAP BusinessObjects Planning and Consolidation has applications which are represented in BW by InfoCubes.

2010


37

Test Your Knowledge

5.

BPC440

Which of the statements below are correct in regards to BW? Answer: A, C B. A BW Dimension table may consist of one or more characteristics. (which are equivalent to SAP BusinessObjects Planning and Consolidation Dimensions!). Characteristics can have Hierarchies, Attributes, and Text. D. The two types of InfoObjects are characteristics and key figures.

6.

Which of the following are true regarding Real Time InfoCubes? Answer: A, B, D, E C. Real time InfoCubes cannot be switched to Standard. Real time InfoCubes have two data modes: Load and Plan. If they are used for SAP BusinessObjects Planning and Consolidation, they will most likely never be in 'Load' mode. F. SAP BusinessObjects Planning and Consolidation cannot be used to write data to a Data Store Object.

38


2010

Unit 2 SAP BusinessObjects Planning and Consolidation Framework Unit Overview In this unit we will discuss the architecture of the application sets, applications, dimensions, and their properties. This implementation phase of a project would normally be carried out after gathering the business requirements. We will also cover the unique logic that is used in consolidation.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • • • •

Identify the applications used in legal consolidation. Create and maintain applications. Identify when dependent applications are needed. Select various business rules to meet your consolidation requirements. Recite the four components of secutity. Identify what dimensions are used by which applications. Discuss the properties used by the various dimensions. Understand how properties are used in the consolidation process. Maintain dimensions. Explain how to use the three types of logic. Understand the architecture of Consolidation tasks. Use default logic and system constants for your consolidation project. Use script logic to create balancing adjustments.

Unit Contents Lesson: Appsets and Applications............................................. 40 Exercise 1: Creating AppSets and Applications......................... 51 Lesson: Dimensions, Properties, and Loading Master Data ............... 86 Exercise 2: Maintaining Dimensions .....................................107 Lesson: Consolidation Logic ..................................................125 Exercise 3: Consolidation Logic ..........................................139

2010


39

Unit 2: SAP BusinessObjects Planning and Consolidation Framework

BPC440

Lesson: Appsets and Applications Lesson Overview This lesson deals with application sets and applications used for legal consolidation.

Lesson Objectives After completing this lesson, you will be able to: • • • • •

Identify the applications used in legal consolidation. Create and maintain applications. Identify when dependent applications are needed. Select various business rules to meet your consolidation requirements. Recite the four components of secutity.

Business Example You need to set Business Planning and Consolidation up to do Legal Consolidations and you are interested in the application set and how to model the applications. Note: Dimensions are discussed in depth in the next unit. That unit also covers which dimensions you need for the various applications.

Figure 33: Implementation Steps

Note: Not all of these steps need to be completed in this exact order. Development can be carried out from the Admin Console. The system automatically populates BW with the related objects.

40


2010

BPC440

Lesson: Appsets and Applications

Figure 34: BI and Business Planning and Consolidation ... A Visual

What Applications do you need for Consolidation?

Figure 35: Legal Consolidation Applications

Application Types

2010


41


BPC440

Figure 36:

Note: Although all applications can be reported on using normal BPC excel, the applications are referred to as 'Reporting' and 'Non-Reporting' because support applications such as rate and ownership cannot be reported on using Insight (Insight is the infrequently used predictive analytics tool). 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 to these application types. All applications require at least the four main dimension-types: Entity, Account, Time, and Category. You will create an IC (Inter Company) Matching application which is a Financial Reporting type application.

42


2010

BPC440


Figure 37: Application Types

Consolidation applications perform more complicated legal consolidation functions than Financial applications. Consolidations can incorporate complex organizational structures involving full ownership, partial ownership, minority ownership and consolidation methods. Consolidation applications must reference an Ownership application and a Rate application

Figure 38: Referencing Applications and Business Rules

Note: Application options are equivalent to business rules.

2010


43


BPC440

Consolidation business rules allow the automated processing of data to render a consolidated set of financial statements. This is commonly thought of as eliminations of investments in subsidiaries, adjustments of minority interest, reclassifications and any other postings depending on the nature of the consolidation methodologies required. The enabling of this functionality is done through a combination of stored procedures (In Microsoft platform), ABAP (Netweaver Platform), Logic Files, Data Manager Packages, and Business Rule tables. Security There are four components of BPC security: Users, Teams, Member access profiles, and Task profiles. BPC security is independent of BW security.

Figure 39: Security - Before Assignments

Security components are normally created first and then the assignments are made according to a well laid out plan.

44


2010

BPC440


Figure 40: Security - Possible Assignments

When you create new applications, you need to select at least one 'secure' dimension. Then the member access profiles need to allow access to the desired members. For example, in the LegalApp below, the category and entity dimensions have been selected as 'Secure Dimensions'.

Figure 41: Legal Application - Secure Dimensions

In security, here is what the member access profiles look like:

2010


45


BPC440

Figure 42: Member Access Profile - Legal

Application parameters provide a nice collection point for properties that affect how applications are used. The Legal application is an excellent example because it requires quite a few settings. In this case, some of the more important parameters are used to determine how organizational information from the ownership application is used.

Figure 43: Legal Application Parameters

Note: Workstatusvalidate is only applicable to the Microsoft releases. It is used to prevent the advance of a work state if there is a balance in the designated 'validation' account.

46


2010

BPC440


The Legal Application Parameters: •

•

•

• • •

• •

• •

Opening Balance: Enables the business rule table for balance carry forward. If you checked the copy opening option when you created the application, then this parameter will already have a value of '1'. Org_Accountlist: Member id’s of the ownership account dimension that store methods, %consolidation, and %ownership. These will appear in the dynamic hierarchy editor. Org_Accountdown: member id of the ownership account that specifies the Position of a consolidation entity within the group for example 90 will be used for 'parents'.. Org_intco: the 3rd party (external) member in the Intercompany dimension to which all ownership calculations are posted. Org_ownershipcube: name of the linked Ownership application. Org_parentproperty: property name in the Groups dimension to define the hierarchy used in the dynamic hierarchy editor. The Group property that will contain the legal rollup members. Ownership_App: the consolidation logic requires the Ownership application to be listed here as well. USElim: Allows the use of the business rule tables for US Eliminations. Note: US Elimination is an easy way to do one sided eliminations. The first to use it happened to be a US company! This can be used for sales and cogs eliminations for example. Validations: Allows the use of the validation business rule tables. YTD Input: This will cause the application to collect Year To Date (cumulative) data in the Fact tables. Note: All of the properties which begin with 'ORG...' are related to the Dynamic Hierarchy Editor.

The 'US Eliminations' option could be used in cases where ownership elimination are not required. Note: We'll discuss what dimensions you need in an application in the next lesson. Year to Date vs. Periodic Applications

2010


47


BPC440

Figure 44: Year to Date vs. Periodic

The application is set to YTD in the web parameters. We will do that shortly. New applications default to periodic.

Figure 45: Year To Date Application

48


2010

BPC440


Optimizing Applications

Figure 46: Application Optimization Overview

2010


49


50


BPC440

2010

BPC440


Exercise 1: Creating AppSets and Applications Exercise Objectives After completing this exercise, you will be able to: • Review your BPC440_## Appset for Legal Consolidation. It is a copy of ApShell. • Create the Legal, Ownership, and IC Matching applications. • Make the required security settings. • Identify the purpose behind the Application parameters. • Copy the course files to your own directory.

Business Example After you have identified the business requirements for a Legal Consolidations project, you will need to understand how to create the necessary applications with the appropriate parameters. Caution: Please give all of the application and dimensions you create a name in UPPER CASE. The descriptions can however be in Mixed Case. Perform these labs as instructed so that subsequent labs will work properly. Caution: Please use the drop downs instead of manually typing field values in the labs this week.

Task 1: Access your BPC440_## AppSet 1.

Log on to BPC using the instructions provided by your instructor.

Continued on next page

2010


51


BPC440

Task 2: Define applications and dimensions Your mission is to create everything you need to do legal consolidation by using Apshell as much as possible. The business requirements call for us to configure for every consolidation task such as balance carry forward and currency translation and also to do reporting on the results. In the first section, we need to basically work on the fields and tables. We will create the applications you need for Legal Consolidation using the dimensions that were inherited from ApShell. We will use the Rate application as is except we will replace Category with C_Category so that all the related applications use the same category dimension. 1.

Take a look at the Rate Application, and make a note of its dimensions. Replace Category with C_Category and make it secure along with R_Entity. We will use the category and entity dimensions to control access to data in the applications. The legal, rate, and ownership applications all need to use the same category dimension. Note: The next unit covers dimensions in detail including which ones you need per application.

2.

Before we create our first application, we must prepare the intercompany dimension. Apshell comes delivered with mixed case members in the Intco dimension and although that may not be critical in real life we decided it would be better for the training labs to use upper case. Normally you can just delete members and add the upper case values back in. However, during testing for this class, we decided to minimize the risk of issues while updating dimension members by deleting the existing Intco dimension and re creating it. Then copy and paste the upper case members from the Legal dimension file on the remote desktop. Dimensions can be deleted if they do not belong to an Application.

3.

Create the CONSGROUP dimension (Group type) and add the members in the 'LegalAppDimension' file on your virtual desktop C Drive in the BPC440_## folder.

4.

Create the OWNERSHIP Application to store ownership data like % ownership and parent assignments. Use the 'Ownership' Type. Make C_Category and Entity secure. Include the following dimensions: Dimension

Type

Secure

Consgroup

Group

No

C_Category

Category

Yes

Entity

Entity

Yes Continued on next page

52


2010

BPC440


5.

IntCo

Intercompany

No

O_Acct

Account

No

Time

Time

No

The Legal application will use the C_Acct dimension which needs to be changed (we'll get to that). But, before we prepare the C_Acct dimension, we need to add members to the R_ACCT dimension. (Account members have a rate type property which will be referenced to members in the R_Acct dimension.) Below you can see the members you need to add to R_ACCT:

6.

ID

Evdescription

AccType

RateType

HISTGDW

Historical Goodwill

AST

FX

HISTFLOW

Historical Flow

AST

FX

CTAFLOW

Curr Tsl Flow

AST

FX

AVGFLOW

Average Flow

AST

FX

HISTINV

Historical Investments

AST

FX

ENDFLOW

End Flow

AST

FX

We need to prepare an Account dimension for it called C_Acct. Apshell comes delivered with the C_Acct dimension but we need a different set of members as well as properties. So while it may not always be necessary in real life, we will delete the existing dimension and re create it with the properties shown below in hopes of giving you the best experience in the class. In addition, C_ACCT will be referenced to R_ACCT. Note: The list below describes how the most important properties are used. 'DIMLIST#' properties are used to provide selection criteria in business rules. 'GROUP' is used to designate an account as PL or BS. 'ELIMACC' is used for US Elims and logic based eliminations in Microsoft typically. 'FORMULA' is for dimension formulas.

7.

In the C_ACCT dimension add the members in the 'LegalAppDimension' file on your virtual desktop C Drive in the BPC440_## folder. Continued on next page

2010


53


BPC440

8.

We'll use the RptCurrency dimension to capture currency data in the Legal Applicaiton. To be able to use it, add CURRENCY_TYPE and STORE_ENTITY to the properties of the existing RptCurrency dimension and enter the transaction currency member as shown below:

9.

Now let's create the Legal Application and call it the 'LEGALAPP'. Select the 'Consolidation type'. Add the following dimensions: Dimension

Type

Secure

ConsGroup

Group

No

C_Acct

Account

No

C_Category

Category

Yes

C_Datasrc

Datasrc

No

Entity

Entity

Yes

Flow

Sub Table

No

IntCo

Intercompany

No

RptCurrency

Currency

No

Time

Time

No

Dimension

Type

Secure

Turn on all of the Business Rule tables except for Intercompany Bookings (we will use this in the IC Matching Application). Business rule tables can be turned on or off at any time. 10. Our business requirements call for us to resolve inter company differences in a separate application. Therefore, create the Inter Company Matching Application called 'ICMATCHING' Select the Reporting / Financial type. Include the following dimensions: Consgroup, C_Acct, C_Category, C_Datasrc, Entity, Flow, Intco, RptCurrency,Time. Select the Business Rule tables for Currency Translation and Inter Company Bookings. Make C_Category and Entity secure. Note: It is also possible to do matching in the legal application depending on the business requirements. 11. When you create a new Appset, it is good practice to process all of the dimensions.

Result Your Appset should look like this: Continued on next page

54


2010

BPC440


Figure 47: All Applications

Task 3: Allow access to the Applications and Tasks in security. Now we need to give ourselves access to the new applications and also, in this case, to all of the tasks. 1.

Give your user rights to all tasks in BPC by modifying the existing 'Full_Tsk' task profile. Give the Full_Tsk profile a description of 'All Tasks'. Select all three Admin functions and add all of the tasks for all of the interfaces.

2.

Add read/write access for both the Category and Entity type dimensions to all of your applications. Modify the existing 'Full_Mbr' member access profile. Add a description of 'All Members'. Caution: Do not type in the selections, use the system drop downs. Give read/write access to both of the secure dimensions for all members. Confirm the assignments of the profiles above to the Admin team. Confirm the assignment of your user id to the team as well .


2010


55


BPC440

Task 4: Application Parameters Set the application parameters for the ICMatching and Legal applications from Web Administration. These settings control how the applications are used (similar to 'configuration settings' in ECC). There are quite a few however so don't forget that they are fully defined in the appendix. Note: Some of these will already have values. For, example if you selected 'currency translation' when you created ICMATCHING, then the FXTRANS web parameter will have a value of '1'. 1.

Set the application parameters for ICMatching as shown below and also make it a YTD application:

2.

From the BPC Web Administration, set the following application parameters for theLegalApp as shown: KeyID

Value

JRN_BALANCE

1

JRN_POST_OVERWRITE

Y

YTDINPUT

Yes

Note: JRN_POST_OVERWRITE is set to Yes so that the system will retain the same journal id # if a posted journal is set to unposted and then back to posted.


56


2010

BPC440


Result Note: We will be using the properties that begin with 'Org' in the consolidation of investments unit. However, here are the explanations on the 'Org' properties and a couple of others for now: •

•

•

• • •

• •

• •

Opening Balance: Enables the business rule table for balance carry forward. If you checked the copy opening option when you created the application, then this parameter will already have a value of '1'. Org_Accountlist: Member id’s of the ownership account dimension that store methods, %consolidation, and %ownership. These will appear in the dynamic hierarchy editor. Org_Accountdown: member id of the ownership account that specifies the Position of a consolidation entity within the group for example 90 will be used for 'parents'.. Org_intco: the 3rd party (external) member in the Intercompany dimension to which all ownership calculations are posted. Org_ownershipcube: name of the linked Ownership application. Org_parentproperty: property name in the Groups dimension to define the hierarchy used in the dynamic hierarchy editor. The Group property that will contain the legal rollup members. Ownership_App: the consolidation logic requires the Ownership application to be listed here as well. USElim: Allows the use of the business rule tables for US Eliminations. Note: US Elimination is an easy way to do one sided eliminations. The first to use it happened to be a US company! This can be used for sales and cogs eliminations for example. Validations: Allows the use of the validation business rule tables. YTD Input: This will cause the application to collect Year To Date (cumulative) data in the Fact tables. Note: All of the properties which begin with 'ORG...' are related to the Dynamic Hierarchy Editor.

2010


57


BPC440

Solution 1: Creating AppSets and Applications Task 1: Access your BPC440_## AppSet 1.

Log on to BPC using the instructions provided by your instructor. a)

Open the “BPC Administration” link to get to the Admin Console. Note: The ## refers to your assigned group number. Where you see BPC440_00 (or 02) for example, you will use your assigned ##.

Figure 48: Logon to Business Planning and Consolidation

b)

Select the Connection Wizard link.


58


2010

BPC440


Figure 49: The Connection Wizard

c)

Next → Select a different user and password → User: CPM-## PW: training

Figure 50: Credentials

d)

Next → Select Appset BPC440_##.


2010


59


BPC440

Figure 51: Logon to your Appset

e)

Select the BPC440_## Appset → Next → Finish → Ok.

f)

Open up the 'Dimension Library' on the upper left → Open up the Applications folder. Note: Below you see the 'Admin Console'. Notice the icon in your status bar with the blue wrench labeled: SAP Business Objects.


60


2010

BPC440


Figure 52: BPC440_## - Copy of ApShell

g)

Collapse the 'Dimension Library'.

h)

Copy the course files to your own folder: In your remote desktop → Select Start on the lower left → Documents → My Documents → Select the C-drive → BPC440 → Right click on Files → Copy → Right click on your folder BPC440_## → Paste. Note: The 'C-Drive' will be used in this these course labs to mean 'Local Disk (C):'.

Task 2: Define applications and dimensions Your mission is to create everything you need to do legal consolidation by using Apshell as much as possible. The business requirements call for us to configure for every consolidation task such as balance carry forward and currency translation and also to do reporting on the results.


2010


61


BPC440

In the first section, we need to basically work on the fields and tables. We will create the applications you need for Legal Consolidation using the dimensions that were inherited from ApShell. We will use the Rate application as is except we will replace Category with C_Category so that all the related applications use the same category dimension. 1.

Take a look at the Rate Application, and make a note of its dimensions. Replace Category with C_Category and make it secure along with R_Entity. We will use the category and entity dimensions to control access to data in the applications. The legal, rate, and ownership applications all need to use the same category dimension. Note: The next unit covers dimensions in detail including which ones you need per application. a)

Select the Rate Application on the upper left → Open up its dimensions folder ( select the '+' sign) just to see what's in there → With your cursor on the Rate Application → Select ‘Modify Application’ on the right.

Figure 53: Rate Application Dimensions (before)

b)

Remove Category → Add C_Category (we will use C_Category for all consolidation related applications) →Make both R_Entity and C_Category secure → ' 'Change application type' → confirm that it is a 'Rate' type application →'Modify Application' → OK. Note: R_Entity is being used as a 'placeholder' as the E type dimension in the Rate application, it only has one member. Continued on next page

62


2010

BPC440


2.

Before we create our first application, we must prepare the intercompany dimension. Apshell comes delivered with mixed case members in the Intco dimension and although that may not be critical in real life we decided it would be better for the training labs to use upper case. Normally you can just delete members and add the upper case values back in. However, during testing for this class, we decided to minimize the risk of issues while updating dimension members by deleting the existing Intco dimension and re creating it. Then copy and paste the upper case members from the Legal dimension file on the remote desktop.


2010


63


BPC440

Dimensions can be deleted if they do not belong to an Application. a)

Select 'dimension library' on the upper left → Select the Intco dimension on the upper left → 'Delete dimension' on the right →Check off Intco if necessary → 'Delete selected dimensions' → OK.

b)

Select 'dimension library' on the upper left → Select 'Add a new dimension' on the right → Use a NAME (UPPER CASE) and Description of INTCO → Go to step 2 of 3 → Select 'I' InterCompany → Use Entity as the Reference Dimension:

Figure 54: Intco referenced to Entity

3.

c)

Go to step 3 of 3 →View the system generated properties → 'Add new dimension' → OK.

d)

Populate your new dimension with master data manually: Select the INTCO dimension on the left → 'Maintain dimension members' on the right → Copy A2:D14 from the LegalAppDimensions file in the INTCO sheet on your remote C Drive in the BPC440_## folder in the Legal folder → Paste into A2 of the member sheet → 'Process dimension' → Ok → Ok.(You have just updated BW)

Create the CONSGROUP dimension (Group type) and add the members in the 'LegalAppDimension' file on your virtual desktop C Drive in the BPC440_## folder. a)

Select dimension library → 'Add new dimension' → Enter CONSGROUP as the name → Enter Consgroup as the description → go to step 2 of 3 → Select type 'G - Group' → Go to step 3 of 3 → You will see the required properties in blue for the Group dimension type: Continued on next page

64


2010

BPC440


Figure 55: CONSGROUP Properties

b)

'Add a new dimension' →OK(now the BW characteristic is in place) → Select CONSGROUP on the left → Select 'Maintain dimension members' on the right.

c)

Go to your virtual desktop C Drive → BPC440 → BPC440_## → Files → LegalApp → Open the 'LegalAppDimension' file → Select sheet 'Consgroup' → The members should already be selected → Right click in the pre-selected area → Copy.

d)

In the Admin Console → Go to cell A2 of the CONSGROUP Membersheet → Right click → Paste → Process Dimension → Ok → Ok.


2010


65


BPC440

Figure 56: CONSGROUP Members

4.

Create the OWNERSHIP Application to store ownership data like % ownership and parent assignments. Use the 'Ownership' Type. Make C_Category and Entity secure. Include the following dimensions: Dimension

Type

Secure

Consgroup

Group

No

C_Category

Category

Yes

Entity

Entity

Yes

IntCo

Intercompany

No

O_Acct

Account

No

Time

Time

No

a)

Select Application on the left → Select 'Add a new Application' on the right → Enter a Name and Description of 'OWNERSHIP' → Go to Step 2 of 4. Select the Ownership application type → Go to Step 3 of 4 → Confirm that the Rate application is selected as the source (mainly to determine the proposed dimensions) → Go to Step 4 of 4 → Deselect dimensions and journals (if it is not greyed out) → 'Add a New Application'. Note: When you create a new application, they system will copy publications which are Excel files published to the web, document attachments such as word and ppt files in the (web) Content Library, Excel Reports, Teams (in security), and data manager packages. All of these options are copied from the Continued on next page

66


2010

BPC440


source application by default. You can also choose whether to copy the dimensions and journal documents (from the journal detail tables, not the journal postings in the Infocube.) b)

Remove all existing dimensions and add the ones shown above: Note: It isn't required to remove all the dimensions however it makes it a little easier to match up with the screen shot. The dimensions with the blue background are required.

Figure 57: Ownership Application Dimensions

c)

Make both C_Category and Entity 'Secure' by selecting each one and pressing the 'Secured' button → 'Add a new application' → OK. You have now created a BW InfoCube.

5.

The Legal application will use the C_Acct dimension which needs to be changed (we'll get to that). But, before we prepare the C_Acct dimension, we need to add members to the R_ACCT dimension. (Account members have a rate type property which will be referenced to members in the R_Acct dimension.) Below you can see the members you need to add to R_ACCT: ID

Evdescription

AccType

RateType

HISTGDW

Historical Goodwill

AST

FX

HISTFLOW

Historical Flow

AST

FX

CTAFLOW

Curr Tsl Flow

AST

FX


2010


67


BPC440

AVGFLOW

Average Flow

AST

FX

HISTINV

Historical Investments

AST

FX

ENDFLOW

End Flow

AST

FX

a)

Open up the Dimension Library on the upper left → Select the R_Acct dimension on the left → Maintain dimension members → In A2 → Add (End and Avg will already be there) the data you see above by copying from your LegalAppDimensions file R_Acct sheet in your BP440_## folder on the C-Drive → Process dimension → Ok → Ok. Note: The FX (foreign exchange) property is required for currency translation to work.

6.

We need to prepare an Account dimension for it called C_Acct. Apshell comes delivered with the C_Acct dimension but we need a different set of members as well as properties. So while it may not always be necessary in real life, we will delete the existing dimension and re create it with the properties shown below in hopes of giving you the best experience in the class. In addition, C_ACCT will be referenced to R_ACCT. Note: The list below describes how the most important properties are used. 'DIMLIST#' properties are used to provide selection criteria in business rules. 'GROUP' is used to designate an account as PL or BS. 'ELIMACC' is used for US Elims and logic based eliminations in Microsoft typically. 'FORMULA' is for dimension formulas. a)

In the Admin Console: Select the C_Acct dimension on the left → Delete Dimension → C_Acct should be checked → Delete selected dimensions → OK.

b)

Select the Dimension library on the upper left → Choose 'Add a new dimension' on the right → Enter the name as 'C_ACCT' and description: 'C_Acct' → Go to step 2 of 3 → Choose the 'R_Acct' as the reference dimension:


68


2010

BPC440


Figure 58: C_ACCT Step 2 of 2

Figure 59: C_ACCT Properties - Initial

Note: Required properties have a blue background. c)

Go to step 3 of 3 → Add the properties as you see below.


2010


69


BPC440

Figure 60: C_Acct Properties - with your additions

d) 7.

8.

After you enter in the properties above → Add a new dimension → OK.

In the C_ACCT dimension add the members in the 'LegalAppDimension' file on your virtual desktop C Drive in the BPC440_## folder. a)

Select C_Acct → Maintain dimension members.

b)

Go to your virtual desktop C Drive → BPC440 → BPC440_## → Files → LegalApp → Open the 'LegalAppDimension' file → Select sheet C_ACCT → The members should already be selected → Right click in the pre-selected area → Copy.

c)

In the Admin Console → Go to cell A2 of the C_ACCT Membersheet → Right click → Paste all members into the member sheet → Check to see if the data is in the correct columns such as account type, hierarchy data, and group → Process Dimension → Ok → Ok.

We'll use the RptCurrency dimension to capture currency data in the Legal Applicaiton. To be able to use it, add CURRENCY_TYPE and STORE_ENTITY to the properties of the existing RptCurrency dimension and enter the transaction currency member as shown below: a)

Select the RptCurrency dimension on the left → Maintain dimension properties on the right → Add the CURRENCY_TYPE and STORE_ENTITY as shown below:


70


2010

BPC440


Figure 61: RptCurrency Properties

b)

Modify dimension property → OK.

c)

In the Admin Console → On the left → Select RptCurrency → On the right → Select 'Maintain dimension members' →In your remote desktop C-Drive LegalApp dimensions sheet → Copy the preselected members from the RptCurrency sheet → Go back to the Admin Console → Go to cell A2 → Right click → Paste → Process Dimension → Ok → Ok.

Figure 62: RptCurrency Members

9.

Now let's create the Legal Application and call it the 'LEGALAPP'. Select the 'Consolidation type'. Add the following dimensions:


2010


71


BPC440

Dimension

Type

Secure

ConsGroup

Group

No

C_Acct

Account

No

C_Category

Category

Yes

C_Datasrc

Datasrc

No

Entity

Entity

Yes

Flow

Sub Table

No

IntCo

Intercompany

No

RptCurrency

Currency

No

Time

Time

No

Dimension

Type

Secure


72


2010

BPC440


Turn on all of the Business Rule tables except for Intercompany Bookings (we will use this in the IC Matching Application). Business rule tables can be turned on or off at any time. a)

Select Application on the left → Select 'Add a new Application' on the right → Enter name and description of LEGALAPP' → Go to Step 2 of 4 → Select the Consolidation Reporting Type → Go to Step 3 of 4.

b)

Confirm that the Planning application is the source (for the proposed dimensions) and the Rate and Ownership applications are selected (referenced) → Deselect Intercompany Bookings (this will be performed in the Matching application)

c)

Go to Step 4 of 4 → Deselect dimensions (to select dimensions before creating the application) and journals → 'Add a New Application'.

d)

Remove all existing dimensions and add the ones shown below:

Figure 63: Legal Application Dimensions

e)

Make both C_Category and Entity 'Secure' by selecting each one and pressing the 'Secured' button → Add a new Application → OK. Note: If you receive a message regarding journals, select ok.

10. Our business requirements call for us to resolve inter company differences in a separate application. Therefore, create the Inter Company Matching Application called 'ICMATCHING' Select the Reporting / Financial type. Include the following dimensions: Consgroup, C_Acct, C_Category, C_Datasrc, Entity, Flow, Intco, RptCurrency,Time.


2010


73


BPC440

Select the Business Rule tables for Currency Translation and Inter Company Bookings. Make C_Category and Entity secure. Note: It is also possible to do matching in the legal application depending on the business requirements. a)

Select 'Application' on the left → Select 'Add a new Application' on the right → Enter name and description of 'ICMATCHING' → Go to Step 2 of 4. Select the Financial Reporting Type → Go to Step 3 of 4 → Select LegalApp as the source application and confirm that the Rate application is selected (referenced). Select application options Currency Conversion and Intercompany Bookings → Go to Step 4 of 4 → Deselect dimensions (so you can select them yourself before creating the InfoCube) and journals → Add a New Application.

b)

Remove all existing dimensions and add the ones shown below:

Figure 64: IC Matching Application Dimensions

c)

Make both C_Category and Entity 'Secure' by selecting each one and pressing the 'Secured' button.

d)

Add a New Application → OK.


74


2010

BPC440


11. When you create a new Appset, it is good practice to process all of the dimensions. a)

Select the Dimension Library → Process Dimension → Select All Dimensions→ OK → OK.

Result Your Appset should look like this:

Figure 65: All Applications

Task 3: Allow access to the Applications and Tasks in security. Now we need to give ourselves access to the new applications and also, in this case, to all of the tasks. 1.

Give your user rights to all tasks in BPC by modifying the existing 'Full_Tsk' task profile. Give the Full_Tsk profile a description of 'All Tasks'. Select all three Admin functions and add all of the tasks for all of the interfaces. a)

In your BPC440_## appset → Open up 'Security' → Open 'Task Profiles' → Select 'Full_Tsk'.

b)

Select 'Modify task profile' → Enter a description of 'All Tasks'

c)

Select all three 'Admin' functions: System, Primary, and Secondary.


2010


75


d)

BPC440

Select Next → Select the drop down for 'View task by Interface' → Scroll through every 'interface' such as 'Analysis Collection' and when tasks appear in the lower left 'available' interface tasks' add them to the right 'Selected interface tasks' via the double right arrow button. Your result should look like this when you are done:

Figure 66: All Tasks

e)

Confirm that you added all of the available tasks by comparing your tasks in the 'selected interface tasks' to the list below:

Figure 67: Selected Interface Tasks

f)

Select Next → Next → Apply → OK.


76


2010

BPC440


2.

Add read/write access for both the Category and Entity type dimensions to all of your applications. Modify the existing 'Full_Mbr' member access profile. Add a description of 'All Members'. Caution: Do not type in the selections, use the system drop downs. Give read/write access to both of the secure dimensions for all members. Confirm the assignments of the profiles above to the Admin team. Confirm the assignment of your user id to the team as well . a)

On the lower left, open up Security and Member Access Profiles.

b)

Select the existing 'Full_Mbr' profile → Modify member access profile.

c)

Enter a description of 'All Members' and select Next.

d)

While you are on the 1st tab for 'ICMatching', set the member access as follows: Caution: Use the system drop downs to make your selections below, do not type them in because if you use the wrong case or enter ALL instead of [ALL] you will get an error message about member access)

Figure 68: IC Matching Member Access Profile (please use the 'dropdowns' to select the values, DO NOT TYPE THESE IN)

e)

Select the LegalApp tab and set the member access as follows:


2010


77


BPC440

Figure 69: LegalApp Member Access Profile

f)

Select the Ownership Application tab and set the member access as follows:

Figure 70: Ownership Application Member Access Profile

g)

Select the Planning tab → Confirm that Read and Write access to ALL members for the category and entity type dimensions is provided. .

h)

Select the Rate Application tab → Set the member access as shown below:

Figure 71: Rate Application Member Access Profile


78


2010

BPC440


i)

Confirm that the Admin team is assigned: → Select Next:

Figure 72: Member Access Profile - Team Assignment

j)

Select Next → Apply → Ok.

k)

Confirm that the two profiles are assigned to the ADMIN team: Open up Teams → Select ADMIN → Modify Team → Next → Add yourself if necessary → Next → Confirm your settings as you see below:

Figure 73: Security Team: BPC Access

l)

Select → Next → Apply → Ok.

m)

Set your appset to 'Available':


2010


79


BPC440

Select your appset on the upper left → On the upper right → Set application set status → Select Available if necessary → Update application set status. Note: Appsets are usually set to 'Unavailable' status by systems admins during non peak times for master data updates. When appsets are 'Unavailable' or 'Offline' no data can by written to its applications at that time. However, users can still 'read' the data in reporting. n)

Since you have created new applications, run the connection wizard to update your user's application list: → Select BPC440_## hypertext on the upper right

Figure 74: Access the Connection Wizard

o)

Connection Wizard: → Next → Use a different user and password → Enter your password → Next → Select your appset → Next → Finish → Confirm your appset is set to BPC440_## → Ok.


80


2010

BPC440


Task 4: Application Parameters Set the application parameters for the ICMatching and Legal applications from Web Administration. These settings control how the applications are used (similar to 'configuration settings' in ECC). There are quite a few however so don't forget that they are fully defined in the appendix. Note: Some of these will already have values. For, example if you selected 'currency translation' when you created ICMATCHING, then the FXTRANS web parameter will have a value of '1'. 1.

Set the application parameters for ICMatching as shown below and also make it a YTD application: a)

From the Admin Console → Available Interfaces → Interface for the Web → That takes you to the launchpad screen → Select Available interfaces (again) → 'Administration' (web) → and you end up in the Web Administration screen:

Figure 75: Web Administration

b)

Launch the 'Set Application Parameters' link. → Use the hypertext to set your Appset to BPC440_## → Set your Application to ICMatching (left click on the application name hypertext)→ Ok. (if you receive an error → Select the back arrow)


2010


81


BPC440

Figure 76: Web Action Pane

Below you can see some of the ICMatching parameters (the YTD setting is at the bottom):

Figure 77: IC Matching Parameters

c)

Set the YTDINPUT parameter to 'Yes' as shown below → Select 'Update' (near the top right) to save your settings. KeyID

Value


82


2010

BPC440


YTDINPUT

Yes

Note: Don't change any other parameters. 2.

From the BPC Web Administration, set the following application parameters for theLegalApp as shown: KeyID

Value

JRN_BALANCE

1

JRN_POST_OVERWRITE

Y

YTDINPUT

Yes

Note: JRN_POST_OVERWRITE is set to Yes so that the system will retain the same journal id # if a posted journal is set to unposted and then back to posted. a)

Make sure your Appset is BPC440_## and the Application is the LegalApp.

b)

Set the parameters as shown above.

c)

Use 'Update' to save the parameters.

Result Note: We will be using the properties that begin with 'Org' in the consolidation of investments unit. However, here are the explanations on the 'Org' properties and a couple of others for now: •

•

•

•

Opening Balance: Enables the business rule table for balance carry forward. If you checked the copy opening option when you created the application, then this parameter will already have a value of '1'. Org_Accountlist: Member id’s of the ownership account dimension that store methods, %consolidation, and %ownership. These will appear in the dynamic hierarchy editor. Org_Accountdown: member id of the ownership account that specifies the Position of a consolidation entity within the group for example 90 will be used for 'parents'.. Org_intco: the 3rd party (external) member in the Intercompany dimension to which all ownership calculations are posted. Continued on next page

2010


83


• •

• •

• •

BPC440

Org_ownershipcube: name of the linked Ownership application. Org_parentproperty: property name in the Groups dimension to define the hierarchy used in the dynamic hierarchy editor. The Group property that will contain the legal rollup members. Ownership_App: the consolidation logic requires the Ownership application to be listed here as well. USElim: Allows the use of the business rule tables for US Eliminations. Note: US Elimination is an easy way to do one sided eliminations. The first to use it happened to be a US company! This can be used for sales and cogs eliminations for example. Validations: Allows the use of the validation business rule tables. YTD Input: This will cause the application to collect Year To Date (cumulative) data in the Fact tables. Note: All of the properties which begin with 'ORG...' are related to the Dynamic Hierarchy Editor.

84


2010

BPC440


Lesson Summary You should now be able to: • Identify the applications used in legal consolidation. • Create and maintain applications. • Identify when dependent applications are needed. • Select various business rules to meet your consolidation requirements. • Recite the four components of secutity.

2010


85


BPC440

Lesson: Dimensions, Properties, and Loading Master Data Lesson Overview This lesson covers the dimensions and properties that are relevant to consolidation. Loading master data will also be discussed and performed in the lab.


Identify what dimensions are used by which applications. Discuss the properties used by the various dimensions. Understand how properties are used in the consolidation process. Maintain dimensions.

Business Example You are in the build phase of your project and now you need to start work on the dimensions, properties, and the master data loading options.

Dimension Types

Figure 78: Dimension Types - Basics

86


2010

BPC440

Lesson: Dimensions, Properties, and Loading Master Data

Figure 79: Continued

Note: You cannot delete a dimension when it is being used by an application. A dimension is a category, such as Account, Entity, or Time, that usually contains a hierarchy of related members, creating parent, child, and sibling relationships among the members. Managing dimensions involves tasks such as creating new dimensions, defining members, and assigning properties. You manage dimensions in an application set using the Dimension Library. The dimensions in an application set's Dimension Library can be added to one or more applications in the application set. C,A,T,E are required in every Application. Measures appear in the user interface as a dimension, but it is a calculated value which provides period, YTD, and QTD values. Intercompany (I) is required for Intercompany Eliminations. You can also create additional dimensions as needed: U# = User defined dimension type. For each user defined dimension you create, the number (#) will be incremented. For example, U1, U2, U3, etc. Additional dimensions can be created as needed. However, the 10 dimension types are fixed. In the Current View in Excel for example, Measures also appears as a dimension but it isn’t really a dimension rather a system provided Periodic vs. ‘To Date’ view of the data. 'I' (Intercompany) is a required reference dimension for a Legal Application but not for a Financial Application. C, A, E, I can be referenced to other dimensions to provide validation of members which are property values in other dimensions. Category can be referenced to a Time type dimension. That means that the property 'Year' in the Category dimension must exist in the time dimension. Account can be referenced to another account type dimension. (the rate type property in the account dimension must exist as a member in the referenced dimension.) Entity can be referenced to a

2010


87


BPC440

Currency type dimension. (local currency in the entity dimension must exist in a currency dimension if it is referenced.) Intercompany can be referenced to an Entity type dimension. (Entities are property values in an Intercompany dimension). Member id’s can have up to 20 characters. ID’s cannot have spaces or any special characters except ‘.’ and ‘_’. ID’s must be unique per dimension. Descriptions are 60 characters and can have special characters and spaces. However, they cannot contain double quotes. Defining the right properties in a dimension support various functions from the user’s interface and make reporting much easier. In addition, properties are often critical components used to evaluate expressions in advanced script logic and business rules. Remember, the value you place in a member’s property may be used in an Excel report. Dimension Properties

Figure 80: Dimension Properties in General

Dimension properties are categories that are assigned to dimensions. Many of the properties are generic, such as ID and EvDescription, and others can be unique to a dimension, such as Scaling. These properties define the behavior of members within the dimension. It is best to have some idea of the properties each dimension requires in the design, but you can build the dimension without defining ALL the properties. They may always be added later in the design process. Based on their assigned type, dimensions are assigned default properties, some of which are required. You can add more properties to further customize your dimension members. The following are general dimension properties that are required for each dimension: •

88

CALC - a system-generated property that indicates calculated members. Required for Account, Entity, Time, Currency, Category, User-defined, Datasrc, Intercompany, and Subtables dimensions.


2010

BPC440


• • • •

• •

•

• • • • • • •

ACCTYPE - stores the account type indicator for balance or income statement account. Required for Account type dimensions. CURRENCY - stores the 'local' currency of the dimension. Required for Entity dimensions. ENTITY - indicates the structure of an organization. Required for Currency and Intercompany dimensions. EVDESCRIPTION - is a user-defined description for the property. Required for Account, Entity, Time, Currency, Category, User-defined, Datasrc, Intercompany, and Subtables dimensions. EVDESCRIPTION can be up to 60 characters and does not need to be unique. It cannot contain double quotation marks ("). This description appears in the language specified in My Settings within BPC Web. FLOW_TYPE - required for Subtables dimensions. HIR - which stores the hierarchy names associated with the member. Required for Account, Entity, Time, Currency, Category, User-defined, Datasrc, Intercompany, and Subtables dimensions. HLEVEL - which is a hidden, system-calculated hierarchy level of the dimension member. Required for Account, Entity, Time, Currency, Category, User-defined, Datasrc, Intercompany, and Subtables dimensions. LEVEL - indicates the level of the Time hierarchy. Required for Time dimensions. PERIOD - indicates the period of the Time dimension. Required for Time dimensions. REPORTING - is required for Currency dimensions. SCALING - indicates a scaling factor. Required for Account, User-defined, Datasrc, intercompany, and Subtables dimensions. RATETYPE - indicates the rate type for the Rate dimension. Required for Account dimensions. YEAR, which indicates the Year attribute for the Time dimension. Required for Time and Category dimensions. SOLVE_ORDER - which defines the order in which BPC solves calculated members when they intersect with other calculated members. SOLVE_ORDER determines the order in which the system evaluates and calculates dimensions, members, calculated members, custom roll ups, and calculated cells. BPC evaluates the member with the highest solve order first, and calculates it last. Zero is the highest priority.

When you create a new dimension from BPC, this will call the SAP Business Planning and Consolidation API (see the appendix) to create a new dimension (which will create the new InfoObjects). Properties will get created as new InfoObjects. (not including EVDESCRIPTION) Reference Dimensions

2010


89


BPC440

Figure 81: Reference Dimensions

Example 1: You can validate the RATETYPE property of the ACCOUNT dimension type by choosing any dimension of dimension type ACCOUNT as a reference dimension of ACCOUNT. This will ensure that the valid values of the RATETYPE property for ACCOUNT are valid members of the reference dimension you choose. The validation will occur for the “ID” of RATETYPE such as AVG, End of Month, Historical, Spot, etc. Example 2: You can validate the “YEAR” property of the CATEGORY dimension type by choosing any dimension of type TIME as a reference dimension. This will ensure that the YEAR property of the CATEGORY dimension has a valid value by checking the value against the “YEAR” property of the dimension type TIME that you select. Hierarchies

90


2010

BPC440


Figure 82: Modeling Hierarchies in BPC

It is natural to have hierarchies for dimensions such as entity and time where the need for rollups is common. Hierarchies also allow the use of multiple views from one dimension. For example the entity (such as Store) dimension can be used to view data by company code, plant, or region. Hierarchies are stored as SAP NetWeaver BW Hierarchies. The hierarchy property PARENTH# does not appear as a property via 'maintain dimension properties' but only as a column in the dimension member sheet. The naming convention is PARENT# where # is the number of the hierarchy such as 1,2, etc. The #'s must be sequential. The property name does not appear to the end user however. Parents are valid members. A member can only be assigned to one parent per hierarchy. Properties are like any other characteristic in BW, they have a maximum of 60 positions in the data base. However, you can create a property in Business Planning and Consolidation of more than 60 but BW creates it with 60 anyway. Also, BW makes it a display attribute only. Dimensions by Application

2010


91


BPC440

Figure 83: Dimensions by Application

92


2010

BPC440


Dimension member examples • •

• • • • • • • • • • •

Account examples include: Balance sheet, Income Statement, Cash Flow, and Validation Accounts. ICAccount consists of the normal account ids but may also have additional hierarchy roll-up ids as well for analysis purposes in the ICMatching application. Rate (Currency) examples include AVG, END and possibly others such as HIST. OwnAccount consists of ownership elimination methods as well as percent control and percent ownership. Flow examples include Opening, Increases, Decreases, Closing, Prior/Current period profit, Currency Translation, Ownership. Category examples include Actual, Plan, Budget, Forecast, Estimates. Entity examples include legal entities such as C1000 and groups such as H1, CG1, CG2. RateEntity examples include: Global. This is the entity type dimension of the Rate application. IntCo examples include I_C1000 so company C1000 has an alias (trading partner) IntCo I_C1000 etc. Time includes YEAR.PERIOD members such as 2008.JAN, 2008.FEB, and parents such as 2008.Q1, 2008.TOTAL. Group examples include: G_H1, G_CG1, G_CG2; In this case Group is being used for consolidation group id's. InputCurrency examples include: USD, EUR, etc. DataSrc is used to identify the origin of values for example: Input, MJ (Manual Journals), AJ (Automatic Journals), Elim (Consolidation Eliminations), etc.

Account Dimension

2010


93


BPC440

Figure 84: Account Dimension

Note: Each application can have only one Account-type dimension. • • • • • • • • • •

• •

ACCTYPE is required for account type dimensions and is used to control sign display and aggregation behavior in reporting. DIMLIST# properties are used as selection criteria in business rules. ELIMACC is used in the US Elimination process to identify 'plug' accounts. FORMULA can be used in any dimension to store dimension logic. GROUP is used to identify accounts as Profit & Loss (PL) or Balance Sheet (BS) accounts. IC_MATCH is used by the IC Matching logic. IS_INPUT is used for report filtering. RATETYPE is required in account type dimensions and is used to store AVG or END (for example) rate types for currency translation. SCALING is used to display values in thousands for example in formula based reports. SOLVEORDER is used to control the sequence of formula calculations. Instead of using the property however, you can just use SOLVEORDER key word in the dimension logic. STORED_CALC is a used defined identifier for whether the member is calculated via a formula or is a parent. VARIATION was used in 4.1 Microsoft version to ID thresholds for scorecards.

KPI examples could include gross margin, return on net assets, etc.

94


2010

BPC440


Figure 85: Account Type Property

You can only use the four delivered ACCTYPEs, you cannot create your own. The four Account types are: Flow Dimension: The flow type property is not shown below but is required in this dimension. Also, you need to have one member with the flow type of 'opening' and one with 'closing'.

Figure 86: Flow Dimension

2010


95


BPC440

This is the S – Subtable dimension which is used to break down the account activity or flow. For example, some accounts like fixed assets have a subtable dimension containing opening, additions, deletions, transfers, and ending balances. The subtable type dimension is important for writing business rules that require currency translation amounts to be calculated by account. Since the subtable information can be used for multiple accounts, it requires its own dimension. • • •

DIMLIST can be used as a selection criteria in business rules. FLOW_TYPE is used by the balance carry forward logic to id opening and closing flows. IS_INPUT is used in reporting.

Entity Dimension Note: The currencies assigned to the groups such as H1 and CG1-4 as well as E_CGx members are only used for reporting purposes and do not affect currency translation or eliminations.

Figure 87: Entity Dimension

Generally speaking, the Entity dimension contains the business units that are used to drive the business process. For consolidations this will be the legal entity in most cases. Depending on your application design, the Entity type can be an operating unit, a cost center, a geographic entity, etc. This dimension is normally used to supply the members that are used in the work status approval process.

96


2010

BPC440


Also, some of the members such as E_CG1 are linked to the consolidation groups such as CG1. •

• • • •

CURRENCY is a required property used to store the local or functional currency for each entity. If entity is referenced to a currency dimension, then currency property values can only be used if they exist as members in the linked currency dimension. ELIM is used by US Eliminations to identify which members to include via a 'Y' value. FX_TYPE can be used to select entity specific currency translation parameters in the business rule tables via the 'Entity FX Type' column. INTCO is used identity the trading partner ID. OWNER is used to store the domain\user ID for work status activity.

Intercompany Dimension: Entity is one of the properties. For example, I_C1000 is linked to C1000 in this dimension.

Figure 88: Intercompany Dimension

The Intercompany dimension defines the base members associated with the level at which intercompany balances are tracked in order to perform intercompany eliminations. •

ENTITY is a required property and is used to link the related entity member. Intco is normally referenced to the entity dimension. Then INTCO members can be thought of as trading partner ID's and are used carry out eliminations.

2010


97


BPC440

Category Dimension: You might know this one as 'Version'. A category member can be used for any year by the way. Year is a property so it can be used in reporting and perhaps planning scenarios in Excel where depending on the property value for year, a column may only be in read mode.

Figure 89: Category Dimension

The Category dimension defines the groupings in which you store information in your application. Typical categories would be Budget, Actual, Forecast, and so on. Any dimension that is assigned the type C is a Category dimension. Each application can have only one Category-type dimension. •

• •

•

•

CATEGORY_FOR_OPE can be used by the balance carry forward(BCF) program to use a target version that is different than the source. So instead of carrying forward actual to actual, carry forward actual to BCF_ACTUAL. COMPARISON is used in reporting. FX_DIFFERENCE_ONLY, FX_SOURCE_CATEGORY, RATE_CATEGORY, RATE_PERIOD, RATE_YEAR, STARTMTH are all used for currency translation simulations. OPENING_PERIOD is used to specify a month different than the prior month for balance carry forward. So instead of running BCF for 2010.JAN from 2009.DEC, you could feed 2009.NOV values to 2010.JAN. YEAR can be used in planning scenarios to control user input to the appropriate time frame based on the version. Otherwise any category member can be used for any time member.

Group Dimension

98


2010

BPC440


Figure 90: Group Dimension

Note: The 'Groups' dimension in Apshell is no longer used. •

•

•

•

•

CURRENCY_TYPE is used to identify whether a group member should be valued at the Group currency or is used to feed unconsolidated data in Local currency. ENTITY is used to identify the entity members which will be used for the group level elimination values. If this is filled with a valid entity member, and the STORE_ENTITY property is set to 'Y', the currency translation results will also be copied into this Entity. PARENT_GROUP is used to identify group members to be used in the dynamic hierarchy editor. This is specified in the web admin parameter 'ORG_PARENTPROPERTY'. STORE_ENTITY can be used to write elimination entries to different members. The results of currency translation can also be copied to the Entity ID in the Entity property above. STORE_GROUP_CURRENCY if set to 'N', currency translation results will only be written to group members.

Data Source Dimension

2010


99


BPC440

Figure 91: Data Source Dimension

• • • • • • • •

•

CONSO_TYPE can be used to limit a consolidation business rule to a certain datasrc via the 'group type filter' in the automatic adjustment details. COPYOPENING - Use a 'Y' to include it in BCF. DATASRC_STAGE is for multilevel staged consolidation, posting will be written to the member value stored in this property. DATASRC_TYPE is used to identify manual, automatic, and input members. Only 'A'utomatic can be used in business rules. ENABLEJRN can be used to limit dimension members in journal entries. IS_CONSOL is used identify members to include in elimination runs. IS_CONVERTED is used to identify members in currency translation. OPENING_DATASRC can be used to identify a member for BCF if different than the source. For example, use a special member to write the results of BCF to such as 'BCF_OPENING'. STYLE can be used for conditional formatting.

Time Dimension

100


2010

BPC440


Figure 92: Time Dimension

The Time dimension defines the units of time for your application and how those units aggregate. Any dimension that is assigned the type T is a Time dimension. Each application can have only one Time dimension. • •

• • •

LEVEL is used to designate the time granularity such as month, quarter, and year. MONTHNUM is used to identify the 1st month etc of the fiscal year such as 1 for jan and 2 for feb etc. If the 1st period of the fiscal calender is April, then its monthnum will be 1 and so forth. PERIOD is used for reporting purposes. TIMEID is either manually maintained or loaded automatically. Consolidation reads this property to determine the current vs. prior month. YEAR is used for reporting.

Some of the other dimensions include the O_ACCT dimension which will be covered in the Ownership discussion. The input currency dimension has all of your currencies and designates which ones are to be used for reporting as well as whether they are direct or indirect rates. The R_ACCT is used to provide an entity dimension for the rate application and so is merely a placeholder most of the time.

Loading Master Data 1. 2. 3.

2010

Automatically via BW Data Loads Automatically via BPC Data Imports Manually from the BPC Admin Console


101


BPC440

Figure 93: BPC Master Data Import Options

There are a number of ways to bring in master data to BPC in an automated fashion.

Figure 94: BPC Attribute and Text Import Package Selections

102


2010

BPC440


Attribute and text imports from BW Infoobjects can be filtered by values or hierarchy node selection, by language, by specific attribute, and by key date. Update options include overwrite and update. The format can be either internal or external. If the write mode is 'Overwrite', the master data in BPC will be replaced/overwritten by the new master data unless it has data in an InfoCube. Update mode will overwrite property values if the ID is the same, otherwise other master records will be kept and new records will be added. If internal format is selected, then no conversion routine will be used during the import. If external format is used, conversion routines will be carried during the import if there is one maintained for the characteristic. In the mapping section of the transformation file, BPC property names are on the left and the BW InfoObject technical name is on the right. In row 22, controlling area and cost center are concatenated together. This is an example of how to handle compounding. In the conversion file, a JavaScript replace method is used in row 2 to substitute an underscore when hyphens (-) are present in the incoming data. In row 3 of the conversion file, split and join methods are used to remove any spaces in the technical ID's of the incoming data records.

Figure 95: BPC Hierarchy Import Package Selections

This import package only supports overwrite mode, not update mode. Reading time and version dependent hierarchy data is supported. Writing time and version dependent data is not. If the source BW hierarchy includes external characteristics, those values will not be imported.

2010


103


BPC440

In the transformation mapping section, observe the source and target field names are identical on both sides of the equal sign since the same structure (UJN_S_HIER_NODE) is used for both. In the conversion file, the default CONVERSION tab is used to convert one or more BW hierarchy names to the corresponding BPC hierarchy. Processing Dimensions

Figure 96: Processing dimension from the member sheet

104


2010

BPC440


Figure 97: Process Dimensions

Processing a dimension will execute the following steps: • • • •

Validate Hierarchy. Validate Dimension member formulas. Update member data into BW. BW Attribute change run.

When you process a dimension, you can choose to process ‘from the member sheet’. This means that when you process a dimension, the values to save back to the master data of the SAP NetWeaver BW InfoObject are taken from the Excel sheet you currently have open on your client machine. If you do not select ‘from the member sheet’, it assumes you have already chosen to save the sheet to the server before processing and therefore the BW master data is updated from the sheet on the server. If you first save the new master data to the server, then you can 'process the dimension' and choose 'process members from server'.

2010


105


106


BPC440

2010

BPC440


Exercise 2: Maintaining Dimensions Exercise Objectives After completing this exercise, you will be able to: • Maintain dimension properties and members for the IC Matching Application. • Update dimension members from a BW Characteristic. • Modify the IC Matching application by adding your new dimensions.

Business Example Understanding your master data for consolidations is extremely important. You also need to know how to modify the dimensions when the need arises. In addition, it is also good to know how to change an existing application. In the task below we will sharpen our skills in this area by setting up the dimensions and properties for the ICMatching application as well as modifying the delivered (in your own appset) dimensions so they can be used for Legal Consolidations.

Task: Dimensions and Properties Now that we have our applications in place, we need to work on the Apshell dimensions and properties in order for the consolidation logic to work etc. So next, we'll learn how to update dimension members manually and also via automatic imports directly from BW Characteristics! Create the dimensions you need for IC Matching and add them to the application. Also, some of the properties for other dimensions will need to be modified (see below). In addition, set the Intco dimension to reference Entity. Reference dimensions allow validation to occur in cases where a member from one dimension is used as a property in another. 1.

Add 4 new members to the C_Datasrc dimension that we are going to need for visibility in the ownership eliminations. Add AJ_COI1 (consolidation of Investments) as a copy of AJ_SHARES. Use a description of 'Auto COI1'. Add two more with the # 2 and 3. Also add a new member for US Eliminations called AJ_USELIM with a description of 'US Eliminations'.

2.

In the Entity dimension, delete the FX_TYPE property values for C9000 and C4000 since we will not be using Entity specific currency translation. Our group currency this week is USD, so change all the groups and group level base members in H1 to USD.


2010


107


BPC440


3.

The delivered logic references two flow members that we need to add: ID

EVDescription

ParentH1

F_ARES

Prior Year Retained Earnings

F_TOP

F_RES

Net Income - Current Per

F_TOP

4.

The new ownership package requires additional O_Acct members to record proposed elimination methods for example.

5.

We need two new dimensions for the IC Matching application based on the assumption that we do not wish to share the existing account and datasrc dimensions. In the Admin Consol, create a new account type dimension called ICACCOUNT. Add the 'Pintco' property as a one position field and a Formula property with 500 characters. Use the dimension file for ICMatching on your desktop to copy in the members.

6.

Create a new datasrc type dimension called ICDATASRC. Add the three properties and # of positions as shown below: Property

Width

IS_CONVERTED

1

IC_ORIGINE

2

DATASRC_TYPE

1


108


2010

BPC440


7.

Create a new dimension called TRNCURRENCY to allow the calculation of currency translation vs. other differences. Include a property called Currency.

8.

Add the new transaction currency to the ICMatching Application along with the ICAccount and ICDatasrc dimensions. Remove the C_Acct and C_Datasrc dimensions. Note: Obviously, it would be better to prepare the dimensions and then create all of your applications in real life. However, we wanted you to realize how you might re model an existing application.

9.

We just have a few currencies we need in the TRNCURRENCY dimension, which you could easily enter in manually. However, the steps you are about to follow are intended as a teaching aid for when you need to load much larger amounts of master data automatically. So let's take this opportunity to learn how to automatically load master data from a BW Characteristic. In order to import data from a BW characteristic, we will carry out these steps: - Add the IMPORT_MASTER data manager package in ICMATCHING. - Load the new TrnCurrency Dimension from the BW characteristic 'TRANCUR'. - Use a transformation file to map the CURRENCY property to the ZCUR00 attribute.. - Validate the data after the load from the Admin Console when you are done.

2010


109


BPC440

Solution 2: Maintaining Dimensions Task: Dimensions and Properties Now that we have our applications in place, we need to work on the Apshell dimensions and properties in order for the consolidation logic to work etc. So next, we'll learn how to update dimension members manually and also via automatic imports directly from BW Characteristics! Create the dimensions you need for IC Matching and add them to the application. Also, some of the properties for other dimensions will need to be modified (see below). In addition, set the Intco dimension to reference Entity. Reference dimensions allow validation to occur in cases where a member from one dimension is used as a property in another. 1.

2.

Add 4 new members to the C_Datasrc dimension that we are going to need for visibility in the ownership eliminations. Add AJ_COI1 (consolidation of Investments) as a copy of AJ_SHARES. Use a description of 'Auto COI1'. Add two more with the # 2 and 3. Also add a new member for US Eliminations called AJ_USELIM with a description of 'US Eliminations'. a)

Open the C_Datasrc member sheet: In the Admin Console → Select the Dimension Library → C_Datasrc Dimension → Maintain dimension members.

b)

Copy the row with AJ_SHARES → Highlight the 4 rows under AJ_SHARES → Right click → Insert copied cells → Name the 4 new members 'AJ_COI1', 'AJ_COI2', 'AJ_COI3', 'AJ_USELIM'→ Use a description of 'Auto COI#' for the first 3 and 'US Elimination' for the fourth → Process Dimension → OK → OK.

In the Entity dimension, delete the FX_TYPE property values for C9000 and C4000 since we will not be using Entity specific currency translation. Our group currency this week is USD, so change all the groups and group level base members in H1 to USD.


110


2010

BPC440



3.

a)

In the Entity dimension: 'Maintain dimension members' → Delete the FX_TYPE property values for C9000 and C4000 .

b)

Since USD will be the group currency, we need to change every group and E_CGx group level member to USD: Change the currency to USD for: H1, CG1-4, E_H1, and E_CG1-4 → Process Dimension → OK → OK Note: The assignment of currency to groups and group level members is for reporting only. It does not affect currency translation.

The delivered logic references two flow members that we need to add: ID

EVDescription

ParentH1

F_ARES

Prior Year Retained Earnings

F_TOP

F_RES

Net Income - Current Per

F_TOP

a)

Select the Flow Dimension → Maintain dimension members → Goto row 53 → Add the two members you see above → Process dimensions → Ok → Ok.


2010


111


4.

5.

BPC440

The new ownership package requires additional O_Acct members to record proposed elimination methods for example. a)

Goto your remote computer desktop → Documents → My documents → C-Drive → BPC440 → BPC440_## → Files → Ownership → Ownership Dimensions → Copy the preselected members for O_ACCT.

b)

Add the new 'Ownership' account members: Select the O_Acct dimension → Maintain dimension members → paste the new members into A9 from the Ownership Dimensions file in your Ownership folder → Process Dimensions → Ok.

We need two new dimensions for the IC Matching application based on the assumption that we do not wish to share the existing account and datasrc dimensions. In the Admin Consol, create a new account type dimension


112


2010

BPC440


called ICACCOUNT. Add the 'Pintco' property as a one position field and a Formula property with 500 characters. Use the dimension file for ICMatching on your desktop to copy in the members. a)

Select the Dimension Library on the upper left → 'Add a new Dimension' on the upper right → Use a name and description of ICACCOUNT → Go to Step 2 of 3. Select dimension type 'A-Account' → Do not select a reference dimension → Go to Step 3 of 3. Add the following properties with the lengths as shown below (PINTCO is used for filtering in reports) → Add a new dimension → OK.

Figure 100: IC Account Properties

6.

b)

On the left: Select the ICAccount dimension → 'Maintain Dimension Members' on the right → Use the Matching Dimensions file in the Matching folder on the C-Drive of the remote desktop in your BPC440_## folder to copy the members into cell A2.

c)

Process Dimension → Select OK → OK.

Create a new datasrc type dimension called ICDATASRC. Add the three properties and # of positions as shown below: Property

Width

IS_CONVERTED

1

IC_ORIGINE

2

DATASRC_TYPE

1


2010


113


a)

BPC440

In the Admin Consol: Select the Dimension Library on the upper left → 'Add a new Dimension' on the upper right → Use a name and description of ICDATASRC →Go to Step 2 of 3 → Select dimension type 'D - Datasrc' → Go to Step 3 of 3 → add the following properties with the lengths as shown below → Add a new dimension → Ok.

Figure 101: IC Datasrc Properties

b)

Select the ICDatasrc Dimension → 'Maintain Dimension Members' → Goto the IC Matching dimensions file on the C Drive→ ICDatasrc sheet → Copy the pre selected data → In the member sheet → Single left click on cell A2 → Right click → Paste → 'Process Dimension' → Select OK → OK.


114


2010

BPC440


Figure 102: IC Datasrc Members (your properties may appear in a different order)

7.

Create a new dimension called TRNCURRENCY to allow the calculation of currency translation vs. other differences. Include a property called Currency. a)

Select the Dimension Library on the upper left → 'Add a new Dimension' on the right → Enter a name and description of 'TRNCURRENCY' → 'Go to Step 2 of 3'

b)

→ Select dimension type 'U - User Defined' → Go to Step 3 of 3 → Add a property 'CURRENCY' → Enter a length of 3 positions → Add a new Dimension → OK.

c)

Add a new member so the dimension can be added to the ICMatching Application: Select TRNCURRENCY → Maintain dimension members → Enter: T_ALL id and description of: 'All transaction currencies' → Process dimensions → Ok → Ok.

d)

Let's check to see if the Appset is still available: On the upper left → Select your appset → On the upper right → Select 'Set Application Set Status' → Available → Update Application Set Status.


2010


115


8.

BPC440

Add the new transaction currency to the ICMatching Application along with the ICAccount and ICDatasrc dimensions. Remove the C_Acct and C_Datasrc dimensions. Note: Obviously, it would be better to prepare the dimensions and then create all of your applications in real life. However, we wanted you to realize how you might re model an existing application. a)

Let's adjust the ICMatching Application by changing it's dimensions. In the Admin Console → Select the ICMatching Application on the left → On the right select 'Modify application' → Remove all of the existing dimensions and replace them with the ones shown below:

Figure 103: IC Matching Revised Dimensions

Note: You may receive a message regarding journals, select OK and continue. b) 9.

Make the category and entity type dimensions 'secure' → Modify Application → OK.

We just have a few currencies we need in the TRNCURRENCY dimension, which you could easily enter in manually. However, the steps you are about to follow are intended as a teaching aid for when you need to load much larger amounts of master data automatically. So let's take this opportunity to learn how to automatically load master data from a BW Characteristic. In order to import data from a BW characteristic, we will carry out these steps: Continued on next page

116


2010

BPC440


- Add the IMPORT_MASTER data manager package in ICMATCHING. - Load the new TrnCurrency Dimension from the BW characteristic 'TRANCUR'. - Use a transformation file to map the CURRENCY property to the ZCUR00 attribute.. - Validate the data after the load from the Admin Console when you are done. a)

From the Admin Console: Select available interfaces → 'Interface for Excel' → Select appset: BPC440_## and the ICMATCHING application:

Figure 104: Accessing Excel

b)

Select 'Connection Wizard' → Next → Use a different user and password → Next → Select BPC440-## → Next → Finish → Ok → Planning and Consolidation → Goto eData → Organize package list → Right click in the yellow area → Add package.


2010


117


BPC440

Figure 105: Add Package

c)

Select the drop down to 'View All Process Chains' → Goto the App Group 'Business Planning and Consolidation: System' → Select: /CPMB/IMPORT_IOBJ_MASTER' → 'Select' → Enter name and description of 'IMPORT_MASTER' → Check both the Admin and User Package task type:

Figure 106: Select Process Chain

d)

Add → Save → Ok.

e)

Create a Transformation File: Goto eData → More → New Transformation File → In the mapping section → Enter the data as shown below:


118


2010

BPC440


Figure 107: Transaction Currency Transformation

f)

Run a simulation and save the sheet: Goto eData → More → Validate and Process Transformation File → Select Data type: Master data / text from NW BW InfoObject → Select the drop down for an InfoObject → Search on ZTRANCUR:

Figure 108: Select InfoObject


2010


119


g)

BPC440

Select ZTRANCUR → OK → Make your selections as you see below:

Figure 109: Simulate Import

h)

Save → Enter 'TRANCUR' for the file name → Save → View the result via the 'Output File' → Cancel.


120


2010

BPC440


Figure 110: Simulation Result

i)

Import the master data: Go Home → Manage data → Run a package → IMPORT_MASTER → Run → Use the drop down to select the ZTRANCUR characteristic → Update → Internal Format:

Figure 111: Import Master

j)

Select the 'Set Selection' button → Goto the Language tab → Confirm that the Short Text radio button is selected: Continued on next page

2010


121


BPC440

Figure 112: Set Selection

k)

Select OK → Next → Make your selections like the ones below:

Figure 113: Run Package

l)

Finish → OK → View Status → Double click the log → close all the pop-ups when done:


122


2010

BPC440


Figure 114: View Status

m)

Confirm that the import was successful by viewing the member sheet: Goto the Admin Console → Select the Trncurrency Dimension → Maintain dimension members → You should have 3 records:

Figure 115: Transaction Currency Membersheet

2010


123


BPC440

Lesson Summary You should now be able to: • Identify what dimensions are used by which applications. • Discuss the properties used by the various dimensions. • Understand how properties are used in the consolidation process. • Maintain dimensions.

124


2010

BPC440

Lesson: Consolidation Logic

Lesson: Consolidation Logic Lesson Overview In this lesson we will go over the system constants and default logic used for consolidation projects.


Explain how to use the three types of logic. Understand the architecture of Consolidation tasks. Use default logic and system constants for your consolidation project. Use script logic to create balancing adjustments.

Business Example You are implementing SAP BusinessObjects Planning and Consolidation and you need to know how to use logic to carry out consolidation tasks.

Types of Logic From an overview perspective, there are three types of logic to consider.

Figure 116: Types of Logic

You can use worksheet formulas and macros to create a convenient launch pad to run jobs and do analysis of the results.

2010


125


BPC440

Figure 117: Worksheet Functions and Commands

You can use Excel formulas in BPC workbooks as well as BPC 'MNU' commands, and 'EV' functions.

Figure 118: Dimension & Script Logic

126


2010

BPC440


Dimension member formulas give you the ability to define very powerful MDX formulas for calculating Account dimension members for example. Dimension member formulas are defined at the Application Set level, thus they are valid across all applications which use the dimension. Script logic is defined within each application and is used to calculate data and to run abap programs. Calculations defined for a specific member ID creates base level data in the application. This is proprietary SQL logic not Microsoft SQL.

Figure 119: The Architecture of Consolidation Tasks

The purpose of each logic file

2010

File

Purpose

Calcaccount.lgf

Calculate cash flow, or other reclassifications.

Consolidation.lgf

Intercompany eliminations, Consolidation of Investments. Using the consolidation methods, consolidation rule formulas, and automatic adjustment details business rules.

Copy_Opening.lgf

Balance Carry Forward

Validation.lgf

Validate Assets = Liabilities + Owners Equity for example.


127


• • • •

BPC440

Fxtrans.lgf

Currency translation of Local to Group currecny.

Allocation.lgf

Managerial consolidations.

ICData.lgf

Calculating partner data.

ICBooking.lgf

Booking inter company differences.

ICElim.lgf

US Elimination. Using the US Elimination business rule table. Non ownership elimination scenario.

// denote comments. '*' indicates executable lines of code. No '.' at the end of statements. '#' is used in MDX statements to denote the receiver of the calculation.

You will have two files for each script logic you create: • •

.LGF' - an ASCII file that you use to create/edit your logic calculations and is accessed through the Script Logic editor in the Admin Console. .LGX - the compiled logic file. Created by the system when you validate and save your logic. This is an executable version of the logic. You can use the script logic tester in UJKT to see this. The compiled file is without comments and it converts system constants.

Default logic is heavily used in Business Planning and Consolidation.

128


2010

BPC440


Figure 120: Default Logic and System Constants

Default logic is a special logic statement that is executed on every writeback to an application. All logic in Default.LGF is run after data is sent. Having all of your logic in the Default.LGF logic file might become unmanageable however. Therefore you can create other logic files, such as FXTrans.LGF for foreign currency translation and use an INCLUDE statement in the default logic to execute it real-time rather than having to run a separate batch process. Hint: Use transaction code 'UJKT' to do logic debugging! Note: The NetWeaver logic files can be accessed by using the t-code UJFS. Note: Note: If you change the code in a logic file, you must validate and save that file before the changes will be reflected in any other logic file that references it. Here are the NetWeaver rule statements that are available. You can access the definitions of each one by going to www.help.sap.com SAP Business User → EPM Solutions → Business Planning and Consolidation → SAP BPC 7.0, Version for SAP NetWeaver → Open → Application Help → English (for example)→ Business calculations → Logic → Voila!. *ADD / *ENDADD *BEGIN / *END *FOR / *NEXT

2010


129


BPC440

*FUNCTION / *ENDFUNCTION *SUB( ) / *ENDSUB *INCLUDE *REC *RUN_ALLOCATION *SELECT *SELECTCASE / *ENDSELECT *WHEN / *ENDWHEN *XDIM_MEMBERSET *XDIM_ADDMEMBERSET *XDIM_MAXMEMBERS *COMMIT Let's consider the components of script logic.

Figure 121: SQL Script Logic: Components

Scoping

Figure 122: Scope: What Data Region to Include

The When Statement

130


2010

BPC440


Figure 123: The *WHEN Statement

The Record Statement

Figure 124: The *REC (record) Statement

Note: Always code in upper case. When data is entered into the PL, the following logic would perform a 'write' into the appropriate BS account and flow. The logic below includes the generic Apshell names. When you validate it in the transaction code UJKT (more in a moment), you can view the code using your own naming conventions. Note: The logic samples below are NW examples. The code you use will depend on your business requirements. A good way to test the default logic is to use a simple input template. Since the default logic is run on a real time basis whenever data in input, you can see the results right away.

2010


131


BPC440

Figure 125: Copy PL to BS Results

Depending on your business requirements, you may need to use various balancing algorithms. F_ERR - Flow Error F_999 - Closing F_100 - Opening F_120 - Additions F_140 - Reductions F_RES - Current Period Net Income F_900 - Current Period Variation

Figure 126: Copy PL to BS Compiled Logic in UJKT

132


2010

BPC440


Figure 127: Copy 'PL Profit to BS' Logic with ApShell naming

Wnen you validate the default logic in UJKT, the system displays the logic without comments and also with the names from the system constants file. Note: UJKT is an SAP transaction code or shortcut on the BW Server. The illustration below shows a simple test of the balancing logic:

Figure 128: Balancing Logic - Result

2010


133


BPC440

Figure 129: Sample Balancing Logic with Apshell Naming

Here is the balancing logic in compiled form: [FLOW].[#F_ERR] =IIF([C_ACCT].CURRENTMEMBER.PROPERTIES("DIMLIST1")="L1_E",[FLOW].[F_999]-[FLOW].[F_100][FLOW].[F_120]+[FLOW].[F_140],0) [FLOW].[#F_900] =IIF([C_ACCT].CURRENTMEMBER.PROPERTIES("DIMLIST1")="L1_V",[FLOW].[F_999]-[FLOW].[F_100][FLOW].[F_120]+[FLOW].[F_140],0) You may also want to consider using some type of indicator that Validation needs to be executed:

Figure 130: Validation 'Counter' Logic in UJKT and the result of a data send (for example the 125 was sent)

134


2010

BPC440


Once the Consolidation User sees the validation account with a non zero value, they would know to run the Validation package which performs customer derived validation checks and sets the validation account back to zero. Note: The validation package will be discussed later in the course material. There will also be an exercise on it.

Figure 131: Run the Validation Package - Result

2010


135


BPC440

More on Consolidation Logic

Figure 132: Consolidation Currency and Elimination Logic (example)

Note: Currency translation code was added to the delivered logic to produce the above example. Currency translation into one of the groups such as G_H1 needs to be run before the consolidation program. The MDXLIB.LGF file includes the explanation and examples of SAP BusinessObjects Planning and Consolidation 7.0, version for NetWeaver MDX. Dimension constants in SAP BusinessObjects Planning and Consolidation version for Netweaver are no longer needed, as the pre-defined DIM KEYWORDS (for example: %TIME_DIM% could be used for holding the actual name of time type dimension) are in place for Business Planning and Consolidation, but other user defined constants can still be used. System Constants System Constants files for Legal Consolidation is used not only to identify dimension names but also to provide members for the default logic.

136


2010

BPC440


Figure 133: System Constants (example)

Script Debugger Hint: To see the system constants: From the BW Server Goto transaction code UJFS → Enter your appset → F8 → Webfolders → AppSet → System Library → Logic Library. The main purpose of system constants is to identify custom dimension names so that the other delivered logic will still work. For consolidations you also use the system constants to: • • •

2010

Identify custom flow dimension id's. Identity the balance sheet account to pass earnings from the income statement. Identify the account member (valrun in this example) for the validation logic to write out of balances to.


137


BPC440

Figure 134: Script Debugger

To run the script debugger go to the BW Server and enter transaction code SE38 and run program: UJK_SCRIPT_LOGIC_TESTER. Enter the appset, application, user id, data region if applicable, your logic goes on the lower left and the output when you validate (reads the code, parks it on the right), execute (writes records), or simulate (does not write records) shows up on the lower right. When you select your code via the 'Script File Location' for example, it will appear in the lower left. Hint: To access the ABAP code from UJKT: • • • • •

138

Enter the script logic in the lower left. Validate. Enter in dimension member restrictions. Enter '/H' into the command field and press enter on your key board. Select Execute and you should now be in the ABAP debug screen.


2010

BPC440


Exercise 3: Consolidation Logic Exercise Objectives After completing this exercise, you will be able to: • Understand the default logic required for Legal Consolidation. • Identify what the System Constants do and when you may need to change them. • Realize that every consolidation package has associated logic files.

Business Example Planning and Consolidation comes with logic that you may need to adjust to meet your specific business requirements. So you need to know that you can access the standard files via UJFS, what the logic does, and how to correctly modify it when necessary.

Task 1: LegalApp System Constants Apshell is delivered with dimension names that need to be mapped to the names used in the delivered logic files. The system constants file does this mapping. 1.

Copy the Legal Application system_constants code from your remote server into a file called SYSTEM_CONSTANTS.LGF in your Legalapp.

Task 2: LegalApp Default Logic We will use the default logic to run the system constants mapping as well as to do some balancing. Copy in the provided default logic for your LegalApp. You will find it on the remote desktop C Drive in the BPC440_## folder. In the Admin Console for the LegalApp, copy the logic into the existing default logic file, validate, and save it. Take a look at the logic and do a spot check to see if it matches up with the system constants file you just uploaded. Then use the provided input template and run a couple of simple tests to make sure the logic works. 1.

Let's access the default logic file from the C Drive and copy it on to your clipboard.

2.

Paste the logic into your LegalApp default logic file, validate, and save it::


2010


139


3.

BPC440

Optional: Let's do some testing. In the Legal Application, go to BPC for Excel, Input Data and open up the provided EVDRE input template. Note: EVDRE stands for Everest Dynamic Range Exchange and is heavily used for both data input and reporting.

4.

Test the logic by sending a PL value first, and then try the balancing logic. Note: When selecting Consgroup and Entity members, switch the 'data view' to Hierarchy if necessary. Also ignore the warning regarding 'a member could not be found'.

Task 3: Consolidation Logic etc Now that we have the system constants and default logic in place, let's set up the script logic files for the LegalApp and ICMatching applications so we can carry out validation, currency translation, etc. While we are at it, we'll also set up the allocation logic in the planning application and we will bring in the system constants code for ICMatching from your remote desktop C Drive in the BPC440_## folder. 1.

The files to perform consolidation activities are located in UJFS on the BW Server however, we will copy and paste from the BPC440 folder on your remote computer C Drive.

Result The Applications in your Admin Console should look like the screen shot below. Notice that all of the consolidation tasks have a logic file associated with them: • • • • • • • • •

Reclassification will use the CALCACCOUNT file. Elimination will use the CONSOLIDATION file. Currency translation will use the FX TRANS file. Allocation will use the ALLOCATION file. Balance carry forward will use the COPYOPENING file. The two IC Matching tasks will use ICDATA and ICBOOKING. Data validation will use the VALIDATION file. US Elimination will use the ICELIM file. Also, dimension name and member name mapping is achieved via the SYSTEM_CONSTANTS files and the DEFAULT logic files cause logic to run on a real time basis.


140


2010

BPC440


Figure 135: Logic Results

2010


141


BPC440

Solution 3: Consolidation Logic Task 1: LegalApp System Constants Apshell is delivered with dimension names that need to be mapped to the names used in the delivered logic files. The system constants file does this mapping. 1.

Copy the Legal Application system_constants code from your remote server into a file called SYSTEM_CONSTANTS.LGF in your Legalapp. a)

Open the system constants file from your remote desktop and copy the code. In your remote computer → Start → Documents → My Documents → C-Drive → BPC440 → BPC440_## → Files → Legal → System_Constants.lgf → Open → Copy all the code.

b)

In the Admin Console, go to your LegalApp → Script Logic → Create new logic → Enter 'SYSTEM_CONSTANTS' → OK → Paste in the script → Validate and Save → Ok.

Figure 136: System Constants - Legal Application


142


2010

BPC440


Task 2: LegalApp Default Logic We will use the default logic to run the system constants mapping as well as to do some balancing. Copy in the provided default logic for your LegalApp. You will find it on the remote desktop C Drive in the BPC440_## folder. In the Admin Console for the LegalApp, copy the logic into the existing default logic file, validate, and save it. Take a look at the logic and do a spot check to see if it matches up with the system constants file you just uploaded. Then use the provided input template and run a couple of simple tests to make sure the logic works. 1.

Let's access the default logic file from the C Drive and copy it on to your clipboard. a)

2.

In your remote computer → Start → Documents → My Documents→ C - Drive → BPC440 → BPC440_## → Files → Legal → Select the 'NW Legal Default Logic.LGF file' → Right click → Open with Notepad → Copy the contents.

Paste the logic into your LegalApp default logic file, validate, and save it:: a)

In the Admin Console → Open up Applications → LegalApp → Script Logic → Default Logic → Control-V → Validate and Save → Ok. Note: Note: if the system did not create a default logic file: Select Script Logic → Create new logic → Enter: DEFAULT → OK.


2010


143


3.

BPC440

Optional: Let's do some testing. In the Legal Application, go to BPC for Excel, Input Data and open up the provided EVDRE input template. Note: EVDRE stands for Everest Dynamic Range Exchange and is heavily used for both data input and reporting. a)

In the Admin Console → Select 'Available Interfaces' on the lower right → 'Interface for Excel' → If necessary, select the BPC440_## Appset and LEGALAPP:

Figure 137: Accessing the Interface for Excel

4.

b)

Select Connection Wizard → Next → Use a different user and password → User: CPM-## Password: training → Next → Select BPC440-## → Next → Finish → Ok.

c)

Open the provided BPC440 Logic Test input template and save it to your application: Goto the 'Office Button' (upper left) → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → BPC440 Logic Test → Open → Select 'Planning and Consolidation' → eTools → Save Dynamic Template→ Company → Save.

Test the logic by sending a PL value first, and then try the balancing logic. Note: When selecting Consgroup and Entity members, switch the 'data view' to Hierarchy if necessary. Also ignore the warning regarding 'a member could not be found'. Continued on next page

144


2010

BPC440


a)

Set your current view as you see below → Select the '+' sign to open the current view → Select the dimension CONSGROUP hypertext → Turn on the 'table data view' if it is on 'Dynamic Hierarchy' → Select NON_GROUP → Repeat this process for the remaining dimension members (do not type in the members!) → eTools → Expand All → Clear input → Ok.

Figure 138: Logic Test Current View

b)

Enter 125 for 30110000 and F_999 → Send Data (E13)→ Your status bar on the lower left will say 'Loading ... ' → Did the logic work as shown below?

Figure 139: Copy PL to BS Result


2010


145


BPC440

Flow Definitions F_ERR - Flow Error F_999 - Closing F_100 - Opening F_120 - Additions F_140 - Reductions F_RES - Current Period Net Income F_900 - Current Period Variation c)

For the 12110300 account (which has the L1_E Dimlist1 property) → Send 250 for F_999, 100 for F_100, 25 for F_120, and 50 for F_140.

d)

For the 21121000 account which has the L1_V Dimlist1 property → Send 250 for F_999, 100 for F_100, 25 for F_120, and 50 for F_140 → Do your results match the ones below? Note: For purposes of conveying concepts we are only doing the balance check for selected accounts in order to minimize the amount of data used in the training class. In reality, you may decide to do this for all balance sheet accounts depending on your business requirements.

Figure 140: Balancing Result

Task 3: Consolidation Logic etc Now that we have the system constants and default logic in place, let's set up the script logic files for the LegalApp and ICMatching applications so we can carry out validation, currency translation, etc.


146


2010

BPC440


While we are at it, we'll also set up the allocation logic in the planning application and we will bring in the system constants code for ICMatching from your remote desktop C Drive in the BPC440_## folder. 1.

The files to perform consolidation activities are located in UJFS on the BW Server however, we will copy and paste from the BPC440 folder on your remote computer C Drive. a)

In the Admin Console → Go to the LegalApp → Script Logic → 'Create new logic' → Enter CALCACCOUNT → OK → Copy and paste the script from the CALCACCOUNT file in your BPC440_## Legal folder → Validate and Save → OK.

Figure 141: CalcAccount Script Logic

Repeat the above steps for the LegalApp for the CONSOLIDATION file. The CONSOLIDATION.LGF should look like this: //For running legal consolidation *RUN_PROGRAM CURR_CONVERSION CATEGORY = %C_CATEGORY_SET% GROUP = %CONSGROUP_SET% TID_RA = %TIME_SET% RATEENTITY = GLOBAL *ENDRUN_PROGRAM *RUN_PROGRAM CONSOLIDATION Continued on next page

2010


147


BPC440

CATEGORY = %C_CATEGORY_SET% GROUP = %CONSGROUP_SET% TID_RA = %TIME_SET% *ENDRUN_PROGRAM Validate and Save → Ok. b)

Repeat the above steps in the LegalApp for COPY_OPENING, ICELIM and VALIDATION. (FXTRANS will already be there)

c)

Also in the LegalApp: Open the FXTRANS.LGF file → Copy the code from the FXTRANS file to replace the existing code→ Validate and Save. *RUN_PROGRAM CURR_CONVERSION CATEGORY = %C_CATEGORY_SET% CURRENCY = %RPTCURRENCY_SET% TID_RA = %TIME_SET% RATEENTITY = GLOBAL ENTITY = %ENTITY_SET% *ENDRUN_PROGRAM

d)

Go to the ICMatching Application → Script Logic → Create new logic → Enter ICDATA → OK → Copy and paste the script from the ICData file on the C Drive in the BPC440 folder for ICMatch → Validate and Save → OK. Modify your code to match the code below: *RUN_PROGRAM ICDATA CATEGORY = %C_CATEGORY_SET% CURRENCY = %RPTCURRENCY_SET% DATASRC = INPUT TID_RA = %TIME_SET% ENTITY = %ENTITY_SET% TYPE = I *ENDRUN_PROGRAM

e)

Repeat this process for the ICBOOKING file. Modify your code to match the code below: *RUN_PROGRAM ICBOOKING CATEGORY = %C_CATEGORY_SET% CURRENCY= %RPTCURRENCY_SET% TID_RA = %TIME_SET% ENTITY = %ENTITY_SET% *ENDRUN_PROGRAM Continued on next page

148


2010

BPC440


f)

In the IC Matching Application: Open the FXTRANS.LGF file → Copy the code from the FXTRANS file in the 'IC Match' folder to replace the existing code → Validate and Save. *RUN_PROGRAM CURR_CONVERSION CATEGORY = %C_CATEGORY_SET% CURRENCY = %RPTCURRENCY_SET% TID_RA = %TIME_SET% RATEENTITY = GLOBAL ENTITY = %ENTITY_SET% *ENDRUN_PROGRAM

g)

Go to your virtual desktop → C Drive → BPC440 → BPC440_## → Files→ ICMatch → Open the SYSTEM_CONSTANTS.LGF file → Copy. → In the IC Matching Application → 'Script Logic' → 'Create new logic' → Enter SYSTEM_CONSTANTS → Ok → Paste via Ctrl-V → OK → Validate and Save → Ok.

h)

We want the system constants to be accessed every time data enters the application. So 'include' it in the default logic: Open the IC Matching default logic file → Enter: *INCLUDE SYSTEM_CONSTANTS.LGF → Validate and Save → Ok.

i)

Go to the Planning Application → Script Logic → Open the Allocation.lgf → Copy and paste the script from the Planning folder Allocation file on your C-Drive→ 'Validate and Save' → Ok. Note: We will be using the allocation logic only in the planning application. However, the process would be the same if it were used in consolidation as well.

j)

In addition, please confirm the purpose of each set of logic: File

Purpose

Calcaccount.lgf

Calculate cash flow, or other reclassifications.

Consolidation.lgf

Intercompany eliminations, Consolidation of Investments.

Copy_Opening.lgf



2010


149


BPC440

Validation.lgf

Validate Assets = Liabilities + Owners Equity for example.

Fxtrans.lgf

Currency translation.

Allocation.lgf

Managerial consolidations.

ICData.lgf

Calculating partner data.

ICBooking.lgf

Booking differences.

ICElim.lgf

US Eliminations.

Result The Applications in your Admin Console should look like the screen shot below. Notice that all of the consolidation tasks have a logic file associated with them: • • • • • • • • •

Reclassification will use the CALCACCOUNT file. Elimination will use the CONSOLIDATION file. Currency translation will use the FX TRANS file. Allocation will use the ALLOCATION file. Balance carry forward will use the COPYOPENING file. The two IC Matching tasks will use ICDATA and ICBOOKING. Data validation will use the VALIDATION file. US Elimination will use the ICELIM file. Also, dimension name and member name mapping is achieved via the SYSTEM_CONSTANTS files and the DEFAULT logic files cause logic to run on a real time basis.


150


2010

BPC440


Figure 142: Logic Results

2010


151


BPC440

Lesson Summary You should now be able to: • Explain how to use the three types of logic. • Understand the architecture of Consolidation tasks. • Use default logic and system constants for your consolidation project. • Use script logic to create balancing adjustments.

152


2010

BPC440

Unit Summary

Unit Summary You should now be able to: • Identify the applications used in legal consolidation. • Create and maintain applications. • Identify when dependent applications are needed. • Select various business rules to meet your consolidation requirements. • Recite the four components of secutity. • Identify what dimensions are used by which applications. • Discuss the properties used by the various dimensions. • Understand how properties are used in the consolidation process. • Maintain dimensions. • Explain how to use the three types of logic. • Understand the architecture of Consolidation tasks. • Use default logic and system constants for your consolidation project. • Use script logic to create balancing adjustments.

2010


153

Unit Summary

154

BPC440


2010

BPC440

Test Your Knowledge


Legal Consolidation applications are referenced to a applications.

and

Fill in the blanks to complete the sentence.

2.

Legal Consolidations which perform COI requires which of the following applications? Choose the correct answer(s).

□ □ □ □ □ □ 3.

A B C D E F

Matching. Legal. Ownership. Rate Planning Cons Unit

Which of the following statements are true regarding Consolidation applications? Choose the correct answer(s).

4.

□

A

□

B

□

C

□ □ □

D E F

They require a time dependent Entity dimension to track subsidiary assignments to consolidations groups through time. The legal application is a consolidation / reporting type application. The ownership application is a non-reporting / ownership type application. The rate application is a non-reporting / rate type application. The planning application is a reporting / financial type application. The matching application is a reporting / financial type application referenced to a rate application.

The four required dimension types for any application include: Choose the correct answer(s).

□ □ □ □ □ □

2010

A B C D E F

Intco Dimension Category Account Time Entity Request Id


155

Test Your Knowledge

5.

BPC440

The Entity dimension has what consolidation related properties? Choose the correct answer(s).

□ □ □ □ □ 6.

A B C D E

Hierarchy Currency Formula Related Intco member Solve Order

In general, dimension properties are used for: Choose the correct answer(s).

□ □ □ □ □ 7.

A B C D E

Data selections in Input Templates Identifying destinations for the system to write to Data selections in Business Rules The execution of logic / programs Display in reports

Which of the following is true regarding the dimensions that applications use? Choose the correct answer(s).

8.

□

A

□

B

□

C

□

D

□ □

E F

The Rate app uses: Rate, Category, RateEntity, Time, Input Currency. The Legal app uses: Account, Flow, Category, Entity, Group currency. The Ownership app uses: OwnAccount, Category, Entity, Time, Flow. The Matching app uses: Account, Flow, Category, Entity, Intco, Time, Group, Datasrc. The Legal app, uses: Real time InfoCubes and DSO's. The ownership app uses: Request ID, Unit, and Time dimension.

Default logic performs the following functions: Choose the correct answer(s).

156

□

A

□ □ □

B C D

□ □

E F

Default logic references system constants which allow you to use different dimension names. Set fixed filters such as the fiscal year. Specifies the balance sheet account to record annual net income. Identifies the application for which you want to perform currency translation. Allows you to use different member id's for close and error flows. Records a value of 1 in a validation account if a difference is detected.


2010

BPC440

Test Your Knowledge

9.

The default logic uses *IF commands to do 'If Then' logic. Determine whether this statement is true or false.

□ □

True False

10. Business Planning and Consolidation uses an XDIMMEMBERSET to select data regions. Determine whether this statement is true or false.

□ □

True False

11. The default logic 'Validation and Increment' works as follows: Choose the correct answer(s).

2010

□

A

□

B

□

C

□ □

D E

□

F

Whenever the default logic is triggered, a incremental value of 1 is written to a designated account member. Then, that incremental value is written off via a manual journal entry. If a user tries to approve a data region and the validation account is not zero, they are prevented from advancing the work status. (Microsoft only) Validation must be run to clear the validation account. The designated validation account is specified in work status configuration. (Microsoft only) Every time validation is run, the validation account is incriminated by 1 so the user knows how many times validation was run.


157

Test Your Knowledge

BPC440

Answers 1.

Legal Consolidation applications are referenced to a Rate and Ownership applications. Answer: Rate , Ownership

2.

Legal Consolidations which perform COI requires which of the following applications? Answer: B, C, D Only the Legal, Ownership, and the Rate applications are required.

3.

Which of the following statements are true regarding Consolidation applications? Answer: B, C, D, F A. Subsidiary assignments to consolidations groups are tracked in the Ownership application. E. The planning application is a reporting / financial type application however it is not used for full blown legal consolidations. Note: Matching applications will be discussed later in the course in detail.

4.

The four required dimension types for any application include: Answer: B, C, D, E A and D. The four required dimension types for a reporting application are easily remember via the name 'CATE'!

5.

The Entity dimension has what consolidation related properties? Answer: A, B, D C and E. Dimension Formulas (and therefore 'solve order') are used primarily in the Account dimension.

158


2010

BPC440

Test Your Knowledge

6.

In general, dimension properties are used for: Answer: A, B, C, D, E For example, a business rule for currency translations will be configured to write translation differences to a specific account. Business Rules require the use of properties so that multiple accounts can be selected via their collective property. That way, business rule table entries can be minimized.

7.

Which of the following is true regarding the dimensions that applications use? Answer: A, C, D B. Group Currency is not a dimension. E. InfoCubes and DSO's are not dimensions. Infocubes have dimensions (which can contain one or more characteristics.) F. Request id's are not dimensions in BusinessObjects Planning and Consolidation but they are in an InfoCube.

8.

Default logic performs the following functions: Answer: A, C, D, E B. None of the logic sets fixed filters. F. The default consolidations logic adds a value of 1 to a validation account when it is triggered.

9.

The default logic uses *IF commands to do 'If Then' logic. Answer: False The *When command performs an 'IF' operation.

10. Business Planning and Consolidation uses an XDIMMEMBERSET to select data regions. Answer: True For example, if you want your calculation to run on the “Non_Interco” member of the INTCO dimension because that is the only member that has data that pertains to your calculation: *XDIM_MEMBERSET INTCO = 'Non_Interco'

2010


159

Test Your Knowledge

BPC440

11. The default logic 'Validation and Increment' works as follows: Answer: A, C, D, E B. BPC should be configured so that the designated validation account cannot be adjusted via a journal entry. F. Every time default logic runs, the validation account is incremented by 1.

160


2010

Unit 3 Data Collection and Preparation Unit Overview In this unit we will start off with the methods to bring data into SAP BusinessObjects Planning and Consolidation such as via flat file and InfoCube to InfoCube loads. Then we will address journal entries, validation, and calculating cash flow by using account transformations.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • •

Import data via flat files. Perform an InfoCube to InfoCube load. Discuss transaction data load options. Build a journal template and post an adjusting entry. Discuss how to upload journal entries. Configure the business rules and run balance carry forward. Calculate and store cash flow values using Business Planning and Consolidation script logic. Reclass annual net income to retrained earnings. Explain how to do allocation. Configure and carry out validation. Set up work status.

Unit Contents Lesson: Transaction Data Collection ........................................163 Exercise 4: Flat File Data Collection .....................................179 Exercise 5: Load IC Matching InfoCube from a BW InfoCube .......195 Lesson: Journal Entries and Balance Carry Forward ......................207 Exercise 6: Optional: Managing Journals ...............................225 Exercise 7: Balance Carry Forward ......................................235 Lesson: Account Transformation, Allocation, and Validation..............241 Exercise 8: Account Transformation, Business Rule Copy and Print Feature.......................................................................257

2010


161

Unit 3: Data Collection and Preparation

BPC440

Exercise 9: Optional: Allocation and Script Debugger ................263 Exercise 10: Data Validation and Work Status .........................271 Exercise 11: Characteristic Validation ...................................279

162


2010

BPC440

Lesson: Transaction Data Collection

Lesson: Transaction Data Collection Lesson Overview In this lesson we will address a variety of methods to load raw data into the consolidation application.

Lesson Objectives After completing this lesson, you will be able to: • • •

Import data via flat files. Perform an InfoCube to InfoCube load. Discuss transaction data load options.

Business Example As you put your implementation plan together, one of the most important parts of the project is to decide how and where the data will be loaded into the Legal Application. You need to know how the flat file process works as well as how to do InfoCube to InfoCube loads for example since some of your data may come from ECC via InfoCubes. Note: Entering data manually via input templates will be discussed in the reporting unit. • • • •

What are the data loading options? How: BW or Business Planning and Consolidation What data: Transaction data, Master data including attributes / properties, hierarchies, and text. What source: Flat Files, ECC, Non SAP Systems Let's take a look at a flat file import via a Business User first since it is so frequently used and it will get you used to the mechanics of BPC data imports.

2010


163


BPC440

Figure 143: Flat File BPC Transaction Data Import Architecture

Figure 144: Data Manager

You might have to modify Data Manager packages to meet your specifications. The packages that come delivered with the application are designed to be dynamic so that you do not need to modify the packages in order for them to work with your applications and dimensions.

164


2010

BPC440


But you might want to modify packages to behave differently or to perform additional functions. The process chain allows you to set up pre-defined parameters for package prompts so that you can automate running packages

Figure 145: Uploading files to the server

In order to import a file, the file must reside in the Data Manager Data Files folder on the server. The Upload function allows you to move files from your local machine or directory to the Data Files folder on the server. The Download function allows you to move files from the Data Files folder on the server to your local hard drive or directory.

2010


165


BPC440

Figure 146: Preview Data File

You can preview data files that reside on the server in Company site or other Site directories. To preview data: • •

Open Data Manager, and select eData > Data Preview. Select a directory, and then a data file, and then click OK. Do one of the following depending on the type of file you opened: –

• • •

For text files, choose Delimited or Fixed-width from the Select a data type list. If you chose Delimited, select a delimiter from the Select a delimiter list. – For Excel files, select a worksheet from the Select a worksheet list. – For database files, select a table from the Select a table list. Use the scroll bars to look at the data. The preview window loads the first 200 lines of your data. If you want to open a different file, click the Open button, select another file, and then click OK. Click the Cancel button when you are done previewing your data.

BPC offers two Excel workbook files to carry out data transformations:(Use this link to read about all of the transformation options in detail)

Transformation File

This file allows you to set up the rules for reading data from an external source and put it in the proper form for your system database. Transformation files are Microsoft Excel files that contain one worksheet named Instructions. The Instructions worksheet has the following sections: Options, Mapping, and Conversion. Options: specify flat file delimiters, header rows, skip if ... , validation of members, switch signs based on the acctype property, tolerance for error records, rounding, filter InfoProvider imports, call start and end routine business add-ins. Mapping: parsing, concatenation, pad, link characteristics to dimensions, link columns in a flat file to dimensions, convert multiple key figures to the single BPC key figure. Conversion: The *CONVERSION section of the transformation file defines which conversion sheet to use with which dimensions. Use the following syntax to associate a

166


2010

BPC440


dimension with a conversion sheet: Dimension Name = [COMPANY]WorkbookName[!SheetName]. Items in brackets are optional. Conversion File

This file allows you to map member names from external to internal dimension structures. You can set up multiple sheets in a conversion file so that many transformations can access the same conversion workbook. You can have one conversion file per dimension

Figure 147: Conversion File Examples

Conversion File Features *skip

If you want to ignore external data (as listed in the External column), you can place the keyword *skip in the Internal column

Wildcards

You can use the asterisk (*) and question mark (?) wildcards in the External or Internal columns. An asterisk (*) stands for any character, while a question mark (?) stands for any single character. For example, if you want to reference all members, use the asterisk (*). To increase the incoming amounts by 10%, use a formula of: Value*1.10. You can also use VBA in the formulas.

Conversion files define the mapping by dimensions from external member names to internal member names. They also provide the ability to perform calculations and rounding on data as it is converted. You create one conversion file or sheet per dimension in a transformation. Each conversion file can contain one or more sheets for different types of data transformations.

2010


167


BPC440

You can use '*' widcards, IF statements, and javascript in conversion files. For more detail on conversion and transformation file options: Goto help.sap.com → SAP Business User → EPM Solutions → Planning and Consolidation → SAP Business Objects Planning and Consolidation 7.5 → Open.

Figure 148: Transformation File Examples

Note: In the Version for the Microsoft Platform, transformation files are always used by the system whether they are selected or not. Even if a transformation file is not used in the import, the log will prove that the system uses a default file regardless. OPTIONS: FORMAT= DELIMITED. There is no default so this option must be defined. You must enter a format type. Delimited means that there is a special character between each column of data, defined by the Delimiter option (below). Fixed means that the data is in a fixed field format. HEADER Default: YES If YES, then your input file contains one header row that defines the fields. DELIMITER can be COMMA | SPACE | TAB. The default is a comma. If the FORMAT option is set to DELIMITED, this option defines the single character that is the delimiter between columns. Use the keywords SPACE or TAB if space or tab-delimited.

168


2010

BPC440


SKIP= Default: 0 (zero) Number of lines to skip at the top of a data file. If your data file has a header, set this value so that those lines are skipped during transformation. SKIPIF = NULL will skip a record if it is null. VALIDATERECORDS= No | Yes Default: No If YES, validate the mapping and that members exist, and map data in the proper order for BPC. CREDITPOSITIVE= Default: YES, If NO, all amounts referring to an ACCOUNT type (LEQ, INC) will have their signs reversed. MAXREJECTCOUNT= The number of bad records before the entire load fails. SELECTION can only be used for InfoProvider imports to filter the data from the source. For example: SELECTION = ZCOMP,1010 will only load company 1010 from the source. ZCOMP is the technical name of the characteristic infoobject.

Figure 149: Transformation File Parsing Example

Start routines can be called to perform mass changes before the record based transformations begin. And just before the data is committed to the data base, End Routines can be used to eliminate zero records for example.

2010


169


BPC440

Figure 150: Start and End Routines

Figure 151: Validating (Simulating) Transformation Files

170


2010

BPC440


Figure 152: Run a Data Manager (DM) Package

You can preview both the Import and Transformation files using the magnifying icon on the right. You might have to modify DM packages to work within your company's requirements. The packages that come with Business Planning and Consolidation are designed to be dynamic so that you do not need to modify the packages in order for them to work with your applications and dimensions. But you might want to modify packages to behave differently or to perform additional tasks. You can make modifications to the packages supplied with Business Planning and Consolidation or use those packages as templates to build packages as per your requirements.

2010


171


BPC440

Figure 153: BW Data Load From Source Scenario

Figure 154: InfoProvider Data Import Scenario

If the source InfoCube has multiple key figures, the MVAL keyword can be used to import the data in only one data load.

172


2010

BPC440


Figure 155: Importing Multiple Key Figures using MVAL key word

Figure 156: A Transformation File for an InfoProvider Import

The BW InfoProvider Data Package

2010


173


BPC440

Figure 157: Loading Transaction Data From a BW InfoProvider

Figure 158: Import Transaction Data - A Closer Look

The business requirement for replace within the import package is the same as inputting a new financial statement for a specific region of the cube. If your source General Ledger system only provided month to date actual, you would not be able to determine accounts that have been reclassified, changed, or remained the same. Replace, lets the user “reset” that region of the cube similar to reloading the file as if it was a new data set. It is really an option for what the import file represents.

174


2010

BPC440


Figure 159: Merge / Replace / Append

In the replace and clear scenario, the system checks to see if records have been loaded previously for three dimensions: Time, Category, and Entity. Please note that the merge option does not delete anything from the existing data set and new records are merged into the existing records. The replace option however does not delete records either. It actually generates offsetting records with the reverse sign thus providing the deletion effect when the application is compressed.

Figure 160: Example of Merge

2010


175


BPC440

Figure 161: Example of Replace and Clear

Figure 162: Example of Append

Delivered Process Chains

176


2010

BPC440


Figure 163: Data Manager Delivered Packages

The Distributor & Collector

Figure 164: Another Option: Distributor & Collector

2010


177


BPC440

Figure 165: Distribution & Collection Wizard

The Distributor and Collector provides reporting and data collection options within SAP BusinessObjects Planning and Consolidation and are heavily used in production environments. This feature allows you to distribute reports and input schedules to multiple recipients, based on a predefined distribution list. You can then collect multiple input schedules from users. From the task menu, select Collection instead of Distribution. Two options exist as to the method of data collection. You can select from E-mail or choose a file directory. In this example, “Local Folder” is selected for the folder path. All the files available from that location are displayed. You have the ability to select one, several, or choose the “Select All” check box to process all identified file(s). The Review Distribution Summary window displays information about your request, including Estimated Pages and Time, Application set name, Application name and the selected template(s).

178


2010

BPC440


Exercise 4: Flat File Data Collection Exercise Objectives After completing this exercise, you will be able to: • Perform a flat file data load via the Business Planning and Consolidation Data Manager. • Use conversion and transformation files. • Use the 'Validate & Process Transformation File' option to simulate the load. • Explain what Business Planning and Consolidation default logic does when you bring data into the Legal Application.

Business Example You have data in a legacy system and each month the IT group sends you a file with the monthly YTD results. There are a couple of intentional problems with the file that we will need to address with the conversion and transformation files but other than that, the data is fine. The data in the file includes income statement as well as balance sheet data.

Task 1: Upload the File Upload the flat file onto the BPC server and preview it. Look for transformation opportunities. Are the values supposed to be positive? 1.

From the Data Manager in the LegalApp, upload the file onto the server.

2.

Preview the data file using the comma delimited view. What transformations do we need to do?

Result • • •

Entities are all missing the letter 'C' in the 1st position. There is no header row. All of the values are positive.

Task 2: Perform Business Planning and Consolidation Transformations Use conversion and transformation sheets to modify the data during the load. Simulate the load with the transformation file 'validate & process' feature. 1.

Create a conversion sheet to solve the issue with the legacy naming convention for Entity. Continued on next page

2010


179


2.

BPC440

Create a transformation sheet to interpret the columns of data for the system and also to integrate the conversion file into the process.

Task 3: Loading the Application and Reporting Now that all the pieces are in place, we are ready to actually load the flat file into the LegalApp application. Then, use Business Planning and Consolidation reports to do some light analysis of the data. 1.

Run a data manager package with the transformation file you just created and use the 'view status' option to check out the log.

2.

Run a dynamic template report for the appropriate current view. Set the workbook options so that the server will not be called on each dimension member selection. Caution: Do not type member values into the current view, use the dimension name hypertext instead.

3.

Optional: Open a provided EVDRE Report to view all of your data.

Result Now you can see all of your data that was in your flat file for all flow members.

Task 4: Optional: Browse the BW InfoCube Now you will learn how to look at the data at the table level. Not everyone obviously needs to do this. However, when you have questions about what the middle ware is doing to your data ... this will never fail you! Also, if you are doing data loads, this is a way to confirm they actually did happen ... among others. 1.

Log on to the BW Server:


180


2010

BPC440


Figure 166: BW Server - Easy Access Screen

2.

Go to the 'relative' of the 'Admin Console' in BW, the 'Data Warehousing Workbench', search for your AppSet and right click to display the data in your LegalApp InfoCube.

Figure 167: In the BW Data Warehousing Workbench


2010


181


BPC440

Result

Figure 168: Browsing Business Planning and Consolidation Data in an InfoCube!

Hint: If you change the column widths, the description will display (if it showing the technical name). Note: You can select the value column and use the sigma icon total it. Then sort by Entity for example and use the sigma/sigma icon to create a report like the above with sub totals. Have a nice day!

182


2010

BPC440


Solution 4: Flat File Data Collection Task 1: Upload the File Upload the flat file onto the BPC server and preview it. Look for transformation opportunities. Are the values supposed to be positive? 1.

From the Data Manager in the LegalApp, upload the file onto the server. a)

Log in to Excel: From the Admin Console → Select 'Available Interfaces' → Select 'Interface for Excel' → Select the BPC440_## Appset and LEGALAPP → Connection Wizard → Next → Use a different user and password→ User: CPM-## Password: training → Next → Select BPC440_## → Next→ Finish → Ok.

b)

Upload the file: 'Manage Data' → Upload data file → Source File → Use the drop down → My Computer→ Local Disk (C:) → BPC440 → BPC440_## → Files → Legal → Double click on the 'Legal Data.csv' → Destination File → Use the drop down → Save → Ok → Ok..

Figure 169: File Import


2010


183


2.

BPC440

Preview the data file using the comma delimited view. What transformations do we need to do? a)

Select 'Preview data file' → Select the file → Open → Select a data type: Delimited → Select a delimiter: Comma. Are all the values positive? (they are supposed to be) → Cancel.

Figure 170: Data Preview

Result • • •

Entities are all missing the letter 'C' in the 1st position. There is no header row. All of the values are positive.


184


2010

BPC440


Task 2: Perform Business Planning and Consolidation Transformations Use conversion and transformation sheets to modify the data during the load. Simulate the load with the transformation file 'validate & process' feature. 1.

Create a conversion sheet to solve the issue with the legacy naming convention for Entity. a)

In Business Planning and Consolidation for Excel: Select 'Planning & Consolidation' → eData → More → New Conversion File → Enter the data as follows: External

Internal

*

C*

This will insert a capital C before each incoming value such as 1000 will be converted to C1000 and so on. b)

eData → More → Validate & Process Conversion File... → Enter 'LEGENT' → Save → OK. Caution: Do not put the file in the Example folder.

2.

Create a transformation sheet to interpret the columns of data for the system and also to integrate the conversion file into the process. a)

Go to eData → More → New Transformation File → Enter data as follows: *OPTIONS: • • • • • • • • • • • •

HEADER = NO Credit Positive = NO (this will switch the sign of the value for Accounts with the INC and LEQ account types during the load.) Leave the other options as is. Under *Mapping: C_ACCT = *COL(1) INTCO = *COL(2) ENTITY = *COL(3) TIME = *COL(4) FLOW = *COL(5) C_DATASRC = *COL(6) RPTCURRENCY = *COL(7) CONSGROUP = *COL(8) Continued on next page

2010


185


b)

• • •

C_CATEGORY = *COL(9) AMOUNT = *COL(10) Under *Conversion

•

ENTITY = LEGENT.XLS

BPC440

While in the Transformation sheet → Go to eData →More → 'Validate and Process Transformation file'.

Figure 171: Validate & Process Transformation File

Data Type is Transaction Data from Flat File → Add your legal data file via the drop down → Save As. Enter: LEGALDATATRANS → Save → View the Output File → Cancel.


186


2010

BPC440


Figure 172: Transformation Validation Log (Your record count may vary)

Task 3: Loading the Application and Reporting Now that all the pieces are in place, we are ready to actually load the flat file into the LegalApp application. Then, use Business Planning and Consolidation reports to do some light analysis of the data. 1.

Run a data manager package with the transformation file you just created and use the 'view status' option to check out the log. a)

Select the 'Home' icon → Manage Data → 'Run a package' Import → Run → Add your 'Legal Data' as the import file via the drop down. Add the transformation file 'LegalDataTrans' via the drop down → Leave it set to Merge → 'Yes', include default logic → Next → Select 'No, do not check work status settings' (we haven't configured work status yet) → Finish → Ok. View Status → Check the box at the bottom left to refresh every 5 seconds → When you get the blue check mark → Double click on the import log → Hopefully all of your records were accepted → Close the pop ups.

2.

Run a dynamic template report for the appropriate current view. Set the workbook options so that the server will not be called on each dimension member selection. Continued on next page

2010


187


BPC440

Caution: Do not type member values into the current view, use the dimension name hypertext instead. a)

Select Home → Reporting and analysis → Build a report using a dynamic template → Double click on 'SubTotals by Account' → Ok → eTools → Workbook options → De select 'Expand on current view(cv) change' (this will make it faster to change the CV members → Ok → Expand the 'CV' → Set your current view to what you see below → eTools → Expand All: Note: If you receive a prompt regarding 'A member could not be found for this search criteria' Select 'Ok' → Set the 'Data View' to hierarchy and proceed. Dimension

Member

Consgroup

NON_GROUP

C_Acct

1 (Balance Sheet)

C_Category

C_100

C_Datasrc

INPUT

Entity

H1

Flow

F_TOP

IntCo

TOTAL

RptCurrency

LC

Time

2008.Dec

Measures

YTD

Dimension

Member

Examples of Memberset Options: BAS returns base level members of the parent in the current view. BASMEMBERS returns all base level members regardless of the current view member. SELF returns the current view member only. DEP returns dependents (first born) of the current view member. LBAS(2) returns base level members of the current view member down to and including level two of the 1st hierarchy in the dimension. Note: The complete list of memberset key words is in the reporting unit. Continued on next page

188


2010

BPC440


Figure 173: Control Panel - Account Totals

b)

Expand all → Open the group above column H and make the following adjustments as you can see above → In G47 → Put Entity in the columns → Select BASMEMBERS for the Entity memberset in G48→ In F48 → Select via the dropdown 'BAS,SELF' for the C_ACCT memberset → Suppress zeroes in the rows and columns by placing a 'Y' in F51 and G51→ Delete the 'Hide Column and Row Key' settings in C52 → Close the group above column H → Unhide row 43 → Hide row 44 → Right justify the column headers in row 43→ Set the data column widths to 10 → Select eTools → 'Expand All' . Note: Since we suppressed zero values, no Balance Sheet total will appear since it is zero. Save the report → eTools → Save Dynamic Templates → Company folder→ Enter: 'Account Totals' → Save.

Figure 174: Flat File Result 'Account Totals' (values may vary)

Note: The report above only shows closing balances since it is restricted by the flow member F_TOP which is the parent of F_999 closing.


2010


189


3.

BPC440

Optional: Open a provided EVDRE Report to view all of your data. a)

On the upper left → Select the 'Office Button' → Open → My Computer→ Local Disk (C:) → BPC440 → BPC440_## → Files → Legal → Select the Excel file 'BPC440 Account by Entity Base Members' → Open → Expand All.

Figure 175: Account by Entity Base Members

b)

Save the report: Go to eTools → Save dynamic template → Select the Company folder → Save.

Result Now you can see all of your data that was in your flat file for all flow members.

Task 4: Optional: Browse the BW InfoCube Now you will learn how to look at the data at the table level. Not everyone obviously needs to do this. However, when you have questions about what the middle ware is doing to your data ... this will never fail you! Also, if you are doing data loads, this is a way to confirm they actually did happen ... among others. 1.

Log on to the BW Server:


190


2010

BPC440



a)

2.

Minimize your remote desktop → Select the Citrix 'START' button → Launch the 'SAP Logon' shortcut → Logon → User: cpm-## → Password: training→ Enter

Go to the 'relative' of the 'Admin Console' in BW, the 'Data Warehousing Workbench', search for your AppSet and right click to display the data in your LegalApp InfoCube.


2010


191


BPC440


a)

To go to the above screen shot: Enter 'RSA1' in the white command field on the upper left → Enter → Select 'Infoprovider' on the upper left if necessary → Use the search (not the binoculars are the top, use the ones below it) to find 'BPC440_## → Open the InfoArea: → right click on your LegalApp→ Display data → Select the green check mark to continue → Select characteristics (see the screen shot) below:

Figure 178: Select Fields in ListCube


192


2010

BPC440


De-select: 'Change run id','Record Type', and 'Request ID' → Enter to continue → Select the button at the top left 'Field select for Output' → Select all → F8 to adopt your selections → F8 on the data selection screen→ And Voila! I know that was a lot but this is really important to see the data in the cube because it is in an un-aggregated state. You can answer a lot of questions this way since you can see the records that the system generates before they are combined with other records with the same key. When you Optimize an application, that's what happens. Note: * At this point there are so many fields available to navigate on that you have to pick from the list which includes every dimension and its properties which are navigational attributes in BW. Hint: If you know the technical name of your Infocube or if you have a unique application description you can go to the transaction code LISTCUBE. Enter your cube name but you will still need to select from your dims and properties as per the above. Also, your data will include NON_GROUP not G_NONE. The ownership calculation requires the use of NON_GROUP.

Result


2010


193


BPC440

Figure 179: Browsing Business Planning and Consolidation Data in an InfoCube!

Hint: If you change the column widths, the description will display (if it showing the technical name). Note: You can select the value column and use the sigma icon total it. Then sort by Entity for example and use the sigma/sigma icon to create a report like the above with sub totals. Have a nice day!

194


2010

BPC440


Exercise 5: Load IC Matching InfoCube from a BW InfoCube Exercise Objectives After completing this exercise, you will be able to: • Perform the set up necessary if you need to load data from a normal BW InfoCube. • Use a variety of transformation options in BPC.

Business Example When it comes to loading transaction data, flexibility is the key. Now that Business Planning and Consolidation sits on top of BW, customers are interested in loading BPC InfoCubes from other InfoCubes in BW. There can be several reasons for this. What if you already have PCA (profit center accounting) or New GL data sitting in BW and you want to feed it into the BPC Legal Application? There will also be situations where customers will need to do data layering in BW and perhaps do some homogenization of the data before it is ready for consolidation. Note: Some customers are doing BW loads directly to Business Planning and Consolidation InfoCubes and that's okay as long as no changes are made to the InfoCube. Of course, this would mean that the Infocube would not be available when performing the BW data load.

Task: InfoCube to InfoCube Data Collection There is an existing InfoCube with ECC 'like' data that you will load into the IC Matching Application. There are a few intentional issues with the dimension names that we'll map in the transformation file. The business requirement also calls for us to do a roll-up during the load. Apparently, the ECC Company Codes are not all legal entities and the customer does not want that much detail in this situation. Note: ECC Stands for ERP Central Component, the SAP OLTP transactional System otherwise known as R/3.

2010

1.

Optional: Analyze the data in the source InfoCube. Before we start, let's go take a look at the data in the source as usual, right? So, we will go to the BW Server and run our new favorite transaction code LISTCUBE. Take a look at the data in the InfoCube so you know what kinds of transformation challenges you will have this time.

2.

From BPC for Excel, open the existing conversion file ICCONV, review it, and validate it. Do not change any data unless the instructor asks you to. Continued on next page


195


3.

BPC440

Use the ICTRANS transformation sheet on the C Drive to interpret the columns of data for the system and also to integrate the conversion files into the process. Note the setting 'CreditPositive=NO' so the system will switch the signs for accounts with account type = Inc and Leq. After the import, launch the 'Subtotals by Account' dynamic template to view the data.

Result Now you have loaded data from one InfoCube to another! Have a nice day!

Figure 180: IC Matching Load Report

196


2010

BPC440


Solution 5: Load IC Matching InfoCube from a BW InfoCube Task: InfoCube to InfoCube Data Collection There is an existing InfoCube with ECC 'like' data that you will load into the IC Matching Application. There are a few intentional issues with the dimension names that we'll map in the transformation file. The business requirement also calls for us to do a roll-up during the load. Apparently, the ECC Company Codes are not all legal entities and the customer does not want that much detail in this situation. Note: ECC Stands for ERP Central Component, the SAP OLTP transactional System otherwise known as R/3. 1.

Optional: Analyze the data in the source InfoCube. Before we start, let's go take a look at the data in the source as usual, right? So, we will go to the BW Server and run our new favorite transaction code LISTCUBE. Take a look at the data in the InfoCube so you know what kinds of transformation challenges you will have this time. a)

Log into BW Minimize your remote desktop → In Citrix → Start → Launch the 'SAP Logon' shortcut → Logon → User: cpm-## → Password: training → Enter.

b)

→ Enter LISTCUBE in the white command field on the upper left → Enter → Type in 'ECCData' InfoProvider name → Deselect 'Display SID's' → F8 → 'Fld Selectn for output' (upper left) → Select All → Deselect the 3 Data Package Fields → F8 → F8 again.

Figure 181: Simulated ECC Data in the Source InfoCube


2010


197


BPC440

Optional: To get the view above: Select the Zamt column → Total with the sigma icon → Use the control key to select both ZTPart and Zcurtyp columns → Sort Ascending → With both columns still selected → Subtotal (sigma sigma icon). 2.

From BPC for Excel, open the existing conversion file ICCONV, review it, and validate it. Do not change any data unless the instructor asks you to. a)

Log into Excel: In BPC for Excel → Expand the current view → Use the drop down to select the ICMATCHING application.

b)

Select the 'Office Button' on the upper left → Open → My Computer → C Drive → BPC440 → BPC440_## → Files → ICMatch → ICCONV → Open → Confirm the data as shown below: Entity (this will perform a roll up)

c)

External

Internal

1010

C1000

1020

C1000

1030

C1000

2010

C2000

2020

C2000

2030

C2000

Confirm the following sheets: C_Category External

Internal

0

C_100

Consgroup External

Internal

None

NON_GROUP

Intco External

Internal

1000

I_C1000

2000

I_C2000


198


2010

BPC440


Flow External

Internal

00999

F_999

ICDatasrc External

Internal

INPUT

INPUT

RptCurrency External

Internal

00

TC

10

LC

TIME External

Internal

2008012

2008.DEC

TRNCURRENCY External

Internal

USD

T_USD

ICACCOUNT External

Internal

12710000

AS274800000

211710000

LI16870000

Note: F_999 is 'Closing' as in 'Closing Balance'. d)

After you review all ten sheets → Select Planning & Consolidation → Go to eData → More → Validate and Process Conversion File → Enter 'ICCONV' → Save → OK. Caution: Do not save the file to the examples folder, just let the system save the file to the default folder.


2010


199


BPC440

Figure 182: IC Matching Conversion Sheet

3.

Use the ICTRANS transformation sheet on the C Drive to interpret the columns of data for the system and also to integrate the conversion files into the process. Note the setting 'CreditPositive=NO' so the system will switch the signs for accounts with account type = Inc and Leq. After the import, launch the 'Subtotals by Account' dynamic template to view the data. a)

Select the 'Office Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → ICMatch → ICTRANS → Open→ Confirm the following data: • • • • • • • • • • • • • • •

Under *Options: CREDITPOSITIVE=NO Under *Mapping: C_CATEGORY = ZVER ENTITY = ZCOMP FLOW = ZFLOW RPTCURRENCY = ZCURTYP CONSGROUP = ZCONSGRP ICACCOUNT = ZACCT ICDATASRC = ZDSRC INTCO = ZTPART TIME = 0FISCPER TRNCURRENCY = 0CURRENCY AMOUNT = ZAMT Under *Conversion


200


2010

BPC440


(in reality, you would not need a conversion if the characteristic value is not changing such as the account number for example.)

Figure 183: IC Matching Transformation File

b)

While in the Transformation sheet → Go to eData → More → Validate and Process Transformation file → Data Type is Transaction Data From NW BW InfoProvider → Add 'ECCDATA' as the InfoCube name (IN CAPS) at the bottom:

Figure 184: Infoprovider - Validate and Process Transformation File


2010


201


c)

BPC440

Save and simulate: Save As → ICTRAN → Save → View the Log → Cancel. Note: Note: If the system detects discrepancies in your data, it will create (if necessary) and propose conversions for you! So if the system says it has 'rejected' records, answer 'Yes' to the prompt for it to modify your files, go look at the adjustments (usually they are highlighted), save your conversion sheet if necessary and try it again.

Figure 185: Transformation Validation Log (yours may vary)

d)

Select the 'Output File' radio button on the lower left to see the data before we load it and to confirm the transformations are working correctly:


202


2010

BPC440


Figure 186: Simulated InfoCube Load

e)

Close the pop-ups and now let's actually load the data with the 'Load InfoProvider' Package.

Figure 187: ICMatching Load InfoProvider Package

f)

Select 'Home' → Go to 'Manage Data' → Run a package → Select the group 'System Administrative' → 'LoadInfoProvider' → 'Run' → Enter 'ECCDATA' in caps → Select your transformation file ICTRAN.


2010


203


BPC440

g)

Next → Finish → Ok → View Status → After viewing your log → Return back to Excel.. Note: You may receive a warning for the duplicate records and there may be records in the 'reject' file, but that's ok, it still loads just fine and it even rolls up!

h)

Now let's run a report to see the data: Select Home → Reporting and Analysis → Build a report using Dynamic Template → Page down → Select 'Nested Rows' → Ok → Etools → Workbook options → De select 'Expand on Current View Change' → OK → Set your current view to:

i)

Dimension

Member

Consgroup

NON_GROUP

C_Category

C_100

Entity

CG2

Flow

F_999

ICAccount

CTLICEND00

ICDatasrc

INPUT

IntCo

INP_INTERCO

RptCurrency

LC

Time

2008.DEC

TrnCurrency

T_USD

On the upper left → Click on the '+' symbol to open up the columns → Set the membersets in F48 and H48 to 'BASMEMBERS' → Set the row with ICaccount to 'BAS,SELF' in G48. Place IntCo into the column in H47→ Set suppression to 'Y' for both rows and the column in F51, G51, H51 → Remove the setting 'Hide row and column keys' (around C52)→ Close the groups → Hide the two description columns M,N, & O → Go to eTools → Expand All.


204


2010

BPC440


Figure 188: Control Panel

j)

Save the report: Go to eTools → Save Dynamic Template → Select the Company folder → Enter 'IC Matching Load Report' → Save.

Result Now you have loaded data from one InfoCube to another! Have a nice day!

Figure 189: IC Matching Load Report

2010


205


BPC440

Lesson Summary You should now be able to: • Import data via flat files. • Perform an InfoCube to InfoCube load. • Discuss transaction data load options.

Related Information •

206

See the how to paper on Inter Company Matching


2010

BPC440

Lesson: Journal Entries and Balance Carry Forward

Lesson: Journal Entries and Balance Carry Forward Lesson Overview In this lesson we will build the template for journals and also post an adjusting entry. Then, we will configure and run balance carry forward.


Build a journal template and post an adjusting entry. Discuss how to upload journal entries. Configure the business rules and run balance carry forward.

Business Example On your project you know that you will need to post adjusting entries in SAP BusinessObjects Planning and Consolidation. Also, you are interested in what is required in the business rules for balance carry forward.

2010


207


BPC440

Journal Entry Management

Figure 190: Journal Overview

Note: Data manager packages do not create journal entries in the Planning and Consolidation application. For example, when you run the eliminations package, no journal entry is created although records are inserted into the InfoCube. There is a log kept in the data manager and you can also use the data audit reports as well. You use journals to record and make adjustments to data in the database. This is typically done as part of the month-end or quarter-end process. For example, administrators load general ledger information into an application using the Data Manager. Before the close, line managers can review the data and make adjustments, as necessary, using a journal entry form. Note: Some customers are okay with a reasonable number of standardizing entries in the Planning and Consolidation solution against a unique datasrc for clarity. If there was an error in the source system, most people would like to make that fix in the source and load that corrected data again. Other companies don't want any journal entries in this system because it makes reconciliation more difficult since the source system will remain unchanged. To enable the journal functionality, a journal template needs to be created in the Admin Console. There is only one template per application.

208


2010

BPC440


Figure 191: Journal Wizard

After creating the journal template, security has to be set up in order to provide access to users. This is done in the Admin Console, as well. Within the financial flow, journals are used to change the total figure on the database. Classical financial planning/consolidation systems are based on reported financial data. This can be done via upload file or manual data input. Journals can be used to adjust imported data as well as to adjust eliminations data. For each journal several detail rows can be saved. To provide this functionality, a set of internal tables are used. The aggregated figure per journal ID will be stored in the reporting cube. This means, that detailed journal information is stored in system tables, aggregated totals of these journals are stored in the cube. Journal Control Features By adding an ‘ENABLEJRN’ property to any dimension, only the members with a ‘Y’ in that property can be selected in journals.

2010


209


BPC440

Figure 192: Journal Control Features

Delivered tasks in security •

Delivered tasks in security AdminJournal - create journal templates, clear journal tables.

• • • •

210

CreateJournal - create journal entries. PostJournal - can post journals entries.l ReviewJournal - can run the journal reports. UnPostJournal - can unpost a journal.


2010

BPC440


Application Journal Parameters 1.

JRN_BALANCE - Defines whether journals must balance. 1 or Y: Journals must balance when they are posted. Journal users can save an unbalanced journal, but may not post it. 0 or N: Journals can be balanced or unbalanced. Journal users can change this behavior. If they select Balanced, it works the same as option 1. 2: Journals users are prompted to save the journal as balanced, but are not required to do so.

2.

3.

4.

JRN_MAXCOUNT - The maximum number of journal entries returned from a query in the Journal Manager This parameter is useful if you have a large number of journal entries and want to protect a user from launching a large query that returns many journals and takes a long time. JRN_POST_OVERWRITE - Determines whether the system keeps the same journal ID when saving journals that were previously set to Posted status, but changed to Unposted status. Y: The Journal ID is preserved. N: A new ID generates when the unposted journal is saved. JRN_DESC_MODE - Determines whether member IDs or descriptions are shown in the Journal template. Y: Member descriptions are shown as row and column headings. N: Member IDs are shown as row and column headings.

Figure 193: Journal Entry Screen

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

2010


211


BPC440

removes your audit trail, even though changes made to the application data through posted journal entries are maintained. If you recreate the journal template, but do not change the structure of the template — keeping all header and detail dimensions the same — then you have the option to keep the existing journal entries. If you do need to change the structure, you should off load the journal tables first. The data can be modified manually and then re-loaded. Note: The Auto Reverse saves the reversed journal entry upon posting the current entry. Then, the entry in the subsequent period would need to be posted.

Figure 194: Journal Entry Tasks

The table below describes the available Journal tasks and how to perform each one. You perform most of these tasks from the Journal Manager, but if you have a journal entry open you can perform many of them from the Journal Options action pane:

212

Task

What you should know

Create a journal entry

Based on your security of course.

Modify a journal entry

You can modify saved and unposted journal entries.

Copy one or more entries

You can copy selected entries to another category and time member.


2010

BPC440


Open one or more entries

You open journal entries to view or edit them.

Post one or more entries When you post an entry, the system applies the values in the journal entry to the database, so that application data is appended. Unpost one or more entries

The system reverses the original entry to the application.

Search for journal entries

If a large number of journal entries are written to an application, use the Journal Manager to define queries so you can search for specific entries. The Journal Manager searches through both header and detail dimensions. If you have multiple journals (available with the Microsoft Platform), they are grouped under the first entry.

Locking journals

When you lock a journal, you cannot make changes to the journal entries.

Reopen journal entries

To copy one or more single journal entries to new single journal entries in a subsequent time period. This requires mapping for old vs. new dimension members.

Repost

Used to book journal values to the InfoCube in case data was deleted.

Require balanced journals

A balanced journal is one in which the debits equal the credits in the journal entry. If this option is set, you cannot post the journal entry until it is balanced.

Delete one or more entries

When you delete an entry that has been posted or unposted, its status changes to Deleted. When you delete saved entries, they are deleted from the system.

Define journal reopen translations

Design a template of translation information for the dimensions you want to copy. You can copy one or more journal entries from a previous year, and post them to another set of accounts for the following year. The 'translations' map the old account to the new account for example.

View a report

You can generate reports based on journal entries.

Review line item journal detail

You can review detail lines of a journal entry for the entries to which you have View rights.

Note: You can easily mandate that all journal entries balance in the application parameters.

2010


213


BPC440

Copying Journal Entries

Figure 195: Copy Journal Entries - Interim Periods

You can copy one or more journal entries to create new journals with different header values such as the subsequent period if using the YTD setting for a Legal Application. Or, you might want to copy queries to another category. When journal entries are copied, they are in saved status and then need to be posted. Reposting a journal entry will send the values to the fact tables again just in case the records were deleted. In other words, let's hope you never need to use this option! Reposting does not offer an option to change the header values. How to Look up Journal Tables To look up the journal tables for your appset: •

214

Goto the BW server: Enter SE16 into the command field → Enter: UJA_APPSET_INFO → Enter → F8 → Note your appset prefix → Green arrow back twice → Enter: UJA_APPL → Enter → Select your appset BPC440_## → F8 → Note your Legalapp prefix → Green arrow back twice → Enter the journal details table: /1CPMB/xxzzzJRDT (xx is your appset prefix, zzz is your application prefix) → Enter → F8 → Voila!


2010

BPC440


Figure 196: Journal Detail Table

How to upload journals The package below can be used to upload journal entries from flat files. To determine the file layout, run the journal export package after you have posted at least one journal entry in the system. The journal export and restore packages can be added to the data manager from BPC for Excel: eData → Organize package list → Right click in the yellow area → Add package → Goto App Group → Business Planning and Consolidation: Examples. Then, use that structure for your new journals!

Figure 197: Uploading Journal Entries

2010


215


BPC440


Figure 198: Copy Year End Balances

The closing balance of one year must be identical to the opening balance of the following year. The first task for a new fiscal year is therefore to carry forward the balance from the previous year. You can however run this task as often as you need to.

Figure 199: Copy Opening - Sub Items (flow)

The default logic will roll up the prior year data into the opening balance flow member.

216


2010

BPC440


Figure 200: The Balance Carry Forward (BCF) Function

For example, if one uses the dimension “flow” in their data model when closing balances of one year are rolled forward into the opening balances of the following year, the balance to be rolled forward will be found under flow type Closing, but will need to be posted in the new year under flow type Opening. As well accounts may also change. In another example, the account Retained earnings current year income, when rolled forward may in the new year be stored under an alternate account Retained Earnings from prior period. Accordingly, the ability must also exist to change accounts during roll-forward. The “Business Rules Tables” in this case are designed to define what values need to be rolled forward (i.e. accounts and flows and to what accounts and flows these values should be posted in the new year). The carry-forward function can be applicable to both Financial and Legal Consolidation Applications. Carry-forward rules give you the ability to generate the Opening Balance of any category based on two main properties: Flow Type in the Account dimension Opening category in the Category dimension This procedure can be used to initialize a new reporting period with the closing balances of the last period from the previous year into the opening balances of the current period. In a Legal Consolidation application, such balances are usually identified as members of the FLOW dimension. In simpler applications, however, it is also possible to store them as additional accounts in the ACCOUNT dimension. Important remark: This procedure is only copies the opening balances as found in the DATASRC dimension members flagged as “I” and “M” in the DATASRC_TYPE property. This means that the procedure will only copy the “Input” balances and their related “Manual” adjustments. The balances generated “Automatically” by the consolidation procedure (DATASRC members flagged as “A”) are taken care of during the consolidation process by the consolidation procedure itself. An Introduction to Business Rules You can apply the carryforward function to both Financial and Legal Consolidation applications.

2010


217


BPC440

Figure 201: Business Rules in General

The Copy Opening Business Rule

Figure 202: Copy Opening - Business Rule

Here's what the data looks like after running the business rule above:

218


2010

BPC440


Figure 203: BCF Result

Balance Carry Example using Flow member for Prior Year RE Note: The example below was taken from a 7.0 system, so it is using the 7.0 GROUPS dimension not the 7.5 GROUP dimension. In row 1 of the business rule, current year retained earnings (CYRE) will be carried forward into the new year CYRE and that is why we need row 2 which negates it, and row 3 which places the value into the appropriate flow for prior year RE.

Figure 204: BCF Example Using Flow member for prior year continued

2010


219


BPC440

Figure 205: BCF Breakdown using Flow member for prior year

How to add prior year to current year RE

Figure 206: How to add current to prior year RE using Flow member for prior year

How to carry forward interim periods:

220


2010

BPC440


In order to run balance carry forward each month, the source period and year must be specified in the category dimension. Otherwise the system will always use the last period of the preceding year as the source. In the example below, the package would be run for 2009.FEB.

Figure 207: Example: How to carry forward interim periods

For balance sheet accounts, when opening a new year for processing, you populate the opening balances for the new year with the closing balances of the last period of the prior year (or roll up the prior year opening plus changes). In addition, you might close current period net income to the balance sheet to create a fully balanced balance sheet for each period. The carry-forward function supports these processes. Depending on the data model you use and the type of accounts you deal with, the sending and receiving values may not always be the same. For example if you use the dimension “flow” in a data model when the closing balances of one year roll forward into the opening balances of the following year, the system finds the balance rolling forward under flow type Closing, but needs to post it in the new year under flow type Opening. Also, accounts may change. For example, the Retained Earnings current year income, when rolled forward, may in the new year be stored under an alternate account Retained Earnings from prior period. Accordingly, the business rules tables define what values need to roll forward. If you are using a YTD application, balance carry forward will need to be run each month for the balance sheet accounts.

2010


221


BPC440

The Copy Opening Big Picture

Figure 208: BCF - Component Architecture

Business rules provide the mathematical foundation for your BPC applications. Business Rules are table based logic that provide the flexibility to customize certain delivered functions to meet specific business needs, without having to understand scripting/programming.

Figure 209: Copy Opening - Business Rule Table

The business rule field 'Opening Datasrc' uses a property value of the datasrc member to write to. For example, if the INPUT member has an 'Opening Datasrc' value of P_INPUT, and INPUT is placed in the business rule table 'Opening Datasrc' column, then the records in the new period will be posted to P_INPUT.

222


2010

BPC440


The business rule field Source Datasrcis used to filter which datasrc members will be carried forward. Important Dimension Properties for Copy Opening

Figure 210: Copy Opening - Dimension Properties

2010


223


224


BPC440

2010

BPC440


Exercise 6: Optional: Managing Journals Exercise Objectives After completing this exercise, you will be able to: • Configure a journal template for an application. • Create journal entries and run journal reports. • Copy journal entries into subsequent periods.

Business Example Depending on your corporate strategy, you may need to make standardizing entries in BPC. For example, when the subsidiary is too aggressive in booking depreciation, or when the subsidiary books Finished Goods Inventory, but it is actually WIP from a Group perspective. And, you may run into some situations where it is a last resort to fix an error. So, you need to know how to set up journal templates for applications, create journal entries, and report on the results.

Task 1: Journal Template 1.

Create a journal template for your Legal Application. In the header, include the following dimensions: Consgroup, C_Category, Entity, Time, Groups, C_DataSrc.

2.

Confirm that the dimensions are in same order as they are listed in Part '1a)'.

3.

In Step 3, confirm that the dimensions in the columns are in this order: C_Acct, Flow, IntCo.

4.

In Step 4, create an item for Group Adjustments with a sub-item for Depreciation, and second sub-item for Finished Goods. This will be used to categorize your journal entries.

5.

In Step 5, quickly scan the summary of the settings and 'Finish'. You are now ready to book an entry.

Task 2: Journal Properties To add some control, let's restrict journal entries to just 'manual journal' DataSrc's. Also, we don't have a need to post unbalanced entries such as for # of shares or # of people, so let's require all journal entries to balance. 1.

In the DataSrc Dimension, add a property called 'EnableJrn' with 1 character and set it to 'Y'es for all of the MJ_* members so that only those can be used in Journal postings.


2010


225


BPC440

Task 3: Journal Entries Create a journal entry in BPC to comply with group accounting principles. 1.

One of the subsidiaries books depreciation more aggressively than the Group accounting standards. So you need to book a 570 (in LC) entry to debit accumulated depreciation and credit depreciation using the data below. Note: We are going back one month to book this entry so we will need to copy the journal into the 'current' month. If Excel was open when you created the journal template, please close it and re open it. Hint: You can just double click to bring up a selection list. Do not type. Note: Depending on what support pack the class is on, the ENABLEJRN property may not work and may also generate a message ('Text property is read only') when determining its member values. Use the following data for your journal entry:

2.

Field

Value

Consgroup

NON_GROUP

C_Category

C_100

C_Datasrc

MJ_Manje

Entity

C1000

Time

2008.Nov

Group Adjustment

Depreciation

Debit for 570

Account: 12120300 Flow: F_999 Intco: I_None

Credit for 570


After entering in the above data, save, post, run an HTML report on it, view it in PDF output, experiment with 'Manage Journals' which allows you to browse through a list of journals and then view the line items in a split screen.


226


2010

BPC440


3.

Since most Consolidations Applications are managed on a year to date basis, many of your journals will need to be copied over from one closing period to the next. Note: In YTD applications, YTD data is loaded every period and that means you are not relying on the system to add periodic data for a YTD total and that includes manual journal entries.

2010


227


BPC440

Solution 6: Optional: Managing Journals Task 1: Journal Template 1.

Create a journal template for your Legal Application. In the header, include the following dimensions: Consgroup, C_Category, Entity, Time, Groups, C_DataSrc. a)

If you have Excel open → Close Excel → Go to the Admin Console → Open up the LegalApp → Select 'Journals' → Select 'Journal Wizard' on the right → If prompted select No→ Check off these five header dimensions: Consgroup, C_Category, C_Datasrc, Entity, RptCurrency, and Time.

Figure 211: Journal Header Dimensions

Note: Category, Time, and Rate type dimensions are all required to be in the Header. 2.

Confirm that the dimensions are in same order as they are listed in Part '1a)'. a)

Go to Step 2 and confirm the order of the dimensions → If necessary → Select the dimension you want to move and use the 'UP' or 'Down' button.


228


2010

BPC440


3.

In Step 3, confirm that the dimensions in the columns are in this order: C_Acct, Flow, IntCo. a)

Go to Step 3 and confirm the order of the dimensions to match the above if necessary.

b)

Set the maximum number of lines per journal document to 10 rows.

Figure 212: Journal - Max number of Rows


2010


229


4.

BPC440

In Step 4, create an item for Group Adjustments with a sub-item for Depreciation, and second sub-item for Finished Goods. This will be used to categorize your journal entries. a)

Add a header 'Item': Go to Step 4 → On the left under the items section → Select 'Add' → Enter 'Group Adjustments' → Add → Ok.

b)

Add two sub-items: On the right Select 'Add' → Enter → Depreciation → Add → Enter Finished Goods → Add → Ok.

Figure 213: Journal Items and Sub Items

5.

In Step 5, quickly scan the summary of the settings and 'Finish'. You are now ready to book an entry. a)

Go to Step 5 → You are presented with a summary of your configuration settings → Select 'Finish' → Ok → The system then gives you a nice preview of the journal entry screen.


230


2010

BPC440


Task 2: Journal Properties To add some control, let's restrict journal entries to just 'manual journal' DataSrc's. Also, we don't have a need to post unbalanced entries such as for # of shares or # of people, so let's require all journal entries to balance. 1.

In the DataSrc Dimension, add a property called 'EnableJrn' with 1 character and set it to 'Y'es for all of the MJ_* members so that only those can be used in Journal postings. a)

In the Admin Console: Select the C_DataSrc dimension in the Dimension Library → Maintain Dimension Property → Enter a new property called 'ENABLEJRN' with 1 position → Modify Dimension Property → Ok.

b)

Select C_DataSrc → 'Maintain Dimension Members' → Enter a 'Y' for the six manual journal (MJ) members listed below → Process dimensions → Deselect 'Take Appset Offline' → Ok → Ok. MJ_CORRECTION MJ_RECLAS MJ_RECLAS_G MJ_MANJE MJ_CNDGAAP MJ_USGAAP

Task 3: Journal Entries Create a journal entry in BPC to comply with group accounting principles. 1.

One of the subsidiaries books depreciation more aggressively than the Group accounting standards. So you need to book a 570 (in LC) entry to debit accumulated depreciation and credit depreciation using the data below. Note: We are going back one month to book this entry so we will need to copy the journal into the 'current' month.


2010


231


BPC440

If Excel was open when you created the journal template, please close it and re open it. Hint: You can just double click to bring up a selection list. Do not type. Note: Depending on what support pack the class is on, the ENABLEJRN property may not work and may also generate a message ('Text property is read only') when determining its member values. Use the following data for your journal entry: Field

Value

Consgroup

NON_GROUP

C_Category

C_100

C_Datasrc

MJ_Manje

Entity

C1000

Time

2008.Nov


232


2010

BPC440


Group Adjustment

Depreciation

Debit for 570


Credit for 570


a)

If you have BPC for Excel already open and it was open when you created the journal template, please close it. If the header fields do not appear, turn off 'freeze panes'. Go to BPC for Excel → Set the application to the LegalApp → Select Journals → Enter a New Journal → Enter the members as shown above by double clicking each cell.

Figure 214: Journal Entry

2.

After entering in the above data, save, post, run an HTML report on it, view it in PDF output, experiment with 'Manage Journals' which allows you to browse through a list of journals and then view the line items in a split screen. a)

Select 'Save Journal' → Ok → Post Journal → Answer 'Yes' to the prompt →Ok.

b)

Choose 'Manage Journals' → Execute Query → Yes → Select the Entry ID → Press the '>>' details button on the top right → You should see the debit and credit lines in the split screen at the bottom.


2010


233


3.

BPC440

Since most Consolidations Applications are managed on a year to date basis, many of your journals will need to be copied over from one closing period to the next. Note: In YTD applications, YTD data is loaded every period and that means you are not relying on the system to add periodic data for a YTD total and that includes manual journal entries. a)

While you are still in 'Manage' mode → Select 'Copy To' → Yes → Copy time values to the next period → Next → Choose 'Next' to keep the same format type i.e. only one header combination → Keep all the members the same → Next → Apply → Ok → Finish → Select Manage Journals → Execute Query → Yes → Select the new 'Saved' journal → Post → Yes → Close. Have a nice day!

234


2010

BPC440


Exercise 7: Balance Carry Forward Exercise Objectives After completing this exercise, you will be able to: • Configure the business rules to do balance carry forward. • Use the provided script logic, programs and data packages that are delivered with Business Planning and Consolidation. • Execute and analyze the data generated by the function.

Business Example To prepare for a new year in the Planning and Consolidation Application, the opening balances are normally rolled over from the prior year.

Task: Balance Carry Forward Business Rules 1.

To configure the business rules, go to the Admin Console, and fill in the business rule based on the data below: In row 1, roll the entire balance sheet (closing flow) from 2008.DEC to 2009.JAN (opening flow). Then, in lines 2 and 3, reverse out the current year retained earnings and post the prior year retained earnings. Source Account

Source Flow

1

F_999

25712000

F_999

25712000

F_999

Destination Flow

Reverse Sign

F_100

Unchecked

25712000

F_100

Checked

25714000

F_100

Unchecked

Destination Account

Data Source Type

Note: '1' is the balance sheet group of accounts ... all of them! F_100 is the opening flow. F_999 the closing balance. 25714000 is the prior year retained earnings. 25712000 is current year retained earnings. Note: Any blank destination fields will then inherit the value from it's associated source field. 2.

There is a delivered package which uses the default logic for carry forward. In BPC for Excel for the LegalApp, go into 'Organize Package List' and save it to the admin and user groups.

3.

Execute the delivered package for 2009.JAN. Continued on next page

2010


235


4.

BPC440

Now let's use a provided EVDRE report to view the data that was copied over. It is called 'BPC440 BCF'.

Result Now your balance sheet for Jan 2009 has opening balances. Have a nice day!

Figure 215: Balance Carry Forward Result (your values my vary)

236


2010

BPC440


Solution 7: Balance Carry Forward Task: Balance Carry Forward Business Rules 1.

To configure the business rules, go to the Admin Console, and fill in the business rule based on the data below: In row 1, roll the entire balance sheet (closing flow) from 2008.DEC to 2009.JAN (opening flow). Then, in lines 2 and 3, reverse out the current year retained earnings and post the prior year retained earnings. Source Account

Source Flow

1

F_999

25712000

F_999

25712000

F_999

Destination Flow

Reverse Sign

F_100

Unchecked

25712000

F_100

Checked

25714000

F_100

Unchecked

Destination Account

Data Source Type

Note: '1' is the balance sheet group of accounts ... all of them! F_100 is the opening flow. F_999 the closing balance. 25714000 is the prior year retained earnings. 25712000 is current year retained earnings. Note: Any blank destination fields will then inherit the value from it's associated source field. a)

Go to the Admin console → Open up the LegalApp → Go To Business Rules → Select 'Carry-Forward Rules' → Fill in the table based on the data above:

b)

Validate and confirm carry-forward-rules rule table → OK.

c)

Confirm that you have the balance carry forward logic in place: Go to 'Script Logic ' in the LegalApp → Select 'Copy_Opening.LGF' → Validate and Save→ Ok.


2010


237


2.

BPC440

There is a delivered package which uses the default logic for carry forward. In BPC for Excel for the LegalApp, go into 'Organize Package List' and save it to the admin and user groups. a)

Goto Excel for the Legalapp → Select 'Planning & Consolidation' (scroll right if you need to)→ eData → More → Organize Package List → Right click in the yellow area → Add Package → Select the drop down to 'view all process chains' → Select the App group called 'Business Planning and Consolidations: System' → Select '/CPMB/Opening_Balances' → Choose the 'Select' button. Check the User and Admin Package Task Type → Enter a package name and description of 'BCF' → Add → Save → Ok.

Figure 216: The BCF Package

3.

Execute the delivered package for 2009.JAN. a)

Select 'Home' → Go to Manage Data → 'Run a package'. Double click on 'BCF' → Select Entity 'all', C_Category 'C_100' (Actual), RptCurrency 'LC', and Time 2009.Jan. Next → Finish → Ok → View Status → After it turns blue → Double click to display the log → Double click the formula log → Review the data → Cancel → Close → Cancel.

4.

Now let's use a provided EVDRE report to view the data that was copied over. It is called 'BPC440 BCF'. a)

Select the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → BPC440 BCF → Open → Set your current view as shown below → Expand all. Save the report into your application: Continued on next page

238


2010

BPC440


Go to eTools → Save Dynamic Template → Select the Company folder → Use the same name → Save. Select the current view members by left clicking the dimension names (do not type these in) Dimension

Member

Consgroup

NON_GROUP

C_Acct

Any value (since accounts are in the rows)

C_Category

C_100

C_DataSrc

Totaladj

Entity

H1

Flow

Any value

IntCo

TOTAL

RptCurrency

LC

Time

Any value

Result Now your balance sheet for Jan 2009 has opening balances. Have a nice day!

Figure 217: Balance Carry Forward Result (your values my vary)

2010


239


BPC440

Lesson Summary You should now be able to: • Build a journal template and post an adjusting entry. • Discuss how to upload journal entries. • Configure the business rules and run balance carry forward.

240


2010

BPC440

Lesson: Account Transformation, Allocation, and Validation

Lesson: Account Transformation, Allocation, and Validation Lesson Overview In this lesson we will use account transformation to calculate and record cash flow values, discuss allocation logic, and carry out validation. We will also discuss the business purpose of each one.


Calculate and store cash flow values using Business Planning and Consolidation script logic. Reclass annual net income to retrained earnings. Explain how to do allocation. Configure and carry out validation. Set up work status.

Business Example You are looking for a way to calculate cash flow and other realignments of data and so you are interested in learning about account transformation (commonly referred to as reclassification. As part of the managerial consolidation, you need to allocate overhead between profit centers. And of course, there are several points in the process where the values need to be validated.

Account Transformation

Figure 218: Account Transformation Function

2010


241


BPC440

Account transformation reads and aggregates the values posted to specific combinations of accounts, flow types and data sources in order to post the aggregated amount under an alternate destination account, flow and data source combination. The account transformation business rule inverts the sign when posting calculated amounts if appropriate, which alternates debit and credit amounts. This rule uses reference data in other periods and years to determine amounts to post. This rule also supports year-to-date calculations in period-based applications. You can utilize account transformation in both financial and legal consolidation applications.

Figure 219: How account transformation works

Figure 220: Account Transformation - Business Rule Tables

242


2010

BPC440


Figure 221: Reclassification Logic and Package

Calculate and store annual net income and retained earnings. Here's an example of how to calculate and store annual net income and retained earnings. This would be very useful in cases where the source system does not contain those metrics such as ECC.

Figure 222: Example of the Reclassification of Annual Net Income

2010


243


BPC440

Figure 223: Results of Annual Net Income Reclass

Example: Simple Cash Flow calculations

Figure 224: Business rules and cash flow calculation results

Allocation •

244

Allocations are used primarily in managerial consolidation scenarios and can be used to disaggregate anything from general overhead to corporate cash.


2010

BPC440


Figure 225: Allocation Concept

Figure 226: Top Down Allocation: The user inputs the amount, source and target!

2010


245


BPC440

Figure 227: Top Down Allocation:Results

Figure 228: Top Down Allocation: Code

246


2010

BPC440


Figure 229: Allocation Usage and Description

Note: The slide above is not in the presentation. Note: There are several 'How To' papers in sdn.sap.com on allocations including one on 'Top Down Allocation'.

2010


247


BPC440

Figure 230: Allocation Logic Components

Note: The slide above is not in the presentation. Note: Factor (Optional) : • • • • •

Omitted - factor will always default to 1, Using and Total columns are ignored. Numerical values such as 2 – What x 2 Using – What is multiplied by Using. Total column is ignored. Using/Total – What is multiplied by Using/Total 1/COUNT – Divided evenly among 1/count of where members Hint: There is an OSS note on Allocations: 1318471. There are also several how to papers. Caution: Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Below you can see the result of running a simple allocation. The total amount in this case was split proportionately between the two Entities based on labor hours.

248


2010

BPC440


Figure 231: Allocation Example - One Account

25,000 in total was entered for social contributions for the first profit center, then the system allocated it based on the relative amount of labor hours.

Figure 232: How the allocation works - Part I

2010


249


BPC440

Figure 233: How the allocation works Part II

Figure 234: Example of a Summary Allocation: Code

250


2010

BPC440


Figure 235: Example of a Summary Allocation: Results

Data Validation

Figure 236: Data Validation Concept

Validation rules must support the ability to define the records to be checked using multiple dimensions (i.e. a given account / flow combination). By running a report on the various “error” accounts, it is then possible to see whether or not all validations have been successful or if issues exist which require further follow-up. Business rule tables exist in order to allow Business Users to define which sets of records they wish to compare. The validation function can be utilized by both Financial and Legal Consolidation applications. Note: In the Version for the Microsoft Platform, validations are integrated with work status so that the work state cannot be advanced if an imbalance exists.

2010


251


BPC440

How does it work?

Figure 237: Data Validations: How does it work?

Validation performs user-defined checks after data entry or at subsequent points in the consolidation process to help ensure the completeness and accuracy of the existing data. If the comparison returns a true condition, then the validation is deemed to have been successful. If a false result is returned, then the validation is deemed to have failed and the system posts any variance between the balances in the two sets of accounts to an error account. You define the records the system checks using multiple dimensions, such as a specific combination of account and flow. You can report on the various error accounts to see whether or not all validations have been successful or if issues exist that require further follow up. You can set up validation for both Financial and Legal Consolidation applications. Data Validation: Field Definitions

252


2010

BPC440


Figure 238: Data Validation - Business Rule Tables

Note: The slide above is not in the presentation. The 'Other Destination Dimension' is used for defining the data region to store the imbalance amount from the validation rule calculation. If it blank, the imbalance amount will be written to the same data region with imported data. Therefore, if the imported data has more than one Intco member for example, the 'Other Destination Dimension' field must be defined.

Figure 239: Validation Logic and Package

In this sample result below, an out of balance of 1000 was calculated and written.

2010


253


BPC440

Introduction to Workstatus • • • •

Used to prevent changes to data at key points in the process. Flexible mechanism to control a process. Optional. Uses the OWNER property in the Entity dimension.

Since data validation is a key point in the consolidation process, using work status at this point is something to consider. Apshell is delivered with three work states however customers can add more. The 'right' to perform a task depends on whether the user is the owner or manager of the Entity in the data region.

Figure 240: How Owners and Managers are Deterimined

Figure 241: Work Status Architecture

254


2010

BPC440


Characteristic Validation

Figure 242: Characteristic Validations Overview

Note: You as a customer will define and configure filters on invalid combinations. If the system tries to save data for an invalid combination this error message will appear: 'Member Third_Party is not valid for dimension InterCo in rule 0000002.' This is only available in the NetWeaver release.

Figure 243: Characteristic Validation - Driver Dimension

The rules are created at the “Dimension” level, not at the application level. That’s why in this example, the rule is created against the Account dimension. Therefore, the same set of rules can be used in multiple applications.

Figure 244: Characteristic Validation - Summary

2010


255


256


BPC440

2010

BPC440


Exercise 8: Account Transformation, Business Rule Copy and Print Feature Exercise Objectives After completing this exercise, you will be able to: • Use the account transformation business rule to calculate cash flow.

Business Example You need to generate some cash flow reports and so you are looking to use the account transformation business rules to calculate the values that you need. You are also interested in using these business rules for reclassification such as moving subsidiary finished goods inventory back to work in process or to reclass annual net income to retained earnings.

Task: Account Transformation Use account transformation to perform a simple cash flow calculation based on Net Income. Use the copy feature to speed up configuration time. Do a print preview of your settings for possible documentation purposes. 1.

Set up the account transformation business rule in the LegalApp based on the following table. Then confirm that your logic is still there, confirm the transformation group id 'CF', and validate it again. Trans. Source Grp. Acc

Cat'y Srce Srce Dest Flow D.Src Acct

Dest. Dest. Cat'y Flow

Dest. Rev D.Src

CF

39000000 C_100 F_999 Input CF001 C_100 F_999

Input

No

CF

30527140 C_100 F_999 Input CF002 C_100 F_999

Input

No

CF

30527150 C_100 F_999 Input CF002 C_100 F_999

Input

No

Note: The 39000000 is the annual net income transfer account, F_999 is the closing flow, 30527140/30527150 are depreciation accounts. Use the drop down where available. Note: If the copy row feature does not appear when you right click in the following directions, just use 'Ctrl-C' and Ctrl-V'. Continued on next page

2010


257


BPC440

2.

There is a delivered package which uses the default logic for reclassification. In BPC for Excel for the Legal Application, go into 'Organize Package List' and save it to your user group and admin group.

3.

Now let's execute the CALCACCOUNT package which will run the logic, ABAP program and related process chain. We'll use member values as seen below.

4.

Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

LC

Time

2008.DEC

Run a provided EVDRE report in eTools called 'BPC440 Cash Flow' in your BPC440_## folder.

Result

Figure 245: Calc Account Cash Flow Result

You will see the values in the 39000000 account which was 'copied' to the cashflow account as well as the depreciation which was added back since it does not affect cashflow. There is no value for the equipment depreciation (30527150) in the 2008.Dec actuals. Have a nice day!

258


2010

BPC440


Solution 8: Account Transformation, Business Rule Copy and Print Feature Task: Account Transformation Use account transformation to perform a simple cash flow calculation based on Net Income. Use the copy feature to speed up configuration time. Do a print preview of your settings for possible documentation purposes. 1.

Set up the account transformation business rule in the LegalApp based on the following table. Then confirm that your logic is still there, confirm the transformation group id 'CF', and validate it again. Trans. Source Grp. Acc

Cat'y Srce Srce Dest Flow D.Src Acct

Dest. Dest. Cat'y Flow

Dest. Rev D.Src

CF

39000000 C_100 F_999 Input CF001 C_100 F_999

Input

No

CF

30527140 C_100 F_999 Input CF002 C_100 F_999

Input

No

CF

30527150 C_100 F_999 Input CF002 C_100 F_999

Input

No

Note: The 39000000 is the annual net income transfer account, F_999 is the closing flow, 30527140/30527150 are depreciation accounts. Use the drop down where available. Note: If the copy row feature does not appear when you right click in the following directions, just use 'Ctrl-C' and Ctrl-V'. a)

In the Admin Console for the LegalApp: Go to Business Rules → Account Transformation → Enter row 1 of the data from above → Left click on row 1→ Right click on row 1→ Copy row → Right click on next empty row → Paste row → Change the account values → Repeat for row 3 → Validate and Confirm Account Transformation Rule Table → OK.

b)

Generate a file for printing and documentaion: Select 'Print business rule table' → My computer → C-Drive → BPC440 → BPC440_## → Files → Legal → Enter file name: BCF Bus Rule → Save → Go view the html file:


2010


259


BPC440

Figure 246: BCF Business Rule Table

c)

2.

3.

For the LegalApp: Go to Script Logic → CALCACCOUNT.lgf → Confirm that you have code there from the previous exercise → Confirm that 'CALC=CF' → Validate and Save → Ok.

There is a delivered package which uses the default logic for reclassification. In BPC for Excel for the Legal Application, go into 'Organize Package List' and save it to your user group and admin group. a)

Log on to Excel: From the Admin Console → Open 'Available Interfaces' on the lower right → Launch the 'Interface for Excel' → Switch to the Legal Application if necessary → Connection Wizard → Next → User different user ID and password → Enter password 'training' → Next → Select Appset BPC440_## → Next → Finish→ Ok.

b)

Save the delivered package: Select 'Planning & Consolidation' → Goto eData → More → Organize Package List → Right click in the yellow area → Add Package → Select the drop down to 'view all process chains' → Select the app group called 'Business Planning and Consolidations: System' .

c)

Select '/CPMB/RUNCALCACCOUNT' → Choose the 'Select' button. → Select the User and Admin Package Task Type → Enter a package name and description of 'CALCACCOUNT' → Add → Save → Ok.

Now let's execute the CALCACCOUNT package which will run the logic, ABAP program and related process chain. We'll use member values as seen below.


260


2010

BPC440


Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

LC

Time

2008.DEC

a)

4.

For the LegalApp: In BPC for Excel → Home → Manage Data → Run a package → Run CALCACCOUNT→ Enter the data region from above → Next → Finish → Ok → View Status → Double click on the log → Double click on the Formula Log to see the number of records processed. It should say that 4 records were processed → Return to Excel.

Run a provided EVDRE report in eTools called 'BPC440 Cash Flow' in your BPC440_## folder. a)

In BPC for Excel in the LegalApp: Goto the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → BPC440 Cash Flow → Open.

b)

Set your current view as you see below → Expand All.

c)

Dimension

Member

Consgroup

NON_GROUP

C_Acct

Any value is fine

C_Category

C_100

C_DataSrc

TOTALADJ

Entity

H1

Flow

F_999

IntCo

TOTAL

RptCurrency

LC

Time

2008.DEC

Save the report: Go to eTools (scroll left if necessary) → Save dynamic template → Select the Company folder → Save.

Result


2010


261


BPC440

Figure 247: Calc Account Cash Flow Result

You will see the values in the 39000000 account which was 'copied' to the cashflow account as well as the depreciation which was added back since it does not affect cashflow. There is no value for the equipment depreciation (30527150) in the 2008.Dec actuals. Have a nice day!

262


2010

BPC440


Exercise 9: Optional: Allocation and Script Debugger Exercise Objectives After completing this exercise, you will be able to: • Demonstrate the setup of an allocation using scrip logic. • Illustrate the use of the script logic test program which is available in the Version for SAP NetWeaver. • Utilize an input schedule to enter data values and validate the allocation results in your application set.

Business Example You are performing managerial consolidation and you need to assign values to lower level operating units. This will typically be done for expense but can be carried out for Revenue or even Balance Sheet items since it is freely definable by you.

Task: 1.

Use the allocation logic in your Planning Application to do a simple expense allocation. If you missed this step in the logic exercise, the file for this exercise can be found on your remote computer's C Drive in the BPC440_## under Files for the Planning application. Also, you will need to reference the lgf file in the default logic so that it will be executed on the fly as data is input.

2.

Use the script logic test program on the BW Server. Goto SE38 and run program UJK_SCRIP_LOGIC_TESTER. Either paste your code in the lower left hand window or let the system access it via the 'Script File Location'. Try the validate and execute (simulate) options. If you enter incorrect code such as removing the '*' from a line, what happens?

3.

In the Planning Application , open the Nested Row Input Schedule in BPC for Excel, input 50,000 EUR for C9000 in the 'Social Contributions' for period 2007.Jan and when you save it the default logic should run the allocation. The assignment will be based on you inputting 400 hours for C1000 and 300 in C2000. Save the revised input schedule as 'Allocation' on the company folder.

Result


2010


263


BPC440

Figure 248: Allocation Result

In cell P51, the Social Contributions for PC4YOU Deutschland Gmbh should calculate to 400/700 times 50,000 = 28,571. In cell P72, the Social Contributions for PC4YOU UK Ltd. should calculate to 300/700 times 50,000 =21,429. Have a nice day!

264


2010

BPC440


Solution 9: Optional: Allocation and Script Debugger Task: 1.

Use the allocation logic in your Planning Application to do a simple expense allocation. If you missed this step in the logic exercise, the file for this exercise can be found on your remote computer's C Drive in the BPC440_## under Files for the Planning application. Also, you will need to reference the lgf file in the default logic so that it will be executed on the fly as data is input. a)

Go to the Admin Console: In the Planning Application → Script Logic → Allocation → Confirm that the logic in your system is the same as in the illustration below. This is what the logic above is going to do: The logic below will allocate the total amount posted to the CE0004030 account using the relative values in the CE0652000 account for the two 'receivers' in the CG1 group. The other members by dimension are: 'Actual' category, 'None' activity, 'Manual' datasrc, and 'EUR' Rptcurrency.

Figure 249: Allocation Script Logic

If necessary, use the Allocation.lgf file in the remote desktop's C Drive in the BPC440_## folder under Files for the Planning application → Copy and Paste it in → Validate and Save.


2010


265


b)

2.

BPC440

In this scenario, we want the allocation logic to run whenever data is input, so we need to reference it in the default logic. Therefore → Goto the admin console → Planning application → Default.lgf → reference the allocation logic by inputting: → *INCLUDE ALLOCATION.LGF → Validate and Save → Ok. Note: If the Default.LGF file does not exit, create it.

Use the script logic test program on the BW Server. Goto SE38 and run program UJK_SCRIP_LOGIC_TESTER. Either paste your code in the lower left hand window or let the system access it via the 'Script File Location'. Try the validate and execute (simulate) options. If you enter incorrect code such as removing the '*' from a line, what happens? a)

Log on to BW Minimize your remote computer session on your desktop → From Citrix → Start → SAP Logon → Log on → User: cpm-## → Password: 'training' → Enter.

b)

Go to the Script Debugger: → Enter SE38 in the white 'command field' on the upper left → Enter → Type in the program UJK_SCRIP_LOGIC_TESTER → F8. (or just use the UJKT t-code ... COOL!)

Figure 250: Script Debugger Screen

Select your appset → Select your planning application → Select your user id → Cut and paste the allocation code in the lower left → Enter in the data region: Time = 2007.JAN .


266


2010

BPC440


When you 'Validate', the compiled code will appear on the lower right: Select the Validate button → If the code is working, the system will copy it exactly as it is (but without comments) to the right hand screen. c)

3.

Optional: If you are an ABAPer and you are interested in how to launch the ABAP debugger Enter '/H' in the command field → Enter → Select the 'Execute' icon → You should now be in the ABAP Debugger Control screen.

In the Planning Application , open the Nested Row Input Schedule in BPC for Excel, input 50,000 EUR for C9000 in the 'Social Contributions' for period 2007.Jan and when you save it the default logic should run the allocation. The assignment will be based on you inputting 400 hours for C1000 and 300 in C2000. Save the revised input schedule as 'Allocation' on the company folder. a)

b)

Go to BPC for Excel: Expand the current view → Use the Application drop down → Select Planning. Set your current view as follows: Application

Planning

Category

Actual

Entity

CG2

P_Acct

CE0001000 (parent)

P_Activity

None

P_DataSrc

Manual

RptCurrency

EUR

Time

2007.Total

Measures

Periodic

Select Data Input → Build a schedule using a dynamic template → Nested Row → Ok → eTools → Workbook Options → De select the 'Expand on Current View Change' (so you can change several current view members before you have to expand) → Ok. Click on the Group icon '+' above column J → Enter C9000,C1000,C2000 for the Entity memberset → Enter CE0004030,CE0652000 for the P_ACCT memberset → Delete ',HideRowKeys' in C56 (leave 'hide column keys')→ Expand All → Select Ok to clear input data (if necessary)→ Hide columns M & N → Close the column group. Save via eTools → Save Dynamic Template → Company Folder → Allocation → Save. Continued on next page

2010


267


c)

d)

BPC440

Enter the following data: Cell

Value 2007.Jan

Entity

Account

P49

50,000 Eur

C9000

Social Contributions (CE0004030)

P52

400 hrs

C1000

Labour Hours (CE0652000)

P54

300 hrs

C2000

Labour Hours (CE0652000)

In the action pane → Send data → Send active worksheet → Yes → Close confirmation. Caution: If you receive a message that an error occurred while communicating with the web server, go check your code in the Admin Console and try it again. Make sure the dimensions in the allocation logic match those in your planning application.

Result

Figure 251: Allocation Result


268


2010

BPC440


In cell P51, the Social Contributions for PC4YOU Deutschland Gmbh should calculate to 400/700 times 50,000 = 28,571. In cell P72, the Social Contributions for PC4YOU UK Ltd. should calculate to 300/700 times 50,000 =21,429. Have a nice day!

2010


269


270


BPC440

2010

BPC440


Exercise 10: Data Validation and Work Status Exercise Objectives After completing this exercise, you will be able to: • Discuss which points in your consolidations process where you may want to run balancing checks. • Configure the business rules for data validation. • Set up the related logic and data manager package.

Business Example At various points during the consolidation process, you would like to run some tests to see if your financial statements are in balance. You are interested in checking for the usual 'Assets equal Liabilities and Owners Equity' but you also want to know how to do some additional checks such as 'Depreciation equal to the change in Accumulated Depreciation'.

Task: Validation Business Rules Configure and execute the Data Validation Business Rules. 1.

In your LegalApp fill in your Validation Rules Details top section as you see below: Hint: The Validation Tolerance of zero means that any difference will be written to the validation account. If you set the tolerance to 1000, a difference of 999 will not result in a posting. Another example: If AR is 1000 and AP is 2000, and you set the Operator to '<=', no records will be posted. Validation Acc.

2.

Remark

V.Op. Other Dest.Dim.

V.Tol

VALID_010 A=LOE

=

0

VALID_020 RE=ANI

=

0

VALID_030 Deprec

=

0

INTCO=I_NONE,F_999

In the bottom section, enter in the data below for each validation account.:


2010


271


Validation Acc.

BPC440

Account 1

Flow 1 Sign 1

Account Flow 2 2

Sign2

VALID_010 A

F_999

1

LOE

F_999

1

VALID_020 25712000

F_999

1

39000000 F_999

1

VALID_030 12120300

F_999

1

30527140 F_999

1

Row 1 of the lower table will appear as follows:

Figure 252: Validation Header and Detail (with VALID_010 selected)

3.

Confirm that your LegalApp has validation logic, validate and save it just in case it wasn't validated earlier.

4.

There is a delivered package which uses the default logic for data validations. In BPC for Excel, go into 'Organize Package List' and save it to the user group.

5.

Go to Excel and Execute the validation package for the data region below:

6.

Dimension

Value

Entity

C_Category

C_100

RptCurrency

Time

2008.Dec

Run the provided BPC440 Validation dynamic template report on the validation accounts: Val001/2/3, use the following data region:


272


2010

BPC440


7.

Dimension

Member

Consgroup

NON_GROUP

C_Acct

Validations

C_Category

C_100

C_Datasrc

TotalAdj

Entity

H1

Flow

F_999

IntCo

TOTAL

RptCurrency

LC

Time

2008.Q4

Measure

YTD

Dimension

Member

Let's run a test to see what happens if we are out of balance. Input some data to cause an out of balance that our validation rules are set up to detect. Run validation and check out the results. Then set the data back to its balanced state.

Result

2010


273


BPC440

Solution 10: Data Validation and Work Status Task: Validation Business Rules Configure and execute the Data Validation Business Rules. 1.

In your LegalApp fill in your Validation Rules Details top section as you see below: Hint: The Validation Tolerance of zero means that any difference will be written to the validation account. If you set the tolerance to 1000, a difference of 999 will not result in a posting. Another example: If AR is 1000 and AP is 2000, and you set the Operator to '<=', no records will be posted. Validation Acc.

V.Op. Other Dest.Dim.

V.Tol

VALID_010 A=LOE

=

0

VALID_020 RE=ANI

=

0

VALID_030 Deprec

=

0

a)

2.

Remark

INTCO=I_NONE,F_999

Open up your LegalApp → Business Rules → Validation Rules Details → In the top section of the screen → Enter in the 3 records per the table above. Note: (A = Assets, LOE = Liabilities + Owners Equity).

In the bottom section, enter in the data below for each validation account.: Validation Acc.

Account 1

Flow 1 Sign 1

Account Flow 2 2

Sign2

VALID_010 A

F_999

1

LOE

F_999

1

VALID_020 25712000

F_999

1

39000000 F_999

1

VALID_030 12120300

F_999

1

30527140 F_999

1

Row 1 of the lower table will appear as follows:


274


2010

BPC440


Figure 253: Validation Header and Detail (with VALID_010 selected)

a) 3.

Confirm that your LegalApp has validation logic, validate and save it just in case it wasn't validated earlier. a)

4.

5.

Enter in the data above into the lower section for each account → 'Validate and confirm validation rules detail rules table' → OK.

In your LegalApp → Script Logic → Confirm that it is there → Validate and Save → Ok.

There is a delivered package which uses the default logic for data validations. In BPC for Excel, go into 'Organize Package List' and save it to the user group. a)

Log into Excel for the LegalApp: From the Admin Console → Open 'Available Interfaces' on the lower right → Select 'Interface for Excel' → Select the LegalApp if necessary → Connection Wizard → next → Use different user ID and password → PW 'training → Next → Select BPC440_## Appset → Next → Finish → Ok.

b)

Select Planning & Consolidation → Goto eData → More → Organize Package List → Right click in the yellow area → Add Package → Select the drop down to 'view all process chains' → Select the App group called 'Business Planning and Consolidations: System' → Select '/CPMB/VALIDATIONS' → Choose the 'Select' button → Select the User and Admin Package Task Type → Enter a package name and description of 'VALIDATION' → Add → Save → Ok.

Go to Excel and Execute the validation package for the data region below:


2010


275


BPC440

Dimension

Value

Entity

C_Category

C_100

RptCurrency

Time

2008.Dec

a)

Go to BPC for Excel → Select your LegalApp if necessary → Home → Manage Data → Run a package → VALIDATION → Run. Enter the above data region → Next → Finish → Ok. View Status → Double click on the log → Double click on the Formula Log → Read the log ... it should say that 0 records were written if you are in balance → Return to Excel.

6.

Run the provided BPC440 Validation dynamic template report on the validation accounts: Val001/2/3, use the following data region: Dimension

Member

Consgroup

NON_GROUP

C_Acct

Validations

C_Category

C_100

C_Datasrc

TotalAdj

Entity

H1

Flow

F_999

IntCo

TOTAL

RptCurrency

LC

Time

2008.Q4

Measure

YTD

Dimension

Member

a)

In BPC for Excel → Select the 'Windows Button' on the upper left → Open → My Computer > C-Drive > BPC440 → BPC440_## → Files → Legal → BPC440 Validation → Open → Set your current view to the above data region → Expand your report → Your report should be blank!

b)

Save this report for later use: Goto eTools → Save dynamic template → Company folder → Save.


276


2010

BPC440


7.

Let's run a test to see what happens if we are out of balance. Input some data to cause an out of balance that our validation rules are set up to detect. Run validation and check out the results. Then set the data back to its balanced state. a)

Input some data to cause an out of balance: In BPC for Excel → Select the 'Windows Button' on the upper left → Open →My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → BPC440 Validation Test → Open → Expand all → Change the 25712000 account to 21,000 and the 30527140 account to 5,500 → 'Send Data':

Figure 254: Before and After the Data Change

b)

Execute the validation: Select 'Run Package' → Run the Validation package for the same data region as before → Check the formula log → It should indicate that two records were written.

c)

Refresh the Validation Report: Goto the Validation report → Refresh:


2010


277


BPC440

Figure 255: After the validation run

d)

Set the data back and run validation again: Select the template 'BPC440 Validation Test' → Expand All → Clear data → Enter the original values → Send data → Run Validation → Confirm zero balances for the validation accounts.

Result

278


2010

BPC440


Exercise 11: Characteristic Validation Exercise Objectives After completing this exercise, you will be able to: • Apply combination checking for an application. • Explain the difference between the typical 'value' validations and characteristic combination validation.

Business Example You want to prevent invalid combinations of characteristics in your consolidation data. In the situation below, we need to prevent non inter company postings in inter company trading accounts.

Task: You will set up characteristic validation for a 'driver' dimension in your LegalApp so that invalid combinations will not be allowed. Then you will demonstrate the system error when you try to enter values that are not allowed based on your settings. Note: The 'Driver' dimension is the one dimension per application whose members are used to compare against other dimension members to see if they are permissible. There is only one driver dimension per application but it can be used as a point of comparison with any other dimension in the application. 1.

Log on to the BW Server and in the UJ_Validation transaction code assign C_Acct as the 'Driver Dimension' for the LegalApp.

2.

Set up the rule maintenance for the C_Acct intercompany AR account so that if a record is posted against 'I_None', it will fail.

3.

Activate the rule for Manual data entry for the LegalApp.

4.

Go to BPC for Excel in the LegalApp and use input template'BPC440 Characteristic Validation' to test out your new configuration.

Result You should receive the message: 'Member I_None not valid for dimension C_Acct in validation rule 0000001'.

2010


279


BPC440

Solution 11: Characteristic Validation Task: You will set up characteristic validation for a 'driver' dimension in your LegalApp so that invalid combinations will not be allowed. Then you will demonstrate the system error when you try to enter values that are not allowed based on your settings. Note: The 'Driver' dimension is the one dimension per application whose members are used to compare against other dimension members to see if they are permissible. There is only one driver dimension per application but it can be used as a point of comparison with any other dimension in the application. 1.

Log on to the BW Server and in the UJ_Validation transaction code assign C_Acct as the 'Driver Dimension' for the LegalApp. a)

Log on to the BW Server: Minimize the BPC remote desktop → In the Citrix desktop → Start → 'SAP Logon' shortcut → Logon → User: cpm=## → Password: 'training'

b)

Enter UJ_VALIDATION in the white 'command field' on the upper left → Enter:

Figure 256: UJ Validation Options

c)

Select your appset BPC440_## → Assign Driver Dimension → Select C_Acct for the LegalApp → Save driver dimension settings.


280


2010

BPC440


Figure 257: Assign Driver Dimension


2010


281


2.

BPC440

Set up the rule maintenance for the C_Acct intercompany AR account so that if a record is posted against 'I_None', it will fail. a)

Select the F3 key (or green arrow back) → Select Rule Maintenance → Use F4 to select the C_Acct dimension → Enter → Create Rule → Enter 'Intercompany account and trading partner' → Use the IC AR account: 11301100. → Add Dimension → Use F4 to select Intco → Select operator <> → For members use F4 to select I_NONE → Save Rule

Figure 258: Create Validation Rule

Note: The only operators are '<>' and '='. But you can include multiple single values separated by commas.


282


2010

BPC440


3.

Activate the rule for Manual data entry for the LegalApp. a)

Select F3 → F3 → Select 'Turn Validations On/Off' → Select 'Application ID': 'LegalApp → Turn manual planning on → Save validation settings → F3.

Figure 259: Turning Validations On


2010


283


4.

BPC440

Go to BPC for Excel in the LegalApp and use input template'BPC440 Characteristic Validation' to test out your new configuration. a)

Set your current view: Application

LEGALAPP

CONSGROUP

NON_GROUP

C_ACCT

11301100

C_CATEGORY

C_100

C_DATASRC

INPUT

ENTITY

C1000

FLOW

F_100 (OPENING)

INTCO

I_NONE

RptCurrency

LC

TIME

2008.Q1

MEASURES

YTD

b)

Goto the 'Windows Button' → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → 'BPC440 Characteristic Validation'→ Open → Select 'Planning & Consolidation' → Expand All.

c)

Try entering and Sending an invalid value for the 11301100 account and intco I_NONE: In the action pane select 'Send data' → Active Worksheet → Yes.

Result You should receive the message: 'Member I_None not valid for dimension C_Acct in validation rule 0000001'.

284


2010

BPC440


Lesson Summary You should now be able to: • Calculate and store cash flow values using Business Planning and Consolidation script logic. • Reclass annual net income to retrained earnings. • Explain how to do allocation. • Configure and carry out validation. • Set up work status.

2010


285

Unit Summary

BPC440

Unit Summary You should now be able to: • Import data via flat files. • Perform an InfoCube to InfoCube load. • Discuss transaction data load options. • Build a journal template and post an adjusting entry. • Discuss how to upload journal entries. • Configure the business rules and run balance carry forward. • Calculate and store cash flow values using Business Planning and Consolidation script logic. • Reclass annual net income to retrained earnings. • Explain how to do allocation. • Configure and carry out validation. • Set up work status.

286


2010

BPC440

Test Your Knowledge


Which of the below are included in the steps to do a flat file transaction data load? Choose the correct answer(s).

2.

□

A

□ □ □ □ □

B C D E F

Upload the file to the SAP BusinessObjects Planning and Consolidation Server. Create a conversion file to map external to internal names. Create a transformation file that includes the conversion file. Identify the InfoProvider. Run the data manager import file package. Save the data.

Which of the following are true regarding the reversal of signs during data loads? Choose the correct answer(s).

3.

□

A

□

B

□

C

□

D

□

E

□

F

If the source value is positive it will be reversed if it is an AST account type. If the source value is positive or negative it will be reversed if it is an AST account type. If the source value is positive or negative it will be reversed if it is an LEQ account type. If the source value is positive or negative it will be reversed if it is an INC account type. If the source value is positive or negative it will be reversed if it is an EXP account type. If the source value is negative it will be reversed if it is an AST account type.

Which of these scenarios could be a viable option to input data into a Planning and Consolidation InfoCube? Choose the correct answer(s).

2010

□ □

A B

□

C

□

D

□ □

E F

You have incoming flat files from a legacy source system. You were faxed the trial balance and you want to enter it manually via an input template. You have data in a BI InfoCube that was loaded from the ECC New General Ledger. You want to distribute spreadsheets and collect them from the various subsidiaries. You have adjusting entries to make at the group level. You want to use the infamous BI ETL data loading functionality.


287

Test Your Knowledge

4.

BPC440

Which of the following are important to keep in mind when you use journal entries for an application? Choose the correct answer(s).

5.

□

A

□

B

□ □

C D

□

E

Once a template has been created, it should not be changed because part of the audit trail is lost. You can use the property 'enablejrn' in a dimension to control which members can be posted against in a journal entry. Journal entries hit the line item DSO and the Totals InfoCube. Journal entries have to be copied from one period to the next when the Legal Application is set to YTD. Journal entries can be forced to balance by either checking that setting in the journal itself or turning that feature on in the application parameters.

Journal control features include: Choose the correct answer(s).

6.

□

A

□ □ □

B C D

□

E

The new NW validation rules which prevent invalid characteristic combinations. Tolerances groups. Work status control for journals. Journal security involves defining users who can administer, create, post, or unpost journal entries. Posting periods can be closed.

Which of the following best describes balance carry forward (BCF)? Choose the correct answer(s).

288

□ □

A B

□

C

□

D

□

E

BCF is normally run at the beginning of the new year. BCF copies balance sheet account balances into period 000 of the new year. BCF does not always write a balance sheet balance to the same account. BCF can be used to copy multiple flows from one year to opening balance in the subsequent year. BCF business rules include: Source account, Source datasrc, Destination account and the reverse sign indicator (the Datasrc is inherit).


2010

BPC440

Test Your Knowledge

7.

Which of the following are true statements regarding the 'Account Transformations? Choose the correct answer(s).

8.

□

A

□

B

□

C

□

D

□

E

They can be used to calculate and store values such as for cash flow reporting purposes. Allows read and write capability for four dimensions: Account, Category, Time, and Datasrc. Additional features include: reversing signs, YTD or Period values, and offsets to determine the source year and period. Account transformations copy from the source and write to the target dimensions. Account transformations delete from the source and write to the target dimensions.

Your client has asked you to provide a synopsis of the Allocation function. Which of the following points should you include? Choose the correct answer(s).

9.

□ □

A B

□ □

C D

□

E

Allocations are typically used in managerial accounting scenarios. Allocations are used as a dis-aggregation feature such as for distributing corporate overhead. The components include a segment, cycle, and cycle run group. The delivered objects for allocation include: Logic, Package, Business Rules, the allocation program, and the allocation process chain. Allocations could also be used for balance sheet items.

Your boss needs a summary of what you learned in the Business Planning and Consolidation class about validations and so you would include which of the following: Choose the correct answer(s).

2010

□

A

□

B

□

C

□

D

□ □

E F

There are actually two types of validations available: the more traditional 'value' validations, and also the characteristic combination validation as well. If a false result is returned, the variance between the balances in the two sets of accounts will be automatically posted to an “error” account. If an out of balance is calculated, the system automatically locks the period based on a special validation account in work status. The validation account that is written to when out of balances exist is defined in Work Status (Microsoft only). If the validation account is not zero, work status can be advanced. Account1, Flow1, and Sign1 form the receiving dimensions.


289

Test Your Knowledge

BPC440

Answers 1.

Which of the below are included in the steps to do a flat file transaction data load? Answer: A, B, C, E D is incorrect. If you do an InfoCube to InfoCube load, then you would need to identify the InfoProvider. F is incorrect, there is no need to save the data, when you load the InfoCube, the data is committed to the database.

2.

Which of the following are true regarding the reversal of signs during data loads? Answer: C, D Of the four account types, only INC and LEQ are reversed and it does not matter what the sign is in the source file or InfoCube.

3.

Which of these scenarios could be a viable option to input data into a Planning and Consolidation InfoCube? Answer: A, B, C, D, E F. It is not recommended to use the BI ETL data loading functionality since the SAP BusinessObjects Planning and Consolidation default logic would be bypassed in that situation. For example, what if you needed to have signs reversed based on the account type? That process only works when you use the Application as a point of entry into the Business Planning and Consolidation InfoCube.

4.

Which of the following are important to keep in mind when you use journal entries for an application? Answer: A, B, D, E A. If an existing journal template structure is changed, the journal entry tables are cleared and the audit trail would be lost however the InfoCube is unaffected. C. Journal entries are recorded in tables on the application server and they also update the Business Planning and Consolidation InfoCube. However, no DSO (Data Store Object) is involved.

290


2010

BPC440

Test Your Knowledge

5.

Journal control features include: Answer: A, C, D B. Tolerance groups like the ones in ECC FI don't exist here. E. Planning and Consolidation doesn't feature the closing of posting periods the same way ECC does, but you can use work status to prevent any further changes to the data.

6.

Which of the following best describes balance carry forward (BCF)? Answer: A, C, D B. BCF writes data into the next posting period. BCF copies current year retained earnings and writes it to prior year RE. Last year acquisitions and other activities get rolled into current years opening balance from a fixed asset perspective. E. The business rules for BCF include: source account, source datasrc, destination account and datasrc, reverse sign, and datasrc type.

7.

Which of the following are true statements regarding the 'Account Transformations? Answer: A, C, D B. Allows read and write capability for three dimensions: Account, Flow, and Datasrc. E. The source is not deleted.

8.

Your client has asked you to provide a synopsis of the Allocation function. Which of the following points should you include? Answer: A, B, E C. The components include: What, Where, Using, Total, and an optional Factor. D. The delivered components include: logic, package, program, process chain, business rules are not used for allocations. E. Allocations are flexible, they can be used for any section of your financials.

2010


291

Test Your Knowledge

9.

BPC440

Your boss needs a summary of what you learned in the Business Planning and Consolidation class about validations and so you would include which of the following: Answer: A, B, D, E C. If there is an out of balance the system writes a value to the 'Error' account. F. Account1, Flow1, and Sign1 form the left side of the equation which are matched up with the Account2, Flow2, and Sign2 dimension members.

292


2010

Unit 4 Currency Translation Unit Overview In this unit we will discuss the reasons to do currency translation, some of the concepts, and then we will get into the configuration and execution on live data.

Unit Objectives After completing this unit, you will be able to: • • •

Understand the high level concepts of currency translation. Configure business rules for a typical scenario. Analyze the data generated by the currency translation program.

Unit Contents Lesson: Currency Translation .................................................294 Exercise 12: Currency Translation .......................................307

2010


293

Unit 4: Currency Translation

BPC440

Lesson: Currency Translation Lesson Overview In this lesson we will address why currency translation is necessary, configure it, and analyze the results.


Understand the high level concepts of currency translation. Configure business rules for a typical scenario. Analyze the data generated by the currency translation program.

Business Example Financial data reported by consolidation units is usually transferred to consolidation in local currency. The local currency of a consolidation unit is not the same as the group currency. You need to translate this data to group currency before you can create consolidated financial statements.

Figure 260: BPC Currency Translation - 50,000 Foot Level

End of Month Currency Translation

294


2010

BPC440

Lesson: Currency Translation

Figure 261: Currency Translation - Big Picture

The currency translation job enables you to translate financial data reported by consolidations units from local to group currency. The type of currency translation you use often depends on relationships between your corporate group and the individual consolidation units (functional currency).

Figure 262: Currency translation: Periodic vs. Cumulative

Accounting guidelines determine whether to translate on a periodic or year to date (cumulative) basis. Income statement accounts are usually periodic while long term assets would be cumulative for example.

2010


295


BPC440

Here are a few key points regarding currency translation: • • • •

•

• •

•

The Currency conversion function is designed to convert local currency values into one or more reporting and/or group currencies. Currency conversion is designed to fully support currency translation in accordance with major Generally Accepted Accounting Principles. Currency conversion applies to both Financial and Legal Consolidation Applications to which a corresponding Rate Application has been referenced. When performing currency translation, in accordance with GAAP and other standards, different exchange rates (i.e. average, period end) and rules need to be applied to different accounts. The “business rule table” for currency conversion provides the business user with the ability to define each required combination of rates and logic, under a unique account rate type. The account rate type is then assigned, as a property, to the accounts to which it relates. Your application sets do not need to be set up for currency conversion if every monetary amount is represented in one currency only. If this is the case, the application does not need a Currency-type dimension or a Rate application, because no currency conversions will be performed. If the majority of your data is entered in just one currency, you do not need a Currency-type dimension. However, a few exceptions might exist, and these can be handled by duplicating a few members in the entity dimension. See the How To Paper on Configuring for Limited Currency Translation. The classic case is an American corporation having most of its operations in the US, but just a few subsidiaries operating in foreign countries, for example, one in Mexico and one in Canada. This type of scenario can be dealt with by just duplicating the few entities representing the foreign operations, to separate the local currency amounts from the translated amounts. This application would require a Rate application to store the exchange rates needed for the automatic translation, and a property in the Entity dimension to determine the local currency.

The end of month currency translation concept

296


2010

BPC440


Figure 263: Currency Translation Conceptual Matrix

OPL - Other P&L ANI - Annual Net Income OLO - Other assets, Liabilities, Owner Equity R - Remaining AD - Accumulated Depreciation BS - Balance Sheet CTA - Currency Translation Adjustment YTD - Year to Date Cum - Cumulative Per - Periodic When performing currency translation, different exchange rates such as average and period end rates, as well as rules, are applied. The business rule table for currency conversion contains the necessary rates and logic for a unique account rate type. The account rate type is then assigned, as a property, to the accounts to which it relates. When currency conversion runs, each account is then translated in accordance with the rules defined for the account rate type which has been assigned to that particular account. Pre-Requisites

2010


297


BPC440

Figure 264: Currency Translation Set Up

The following list provides a summary of the application setup required to support currency translation: • • •

• •

The application set must include a Rate application where exchange rates are stored. You must assign this rate application to any application that utilizes it. The application itself must include a Currency type dimension. The Currency dimension must include the properties REPORTING, whose values are Y or blank, and CURRENCY_TYPE, whose values are 'T' for transaction currency, 'R' for Reporting, and 'L' for local currency. The Entity dimension must include the property CURRENCY, whose values are valid Input Currencies. The Group dimension must include the property CURRENCY_TYPE with a value of 'G' for Group. It also includes the property GROUP_CURRENCY which contains the value of the group currency such as USD for a member such as G_CG2 for example. One member with a currency type value of 'N' is also needed for local currency. (We'll use member 'G_NONE' for that. Note: If you need multiple group currencies, you can include multiple values separated by a comma.

• • •

The Account dimension must include the property RATETYPE, whose values are valid Accounts in the Rate application. The TIMEID dimension must include the properties YEAR, PERIOD, TIMEID, and MONTHNUM. The DATASRC dimension is not mandatory for currency translation, but if you include it, the dimension must include the properties DATASRC_TYPE, whose values are I (input), M (manual), A (automatic), or L(Local), and IS_CONVERTED, whose values are Y, G, or Blank. Blank - If figures are entered in Group currency then no translation would occur. For example, this could be for a post-consolidation top level adjustment. Base level members should not be left blank. G - Figures are entered in Reporting Currencies and translated to Group Currency. For example, some journal adjustments might be entered directly on reporting currency and not in local currency.

298


2010

BPC440


• •

• •

Y - Figures are entered in LC and translated to Reporting and Group Currencies. This occurs when the FX Restatement package is executed or any other package that includes this package, like Consolidation. The FLOW dimension is not mandatory for currency translation, but if you include it, the dimension must include the property FLOW_TYPE. The INPUTCURRENCY dimension within the applicable Rate application must include the property MD, whose values are M for multiply rates or D for divide rates. The appropriate FXTRANS logic and program must be available. The DEFAULT logic must include a call to the FXTRANS logic, if the translation is to be performed whenever data is entered.

In summary, you must set up the following list of attributes for relevant dimensions in addition to the required attributes: Dimension

Attribute

ACCOUNT

RATETYPE

DATASRC

DATASRC_TYPE (I, M, A, or L) IS_CONVERTED (Y, G, or N)

ENTITY

CURRENCY (local currency)

FLOW

FLOW_TYPE (used to find the closing flow)

CURRENCY

CURRENCY_TYPE (currency type — Reporting, Local, or group)

TIME

YEAR, PERIOD, TIMEID, MONTHNUM

INPUTCURRENCY (with the Rate Application)

MD (indicator of multiply or divide)

Dimension

Attribute

The Rate Type determines whether an average or end of month rate is used for example. This is a key driver in this process because it controls the translation rule to apply to a given account. All accounts with no ratetype (ratetype = blank) will be translated with a factor of 1. All accounts with the reserved ratetype = 'NOTRANS' will not be translated. Required Components and Process Steps

2010


299


BPC440

Figure 265: Currency Components and Process Steps

The business rule table for currency conversion links to the necessary rates and logic for a unique account rate type. The account rate type is then assigned, as a property, to the accounts to which it relates. When currency conversion runs, each account is then translated in accordance with the rules defined for its account rate type.

Figure 266: Currency Logic and Package

Currency conversion can apply to both Financial and Legal Consolidation applications to which a corresponding Rate Application has been referenced. When performing currency translation, different exchange rates such as average and period end rates, as well as logic, are applied. Data in the Rate Application

300


2010

BPC440


Figure 267:

Caution: Since this is such a flexible tool, the example below is merely an illustration, it is not intended to imply how you should configure your system to do currency translation to meet currency translation requirements per your interpretation of the accounting standard you are using. Currency Business Rules The rate formula field contains arithmetic expressions combining any defined RATE as per the account dimension of the Rate cube. All rates with the property RateType equal to 'FX Trans' can be used. For example, if we have AVG and END in the rate cube: the opening value of any rate can be specified by adding the prefix 'OPE' to the rate itself such as 'OPEEND'. Note: The END rate is similar to the BCS 'Reference' rate. The 'OPEEND' does not need to exist in the rate cube since the system interprets it to mean the last months rate of the prior year. 'AS_IS' is key word that is supported in the formula field that means to leave a value untouched if it is already in the destination currency. 'AS_IS' cannot be combined with anything other than '-1'. 'AS_IS' is used when you need a historical rate.

2010


301


BPC440

Figure 268: Business Rule Definition

Note: The formula operands come from the rate application which is referenced to the legal application. •

• • •

• •

•

302

The source flow: can be a valid base level or parent member ID from the Flow dimension or several flow members as identified by one of their properties such as Subtables_Org in this case. Destination account: The account that stores the specific conversion. If empty, it is the same as the source account's member. Destination flow: The specific Accdetail member where translations are stored. If empty, then it is the same as the source subtable's member. Formula: This field can contain any arithmetic expression combining any defined rate as per the account dimension of the rate application. All rates with the ratetype property value of FX can be used. Force closing: If checked, the system will also write a value into the closing balance. Apply to periodic: This field should only be used in a YTD application for the cases in which the currency conversion should be performed on the Periodic values and not on the YTD values. If the box is checked, the engine calculates the difference between current period and prior period amounts, and applies to it the rate specified in FORMULA column. Entity FX type: This field can be used to enforce a given set of rules to only apply to a desired set of ENTITIES. If this field has a value, the rule will only be applied to the entities having a matching value in a similarly named property (FX_TYPE) of the ENTITY dimension.


2010

BPC440


Currency Key Words • • • • • •

END - uses the end of month rate as stored in the rate application. AVG - uses the average rate as stored in the rate application. COPYLC - translate the local currency to group or reporting currency with a factor of '1. OPEEND - the end rate of the last period of the prior year. AS_IS - Leave untouched a value already in the target currency. OPEAVG - the average rate of the last period of the prior year. Note: A rate type of 'blank' is supported for accounts that do not require translating such as headcount.

Translate the Opening

Figure 269: Opening - 2008.Dec

Translate the Increase

2010


303


BPC440

Figure 270: Increase

Translate the Ending

304


2010

BPC440


Figure 271: Ending

• •

The End rate for the period ending 2007.DEC is 1.2. The Average rate and the end rate for the period 2008.DEC is 1.5 and 1.3. Note: Here are some of the acronyms you may see when you do currency translation. CTA = Currency translation adjustment. PL = Profit and Loss, OE = Owners Equity, YTD = Year to Date, Per = Periodic, Cum = Cumulative, RE = Retained Earnings, BS = Balance Sheet.

Depending on how you interpret your accounting standard guidelines, you will translate different 'sections' of your financial statements in different ways. In other words, your financial statements are 'carved' up and translated using different rates, periodic or cumulatively, and with various account assignments for the adjustment postings. Notice how values that existed before the current year are being treated in a cumulative basis using the prior year spot rate whereas current values like an asset acquisition is being translated on a period basis with a current rate. This is getting close to the essence of currency translation although that is not the goal of the class. The Overall Process

2010


305


BPC440

Figure 272: Currency Translation Process

For the selection of the correct rate, the following rules apply: • •

• •

306

The source currency is derived from the property CURRENCY of the entity being translated. The rate to be applied during translation, such as ENDFLOW, HISTRATE, and so on, is derived from the property RATETYPE of the account being translated. The valid rate indicators are those corresponding to an account of the RATE application belonging to the GROUP FX Rate. The system does not convert any accounts with a rate type that is not a part of the currency conversion business rules and converts all accounts with a blank rate type with a factor 1.


2010

BPC440


Exercise 12: Currency Translation Exercise Objectives After completing this exercise, you will be able to: • Explain how to configure the currency translation business rules. • Execute the function and explain how the system generated the data.

Business Example You are performing legal consolidations since you have offshore operations, you need to translate all of the local currencies into the group currency.

Task 1: Exchange Rates Load the exchange rates into your Rate application. 1.

Go to your remote desktop in the BPC440_00 folder for Rates and open the 'Rates.csv' file. There should be rates for both 2007 and 2008 so the system can generate adjustment postings by comparing back to the prior year rates.

2.

In BPC for Excel, create a transformation file and save it without making any changes, then load the rate application.

Task 2: Currency Translation Business Rules Note: These business rules are not intended to model a solution where all statutory reporting requirements are met but rather are meant to be used as a learning device on how to change the 'logic' to meet the various methods to perform currency translation. Set up the currency translation business rules. Then, confirm that the fxtrans script logic is still in place and it matches the screen shot below. Caution: Use the drop down where available. 1.

In the LegalApp, configure the currency translation conversion rules as you see below. AccRateTyp

SrcFlow

DestAcc

DestFlow Formula

AVG

F_999

AVG

ENDFLOW

F_100

OPEEND

FrcClose


2010


307


BPC440

ENDFLOW

F_100

F_180

ENDOPEEND

ENDFLOW

F_120

ENDFLOW

F_120

ENDFLOW

F_999

END

HISTFLOW

F_999

END

AVGFLOW

F_999

HISTINV

F_999

AVG F_280

25815000 F_180

END-AVG

END-AVG END

Note: Brackets are optional in the Version for SAP NetWeaver. 2.

Confirm that your scrip logic matches the one shown below:

Figure 273: Currency Translation Logic

3.

Let's run a report in the LegalApp to see the data before we run the job. Use EVDRE to generate a report with both C_Acct and Flow in the rows and Groups in the columns. Use the following current view: Dimension

Member

Consgroup

NON_GROUP

C_Acct

12110300

C_Category

C_100


308


2010

BPC440


C_DataSrc

TotalAdj

Entity

C1000

Flow

F_Top

IntCo

Total

RptCurrency

LC

Time

2008.DEC

Measures

YTD

4.

Execute the Currency Translation in BPC for Excel by using the data manager.

5.

Let's refresh the currency report to see the data now. Can you see the new values for USD ?

6.

Now let's see if we can figure out how the system did the calculations. Fill out the grid below for two accounts. Hint: The End rate is 1.3. The Avg rate is 1.5, and the OpeEnd rate is 1.2. Acc

Flow

RateType

Dest.Acc Dest.Flow Rate Entity

Exch. Rates

11112000 F_999 25712000 F_999

Result Now you can look at the Currency report and the table you just filled in (unless you are really smart and you are just looking at the answer!) and you should be able to see what the system did! Have a nice day!

2010


309


BPC440

Solution 12: Currency Translation Task 1: Exchange Rates Load the exchange rates into your Rate application. 1.

Go to your remote desktop in the BPC440_00 folder for Rates and open the 'Rates.csv' file. There should be rates for both 2007 and 2008 so the system can generate adjustment postings by comparing back to the prior year rates. a)

Go to Start (on your remote desktop) → Documents → My documents → C-Drive → BPC440 → BPC440_## → Files→ Rate → Open the 'Rate.csv' file with Notepad. Does the data look reasonable? Notice the two rate entity types: AVG and END.

2.

In BPC for Excel, create a transformation file and save it without making any changes, then load the rate application. a)

In BPC for Excel →Open up the CV (current view) → Select the application drop down → Select the RATE application. Note: A transformation file is required for every data import in case a simulation is needed.

b)

Home → Manage Data → Maintain transformations→ Create new transformation → Validate and save transformation definitions → Call it 'RateTrans' → Save

c)

Go back one step → 'Upload data file'→ Select the Source File drop down → My Computer → C-Drive → BPC440 → BPC440_## Files → Rate→ Rates → Open → Use the drop down on the destination file → Save → Ok → Ok.

d)

Add the Import Data package: Select 'Planning & Consolidation' → Goto eData → More → Organize package list → Right click in the yellow area → Add package → Select the drop down for process chains → Open the folder 'Business Planning and Consoldiation: System → Select /CPMB/IMPORT → Select → Enter a name and description of IMPORT → Check off both the Admin and User task types → Add → Save → Ok.

e)

Go back one step(if necessary)→ 'Run a package' → Import → Run → Select the Rates import file → Select the RateTrans transformation file → Leave it set to 'Merge' → Select 'No' for the Default logic (there isn't any) → Next → Finish → Ok → View Status → Drill down on the log → Make sure you have accepted records → Close the pop-ups.


310


2010

BPC440


f)

Open an existing report: Select Excel Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Rate → BPC440 Rate Report → Open → Expand all. Save the report on your appset: Goto → eTools → Save Dynamic Template → Choose the Company Folder → Save.

Figure 274: Exchange Rate Report (your values may vary)

Note: Commas may appear rather than '.' as decimals indicators.

Task 2: Currency Translation Business Rules Note: These business rules are not intended to model a solution where all statutory reporting requirements are met but rather are meant to be used as a learning device on how to change the 'logic' to meet the various methods to perform currency translation. Set up the currency translation business rules. Then, confirm that the fxtrans script logic is still in place and it matches the screen shot below. Caution: Use the drop down where available. 1.

In the LegalApp, configure the currency translation conversion rules as you see below. Continued on next page

2010


311


BPC440

AccRateTyp

SrcFlow

DestAcc

DestFlow Formula

AVG

F_999

AVG

ENDFLOW

F_100

OPEEND

ENDFLOW

F_100

ENDFLOW

F_120

ENDFLOW

F_120

ENDFLOW

F_999

END

HISTFLOW

F_999

END

AVGFLOW

F_999

HISTINV

F_999

F_180

FrcClose

ENDOPEEND AVG

F_280

25815000 F_180

END-AVG

END-AVG END

Note: Brackets are optional in the Version for SAP NetWeaver. a)

In the Admin Console → Applications → LegalApp → Business Rules → Currency conversion rules → Enter the data as you see above. For example → Select the AVG rate type in the upper table → In the lower table → Enter F_999 for Source Flow and AVG for formula → Save without validating → OK →Now enter in the rest of the data using the same procedure. Save without validating → OK → Validate and confirm currency conversion rules rule table→ Ok.

Figure 275: AVG Rate Type


312


2010

BPC440


Caution: If you enter an Account Rate Type without any data in the detail, it will be deleted when you save.

Figure 276: ENDLFOW Rate Type

2.

Confirm that your scrip logic matches the one shown below:


2010


313


BPC440

Figure 277: Currency Translation Logic

a)

3.

Now let's go have a look at the logic for currency translation: In the LegalApp → Select Script Logic → Fxtrans → Make sure it matches the code above→ Enter 'CURRENCY = %RPTCURRENCY_SET%' if necessary → Validate and Save → OK.

Let's run a report in the LegalApp to see the data before we run the job. Use EVDRE to generate a report with both C_Acct and Flow in the rows and Groups in the columns. Use the following current view: Dimension

Member

Consgroup

NON_GROUP

C_Acct

12110300

C_Category

C_100

C_DataSrc

TotalAdj

Entity

C1000

Flow

F_Top

IntCo

Total


314


2010

BPC440


RptCurrency

LC

Time

2008.DEC

Measures

YTD

a)

Switch back to the LegalApp: In the current view → Select the application drop down → Select 'LEGALAPP'. Open an existing report: Goto the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal→ BPC440 Currency Report → Open → (select 'Yes' if prompted) Expand all. Save the report on to your Appset: Go to → eTools → Save dynamic templates →Company Folder → Save.

4.

Execute the Currency Translation in BPC for Excel by using the data manager. a)

Select the 'hypertext' Run Package in F24 → Financial Processes → FX Restatement → Run → Use the following members: Entity: C_Category: C_100 RptCurrency: USD Time: 2008.Dec

b)

5.

Next → Finish → OK → View status → Check the formula log for number of records processed → Cancel → Check the log → Close → Cancel.

Let's refresh the currency report to see the data now. Can you see the new values for USD ? a)

Select the Currency report and refresh it.

Figure 278: Currency Result for C1000


2010


315


6.

BPC440

Now let's see if we can figure out how the system did the calculations. Fill out the grid below for two accounts. Hint: The End rate is 1.3. The Avg rate is 1.5, and the OpeEnd rate is 1.2. Acc

Flow

RateType

Dest.Acc Dest.Flow Rate Entity

Exch. Rates

11112000 F_999 25712000 F_999 a)

Fill in the table above. To look up the rate type → Go to the Admin Console → Select the C_Acct dimension → Maintain dimension members. To look up the other columns except for the exchange rates → Open the business rules for the LegalApp → Currency conversion rules. Below you can see the answers although more accounts are spelled out. Account

Flow

RateType

Dest.Acc D.Flow Rate Entity

11112000 F_999 EndFlow

End

1.3

25712000 F_999 AvgFlow 25815000 F_180

End-Avg

1.3-1.5

12110300 F_100 EndFlow

OpeEnd

1.2

EndOpeEnd

1.3-1.2

Avg

1.5

End-Avg

1.3-1.5

End

1.3

12110300 F_100 EndFlow

F_180

12110300 F_120 EndFlow 12110300 F_120 EndFlow 12110300 F_999 EndFlow b)

Exch Rates

F_280

To see the results for all entities set your current view and run the provided report. Set your current view as shown below:


316


2010

BPC440


Figure 279: BPC440 Currency All Entities Current View

c)

Run the following report and note the USD have not been translated since that is the Group Currency: Goto the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → BPC440 Currency All Entites → Open → (Answer 'yes' if prompted) Expand All.

Figure 280: BPC440 Currency All Entities


2010


317


BPC440

Result Now you can look at the Currency report and the table you just filled in (unless you are really smart and you are just looking at the answer!) and you should be able to see what the system did! Have a nice day!

318


2010

BPC440


Lesson Summary You should now be able to: • Understand the high level concepts of currency translation. • Configure business rules for a typical scenario. • Analyze the data generated by the currency translation program.

2010


319

Unit Summary

BPC440

Unit Summary You should now be able to: • Understand the high level concepts of currency translation. • Configure business rules for a typical scenario. • Analyze the data generated by the currency translation program.

320


2010

BPC440

Test Your Knowledge


You are interested in sharing the conceptual information you learned in class with your fellow accountants. Which of the following would be correct to convey? Choose the correct answer(s).

2.

□

A

□

B

□

C

□

D

□

E

Currency translation is used to prepare a set of financials in a corporation's group currency with the potentially distorting effects of exchange rate fluctuations clearly presented. Currency translations for legal consolidations is usually run as a job at month end not as data is input into the system. Long term asset opening balances are translated normally using average periodic rates. Asset acquisitions are usually translated using average periodic rates. PL items are usually translated using average periodic rates.

Currency translation business rule tables have which of the following features? Choose the correct answer(s).

□ □ □ □ □ □ 3.

A B C D E F

Define the rates and logic to be applied to each Account Rate Type. Source flow member determination. Destination account. Source flow. Formulas using the Rate application account dimension. Force closing which closes the period.

The currency conversion setup includes which of the following? Choose the correct answer(s).

2010

□

A

□

B

□

C

□

D

□ □

E F

A rate application which is referenced to the legal application and stores the exchange rates used to translate into the reporting and group currencies. The currency property of the Entity dimension which designates the local operating currency of legal subsidiaries normally. Rate Type property in the account dimension which determines the rate and logic to be used in translation. Tcurr table which stores exchanges rates such as spot and historical. Currency business rules. The currency data manager package and process chain.


321

Test Your Knowledge

4.

BPC440

Currency translation calculations typically work as follows: Choose the correct answer(s).

322

□

A

□

B

□ □ □

C D E

Opening balance is bought in at the END rate plus the change in the END rates multiplied by the closing LC value. The change is bought over at the average rate plus the difference between the END and AVG rate multiplied by the LC . The closing balance is valued at the LC times the END rate. Translation differences can be written to separate flow members. Translation differences are also written to the journal document DSO.


2010

BPC440

Test Your Knowledge

Answers 1.

You are interested in sharing the conceptual information you learned in class with your fellow accountants. Which of the following would be correct to convey? Answer: A, B, D, E C: Long term asset opening balances are translated normally using end of month year to date rates.

2.

Currency translation business rule tables have which of the following features? Answer: A, B, C, E D: There is no source flow. E: The formulas use the rate application's account dimension members such as 'AVG' and 'END'. F: Force closing writes the movements to the closing balance if selected.

3.

The currency conversion setup includes which of the following? Answer: A, B, C, E, F D: The TCurr table is not used for Business Planning and Consolidation.

4.

Currency translation calculations typically work as follows: Answer: A, B, C, D E: There are no journal entries created for currency translation and Business Planning and Consolidation does not write to DSO's (Data Store Objects).

2010


323


324

BPC440


2010

Unit 5 Consolidation of Investments Unit Overview In this unit we will discuss the reasons for performing consolidation of investments, why you may want to automate it using SAP BusinessObjects Planning and Consolidation and then we will configure the system and execute COI on live data and report on the results.

Unit Objectives After completing this unit, you will be able to: • • • • • • •

Understand the basic purpose of COI. Understand the key concepts such as First and subsequent consolidation. Explain the basic concept of the Purchase Method. Identify the key properties that affect the COI processing. Configure Business Rules. Understand what the Business Rules do. Analyze the results of the elimination job.

Unit Contents Lesson: Consolidation of Investment Concepts ............................326 Lesson: Consolidation of Investments Architecture ........................333 Exercise 13: Ownership data, Business rules, and Running COI....367

2010


325

Unit 5: Consolidation of Investments

BPC440

Lesson: Consolidation of Investment Concepts Lesson Overview In this lesson we will focus on the concepts of COI.


Understand the basic purpose of COI. Understand the key concepts such as First and subsequent consolidation. Explain the basic concept of the Purchase Method.

Business Example Your corporation has a lot of legal subsidiaries and not all of them are wholly owned. There are a fair number of acquisitions and divestitures during the year as well and that has helped to create a very long manual process to eliminate ownership and book minority interest during closes so you are looking into automating that process as much as possible. Consolidation of Investments

Figure 281: Consolidation of Investments

Note: The method assignment is stored in the Ownership application as well. First Consolidation

326


2010

BPC440

Lesson: Consolidation of Investment Concepts

Figure 282: Course scenario: Investment Structure

Figure 283: First Consolidation (For an Acquisition)

2010


327


BPC440

When a subsidiary is first acquired, the process of first consolidation using the purchase method eliminates the investment against the equity of the subsidiary with the difference going to goodwill (US GAAP examples are coming up). Note: First consolidation as it relates to Planning and Consolidation is referring to the accounting entry generated when there is an acquisition or a change in the ownership percentage for example. Planning and Consolidation logs etc. do not have anything actually called 'First Consolidation'. In the US, direct shares are typically used but in Europe, group shares are normally used. An example of direct share would be: Company B owns 75% of C. The Group (indirect) share of A's ownership of C is 80% of 75% or 60%. Also, there are more than one criteria used to determine what method to use for the elimination such as the % of ownership or the amount of control a parent has. Generally speaking, if the ownership % is greater that 50% the purchase method will be used in the US but the equity method is used if the amount is less than 50%. The proportionate method is similar to the purchase method and is used more frequently in Europe. More on that later. Subsequent Consolidation

Figure 284: Subsequent Consolidation (of Earnings)

328


2010

BPC440


After the first consolidation, assuming there are no changes in ownership %'s etc., the parent and minority share of the subsidiary's earnings is determined. For example, if you own 80% of a subsidiary, you claim 80% of their annual net income (ANI) while the minority share is 20%. Also, goodwill may also be amortized (for non US companies only.) Note: Subsequent consolidation as it relates to 'Planning and Consolidation' is referring to the accounting entries generated when the subsidiary reports net income. Purchase Method Examples

Figure 285: COI Example - Purchase Method 100% @ 50,000

Note: Co A (Company A) is the buyer of Co B (Company B). The key point is that you cannot just aggregate (agg) or sum up the individual financial statements, values in common between the parent and subsidiary must be eliminated (elim). This subsidiary is wholly owned and was purchased at its book value so there is no goodwill. The investment was 50,000 and the equity of the subsidiary was 50,000 so they washed each other out. Dominating influence exists if the parent unit directly or indirectly owns the majority of the investee's voting rights, or is able to exercise such influence due to a contract, the articles of incorporation, and so forth.

2010


329


BPC440


This subsidiary is wholly owned and was purchased at market value so there is goodwill booked in this case. The investment was 80,000 (market value) and so there was goodwill of 30,000 since the subsidiary's equity was 50,000.


Only 80% of the subsidiary is owned in this example so there was a premium paid which is booked as goodwill and minority interest is also booked for the 20%. Goodwill of 40,000 is based on the parents share of the subsidiary equity which is 40,000 (.8 times 50,000) for which they paid 80,000 and voila ... you have goodwill! A Few Business Requirements

330


2010

BPC440


Figure 288: Getting Started With COI

2010


331


BPC440

Lesson Summary You should now be able to: • Understand the basic purpose of COI. • Understand the key concepts such as First and subsequent consolidation. • Explain the basic concept of the Purchase Method.

332


2010

BPC440

Lesson: Consolidation of Investments Architecture

Lesson: Consolidation of Investments Architecture Lesson Overview In this lesson we will review the set up, execution, and results of the ownership elimination in Planning and Consolidation primarily as it relates to the Purchase Method.


Identify the key properties that affect the COI processing. Configure Business Rules. Understand what the Business Rules do. Analyze the results of the elimination job.

Business Example You need to implement Planning and Consolidation to do all of your intercompany eliminations including ownership and so you are interested in the properties, business rules, logic, and the results generated by the programs. The process can be organized into 10 key steps:

Figure 289: 10 Key Steps for COI

Note: These steps include the set up and execution steps. Only the execution steps would need to be repeated every close and they do not have to be carried out in this exact order. Dimensions and Properties

2010


333


BPC440

Figure 290: Step 1: Dimension Members and Properties

Datasources have been established to represent the various types of automatic adjustments that would be made as part of the consolidation process. This allows easier tracking of data posting and lessens the chance of overwriting data between tow calculations. By adding a value of 'Y' to the IS_CONSOL property, the corresponding datasource will be included in the consolidation processing, otherwise they are ignored. By adding a value of 'Y' to the IS_CONVERTED property, the corresponding datasource will be included in the conversion from local to the desired currency, otherwise they are ignored. A value of 'A' for the DATASRC_TYPE is required for all elimination datasources. The Group Dimension

Figure 291: Step 1: Group Dimension Properties

Note: You will see postings against the 'E' entity in this set up. Notice how the 'G' member is linked to the 'E' member here. In the Ownership cube, the % ownership for example is recorded against 'G' member and Entity so that's how the system indirectly determines the 'E' postings.

334


2010

BPC440


Figure 292: Step 1: Group Dimension Members

To perform legal consolidation requires your application set to have an application designated for consolidation which references both a rate and an ownership application.

Figure 293: Step 2: Applications

The Ownership application is type: Non Reporting / Ownership. Its dimensions include Category and Time. Its Entity is the same as the Legal Application. O_Acct (OwnAccount) contains the Percentages, Methods, and Parent Positions. The Groups dimension contains the Consolidation Groups. The Ownership data: All data is entered for one specific Group. Ownership data is collected and stored By Entity and Intco. Percentages and Methods are by Entity. As a prerequisite to using consolidations, you must update some settings via the 'set application parameters' option from the web client. The parameters reference how organizational information from the ownership application is used for example. You did this back on day one and now you'll see how they (the ones that start with 'ORG' )are used in the Dynamic Hierarchy Editor (DHE).

2010


335


BPC440

Figure 294: Step 3: Application Parameters

Application Parameters COI related Application Parameters: • • • • • • •

Opening Balance: Enables the business rule table for balance carry forward. Org_Accountlist: Member id’s of the ownership account dimension that store methods, % consolidation and , % ownership. Org_Accountdown: member id of the ownership account that specifies the Position of a consolidation entity within the group. Org_intco: the 3rd party member in the Intercompany dimension. Org_ownershipcube: name of the linked Ownership application. Org_parentproperty: property name in the Groups dimension to define the hierarchy used in the dynamic hierarchy editor. Ownership_App: the consolidation logic requires the Ownership application to be listed here as well. Note: The properties that begin with 'Org' all relate to the dynamic hierarchy editor.

The Course Investment Structure

336


2010

BPC440


Figure 295: Investment Structure - Course Example

Step 4: Entering Methods, Parents, and Percentages into the Ownership Application and Run Ownership Calculation Enter any ownership changes into the Ownership cube, such as the acquisition of a new company, the sale or transfer of shares, and divestitures. Update consolidation methods and accounting methods appropriately. Also update percentage ownership and percentage consolidation within the group. The ownership application stores on a version and time dependent basis the overall ownership and consolidation percentage of each entity by group as well as the corresponding method of accounting to apply. The ownership calculation program then needs to be run in order to calculate the overall ownership within each group. You may also manually update the group percentages. Ownership data can be entered via the Dynamic Hierarchy Editor or via input templates. Note: The ownership values below are entered using the 'pown' O_ACCT member and LC. In the Ownership Application, the POWN ownership percentages are maintained either manually or calculated automatically. In the example below, they are entered manually via an input template.

2010


337


BPC440

Figure 296: Step 4 - Enter Percent Ownership Data

Ultimate ownership is a function for legal consolidation used to perform certain calculations used by he application (primarily in regard to calculating the group share of a subsidiary). This information is needed by the business rule library to properly consolidate the operations of various subsidiaries in accordance with GAAP. Note: For BCS folks, this means making the organizational hierarchy, assigning the ownership percentages, and assigning consolidation methodologies in the Ownership Application. • • •

• •

Account members represent ownership%, group positioning, consolidation method, etc. POWN - Percent ownership. How much is owned at a certain level? PCON - Percent Consolidation. What is the percent of consolidation, for example in the Proportionate method, what portion of the subsidiary should be included? PGROUP = Is the entity part of this group for consolidation purposes? (1 if yes) METHOD - By what method is the entity to be consolidated? Standard methods include: 30 for equity, 70 for proportionate, 86 for purchase, and 90 for holding (i.e., group parent).

Customers may decide to also enter the direct and indirect pown values instead of having the system derive them. Each group must have one and only one parent. Note: The data below is entered using 'I_NONE' intercompany member. The Ownership application also contains the method assignments, the position in the group (90 is holding), percent consolidation, and percent ownership. Below is an example of an input template for this data:

338


2010

BPC440


Figure 297: Step 4 - Before Ownership Calculation

The delivered ownership package would now be executed in the Ownership Application. You can see the ownership results below.

Figure 298: Step 4 -After the Ownership Calculation: CG1-2

2010


339


BPC440

Figure 299: After Ownership Calculation: CG3-4

Here's how to interpret the data:

Figure 300: Interpreting Ownership Data

Step 4 -The Dynamic Hierarchy Editor - User Interface The same data can also be maintained with the DHE.

340


2010

BPC440


Figure 301: Dynamic Hierarchy Editor (DHE)

DHE (Dynamic Hierarchy Editor) Key Features • • • • • • • •

Graphical view of ownership data. Drag and drop navigation. Data is stored in the Ownership InfoCube. Data is stored by category and period. You can copy from one period / category to another. The security task for Edit rights is provided. Methods and percentages can be easily entered. Navigation buttons include: Refresh, Move leaf up or down, Add child, Delete, Copy to, and Exit. When you choose to delete an entity for example, these are the options: – – –

Delete current node only. Delete current node and associated details. Delete only details associated with the current node.

Here's an example of the copy feature.

2010


341


BPC440

Figure 302: DHE - Copy Feature

Note: The DHE or an input template can easily be used to write the ownership data into the Ownership Application. How to handle consolidation group changes If an entity moves from one group to another, is acquired, or sold this is the process you could follow. But first of all, you need to know that ownership data is stored by month and year. Here is an example of entity C1000 in the G_CG2 group in December 2008.

Figure 303: DHE 2008.DEC

342


2010

BPC440


C1000 is being divested from the G_CG2 group and acquired by the G_CG3 group in January 2009. The method for C1000 in G_CG2 should be 'leaving during the year' and 'new' in G_CG3.

Figure 304: DHE - 2009.JAN

The 'Leaving' and 'New' rule types are quite easy to set up. Add two rows to the application automatic adjustments detail (only in the header) . Specify the destination datasrc along with the 'Leaving' and 'New' Adjustment ID. In the flow dimension, create two members and assign them the FLOW_TYPES 'vARSCPLEAVE' and 'VARSCPNEW'. When the system detects a new entity, it will move the values on the opening flow (the one with FLOW_TYPE = 'Opening') to the flow member with the property 'New'. When the system detects a divestiture (you must use a method of 'Leaving' for them), values will be moved from the opening flow to the flow with the FLOW_TYPE 'Varscpleave'. The relevant accounts should then balance to zero. How to enter data into the DHE Here's how to enter ownership data via the DHE from scratch:

2010


343


BPC440

Figure 305: How to use the DHE - Initial Screen

1.

2. 3.

Goto BPC for Excel in the Ownership Application: Select eSubmit → Manage Dynamic Hierarchies → Enter: • C_101 for C_Category • 2008.DEC for Time • G_H1 for Consgroup Expand the G_H1 folder → Select the G_CG1 node → Select the 'Add Child icon → Select C9000 → Ok With C9000 still selected → Check the Auto Fill Up and Show Empty boxes:

Figure 306: How to use the DHE - C9000 Initial Screen

Select the method and enter the PCON and POWN percentages: From the G_CG1 group → Double click the method cell → Select 90 (Parent) → Ok → Type 1 for PCON and POWN (don't hit enter) → See your results below:

344


2010

BPC440


Figure 307: How to use the DHE - C9000 Result

Add C1000 and C2000: Select the G_CG2 folder → Select the G_CG2 node → Select the 'Add Child' icon → Select C1000 and C2000 (use the ctrl key) → Ok

Figure 308: How to use the DHE - After adding C1000 and C2000

Select the method and enter the PCON and POWN percentages: From the G_CG2 group → Double click the method cell → Select 86 → Ok → Type 1 for PCON → Type .8 for POWN (don't hit enter) → In the G_CG1 group → Enter .64 for POWN → See your results below:

2010


345


BPC440


Add C3000/C4000 to the G_CG3 group and C5000/C5100 to the G_CG4 group.

Figure 310: How to use the DHE - After adding all subsidiaries

Set C3000 as the parent of the G_CG3 group but with the purchase (86) method in the G_CG1 group.

346


2010

BPC440



Enter the data as you see below for C4000. Note that the direct share is 75% however the group share is 60% since C3000 owns 80% of C4000.


Set up C5000 as the parent of the G_CG4 group.

2010


347


BPC440


C3000 uses the equity method and they are 30% owned.


The result is the same in terms of the data stored in the Ownership Infocube.

348


2010

BPC440


Figure 315: How to use the DHE - Overall Result

Business Rules A consolidation of investments method is assigned to every consolidation unit within each consolidation group by time period and version. The method assignment uses an "effective period" approach, which avoids the need to re enter repetitive definitions for each subsequent period, as long as the method remains consistent. You can make the assignments easier by using an inheritance logic to assign one method to the entire consolidation group. This default method is then overridden for individual units. Changing the accounting technique causes the system to automatically change the method. The system posts the Method Change function automatically when it recognizes a change in the accounting technique. Legal consolidation requires the set up of three business rules libraries, two business rules tables, and information in the ownership application. The business rules libraries are responsible for holding the rules, methods, and rules formulas that are used in the business rules and ownership setup. The business rules have details on the types of adjustments to make, The ownership application stores the additional financial data needed to process (which group owns what entity and for how much). The Delivered (sample) Appset Consolidation Rules The application set rules are normally used if possible, otherwise it is ok to create your own. These are logical identifiers that you will assign methods and formulas to. Rules by themselves do not have any programming logic associated with them in other words.

2010


349


BPC440

When the consolidation program is executed, it reads dimension properties, consolidation methods and %'s in the Ownership Application, and the business rule tables. The method assignments by entity and their percentages are read from the Ownership application. The business rules are broken down into Appset and Application sections. In the Appset, the Rules, Methods, and Formulas are defined. In the Application, the destination datasource is assigned to the method in the 'automatic adjustments'. In the 'automatic adjustment details', the source accounts, reverse signs, target accounts, and target flows, etc. are specified.

Figure 316: Step 5: Appset Consolidation Rules

The 'Consolidation Rules' hold various rule IDs for which formula details are later created. Basically if by combination of entity/intercompany entity you would have different ways of calculating group/minority/total values, then that would lead to creating a new rule. So for example, the rules for IC eliminations would differ from investment eliminations for purchase consolidated entities. When defining a rule, you need to make a unique identifier, provide a description and specify the rule type. Rule types can take on one of five fixed forms (proportional, equity, generic, new, and leaving). Rule010 Stock Holder Equities can be used to split equity into group and minority shares. Rule011 Result can be used to eliminate profit only on holding companies. Rule030 can be used to eliminate dividends from subsidiaries to parent entities. Rule040 Inter Company Elimination can be used to eliminate inter unit activities such asnd AP and AR.

350


2010

BPC440


Rule050 Internal Profits can be used to eliminate subsidiary profits. Rule051 can be used to eliminate internal profits in inventory. Rule200 and 210 are 'default' rules for the Equity and Proportional method that can be used by the system but are not assigned to the Automatic Assignment Details like the other rules, The rules have a description and a rule type which can be set to either 'Generic', 'Equity', 'Proportional', 'New', or 'Leaving'. Note: A blank is typically used however unless you are using the Equity or Proportional methods. This table defines the list of business rules that can be used in the application set. The rules are used in the formulas along with the methods. The 'Rule ID' is the identifier for the rule such as 'Rule010'. The description could say something like 'Equity, 100% Minority Part, Dividends, Stock Holder Equities, IC Elimination'. The 'Rule Type' can be one of five types that you want to use in the applications. The Appset Rules, Methods, and Formulas

Figure 317: Step 5: AppSet Business Rule View

The methods are used in the formula table to control the behavior of a given rule. Methods represent the various techniques used to consolidate (note that Global is equivalent to the Purchase Method).

2010


351


BPC440

These are assigned to the ownership data to tell the system by which methodology to consolidate a subsidiary and to the consolidations rules formulas to tell the system how to calculate. The method types can be one of seven different types: Note: New and Leaving are rarely used. When they are used to capture 'variation in scope', it is usually in conjunction with unique flow and datasrc members. 1. 2. 3. 4. 5. 6. 7.

Equity Proportional (Proportionate) Global (Purchase method) New Leaving (End of Year) Leaving (During the Year) Holding

The Consolidation Method table describes the Accounting methods available for use in the consolidation for each entity. The 'Method Code' can be a single value or a list separated by commas. 99 is used to designate all methods. The Method Name could say something like Leaving, Equity, Proportional, Global, Holding. Consolidation Rules Formula table The Consolidation Rules Formula table controls how the amounts or the destination accounts should be calculated. The behavior is controlled by the rule being used, the consolidation method assigned to the current entity, and its Intercompany partner, if applicable. Rules Formulas have the rule, the method and the formulas for ‘All’, Group, and Minority. Rule formulas govern the formula calculations for rules later entered in the business rules tables. In the example above, Rule 10 states that Entity is consolidated using the Global method (86). It is Valid for any Intco Member (99) and it uses 100% for the 'All' formula and % of Ownership for the Group formula and (1- % of Ownership = % of Minority) for the Minority Interest forumula. In row two above, Rule 20 states that where you have an entity with method 86 and an intercompany's related entity with method 30, then the percentage used in determining the adjustments would be 100% for 'All', POWN for 'Group' and 1-POWN for Minority.

352


2010

BPC440


In row three above, Rule 20 will use the same formulas as in row two if the entity uses method 90 and the intercompany entity uses method 30. Note: 'POWN' stands for percent ownership, in the system you will see MIN which is minority interest. The rule id is the name of the rule, use the drop down for this. The Entity method is defined in the Methods table and can be a single value or multiple separated by commas. The Intco method is also defined in the above methods table. 99 can be used to select Intco's with any method. All Formula: In 'English' the account in this field gets all of the value in the source account except the sign will be reversed. This is the % or formula to apply to the destination 'All' account property from the automatic adjustment detail table. The value can be an arithmetic expression combining any defined percentage in the account dimension of the Ownership application. All percentages where the property IS_input is equal to 'Y' can be used. Note the following guidelines: • • • •

In the Microsoft Platform, the members must be in square brackets such as [POWN], [PCTRL] (percentage control), [POWN]. Add the prefix 'I_' to add the IntCo value for example [I_POWN]. The syntax of the prior value can be combined with the syntax of the Intco value for example [I_PPOWN]. Add the prefix P to the percentage to use the prior value for example [PPOWN]. Note: The calculation of PCTRL in the business rule table is currently supported. However, the automatic calculation scripts of PCTRL (% of control) from investor/investee ownership percentage is not supported. You must manually input the PCTRL % into the ownership application in order to use it for further calculations.

Group formula: The account(s) in this field will use the group share (such as 80%) of the source account. Group formula is an expression that represents the percentage (or formula) to apply to the destination 'Group' account from the automatic adjustment detail table. The value can be an arithmetic expression combining any stored percentage as defined by the account dimension of the ownership application. All percentages where the property IS_Iput is equal to 'Y' can be used. The percentage must by enclosed in square brackets. Minority formula: The account(s) in the field receive the minority shareholders share of the source account such as 20%.

2010


353


BPC440

An expression that represents the percentage (or formula) to apply to the destination minority account from the automatic adjustment detail table. An arithmetic expression combining any stored percentage as defined by the account dimension of the ownership application. All percentages where the property IS_Input is equal to 'Y' can be used. The percentage must be enclosed in square brackets. Application Business Rule Tables (examples are coming up)

Figure 318: Step 6: Application Business Rules

Automatic adjustments represent the headers for various elimination rules that are of free form design. These are linked to various details in the automatic adjustment details tables. Any adjustment ID can be created. The rest of the fields restrict the behavior of the overall rule. The adjustment types may cause additional system functions to occur (i.e., equity causes the system to automatically zero out the subsidiary's financials so that it is not reported as per the equity method). The datasource members need to have a datasrc_type property value of 'A' (Automatic). The rule id comes from the consolidations rules in the AppSet. There are five possible adjustment types: But typically this is blank except for Equity and Proportionate. • • • • •

Generic Equity Proportional New (acquisitions) Leaving (divestitures)

Multilevel calculations are available, Adjustment level 0 means just one level. The adjustment level field must contain an integer value ranging from 0 to 99 and can be used to order the sequence of execution of the various ELIM rules, if desired. Here is a summary of the columns in the Automatic Adjustments table: •

354

Adjustment ID: The identifier for the adjustment rule.


2010

BPC440


•

• •

•

Source data source: This field may contain the following values: Blank (all DATASRC members). A valid base level or parent member ID from the DATASRC dimension. A list of members of the DATASRC dimension, as defined by filtering the members using a value of the DIMLIST property (or any property whose name begins with “DIMLIST”). Destination DataSource: ID of a DATASRC member with a valid Datasource Type = A. Group type filter: The CONSO_TYPE property value from the Groups (Currency) dimension. If, for example, you have the Group GROUP1 with conso_type = A, all the Automatic Eliminations with Blanks are available for all groups. The Automatic Eliminations with Group_filter member = A are available for GROUP1 and all groups with Group filter member = A. Adjustment type - This field may contain the following values: 1.

2. 3.

4.

•

•

•

Adjustment level: This field must contain an integer value ranging from 0 to 99 and can be used to order the sequence of execution of the various ELIM rules, if desired. Entity property filter: This field is only utilized for intercompany eliminations. If this field contains a value, the system will look for the existence of a corresponding PROPERTY in the ENTITY dimension, and will only perform the elimination if the ENTITY and the INTCO partner have the same value in this property. Other dimension filter: This field can be used to define a filter controlling the region where the elimination can be applied. It can contain the following values: – – – –

2010

Blank: A generic ELIM rule E: “Equity” - This value indicates that this rule is used on the entities using an Equity method (i.e., having a method of type “E”). P: “Proportional” - This value indicates that this rule is used on the entities using a Proportional method (i.e. having a method of type “P”) N: “New” - This value indicates that this rule is used on the entities just entering into the consolidation perimeter (i.e., having a method of type “N”). L: “Leaving” - This value indicates that this rule is used on the entities that are leaving the consolidation perimeter (i.e. having a method of type “L”) In case this field has a non-blank value, there are never details associated with it in the clcELIM table.

Blank (No Filter). An expression defining one or more filters. Any dimension of the MAIN cube (example: CATEGORY=BUDGET). The SIGNEDDATA amount (example: SIGNEDDATA> 10).


355


BPC440

–

•

•

Any ACCOUNT of the OWNERSHIP cube (example: METHOD = 85). – Any ACCOUNT of the OWNERSHIP cube as defined in Prior period (example: PPOWN <>0, where PPOWN is Prior period’s POWN account). – Alternatively, any valid SQL expression filtering the values in any desired way can be used. In this case the syntax must strictly comply with SQL requirements (single quotes around the members IDs, etc.) – Any ACCOUNT of the OWNERSHIP cube as assigned to the INTER_COMPANY partner (example: I_POWN < POWN). The filters can be concatenated with the “AND” operand. Forced destination members: This field can be used to enforce the destination member of any dimension existing in the MAIN cube. This field may contain a 'Blank' (No Change) or an expression enforcing the value for one or more dimensions of the MAIN cube. Each dimension must be separated by a comma (for example: Category=Budget, Entity= NewYorkBranch) Local currency: This field can be used to control the reporting currency for which the elimination is to be performed. It may contain either the ID of a valid reporting currency or it may be left blank, to indicate that the GROUP currency must be used.

Business Rule Schema

Figure 319: Business Rule Schema

Automatic Adjustment Details Automatic adjustments details contain the account and flow (i.e., AccDetail) information that determines how eliminations should post for a particular adjustment category. They can be thought of as the information needed to

356


2010

BPC440


automatically post line items for a consolidation entry. This is done through a process of linking an adjustment category to consolidation rules formulas. Together with the account/flow information this allows the system to post the appropriate eliminations into a unique datasource for ease of tracking. Each line of the business rul table represents a unique posting relationship. Muliple lines can reference the same automatic adjustment category and consolidation rules formula, but each line considers only the accounts/flows listed for purposes of posting with respect to that line. Here is a summary of the columns in the Detail table: • • • •

• • • •

Elimination Rule : A valid Elimination ID from the Elimination Headers. An ELIM rule definition may span multiple lines Source Account : can be a valid base or parent Account, a valid TYPEELIM or DIMLIST property in the account dimension. Accounts to be eliminated. Reverse Sign : “Y” or Blank. This will invert the value calculated is flagged. Destination All Accounts : Account Destination 1 (Link to the Rules Table), can be a valid base or parent Account, a valid TYPEELIM or DIMLIST property in the account dimension Destination Group Account : Account Destination 2 (Group Impact) Destination Minority Account : Account Destination Minority Account: What minority account will used. Destination Equity Account : Account Destination 4 (If Equity Method replace All Accounts) Rule ID : Valid rule of the Appset Consolidation Table. This links the automatic adjustment detail back to the consolidation rules formula. This determines what amounts are placed into the accounts specified. The math is determined as follows: 1. The account to eliminate in the automatic adjustments details table (linked to the consolidation rules formulas via the Rule ID) is multiplied by the 'ALL' Formula in the consolidations rules formula table and stored to the 'Destination All' account. In the consolidation rules formulas, a value of 1 means multiply by 1, a value of POWN means multiply by the percentage owned, a value of I_POWN means multiply by the percentage the parent owns of the Intercompany trading partner, and a value of 1-POWN means multiply by the percentage not owned (i.e., the minority share). 2. The Account to eliminate in the automatic adjustments details table (linked to the consolidation rules formulas via the Rule ID) is multiplied by the 'GROUP' formula in the consolidations rules formula table and stored to the 'Destination Group' account.

2010


357


BPC440

3. The Account to eliminate in the automatic adjustments details table (linked to the consolidation rules formulas via the Rule ID) is multiplied by the 'Minority' formula in the consolidations rules formula table and stored to the 'Destination Minority' account. • • • • •

•

•

Source Flow : Source Flow, can be blank to specify all flows, a valid base or parent member, a set of members identified with a DIMLIST property Destination Flow : Blank or Valid Member of the Flow Dimension Force Closing : Y or Blank. If Y, generate an extra record on the “Closing” Flow (F_999 in our case) Invert Entity / Interco : “Y” or Blank. Entity Code and Intco Code are inverted Force Intco Member : Blank or Valid Intco Member. Can be used to explicitly specify a member of the IntCo dimension to be used in the posting instead of the existing member. If left blank, the existing IntCo member will not be charged. Periodic : Should only be used in a YTD application for the cases in which the ownership percentage should be applied on the periodic values. If the field is set to 'Y', the system calculates the difference between the current period and prior period amounts, and it applies to it the ownership percentages specified for ALL, GROUP, and MINORITY in the consolidation rules formula table. The result is added back to prior period's value as written in the current period. Swap Entity - Intco : If flagged, will swap out the member of the Legal Entity dimension with that of the IntCo member.

Application Business Rules

Figure 320: Step 6: Application Business Rule Summary

358


2010

BPC440


Figure 321: Design Time Business Rule Validation

Consolidation Logic

Figure 322: Step 7: Sample Logic

Normally, this would also include the currency translation into a group as well. (We'll do that in the lab). This logic is delivered along with the related data manager package and process chain. The Consolidation Data Package In the NetWeaver release, the 'Groups' dimension is typically used whereas the Microsoft release referred to it as the 'Consolview' dimension.

2010


359


BPC440

Figure 323: Step 8: Data Package

Rates and Investment Sample Data

Figure 324: Step 9: Load Rates and Legal Application Ownership Data

Note: C9000 already owns I_C1000 since it has a closing flow. The rates are all per group currency which is USD in this case. The Investment data has the investment (source) account , the investee (C1000), the parent (C9000), and the amount.

360


2010

BPC440


Figure 325: Step 10d - Run the Program

Purchase Method Example without Goodwill These are the business rules that we are going to use. They are very flexible and usually there is more than one way to achieve a certain result. The rules shown below represent everything you need to configure, in the slides that follow, these are broken down into their components so it is easy to see how they work with data. We are also using several Datasrc members for clarity. However, you may want to balance by Datasrc in real life in which case only one would be needed. Caution: None of these examples are attempting to demonstrate compliance with any particular accounting standard. The intent is to show techniques to generate various outcomes so that you walk away with the skill set that you need to implement your specific project related business requirements.

2010


361


BPC440

Figure 326: COI Business Rule Example

This the data, both before and after. This is a very straightforward example where the parent C1000 buys the subsidiary C2000 for 80,000 to acquire an 80% share. The subsidiary's equity is 100,000, so there in no goodwill in this case. Note: The values in the illustration below are in Group Currency. Note: See the upcoming example with Goodwill.

Figure 327: Step 10 - The Results!

Below is the record generated for the investment elimination.

362


2010

BPC440


Figure 328: Investment Entry

Below is the record generated for the Equity Elimination.

Figure 329: The Equity Entry (in the purchase method approach)

Below is the record generated for the minority interest. The ownership percentage is 80%.

2010


363


BPC440

Figure 330: Minority Interest

Purchase Method with Goodwill Typically you will have Goodwill when using the Purchase Method. Here is one way to account for it. The graphic below shows the two incoming data records along with the business rules set up. The 100,000(LC) in 12311000 account will translated to 130,000 when you run consolidation. 80% of the subsidiary has been purchased so that means 50,000 of goodwill should be generated. Note: The system does not calculate Goodwill however you can use a little creativity to generate it. In practice, manual journal entries may also be required.

364


2010

BPC440


Figure 331: Purchase Method with Goodwill Example - Set Up

In the results below, you can see that Goodwill has been booked.

Figure 332: Purchase Method with Goodwill - Result

Profit Elimination Example In subsequent consolidations, the profit from the subsidiary needs to be split between the Group and the Minority shareholders. The Minority Interest retained earnings also need to be updated. Here is one way to do it:

2010


365


BPC440

Figure 333: Profit Elimination

366


2010

BPC440


Exercise 13: Ownership data, Business rules, and Running COI Exercise Objectives After completing this exercise, you will be able to: • How to provide the required ownership data by using input schedules and the dynamic hierarchy editor. • Configure the business rules to do ownership eliminations. • Understand the entries generated by the system as a result of your configuration.

Business Example Your company has many legal subsidiaries and they are not all 100% owned so the manual close takes a long time. You are interested in seeing how easy it is to perform this automatically with the planning and consolidation application.

Task 1: Ownership Data


Enter Ownership Data into the ownership application. 1.

Update the ownership related web parameters in the Legalapp and Ownership applications. Continued on next page

2010


367


2.

BPC440

Set the application parameters for Ownership as shown: KeyID

Value

ORG_ACCOUNTLIST

METHOD,PCON,POWN

ORG_ACCOUNTOWN

PGROUP

ORG_INTCO

I_NONE

ORG_OWNERSHIPCUBE

OWNERSHIP

ORG_PARENTPROPERTY

PARENT_GROUP

OWNERSHIP_APP

OWNERSHIP

3.

Now we will update the data in the Ownership Application.

4.

Use a provided EVDRE input template 'BPC440 Enter Pown Data' to enter ownership percentages. You may need to use commas as the decimal indicator.

Figure 335: Enter Pown Data

You may need to enter the % with a ',' separator. Your instructor will let you know. 5.

Open the 'BPC440 Groups Methods Pcon' input schedule from your BPC440_## folder enter the data as shown below and save the template to your appset.

6.

Copy the 'CalcOwn' package to the user and admin groups via the 'Organize Package List' in eData, and run the Ownership calculation package using the following data selections:


368


2010

BPC440


7.

Refresh the 'Group Method Pcon' template to see the Ultimate ownership percentages. Then run the Dynamic Hierarchy Editor so you can see the delivered user interface to manage ownership data. Note: If the system does not calculate the POWN values as you see below, enter them in and save to the application. There is a known issue for the current support pack.

Figure 336: Group Methods Pcon After the Calculation: G_CG1-2


Task 2: Consolidation of Investments Configure the business rules for ownership elimination. 1.

Review the consolidation methods in your Appset as shown below:


2010


369


BPC440

Figure 338: Consolidation Methods

2.

Review the consolidation rule formulas in your Appset as shown below.

Figure 339: Consolidation Rules as Delivered

3.

The product comes with many permutations in the formula table. In real life you may choose not to clear out these entries but in class we need to know which formulas are being used. Therefore, delete all existing rows, then add the entries below. Hint: To delete multiple entries at one time: Hold the left mouse button down and drag over several rows without letting up → Select the delete key → Voila!

4.

Set up the automatic adjustments header in your LegalApp as shown below:


370


2010

BPC440


Adjust.ID Src DataSrc

DestDatasrc

Adjust.Type

AdjLevel

ELCOI1

AJ_COI1

0

ELCOI2

AJ_COI2

0

ELCOI3

AJ_COI3

0

Note: It is not required to use a separate datasrc for each Adjustment ID but it is a big advantage for visibility. 5.

Set up the automatic adjustments details in your LegalApp as shown below: Adj.ID

SrcAcc

Rev

DestAllAcc DestM.A.

RuleID

ELCOI1

12311000

NO

12311000

RULE060

ELCOI2

25110000

NO

25110000

RULE010

ELCOI3

25110000

NO

24111000

RULE010

6.

There is a delivered package for Legal Consolidations (Ownership and Inter Company Eliminations). In BPC for Excel, go into 'Organize Package List' and save it to the User and Admin Package task type.

7.

In the LegalApp, execute the CONSOLIDATION package.

8.

Run the 'Nested Rows' dynamic template to see the results for the C1000 / C2000 elimination. Leave C_Acct in the rows but put it in the 1st expansion and Entity in the 2nd. Put C_Datasrc in the columns. Suppress zeroes on all expansions, remove the 'hide row and column keys', select the memberset 'LBAS(2),Self' for C_Acct, 'C1000,C2000' for Entity, and 'Bas,Self' for C_Datasrc. . Use the following current view and save it as 'Consolidation'.

Result You should recognize the investment, equity, and minority interest elimination entries ... can you feel the power? Note: If you don't get the same results, check the business rule tables.


2010


371


BPC440

Figure 340: Purchase Method Elimination Result

372


2010

BPC440


Solution 13: Ownership data, Business rules, and Running COI Task 1: Ownership Data


Enter Ownership Data into the ownership application. 1.

Update the ownership related web parameters in the Legalapp and Ownership applications. a)

Goto Web Administration: From the Admin Console or Excel → Available Interfaces → Interface for the Web → That takes you to the launchpad screen → Select Available interfaces (again) → 'Administration' (web) → and you end up in the Web Administration screen:


2010


373


BPC440

Figure 342: Web Administration

b)

'Set Application Parameters' → Make sure your Appset is BPC440_## and the Application is the LegalApp: KeyID

Value

ORG_ACCOUNTLIST

METHOD,PCON,POWN

ORG_ACCOUNTOWN

PGROUP

ORG_INTCO

I_NONE

ORG_OWNERSHIPCUBE

OWNERHSIP

ORG_PARENTPROPERTY

PARENT_GROUP

OWNERSHIP_APP

OWNERSHIP

Note: The 'Org_' etc parameters will be needed for the dynamic hierarchy editor.

2.

c)

Set the parameters as shown above.

d)

Use 'Update' to save the parameters.

Set the application parameters for Ownership as shown:


374


2010

BPC440


KeyID

Value

ORG_ACCOUNTLIST

METHOD,PCON,POWN

ORG_ACCOUNTOWN

PGROUP

ORG_INTCO

I_NONE

ORG_OWNERSHIPCUBE

OWNERSHIP

ORG_PARENTPROPERTY

PARENT_GROUP

OWNERSHIP_APP

OWNERSHIP

a)

Make sure your Appset is BPC440_## and the Application is Ownership.

b)

Set the parameters as shown above. Note: The YTD setting is not applicable to the ownership application.

c)

Use 'Update' to save the parameters. Here are the definitions of the 'ORG' properties: •

•

• • •

• •

Org_Accountlist: Member id’s of the ownership account dimension that store methods, %consolidation, and %ownership. These will appear in the dynamic hierarchy editor. Org_Accountdown: member id of the ownership account that specifies the Position of a consolidation entity within the group for example 90 will be used for 'parents'.. Org_intco: the 3rd party (external) member in the Intercompany dimension to which all ownership calculations are posted. Org_ownershipcube: name of the linked Ownership application. Org_parentproperty: property name in the Groups dimension to define the hierarchy used in the dynamic hierarchy editor. The Group property that will contain the legal rollup members. Ownership_App: the consolidation logic requires the Ownership application to be listed here as well. USElim: Allows the use of the business rule tables for US Eliminations. Note: US Elimination is an easy way to do one sided eliminations. The first to use it happened to be a US company! This can be used for sales and cogs eliminations for example.

• Note: All of the properties which begin with 'ORG...' are related to the Dynamic Hierarchy Editor.


2010


375


3.

Now we will update the data in the Ownership Application. a)

b) 4.

BPC440

Log on to the Ownership Application: In BPC for Excel →Select the Application drop down in the current view → Select the OWNERSHIP application. Application

Ownership

ConsGroup

NON_GROUP

C_Category

C_100

Entity

H1

IntCo

I_NONE

O_Acct

Pown

Time

2008.Dec

Measure

Periodic

Set the current view as you see above.

Use a provided EVDRE input template 'BPC440 Enter Pown Data' to enter ownership percentages. You may need to use commas as the decimal indicator.


You may need to enter the % with a ',' separator. Your instructor will let you know. a)

Goto the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Ownership → Select 'BPC440 Enter POWN Data' → Open → Select 'Planning & Consolidation' → Expand all → Enter the POWN data as shown above → 'Send data' (in F24).

b)

Save the template: Goto → eTools → Save dynamic templates → Company → Save. Continued on next page

376


2010

BPC440


5.

Open the 'BPC440 Groups Methods Pcon' input schedule from your BPC440_## folder enter the data as shown below and save the template to your appset. a)

In the Ownership application → Goto the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Ownership → Select 'BPC440 Groups Methods Pcon” → Open → Expand all → Try entering 1 data point as a quick test → Send data (in I26)→ Now Enter the rest of data as shown below → Send data.

Figure 344: Before Ownership Calculation

b) 6.

Goto eTools → Save dynamic templates → Company → Save.

Copy the 'CalcOwn' package to the user and admin groups via the 'Organize Package List' in eData, and run the Ownership calculation package using the following data selections: a)

Add the Ownership calculation package: In BPC for Excel for the Ownership Application→'Planning & Consolidation' → eData → More → Organize package list → Right click in the yellow area → Add package. → Select the process chain drop down → Business Planning and consolidation: System → Select '/CPMB/OwnershipCalc' → Select → Check the user and admin package task types → Enter Package name and description 'CALCOWN' → Add → Save → Ok Continued on next page

2010


377


b)

BPC440

In the template 'Groups Methods Pcon' → Select 'Run package' in I24 → CALCOWN → Run → Select 'Calculate ultimate % of ownership using group share method' → Enter POWN as the input account → Select 'Yes' to replace any manual input.

Figure 345: Calcown Package - POWN

c)

Next → Do not request the system to calculate any proposals:

Figure 346: Calcown proposal


378


2010

BPC440


d)

Next → Use the data selection below → Next → Finish → Ok → View Status → Cancel → Close → Cancel. Note: The proposal feature uses the threshold percentages entered into the appset consolidation methods for 'share range' (pown) and 'percent control' (pctrl). Dimension

Value

C_Category

C_100

Time

2008.Dec

Groups

G_CG1 to G_CG4

Note: This package does not provide the number of records submitted but we will look at the data in the next step anyway. 7.

Refresh the 'Group Method Pcon' template to see the Ultimate ownership percentages. Then run the Dynamic Hierarchy Editor so you can see the delivered user interface to manage ownership data. Note: If the system does not calculate the POWN values as you see below, enter them in and save to the application. There is a known issue for the current support pack.



2010


379


BPC440


a)

Go back to the 'Group Method Pcon' schedule → Expand All → The ownership percentages should appear as shown above. Can you feel the power?

b)

We could have entered the data above via the DHE. Since you may like to do that on your project, let's become familiar with. Open the Dynamic Hierarchy Editor: While still in the Ownership application → Goto eSubmit → Manage dynamic hierarchies → Make your settings equal to the following:

c)

Dimension

Value

C_Category

C_100

Time

2008.DEC

ConsGroup

G_H1

Open up the nodes and left click on 'G_CG1'


380


2010

BPC440


Figure 349: Dynamic Hierachy - G_H1

Note: You should not need to change any data at this point. If you do, let your instructor know.

Figure 350: Dynamic Hierachy - G_H1 Close Up

d)

Select the node G_CG2 to see the entities that are part of that group:

Figure 351: Dynamic Hierarchy - G_CG1

e)

Select the C1000 entity to see the groups that it belongs to: Continued on next page

2010


381


BPC440

Figure 352: Dynamic Hierarchy - C1000

The ownership data is now complete and we can proceed with the business rules. Note: Check out the 'how to' steps on the DHE in your lecture notes on how to build your investment structure from scratch.

Task 2: Consolidation of Investments Configure the business rules for ownership elimination. 1.




382


2010

BPC440


a)

2.

In the Admin Console → Open up your AppSet → Business rule library → Consolidation methods→ Confirm that yours is similar to the one above. Note: Global is the Purchase Method.

Review the consolidation rule formulas in your Appset as shown below.

Figure 354: Consolidation Rules as Delivered

a)

3.

In the Admin Console → Open up your AppSet → Business rule library → Consolidation rule formulas → Confirm that yours is similar to the one above. Note: In the screen capture above, the Rule ID 'RULE010' is selected and therefore the lower half of the screen is displaying the equity methods below.

The product comes with many permutations in the formula table. In real life you may choose not to clear out these entries but in class we need to know which formulas are being used. Therefore, delete all existing rows, then add the entries below. Hint: To delete multiple entries at one time: Hold the left mouse button down and drag over several rows without letting up → Select the delete key → Voila! a)

In the Admin Console → Open up your AppSet → Business rule library → Consolidation rules formulas→ Select RULE010 → Delete all Entity Methods in the lower half of the table→ Select RULE011 → Delete all Entity Methods in the lower half of the table → Repeat for every Rule ID → Save without validation. Continued on next page

2010


383


BPC440

Figure 355: After Deletion of all Entity Methods

b)

Add the two Entity Methods shown in the table below → OK → Validate and confirm consolidation rules formulas rule table → OK. RuleID

4.

Ent.Meth. IntCoMeth.

AllForm.

GroupForm.

Min.Form.

RULE010 86

99

1

POWN

1-POWN

RULE060 90

99

1

POWN

1-POWN

Set up the automatic adjustments header in your LegalApp as shown below: Adjust.ID Src DataSrc

DestDatasrc

Adjust.Type

AdjLevel

ELCOI1

AJ_COI1

0

ELCOI2

AJ_COI2

0

ELCOI3

AJ_COI3

0

Note: It is not required to use a separate datasrc for each Adjustment ID but it is a big advantage for visibility. a)

5.

In the Admin Console → Open up your AppSet → Applications → LegalApp → Business rules→ Automatic Adjustment Details → Fill in the header of the table as you see above → Save without validation → OK.

Set up the automatic adjustments details in your LegalApp as shown below:


384


2010

BPC440


Adj.ID

SrcAcc

Rev

DestAllAcc DestM.A.

RuleID

ELCOI1

12311000

NO

12311000

RULE060

ELCOI2

25110000

NO

25110000

RULE010

ELCOI3

25110000

NO

a)

24111000

RULE010

In the Admin Console → Open up your AppSet → Applications → LegalApp → Business rules→ Automatic Adjustments Details → Fill out your table details as you see above → Save without validation → OK → Validate automatic adjustments details rule table → OK. Here is an example of what yours should look like:

Figure 356: Application Adjustment Details: ELCOI1

Now all of your business rules at the AppSet and Application level are complete and ready to be tested. 6.

There is a delivered package for Legal Consolidations (Ownership and Inter Company Eliminations). In BPC for Excel, go into 'Organize Package List' and save it to the User and Admin Package task type. a)

Access the Legalapp in Excel: In BPC for Excel →Expand the current view → Use the drop down to select the LEGALAPP.

b)

Add the Consolidation package: Select 'Planning & Consolidation' → eData → More → Organize Package List → Right click in the yellow area → Add Package → Select the drop down to 'view all process chains' → Select the App group called 'Business Planning and Consolidations: System' → Select '/CPMB/Legal_Consolidation' → Choose the 'Select' button. Select the User and Admin Package Task Type → Enter a package name and description of 'CONSOLIDATION' → Add → Save → Ok.

c)

Access the package parameters: Goto eData → More → Organize Package List → CONSOLIDATION → Right click → Modify package:


2010


385


BPC440

Figure 357: Organize Package List: Modify Package

d)

Confirm that the parameters refer to the GROUP dimension: Select the 'View Package' icon as shown below:.

Figure 358: The 'View Package' Icon

e)

Select the 'Advanced' button → Input '%GROUP_DIM%' instead of '%CURRENCY_DIM%' if necessary:


386


2010

BPC440


Figure 359: Advanced Settings

f)

Ok → Save 3 times → Ok.


2010


387


7.

BPC440

In the LegalApp, execute the CONSOLIDATION package. a)

b)

In BPC for Excel in the LegalApp → Select 'Home' → Manage Data → Run a package → CONSOLIDATION → Run → Select the data region members as follows: Dimension

Member

C_Category

C_100

Consgroup

G_CG2

Time

2008.DEC

Next → Finish → Ok → View Status→ Review the log entries → Do you have records generated for the currency translation into the group? → Do you have records generated for Consolidation? → Return to Excel. Since this exercise deals with the Purchase method, we are interested in CG2.


8.

Run the 'Nested Rows' dynamic template to see the results for the C1000 / C2000 elimination. Leave C_Acct in the rows but put it in the 1st expansion and Entity in the 2nd. Put C_Datasrc in the columns. Suppress zeroes on all expansions, remove the 'hide row and column keys', select the memberset 'LBAS(2),Self' for C_Acct, 'C1000,C2000' for Entity, and 'Bas,Self' for C_Datasrc. . Use the following current view and save it as 'Consolidation'. Continued on next page

388


2010

BPC440


a)

Select the Home icon → Reporting and Analysis → Build a report using a dynamic template → Page down → Nested Rows → OK. Open the column group → Leave C_Acct in the rows →but put it in the 1st expansion and Entity in the 2nd. Put C_Datasrc in the columns → Suppress all zeroes by placing 'Y' in cells F51, G51, H51 → Remove the setting 'hide row and column keys' in C52.

b)

Make these memberset selections: In F48 → Enter the memberset 'BASMEMBERS' → In G48 → Enter 'C1000,C2000' for Entity → In H48 → Select 'BAS,SELF' for C_Datasrc

Figure 361: Control Panel for Consolidation Report (Gorgeous!)

c)

In eTools → Workbook options → un-check 'Expand on current view change' → Ok → Hide column N and M → Un hide row 43 → Hide row 44 → Right justify the column headers (in P43 and Q43) → Use the current view below → Expand All. Note: If you receive a message 'A member could not be found ... ', select ok and set your data view to hierarchy. Application

LegalApp

ConsGroup

G_CG2

C_Acct

1

C_Category

C_100

C_Datasrc

TotalAdj

Entity

CG2

Flow

F_Top

IntoCo

Total

RptCurrency

USD

Time

2008.Dec Continued on next page

2010


389


d)

BPC440

Measure

YTD

Application

LegalApp

Save the report: Go to eTools → Save Dynamic Template → Company Folder → Enter 'Consolidation' → Save.

Result You should recognize the investment, equity, and minority interest elimination entries ... can you feel the power? Note: If you don't get the same results, check the business rule tables.

Figure 362: Purchase Method Elimination Result

390


2010

BPC440


Lesson Summary You should now be able to: • Identify the key properties that affect the COI processing. • Configure Business Rules. • Understand what the Business Rules do. • Analyze the results of the elimination job.

2010


391

Unit Summary

BPC440

Unit Summary You should now be able to: • Understand the basic purpose of COI. • Understand the key concepts such as First and subsequent consolidation. • Explain the basic concept of the Purchase Method. • Identify the key properties that affect the COI processing. • Configure Business Rules. • Understand what the Business Rules do. • Analyze the results of the elimination job.

392


2010

BPC440

Test Your Knowledge


Your closing activities take less than an hour for COI since most of your subsidiaries are wholly owned so there would not be any benefit of automating the COI manual process. Determine whether this statement is true or false.

□ □ 2.

True False

What statements are true for the purchase method? Choose the correct answer(s).

3.

□

A

□

B

□

C

□

D

□

E

First consolidation eliminates the sub's equity against the parent's investment. During first consolidation, any difference between the investment and the parent's share of the sub's equity is written to goodwill. The purchase method only adjusts the investment for market value changes in the subsidiary. The purchase method is typically used in the US where the parent has a majority of the shares or has controlling interest over the subsidiary. Annual net income of the subsidiary is split between the parent and the minority shareholders during subsequent consolidation activities.

If a subsidiary reports $150m of annual net income, the corporation would report $100m if they own 67% of the subsidiary's shares while minority stockholders would report $50m. Determine whether this statement is true or false.

□ □

2010

True False


393

Test Your Knowledge

4.

BPC440

Which of the following describe the COI process? Choose the correct answer(s).

5.

□

A

□

B

□

C

□

D

□ □

E F

When the consolidation program is executed, it reads dimension properties, consolidations methods and %'s in the Ownership application. The 'dimlist' (or related property) in the account dimension can be used as a selection criteria for accounts to be included in the source of the calculation. The method assignments by entity and their percentages are read from the Dynamic Hierarchy. The business rules are broken down into Appset and Application sections. In the Appset, the Rules, Methods, and Formulas are defined. In the Application, the destination datasource is assigned to the method in the 'automatic adjustments'. In the automatic adjustment details, the source accounts, reversal signs, target accounts, and target flows, are specified.

Which of the following are included in the 10 key steps? Choose the correct answer(s).

□ □ □ □ □ □

394

A B C D E F

Set up the dimension members and properties. Create the IC Matching Application. Set the application parameters. Configure the business rules at the Appset level. Configure the automatic adjustment bus rules in the Legal App. Input methods, position, and percentages in the Ownership application.


2010

BPC440

Test Your Knowledge

Answers 1.

Your closing activities take less than an hour for COI since most of your subsidiaries are wholly owned so there would not be any benefit of automating the COI manual process. Answer: True True: It would not be prudent to automate COI if most or all of your subsidiaries are wholly owned. The only caveat would be Sarbanes Oxley concerns.

2.

What statements are true for the purchase method? Answer: A, B, D, E C. The equity method only adjusts the investment for market value changes in the sub and leaves the investment on the parent's books.

3.

If a subsidiary reports $150m of annual net income, the corporation would report $100m if they own 67% of the subsidiary's shares while minority stockholders would report $50m. Answer: True Absolutely! Annual net income is split up and distributed based on ownership %'s.

4.

Which of the following describe the COI process? Answer: A, B, D, E, F C. The method assignments by entity and their percentages are read from the Ownership Application. The DHE is an user interface to enter the data.

5.

Which of the following are included in the 10 key steps? Answer: A, C, D, E, F B. The IC Matching application is not required but if the customer wants to use it, they would create it in step 2.

2010


395


396


BPC440

2010

Unit 6 Inter Company Eliminations Unit Overview In this unit we will earn about the Intercompany Matching application. We will also discuss the basic concepts of eliminating inter unit activity, we'll configure the system, test it, and report on the results.

Unit Objectives After completing this unit, you will be able to: • • • • • • • •

State the possible reasons to use an IC Matching application. List the master data, properties, logic, and packages required. Understand the output generated from the IC Matching application. Recite the business reasons for eliminating inter company activity. Identify the most important dimension properties that relate to inter unit eliminations. Make the related configuration changes in the business rule tables. Analyze and understand the results. Discuss the options to carry out Inter Company eliminations.

Unit Contents Lesson: Inter Company Matching ............................................398 Exercise 14: Inter Company Matching...................................407 Lesson: Inter Unit Elimination and US Elimination .........................420 Exercise 15: Accounts Payable / Receivable Elimination .............431 Exercise 16: Intercompany (US) Elimination ...........................443

2010


397

Unit 6: Inter Company Eliminations

BPC440

Lesson: Inter Company Matching Lesson Overview In this lesson we will discuss the business reasons to consider using an IC Matching application that will perform matching of intercompany transactions between the legal entities. We'll also cover the master data required, the properties, logic, and packages.


State the possible reasons to use an IC Matching application. List the master data, properties, logic, and packages required. Understand the output generated from the IC Matching application.

Business Example During the close, your company has been struggling with differences in the inter company ARAP elimination. One of the problems is that accountants in one area don't have access to see the data for the other divisions they do internal business with. You are also interested in matching on transaction currency but that is not included in the Legal Application. The option of using one application with a different Datasrc for the IC data would make work status on Datasrc more complex. For these three main reasons, we need to consider using the IC Matching Application.

398


2010

BPC440

Lesson: Inter Company Matching

Figure 363: Traditional Inter Company Matching Process

Inter company booking concentrates into each entity the declarations and reported balances of all other entities versus a specific entity. This then allows business users within each reporting entity to run a report that matches all of its declarations and reported balances against the balances of the rest of the entities without the need to assign to each owner read-access into other entities. This function also automatically generates the bookings that make the Inter company declarations match and support the passing of posting detail to the actual consolidation application. You use the Inter company Booking business rule table to define the posting rules the system uses in generating the entries to match the Inter company balances and declarations.

2010


399


BPC440

Figure 364: Advantages of a Peer to Peer Matching Process

Figure 365: Inter Company Matching Application

For the purpose of resolving intercompany differences, here are the pros and cons:

400


2010

BPC440


Pros and Cons for a separate Inter Company Matching Application Topic

Pro

You can use different dimensions than the Legal Application

X

Easier to restrict what data people can access

X

Con

An additional application to maintain

X

The 'balanced' data would need to be loaded to the Legal Application

X

Note: Ideally, if these differences can be resolved in the source system before the data is imported into the BPC InfoCube, the BPC matching process could be eliminated. The Inter Company Matching Application

Figure 366: Inter Company Matching

The following are required to support an application to perform intercompany matching: • • • • •

The application must include an Intercompany dimension of type I. The intercompany dimension must include the property ENTITY, whose values are Entity names. The Entity dimension must include the property ELIM, whose values are Y or blank. The currency and inter company booking business rule table must be set up. A data manager package executing the intercompany logic must be available.

The values entered in the following properties drive default elimination logic:

2010


401


BPC440

Dimension

Property

Length

Content

Account

Pintco

20

Y, S, or blank

Entity

Elim

1

Y or blank

Intercompany

Entity

20

The entity ID corresponding to this intercompany member

Currency

Reporting

1

Y or blank

Note: The Pintco property uses a value of 'Y' for those members that should be considered for intercompany matching. The Booking Function in General

Figure 367: Inter Company Booking

402


2010

BPC440


IC Matching MetaData

Figure 368: IC Matching Dimension Properties

Note: The () indicate the dimension type. U = User defined. The IS_Converted property is used to indicate whether a datasrc should be included in the currency translation or not. IC_Origine is used to identify the origin datasrc (I) and the destination datasrc (D1, D2, C1, C2) used by the ICData Logic (SpicData stored procedure in Microsoft platform). Application Type

2010


403


BPC440

Figure 369: Building IC Matching Applications

Dimensions

Figure 370: IC Matching Dimensions

Business Rules

404


2010

BPC440


Figure 371: IC Matching Business Rules and Result - Seller

Figure 372: Example: Buyer Rule Type

System Constants

2010


405


BPC440

Figure 373: IC Matching System Constants

The Logic and Package

Figure 374: Intercompany Booking Logic & Package

The intercompany reconciliations process is handled by a program called ICBOOKING. Running the ICDATA.LGF logic file via the corresponding ICDATA Package runs intercompany reconciliation. Running the ICBOOKING.LGF logic file via the corresponding ICBooking package runs intercompany reconciliation and posts differences.

406


2010

BPC440


Exercise 14: Inter Company Matching Exercise Objectives After completing this exercise, you will be able to: • Identify the components required to do IC matching. • Understand the difference between the ICData and ICBooking programs. • Create reports to analyze the results.

Business Example During the close, your company has been struggling with differences in the inter company ARAP elimination. One of the problems is that accountants in one area don't have access to see the data for the other divisions they do internal business with. You are also interested in matching on transaction currency but that is not included in the Legal Application. The option of using one application with a different Datasrc for the IC data would make work status on Datasrc more complex. For these three main reasons, we need to consider using the IC Matching Application.

Task 1: IC Components and Pre Requisites Review the logic(modify it if necessary), business rules, packages, and master data related to the IC Matching Application that you carried out in the previous exercises. 1.

Review the Script logic files in the ICMatching application. What two script files are unique to IC Matching (ICM)? What name is the system constants using for the account dimension?

2.

We need to set up the Currency Translation and Intercompany Booking Business Rules for it as you can see below:


2010


407


BPC440

Figure 375: IC Matching Currency Conversion Business Rule: AVG

Figure 376: IC Matching Currency Conversion Business Rule: ENDFLOW

3.

Review the Master Data in the ICAccount and ICDataSrc. What's the RateType for the IC AP and AR accounts? Can we 'convert' the currency for the Input DataSrc?

4.

Add the Packages in BPC for Excel in the ICMatching Application.

Task 2: Evaluate the data then Execute Currency Translation, ICData, and ICBooking 1.

Let's run a report to see the data before we run the job. Use the Nested Row template to generate a report with both ICAccount and Entity in the rows and Group in the columns. Save it as 'ICM Currency'. Set the rows to 'basmembers' with zeroes suppressed and the columns to LC and USD. Use the following current view:


408


2010

BPC440


2.

3.

4.

Dimension

Member

ConsGroup

NON_GROUP

C_Category

C_100

Entity

CG2

Flow

F_999

ICAccount

anything

IC DataSrc

Input

Intco

Total

RptCurrency

LC

Time

2008.Dec

TrnCurrency

T_USD

Measures

Periodic

Dimension

Member

Run the Fx Restatement Package for the following selections. Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

USD

Time

2008.DEC

Run the IC Data Package for the following selections. Execute the provided EVDRE BPC440 IC Matching Summary report to analyze the results. Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

USD

Time

2008.DEC

Run the IC Booking Package for the following selections.


2010


409


BPC440

Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

USD

Time

2008.DEC

Result

Figure 377: IC Matching Summary After Booking

Now we know how to set up an Intercompany Matching Application, identify the required components, build supporting reports, and understand the potential value to the eliminations process.

410


2010

BPC440


Solution 14: Inter Company Matching Task 1: IC Components and Pre Requisites Review the logic(modify it if necessary), business rules, packages, and master data related to the IC Matching Application that you carried out in the previous exercises. 1.

Review the Script logic files in the ICMatching application. What two script files are unique to IC Matching (ICM)? What name is the system constants using for the account dimension? a)

Go to the Admin Console → Applications → ICMatching → Script Logic → Note the two files unique to ICM: ICDATA and ICBOOKING. Open the system_constants.lgf → Note that 'ICAccount' is being used as the account dimension.

b)

Make sure the FXTRANS logic file looks like the one below: Open up the Fxtrans file → confirm that the currency statement is: CURRENCY = %RPTCURRENCY_SET%.

Figure 378: IC Matching FXTRANS Logic

2.

We need to set up the Currency Translation and Intercompany Booking Business Rules for it as you can see below:


2010


411


BPC440

Figure 379: IC Matching Currency Conversion Business Rule: AVG


412


2010

BPC440


Figure 380: IC Matching Currency Conversion Business Rule: ENDFLOW

a)

In the Admin Console: Open the ICMatching App → Business Rules → Currency Conversion Rules → Enter the data as you see above: AVG rate type with formula AVG → ENDFLOW rate type with END formula.. Validate currency conversion rules rule table → OK

b)

Now set up the Intercompany booking rule: Select the Business Rule: Intercompany Booking → Enter the information in as you see below → Validate and confirm intercompany booking rules rule table → OK. Parent Matching Account

CTLICEND00

Type

Seller Rule

Other Destination Dimension Booking Destination Datasrc

ICDIFF

Max booking amount

10000

Debit Account

ICDIFF01

Debit Flow

F_999

Debit Intco Credit Account

LI16870000

Credit Flow

F_999

Credit Intco Note: The 'Seller' type rule: This means the Seller will receive any variances.


2010


413


3.

4.

BPC440

Review the Master Data in the ICAccount and ICDataSrc. What's the RateType for the IC AP and AR accounts? Can we 'convert' the currency for the Input DataSrc? a)

Select the ICAccount dimension → Maintain dimension members → Note the RateType for IC AP AR is Endflow.

b)

Select the ICDataSrc dimension → Maintain dimension members → Note the 'IS_Converted' property for INPUT is 'Y'.

Add the Packages in BPC for Excel in the ICMatching Application. a)

In BPC for Excel → Switch to the ICM application if necessary via the application drop down → Select 'Planning & Consolidation' → eData → More → Organize Package List → Right click in the yellow area → 'Add Package' → Select the Process Chains drop down→ Go to the folder: Business Planning and Consolidation: System → Select the '/CPMB/ICData' →

b)

Select → Check off the 'User and Admin Package' task types→ Name and Description: ICDATA

c)

Add → Save → Ok.

d)

Repeat the above process for ICBooking.

Task 2: Evaluate the data then Execute Currency Translation, ICData, and ICBooking 1.

Let's run a report to see the data before we run the job. Use the Nested Row template to generate a report with both ICAccount and Entity in the rows and Group in the columns. Save it as 'ICM Currency'. Set the rows to 'basmembers' with zeroes suppressed and the columns to LC and USD. Use the following current view: Dimension

Member

ConsGroup

NON_GROUP

C_Category

C_100

Entity

CG2

Flow

F_999

ICAccount

anything

IC DataSrc

Input

Intco

Total

RptCurrency

LC


414


2010

BPC440


Time

2008.Dec

TrnCurrency

T_USD

Measures

Periodic

Dimension

Member

a)

Select the 'Home' icon → Reporting & Analysis → Build a report using a dynamic template → Nested Rows → Ok → Open the group '+' in column J → Unhide any hidden rows. Put RptCurrency in Expansion 3 → In H48 → Enter: LC,USD → Set both rows to 'BASMEMBERS' in F48 and G48 → Enter 'Y' for both rows for zero suppression Hide columns M and N → Remove the hide key setting in C52→ Expand All → You should only have LC and no USD.

Figure 381: ICM Currency Report - Before Translation

Go to → eTools → Save dynamic templates → Company Folder → Call it 'ICM Currency' → Save. 2.

Run the Fx Restatement Package for the following selections.


2010


415


BPC440

Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

USD

Time

2008.DEC

a)

In BPC for Excel → Home → Manage Data → Run a package → In the Financial Processes Folder → Select the FX Restatement package → Run → Select the data region above → Next → Finish → Ok → View Status → Go back to Excel.→ Go to the ICM Currency report → Expand all → Do you have USD values now?

Figure 382: ICM Currency Report - After Translation

3.

Run the IC Data Package for the following selections. Execute the provided EVDRE BPC440 IC Matching Summary report to analyze the results. Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

USD

Time

2008.DEC

a)

In BPC for Excel → Manage Data → 'Run a package' → Select the IC Data package → Run → Select the data region above → Next → Finish → Ok → View Status → Go back to Excel.

b)

Open the provided report from your C Drive: Goto the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → IC Match → BPC440 IC Matching Summary → Open → Set your current view according to the table below→ Expand all → Do the results make sense? You just copied the data to different datasrc members which could then be used to control the visibility of the information. Continued on next page

416


2010

BPC440


Figure 383: IC Matching Summary - After IC Data

c) 4.

Dimension

Member

ConsGroup

NON_GROUP

C_Category

C_100

Entity

CG2

Flow

F_999

ICAccount

anything

IC DataSrc

Input

Intco

Total

RptCurrency

LC

Time

2008.Dec

TrnCurrency

T_USD

Measures

Periodic

Dimension

Member

Save the report→ eTools → Save dynamic templates → Company → Save.

Run the IC Booking Package for the following selections.


2010


417


BPC440

Dimension

Member

Entity

C1000,C2000

C_Category

C_100

RptCurrency

USD

Time

2008.DEC

a)

In BPC for Excel → Manage Data → Run a package → Select the IC Booking package → Run → Select the data region above → Next → Finish → Ok → View Status → Go back to Excel.Go to the ICMatching Summary → Expand all → Do the results make sense? Notice that the Buyer (C2000) received the difference.

Result

Figure 384: IC Matching Summary After Booking

Now we know how to set up an Intercompany Matching Application, identify the required components, build supporting reports, and understand the potential value to the eliminations process.

418


2010

BPC440


Lesson Summary You should now be able to: • State the possible reasons to use an IC Matching application. • List the master data, properties, logic, and packages required. • Understand the output generated from the IC Matching application.

2010


419


BPC440

Lesson: Inter Unit Elimination and US Elimination Lesson Overview In this lesson we will discuss the eliminations of inter company activities such as accounts payable and receivable, sales and cost, etc. We'll also discuss the key properties, the business rules and the logic involved as well. The option called 'US Elimination' option will also be addressed here.


Recite the business reasons for eliminating inter company activity. Identify the most important dimension properties that relate to inter unit eliminations. Make the related configuration changes in the business rule tables. Analyze and understand the results. Discuss the options to carry out Inter Company eliminations.

Business Example The units to be consolidated report item values for inter unit receivables and payables. Sales revenue has been produced within the group by exchanging goods and services with affiliated companies. Goods produced internally within the group remain partly in inventory. On the sale, a profit has been generated that needs eliminating. Inter Company Elimination Options

420


2010

BPC440

Lesson: Inter Unit Elimination and US Elimination

Figure 385: BPC Elimination Options

Figure 386: Simplified Inter Unit Elimination

2010


421


BPC440

The types of intercompany activity which require elimination include: • • • • • •

Intercompany accounts payable and accounts receivable. Intercompany loans and interest. Intercompany profit on fixed asset transfers. Intercompany royalties. Intercompany revenue and cost of goods sold. Intercompany dividends.

Figure 387: Elimination of IU Payables and Receivables

A consolidated balance sheet shows only payables and receivables that relate to non-affiliated (third-party) companies. Payables and receivables resulting from the exchange of goods and services within the corporate group must be eliminated otherwise they are double counted. In the example above, the system interprets the elimination difference between the receivables record of unit A and the payables record of unit B as miscellaneous receivables and posts this automatically.

422


2010

BPC440


Figure 388: Elimination Schema

Note: The consolidation logic, data package and process chain that is used for COI also eliminates inter company activity. The diagram above is an illustration. For clarity, it does not show the abap program or the process chain. When the consolidation program is executed, it reads dimension properties and the business rule tables. The 'dimlist' property in the account dimension can be used as a selection criteria for accounts to be included in the source of the calculation. For example, you could use ARAP for the accounts payable / receivable elimination. The business rules are broken down into Appset and Application sections. In the Appset, the Methods, and Rule Formulas are defined. In the Application, the destination datasource is assigned to the adjustment id which is then assigned to the source accounts, reverse signs, target accounts, and target flows.

2010


423


BPC440

Figure 389: APAR Configuration

Figure 390: ARAP Related Dimension Properties

424


2010

BPC440


Figure 391: ARAP Logic & Data Package

Consolidation rules define the formulas to use in calculating the amounts to post. Business rules define the balances upon which automatic adjustments are made and the items such as accounts and flows to which calculated amounts are posted. The formulas contain the rules and the entities are being included indirectly via the method that is assigned to them. For example Rule40 is being applied to all entities using methods 86 and 90. Note: The Rules and Formulas are located in the Admin Console in the Appset business rule library. The automatic adjustment and details can be found in the Legalapp under business rules.

Figure 392: ARAP Example - Before

2010


425


BPC440

Figure 393: ARAP Example - After

InterCompany (US) Elimination In the Version for NetWeaver, logic based eliminations are not possible. Therefore, 'US Eliminations' becomes an option to perform simplified eliminations. Although this was heavily used in the US, it may be advisable to refer to it simply as 'IC Elimination'.

Figure 394: US Eliminations

When reporting on the Financial results of a selected group of entities, one may wish to see the results for the group net of all Inter-Company activity within the group. When utilizing a Legal Consolidation application, Inter-Company eliminations are normally handled as part of the “Automatic Adjustments” function. A unique requirement when dealing with inter unit elimination entries is that they should only be reflected in any given group if both the entity and the partner entity which it was doing business with are part of the group. For each of these data sources it is then possible to define the corresponding destination data source under which the elimination postings should be posted.

426


2010

BPC440


US elimination functionality addresses the posting of inter-company eliminations in scenarios where a full legal consolidation application is not required such as within a standard Financial application.

Figure 395: US Elimination - Pre Requisites

Below you can see a sample account dimension and business rule table. The US Elimination business rule can be used in a Financial and / or a Consolidation type application.

Figure 396: IC Elimination Account dimension and Business Rule

The Entity dimension in the example below is set up to store postings against base level members (E_CGx) that represent the group that they belong to. The property value for the 'group level' entities is 'Y'.

2010


427


BPC440

Figure 397: IC Elimination Entity Dimension

The logic is shown below:

Figure 398: IC Elimination Logic

You can see the results below in the AJ_USELIM datasrc member. Currency translation would need to be run prior.

428


2010

BPC440


Figure 399: IC Elimination Results

2010


429


430


BPC440

2010

BPC440


Exercise 15: Accounts Payable / Receivable Elimination Exercise Objectives After completing this exercise, you will be able to: • Configure business rules for AP/AR Eliminations. • Discuss all of the components required to carry out eliminations. • Analyze the eliminations data generated by the consolidations program.

Business Example Your legal subsidiaries are transferring goods and services to each other and we need to eliminate the inter company accounts payable and receivables for the transactions that have not cleared yet so that we only report external AP AR on the consolidated balance sheet.

Task 1: APAR Business Rules Identify the Appset consolidation rules required for APAR, add to the formulas, and then configure the LegalApp Automatic Adjustment Business Rules. 1.

Which Method is used?

2.

In the Admin Console, which Consolidation Rule Formula 'Header' is used for IC Eliminations?

3.

In the Consolidations Rules Formulas 'Details', add the following rows: RuleID


All Form. GroupForm.

RULE040

86

99

1

1

RULE040

90

99

1

1

Min.Form.

The Group Formula value of '1' will drive an offset of 100% into each partners PLUG account. 4.

In your LegalApp business rules for automatic adjustments details, add the header data as you see below: (ELPAR stands for Elimination of Payables and Receivables)


2010


431


Adjust.ID

BPC440

Src DataSrc

ELPAR

5.

DestDatasrc Adjust.Type AdjLevel AJ_ELIM

0

Set up the automatic adjustments details in your LegalApp as shown below: (if a column is not shown, then it should be blank.) Adjust.ID

SrcAcc

ELPAR ELPAR

Rev

DestAllAcc

DestGrpAcc

RuleID

11301100 NO

11301100

APAROFF- RULE040 SET

21171000 NO

21171000


6.

In the LegalApp, go to Excel and execute the Consolidations package for C_Category: C100; Time: 2008.DEC; Groups: G_CG2.

7.

Run the 'BPC440 AR AP Elim' report Use the following current view. We are evaluating the AP AR between C1000 and C2000. Application

LegalApp

Consgroup

G_CG2

C_Acct

1

C_Category

C_100

C_Datasrc

TOTALADJ

Entity

CG2

Flow

F_Top

IntoCo

Total

RptCurrency

USD

Time

2008.Dec

Measure

YTD

Result Your Report should look similar to this one:


432


2010

BPC440


Figure 400: AP AR Elimination Result

Note: The EVDRE report above is restricted to just those accounts and datasrc members that are relevant to the AP AR elimination.

Task 2: Optional: Look at the results in the LegalApp InfoCube From the BW Server, go to RSA1 and display the original records loaded that relate to the IC Elimination as well as the records generated by the system. 1.

Log on to the BW Server.


2010


433


BPC440


2.

Go to the 'relative' of the 'Admin Console' in BPC, the 'Data Warehousing Workbench', search for your AppSet and right click to display the data in your LegalApp InfoCube.


434


2010

BPC440


Solution 15: Accounts Payable / Receivable Elimination Task 1: APAR Business Rules Identify the Appset consolidation rules required for APAR, add to the formulas, and then configure the LegalApp Automatic Adjustment Business Rules. 1.

Which Method is used? a)

2.

In the Admin Console, which Consolidation Rule Formula 'Header' is used for IC Eliminations? a)

3.

In your BPC440_## appset → Goto the business rules library→ Consolidations Methods → We'll use the Global 86 'Purchase' method → No changes are required.

Go to the Admin Console → In your Appset → Business Rule Library → Consolidation Rule Formulas → Rule040 is used for IC Eliminations → Don't leave this screen.

In the Consolidations Rules Formulas 'Details', add the following rows: RuleID


All Form. GroupForm.

RULE040

86

99

1

1

RULE040

90

99

1

1

Min.Form.

The Group Formula value of '1' will drive an offset of 100% into each partners PLUG account. a) 4.

With RULE040 selected → Add the rows above → Validate and confirm consolidations rules formulas rule table → Ok.

In your LegalApp business rules for automatic adjustments details, add the header data as you see below: (ELPAR stands for Elimination of Payables and Receivables)


2010


435


Adjust.ID

BPC440

Src DataSrc

ELPAR

a)

5.

AJ_ELIM

0

In the Admin Console → Open up your AppSet → Applications → LegalApp → Business rules→ Automatic Adjustments Details → Input the data above into the header as you see above → Stay on this screen

Set up the automatic adjustments details in your LegalApp as shown below: (if a column is not shown, then it should be blank.) Adjust.ID

SrcAcc

ELPAR ELPAR

a)

6.

DestDatasrc Adjust.Type AdjLevel

Rev

DestAllAcc

DestGrpAcc

RuleID

11301100 NO

11301100


21171000 NO

21171000


With ELPAR still selected → Input the data above into the detail (lower) section → Validate and confirm automatic adjustments details rule table → OK.

In the LegalApp, go to Excel and execute the Consolidations package for C_Category: C100; Time: 2008.DEC; Groups: G_CG2. a)

In BPC for Excel → Go to the LegalApp → Manage Data → Run a package → CONSOLIDATION → Run → Select the following data region: C_Category: C_100; Time: 2008.DEC; Groups: G_CG2.

b)

Next → Finish → Ok → View Status → In the log you should see records processed by the consolidation logic → Go back to Excel. Note: The currency translation took place when you did the purchase COI elimination.

7.

Run the 'BPC440 AR AP Elim' report Use the following current view. We are evaluating the AP AR between C1000 and C2000. Application

LegalApp

Consgroup

G_CG2

C_Acct

1

C_Category

C_100 Continued on next page

436


2010

BPC440


C_Datasrc

TOTALADJ

Entity

CG2

Flow

F_Top

IntoCo

Total

RptCurrency

USD

Time

2008.Dec

Measure

YTD

a)

Goto the 'Windows Button' on the upper left → Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → BPC440 AR AP Elim → Open → Set your current view as you see above →Select 'Planning & Consolidation' → Expand all.

b)

Goto eTools → Save dynamic templates → Company → Save.

Result Your Report should look similar to this one:

Figure 403: AP AR Elimination Result

Note: The EVDRE report above is restricted to just those accounts and datasrc members that are relevant to the AP AR elimination.


2010


437


BPC440

Task 2: Optional: Look at the results in the LegalApp InfoCube From the BW Server, go to RSA1 and display the original records loaded that relate to the IC Elimination as well as the records generated by the system. 1.

Log on to the BW Server.


a) 2.

Minimize your remote desktop → Start → Sap Logon → Logon → User cpm-##→ Password: training→ Enter

Go to the 'relative' of the 'Admin Console' in BPC, the 'Data Warehousing Workbench', search for your AppSet and right click to display the data in your LegalApp InfoCube.


438


2010

BPC440



a)

To go to the above screen shot:Enter 'RSA1' in the white command field on the upper left → Enter → Use the search to find 'BPC440_## → Open the InfoArea: Goto the data browser for your LegalApp: Right click on your LegalApp→ Display data → Enter through the prompt → Left click on the Select icon on the upper left → 'Select characteristics' → Uncheck the change run, request id and record type → Enter → Select the button at the top left 'Field select for Output' → Select all → F8 → Filter the report by selecting the yellow arrow to the right of the C_Acct → Enter 11301100, 21171000, and APAROFFSET.→ F8 → F8→ And Voila!


2010


439


BPC440

Figure 406: Select Characteristics

Figure 407: Browse the Cube - Filter


440


2010

BPC440


Figure 408: AP AR Elimination results in the InfoCube

Note: The word characteristic in BPC = Dimension, while attribute = property. Note: We did not select the request ID however, if you close the request ID before you run an elimination for example, the new request id will only have the records generated by that task and you can select the latest request ID to easily view them! Hint: If you know the technical name of your Infocube or if you have a unique application description you can go to the transaction code LISTCUBE. Enter your cube name but you will still need to select from your dims and properties.

2010


441


442


BPC440

2010

BPC440


Exercise 16: Intercompany (US) Elimination Exercise Objectives After completing this exercise, you will be able to: • Learn how to set up and carry out the 'US' InterCompany Elimination. • Understand the accounting values it generates.

Business Example You company needs to carry out some straight forward revenue and cost of goods eliminations against at the group entity level.

Task: Intercompany Eliminations Identify the Application business rules required for the InterCompany 'US' Elimination. Note: This method was widely used in the US initially. 1.

In your LegalApp business rules for US Elimination, add the data as you see below. Also, confirm that the ICELIM script logic is in place. Elim ID

Src DataSrc

DestDatasrc

ICELIM

INPUT

AJ_USELIM

2.

In the LegalApp, goto Excel and add the IC Elimination package then execute the ICELIM package for C_Category: C100; Time: 2008.DEC; ConsGroup: G_NONE, RptCurrency: USD.

3.

Run the 'BPC440 IC Elim Rev & Cost ' report with the following current view.


2010


443


BPC440

Figure 409: Current View for BPC440 IC Elim Report

Result The program read the ELIMACC property in the account dimension to determine the USELIMDIFF account as well as what accounts to include in the elimination. It also read the ELIM property in the Entity dimension to identify which entities to include and it also read the parent ID of the E_CG# to obtain the group level elimination entity.

444


2010

BPC440


Solution 16: Intercompany (US) Elimination Task: Intercompany Eliminations Identify the Application business rules required for the InterCompany 'US' Elimination. Note: This method was widely used in the US initially. 1.

2.

In your LegalApp business rules for US Elimination, add the data as you see below. Also, confirm that the ICELIM script logic is in place. Elim ID

Src DataSrc

DestDatasrc

ICELIM

INPUT

AJ_USELIM

a)

Set up the business rule: In the Admin Console → Open up your AppSet → Applications → LegalApp → Business rules→ US Elimination → Input the data above as you see above → Validate and confirm us elimination rule table → Ok.

b)

Confirm the logic: In the Legalapp → Script Logic → ICELIM → Make sure the logic is there → Validate and save → Ok.

In the LegalApp, goto Excel and add the IC Elimination package then execute the ICELIM package for C_Category: C100; Time: 2008.DEC; ConsGroup: G_NONE, RptCurrency: USD. a)

Add the ICELIM package to your LegalApp: In BPC for Excel → Select 'Planning & Consolidation' → Goto eData → More → Organize package list → Right click in the yellow area → Add package → Select the drop down for process chains → Open the 'Business Planning and Consolidation: System' group → Select /CPMB/IC_ELIMINATION → Select → Enter name and description of ICELIM → Check off the User and Admin package task types → Add → Save → Ok.

b)

Confirm that the package parameters include the Group dimension: Goto eData → More → Organize package List → ICELIM → Right click → Modify Package → View Package → Advanced → Enter ',%GROUP_DIM%' as shown below:


2010


445


BPC440

Figure 410: ICELIM Package Parameters

c)

Save your change: Select Ok → Save 3 times → Ok.

d)

Select Home → Manage Data → Run a package → ICELIM → Run → Select the following data region:

e)

Dimension:

Members:

Entity

C1000,C2000

C_Category

C_100

RptCurrency

USD

Time

2008.DEC

Consgroup

NON_GROUP

Next → Finish → Ok → View Status → In the formula log you should see records processed by the consolidation logic → Go back to Excel. Note: The currency translation was run earlier otherwise you would need to translate LC to USD.

3.

Run the 'BPC440 IC Elim Rev & Cost ' report with the following current view.


446


2010

BPC440


Figure 411: Current View for BPC440 IC Elim Report

a)

Open the IC Elim report: In BPC for Excel → Goto the 'Windows Button' on the upper left→ Open → My Computer → C-Drive → BPC440 → BPC440_## → Files → Legal → BPC440 IC Elim Rev and Cost → Open → eTools → Save Dynamic Template → Save.

b)

Expand all:

Figure 412: IC Elim Result

The USELIMDIFF netted to zero as you can see above from the '-'. To know for sure, check out the view below of the data in the InfoCube: Continued on next page

2010


447


BPC440

Figure 413: IC Elim Rev & Cost - From the InfoCube

Result The program read the ELIMACC property in the account dimension to determine the USELIMDIFF account as well as what accounts to include in the elimination. It also read the ELIM property in the Entity dimension to identify which entities to include and it also read the parent ID of the E_CG# to obtain the group level elimination entity.

448


2010

BPC440


Lesson Summary You should now be able to: • Recite the business reasons for eliminating inter company activity. • Identify the most important dimension properties that relate to inter unit eliminations. • Make the related configuration changes in the business rule tables. • Analyze and understand the results. • Discuss the options to carry out Inter Company eliminations.

2010


449

Unit Summary

BPC440

Unit Summary You should now be able to: • State the possible reasons to use an IC Matching application. • List the master data, properties, logic, and packages required. • Understand the output generated from the IC Matching application. • Recite the business reasons for eliminating inter company activity. • Identify the most important dimension properties that relate to inter unit eliminations. • Make the related configuration changes in the business rule tables. • Analyze and understand the results. • Discuss the options to carry out Inter Company eliminations.

450


2010

BPC440

Test Your Knowledge


What reasons do you have for using an IC Matching Application? Choose the correct answer(s).

□ □ □ □ 2.

A B C D

You cannot use transaction currency in the Legal App. It makes it easier to manage the data due to the smaller volumes. You can avoid changing users data access for the legal app. It is easier to manage work status.

Which of the following are required to do IC Matching? Choose the correct answer(s).

3.

□

A

□ □

B C

□

D

□ □

E F

The IC Matching App must include an Inter Company Dim of type 'I'. The Inter Company Dim must include the property Entity. The Entity Dim needs a property of I or E for Internal vs. Customer facing subsidiaries. The Inter Company Booking business rules and Currency Conversion rules need to be set up. A data manger package that executes the ICBooking program . Default logic which has the ICData logic referenced.

The ARAP related dimension properties include which of the following? Choose the correct answer(s).

2010

□

A

□

B

□ □ □

C D E

Entities have an internal vs. external indicator for inter unit vs. customer activities. Datasrc has: DataSrc_Type A (automatic), Is_Converted which can be yes, no, or filled with Group currency. Intco has the corresponding Entity property. Account can have a 'DimList' property with a value such as ARAP. Category has an a book vs. tax indicator for book Gaap vs. IRS valuations.


451

Test Your Knowledge

4.

BPC440

When the consolidation program is executed, what happens? Choose the correct answer(s).

452

□

A

□

B

□

C

□

D

□

E

□

F

The program reads the dimension properties, consolidation methods and %'s in the Ownership application. The program then reads the business rule tables and a DimList property for the Account Dimension. The program reads the Rules, Methods and Formulas from the application business rules. The program then reads the destination datasrc which is assigned to the method in the application business rules table called 'automatic adjustments'. The program then will post a validation account for any differences. The program reads the automatic adjustment tables to fetch the source accounts, reverse signs, target accounts, and target flows.


2010

BPC440

Test Your Knowledge

Answers 1.

What reasons do you have for using an IC Matching Application? Answer: B, C, D A. You can use transaction currency in a Legal App.

2.

Which of the following are required to do IC Matching? Answer: A, B, D, E, F C. The Entity Dim requires a property 'Elim' with a value of 'Y' to be included in the matching algorithm.

3.

The ARAP related dimension properties include which of the following? Answer: B, C, D A. Entities have a corresponding partner id via the Intco property. E. Category does not have any elimination related properties.

4.

When the consolidation program is executed, what happens? Answer: A, B, D, F C. The program reads the Rules Methods and Formulas from the appset consolidation rules. E. Differences are only posted to validation accounts by the validation process.

2010


453


454


BPC440

2010

Unit 7 COI - Equity and Proportional Methods Unit Overview In this unit we will take a look at the Equity and Proportionate Methods as well as scope changes.

Unit Objectives After completing this unit, you will be able to: •

Understand the Equity and Proportional methods and the properties which affect them.

Unit Contents Lesson: COI Equity and Proportional Methods ............................456 Exercise 17: Equity and Proportional ownership elimination. ........465

2010


455

Unit 7: COI - Equity and Proportional Methods

BPC440

Lesson: COI Equity and Proportional Methods Lesson Overview Now that we have a lot of background covered, let's take a look at the Equity and Proportional COI set up and methods, and scope changes.

Lesson Objectives After completing this lesson, you will be able to: •

Understand the Equity and Proportional methods and the properties which affect them.

Business Example Some of your subsidiaries are less than 50% owned and so you need to use the Equity method. You are also a European based company so you are interested in the Proportional method (this isn't used as much in the US).

The Equity Elimination Process

Figure 414: Equity Elimination Process

Equity Concept

456


2010

BPC440

Lesson: COI Equity and Proportional Methods

Figure 415: Equity Method Concept

The Equity method is an accounting technique used for consolidating affiliates, as well as subsidiaries or joint ventures (all of which are referred to as consolidation units) that are not consolidated using the purchase or proportionate methods. Reported financial data of an equity unit is not taken into account in the consolidated financial statements. Therefore, you do not need to enter that data into the Consolidation system. Only changes in the stockholders' equity of the company are taken into consideration; these affect, in particular, the investment value stated in the consolidated balance sheet. The Equity Method Example In the example below, the flat file includes entity '5000' (C5000) who purchased 30% of C5100 for 20,000. To achieve the desired result, this example is using Rules 010, 060, and 200. The net effect will be to debit Goodwill 5,000 and credit the investment account by 5,000. C5100 has equity of 50,000, of which, 15,000 belongs to C5000 and since they paid 20,000, there is 5,000 of Goodwill. One of the key differences in the equity set up versus the purchase method is that the equity rule200 is a 'default' rule and as such it does not have to be included in the Automatic Adjustment Details table. Correspondingly, this will cause all balance sheet items to be eliminated using the percentage specified in the formula table. In the following illustration, you can see the two records in the flat file. Note the Intco member I_C5000 in the second record. That will be used to 'Swap the Entity - Intco' in the Automatic Adjustment Details table so that all of the entries will show against the parent C5000.

2010


457


BPC440

Figure 416: The Equity Method - Data and Set Up

In the following illustration, you will see the Automatic Adjustment table which has the datasrc assignments and the all important Equity adjustment type. You can also view the results. Note: The intent of this example to illustrate the mechanics of how the business rules can be used to generate various outcomes. The illustration is not necessarily a depiction of a solution for any particular accounting standard. Also, we are using several datasrc's to show the effect of the model but in reality that would not be necessary. Note: The system does not contain logic to calculate goodwill. Since it is a very flexible solution, you may be able to achieve the desired result using a technique as shown below however, manual entries my also be required. Row 1 below writes the investment amount into the goodwill account. Row 2 below writes the equity amount that is owned into the goodwill account and nets with row one. Row 3 below writes the investment amount to the investment account. Row 4 below writes the equity owned amount to the investment account and nets with row three. In Row 2 and 3, we are using the 'Swap Entity - Intco' so that the entries are recorded against the parent.

458


2010

BPC440


Figure 417: Equity Method Details and Result

The Proportional Elimination Concept and Set Up

Figure 418: Proportional Method Example

In contrast to the purchase method, the Proportional method of consolidation collects the items of a unit’s balance sheet and income statement into the consolidated statements to the extent of the investor unit’s percentage of ownership in the investee unit, rather than at the full amount. Hint: You can sort the rules by clicking on the column header.

2010


459


BPC440

Consolidation rules define the formulas to use in calculating the amounts to post. If desired, each business rule can be restricted to specific consolidation methods. You define a name, description, and consolidation method as noted in the on line help. The consolidation method as defined in Rule Type limits the use of the rule to the specified type of consolidation method.

Proportional Example with Goodwill The illustration below includes the incoming data with two records, one for the investment and one with the equity. The ownership data is not shown here but the key information is that C3000 purchased 75% of C4000 for 80,000. One of the key differences in the proportional set up versus the purchase method is that the proportional rule210 is a 'default' rule and as such it does not have to be included in the Automatic Adjustment Details table. Correspondingly, this will cause all balance sheet items to be eliminated using the percentage specified in the formula table. One key point is that the equity record below does include I_C3000 in the Intco field. That data is used to 'swap' the Entity and Intco in the Automatic Adjustment Details and that way the Goodwill is booked exclusively against the parent. Note: The intent of this example to illustrate the mechanics of how the business rules can be used to generate various outcomes. The illustration is not necessarily a depiction of a solution for any particular accounting standard. Also, we are using several datasrc's to show the effect of the model but in reality that would not be necessary.

460


2010

BPC440


Figure 419: Proportional Method Example Set Up

Note: The system does not contain logic to calculate goodwill. Since it is a very flexible solution, you may be able to achieve the desired result using a technique as shown below however, manual entries my also be required. In the illustration below, the first 'ELCOI1' row is used to back off 100% (via the Rule060 ALL Formula = 1) of the investment amount. The 'ELCOI2/3' rows are netting the investment against the equity to produce the Goodwill. The fourth row is clearing out the remaining balance in the equity account.

2010


461


BPC440

Figure 420: Sample Proportional Result

Note: Goodwill was not included in the above example. Please see the COI Purchase example on Goodwill. The technique will essentially be equivalent. Business rules define the balances upon which automatic adjustments are made and the items such as accounts and flow to which calculated amounts are posted.

Figure 421: Aggregated Balance Sheet Before

Note: CLO = Closing

462


2010

BPC440


Figure 422: Consolidated Balance Sheet

The results above are without any change in ownership.

Figure 423: Assignment of Profit

2010


463


BPC440

Figure 424: Consolidated results with Change in Ownership

464


2010

BPC440


Exercise 17: Equity and Proportional ownership elimination. Exercise Objectives After completing this exercise, you will be able to: • Configure the business rules to do ownership eliminations. • Understand the entries generated by the system as a result of your configuration.

Business Example Your company has many legal subsidiaries and they are not all 100% owned so the manual close takes a long time. You are interested in seeing how easy it is to perform this automatically.

Task 1: COI - Equity and Proportional Methods Configure the business rules for Equity and Proportional ownership elimination. 1.



2.

Set up the following consolidation rule formulas or confirm that they exist in your Appset as shown below. Leave any other entries as it.


2010


465


3.

4.

BPC440

RuleID


AllForm.

GroupForm.

RULE210

70

99

1-POWN

RULE060

70

99

1

POWN

RULE200

30

99

1

1

RULE060

30

99

POWN

POWN

RULE010

30

99

POWN

POWN

RULE060

90

99

POWN

POWN

RULE010

90

30

1

1

RULE010

70

99

POWN

1

RuleID


AllForm.

GroupForm.

Min.Form.

Min.Form.

Add the two automatic adjustments in your LegalApp as shown below. Leave any other entries unchanged. Adjust.ID Src DataSrc

DestDatasrc

Adjust.Type

AdjLevel

ELEQY

AJ_EQUIMETH

EQUITY

0

ELPRO

AJ_PROP

PROPORTIONAL

0

Enter the following automatic adjustments 'details' into your LegalApp. Note: Leave the other entries for the purchase method and AP AR elimination unchanged. A '-' may appear in the table below, please ignore them. Adj.ID SrcAcc

Rev DestAllAcc

DestG.A.

RuleID

Swap E -I*

ELCOI1

12313000

NO

12313000

RULE060 NO

ELCOI1

25130000

NO

25130000

RULE010 NO


466


2010

BPC440


ELCOI2

12313000

YES 12413000

RULE060 NO

ELCOI3

25130000

YES 12413000

RULE010 YES

ELCOI1

12312000

YES 12412000

RULE060 NO

ELCOI2

25120000

YES

12312000 RULE010 YES

ELCOI2

25120000

NO

12412000 RULE010 YES

ELCOI3

12312000

YES

12312000 RULE060 NO

Rev DestAllAcc

DestG.A.

(1) SAVE NOW!

Adj.ID SrcAcc

RuleID

Swap E -I*

Note: (1) We'll have you save once before you are done just in case. Save without validation and then validate. * Swap Entity - Intco Note: The account id's with '11' are for the Purchase method, '12' Equity, and '13' is Proportional.

Result Now all of your business rules at the AppSet and Application level are complete and ready to be tested. Below you can see the Investment Structure we are using.


2010


467


BPC440


Task 2: Optional: Review Ownership Data Execute the Ownership input schedules to review the ownership data. 1.

Go to the Ownership application and review the pown data.

2.

Now let's review the Methods, Pgroup, and Pcon data.

Task 3: Execute Consolidation Run the Consolidation package in the LegalApp to process your new configuration for equity and proportional eliminations.

468

1.

For the Proportional Elimination execute the Consolidation package for CG3 then run the Consolidation report for G_CG3 with CG3 in the current view and C3000,C4000 in the memberset.

2.

Now for the Equity Elimination, run the Consolidation package for CG4, modify the consolidation report and current view to see the results.


2010

BPC440


Solution 17: Equity and Proportional ownership elimination. Task 1: COI - Equity and Proportional Methods Configure the business rules for Equity and Proportional ownership elimination. 1.



a) 2.

In the Admin Console → Open up your AppSet → Business rule library → Consolidation methods→ Confirm that yours matches the one above.

Set up the following consolidation rule formulas or confirm that they exist in your Appset as shown below. Leave any other entries as it. RuleID


AllForm.

GroupForm.

RULE210

70

99

1-POWN

RULE060

70

99

1

POWN

RULE200

30

99

1

1

RULE060

30

99

POWN

POWN

RULE010

30

99

POWN

POWN

RULE060

90

99

POWN

POWN

Min.Form.


2010


469


RULE010

90

30

1

1

RULE010

70

99

POWN

1

RuleID


AllForm.

GroupForm.

a)

3.

BPC440

Min.Form.

In the Admin Console → Open up your AppSet → Business rule library → Consolidation rules formulas→ Fill out your table as you see above by selecting the RuleID in the upper section and entering the Entity Method etc in the lower section → Validate and confirm consolidation rules formulas rule table → OK.

Add the two automatic adjustments in your LegalApp as shown below. Leave any other entries unchanged. Adjust.ID Src DataSrc

DestDatasrc

Adjust.Type

AdjLevel

ELEQY

AJ_EQUIMETH

EQUITY

0

ELPRO

AJ_PROP

PROPORTIONAL

0

a)

In the Admin Console → Open up your AppSet → Applications → LegalApp → Business rules→ Automatic Adjustments Details → Fill out your table 'header' as you see above → Validate and confirm automatic adjustments rule table. Note: There are no entries necessary for the lower details part of the table since these are global methods. (No account assignment is necessary)

Figure 428: Equity and Proportional Detail Table


470


2010

BPC440


4.

Enter the following automatic adjustments 'details' into your LegalApp. Note: Leave the other entries for the purchase method and AP AR elimination unchanged. A '-' may appear in the table below, please ignore them. Adj.ID SrcAcc

Rev DestAllAcc

DestG.A.

RuleID

Swap E -I*

ELCOI1

12313000

NO

12313000

RULE060 NO

ELCOI1

25130000

NO

25130000

RULE010 NO

ELCOI2

12313000

YES 12413000

RULE060 NO

ELCOI3

25130000

YES 12413000

RULE010 YES

ELCOI1

12312000

YES 12412000

RULE060 NO

ELCOI2

25120000

YES

12312000 RULE010 YES

ELCOI2

25120000

NO

12412000 RULE010 YES

ELCOI3

12312000

YES

12312000 RULE060 NO

Rev DestAllAcc

DestG.A.

(1) SAVE NOW!

Adj.ID SrcAcc

RuleID

Swap E -I*

Note: (1) We'll have you save once before you are done just in case. Save without validation and then validate. * Swap Entity - Intco Note: The account id's with '11' are for the Purchase method, '12' Equity, and '13' is Proportional. a)

In the Admin Console → Open up your AppSet → Applications → LegalApp → Business rules→ Automatic Adjustments Details → Enter the data above by first selecting the Adjustment ID (such as ELCOI1 Continued on next page

2010


471


BPC440

in the upper section and entering the Source account etc in the lower section → Save without validation → Ok → Validate and confirm automatic adjustments details rule table → Ok. Here's what your table looks like in the system, with ELCOI1 selected:

Figure 429: Adjustment Details - ELCOI1

Result Now all of your business rules at the AppSet and Application level are complete and ready to be tested. Below you can see the Investment Structure we are using.



472


2010

BPC440


Task 2: Optional: Review Ownership Data Execute the Ownership input schedules to review the ownership data. 1.

Go to the Ownership application and review the pown data. a)

In BPC for Excel Select the Ownership Application → Select 'Planning & Consolidation' → eTools → Open Dynamic Templates → Select 'BPC440 Enter Pown Data' → Open:


Figure 432: Ownership Current View

b)

Set your current view: Use the current view above → Expand All.


2010


473


2.

BPC440

Now let's review the Methods, Pgroup, and Pcon data. a)

In BPC for Excel: Select the Ownership Application → eTools → Open Dynamic Templates → Select 'BPC440 Group Methods Pcon' → Open → Expand all:

Figure 433: Group Methods Pcon with Ownership Calculated Group 1 & 2

Figure 434: Group Methods Pcon with Ownership Calculated Group 3 & 4

Task 3: Execute Consolidation Run the Consolidation package in the LegalApp to process your new configuration for equity and proportional eliminations. 1.

For the Proportional Elimination execute the Consolidation package for CG3 then run the Consolidation report for G_CG3 with CG3 in the current view and C3000,C4000 in the memberset. a)

Go to the LegalApp → Manage Data → Run a package → Consolidation → Run → Select the data region members as follows: C_Category: C100; Time: 2008.DEC; ConsGroup: G_CG3. Continued on next page

474


2010

BPC440


b)

Next → Finish → Ok → View Status → Review the Formula log entries → Do you have records generated for Translation and Consolidation?

c)

Change your current view to the one below (including CG3 and G_CG3) → Goto eTools → Open Dynamic Template → Company → 'Consolidation' → Open→ Open the column group → Switch the entities to 'C3000,C4000' → And expand all. Dimension

Member

ConsGroup

G_CG3

C_Acct

1

C_Category

C_100

C_DataSrc

Totaladj

Entity

CG3

Flow

F_Top

IntCo

TOTAL

RptCurrency

USD

Time

2008.Dec

Measures

YTD

Dimension

Member

A credit of (16,250) to eliminate the cash not owned (AJ_PROP). A credit of (80,000) to clear out the investment (AJ_COI1). A debit of 80,000 for the Goodwill account (AJ_COI2). A credit of (48,750) for the Goodwill account (AJ_COI3). A debit of (16,250) (AJ_PROP) and (48,750) (AJ_COI3) for the equity.

Figure 435: Proportional Method Result


2010


475


2.

BPC440

Now for the Equity Elimination, run the Consolidation package for CG4, modify the consolidation report and current view to see the results. a)

In the LegalApp → Home → Manage Data → Run a package → Consolidation → Run → Select the data region members as follows: C_Category: C100; Time: 2008.DEC; ConsGroup: G_CG4

b)

Next → Finish → Ok → View Status → Review the Formula log entries → Do you have records generated for Translation and Consolidation?

c)

Change your current view: → Change Entity to CG4 → Change Consgroup to G_CG4 → open up the column group → input C5000,C5100 → Expand all. A credit of (65,000) for cash. (AJ_EQMETH) A credit of (26,000) for the investment. AJ_COI3) A debit of 19,500 for the investment ... therefore a net credit of 6.500. (AJ_COI2) A credit of (19,500) into the Goodwill account. (AJ_COI2) A debit of 26,000 into the Goodwill account ... therefore a net debit of 6,500. (AJ_COI1) A debit of (65,000) into the subsidiary equity account to clear it out. (AJ_EQMETH) Note: If necessary, set the c_acct memberset to BASMEMBERS,SELF to get the save result as below.

Figure 436: Equity Method Result

Result Now the report should display the results from the Equity elimination. Have a nice day!

476


2010

BPC440


Lesson Summary You should now be able to: • Understand the Equity and Proportional methods and the properties which affect them.

2010


477

Unit Summary

BPC440

Unit Summary You should now be able to: • Understand the Equity and Proportional methods and the properties which affect them.

478


2010

BPC440

Test Your Knowledge


The Equity elimination process includes which of the following supporting information? Choose the correct answer(s).

2.

□ □

A B

□

C

□ □

D E

The entity and linked intercompany member. The method 'posted' into the Ownership Application for each entity. The Elimination name or ID from a DimList property for the account dimension. The Dynamic Hierarchy method assignments. The Equity Data Store Object.

Which of the following are true regarding Consolidation Rules? Choose the correct answer(s).

3.

□ □ □ □

A B C D

□

E

They can be found in the application. The can be found in the appset. Consolidation rules have 5 possible rule types. All of the rule types also appear in the consolidation methods as 'method' types. Rule id's are assigned to rule types in the Cons Rules and then to the automatic adjustment details.

The application business rule tables have which of the following attributes? Choose the correct answer(s).

2010

□

A

□

B

□

C

□ □ □

D E F

The automatic adjustment table includes link to the consolidation rules via the adjustment types which are linked to the rule types. The destination datasrc member has to have an 'A'utomatic datasrc type property value. The adjustment id identifies the destination datasrc and adjustment type and links that to the details which include the source account, sign reversal, destination all account, etc. They can only be maintained at the appset level. The 'Level' is the solve order, lower values are processed first. The rule id in the details table comes from the consolidation rules table.


479

Test Your Knowledge

BPC440

Answers 1.

The Equity elimination process includes which of the following supporting information? Answer: A, B, C D. The dynamic hierarchy is on an input user interface, it doesn't store data. E. The equity data store object is only used for BW based consolidations. (BCS)

2.

Which of the following are true regarding Consolidation Rules? Answer: B, C, E A. Rules are found in the AppSet. C. New, Generic, Leaving, Equity, Proportional. D. The consolidation method types include: New, Holding, Global, Proportional, Equity, Leaving @ the beginning of the year, Leaving @ the end of the year.

3.

The application business rule tables have which of the following attributes? Answer: A, B, C, E, F A. The adjustment types include the same 5 rule types: Generic, Equity, Proportional, New, and Leaving. D. Business rules exist at the application level also.

480


2010

Unit 8 Business Process Flow for Consolidation Unit Overview In this unit we will build and use a sample BPF for the Consolidation process.

Unit Objectives After completing this unit, you will be able to: • •

Build a BPF for Consolidation. Use a BPF user interface.

Unit Contents Lesson: Business Process Flows for Consolidation........................482 Exercise 18: Consoldation BPF ..........................................503

2010


481

Unit 8: Business Process Flow for Consolidation

BPC440

Lesson: Business Process Flows for Consolidation Lesson Overview In this lesson we will see how to build and use a BPF for Consolidation.

Lesson Objectives After completing this lesson, you will be able to: • •

Build a BPF for Consolidation. Use a BPF user interface.

Business Example Your company or client is interested in a solution to control the consolidation process and provide a user interface to the users that clearly identifies what step(s) they need to carry out. Management is also interested in a monitoring and control device whereby approval steps can be used. Business Process Flows (BPFs) guide users through the sequence of tasks within a defined business process. Business process flows are comprised of steps that must be completed sequentially, and substeps, which can be optional. Depending on a user's role, the steps available to them can involve completing actions, or reviewing submitted actions. In this section we will go over the build concepts of BPF's. Note: The objective of this unit is to see how we can use BPF's to do consolidation not necessarily to become experts at how to create BPF's.

Figure 437: What a BPF Does and Does Not Do

482


2010

BPC440

Lesson: Business Process Flows for Consolidation

Figure 438: New Concepts in BPF's

Figure 439: BPF Terminology -1

2010


483


BPC440

Figure 440: BPF Terminology - 2

Building a BPF template is the first step. One template can be used multiple times.

Figure 441: Defining a BPF Template

To begin creating a BPF template, you must provide details, such as name, description, and controlling application of the BPF (see Setting Up Business Process Flows). You add steps to represent the flow of the business process (see Defining Steps and Sub-Steps). You can copy or modify an existing step or substep. You can also reorder steps and substeps using up and down arrows. You add actions to define the specific tasks users perform within the steps of the process (see Defining Actions). An action can be any user authorized task, for example, opening a schedule, publishing a report, or approving entered data. You review the information and parameters you provided throughout the template creation process in the Finish BPF step.

484


2010

BPC440


You validate the BPF template definition to ensure it is properly defined and completed. This also allows you to check whether any changes made in the application have impacted the template definition. If you do not manually validate the template, the system automatically validates it when you choose Create BPF Instance. Template validation is a prerequisite for creating an instance.

Figure 442: Creating a BPF Template - Definition

Figure 443: Defining BPF Steps and Sub Steps

2010


485


BPC440

Figure 444: Creating a Step

Figure 445: Defining a Step Region

The owner of a step region is the person responsible for completing the step region. The reviewer is the person who must verify the actions taken in a particular step region. Owners and reviewers can be individual users or made up of a team of users. Two or more users can select the same step region concurrently, as multiple users may be involved in the completion of a step region. If you are the responsible reviewer for a step region, you see a Review flag in the Action Required column. You can choose Accept or Reject in that step. Accept sets the step region to status Completed. Reject causes the step region to remain open until the user resubmits it for approval.

486


2010

BPC440


Figure 446: Step Region Criteria

Figure 447: Three Steps Completed

2010


487


BPC440

Figure 448: BCF Sub Step

Figure 449: Steps and Sub Steps

488


2010

BPC440


Figure 450: BCF Action

Figure 451: File Upload Actions

2010


489


BPC440

Figure 452: Dynamic Hierarchy Editor Action

Figure 453: Set Work State Action

490


2010

BPC440


Figure 454: Finish and Save a BPF Template

A BPF instance is an iteration of a business process flow template that is in active use. Example: An authorized user can create a BPF template called Monthly Reporting to coordinate the monthly reporting activities of various personnel. When that user, or another authorized user, creates a business process flow for a specific period, such as November 2009, based on the Monthly Reporting template, the November 2009 BPF is considered an instance. In this example, there are 12 instances of the Monthly Reporting BPF, one for each month of the year.

Figure 455: Managing a BPF Instance

The authorized user can create a Business Process Flow (BPF) instance within the administration console. This activates a BPF template using a specific BPF identifier, which enables end-user participation in the process. It also establishes the BPF instance owner.

2010


491


BPC440

Figure 456: Create an Instance

Figure 457: Set Instance Owner

492


2010

BPC440


Figure 458: BPF Instance Preview

Figure 459: Activate the Instance

Figure 460: Finalizing a BPF Instance

2010


493


BPC440

Figure 461: Sizing Restrictions

In this section we will use the BPF to carry out a few of the key steps in a sample consolidation process.

Figure 462: Accessing BPF's

My Activities displays the processes and steps in which the currently logged-on user can perform certain actions. You can open a specific step region or activity and execute tasks for that step region.

494


2010

BPC440


Figure 463: My Activites

Steps can have the following statuses: Open: waiting for completion or to be submitted as a new step region Submitted: action has been taken and the step region is waiting for review Completed: the step region is fully completed Reopened: the step has been reopened for further action. The previous step (or specific step region in the case of matching) must be at Completed status to be reopened. Pending: the step region is waiting for an open step to be completed. Users cannot perform actions on pending step regions. Rejected: a reviewer has rejected a step region action, the step region is open again for user action Delayed: completion of the step region has been delayed due to the previous step being reopened. Users cannot perform actions on delayed step regions.

2010


495


BPC440

Figure 464: Data Preparation Step

Figure 465: Run Package and Back to BPF

496


2010

BPC440


Figure 466: Complete the Step

Figure 467: My Activities After a Step is Complete

2010


497


BPC440

Figure 468: A Step With Reviewer

Figure 469: Set Work Status

498


2010

BPC440


Figure 470: The Monitor

Figure 471: Factors Affecting Re Opening -1

Figure 472: Factors Affecting Reopening -2

2010


499


BPC440

Instance owners receive an e-mail notification when a new instance is created or an action is taken in a specific instance. The owner of a step region receives a notification when the step region is ready for action to be taken. The responsible reviewer for a step region receives notification that the step region is ready for review. When a BPF instance is created, all users with access to the BPF monitor receive a notification. The BPF Instance owner receives an e-mail notification when the BPF is completed and ready to be finalized.

Figure 473: E-Mail Notifications

500


2010

BPC440


Figure 474: Security, Work Status, BPF Integration Concept

Figure 475: Work Status Concept

2010


501


502


BPC440

2010

BPC440


Exercise 18: Consoldation BPF Exercise Objectives After completing this exercise, you will be able to: • Create and run a BPF for Consoldation

Business Example You need to create a BPF for your Consolidation Process.

Task 1: Create a BPF 1.

Before we create the BPF, we need to add the reviewer property to the Entity dimension and populate it with your domain\user. And, if you did not do the reporting lab, save the Account by Entity report to your Legal application.

2.

Create a new BPF with 3 steps from the Admin Console.

3.

Create the Sub Steps.

4.

Create the Actions.

5.

Validate, Create the Instance, and Activate your BPF.

Task 2: Run your BPF 1.

2010

Access your BPF.


503


BPC440

Solution 18: Consoldation BPF Task 1: Create a BPF 1.

2.

Before we create the BPF, we need to add the reviewer property to the Entity dimension and populate it with your domain\user. And, if you did not do the reporting lab, save the Account by Entity report to your Legal application. a)

Add the OWNER and REVIEWER property: Select the Entity dimension → Maintain dimension property → Enter OWNER with 60 characters →→ Enter REVIEWER with 60 characters → Modify dimension property → Ok.

b)

Populate the domain\user: Select Entity → Maintain dimension members → Enter ADTWDFVM2001\CPM-## into the OWNER property and the REVIEWER property for all entities → Process dimensions → Deselect 'Take system offline' → Ok → Ok.

Create a new BPF with 3 steps from the Admin Console. a)

In the Admin Console → Confirm that you are in your BPC440_## Appset → Select Business Process Flows on the lower left → On the right → 'Create new BPF template'.

Figure 476: Create a new BPF Template

b)

Enter 'Consolidation' as the name and description → Select the LEGALAPP as the Controlling application.


504


2010

BPC440


Figure 477: BPF Definition

c)

Determine the data region for your BPF: Select 'B. Instance Identifier' on the upper left → Check off Entity and C_Category. Note: Time is the only required dimension. It is best practice to select at least two dimensions to define an instance.

Figure 478: Instance Identifier

d)

Select 'C. Set Access' on the upper left → Double click on the ADMIN team to move it to the right to the 'Selected' box.


2010


505


BPC440

Figure 479: Set Access

e)

Create step one: Select 'Next' → Add → Make your selections as you see below: Note: ‘Allow Reopen’ will allow that step to be reopened after completion. If this is set to ‘No’ that step can’t be reopened during execution. Opening criteria ‘All Step Regions’ will enable opening of the next step only after all step regions are complete whereas in case of ‘Matched Step Region’ when you complete a step region, the next step opens for the same step region. The first step of the BPF always opens regardless of the opening criteria. Defining these options will be important for the second step onwards.


506


2010

BPC440


Figure 480: Create Step One

f)

Select 'Define step region criteria... → Make the following selections: Note: To select a dimension member, first left click in the field and it turns gray, then left click again and a selector box pops up. You can select up to six. Note: The ‘Choose reviewer property’ is grayed out because you did not check the box ‘Enable Reviewers’ in the earlier screen. You can select any property as the owner property. The property that you select must have a fully qualified user name. The same rule applies for the reviewer property that you will use in the next BPF step you create.


2010


507


BPC440

Figure 481: Step 1 - Region Criteria

g)

Create Step Two: Select Ok → Ok → Add:

Figure 482: Create Step 2

h)

Select 'Define step region criteria...' → Make the following selections: Continued on next page

508


2010

BPC440


Figure 483: Step 2 Region Criteria

i)

Select preview to see what users are determined:

Figure 484: Preview Step 2

j)

Create step Three: Select Ok 3 times → Add:


2010


509


BPC440

Figure 485: Create Step 3

k)

'Define step region criteria':

Figure 486: Step 3 Region Criteria

l)

Select Ok → Save → Ok → You should have the following 3 steps. Continued on next page

510


2010

BPC440


Figure 487: Three Steps Completed

3.

Create the Sub Steps. a)

Create the BCF sub step: Select Step 1 → Select ”Add New Sub Step' → Add a name and description as you see below:

Figure 488: BCF Sub Step

b)

Select Ok


2010


511


BPC440

Figure 489: Message on 1st Sub Step

c)

→ Select 'Yes' to assign all actions to the sub steps → Select Step 1 → Add new sub step:

Figure 490: Upload file sub step

d)

In a similar fashion → Add the sub steps as you see below → Save → Ok.


512


2010

BPC440


Figure 491: Save steps and sub steps

4.

Create the Actions. a)

Create the BCF Action: Select 'Next' → Select the Balance Carry Forward sub step → Select the Interface to Data Manager → Select the 'Run user package' task.

Figure 492: BCF Action

b)

Since the action of the first sub step of each step inherits the step name, rename the action: 'Modify' → Enter 'BCF' → Ok.


2010


513


BPC440

Figure 493: BCF Action Renamed

c)

Select the Upload File sub step → Set the interface and task to 'Data Manager' and 'Data Upload' for the first action → Add → Enter the action name 'Preview' → Ok → Select the Preview action → Fill in the interface and task as you see below:

Figure 494: Upload Action


514


2010

BPC440


d)

Import Action: Fill in the interface and task as you see below:

Figure 495: Import Action

e)

Validation Action: Fill in the interface and task as you see below:

Figure 496: Validation Action

f)

Action - Run validation report: Fill in the interface and task as you see below:


2010


515


BPC440

Figure 497: Action - Run validation report

g)

DHE Action: Fill in the interface and task as you see below:

Figure 498: DHE Action

h)

516

Step1 Work Status Action: Fill in the interface and task as you see below: Note: For each dimension, note the current view type. Since you selected Category, Entity, and Time in the instance identifier, you have an option to inherit those values from the BPF instance. Continued on next page


2010

BPC440


Figure 499: Step1 Work Status Action

i)

Rename the matching action: Select the Matching sub step → Modify → Enter 'Matching' → Fill in the interface and task as you see below → Ok.

Figure 500: Matching action renamed


2010


517


j)

BPC440

IC Revenue and COGS Action: Fill in the interface and task as you see below:

Figure 501: IC Revenue and COGS Action

k)

Calculate Ownership Action: Fill in the interface and task as you see below: Note: In order to set the application to Ownership, try changing the interface to Word, select Ownership, then switch the interface back to Data Manager.

Figure 502: Calculate Ownership Action


518


2010

BPC440


l)

Run Consolidation Action:: Fill in the interface and task as you see below:

Figure 503: Run Consolidation

m)

Re-name the Account by entity action and fill in the interface and task as you see below:

Figure 504: Account by entity action renamed


2010


519


n)

BPC440

Consolidated Financial Report Action: Fill in the interface and task as you see below:

Figure 505: Consolidated Financial Report Action

o)

Step2 Work State Action: Fill in the interface and task as you see below → Save → Ok.

Figure 506: Step2 Work State Action


520


2010

BPC440


5.

Validate, Create the Instance, and Activate your BPF. a)

Validate the BPF: 'Close' → Select Yes regarding the save prompt → Select your BPF → 'Validate BPF Template' → Yes → Ok → Yes.

Figure 507: Validate Template

b)

Create an Instance: 'Create BPF Instance' → Set the data region

Figure 508: Create Instance

c)

Select 'Create Instance' → Set Instance Owner Go to step 2 → Select your domain and user: ADTWDFVM2001\CPM-##:


2010


521


BPC440

Figure 509: Set Instance Owner

d)

'Create BPF Instance' → Select CG2 for each step → Finish.

Figure 510: Instance Preview


522


2010

BPC440


e)

Activate the Instance: Select your BPF on the left → 'Manage BPF Instance' → Set status to inactive → Refresh → Select your instance → Activate → Ok. Your BPF is now ready to use.

Figure 511: Activate the Instance

Task 2: Run your BPF 1.

Access your BPF. a)

Open 'Available Interfaces' → Interface for the Web → Business Process Flows.

Figure 512: Accessing a BPF

b)

2010

Select your BPF → You should see 3 steps underneath the BPF. Continued on next page


523


BPC440

Figure 513: My Activities

c)

Select the Data Preparation step.

Figure 514: The Data Preparation Step


524


2010

BPC440


d)

Select the Balance Carry Forward sub step → Log into the LegalApp if necessary → Just view the data packages without running one (we are only testing at this point) → 'Back to the BPF'.

Figure 515: Run Package and Back to the BPF

We are going to do an abbreviation run of this process chain to optimize our time and to provide you with a feel for the mechanics without too much repetition. e)

Select the Data Preparation step again → Select 'Complete' → 'Back to My Activities'.


2010


525


BPC440

Figure 516: Complete Step 1

f)

You should have the same result as follows:

Figure 517: My activities with one step completed

g)

Select 'Monitor' on the right.


526


2010

BPC440


Figure 518: Monitor with one step completed

h)

Left click on the BPF to see the steps and their status.

Figure 519: Monitor with steps displayed

i)

Select 'Business Process Flows' again → Select Step Two → 'Complete': Note: At this point 'My Activities' would display a 'Review' flag on this step with a status of 'Submitted'.


2010


527


BPC440

Figure 520: Step two after selecting complete

j)

Select 'Approve'. Note: The approval would normally be done by another user.

Figure 521: After Approval

k)

Select 'Back to my activities' → Select Step 3.


528


2010

BPC440


Figure 522: Step Three

l)

Select the 'Account by Entity Report'.

Figure 523: Account by Entity Report

m)

'Back to BPF' → Step 3 → 'Set work status' → Set your data range as seen below → Check 'Include children...' → Approved → Continue.


2010


529


BPC440

Figure 524: Set Work Status

n)

'Back to BPF' → Step 3 → 'Complete' → 'Back to my Activities'.

Figure 525: My Activities Completed

o)

'Monitor'. Note: Normally a 'Finalize Process' button will be available in the Monitor. The BPF instance owner will have the option to ‘Finalize’ the BPF by clicking the Finalize process button. Continued on next page

530


2010

BPC440


Once the BPF is finalized, it can be seen in the monitor and in ‘My Activities’ screen with Status filter set to ‘Finalized’. Once the BPF is finalized, it is no longer active. The finalized BPF can be archived from the ‘Manage BPF Instance’ action in the Admin Console.

Figure 526: Monitor - At Completion

Result Those are the key steps to build and run a BPF for Consolidation.

2010


531


BPC440

Lesson Summary You should now be able to: • Build a BPF for Consolidation. • Use a BPF user interface.

532


2010

BPC440

Unit Summary

Unit Summary You should now be able to: • Build a BPF for Consolidation. • Use a BPF user interface.

2010


533

Unit Summary

534

BPC440


2010

Unit 9 Optional: Reporting Unit Overview In this unit we will take a look at some of the reporting options for consolidation data.

Unit Objectives After completing this unit, you will be able to: • • • •

List all of your reporting options using SAP BusinessObjects Planning and Consolidation tools. Decide how you might want to use the SAP BusinessObjects Planning and Consolidation Commenting feature. Consider using other reporting tools such as Xcelsius and the Drill Through feature. Discuss how to use the Dynamic Hierarchy Editor to manage ownership data.

Unit Contents Lesson: Reporting for SAP BusinessObjects Planning and Consolidation ....................................................................536 Exercise 19: Optional: Income Statement and Balance Sheet Reporting ....................................................................565

2010


535

Unit 9: Optional: Reporting

BPC440

Lesson: Reporting for SAP BusinessObjects Planning and Consolidation Lesson Overview During the close process and after it is complete, there is a lot of analysis that needs to take place. So, in this lesson we will discuss all of your reporting options and what you need to know when you report on consolidated data. You are also interested in using dashboards in Xcelsius and you would like some information about drill through to ECC as well as using the Dynamic Hierarchy data for analysis.


List all of your reporting options using SAP BusinessObjects Planning and Consolidation tools. Decide how you might want to use the SAP BusinessObjects Planning and Consolidation Commenting feature. Consider using other reporting tools such as Xcelsius and the Drill Through feature. Discuss how to use the Dynamic Hierarchy Editor to manage ownership data.

Business Example During the close, you need reports to do analysis of your data both before and after you run eliminations etc. After the close, the reports you need are oriented more towards communicating results and explanations of course. Therefore, you need to know what your options are in terms of the SAP BusinessObjects Planning and Consolidation and BW reporting solutions.

536


2010

BPC440

Lesson: Reporting for SAP BusinessObjects Planning and Consolidation

Business Planning and Consolidation Reporting Interfaces

Figure 527: Available Interfaces

You use this function to access and analyze your data. You access your data using a report that pulls requested data from the database. You analyze your multidimensional data using the current view, which is available on the action pane. Live Reporting on the Web

Figure 528: Planning and Consolidation Web 'Live' Report

2010


537


BPC440

Live Reporting provides the ability to create a web report. You can start from a blank page, or edit an existing report or input schedule. You can create grids (that also support data input) as well as charting. From the main Live Reporting page, you can see a list of reports that have been built for the current application set and application specified in your current view. You can click a column name to sort the list of reports, or choose a report name to open the report. You can submit data, add and view comments, refresh the report, and see report information. You can also set the work status. Depending how the report was configured, some dimensions in the current view cannot be changed. For those dimensions, the values to use were specified in the report definition. The dimension values that are hard coded do not update the current view. The current view uses color coding to indicate the status: Blue — a dimension that is in the rows/columns/page keys of the report. Red — a dimension that was not included in the report definition, and is therefore just acting as a filter. You can format live reports by doing the following: • • • • •

Scaling numbers. Suppressing rows and columns containing null values. Displaying and hiding column and row headers. Setting column width. Defining the font type, size, and color of report data. To format a live report, click Edit report using drag & drop, click Format report, then set a formatting option from the Format Report Options action pane.

BPC web reporting is not as popular since most users prefer excel but this may be an option for simple reports especially for users in the field connecting via the web. BPC for Excel

Figure 529: BPC for Excel

Excel is the primary interface complimented by features for Word and PowerPoint.

538


2010

BPC440


Figure 530: Business Planning and Consolidation Functions

Action Panes are used within BusinessObjects Planning and Consolidation for Excel reports and input schedules to drill to other reports or input schedules or to show the current view settings for dimensions and to link to Web content and documents. Expansion functions in reports and input schedules allow you to use the following features: You can dynamically expand dimensional data based on criteria defined in the expansion formula. In the expansion formula, you can specify whether to expand the report by row, column, or both; and on which member to base the expansion criteria. Linking Functions: You use these functions with Excel's hyperlink function to return references to books or documents on BPC Web. Text Functions return text strings. These text strings can be used to display information, or as parameters in other functions. Value Functions return or send one or more values to the database by data region. Note: Any cell in a report or input schedule that contains a value function is dependent on the current view. If you change the current view, the displayed data changes to reflect the new current view settings. Commenting Features

2010


539


BPC440

Figure 531: Submitting Comments

Comments provide a vehicle for submitting, storing, and retrieving text commentary associated with SAP Business Planning and Consolidation (Business Planning and Consolidation) data cells. This allows users to annotate data so other users can view supporting information associated with a particular data point.

Figure 532: Comments Function

540


2010

BPC440


Figure 533: The Architecture of Centrally Stored Comments

You can add comments using the EvCOM function or through the action pane. The Add comment link is available on any action pane from which the context of the page allows you to enter a comment. Note: If you use EvCOM, you must pass along all the dimension members and the application with the text within the formula syntax. Delivered Templates

2010


541


BPC440

Figure 534: Delivered Dynamic Report Templates

These are the standard delivered reports that are great for ad hoc reporting. In NW, there are 10 delivered templates: • • •

•

• • • • • •

Subtotals by Account: Accounts with subtotals are in the rows and any dimension across in columns. Consolidating: Any dimension in rows and entity members across the columns with a hierarchy. Variance: Any dimension in rows and category comparison in columns. It also features variances, calculation of both amount and percentage with both YTD and Periodic boxes. Comparison with Prior Year: Any dimension in rows and category comparison in columns and also retrieves the last year same period data with both YTD and Periodic boxes. Comparison with 3 Year: Year over Year comparisons. Drill in Place: Performs drill in place. Sort On Values: Sorts by total value. Sort On Members: Sorts on members. Nested Rows: Allows any two dimensions to be nested in the rows and a third dimension in the column. Drill Across Dimensions: Allows you to drill from one dimension to another in the rows.

You can modify the generic reports to meet your requirements and then save it without affecting the global template. This is why they call them 'Templates'.

542


2010

BPC440


You can save a report locally to the My Reports folder by choosing Save to My Reports folder in the Report State action pane. You can save a report as a template by selecting eTools Save Template Library (you must have authorization for this task). After a template is saved as a template, you can make it available for downloading to other users' machines by updating the template version number. Note: These all use EVDRE.

Figure 535: Delivered Dynamic Input Templates

There are five delivered input templates which can be used for easy input of trial balance data or planning data: • • • • •

Account Trend: Accounts in the rows and time in columns. Entity Trend: Entity type members are in the rows and time is in the columns. Consolidating: Accounts are in the rows and entity is in the columns. Nested Row: Choose the dimensions for the rows, columns, and page, two row dimensions can be selected and they will be nested. Comparative: Accounts are in the rows and category members are in the columns with a variance column. Note: These all use EVDRE.

2010


543


BPC440

Figure 536: Configure the Layout

Memberset Options

• • •

544

If the Current View is set to:

If the Memberset is set What shows up in the report: to:

2009.TOTAL

DEP

2009.Q1 - 4

2009.TOTAL

BAS

2009.JAN - DEC

2009.TOTAL

BAS,SELF

2009.JAN - DEC, 2009.TOTAL @BOTTOM

2009.TOTAL

SELF,BAS

2009.JAN - DEC, 2009.TOTAL @ TOP

ANY

BASMEMBERS

ALL BASE LEVEL MEMBERS IN THE TIME DIMENSION

2009.TOTAL

LDEP(1)

2009.Q1 - 4

2009.TOTAL

LDEP(2)

2009.Q1 JAN-MAR ETC.

MEMBERS - all members of a dimension. BASMEMBERS - all base members of a dimension. BAS - base level members below a parent in the current view or page key range.


2010

BPC440


•

DEP - all children of the current view member. You can also enter DEP(parent) to return the members of a specified parent. Note: If the memberset is DEP and the current view is a base level member, no members will be selected.

• • • • • • • • • • •

• • •

ALL - all descendants of a current view member. SELF - the current view member. LDEP(n) - all descendants down # levels. LALL(n) - all descendants down # levels. LBAS(n) - all base level members down # levels. DEP(n) - dependants of n member. ALL(n) - descendants of n member. BAS(n) - leaves of n member. NOEXPAND - converts a dynamic dimension into a static one. GDEP, GBAS, GALL - relate to the dynamic hierarchy editor and can only be used if the application has a GROUP dimension. GDEP - generates the list of entities defined as dependents of the Group set in the page key, as found in the dynamic hierarchy stored in the Ownership cube for the current category and time combinations. This keyword also supports a direct assignment of the Group to use, with the following syntax: GDEP(GroupName). GBAS - selects the group base level members. GALL - selects all members below the current parent. ALL,[,PARENTAFTER] - returns all descendants of a current member. For example ALL(WORLDWIDE2) returns the members of WORLDWIDE2.

The Off Line Options in Park N' Go

2010


545


BPC440

Figure 537: Park N' Go

Note: In off line mode, native Excel formulas and functions are retained. You use this function to lock the current view in a report or input schedule, or both the current view and data, or to take the workbook offline. The data and current view in a report or input schedule is live until you use one of these features from the Park N Go action pane: You can lock the current view by choosing Set to live data and static current view. Locking the current view allows you to store the file on the server and share it with others who are authorized. Note: The term 'static' indicates that a refresh does not update the current view or the data. You can lock the current view and data by choosing Set to static data and static current view. You lock the current view and data when you want to protect the data in the report or input schedule from being refreshed. In addition, you can use this function to take a report or input schedule completely offline and bring it back online. You can make changes to the report or input schedule when you are disconnected from the server, then bring it back online later. You can take reports and input schedules offline by choosing Set to offline (no connectivity). When you want to send a report or input schedule to remote users you can take the workbook offline. Remote users can look at published information and enter data in an offline workbook, but do not have authorization to update or view unpublished data. These users do not have access to BPC for Excel. After

546


2010

BPC440


a workbook has been taken offline, you can bring it back to its live state when you want to work with it in BPC for Excel (as long as there are no significant changes to the format). Note: When you set reports and input schedules to offline, the system changes the Ev functions so that you can open the workbook in native Excel. If you want to set the template to live and send the data, do not change the format or formulas.

Figure 538: High Performance BPC Reports

This tool allows you to quickly create a report by selecting the dimensions you want in the columns and rows, as well as a few more report details.

2010


547


BPC440

A default report contains one expansion on the columns using the Time dimension, one expansion on the rows using the Account dimension, and the MemberSet Self,Dep. You can use the following options for modifying the default report: •

• • • • • •

•

•

Available dimensions - Lists the dimensions that are available in the active application. You can select one or more dimensions and place them on the 'In columns' and 'In rows' fields using the arrow icons. In columns - Lists the dimensions that are placed in the column axis of the report. Use the up and down arrows to change the nesting order. In rows - Lists the dimensions that are placed in the row axis of the report. Use the up and down arrows to change the nesting order. Spread across worksheets - Lists the dimension that has its members enumerated across the worksheets. Member selection - Displays the memberset for the dimensions. Allow expansions - Automatically triggers an expansion in the report. Allow options - Generates an Options range. An Option Range is a range of cells in which you can define your EvDRE options. Alternatively, you can enumerate the options in a comma-delimited list in the Options field. Allow formatting - Allows you to choose a default formatting style generated automatically, or import the style from a predefined workbook (either local or server-based). Select this option to use the format section to customize the format of the template. Allow sorting - Inserts a sorting range into the worksheet. You can have the system automatically insert a break total into the worksheet, and choose to display the values in descending order.

Figure 539: Building an EVDRE Report

548


2010

BPC440


Figure 540: The EVDRE Builder

This tool allows you to quickly create a report by selecting the dimensions you want in the columns and rows, as well as a few more report details.

Figure 541: The EVDRE Builder: Grid Layout

2010


549


BPC440

Figure 542: The EVDRE Builder: Grid Design

Figure 543: The EVDRE Result (with design area open)

When you build a workbook using EvDRE, the system checks the syntax of the function, and displays a descriptive status message within the control panel section of the workbook. The status message informs you of syntax and other data-related issues. If the status is OK, the EvDRE parameters have the correct syntax. If the status starts with #ERR, an error has been detected. The status message provides a short description of the problem. Dynamic Hierarchy Editor Reporting Option

550


2010

BPC440


Figure 544: Ownership data via Dynamic Hierarchy Editor

Figure 545: Ownership data reporting

2010


551


BPC440

Figure 546: DHE Expansion Options

Word

Figure 547: Example: BPC for Excel Object in Word

Note: The data is refreshed when opening the word document. With BPC for Word and BPC for PowerPoint, you can perform many tasks on data contained in your documents. To start BPC for PowerPoint, select BPC for PowerPoint from the BPC Launch page, or from the Available Interfaces drop down list in the action pane. To start BPC for Word, select BPC for Word from the Launch page, or from the Available Interfaces drop down list in the action pane. PowerPoint

552


2010

BPC440


Figure 548: Sample: Object for Excel in PowerPoint

Note: The data is refreshed when opening the PowerPoint. It is possible to embed multiple workbooks into multiple slides in a PowerPoint file. Note: Business Planning and Consolidation (Business Planning and Consolidation) system reports are pre-designed web reports that allow you to report on system information and activity. You can report on: Activity audit information, Security, Comments, Data audit information, and work states. You access system reports by selecting: Launch Business Planning and Consolidation System Reports from the Getting Started action pane in Business Planning and Consolidation for Office, Business Planning and Consolidation Web, or Business Planning and Consolidation Administration. You then choose from the list of available reports in the action pane. Integration Features

2010


553


BPC440

Figure 549: Xcelsius

Figure 550: Voyager

554


2010

BPC440


Figure 551: GRC Process Control Reporting

Drill Through

Figure 552: Drill Through Introduction

Drill Through to a BW Query In the following example, we'll identity the steps to drill through from BPC for Excel into a BW query. The query could be on the same InfoCube as the Application is using or an InfoCube being used in the staging layer. For example, it could be a normal BW General Ledger InfoCube. ('Normal' in this case meaning a standard InfoCube).

2010


555


BPC440

Figure 553: BW Query Drill Through - Wizard

Parameter Mapping Dimensions and user defined values can be used as mapping sources. Dimension member ID's and well as property values can be used as selection criteria for the target reports. The URL parameters can be used to feed the user and date with the '%CurrentUser%' and '%CurrentDate%' values. Constants can also be used in the URL.

Figure 554: BW Query Drill Through - Mapping Parameters

556


2010

BPC440


Figure 555: System Parameters

Figure 556: BW Query Drill Through - Excel

Note: The user will normally be prompted for a log in to access the BW data.

2010


557


BPC440

Figure 557: BW Query Drill Through - Results!

Figure 558: BW Query Definition

Drill Through to ECC Data If there is a business requirement, users can launch ECC reports from BPC for Excel.

558


2010

BPC440


Figure 559: GL Balance Drill Through - Mapping

Figure 560: ECC Prerequisite

2010


559


BPC440

Figure 561: ECC Parameters

Figure 562: GL Balance Drill Through - Excel

560


2010

BPC440


Figure 563: GL Balance Drill Through - Current View

Figure 564: GL Balance Drill Through - Log into ECC

2010


561


BPC440

Figure 565: GL Balance Drill Through - Result

Figure 566: GL Balance Drill Through - Line Item Display

562


2010

BPC440


Figure 567: GL Balance Drill Through - Document Display

Figure 568: GL Balance Drill Through - Header

2010


563


BPC440

Figure 569: Google Search Example

564


2010

BPC440


Exercise 19: Optional: Income Statement and Balance Sheet Reporting Exercise Objectives After completing this exercise, you will be able to: • Become familiar with the EVDRE function. • Construct a Profit and Loss and Balance Sheet report using EvDRE and multiple expansions. • Build an EvDRE report with easy formatting that shows P&L Accounts by Entity.

Business Example Both during and after the close you will need a few different types of reports. This is one of the basic ways to view PL (Profit & Loss) and BS (Balance Sheet) data in the Legal Application.

Task 1: Account by Entity Build an EVDRE report in the Legal Application with Entities in the columns and Accounts in the rows however. 1.

In the Legal Application, go to BPC for Excel, open up the EVDRE builder and set up your rows and columns. Use the following current view: (DO NOT TYPE - USE THE DIMENSION NAME (HYPERTEXT) Dimension

Member

Consgroup

NON_GROUP

C_Acct

A (assets)

C_Category

C_100

C_Datasrc

INPUT

Entity

CG2

Flow

F_TOP

IntCo

TOTAL


2010


565


BPC440

RptCurrency

LC

Time

2008.DEC

Measure

YTD

Note: When you select the Entity dimension, set the 'data view' to 'Hierarchy' to make your selection. (It may default to 'Dynamic Hierarchy') 2.

Use DEP,SELF for both membersets so that the dependents will appear first and then the parent(total). Hide row and column keys. Suppress zeroes in the rows.

3.

Save your report.

Result You have created your first EVDRE report.

Task 2: PL and BS Multiple Expansion Report in the Legal Application Build an EVDRE report in the Legal Application with Entities in the columns and Accounts in the rows however, we need to see PL first and then BS down below. Caution: Do not expand the report until you are asked to. 1.

In the Legal Application, go to BPC for Excel, open up the EVDRE builder and set up your rows and columns.


566


2010

BPC440


Figure 570: Account by Entity EVDRE Builder

2.

We'll use the initial RowKeyRange for PL accounts. Set up a second 'RowKeyRange' for BS accounts below the first one as you see below:

Figure 571: PL & BS Multiple Expansion Report Expansion Ranges


2010


567


BPC440

3.

Copy the EVDES function so you will have descriptions in the rows.

4.

Use the '|' symbol to separate the PL base members in the top section from the BS in the lower section. You can use the hierarchy nodes '1' and '2' for the selection of the BS and the PL. Suppress zeroes as shown below:

Figure 572: PL & BS Multiple Expansion Report Expansion Settings

5.

Execute your report and format the data cells as follows: Numeric, No decimals, Red parentheses for negatives, Comma for thousands separator, Borders in the cells, No pattern color. Use the following current view:

Figure 573: PL & BS Multiple Expansion Report Current View

6.

Group the unwanted rows and columns and hide them.

7.

Title your report as 'PL and BS Multiple Expansion Report'. Center it.


568


2010

BPC440


Result

Figure 574: PL & BS Multiple Expansion Report Result (your numbers will vary)

Task 3: PL by Entity Report Build an EVDRE report that shows P&L Accounts by Entity over time. Caution: Do not expand the report until you are asked to. 1.

In BPC for Excel, open up the EVDRE builder and set up your rows and columns.


2010


569


BPC440

Figure 575: PL by Entity - EvDRE Builder

2.

Set up a second 'RowKeyRange' for BS accounts below the first one as you see below:

Figure 576: PL by Entity Expansion Range

3.

Copy the EVDES function so you will have descriptions in the rows.

4.

Use the '|' symbol to separate the C1000 and C2000 Entity members into a top section and bottom section. Suppress zeroes etc. as shown below:


570


2010

BPC440


Figure 577: PL by Entity - Expansion Settings

5.

Set your current view as shown below. Set up a 'formatting cell. Enter =EVRNG(D1) in the 'Format Range' and format cell D1 as follows: Numeric, No decimals, Red parentheses for negatives, Comma for thousands separator, Borders in the cells, Yellow pattern color.

Figure 578: PL by Entity - Current View

6.

Group the unwanted rows and columns and hide them.

7.

Title your report as 'PL by Entity Report' in I1. Copy the description formula from a row in column I to the row in the lower section.

8.

Now we need to switch to a quarterly view. Use one of the new expansion options, 'LDEP' that returns members based on levels of a hierarchy. Configure the member set for time to: LDEP(1,2008.TOTAL) and run your report again!


2010


571


BPC440

Figure 579: PL by Entity - Level dependent command

9.

572

Now we need to suppress repeated key text for Entity. Insert two rows at the top of your spreadsheet. Use EVDES in H1 that references F1 (that is the Entity key column). Use the Before Range feature to insert a row before each set of accounts by entity with a gray pattern.


2010

BPC440


Solution 19: Optional: Income Statement and Balance Sheet Reporting Task 1: Account by Entity Build an EVDRE report in the Legal Application with Entities in the columns and Accounts in the rows however. 1.

In the Legal Application, go to BPC for Excel, open up the EVDRE builder and set up your rows and columns. Use the following current view: (DO NOT TYPE - USE THE DIMENSION NAME (HYPERTEXT) Dimension

Member

Consgroup

NON_GROUP

C_Acct

A (assets)

C_Category

C_100

C_Datasrc

INPUT

Entity

CG2

Flow

F_TOP

IntCo

TOTAL


2010


573


BPC440

RptCurrency

LC

Time

2008.DEC

Measure

YTD

Note: When you select the Entity dimension, set the 'data view' to 'Hierarchy' to make your selection. (It may default to 'Dynamic Hierarchy') a)

In Excel → Set your current view per the above → Go to Reporting & Analysis → Open a blank workbook → In A1 → Enter =EVDRE() → Refresh → Drag and drop Entity into the columns → Drag Time out of the columns → OK.

Figure 580: EVDRE for Account by Entity

2.

Use DEP,SELF for both membersets so that the dependents will appear first and then the parent(total). Hide row and column keys. Suppress zeroes in the rows. a)

Open the column group by selecting the '+' symbol above column D In the row memberset in C17 → Enter DEP,SELF → Repeat for the column memberset in B17.

b)

In the Options section → In the 'Hide row keys' and 'Hide col keys' → Enter Y in B29 and B30.


574


2010

BPC440


c)

In the Row expansion → In the Suppress field → Enter Y in C20 to suppress accounts with no values.

Figure 581: Account by Entity Expansion Settings

d)

In the first data cell G16 → Goto Format → Cells → Number → Set zero decimals → Border → Outline → Patterns → No color → Ok → eTools → Expand all..

Figure 582: Account by Entity Results: Your values may vary


2010


575


3.

BPC440

Save your report. eTools → Save Dynamic Templates → Company → 'EVDRE Account by Entity' → Save.

a)

Result You have created your first EVDRE report.

Task 2: PL and BS Multiple Expansion Report in the Legal Application Build an EVDRE report in the Legal Application with Entities in the columns and Accounts in the rows however, we need to see PL first and then BS down below. Caution: Do not expand the report until you are asked to. 1.

In the Legal Application, go to BPC for Excel, open up the EVDRE builder and set up your rows and columns.

Figure 583: Account by Entity EVDRE Builder

a)

In Excel → Set your current view to one C_Acct member such as 39000000→ Go to Reporting & Analysis → Open a blank workbook → In A1 → Enter '=EVDRE()' → Refresh → Drag and drop Entity into the columns → Drag Time out of the columns → OK → Open the Group by selecting the '+' symbol above column D. Continued on next page

576


2010

BPC440


2.

We'll use the initial RowKeyRange for PL accounts. Set up a second 'RowKeyRange' for BS accounts below the first one as you see below:

Figure 584: PL & BS Multiple Expansion Report Expansion Ranges

a) 3.

Copy the EVDES function so you will have descriptions in the rows. a)

4.

Go to B6 → Add to the formula as you see in the formula bar above:

Copy the EVDES formula in F16 to F17-22.

Use the '|' symbol to separate the PL base members in the top section from the BS in the lower section. You can use the hierarchy nodes '1' and '2' for the selection of the BS and the PL. Suppress zeroes as shown below:


2010


577


BPC440

Figure 585: PL & BS Multiple Expansion Report Expansion Settings

a)

5.

In C17 → Enter: BAS(2)|BAS(1) → (the '|' pipe is on the backslash key) → Enter 'Y' to suppress zeroes as seen above. Enter SELF,BAS as the column memberset.

Execute your report and format the data cells as follows: Numeric, No decimals, Red parentheses for negatives, Comma for thousands separator, Borders in the cells, No pattern color. Use the following current view:


578


2010

BPC440


Figure 586: PL & BS Multiple Expansion Report Current View

a)

Set your current view per the above → Select Expand All Format each data block separately → Select G16 → Format → Cells → Number → Zero decimals → Red parentheses for negatives → Comma for thousands separator → Border → Outline→ Patterns → No color → Ok.

b)

6.

Repeat for the lower block or use the paint brush: Select G23 → Format → Cells → Numeric → Zero decimals → Red parentheses for negatives → Comma for thousands separator → Border → Outline → Patterns → No color → Ok.

Group the unwanted rows and columns and hide them. a)

Use the paint brush to copy the style from row 15 to 14 → Highlight row 2-12 → Data → Group and Outline → Group → Select the' -' symbol to the left of row 13 or 14 to close the group → Repeat for columns D and E → Hide row 15 → Right justify row 14 → Expand all.


2010


579


7.

BPC440

Title your report as 'PL and BS Multiple Expansion Report'. Center it. In F1 → Title your report → 'PL and BS Multiple Expansion Report'.

a)

Highlight F1:N1 → Format → Cells → Alignment → Horizontal → Center → Check 'Merge Cells' → Font → Bold/Italic → Underline → Single → Size 12 → OK. b)

Save your report: eTools → Save Dynamic Templates → Company → 'PL BS Mult Exp Report' → Save. Note: This report is best used to view accounts with the same account types.

Result

Figure 587: PL & BS Multiple Expansion Report Result (your numbers will vary)

Task 3: PL by Entity Report Build an EVDRE report that shows P&L Accounts by Entity over time. Caution: Do not expand the report until you are asked to. 1.

In BPC for Excel, open up the EVDRE builder and set up your rows and columns.


580


2010

BPC440


Figure 588: PL by Entity - EvDRE Builder

a)

In Excel → Set your current view for C_Acct to 39000000 → Set Entity to A1000 (to keep the initial row key ranges small) → Go to Reporting & Analysis → Open a blank workbook . In A1 → Enter '=EVDRE()' → Refresh → Set your rows and columns as you see above → OK → Open the Group by selecting the '+' symbol above column E.

2.

Set up a second 'RowKeyRange' for BS accounts below the first one as you see below:

Figure 589: PL by Entity Expansion Range

a)

Go to B6 → Add to the formula as you see in the formula bar above: Continued on next page

2010


581


3.

Copy the EVDES function so you will have descriptions in the rows. a)

4.

BPC440

Copy the formula in H16:I16 to H17:I17-H22:I22.

Use the '|' symbol to separate the C1000 and C2000 Entity members into a top section and bottom section. Suppress zeroes etc. as shown below:

Figure 590: PL by Entity - Expansion Settings

a) 5.

In C17 → Enter: C1000|C2000→ (the '|' pipe is on the backslash key) → Enter 'Y' to suppress zeroes and select the membersets as seen above:

Set your current view as shown below. Set up a 'formatting cell. Enter =EVRNG(D1) in the 'Format Range' and format cell D1 as follows: Numeric, No decimals, Red parentheses for negatives, Comma for thousands separator, Borders in the cells, Yellow pattern color.


582


2010

BPC440


Figure 591: PL by Entity - Current View

a)

6.

Set your current view per the above → Enter =EVRNG(D1) in the 'Format Range' in cell B9 → Format cell D1 as follows: Numeric → No decimals → Red parentheses for negative → Comma for thousands separator → Border Outline → Yellow pattern color → Expand All.

Group the unwanted rows and columns and hide them. a)

Highlight row 2-13 → Data → Group and Outline → Group → Select the' -' symbol to the left of row 14 to close the group → Repeat for columns E,F, and G.


2010


583


7.

BPC440

Title your report as 'PL by Entity Report' in I1. Copy the description formula from a row in column I to the row in the lower section. a)

In I1 → Title your report → 'PL by Entity Report' → Format the Title as you wish → If necessary copy the Account description (EVDES) formula in column I from a row in the top section to the rows in the lower section as you see below (in addition, you will actually have 12 months across the columns):

Figure 592: PL by Entity Report by Month

8.

Now we need to switch to a quarterly view. Use one of the new expansion options, 'LDEP' that returns members based on levels of a hierarchy. Configure the member set for time to: LDEP(1,2008.TOTAL) and run your report again!


584


2010

BPC440


Figure 593: PL by Entity - Level dependent command

a)

Open up all of the 'Groups' → enter in the memberset for Time as shown above LDEP(1,2008.TOTAL) → Expand all.

b)

Save the report: eTools → Save Dynamic Template → Enter: PL by Entity by Quarter → Save. Have a nice day!


2010


585


9.

BPC440

Now we need to suppress repeated key text for Entity. Insert two rows at the top of your spreadsheet. Use EVDES in H1 that references F1 (that is the Entity key column). Use the Before Range feature to insert a row before each set of accounts by entity with a gray pattern. a)

Insert two rows at the top of your workbook → In cell H1 → Enter =EVDES(F1) → It will say 'nodata' → Make H1 bold → Make I1:M1 a Gray Pattern → Delete the existing descriptions in column H..

b)

In the Expansion3 BeforeRange → Enter SHEET1!H1:M1 → Expand all → Respond 'Yes' to the EVDRE warning..

c)

Save the report: eTools → Save Dynamic Template → Enter: PL by Entity by Quarter → Save.

Figure 594: PL by Entity by Quarter (your values my vary)

Have a nice day!

586


2010

BPC440


Lesson Summary You should now be able to: • List all of your reporting options using SAP BusinessObjects Planning and Consolidation tools. • Decide how you might want to use the SAP BusinessObjects Planning and Consolidation Commenting feature. • Consider using other reporting tools such as Xcelsius and the Drill Through feature. • Discuss how to use the Dynamic Hierarchy Editor to manage ownership data.

2010


587

Unit Summary

BPC440

Unit Summary You should now be able to: • List all of your reporting options using SAP BusinessObjects Planning and Consolidation tools. • Decide how you might want to use the SAP BusinessObjects Planning and Consolidation Commenting feature. • Consider using other reporting tools such as Xcelsius and the Drill Through feature. • Discuss how to use the Dynamic Hierarchy Editor to manage ownership data.

588


2010

BPC440

Test Your Knowledge


Which of the following are feasible scenarios for how to use the reporting tool set available to you? Choose the correct answer(s).

2010

□ □ □ □

A B C D

□ □

E F

Use EVDRE when you need the most efficient and robust solution. Use Word/PPT for documents or presentations that have live data. Use Live Reporting for the biggest data volumes. Export data on to a normal BI InfoCube ... as part of a standard solution. Use Dynamic Schedules for manual data input. Use Dynamic Reports for Ad Hoc Excel reporting.


589

Test Your Knowledge

BPC440

Answers 1.

Which of the following are feasible scenarios for how to use the reporting tool set available to you? Answer: A, B, E, F C. Live reporting is better suited for quick ad hoc low volume scenarios. D. Exporting data to a BI InfoCube is not a standard solution.

590


2010

Unit 10 Appendix Unit Overview We have some reference information in this unit that you may find very helpful.

Unit Objectives After completing this unit, you will be able to: • • • • • • •

Use this example to understand what COI is all about. Understand currency translation concepts. Explain what content is delivered with the application. Better use application and appset parameters. Try a few tips and tricks for performance, debugging, and transports. Discuss what how to papers you may be able to leverage on your project. Understand how default logic for the Microsoft Platform works.

Unit Contents Lesson: COI Example ..........................................................592 Lesson: Currency Translation Example......................................596 Lesson: More on Delivered Content..........................................600 Lesson: AppSet and Application Parameters ...............................608 Lesson: Technical Content on Connectivity, Performance, Transports, Traces ............................................................................618 Lesson: List of How To Papers................................................632 Lesson: Sample Logic for the Microsoft Platform Version.................635

2010


591

Unit 10: Appendix

BPC440

Lesson: COI Example Lesson Overview This lesson goes into a full blown example of all the steps for the COI Purchase Method.


Use this example to understand what COI is all about.

Business Example You are just getting started on the COI part of the project and you would like a refresher on the accounting entries for various activities and so you are interested see an example of the Purchase Method using the BCS (Business Consolidations System) application.

Figure 595: Acquisition

592


2010

BPC440

Lesson: COI Example

Figure 596: Net Income

Figure 597: Increase in Capitalization

Figure 598: Dividend Elimination

2010


593

Unit 10: Appendix

BPC440

Figure 599: Buy Out

Figure 600: Divestiture

594


2010

BPC440

Lesson: COI Example

Lesson Summary You should now be able to: • Use this example to understand what COI is all about.

2010


595

Unit 10: Appendix

BPC440

Lesson: Currency Translation Example Lesson Overview Here is a nice example of currency translation for various sections of the financial statements over time.


Understand currency translation concepts.

Business Example You want to become a currency guru and you would like to see an example to get a better feel for what entries you want the system to create. Note: These examples are from BCS (Business Consolidation Systems).

Figure 601: Currency Translation Example

596


2010

BPC440

Lesson: Currency Translation Example

Most of the differences that occur during currency translation is on the balance sheet side on the longer term items. Long term fixed asset balances for example are valued on a cumulative basis using a historical rate as a benchmark. As you look through these examples, take note of where periodic valuation vs. cumulative is taking place. Also check out the current vs. average rates being used. Note: This is only an example and should not be used as a guideline on how to meet GAAP requirements. On the other hand, it should be fairly close to how a US based company would do it. • • •

•

GC - Group Currency LC - Local Currency ERI - Exchange Rate Indicator, this determines what exchange rate to use. It consists of a source currency, target currency, date, and type of rate such as average, end of month or historical, etc. M Type - these are movement types such opening balance, acquisitions, depreciation etc. Like sub type in BPC.

Figure 602: Currency Translation Example Continued

2010


597

Unit 10: Appendix

BPC440

Figure 603: Default Currency Translation Example - As data is input

598


2010

BPC440

Lesson: Currency Translation Example

Lesson Summary You should now be able to: • Understand currency translation concepts.

2010


599

Unit 10: Appendix

BPC440

Lesson: More on Delivered Content Lesson Overview In this lesson we have included content that is delivered with BPC.


Explain what content is delivered with the application.

Business Example Before the project begins, you would like to know what comes delivered with BPC so you can do a quicker installation. Since we have already discussed the most important delivered objects in ApShell, on the remaining are discussed here.

Figure 604: ApShell InfoArea

Note: An InfoArea in BW is a folder for InfoProviders and InfoObjects.

600


2010

BPC440

Lesson: More on Delivered Content

Figure 605: ApShell pre-delivered BI Objects

Figure 606: ApShell Pre-Delivered BI Roles

2010


601

Unit 10: Appendix

BPC440

Figure 607: ApShell Dimension List

Figure 608: Financial Packages 1

Note: These use the delivered data manager packages that are accounting related.

602


2010

BPC440


Figure 609: Financial Packages 2

Figure 610: Delivered Administrative Packages

2010


603

Unit 10: Appendix

BPC440

Figure 611: Misc Delivered Data Manager Packages

Figure 612: Delivered Package for Text

604


2010

BPC440


Figure 613: Data Manager - Delta Terminology

Figure 614: Delivered Process Chain Templates

2010


605

Unit 10: Appendix

BPC440

Figure 615: Delivered Process Types

606


2010

BPC440


Lesson Summary You should now be able to: • Explain what content is delivered with the application.

2010


607

Unit 10: Appendix

BPC440

Lesson: AppSet and Application Parameters Lesson Overview Here are the Appset and Application Parameters for your convenience.


Better use application and appset parameters.

Business Example Here's what you need to know about Application and Appset Parameters.

Application and AppSet Parameters Note: Please let your instructor know if you would like a soft copy of these since they are a little hard to read.

Figure 616: Application Parameters 1

608


2010

BPC440

Lesson: AppSet and Application Parameters



2010


609

Unit 10: Appendix

BPC440



610


2010

BPC440




2010


611

Unit 10: Appendix

BPC440



612


2010

BPC440




2010


613

Unit 10: Appendix

BPC440



Figure 629: Appset Parameters 1

614


2010

BPC440




2010


615

Unit 10: Appendix

BPC440



616


2010

BPC440


Lesson Summary You should now be able to: • Better use application and appset parameters.

2010


617

Unit 10: Appendix

BPC440

Lesson: Technical Content on Connectivity, Performance, Transports, Traces Lesson Overview Here are a few special topics that tend to come up in every class. Hope you enjoyed the class!


Try a few tips and tricks for performance, debugging, and transports.

Business Example These are some technical help aids that may help you on your projects

Figure 634: Connectivity

618


2010

BPC440

Lesson: Technical Content on Connectivity, Performance, Transports, Traces

Figure 635: Connectivity - Users

Figure 636: Connectivity - Debug Users

2010


619

Unit 10: Appendix

BPC440

Figure 637: Connectivity - Maintain Debug Users

Figure 638: Tracing BPC with ABAP

620


2010

BPC440


Figure 639: UJ Package - Tables

Figure 640:

2010


621

Unit 10: Appendix

BPC440

Figure 641: UJ Package - RFC API's

Figure 642: Exception - Shared Objects across Appsets

622


2010

BPC440


Figure 643: Concurrency Locking (NW)

Figure 644: Concurrency Locking Parameters

2010


623

Unit 10: Appendix

BPC440

Figure 645: Concurrency Locking - Write Back

Figure 646: Performance - BI Accelerator

624


2010

BPC440


Figure 647: Performance - .Net Configuration 1


2010


625

Unit 10: Appendix

BPC440


Figure 650: Performance - Components & .Net Tier

626


2010

BPC440


Figure 651: Performance - Server Profile Parameters

Figure 652: Program - Push BI Hierarchy into BPC

2010


627

Unit 10: Appendix

BPC440

Figure 653: Program - Delete Statistics

Figure 654: Program - Copy An Application

628


2010

BPC440


Figure 655: Program - Copy an Appset

Figure 656: Program - Refresh Dimension Cache

Figure 657: Delete Data Manager Logs

2010


629

Unit 10: Appendix

BPC440

Figure 658: Program - Create Transport Request

Figure 659: Program - Check Transport Tables

630


2010

BPC440


Lesson Summary You should now be able to: • Try a few tips and tricks for performance, debugging, and transports.

2010


631

Unit 10: Appendix

BPC440

Lesson: List of How To Papers Lesson Overview How To Papers


Discuss what how to papers you may be able to leverage on your project.

Business Example You want to know about all the different ways to use the Application and you are looking for some step by step instructions.

Figure 660: Version for the Microsoft Platform

632


2010

BPC440

Lesson: List of How To Papers

Figure 661: Version for NetWeaver 1

Figure 662: Version for NetWeaver 2

2010


633

Unit 10: Appendix

BPC440

Lesson Summary You should now be able to: • Discuss what how to papers you may be able to leverage on your project.

634


2010

BPC440

Lesson: Sample Logic for the Microsoft Platform Version

Lesson: Sample Logic for the Microsoft Platform Version Lesson Overview Here is some sample default logic for the Version for the Microsoft Platform


Understand how default logic for the Microsoft Platform works.

Business Example You are implementing the Version for the Microsoft Platform and you need to see some sample default logic. Note: Tip on Syntax: '#' designates parent members.

Figure 663: Sample Default Logic - The include statement

Note: These examples are using Microsoft key words. Note: Note: If you change the code in a logic file, you must validate and save that file before the changes will be reflected in any other logic file that references it.

2010


635

Unit 10: Appendix

BPC440

Figure 664: Scope: What Data Region to Include

Figure 665: The *WHEN Statement

Figure 666: The *REC (record) Statement

Note: Always code in upper case.

636


2010

BPC440


Figure 667: Sample Default Logic - Copy PL Profit to BS

Note: PL = Profit and Loss (statement), BS = Balance Sheet. The logic above is based on the Microsoft platform. The logic in the Labs is based on NetWeaver.

Figure 668: Calculate Closing, Error, and Variation Flows

Note: The sample logic above is based on the Microsoft platform.

2010


637

Unit 10: Appendix

BPC440

The Default logic calculates the error / automatic variation flows for the Balance Sheet accounts. In the example above, the system calculated an error of 2,000 for the Building Gross Value account. To illustrate how the logic works, 2,000 was manually entered into the F_INC flow and the logic then calculated an error of zero.

Figure 669: Calculate Closing from the Total


Figure 670: Variation Increment & Commit


638


2010

BPC440


When the default logic is executed, a value of 1 is added to the validation account in the work status setting. This will force the user to run validation to check account totals and assuming everything balances, the validation logic will reset the validation account to zero, and then the system will allow the user to advance the work status to ‘Approved’ or equivalent.

Figure 671: Consolidations Logic (example)

Note: Currency translation code was added to the delivered logic to produce the above example. Currency translation into one of the groups such as G_H1 needs to be run before the consolidation program. The MDXLIB.LGF file includes the explanation and examples of SAP BusinessObjects Planning and Consolidation 7.0, version for NetWeaver MDX. For consolidations you also use the system constants to: • • •

2010

Identify custom flow dimension id's. Identity the balance sheet account to pass earnings from the income statement. Identify the account member (valrun in this example) for the validation logic to write out of balances to.


639

Unit 10: Appendix

BPC440

Lesson Summary You should now be able to: • Understand how default logic for the Microsoft Platform works.

640


2010

BPC440

Unit Summary

Unit Summary You should now be able to: • Use this example to understand what COI is all about. • Understand currency translation concepts. • Explain what content is delivered with the application. • Better use application and appset parameters. • Try a few tips and tricks for performance, debugging, and transports. • Discuss what how to papers you may be able to leverage on your project. • Understand how default logic for the Microsoft Platform works.

2010


641

Unit Summary

642

BPC440


2010

BPC440

Course Summary

Course Summary You should now be able to: • • • •

2010

Set up the Appset and Applications; Prepare the dimensions, properties, logic and business rules. Collect the transaction data, Create reports. Perform consolidation activities such as balance carry forward, journal entries, currency translation, validation, and eliminations. Report and analyze the data during and after the process.


643

Course Summary

644

BPC440


2010

Glossary Account Dimension The Account dimension defines the chart of accounts for your application, and how those 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. Account Type Account type. Can be INC for Income, EXP for Expense, AST for Asset, LEQ for Liabilities & Equity. Application types Reporting and Non-Reporting Application Types Balance Carry Forward Carry-forward populates the opening balances for the new year with the closing balances of the last period of the prior year. Or, BCF can roll prior year opening plus changes into new year opening. For balance sheet accounts, when opening a new year for processing, you populate the opening balances for the new year with the closing balances of the last period of the prior year. In addition, you might close current period net income to the balance sheet to create a fully balanced balance sheet for each period. Business Rules Business rules are functions within BPC applications for calculating and posting monetary amounts in support of common accounting activities, such as inter-company booking and currency translation. Define the balances upon which automatic adjustments are made and the items such as accounts and flow to which calculated amounts are posted. Category Dimension The Category dimension defines the groupings in which you store information in your application. Typical categories would be Budget, Actual, Forecast, and so on. Any dimension that is assigned the type C is a Category dimension. Each application can have only one Category-type dimension. Consolidation rules Consolidation rules define the formulas to use in calculating the amounts to post. Dimension A dimension is a qualitative field, such as Account, Entity, or Time, that usually contains a hierarchy of related members, creating parent, child, and sibling relationships among the members. Managing dimensions involves tasks such as creating new dimensions, defining members, and assigning

2010


645

Glossary

BPC440

properties. You manage dimensions in an application set using the Dimension Library. The dimensions in an application set's Dimension Library can be added to one or more applications in the application set. ECCS 'Enterprise Controlling Consolidation Systems' (ECC Based) ECCS BCS BPC Comparison ECCS / BCS / SAP BusinessObjects Planning and Consolidation Comparison of Terms Entity The Entity 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. Group Dimension The group dimension is used to store Consolidation Groups InfoCube a set of tables joined on integers in BW. Make up of dimension and fact tables. Also referred to as a Star Schema. InfoObjects fields in BW such as account, company, and amount. InfoProvider A BW term for InfoCubes and Multiproviders for example. IntCo The Intercompany dimension defines the base members associated with the level at which intercompany balances are tracked in order to perform intercompany eliminations. Master Data BW master data belongs to characteristics and may include text, attributes and hierarchies. MultiProvider A BW InfoProvider that is a semantic reporting layer between InfoCubes and Queries. The system automatically creates one for every Application. In a pure BW scenario, multiproviders are used 'Union' data from several other InfoProviders. Processing Dimensions Processing a dimension is used to update the tables for manual master data changes. Purchase method Purchase method is an accounting technique of the consolidation of investments, which is used when the parent unit of a consolidation group exercises a dominating influence over a specific investee unit.

646


2010

BPC440

Glossary

Rate Type The Rate Type determines whether an average or end of month rate is used for example. Script Logic These are formulas in applications that either do calculations or call ABAP programs. This function allows you to create files containing instructions for performing calculations with special requirements on SAP BusinessObjects Planning and Consolidation data. Time Dimension The Time dimension defines the units of time for your application and how those units aggregate. Any dimension that is assigned the type T is a Time dimension. Each application can have only one Time dimension. US Elimination US elimination functionality addresses the posting of inter-company elimination entries in scenarios where a full legal consolidation application is not required such as within a standard Financial application. US Eliminations A business rule that can be used for non COI (ownership) eliminations in the US or else where.

2010


647

Glossary

648

BPC440


2010

Index A Account Dimension, 93 Account Transformations, 241 Account Types, 89 Allocations, 247 Application Parameters, 335, 608 Appset Parameters, 614

B Balance Carry Forward, 216 BPC Hierarchies, 90 Business Rules, 218, 462 BW Attributes, 24 BW Hierarchies, 26 BW InfoObjects, 24 BW Master Data, 25

C Calculate and store annual net income and retained earnings, 243 Calculate closing, 638 Characteristic Validation, 255 COI 10 Steps, 333 Collector, 177 Commenting Feature, 539 Consolidation Rules, 460 Consolidations Logic, 136, 639 Control Panel, 543 Conversion File, 167 Copy PL to BS, 133, 636 Currency Key Words, 303 Currency Processing, 305 Currency Translation, 296

Data Manager, 164 Data Validation, 251 Default Logic, 128 Definition of 'ORG' properties., 375 Delivered Packages, 177 Dimension by Application, 91 Dimension member examples, 93 Dimension Properties, 88 Dimension Types, 86 Dimensions, 21 Dynamic Hierarchy Editor, 340

E Eliminate ARAP, 422 Elimination Schema, 422 Entity Dimension, 96 Equity Method, 456–457 EvDRE, 547

F Flow Dimension, 95

G Groups Dimension, 98

H How to carry forward interim periods, 220 How to enter data into the DHE, 343 How to handle consolidation group changes, 342 How to Look up Journal Tables, 214 How to upload journals, 215

D Data 'writes', 30

2010


649

Index

BPC440

I

R

IC Matching Requirements, 401 InfoCube to InfoCube Load, 173 InfoCubes, 26 Input Templates, 543 Intco Dimension, 97 Inter Company Booking, 402

Rate Type, 299 Rate Type Property, 89 Reclassification, 5, 242 Reclassifications, 241 Referencing Applications, 43 Report Templates, 541 Reporting Interfaces, 537 Request Id's, 28

J

S

Journal Controls, 209 Journal Entry, 211 Journal tasks, 212

Scrip Debugger, 137 Star Schema, 27 System Constants, 137

L

T

ListCube, 195, 197 Live Reporting, 537 Logic Types, 125

The Dynamic Hierarchy Editor, 340 Time Dimension, 100 Top Down Allocation, 245 Transformation File, 168

M Member Ids, 88 Merge / Replace / Append, 175

650

U US Eliminations, 426

P

W

Park N' Go, 546 PPT Example, 553 Processing Dimensions, 104 Proportional Method, 459 Purchase Method, 329

Word example, 552


Y YTD Applications, 47

2010

Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.

2010


651

Bpc440 en Col95

Recommend Documents