Intercompany Matching Guide

SAP BusinessObjects Planning and Consolidation 7.0 & 7.5

version for the Microsoft platform version for SAP NetWeaver

Technical Consultants System Administrators

Release 724

PUBLIC Document version: 1.0 05/28/2010

ADDONX.BPC_SHARED_CONSOL

Target Audience

Copyright
Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty

2010-28-05

PUBLIC

2/13

Icons in Body Text

Icon Meaning Caution Example Note Recommendation Syntax

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

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

Example text

Example text <Example text>

EXAMPLE TEXT

2010-28-05

PUBLIC

3/13

Table of Contents
Intercompany Matching ............................................................................................................... 5 Creating New ICAccount and ICDataSrc Dimensions ............................................................... 7 Define Content of ICAccount and ICDatasrc Dimensions.......................................................... 8 Create the ICMatching Application and Define Security ............................................................ 9 Setup Script Logic and Business Rules Table ........................................................................ 10 Create an Input Schedule to Enter Data ................................................................................. 11 Create an IC Matching Report (for a Single Entity) ................................................................. 12 Test the Setup ....................................................................................................................... 13

2010-28-05

PUBLIC

4/13

Intercompany Matching
You use this to create a report that lists the intercompany matches and differences. These intercompany differences can then be booked automatically according to specific business rules.

Prerequisites
Security has been set up with full access given to all tasks and all existing applications. Exchange rates (AVG and END) have been loaded for the period that is used for intercompany matching. An entity-type dimension exists with a defined INTCO property. An intercompany-type dimension exists with a defined ENTITY property.

Features
Two dimensions are key for the matching process: data source (type D dimension) and account (type A dimension). The data source-type dimension is used to make the amounts entered by an intercompany counterpart available to an entity. An entity is normally only allowed to see their figures if it has the required security settings. It is necessary to copy the values entered by the intercompany counterpart to the entity, so that the entity can see the input of the intercompany counterpart against them. These two values need to be kept separated: this is the purpose of the data source-type dimension.

The dimension names used in this document are not mandatory. Planning and Consolidation uses the dimension types to identify dimensions; the dimension name can be set as required. The transaction currency-type dimension is not mandatory for intercompany matching or intercompany booking. If you do not plan to use it, you can ignore that dimension. The intercompany booking process only works after the intercompany data process has been run.

Activities
The intercompany matching process consists of the following tasks: 1. Creating the account-type and data source-type dimensions for use in the intercompany matching process. See Creating New ICAccount and ICDataSrc Dimensions [Page 7]. 2. Maintaining the dimension members that are required for the account-type and data source-type dimensions. See Define Content of ICAccount and ICDatasrc Dimensions [Page 8]. 3. Creating the intercompany matching application and define security. See Create the ICMatching Application and Define Security [Page 9].

2010-28-05

PUBLIC

5/13

4. Setting up script logic and the business rules table. See Setup Script Logic and Business Rules Tables [Page 10]. 5. Creating an intercompany input schedule. See Create an Input Schedule to Enter Data [Page 11]. 6. Creating an intercompany matching report. See Create an IC Matching Report (for a Single Entity) [Page 12]. 7. Testing the setup. See Test the Setup [Page 13]. The output of this process is a report that lists the intercompany matches and differences. These intercompany differences can then be booked automatically according to specific rules.

2010-28-05

PUBLIC

6/13

Creating New ICAccount and ICDataSrc Dimensions

You use this to create the ICAccount and ICDataSrc dimensions for use in the intercompany matching process. These two dimensions are key for the matching process.

Procedure
1. In the Admin Console, open the Dimension Library, and select the dimension AccountL. 2. In the action pane, choose Copy a dimension. 3. In Name and Description, enter ICAccount, then choose Save as dimension. 4. In the Dimension Library, highlight the dimension Datasrc. 5. In the action pane, choose Copy a dimension. 6. In Name and Description, enter ICDatasrc, then choose Save as dimension. 7. In the Dimension Library, and highlight the dimension ICDatasrc. 8. In the action pane, select Maintain dimension property. 9. Add the property IC_ORIGINE with a size of 2. 10. In the action pane, select Modify Dimension Property.

2010-28-05

PUBLIC

7/13

Define Content of ICAccount and ICDatasrc Dimensions

You use this to maintain the dimension members that are required for the ICAccount and ICDatascr dimensions.

Procedure
1. In the Admin Console, open the Dimension Library and select the ICAccount dimension. 2. In the action pane, select Maintain dimension members. 3. Update the member sheet. 4. In the action pane, choose Save to Server, and then Process dimension. 5. Choose OK to start the dimension processing. 6. In the Admin Console, open the Dimension Library and select the ICDatasrc dimension. 7. Repeat steps 2 to 6. 8. In the Dimension Library, from the action pane, choose Add a new dimension. 9. Enter TrnCurrency and an appropriate description, and click Go to Step 2 of 3. 10. Select the Type U Userdefined, and click Go to Step 3 of 3. 11. Add a new property called CURRENCY with a size of 20, and choose Add a new dimension. 12. Open the Dimension Library, and choose TrnCurrency. 13. In the action pane, choose Maintain dimension members. 14. Enter the dimension members. 15. In the action pane, choose Save to Server, and then Process dimension.

