You are on page 1of 797
SAP BusinessObjects Planning and Consolidation, Version for SAP NetWeaver: Administration SAP Bu nessObjects - Financia Performance Manag Date Training Center Instructors Education Website Participant Handbook Course Version Cc Duration: Material Number Copyright Copyright © 2011 SAP .AG- All sights reserved ‘No part ofthis publeation! may be epreduved or Wansmite any frm otf an purpose without tl mission of SAP AG. The information gontied herein express ay be changed without prior notice Sonie software prods feted by SAD AG and its distributors contain proprietary software Leomponcs of ether soibware vera ‘Trademarks + Microsoitk, WINDOWS, NTR, EXCELY, Word®, PowerPoint ® aint SOL Server are registered trademarh of Mic sat Corporatio + IBM, D2, OS 2%, DAZGINR, Parallel Syspleo®, MYSTSAR, RS GADD, AINE, 83908 AS:HUW, OS 8908, and OS JUD are registered trdemarksof THM Comporation + GRACL IW is registred trademark ef ORACLE Conporatio = INFORMIX OnLine for SAP and INFORMIX Danae Se0ver IME of Informs Software Incomporaied © UNIX, X Opens, OSE 1. and Motif are + Citrivt the Citri Jogo. ICA. Program Ni ‘Vigeo! rane, Muliin® and other Citta product nates teeter A trademarks ‘rod wadaaths of the Open Cioup boriood®, Mota came, Win ames st herein are uaemarks of itr Systems, Ine + HIM DEIML, XML, XHTML are trademarks or euisterad tademarks of W308, World Wide Web Consortium, Massachusetts baste of Technolog + JAVA isa repistered ademark of Sun Microsystems, Ine + JAVASCRIPT # isa regiserol tench of Sun Microssstems, Ine used under Hicense For teelology invented and implemented by Netscape © SAP SAP Logo, R-2. RIVA, R 8, SAP Archivel ink, SAP Faniness Workllou, WebFows, SAP Harleiieh, BAPL SAPPHIRE. Management Cockpit sSAPsom Loge and msSAB.om ste leudesnachs of repisteredtnadesarhs of SAP AG it Gets ana in several ater counties ll fe world. All other products mentioned are trademarks or registered trademarks of their respestve eompines Disclaimer USE MATERIALS ARE PROVIDED BY SAP ON AN “AS IS" BASIS, AND SAP EXPRESSLY DISCLATMS ANY ANTD ALL WARRANTIFS, EXPRESS OR APPLIPD. INCI UDING WITHOUT LIMIIATION WARRANTIES OF MERCHAN ABILITY AND FITNESS FOR & PARTICULAR, PURPOSE, WITH RESPECT 10 THESE MATE RIMLS AND THE SERVICE, INFORMATION, TEXT GRAPHICS, LINKS. OK ANY OTH 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 WHHOUT LIMIATION LOST REVENUES OR LOST PSO IIS. WHICH MAY RESULT FROM IP USE OF THESE MATFRIATS 08 INCLUDED SOFTWARE COMPONENTS 9201211021726 This handbook is intended to complemen} the instructor-led presentation of this course, and serve asa souree of reference, [Lis nol suitable for self-study Typographic Convent ns, American English is the standard used in this handbook, The following typographic conventions are also used Example text Words or characters that appear on the sereen. These include field names, sereen titles, pushbuttons as well as menu names, paths, and options Also used for cross-references to other documentation both intemal and external Example text Emphasized words or phrases in body test, titles of aphies. and tables EXAMPLE TEXT Names of elements in the system, These include report haimes. program names. transaction codes. table names. and individual ey words of a programming language avhon surrounded by body text, for example SELECT and INCLUDE. Serven output, This includes file and dirvetory names and their paths, messages, names of variables and parameters, and passages of the source text of a program, Example text Exaet user entry. These are words and characters hat you enter in the system exaetly as they appear in the documentation — | Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate catrivs esenves ii 2011 2011 SAP AG. All rig ay About This Handbook Bpc420 Icons in Body Text The following icons ate used in this handbook % For more information. tips. or background Note or further explanation of previous point Exception or caution Procedures A v @ Indicates that the item is displayed inv the instructor's prescatation reserved Course Overview vii Course Goals. vii Course Objectives vil Unit 1: Application Presentation. a4 Introducing the Benefits, the Interfaces, and the Components 2 implementing SAP BusinessObjects Planning and Consolidation 4 Presenting Modeling Aspects 23 Unit 2: Configuration .oscssccucessecssesseestsenessnesseerecnieesnerseenecnneesnes 3B, Describing the Technical Architecture of BO PC 37 Navigating in the Administration Interface 4 Creating Environments 89 Creating Dimensions 82 Creating Models 125 Describing the Security Model 154 Defining Parameters 491 : Using the EPM add-in. 201 Introducing the Excel Interface of the EPM add-in 202 Unit 4: Data Acauisition. 251 Managing Data with Data Manager 262 Flat File Upload and BW Data Upload — Master Data and Hierarchy Upload and Loading of Transaction Data 267 : Logic Scripts. 375 Creating Basic Logic Scripts and Online Execution 377 Creating Logic Scripts and Central Execution 464 Defining Logic Scripts for Allocation. 498 integrating Logic Scripts and ABAP. 523 Introducing Member Formulas 548 : Business Process Flows . Creating Planning Business Process Flows 572 2011 2011 SAP AG. All rig eserved vey Contents Bpc420 Unit 7: Administration. 1633 Validating Master Data 635 Configuring Audits 654 Presenting Concurrency Locking 676 Configuring Work Status. 679 OPTIONAL: Explaining Transports. 700 TAT 721 Appendix 1: Web Client Interface Features Appendix 2: Workspace and Library Appendix 3: Library and Folders 729 Appendix 4: Flat File Upload - Append Package, Import Package and Import Append Package with Merge and Replace and Clear 735 Appendix 5: BW Data Upload - Aggregate Overwrite and Append with Merge and Replace and Clear 741 Appendix 6: BO PC NetWeaver Authorizations 745 Appendix 7: Appendix 2: Task Profiles and Descriptions 747 Appendix 8: Appendix 4: ‘Options in Transformation Files 755 Appendix 9: Appendix 5: Retraction Scenarios in BO PC 759 ay vi Target Audience This course is intended for the following audiences + Application Consultants + BO PC Administrators + Project Leaders + Project Team Members + Technical Pre-Sales Course Prerequisites Required Knowledge + BW310 . Excel Recommended Knowledge + Experience with SAP NetWeaver BW Course Goals This course will prepare you to + Configure SAP Bu: SAP NetWeaver + Understand the system architecture and integration ssObjects Planning and Consolidation (111.0), version for + Perform administration + Use logie for planning and reporting + Execute data imports, + Build business process flows for planni Course Objectives Afier completing this course, you will be able to: 2011 esenves vii 2011 SAP AG. All rig Course Overview Bpc420 Set up environments, models, and dimensions Work with hierarchies Navigate in the interface for Excel Pestiorm flat file, InfoCube to InfoCube transaction data imports Set up BW characteristic master data imports Create Data manaver package “links Work with logic, business add-ins (BAdI's), and custom process chains Execute Allocations Con! Set up work stams and security re business process flows Work with activity and data audit Discuss locking Discuss transports 2011 SAP AG Al Application Presentation Unit Overview This unit includes a conceptual overview, It shows the benefits of Business Objects Planning and Consolidation and some important modeling project guidance aspects, [Lalso gives some Unit Objectives Afier completing this unit, you will be able to + Explain the key terms + Discuss the benefits of SAP BusinessObjects Planning and Consolidation + Describe the components + Identify the most important features of SAP BusinessObjects Planning and Consolidation + Discuss the implementation process + Deseribe goncral business requirements for the planning and consolidation application + Discuss the key tems of Planning, and Consolidation + Explain the main idea of Dimension properties in Planning and Consolidation + Deserihe Modeling. of Bottom up and ‘lop Down Planing in Planning and Consolidation Unit Contents Lesson. Introducing the Benefits, the Interfaces, and the Components 2 Lesson: Implementing SAP BusinessObjects Planning and Consolidation... “1 Lesson: Presenting Modeling Aspects 23 2011 © 2011 SAP AG All cig Unit 4: Application Presentation Bpc420 Lesson: © Introducing the Benefits, the Interfaces, and the Components Lesson Overview In this lesson, you will learn about d Consolidation as well benefits of SAP BusinessObjects Planning and the interfaces. the hey teem, and eompon Lesson Objectives After complet iis lesson, you will be able to + Explain tho kev torms + Discuss the benefits of SAP BusinessObjects Planni + Describe the components nd Consolidation + Identify: the most important features of SAP BusinessObjects Planning Consolidation, and Business Example You key mplementing the produet and therefore need to familiarize yoursell with the mes, the interfuees, and the components, The Key Terms In this seetion, you will eam some of the key terms, Key Terms Term Definition Dinvensions Master data such as companies and accounts Models ‘Transaction data such as expense values and. exchange rates Environments Contains dimensions and models, for example BW SAP Business Information Warehouse Properties Related fields such as eurrency Dimension Members Example: Company C1000 Base Level Members Members with no children Ey 2 @ 2011 SAP AG, All rights reserved BPc420 Prior Versions versus 10.0 (1) Terms Lesson: Introducing the Benefits, the Interfaces, and the Components Previous Term 10.0 Term Applications Models: Environments Performer Dimension Iype tuk Dimension ‘Iyp Gran Dimension Type Scope Dimension Type Live Reports Web Reports / Input Forms Dynamic Hierarchy Editor Ownership Manager Current View Context Member Access Pi Data Access Profile Apshell EnyironmentShell Validations Controls > Note: The terms above apply to both platforms (listed below) (1) SAP BusinessObivets NetWeaver (1) SAP BusinessO! platform, Plannin 5 Planning. and Consolidation 111.0 and Consolidation 10.0, version for SAP Planning and Consolidation is part of Enterprise Performance Management he Microsoft AG. All nights reserved 37 Unit 4: Application Presentation pce20 ea roms — Tot a — 9 A eas ae =| ico ee a == = use — ae, na Sen eae sttowreand Seah ard ~ See —— = Newnat —ogenet Figure 1: SAP BusinessObjects Portfolio with SAP Applications Regardless of which inter ce is used for reporting, the data comes from one central database. From there, you can retneve data into four possible inte faces, ‘The data is stored in InfoCubes for each model, The InfoCube is a star sehema and comprises a fact table and dimension tables. @ Environment: = Dimensions: ‘The Excel Interface ofthe EPM addin = Models 7 Model ‘The Powerpoint Interface of the EPM addin Planning and Consolidation 3 Web interface ———— “The Word Interface of the EPM add-in Figure 2: SAP BusinessObjects Planning and Consolidation Architecture aya @ 2011 SAP AG, All rights reserved BPC420, Lesson: Introducing the Benefits, the Interfaces, and the Components, The Ese! herface 0 sources such as Plan can be used (0 access d EPM a from multiple jnxz and Consolidation and Profitability Cost Management, for example. The cata rvirievat options are the same, regardless of the source. However, when used for the planning and consolidation application. additional features are available including data input and Data Manager. for example. Data Manager is used to import data and run planning funetions such as cops, delete ane move EPM data retrieval: ‘SAP BusinessObjects Planning and ® Create reports Consolidation only: = Analyze data «Data input = Dynamic formatting = Planning ® Calculations and charts = Workbook collection «= Print and share «= Data Manager Figure 3: The Excel Interface of the EPM Add-In Note: The term “planning” above refers to the spread. trend, and weight functions that are used to disaggregate planning data. ‘Workbook collection” refers to the distribution and collection feature that can be used fo distribute reports via e-mail. for example. oF to collect planning data entered in Excel templates ‘The cate of use of SAP BusinessObjects Planning and Consolidation has always been a key feature, along with the fact that dats is stored in a central database and not in local spreadsheets 2071 ©2011 GAP AG All nghisresewed 5 ay Unit 4: Application Presentation Bpc420 @ Familiar, Easy to Use Exates rapid adoption by ever i Dt iar ae aay Fe ee Te ene 3 eee spire ctbot Gos obs an & Le = Unified -Planning and Consalidation = A Sige Envrrmetreaicn £ Ccoreccsteand ec muple —Sndumpacs daoyment é ‘owned and Managed by Business Users «Business users manago processes, A models, and reports, with “mat iece . = Epencence oar 2 © Cotaboratvely create plans i ee Business process centric * Confgurebe Busines Prosess Fle Sue tere and ass process + A Sorastoncy | FF - emma E eno value of your ivestmentin é ee a both SAP and non-SAP environments Figure 4: The Value of Planning and Consolidation Business process Hows (BPFs) provide the customer with a web-based launchpad. guided navigation, e-mail, and visibility of process status. Business process flows ean bbe used fo improve the coordination aspects of a process, Actions that are Open have an Aetion Reguired of To Perform. An action ean only be performed if its preceding action 1s complete, That is why the Planning Piurctions action has the status Pending ‘The action status can also be changed via the Aetiony button, a6 @ 2011 SAP AG, All rights reserved BPc420 Lesson: Introducing the Benefits, the Interfaces, and the Components, @ QO Business Process Flows ensure consistency and visibility ‘Step-by-step guidance through consolidations processes Enforce policies and procedures - track process status and completion Details: EKPENSE_PLANNING - Forecast, 2012 show [ard Oven | Acne « | Reopen Refresh Nene (cote -Aaton Regured satus IMPORT ACTUAL DATA Consuting © ToPerm 1B Open IMPORT ACTUAL DATA. Manufactuting © ToPertm 1B Open PLARMMOFLNCTONS —— Conouting 1B Pending PLANNNGFUNCTIONS — Merufoctuing 1B Pending MANUAL RPUTPLANAING —Censiing 1B Pending MANUAL REUTPLARNING Merutectureg 1B Pending Figure 5: Process-Centric Singe itis easy to use, IT does not always need to be involved in the configuration of SAP BusinessObjects Planning and Consolidation 2071 ©2011 SAP AG All nghisresewed 7a Unit 4: Application Presentation Bpc420 @ mM ramones == ee a = Roles ——P = « Excel Interface of the EPM add-in = Privileges ‘Temptetes Data and Applicaton Infrastructure Database Server 1 Application Server = OLAP Structure e : «= Create and Modify Metrics =| jet Up by IT - Owned and Maintained by Bu: jess Users s Home workspace provides an easy to use Web interface ‘Aweb launch pad for users , Easy access to Activities Easy access to Process Monitor Easy access to Document attachments Process Monte Library of web reports / input forms / workspaces Consolidation Central Audit and Security reports a, Figure 7: The Home Workspace a7 8 © 2017 SAP AG. All rights reserves 2011 BPC420, Lesson: Introducing the Benefits, the Interfaces, and the Components, 8 ‘The Home tab provides a very convenient entry point for SAP BusinessObjects Pl ining and Consolidation users, and includes the follow ing components © Starr Page ~ includes links to create reportsand launch the Excel interface of the EPM add-in, for example + Aenvities ~ activities the user is involved in + Process Monor ~ micludes the status of processes + Library - includes public and private reports, input forms, workspaces. and dashboards, for example + Documents - this 18a central storage location for important attachments + Consolidation Central - the all-in-one interface for accountants + Consotidasion Monitor ~ used to exceute closing activities and monitor pr + Contrets Aten so ir used Lo exceute data validation and monitor the results waly ~ used to manage and ercate journal entries + Ownership Manager - used to manage ownership data 2071 © 2011 SAP AG All rights resewved 9 my Unit 4: Application Presentation Bpc420 @ Lesson Summary You should now be able to + Explain the key tems and Consolidation + Discuss the benefits of SAP BusinessObjects Planning + Deseribe the compon nis + Identify the most important features of SAP BusinessObjects Planning and Consolidation 9 2011 SAP AG. Al rights reserved BPC420, Lesson: Implementing SAP BusinessObjects Planning and Consolidation Lesson: © Implementing SAP BusinessObjects Planning and Consolidation Lesson Overview In this lesson. you will leam about implementing SAP BusinessObjects Planning and Consolidation Lesson Objectives Aficr completing this lesson, you will be able to + Discuss the implementation process + Deseribe general business requirements for the planning and consolidation application Business Example Your company or your elient has purchased SAP BusinessObjects Planning and Consolidation, so you need to leain how to implement it Implementation Factors Every projeet has the following factors to consider Project Objectives Timeline Scope Project Start Sequence Figure 8: Implementation Factors 2071 © 2011 SAP AG All nights resenved 11 Unit 4: Application Presentation Bpc420 © ‘The Most Important Success Factors for BPC Implementations: = Product expertise = Astrvctred project delivery using hest Method Based Scoping (ASAP 7.1 BPC Add-on), = Blueprinting Project Quality Assurance > Note: Performance is a very important component in a project and it should be addressed right from the beginning of the project add-on for BPC SAP Methodology for hmplementation 7.1 Pushing the performance topic to the end of a project will, in most eases. cause delays in the project Possible Reasons for Performance Issues: + Lack of data in the development system (reports were built on completely empty applications). so the performance of the reports could nat be assessed up front (some dummy data should be generated in the development system) + Lack of stress testing aetivities in the project plan, in a system with Tange number of concurrent users + Design errors: An application. calculation, or report was designed in a way that they could not be hi perform Factors to consider Factor Example Project Objectives Define the project objectives. For example. implement cast center Seope Detennine the scope of the implementation Por example, the seope may only be for North America and Ewrope Define the project strateuy. Por example, perform most cost center planning, using Planing ame Consolidanion ay 12 9 2011 SAP AG. Al rights reserved BPC420, Lesson: Implementing SAP BusinessObjects Planning and Consolidation : Define both the timeline for the entire project and the implementation sequence Sequence Determine the sequence oF events from a project planni verspective, ‘Resonrces Identify the imen 1 project eam mentbers and consultants required The Roadmap to Success SAP and its partners have implementation methodologies that are used to standardize the process. The roadmap includes the key steps in the process of implementing a solution 1 SAP BY Strategic Decision. For the planning and consolidation application, you may need to decide whether to use an existing BW server or install a standalone server, for example Pilor Project: 4 pilot phase may be beneficial to help determine your “wo-be solution Pret’ Once your “to-be” solution has been determined, you proceed withthe implementation ‘The Implementation Roadmap forms the methodical framework for the steps tht you require to implement SAP BusinessObjects Planning and Consolidation, It includes the necessary project mana fi ation for the business processes. aS well as the technical features, the test procedure, and the training, concepts The methodology of the an Roadmap supports the inclusion of these requirements that are used as the basis tor installing, the application 2071 © 2011 SAP AG All nights resenved 13 Unit 4: Application Presentation Bpc420 @ ‘SAP BI Strategie Decision Global ego, Ter te otemeraton Gti Impibmentations Local BW Strategy Figure 9: The Roadmap to Success © Pryject Preparation - initial project planning, project procedures. landscape strategy = Business Blueprint ~ project planning. architecture = Real = Pina! Preparation ~ wst the solution, conduet training ion ~ configure the initial solution = Go Live and Support - cut over ( the new system, Follow up on possible go live issues Below. you ean see the recommended resourees by phase ay 14 @ 2011 SAP AG, All rights reserved BPC420, Lesson: Implementing SAP BusinessObjects Planning and Consolidation i) Method-based role allocation - Delivery Plan (ASAP 7.1) Figure 10: Method-Based Role Allocation BPC isa very versatile too! and ean be used to cover many different business processes. A BPC Business Blueprint document can therefore look quite different, dependling on the type of project and on the elient as well, Dus to the nature of BPC, there is nota single template that will it all requirements The bluoprinting activity isa key activity in any BPC project. It is important not to underestimate the time required for this task (at least 20 to 30 pereent of the total time of the projeet ~ depends on the availability of documented requirements) Prototyping is key for carly user involvement and to prove designs. It reduces change management efforts during Go-Live Preparation (lean implementation mode!) Business requirements hie al the center of the project. ‘The scope of your initiative: must be driven by business requirements. A key ingredient is to gather securate requirements in the information gathering process. 2071 © 2011 SAP AG All rights resewved 15 Sy Unit 4: Application Presentation Bpc420 @ : Preparation Requirements Analysis ‘Matching Presentation Documentation/Tools Figure 11: Information Gathering Process + Preparation Identification of the interview / workshop team as well as the interviewees / attendees heduling interviews/workshops — Communication of project goals, moles, and responsibilities + Reguivemens analysts Use SAP-delivered business content as at first step to structure the analysis Collect the business requirements, foc ny. on the processes Find a suitable combination of interview and workshop techniques + Matching — Cheek user requirements against the business content Identify gaps = Develop strategies to close gaps © Presentarion Prepare and publish the results Find age De sment on next steps mine success eriteria and risk fa Development Guidelines Here are some development guidelines to keep int muind EY 16 ©2017 GAP AG, Alrights resewves zon BPC420, Lesson: Implementing SAP BusinessObjects Planning and Consolidation © Naming conventions Responsioites ‘Authorization concept Gioballocal data Development Master data renee Transaction data Data Flow Data targets Bl objects Figure 12: Development Guidelines + No + Responsih + Globe! Loca! data = identify data sti Data model integration DW Archiving Initial data transfer Delta handling Operating concept! transport Business content Documentation Special topics ay gniddedines - define naming conventions for all objects ‘ies ~ define and communicate to each team member an concept ~ build your security plan early in the projeet layers where you may liave a corporate repository of Global data versus an application-specific set of Loca! data, + Master dats - identity where master data will be main + Data flow - similar to the above but includin ied on dora ~ identify where transaction data will be sourced transformations + Pasa sorgess ~in the data How, identify where data wall be stored + objects - determine which BNV objects will be involved in the data flow + Pata model wtegration ~ are there ink InfoCubes for example" + EDI do you need to use other Ht Iaformas + Archiving a life eyele strateg: + trie + Data hand and mappiny prise Dates Warehousi ration points between BW and Planning. uy solutions such as is important to reduce the storage of older data dota rangger ~ daring start-up, how will the inital data transfer occur 4g - similar to the above, but also include possible tanstiormation 2071 9 2011 SAP AG. All rights reserved 17

You might also like