SAP BOBJ Planning & Consolidation, version for SAP NetWeaver How-To Guide How to do Breakdown Validation in SAP BPC 7.0 for the SAP NetWeaver Platform Applicable Releases: SAP BPC 7.0 NW SP02 (and higher) Version 1.0 November 2009
Copyright 2009 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. 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 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. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way.
Document History Document Version Description 1.10 << Enter your summary of changes in this version >> 1.00 First official release of this guide
Typographic Conventions Icons Type Style Description Icon Description Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Caution Note or Important Example Recommendation or Tip Cross-references to other documentation Example text Emphasized words or phrases in body text, graphic titles, and table titles Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 orenter.
Table of Contents 1. Business Scenario...1 2. Background Information...1 3. Prerequisites...2 4. Step-by-Step Procedure...3 4.1 Create the Validation...3 4.1.1 Assign Driver Dimension...3 4.1.2 Rule Maintenance...5 4.1.3 Turn Validations On/Off...7 4.1.4 Check Validation...8 4.2 Test the Validation Rules...9 4.2.1 Manual Planning...9 4.2.2 Data Manager... 11 4.2.3 Journals... 15
1. Business Scenario This document describes how to set up new validation used in the business consolidation environment with BPC7.0 SAP NetWeaver BI based version. To setup the consolidation environment please refer to the How To setup the Consolidation environment using BPC 7.0 for SAP NetWeaver document. This How to Guide will focus on dimension properties and their required settings for creating the backend validations in the SAP NetWeaver system. This validation will ensure that only valid records are written to the application during write back (i.e. to prevent incorrect records being saved to the cube). Please note that the breakdown validation is also referred to as characteristic validation or backend validation. 2. Background Information Validations are designed to prevent incorrect records being saved to the cube. The user controls what is deemed an incorrect record. An example of an incorrect record is one where you have specified an intercompany Account, but left the Trading Partner dimension empty. Please note that in BPC 5 and 7M, validations have been implemented but only Journals data is checked for validation. Therefore, it is very easy to end up with invalid records in your application as all other modules (Excel, Web, Data Manager, etc) will not be validated. The existing Journals validation functionality is not implemented in BPC 7NW. Instead, this module is intended to supersede this functionality. In BPC 7, it is not possible (or supported) to get data into a cube without going through the Write-Back module. Therefore, we implemented the validations in write-back, to ensure that invalid records can not get into the cube from any source including journals, all Data Manager Packages, and manual data input. Validations introduce the concept of a Driver Dimension. This is the dimension in each application that the validation rules will be created from. In most cases, the Driver Dimension will be the Account dimension, but it can be any dimension. However, it is only possible to have 1 driver dimension per application. Per the previously described example, Account (intercompany account) should be the driver dimension because we want to check the value of another dimension (e.g. IntCo for Trading Partner) whenever a record is written to a certain account member (e.g. ICSales). The rules are created at the Dimension level, not at the application level. That means in this example, the rule is created against the Account dimension. Therefore, the same set of rules can be used in multiple applications. Validation configuration is developed in the SAP NetWeaver BW environment (the BPC Backend or SAP NetWeaver tier), using transaction code UJ_VALIDATION. All configurations are AppSet specific. Configuration for Validations must be performed in the SAP Graphical User Interface (GUI).
3. Prerequisites Successful installation of BPC 7.0 version for SAP NetWeaver. Access to BW via SAP Graphical User Interface Access to SAP transaction code: UJ_VALIDATION
... How To do Breakdown Validation in BPC 7 NW 4. Step-by-Step Procedure All breakdown validation configurations are AppSet specific. 4.1 Create the Validation 4.1.1 Assign Driver Dimension 1. Double click the SAP Logon shortcut icon on your desktop. 2. Log in to the BI Backend system where the BPC resides. 3. In the upper left hand corner, enter Transaction UJ_VALIDATION and then click the green check mark. 4. The BPC Validations Maintenance -Initial Screen is opened 5. Select the appset where you want the validation rule to be applied to. 6. Click on Assign Driver Dimension as shown above. Note: This is where the user selects which dimension they want to be the driver dimension for each Application. If you leave the driver dimension empty, then no validation rules will be applied to this Application. 7. Click on the symbol circled below and select C_ACCT for the Consolidation application which is the Account dimension type of the Consolidation application.
Tip: The help popup (F4) window displays only the dimensions assigned to the application. 8. Once the dimension is selected, click on Save Driver Dimension setting as shown above. 9. In the status bar you will see the message. 10. Once the setting is saved click on the back button to go back to the BPC Validations Maintenance -Initial Screen.
4.1.2 Rule Maintenance 1. Click on the Rule Maintenance button to define the validation rules as shown below. Note: The Edit Rules icon allows you to jump directly to maintaining the rules for one dimension. Before clicking on the button, a row must be selected from the Assign Dimension Driver Screen. 2. Select the C_ACCT dimension by clicking on the symbol circled below and then click on the green check mark. 3. The BPC Validations Maintenance Edit Rules screen is opened as shown below: 4. Click on Create Rule button to create the validation rule. 5. Enter the validation rule. In our example we going to test that all the Inter company accounts should have valid trading partner populated.
Note: When maintaining a rule, you can give it a text description that gives a brief description of what the rule is defined for. You can assign the rule to multiple members (in this case, all IC account members are used). You can then choose to use the logic table or write you own custom check as a BAdI (i.e. ABAP code for more complicated checks). In the logic table, all rules must be passed. In this example, you can see that the Logic Table is still being used, but in this case, the INTCO dimension has single value. But you can define multiple values if required depending on the requirement. This rule means that a record can not be saved to the cube, if the Account is in the list and for the IntCo has a value of I_NONE. Note: The only operators supported are = and <>. In this example Rule, please note the following points: One is that you can use a range of members (useful for account number ranges, or for creating a rule that applies to ALL accounts, such as in this example). You can also use members that don t exist yet (you will get a warning, but you can continue through this). The BAdI Implementation has been selected. You can click on the BADI name provided to create the implementation (see Technical section for details). 6. Here is the information that has been entered: Rule Description: IC accounts require Trading Partner. Assigned Members: All IC accounts. Validation Logic: INTCO Dimension for Dimension <> for Operator I_NONE for Members.
7. Click on Save and you should see the on the status bar. 8. Once the rule is saved click on the back button to go back to the BPC Validations Maintenance -Initial Screen. 4.1.3 Turn Validations On/Off 9. Click on the Turn Validation On/Off button as shown below: 10. It is also possible to turn validations on/off by application and by 3 different modules: Journals, Manual Planning and Data Manager.
Note: Manual Planning means Excel and Web input by users. Data Manager includes all Data Manager logic, K2 Script Logic, and Parameter Driven Logic (Consolidations). 11. In our example we are going to turn the validation on for both the Journals as well as the Data Manager as shown below: 12. Turning validations On/Off allows you to specify whether you want the rules that have been implemented to actually be obeyed. By default, all modules are turned Off, so you must proactively turn validations On. 13. Click on Save Validation Settings as shown above to save the setting. 14. The message appears on the status bar confirming that it is successfully saved. 15. Once the setting is saved click on the back button to go back to the BPC Validations Maintenance -Initial Screen. 4.1.4 Check Validation 16. Click on Check Validation button as shown below to check if there are any inconsistencies. 17. This check will ensure that the validation have passed successfully as shown below.
... How To do Breakdown Validation in BPC 7 NW 18. This concludes the setup required at the Backend BW System. 4.2 Test the Validation Rules As described in section 4.1.3 in our example we have turned on the validation for both the Journals as well as the Data Manager. This section will show how to validate that the validation rule is ensuring that no incorrect records are allowed. 4.2.1 Manual Planning These are done using the BPC for Excel and follow the steps mentioned below after you successfully log in to the system. 1. From the Action Pane, click Data Input. 2. From the Action Pane, click Open a blank workbook. 3. In cell A1 type =EVDRE() and press [Enter]. 4. Click on the Refresh Workbook icon from the BPC for Excel toolbar. 5. When prompted to clear existing input data, select Yes. 6. In the EvDRE Builder select the Entity on the column and C_ACCT and the IntCo in the row. Leave the defaults as is and click OK. 7. Ensure your current view has the Intercompany account and all the respective basemember selected. In this example we use the current view shown below:
8. Verify that your workbook looks similar to the following: 9. From the Action Pane, click Send Data. 10. From the Action Pane, select Send active worksheet. 11. When prompted, 1 record(s) will be sent. Do you want to continue? click Yes. 12. Verify that the rule has been violated as shown below.
13. Close the Refresh schedule results dialog box. 14. From the Excel File menu, select Close to close the workbook and do not save any changes if prompted. 4.2.2 Data Manager 1. Open native Excel and enter the test data and save the file as Validation.csv on your desktop. 2. From the BPC For Excel Action pane select Manage Data/Upload Data File. 3. Click the folder icon in the source file to select the.csv file you just created.
4. 8. In the destination field, click the folder icon. The filename is populated automatically. Then click Save and OK. 5. Ensure you get the following message and then click OK. 6. Select Preview to see the records in the file. 7. From the edata menu, select Run Package. 8. Select the ImportTransactionData and click Run. 9. In the Import File field, select the.csv file you created earlier to import the data from. 10. Select the transformation file and click Open and then click Next.
Select Run now and then click Finish. 11. View the status of your data load. Double click the log when the status is completed to view it. 12. Select the last task that shows and click on Detail.
13. Click on the Package log to see the details as shown below
14. Click on the Reject Records to see the records that was rejected by the system. 4.2.3 Journals 1. In the Admin Console, Select the Consolidation Application and click on Journals. In the Action Pane select Journal Wizard. a. In Step 1, select the following dimensions i. C_Category ii. RptCurrency iii. C_Datasrc b. In Step 3, Arrange the dimension in the following order: i. C_ACCT ii. Entity iii. Flow iv. Intco c. In Step 4, click Next In Step 5, click Finish (this process may take a couple of minutes to complete)
2. Open BPC for Excel. 3. Click on Journals in the Action Pane, then click on Enter a new journal. 4. Fill in the journal according to the following print screen, then click on save journal in the Action Pane 5. Click on Post Journal, answer Yes to the question and wait for the confirmation dialog box. 6. You will see that the validation rule will fail as there was no IntCo entered for C_ACCT 140040.