2010-28-05

PUBLIC

8/13

Create the ICMatching Application and Define Security

In order to run intercompany matching, you must set up a financial-type application. In this application, you must add the business rules table Intercompany Bookings and secure the legal entity-type dimension.

Procedure
1. In the Admin Console, select Application. 2. In the action pane, select Add a new application. 3. Enter an application name and description, select Financial as the application type, and LegapApp as the source application, then add the business rules table Intercompany Bookings. 4. Deselect the Dimensions checkbox, click Add a new application, and secure the legal entity-type dimension. 5. In the Admin Console, modify the member access profile by choosing Modify the selected profile definition in the Manage Profile Options action pane. Follow the prompts in the Modify Profile assistant. 6. In the BPC Administration Web page, select Application Parameters. Check that the application ICMatching is selected in the current view. 7. Change the parameter YTDINPUT to Yes. 8. Choose Update to save the changes. 9. In the Admin Console, select the ICMatching application. 10. In the action pane, choose Modify application, then choose Modify application again. 11. Select the name of the application set at the top of the list. 12. In the action pane, choose Set application set status. 13. Set the status to available, and choose Update application set status.

2010-28-05

PUBLIC

9/13

Setup Script Logic and Business Rules Table

This function validates the Intercompany Booking business rules table by setting up script logic and the business rules table.

Procedure
1. In the Admin Console, open the Script Logic folder, and select Default.lgf. 2. Edit the default logic. 3. In the action pane, choose Validate and Save. 4. In the Admin Console, choose Script Logic. 5. In the action pane, choose Create New Logic and in the Name field, enter ICElim, then choose OK. Create specific logic for IC Booking here. Reuse the ICElim package that already exists and not used in the ICMatching application. 6. Edit the default logic. 7. Select Validate and Save in the action pane. 8. In the Admin Console, open the Business Rules folder and choose Currency conversion rules. 9. Update the content of the table. 10. In the action pane, choose Save without validation and Validate Currency Conversion rules rule table. 11. In the Admin Console, open the Business Rules folder and choose Intercompany Bookings. 12. Update the content of the table. 13. In the action pane, choose Save without validation and Validate Intercompany booking rule table.

2010-28-05

PUBLIC

10/13

Create an Input Schedule to Enter Data

Procedure
1. Open Interface for Excel, and create a new EVDRE report. 2. Enter formulas using the Insert option. 3. In the action pane, choose Worksheet Dimension Lock Options, and set the lock options appropriately. 4. Choose Workbook Options, then select the following workbook options: o o o o o Refresh workbook on worksheet update Refresh workbook on workbook open Refresh after data send Expand on workbook open Expand on CurrentView change

2010-28-05

PUBLIC

11/13

Create an IC Matching Report (for a Single Entity)

Procedure
1. Open Interface for Excel, and create a new EVDRE report. 2. In the ColKeyRange cell, select the formula, and choose fx to open the Formula Editor. 3. Select the empty Range2, and select the four cells copied in the previous step. 4. Update the formula table. The value COL is added for the EVALUATE IN column for the row starting with CALC. 5. In the action pane, choose Worksheet Dimension Lock Options, and set the lock options appropriately 6. Update the formatting table. 7. Choose Expand all. Only the first columns of the report are displayed.

2010-28-05

PUBLIC

12/13

Test the Setup

Procedure
1. Open the input schedule that you previously created, and set the currency exchange rate. Make sure that currency exchange rates are defined for the period selected. 2. Click the empty green area, and choose EVDRE: Insert member. 3. Select I_CGUSA as INTCOL and T_EUR as TRNCURRENCY, then choose OK. 4. Find the account AS27480000 and enter 100 in the columns LC and TC. 5. In the action pane, choose Send Data, then Send Active Worksheet, and then choose OK in the confirmation dialog box. Make sure that the records were sent successfully. 6. Select the entity CGUSA, and repeat the same steps. 7. Close the input schedule, and open the IC Matching Report. 8. In the action pane, choose Home, and then Manage Data. 9. In the action pane, choose Run a Data Management Package. 10. Select Financial Process as Package Group, and double-click IC Elimination to start that package. 11. In the first screen, choose Next, and set the Data Region. Choose Next, and then choose Finish. 12. Choose View Status, and check that the package has completed successfully. Close all the dialog boxes. 13. Choose Home, then Reporting & Analysis, and then Open a blank workbook. 14. In the cell A1, enter =EVDRE(), and choose Refresh. 15. Set the EVDRE parameters, and set the current view. 16. Expand the report and compare the results. Check that two records are generated on the data source ICDIFF.

2010-28-05

PUBLIC

13/13