SAPBO - SAP BusinessObjects for SAP Netweaver BW(Col91)

SAPBO SAP BusinessObjects for SAP NetWeaver BW SAP NetWeaver

Date Training Center Instructors Education Website

Participant Handbook Course Version: 91 Revision A Course Duration: 2 Day(s) Material Number: 50098327

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.

g2010027115034

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.

2009

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

SAPBO

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 SAP AG. All rights reserved.

2009

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

Unit 1: SAP BusinessObjects Strategy ............................... 1 The SAP BusinessObjects Tools......................................2 SAP BusinessObjects Roadmap......................................9

Unit 2: BusinessObjects Architecture .............................. 25 Architecture Overview ................................................ 26 BusinessObjects Integration with SAP solutions ................. 36

Unit 3: Crystal Reports ................................................. 45 Crystal Reports Connectivity with SAP Netweaver BW.......... 46 Create a Report with Crystal Reports .............................. 57 Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures. ........................... 74

Unit 4: Web Intelligence ............................................... 103 BusinessObjects Universe ..........................................104 SAP BusinessObjects Terminology ............................... 116 SAP Hierarchies in OLAP Universes ..............................131 Web Intelligence Connectivity with SAP Netweaver BW .......136 Create a Report with Web Intelligence ............................139

Unit 5: Live Office....................................................... 153 Live Office.............................................................154

Unit 6: Xcelsius.......................................................... 167 Xcelsius Connectivity with SAP Netweaver BW .................168 Query as a Web Service ............................................172 Create a Dashboard with Xcelsius.................................179

Unit 7: Special Themes ................................................ 213 Authorization..........................................................215 Intelligence Search ..................................................220 BusinessObjects Explorer (formerly Polestar) ...................229 Scheduling ............................................................236 Performance ..........................................................243

2009

© 2010 SAP AG. All rights reserved.

v

Contents

SAPBO

BI Widgets (Optional)................................................248 Auditing (Optional) ...................................................252

Unit 8: Perspectives .................................................... 261 Perspectives (Optional) .............................................262

Unit 9: Appendix ........................................................ 269 Additional Exercises .................................................270

vi

© 2010 SAP AG. All rights reserved.

2009

Course Overview This course provides and introduction to the various integration points between SAP NetWeaver Business Intelligence and SAP BusinessObjects. During the course, you will examine BusinessObjects tools such as Crystal Reports, Web Intelligence, Xcelsius, Query as a Web Service and others and how these analysis tools can access the data from an SAP BW data warehouse.

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

SAP Netweaver BW customer, project team members, and consultants

Course Prerequisites Required Knowledge •

Fundamental knowledge in SAP NetWeaver BW 7.0 Advanced know-how in reporting capabilities in SAP NetWeaver BW 7.0

Course Goals This course will prepare you to: • • • •

SAP Business Object strategy SAP data provider for BO frontend tools Actual reporting capabilities with SAP Business Object (short introduction) Comparison and discussion of the different tools

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

2009

Introduction of the reporting options with SAP Business Objects alongside with the product roadmap. Participants should learn about the strategic development of SAP Netweaver BW in combination with SAP Business Objects The tools in SAP Business Objects are introduced and participants gain practical experiences based on hands-on sessions

© 2010 SAP AG. All rights reserved.

vii

Course Overview

viii

SAPBO

© 2010 SAP AG. All rights reserved.

2009

Unit 1 SAP BusinessObjects Strategy Unit Overview In this unit, you will be introduced to the concepts of Business Intelligence, the BusinessObjects Enterprise, and to the various roles that are important in your organization as you implement your business intelligence strategy. Later in the unit, the SAP BusinessObjects roadmap will be discussed.

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

Describe Business Intelligence and BusinessObjects Enterprise. Describe the BusinessObjects Enterprise client applications by role. Explain how the new SAP BusinessObjects Intelligence Platform co-exists with SAP Netweaver BW.

Unit Contents Lesson: The SAP BusinessObjects Tools ......................................2 Lesson: SAP BusinessObjects Roadmap ......................................9

2009

© 2010 SAP AG. All rights reserved.

1

Unit 1: SAP BusinessObjects Strategy

SAPBO

Lesson: The SAP BusinessObjects Tools Lesson Overview This lesson provides a high-level overview of the different client tools and applications in BusinessObjects Enterprise.

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

Describe Business Intelligence and BusinessObjects Enterprise. Describe the BusinessObjects Enterprise client applications by role.

Business Example What is Business Intelligence? By understanding Business Intelligence (BI), you will better comprehend how a BusinessObjects Enterprise solution addresses the BI product spectrum. Gartner defines Business Intelligence Gartner, Inc., a research and advisory firm that helps clients leverage technology, coined the term “Business Intelligence” in the late 1980s. Business Intelligence, as defined by Gartner, is an iterative user-centered process that includes accessing and exploring information, analyzing this information, and developing insights and understanding that lead to improved and informed decision making. BI usage crosses the spectrum of users, both internally and externally throughout any enterprise, and includes rank-and-file workers, executives, analysts, and knowledge workers. Examples of internal and external BI applications include: • • • •

2

Generating a class list for a training session Creating an employee performance review Scheduling in a health care setting Manufacturing computer parts

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: The SAP BusinessObjects Tools

Benefits of Business Intelligence Business Intelligence can help organizations to: • • • • • • • • •

Identify and track key performance metric against their direct competitors and the overall market Improve customer service and target high yield accounts Streamline operations and improve supplier and warehouse operations Identify successful marketing campaigns Improve response time to market trends and customer requests Decrease query and reporting time Reduce cost and anxiety over compliance Deliver true cost of Days Sales Outstanding and services Reduce strain on IT departments

Business Intelligence provides insights that enable business managers to make tactical decisions, as well as to establish, modify, or tune business strategies and processes in order to gain competitive advantage and improve business operations and profitability.

Describing BusinessObjects Enterprise BusinessObjects Enterprise brings together features from across the BusinessObjects product line to meet the diverse needs of users, from reporting query and analysis, dashboards and visualization to predictive analysis. BusinessObjects Enterprise ensures that all people within an organization get the right interface and level of interactivity necessary for their role

Describing BusinessObjects Enterprise client application by role BusinessObjects Enterprise includes and/or interacts with most BusinessObjects client tools. Depending on the job role, different client tools are used. The major four roles in BusinessObjects Enterprise are: • • • •

Administrator Business User Data Manager Designer

The following diagram identifies some common roles and the client tools that may be used in BusinessObjects Enterprise.

2009

© 2010 SAP AG. All rights reserved.

3

Unit 1: SAP BusinessObjects Strategy

SAPBO

Figure 1: Roles In BusinessObjects

Role

Tools

Description

A web-based interface that end users access BusinessObjects Enterprise to view, schedule, and keep track of published reports. InfoView

Business User

Web Intelligence

A web-based tool that provides query, reporting, and analysis functionality for relational data sources in a single web-based product. Web Intelligence allows users to create reports, perform ad hoc queries, analyze data, and apply report formatting.

Web Intelligence rich client

Web Intelligence can be used offline as a Web Intelligence rich client, or as a standalone application.

Live Office

BusinessObjects Live Office integrates with the Microsoft Office environment, allowing for dynamically updated data to be embedded within Microsoft PowerPoint, Excel, and Word documents. In addition, you can share your documents with others over the web for collaborative decision-making.

Query as a Web Query as a Web Service provides new and Service easy ways to analyze information through user-driven client solutions for businesses. Business Intelligence (BI) content is usually bound to a specific user interface of BI tools.

4

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: The SAP BusinessObjects Tools

Query as a Web Service changes this by allowing BI content to be delivered to any user interface that can process web services.

Designer

2009

Voyager

Voyager is an AJAX-based online analytical processing (OLAP) web client designed for business and financial analysts. It not only provides access to a wide range of OLAP databases, but also allows users to combine information from different systems within a single work space. Voyager offers a comprehensive range of business and time calculations, and includes features such as time sliders to analyze OLAP data.

Dashboard Builder

A web-based tool used to monitor key performance indicators (KPIs) and proactive alert managers via email and dashboards with the information they need, wherever they are.

Performance Manager

A web-based tool that allows users to track and analyze key business metric via management dashboards, scorecards, set analysis, and alerting.

Crystal Reports

A Windows-based reporting tool that is the industry standard. Used to create and integrate powerful reports in BusinessObjects Enterprise.

Web Intelligence

A web-based interface to provide query, reporting, and analysis functionality for relational and OLAP data sources all within one web-based product. Allows users to create reports, perform ad hoc queries, analyze data, and apply report formatting.

Dashboard Manager

A web-based tool that facilitates the deployment of powerful BI dashboards.

Desktop Intelligence

A Windows-based reporting tool that installs with BusinessObjects Enterprise. Designers can create reports, then publish them to InfoView where they can be viewed and scheduled. Users can share and distribute Desktop Intelligence documents by exporting them in different formats.

Xcelsius

Xcelsius is an intuitive application that uses a Windows interface to allow you to build interactive models of data and formulas from Excel spreadsheets. These models can then

© 2010 SAP AG. All rights reserved.

5

Unit 1: SAP BusinessObjects Strategy

SAPBO

be exported in multiple formats to meet your specific business needs and be used by other individuals in your organization.

Administrator

6

Central Management Console Administrator (CMC)

A web-based interface that allows you to perform user management tasks such as setting up authentication and adding users and groups. It also allows you to publish, organize, and set security levels for all of your BusinessObjects Enterprise content and enables you to manage servers and create server groups.

Central Configuration Manager Administrator (CCM)

The CCM is a Windows based application that allows you to create and configure SIA nodes and start/restart your Web Applications Server. In addition, the CCM allows you to configure Windows specific networking parameters (such as SSL encryption). These configuration parameters apply to all the servers contained in the node. The CCM can also be used for limited system administration such as starting and stopping servers.

Publishing Wizard

A locally-installed Windows application that enables both administrators and end users to add reports to BusinessObjects Enterprise. It can be used for mass publishing of reports.

Report Conversion Tool

The Report Conversion Tool converts Desktop Intelligence reports to the Web Intelligence format and publishes the converted reports to the CMS.

Import Wizard

A locally-installed Windows application that guides administrators through the process of importing users, groups, and folders into BusinessObjects Enterprise. It also allows you to import objects, events, server groups, repository objects, and calendars in BusinessObjects Enterprise XI.

Repository Diagnostic Tool

The Repository Diagnostic Tool (RDT) scans, diagnoses, and repairs inconsistencies that may occur between the Central Management Server (CMS) system database and the File Repository Servers (FRS) filestore.

Life Cycle Manager

BusinessObjects Enterprise Life Cycle Manager (the LCM tool) is a web-based application that provides a centralized view to monitor the progress of the entire life cycle process. It

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: The SAP BusinessObjects Tools

enables you to move BI resources from one system to another system without affecting the dependencies of these resources. It also enables you to manage different versions of BI resources, map dependencies of BI resources, and roll back a promoted resource to restore the destination system to its previous state. Universe Designer

A Windows-based tool that allows users to build semantic layer objects that simplify underlying database complexity, and set row- and columnlevel security. The objects (such as filters) set row-level security. This semantic layer is the foundation for empowering end users to customize query and analysis. It abstracts the complexity of data by using business language rather than data language to access, manipulate, and organize data.

Business View Manager

A Windows-based tool that allows users to build semantic layer objects that simplify underlying database complexity, and set rowand column-level security. The objects (such as filters) set row-level security. You can simplify data access for report designers by insulating them from the raw data structures. You can build connections to multiple data sources, join tables, alias field names, create calculated fields, and then utilize this simplified structure as a Business View in BusinessObjects Enterprise. Report designers can then use the Business View as the basis for their reports, rather than accessing the data directly and building their own queries.

Data Services

A Windows-based tool that provides an easy-to-use, graphical environment that simplifies and automates complex data quality and data integration processes

Data Manager

2009

© 2010 SAP AG. All rights reserved.

7

Unit 1: SAP BusinessObjects Strategy

SAPBO

Lesson Summary You should now be able to: • Describe Business Intelligence and BusinessObjects Enterprise. • Describe the BusinessObjects Enterprise client applications by role.

8

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Roadmap

Lesson: SAP BusinessObjects Roadmap Lesson Overview In this lesson you will learn about the actual an the planned BI/BusinessObjects portfolio and the roadmap for the existing and upcoming tools. The information in this document is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information on this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided 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. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

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

Explain how the new SAP BusinessObjects Intelligence Platform co-exists with SAP Netweaver BW.

Business Example You want to get an overview of the currently available and planned tools for your reporting scenarios.

Purpose The primary purpose of this lesson is to educate SAP customers on the new SAP BusinessObjects Intelligence Platform and how it will co-exist within SAP Netweaver BW. Furthermore, to reassure existing SAP Netweaver BW

2009

© 2010 SAP AG. All rights reserved.

9

Unit 1: SAP BusinessObjects Strategy

SAPBO

customers of the value of SAP Netweaver BW (especially BI Accelerator and Data Warehouse). It will also provide a roadmap for the future of BI frontend tools, and SAP Netweaver BW (especially BI Accelerator and Data Warehouse) for SAP customers going forward. The secondary purpose is to help SAP customers see the value in the new SAP BusinessObjects Intelligence Platform by describing the capabilities of the new business intelligence (BI) and information management (IM) solutions that are sold to SAP customers today.

Figure 2: How SAP BusinessObjects Tools Expand the Scope of BW

SAP BusinessObjects tools expand the scope of BW by providing a wide range of tools and applications. The SAP BusinessObjects tools support businesses by optimizing the connection between people and information. Crystal Reports is the flagship product for formatted reports. Xcelsius provides superior dashboard capabilities and sophisticated visual presentations. When Pioneer becomes available, it will run on SAP BusinessObjects Enterprise platform along side Netweaver BW. It will be the product of choice for OLAP analysis. Web Intelligence is the flagship produce for Ad Hoc query and analysis. Web Intelligence is a very agile and easy to use tool. BusinessObjects Explorer is the tool that provides quick access and intuitive search and exploration capabilities.

10

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Roadmap

Figure 3: BEx Suite Cases and How They Should be Handled

The BEx Query designer will continue to be supported. The BEx Query Designer remains the central tool for SAP Netweaver BW. Projects requiring Excel OLAP integration may use the BEx Analyzer, until the tool Pioneer becomes available. The BEx Report Designer will remain in the BEx portfolio and may be used for light weight formatted reports. This product will continue to be supported, but not enhanced. The superior product, Crystal Reports is recommended. The BEx Web Application Designer will continue to be a supported tool in the BEx portfolio. Eventually, this tool will be replaced with more superior tools, such as CE Visual Composer, Xcelsius or Pioneer Web.

2009

© 2010 SAP AG. All rights reserved.

11

Unit 1: SAP BusinessObjects Strategy

SAPBO

Figure 4: BEx Web Application Designer / Web Templates and How They Should be Handled

Hint: •

•

•

•

The roadmap portion of this presentation is primarily focused on the long term direction of the frontend tools found in SAP Netweaver BW (i.e. BEx Analyzer, Web Analyzer, Web Application Designer, Report Designer) The roadmap will not explicitly discuss the future direction of SAP BusinessObjects BI tools since these tools are an integral part of the new SAP BusinessObjects BI Solutions for SAP customers going forward In addition, it is important to note that the core foundation of SAP Netweaver BW as well as the SAP Netweaver BW Accelerator, MDM and Visual Composer will continue to receive innovation and development going forward. This lesson only covers the SAP BusinessObjects Intelligence Platform and not the Enterprise Performance Management (EPM) or Governance, Risk and Compliance (GRC) solutions.

SAP BusinessObjects Portfolio – Immediate Value for SAP Customers SAP acquired BusinessObjects to provide for all customers a full suite of business intelligence (BI) and information management (IM) solutions available on one BI platform with deep integration to SAP Business Suite and SAP NetWeaver.

12

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Roadmap

SAP customers have immediate access to a premium suite of reporting, analytical and dashboarding capabilities optimized for their SAP applications all running on the SAP BusinessObjects Intelligence Platform. SAP customers benefit from an open and agnostic BI platform – with access and information management across all corporate databases and applications. With this you gain access to a broader set of Enterprise Performance Management solutions that includes the leading planning, budgeting, consolidation, profitability, operational analytics and compliance reporting.

SAP BusinessObjects Intelligence Platform

Figure 5: The Current Portfolio

2009

© 2010 SAP AG. All rights reserved.

13

Unit 1: SAP BusinessObjects Strategy

SAPBO

Figure 6: Product Directions

Detail View of the Tools

Figure 7: Dashboarding and data visualization

SAP BusinessObjects Xcelsius Enterprise offers a completely new, innovative user experience to customers, covering scenarios that SAP NetWeaver do not offer, going beyond the realm of the classical SAP BEx usage types.

14

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Roadmap

What is Xcelsius? •

•

Xcelsius is a tool for rapid development of Visualizations and highly interactive Dashboards through a flexible and easy to use point and click interface. Xcelsius supports deployment to a variety of destinations including Web, Desktop and MS Office documents.

Xcelsius enables creating Dashboards and Visualizations by… • • • •

Free-form layering a variety of visualizations on a canvas Customizing visualizations Setting fine grained control over eventing between visualizations and defining data bindings Compiling solution into flash format and deploying to various environments

Xcelsius is the SAP Strategy for Dashboards and Data Visualization What is the roadmap for Dashboards and Data Visualization? • •

• •

SAP Netweaver BW used to offer in the past the SAP BEx Web Application Designer for dashboard creation. The Web Application Designer will not be further enhanced and is going into maintenance, following the standard maintenance strategy from SAP. However, Pioneer will offer an OLAP SDK to enable web application design capabilities Xcelsius is the SAP Strategy for Dashboards and Data Visualization, bringing users a completely new, innovative experience Xcelsuis is available today and customers should start today to consider working with Xcelsuis

The integration and connectivity of Xcelsius with SAP NetWeaver BW will be enhanced •

New connectivity via a new BI Consumer Services (BICS) Web Services – – – –

•

Full integration with SAP NetWeaver’s Life Cycle Management – –

2009

Access data from SAP NetWeaver BW: SAP BEx queries and query views Access all query information: characteristics, key figures, variables, value help,… Access technical information of the query: Infoprovider, author,… Solution is Independent from BusinessObjects Enterprise Server

Integration of the Xcelsius dashboard in the transport framework Multilingual support, transport, accessibility

© 2010 SAP AG. All rights reserved.

15

Unit 1: SAP BusinessObjects Strategy

SAPBO

The BICS connectivity for Xcelsius integration into NetWeaver Life Cycle Management is available if the following software requirements are met: • •

Server side: Support Package 05 for SAP NetWeaver BW Release 7.01 ( 7.0 Enhancement Package 01) Client side (dashboard authors): – – –

Xcelsius 2008 SP2 BI 7.X AddOn SP901 or higher SAP GUI 7.10 or higher

Figure 8: Enterprise reporting

With Crystal Reports, SAP can offer the de-facto industry standard for enterprise reporting. What is Crystal Reports? •

•

Crystal Reports is a powerful, dynamic, actionable reporting solution that helps you design, explore, visualize, and deliver reports to thousands of end users to any destination including the web or embedded in enterprise applications. It enables end users to consume presentation quality reports with stunning visualizations, conduct on-report business modeling, and execute decisions instantly from the report itself—reducing dependency on IT and developers.

Crystal Reports is the flagship product for Enterprise Reporting going forward.

16

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Roadmap

Already today, Crystal Reports is tightly integrated with both SAP NetWeaver BW and SAP ERP. The connectivity of Crystal Reports is optimized to access InfoCubes, BW Queries, Data Store objects and Infosets. In addition, Crystal Reports offers direct connectivity to SAP ERP and SAP Business Suite for operational reporting. Crystal Reports will be integrated in the SAP NetWeaver platform in terms of: • • •

SAP NetWeaver Portal iViews SAP NetWeaver life cycle management Access to SAP BEx / Pioneer Queries and Views

Figure 9: Advanced OLAP analysis

Crystal Reports and Xcelsius will also be delivered with Business Suite 7 and the embedded analytics project. The target ist to provide one view and one common interface for reports created in Business Suite applications by embedding Crystal Reports and Xcelsius.

2009

© 2010 SAP AG. All rights reserved.

17

Unit 1: SAP BusinessObjects Strategy

SAPBO

Figure 10: SAP BusinessObjects Business Content delivered in SAP Business Suite

Pioneer is SAP’s Next Generation Advanced Analysis Client Pioneer stands for the new SAP BusinessObjects product family for advanced analysis on multi-dimensional (OLAP) data sources. As premium offering it will replace Voyager and will also become a more advanced & innovative alternative for the base OLAP clients BEx Analyzer & BEx Web Analyzer. Pioneer is designed for key users, business analysts & information consumers to optimally leverage the data and analytic capabilities from BW, MS Analytical Services and others. Usability and openness are key design principles for making Pioneer suitable to this target group. Pioneer comes in two flavors: Web & Microsoft Office. The two parts can interchange analyses created with one or the other. Pioneer Web is initially expected to support most of the BW OLAP and MS Analysis Services functionality, with more detailed OLAP-provider specific functionality added over time. Pioneer Web will also be an alternative for Web Application Designer templates focusing on OLAP analysis. Pioneer will answer these current customer needs:

18

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Roadmap

Pioneer Office will focus more on the support of specific SAP BW OLAP capabilities and add innovations on top as they become proven capabilities. • • • • • • • •

Direct access to various OLAP servers Support for SAP specific OLAP functions High Usability Standards State-of-the art Web 2.0 Client Deep integration with MS Office High Interoperability with BusinessObjects tools Support of BW Accelerator Runs on BusinessObjects Enterprise and SAP NetWeaver

Further information for SAP Netweaver BW customers: • • • •

The BW data model will not be affected by Pioneer, Pioneer will operate above query level BW 3.5 / 7.0 queries and query views can be re-used Query Views based on BW InfoProviders and saved with Pioneer Office can be used by Business Explorer tools The migration of BEx Analyzer workbooks to Pioneer will be possible

Figure 11: Project Pioneer Overview

2009

© 2010 SAP AG. All rights reserved.

19

Unit 1: SAP BusinessObjects Strategy

SAPBO

Figure 12: Ad-hoc Reporting and Analysis

WEBI is for casual end users looking for an intuitive BI tool for ad-hoc reporting and analysis 1.

Openness/multiple sources •

2.

3.

A single interface for SAP NetWeaver BW and any other non-SAP data sources, including personal XL files • Combine multiple heterogeneous data sources in a single report • Merging multiple data sources done by creator of report without IT Ease-of-use: same environment for design and consumption of interactive reports • Easily build queries with rich semantic layer • Easily analyze data with adapted set of features • Easily format reports with MS Office-like toolbar Combination of Web + offline • •

4.

A single interface for all business users: HQ/office, mobile, remote Share reports with built-in interactivity among all users and enable mobile and remote users to drill down Report layout and printing

• • •

20

Add charts & tables with precise positioning or free-form layout Insert custom calculations directly on the reports Print multi-page reports with managed page breaks

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Roadmap

Customer should start today with SAP BusinessObjects Web Intelligence • • •

SAP BusinessObjects Web Intelligence is a leading solution, available today for SAP customer with ad-hoc reporting needs. In addition the planned capabilities and functionalities, WebI will provide an even better integration with SAP NetWeaver in the near future. Interoperability between WebI and other tools is key for the future.

Performance and openness is key for WebI’s business users - planned availability of enhancements listed below is in 2010 • • • • •

2009

WebI will provide a seamless access to SAP NetWeaver BW queries via BI Consumer Services (BICS). The already existing MDX connectivity will get major improvements. Users will get a better and faster access to SAP NetWeaver BW SAP NetWeaver BW hierarchies integrated into Web Intelligence query and interactive reporting models Interoperability with Pioneer to conduct ad-hoc reporting from OLAP analysis

© 2010 SAP AG. All rights reserved.

21

Unit 1: SAP BusinessObjects Strategy

SAPBO

Lesson Summary You should now be able to: • Explain how the new SAP BusinessObjects Intelligence Platform co-exists with SAP Netweaver BW.

22

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Unit Summary

Unit Summary You should now be able to: • Describe Business Intelligence and BusinessObjects Enterprise. • Describe the BusinessObjects Enterprise client applications by role. • Explain how the new SAP BusinessObjects Intelligence Platform co-exists with SAP Netweaver BW.

2009

© 2010 SAP AG. All rights reserved.

23

Unit Summary

24

SAPBO

© 2010 SAP AG. All rights reserved.

2009

Unit 2 BusinessObjects Architecture Unit Overview This unit begins with an exploration of the rich architecture of SAP BusinessObjects Enterprise. The unit also discusses important vocabulary terms used in both SAP BW and SAP BusinessObjects and how various elements map between the two. The unit finishes with an introduction to SAP BusinessObjects XI Integration for SAP Solutions, the components that integrate these two powerful business intelligence platforms to form a world class solution.

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

Explain the architecture and technical requirements for SAP BusinessObjects Enterprise front-end tools. Describe the BusinessObjects Enterprise service groups and servers. Describe the components and features in BusinessObjects XI Integration for SAP Solutions

Unit Contents Lesson: Architecture Overview ................................................ 26 Lesson: BusinessObjects Integration with SAP solutions .................. 36

2009

© 2010 SAP AG. All rights reserved.

25

Unit 2: BusinessObjects Architecture

SAPBO

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

Explain the architecture and technical requirements for SAP BusinessObjects Enterprise front-end tools. Describe the BusinessObjects Enterprise service groups and servers.

Business Example End users log in, create, edit, and interact with reports and documents using specialized BusinessObjects Enterprise tools and applications that include: • • •

Crystal Reports Web Intelligence Performance management applications

Administrators in the IT departments use data and system management tools that include: • • • • •

Central Management Console Central Configuration Manager Import Wizard Publishing Wizard Universe Designer

Developers access the platform using a set of web services and Java APIs to integrate BusinessObjects Enterprise into other enterprise systems, and to share dynamically updated documents with users on separate networks. When certain tasks are performed in BusinessObjects Enterprise, such as logging in, scheduling a report, or viewing a report, information flows through the system and the various servers communicate with each other. BusinessObjects Enterprise server architecture consists of web, management, processing, and storage services. Understanding this architecture will help you visualize how actions performed in client applications are processed by the services.

BusinessObjects Enterprise architecture A full deployment of BusinessObjects Enterprise is made up of client applications, BusinessObjects Enterprise services, and the organization’s relational and/or OLAP data sources.

26

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Architecture Overview

Figure 13: BusinessObjects XI 3.1 Architecture

Describing BusinessObjects Enterprise service groups and servers The BusinessObjects Enterprise system can be installed on a single machine, spread across different machines in an intranet, or separated over a wide area network (WAN). For learning purposes, BusinessObjects Enterprise services can be grouped as follows:

2009

Service group

Servers

Web services

Web Application Server, Business Process BI Services

Management services

Central Management Server, Event Server, Destination Job Server

Storage services

Input File Repository Server, Output File Repository Server, Crystal Reports Cache Server, Desktop Intelligence Cache Server

Processing services

Adaptive Processing Server, Adaptive Job Server, Program Job Server, Crystal Reports Job Server, Web Intelligence Job Server, Web Intelligence Processing Server, List of Values (LOV) Server, Desktop Intelligence Job Server, Desktop Intelligence Processing

© 2010 SAP AG. All rights reserved.

27

Unit 2: BusinessObjects Architecture

SAPBO

Server, Connection Server, Crystal Reports Processing Server, Report Application Server, Multi-dimensional Analysis Server (MDAS), Publication Job Server, Search Server. Note: The service groups indicated above are logical groupings meant to facilitate learning in this course by grouping servers together that share similar operating behavior. In reality, BusinessObjects Enterprise web services must interact with management and processing services, storage services must interact with management and processing services, and so forth.

Enterprise Infrastructure The Enterprise Infrastructure provides the basic messaging mechanism needed for BusinessObjects Enterprise components to communicate with one another. The Enterprise Infrastructure is a series of services that are designed to communicate via CORBA (Common Object Request Broker Architecture), which runs over TCP/IP. Some CORBA applications use a Name server. The Name server service is a facility of the underlying CORBA architecture that binds the BusinessObjects Enterprise servers together. The Name server provides a directory of the servers registered in the BusinessObjects Enterprise environment and helps establish connections between clients and these servers. The Name server service is a part of the Central Management Server. The Enterprise Infrastructure establishes connections between clients and servers. 1. 2.

It is the centerpiece of BusinessObjects Enterprise technology which facilitates communication between servers. A client object can transparently make requests to server objects using the Enterprise Infrastructure. • •

A server object is a server that participates in serving requests to client objects. A client object is a client that makes requests to servers on the Enterprise Infrastructure. Note: In the BusinessObjects Enterprise environment, most services act as clients and servers to each other during transactions between the servers. When a BusinessObjects Enterprise server starts, it registers itself with the Name server in the CMS. The server provides information about itself, such as its IP address, TCP port, and description of the server, to the Name Server. Each individual server polls the CMS every 60 seconds to get an updated list of available servers in the system.

28

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Architecture Overview

BusinessObjects Enterprise web services The web services are server-side components that process requests from client applications and communicate these requests to the appropriate server. They include support for report viewing, and logic to understand and direct web requests to the appropriate BusinessObjects Enterprise server. BusinessObjects Enterprise web services include: •

Web Application Server

The Web Application Server uses the BusinessObjects Enterprise SDK to interface with the rest of the BusinessObjects Enterprise services. The Web Application Server acts as a gateway between the browser and the rest of the components in BusinessObjects Enterprise. Note: When configuring servers using the Central Management Console, the CMS holds the configuration settings and the CMS communicates with all BusinessObjects Enterprise servers. BusinessObjects web services provide a Java API accessed by rich clients in the user interaction tier, such as Live Office and Crystal Reports. Web Services consists of software components that can be called remotely using the Simple Object Access Protocol (SOAP). SOAP is a protocol for exchanging information that is not dependent on a specific platform, object model, or programming language. BusinessObjects Enterprise Web Services includes functionality in the following areas: • •

• •

Session: Authentication and user privilege management. BI platform: Exposes advanced platform features such as scheduling, search, user and group administration, server administration, platform events, and calendars. Report Engine: Displays Web Intelligence and Crystal Reports in HTML, PDF, Excel, and XML format. Query: Builds ad hoc queries based on the BusinessObjects universe semantic layer.

BusinessObjects Enterprise management services The management services manage the BusinessObjects Enterprise system. These services maintain all security information, send requests to the appropriate services, manage auditing information, and maintain a record of each and every instance and its location. The management services are: •

2009

Central Management Server (CMS)

© 2010 SAP AG. All rights reserved.

29

Unit 2: BusinessObjects Architecture

SAPBO

The CMS is responsible for authenticating users and groups, and keeping track of the availability of the other BusinessObjects Enterprise services. It also maintains the BusinessObjects Enterprise system database, which includes information about users, groups, security levels, BusinessObjects Enterprise content, and services. The CMS also maintains a separate audit database of information about user actions and manages the BusinessObjects system database. Note: All servers communicate with the CMS when they start up. Note: The Audit Database is optional in a regular system deployment. It allows for extra auditing and tracking of some system information. •

Server Intelligence Agent

Server Intelligence Agent is a component of the Central Management Console (CMC) that simplifies administrative procedures, such as the management of CMC server processes. This includes the addition and removal of server processes, server process configuration, and the automatic restart or shutdown of servers that encounter unexpected conditions. •

Event Server

The Event Server manages file-based events. It monitors the directory you specified when setting up a file-based event. When the appropriate file appears in the monitored directory, the Event Server triggers your file-based event. •

Destination Job Server

The Destination Job Server makes it possible for a user to send an existing instance or object to a specified destination (Inbox, Email, FTP, disk location) independent of any schedules related to those instances or objects. It can also send a shortcut to a user’s inbox. For example, the server updates the shortcut in the CMS database to point to the object location. If the destination is to send a copy to a user inbox, then the server copies the object to the Input File Repository Server.

BusinessObjects Enterprise storage services The storage services are responsible for storing objects and object instances. The storage services are: •

Input File Repository Server

The Input File Repository Server manages all of the report and program objects that have been published to the system. It can store the following files: .rpt, .exe, .bat, .js, .xls, .doc, .ppt, .rtf, .txt, .pdf, .wid, .rep, .unv, and Voyager workspaces. Note: .rpt files can be stored to Input with Data. •

30

Output File Repository Server

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Architecture Overview

The Output File Repository Server manages all of the report instances generated by the Crystal Reports Job Server and the program instances generated by the Program Job Server. It also manages instances generated by the Web Intelligence Processing Server and the LOV Job Server. It can store the following files: .rpt, .csv, .xls, .doc, .rtf, .txt, .pdf, .wid, .rep. Note: .rpt and .wid files are stored as reports/documents with saved data.

Crystal Reports Cache Server The Cache Server maintains a folder of cached report EPF files and determines if a request can be fulfilled with a cached report page. If the request cannot be fulfilled with a cached report page, it passes the request to the Crystal Reports Processing Server. The benefit of caching is that BusinessObjects Enterprise doesn’t have to generate .epf files each time a page is viewed. Therefore, report pages that have been cached can be shared among users.

Desktop Intelligence Cache Server The Desktop Intelligence Cache Server handles viewing requests for Desktop Intelligence documents and manages the viewable pages created by the Desktop Intelligence Processing Server.

BusinessObjects Enterprise processing services The processing services access the data and generate reports. This is the only tier that interacts directly with the databases that contain report data. Which services become involved in processing an object is determined by whether the object is being scheduled or viewed on demand. Viewer choice also plays a role in determining which servers are involved in object processing. The processing services are:

Program Job Server The Program Job Server processes scheduled actions on objects at the request of the CMS and generates text output. The Program Job Server processes the program objects by invoking the BAT and EXE file that are added to the BusinessObjects Enterprise system.

2009

© 2010 SAP AG. All rights reserved.

31

Unit 2: BusinessObjects Architecture

SAPBO

Crystal Reports Job Server The Crystal Reports Job Server processes report objects, as requested by the CMS, and generates report instances. Note: Both the Program Job Server and the Crystal Reports Job Server retrieve the file to be run from the Input File Repository Server, run the report or program, and then save the processed file to the Output File Repository Server as an instance.

Adaptive Job Server The Adaptive Job Server receives scheduling Web Intelligence documents requests from the CMS and then forwards them to the processing servers for processing.

Adaptive Processing Server The Adaptive Processing Server is a generic server process that hosts BusinessObjects Enterprise services such as Client Auditing Proxy Service, Publishing Post Processing Service, and Search Service.

Web Intelligence Processing Server The Web Intelligence Processing Server processes Web Intelligence Document requests.

List of Values (LOV) Job Server The List of Values Job Server receives scheduling requests from the Business View manager and processes scheduled List of Values objects to populate them with values retrieved from a database.

Desktop Intelligence Job Server The Desktop Intelligence Job Server processes scheduling requests received from the CMS for Desktop Intelligence documents and generates the instance of the Desktop Intelligence document.

Desktop Intelligence Processing Server The Desktop Intelligence Processing Server processes viewing requests for Desktop Intelligence documents and generates the Desktop Intelligence document.

32

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Architecture Overview

Connection Server The Connection Server is a service that can be administered and configured through the CMC (Central Management Console). The Connection Server is responsible for the database connectivity to access data. It is invoked when users want to edit and view Desktop Intelligence documents through InfoView in 3-tier mode. It is also used by some EPM services. Note: The Connection Server libraries are present on the Web Intelligence Processing Server, and Desktop Intelligence Processing Server. These libraries allow services to query the database directly without communicating with the Connection Server service. The viewing processing services are. •

Crystal Reports Processing Server

The Crystal Reports Processing Server is responsible for responding to files requests by processing reports and generating Encapsulated Page Format (.epf) files. The Crystal Reports Processing Server retrieves data for the report from the latest instance or directly from that database. After it generates the report, the Processing Server converts the requested data to one or more EPF files. These files are then sent to the Crystal Reports Cache Server. •

Web Intelligence Processing Server

The Web Intelligence Processing Server is responsible for generating documents. The Web Intelligence Processing Server obtains document creation requests from the Web Application Server and then communicates with the Input File Repository Server in order to obtain a copy of the Web Intelligence Document (WID) file and the universe definition. When viewing an existing instance of a WID, the Web Intelligence Processing Server communicates with the Output File Repository Server to obtain an existing historical instance of a WID. •

Report Application Server

Report Application Server resolves Dynamic Recipient Lists at design time and Runtime in Publishing, as well as with LiveOffice. The RAS also provides the ad hoc reporting capabilities that allow users to create and modify reports over the Web. As with the Crystal Reports Processing Server, the RAS supports Java viewer SDKs. The Report Application Server also includes an SDK for report creation and modification, providing you with tools for building custom report interaction interfaces. •

Multi-Dimensional Analysis Server

The Multi-Dimensional Analysis Server (MDAS) is a dedicated server intended to interact with OLAP data sources and to support Voyager.

2009

© 2010 SAP AG. All rights reserved.

33

Unit 2: BusinessObjects Architecture

SAPBO

The MDAS needs an appropriate OLAP database client configured for the appropriate OLAP data source. The list of providers is dynamically generated, based on which database drivers are installed on the MDAS that you happen to connect to. If more than one MDAS exists, the server contacted is selected randomly, so the same drivers should be installed on all servers. Connections to OLAP data sources are defined and managed from the CMC. Entries can include: • • • • •

Oracle SAP Essbase Microsoft Analysis Services 8.0 (MSAS 2000) Microsoft Analysis Services 9.0 (MSAS 2005)

•

Search Server

The Search Server processes search requests and executes the indexing. Your deployment can include multiple Search servers, and search requests are actively processed by all available servers. However, only one Search server performs the indexing process.

34

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Architecture Overview

Lesson Summary You should now be able to: • Explain the architecture and technical requirements for SAP BusinessObjects Enterprise front-end tools. • Describe the BusinessObjects Enterprise service groups and servers.

2009

© 2010 SAP AG. All rights reserved.

35

Unit 2: BusinessObjects Architecture

SAPBO

Lesson: BusinessObjects Integration with SAP solutions Lesson Overview This lesson provides a high-level overview of the major features in BusinessObjects XI Integration for SAP Solutions.

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

Describe the components and features in BusinessObjects XI Integration for SAP Solutions

Business Example The management executives in Company A felt that they did not have enough visibility into the various aspects of their business. They wanted to see trends, note exceptions and evaluate against goals. They were looking for a way to get highly summarized monthly data, displaying various aspects of their business performance. BusinessObjects XI Integration for SAP Solutions provides you with powerful report design tools and a framework for managing, scheduling, and distributing your reports over the Web. Also it enables you to extract additional value from your SAP Business Warehouse (BW) and ECC data and share it with users across the enterprise. In addition, SAP Authentication enables Single Sign On between your SAP system and BusinessObjects Enterprise.

What’s in BusinessObjects XI Integration for SAP Solutions? BusinessObjects XI Integration for SAP Solutions consists of several key components: Crystal Reports is the report design tool that allows you to report off your SAP data; BusinessObjects Enterprise provides the framework for managing, scheduling, and distributing reports over the Web; Web Intelligence enables you to create queries and documents quickly; and Voyager allows you to analyze and report off the multidimensional data that is stored in the InfoCubes of SAP BW. This solution allows tools such as Voyager, Web Intelligence, LiveOffice and Xcelsius to report on SAP data. BusinessObjects XI Integration for SAP Solutions also includes several add-on components to further integrate the BusinessObjects reporting technologies with existing SAP systems. The add-on components include •

36

Data Access

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Integration with SAP solutions

This component provides database drivers that are designed specifically for reporting on SAP data. Crystal Reports drivers are included for OpenSQL, InfoSet, BW Query, BW MDX and DSO. •

Crystal Reports SAP Toolbar

Integrated within Crystal Reports, the SAP Tools toolbar facilitates tasks associated with reporting based on BW queries. It allows you to log on to BW and work with its data sources, save reports to BW, and publish reports immediately to BusinessObjects Enterprise via BW. •

SAP Authentication

This component allows you to map your existing SAP roles and users to BusinessObjects Enterprise. It also enables BusinessObjects Enterprise to authenticate users against the SAP system, thereby providing Single Sign On to your SAP users. As a result, once SAP users are logged on to the SAP system, they are recognized by BusinessObjects Enterprise as authenticated users. •

BW Publisher

This component allows you to publish reports individually or in batches from BW to BusinessObjects Enterprise •

Web content

This component includes BusinessObjects Enterprise InfoView. InfoView allows users to organize and view their Crystal reports in multiple languages over the internet. •

Transport files

You use these transport files to connect to SAP through Crystal Reports and BusinessObjects Enterprise. •

BW Content Administration Workbench

This feature allows you to manage report publishing from within BW. You can identify roles in BW with specific BusinessObjects Enterprise systems, publish reports, and synchronize between BW and a BusinessObjects Enterprise system. •

Sample reports

The sample reports demonstrate a variety of ways in which you can extract value from SAP data using different database drivers. •

Sample iViews

Sample iViews illustrate how BusinessObjects Enterprise SAP Edition can be implemented with SAP Enterprise Portal version 6 and later. These iViews demonstrate sample functionality for alerts, and thumbnail views inside SAP Enterprise Portal. •

2009

Knowledge Management (KMC).

© 2010 SAP AG. All rights reserved.

37

Unit 2: BusinessObjects Architecture

SAPBO

The Knowledge Management interface enables third-parties to integrate any repository into the SAP Enterprise Portal. The KMC allows users to integrate BusinessObjects Enterprise into the SAP Enterprise Portal, When the BusinessObjects Enterprise repository is integrated into the KMC framework, the objects in the repository are accessible for different work flows like the collaboration features of the SAP Enterprise Portal.

Integrated architecture The following diagram illustrates how each of the BusinessObjects XI Integration for SAP Solutions components expands upon the multi-tier framework of BusinessObjects Enterprise.

Figure 14: Integrated Architecture

Reporting with BusinessObjects XI Integration for SAP Solutions Major features provided by BusinessObjects XI Integration for SAP Solutions include: • • • • •

38

Authenticating SAP users Reporting on BW queries, InfoSets, operational data stores, and MDX cubes Reporting on other SAP data sources Publishing from BW to BusinessObjects Enterprise Distributing information over the web

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Integration with SAP solutions

Authenticating SAP users Security plug-ins expand and customize the ways in which BusinessObjects Enterprise authenticates users. This SAP security plug-in offers several key benefits: •

•

•

•

It acts as an authentication provider that verifies user credentials against your SAP system on behalf of the BusinessObjects Enterprise Central Management Server (CMS). When users log onto BusinessObjects Enterprise directly, they can choose SAP Authentication and provide their usual SAP user name and password. BusinessObjects Enterprise can also validate Enterprise Portal logon tickets against SAP systems. It facilitates account creation by allowing you to map roles from SAP to BusinessObjects Enterprise user groups, and it facilitates account management by allowing you to assign rights to users and groups in a consistent manner within BusinessObjects Enterprise. It dynamically maintains SAP role listings. Therefore, once you map an SAP role to BusinessObjects Enterprise, all users who belong to that role can log onto BusinessObjects Enterprise. When you make subsequent changes to the SAP role membership, you need not update or refresh the listing in BusinessObjects Enterprise. The SAP Authentication component includes a web application for configuring the plug-in. You can access this application in the "Authentication" area of the Central Management Console (CMC).

Figure 15: SAP Authentication

2009

© 2010 SAP AG. All rights reserved.

39

Unit 2: BusinessObjects Architecture

SAPBO

Reporting on BW queries, InfoSets, Data Store Objects, and MDX cubes BusinessObjects XI Integration for SAP Solutions provides connectivity to your SAP data through four database drivers—the BW Query driver, the InfoSet driver, the DSO driver, and the MDX driver. •

•

• •

The BW Query driver is integrated directly within the Crystal Reports interface. The SAP Tools toolbar works with the BW Query driver to allow you to report on your BW queries within Crystal Reports. The toolbar also allows you to save reports to BW and publish them directly to BusinessObjects Enterprise. The InfoSet driver provides Crystal Reports with another means of accessing SAP data sources: this driver can access ECC InfoSets (previously known as Functional Areas) and ABAP Queries. You access this driver through the Data Explorer in Crystal Reports. The DataStore Objects (DSO) driver allows you to use existing DSO objects from your BW Data Warehouse as a data source in Crystal Reports. The SAP BW MDX Query driver introduces new flexibility when reporting off BW InfoCubes and queries. By writing reports with the MDX Query driver, you gain direct access to BW InfoCubes, display attributes and multiple structures. Note: One advantage of these drivers is that they allow business users to report on predefined views of your SAP data. Tables and fields are first logically grouped by an SAP content expert into queries, InfoSets, and so on. You then make these data sources accessible to users who are designing reports with Crystal Reports.

40

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Integration with SAP solutions

Reporting on other SAP data sources BusinessObjects XI Integration for SAP Solutions also includes the Open SQL driver, which allows you to report off additional SAP data sources within Crystal Reports, BusinessObjects Enterprise and Voyager. 1.

Reporting off tables, views, clusters, and functions The Open SQL driver is the most powerful of the drivers due to the flexibility it provides for accessing data in SAP. This flexibility, however, results in a higher level of complexity than with the InfoSet driver. When you create reports that use the Open SQL driver, you gain easy access to SAP's transparent tables, pool tables, cluster tables, and views. Users who are currently involved with the production of ABAP reports will find it easy to build reports quickly with this driver. Advanced functionality in the driver also allows reporting against ABAP functions and ABAP data clusters. ABAP developers can use these features to perform advanced tasks such as reporting against data clusters in HR.

2.

Reporting off multidimensional data in BW The BW Voyager has been specially designed to integrate the Online Analytical Processing (OLAP) viewing capabilities of Voyager and Crystal Reports with your SAP BW system. Users can connect to multidimensional BW InfoCubes and generate reports that incorporate complex data analysis.

Publishing from BW to BusinessObjects Enterprise The BW Publisher allows you to publish Crystal reports (.rpt files) individually or in batches from BW to BusinessObjects Enterprise. Reports are published from BW to BusinessObjects Enterprise in several ways: users who design Crystal Reports can simultaneously save reports to their roles in BW and publish them to BusinessObjects Enterprise, provided they have sufficient rights. Users with the appropriate rights within BW and BusinessObjects Enterprise can also publish reports individually or in batches using the Content Administration Workbench.

2009

© 2010 SAP AG. All rights reserved.

41

Unit 2: BusinessObjects Architecture

SAPBO

Distributing Information over the Web SAP functionality is integrated with your version of InfoView. These features are designed especially for SAP users. • •

•

42

Users whose roles you import can log on to InfoView with their usual SAP credentials Users can browse a hierarchy of My Groups folders that correspond to the structure of the imported roles whose content you publish from BW to BusinessObjects Enterprise. In these folders, users can locate, view, and refresh Crystal Reports that have been saved in their BW roles. Users can schedule translated reports in specific languages and view report titles and on-demand reports.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Integration with SAP solutions

Lesson Summary You should now be able to: • Describe the components and features in BusinessObjects XI Integration for SAP Solutions

2009

© 2010 SAP AG. All rights reserved.

43

Unit Summary

SAPBO

Unit Summary You should now be able to: • Explain the architecture and technical requirements for SAP BusinessObjects Enterprise front-end tools. • Describe the BusinessObjects Enterprise service groups and servers. • Describe the components and features in BusinessObjects XI Integration for SAP Solutions

44

© 2010 SAP AG. All rights reserved.

2009

Unit 3 Crystal Reports Unit Overview In this unit you will receive an overview of Crystal Reports and the connectivity used to integrate SAP BW data into its formatted reports. You will also complete an exercise to build your own Crystal Report using data from an SAP BW query.

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

Explain the connectivity with SAP NetWeaver BW and Crystal Reports. Create a Crystal Report based on a BW query using standard Crystal Reports components and methods. Create a Crystal Report based on a BW query with variables. Describe the differences between BW MDX and BW Query driver in regards to hierarchies. Create a Crystal Report based on a BW query with hierarchies. Create a Crystal Report based on a BW query with a hierarchy variable. Create a Crystal Report based on a BW query with multiple structures.

Unit Contents Lesson: Crystal Reports Connectivity with SAP Netweaver BW .......... 46 Lesson: Create a Report with Crystal Reports............................... 57 Exercise 1: Create a Report using Crystal Reports..................... 63 Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures. .......................................... 74 Exercise 2: Create Crystal Reports Based on BW Queries with Variables. .................................................................... 79 Exercise 3: Create Crystal Reports Based on BW Queries with hierarchies. .................................................................. 87 Exercise 4: Create Crystal Reports Based on BW Queries with Multiple Structures. .................................................................... 97

2009

© 2010 SAP AG. All rights reserved.

45

Unit 3: Crystal Reports

SAPBO

Lesson: Crystal Reports Connectivity with SAP Netweaver BW Lesson Overview This lesson provides you with an overview of the connectivity between SAP NetWeaver and Crystal Reports.

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

Explain the connectivity with SAP NetWeaver BW and Crystal Reports.

Business Example You want to access your organization’s data and transform it into actionable information to improve performance. By delivering the most-requested pieces of information reliably and securely – via the web or embedded in enterprise applications – reports can serve as the foundation of a successful business intelligence (BI) strategy. Crystal Reports software enables you to easily design interactive reports and connect them to virtually any data source. Your users can benefit from on-report sorting and filtering – giving them the power to execute decisions instantly.

Advantages of Crystal Reports Crystal Reports provides comprehensive functionality to design, explore, visualize, and deliver compelling reports. With Crystal Reports, you can: • • • • • • •

46

Leverage professional reporting Empower end users to explore reports with on-report sorting and parameters Minimize IT and developer effort with interactive reports Develop powerful data mash-ups Save valuable report design time Embed professional-looking reports in Java and .NET applications Tailor your solution by adding report management and viewing tools

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Crystal Reports Connectivity with SAP Netweaver BW

Figure 16: Crystal Reports Business Value

Connectivity Overview

Figure 17: Connectivity Overview

BusinessObjects XI Integration for SAP Solutions includes components that integrate Crystal Reports with your existing SAP systems. Available SAP data sources for Crystal Reports are:

2009

© 2010 SAP AG. All rights reserved.

47

Unit 3: Crystal Reports

SAPBO

SAP ERP/ECC • • • •

Classic InfoSets SAP Queries and InfoSet queries ABAP Functions Tables and Clusters (Open SQL)

SAP BW • • • •

Direct DSO access (no need for a BW query) BW queries and BW InfoCubes ABAP Functions Tables and Clusters (Open SQL)

Figure 18: Crystal Reports: Connectivity Overview

In order to be able to access all available SAP data sources the SAP Integration Kit needs to be installed on top of Crystal Reports. This includes: • • • •

48

Data access components for SAP ERP/ECC Data access components for SAP BW SAP authentication SAP BW toolbar

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Crystal Reports Connectivity with SAP Netweaver BW

Connection Methods There are two ways to get connected with crystal reports 1. 2.

Using Database Expert of Crystal Reports Using SAP Toolbar

Figure 19: Connection Methods

SAP BW metadata in Crystal Reports When you connect to an SAP BW query in Crystal Reports, the underlying metadata from the SAP BW query is leveraged and matched to Crystal Reports elements. The table below shows how SAP BW metadata is used in Crystal Reports. BW Query element

2009

Crystal Reports Designer Element

Characteristic

Separate fields for key and description per characteristic.

Hierarchy

Fields representing a parent-child relationship.

Key Figures

Measure element in a grouping called Key figure. Each Key figure can have up to three elements: numeric value, unit, and formatted value.

Calculated Key Figure

Measure element in the folder Key figure. (Information about the details of the calculated key figure is not available in Crystal Reports.)

© 2010 SAP AG. All rights reserved.

49

Unit 3: Crystal Reports

SAPBO

Restricted Key Figure

Measure element in the folder Key figure (Information about the details of the restricted key figure is not available in Crystal Reports.)

Filter (Characteristic Restriction)

Characteristic Restrictions willl be applied to the underlying query but are not visible in the Crystal Reports designer.

Filter (Default Value)

Note that Default Value restrictions are ignored in Crystal Reports.

Navigational attribute

Separate fields for key and description per navigational attribute.

Display attribute

Each display attribute becomes one field in the field explorer. The display attributes are grouped together with the actual characteristic.

SAP variables

Parameters.

Dimension and characteristics The image shows an SAP BW query in the BEx Query Designer.

Figure 20: Dimensions and Characteristics

The rows of this query include several characteristics and the columns display several key figures. On the left side, the actual InfoCube structure is shown with the InfoCube dimensions (not to be confused with characteristic InfoObjects). Building a Crystal Report on top of such an SAP BW query will result in the following elements:

50

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Crystal Reports Connectivity with SAP Netweaver BW

Figure 21: Database Fields

• • •

Each characteristic in the query will result in an element in the Field Explorer with a key and a description item. In addition, each characteristic will also generate a Node ID and a Parent Node ID that can be used for hierarchical reporting. Each characteristic will also generate a Member Unique Name field which represents the technical key value.

Hierarchies Hierarchies can be activated for characteristics in the BEx Query Designer which enables you the capability to navigate along a hierarchical structure. The image shows the Field Explorer in Crystal Reports based on an SAP BW query with a hierarchy (001).

Figure 22: Hierarchies In Crystal Reports

2009

© 2010 SAP AG. All rights reserved.

51

Unit 3: Crystal Reports

SAPBO

A hierarchy results in a parent-child relationship. Note: In terms of hierarchical reporting, the BW connectivity offers two different solutions: •

The BW Query driver connectivity offers each level of the hierarchy as a separate field and also offers parent child-relationship information. The listing of the separate levels is a legacy feature; use the new parent-child relationship and the hierarchical grouping functionality of Crystal Reports.

•

The BW MDX driver only offers a parent-child relationship.

Connection methods to SAP BW queries with Crystal Reports When creating new reports against SAP BW there are two options: 1. 2.

Using the SAP toolbar Using the Database Explorer

Using the SAP Toolbar Integrated within Crystal Reports, the SAP Tools toolbar facilitates tasks associated with reporting on BW queries. It allows you to log onto BW, work with its data sources, save reports to BW, and publish reports immediately to BusinessObjects Enterprise via BW. The SAP specific toolbar and the SAP specific menu items offer you the typical SAP open and save dialogs that are also used in the Business Explorer. Also they allow you to store the Crystal Report object directly into SAP BW roles. The following table shows all available menu options of the SAP toolbar:

52

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Crystal Reports Connectivity with SAP Netweaver BW

Figure 23: SAP Toolbar

As part of the settings available in the SAP toolbar the report designer can choose to use the SAP BW MDX driver for creating new reports against SAP BW.

Figure 24: BW MDX Driver

Note: It is highly recommended to use the BW MDX driver. The BW Query driver does not support multiple structures of a BW query and does not support display attributes. Note: Display attributes are InfoObjects which are logically assigned or subordinated to another characteristic InfoObject.

Crystal Reports and multi-structure queries The BEx Query Designer allows creating a query that contains structures. A structure is very similar to the specified grouping functionality of Crystal Reports. A structure can contain a definition of selections and formulas.

2009

© 2010 SAP AG. All rights reserved.

53

Unit 3: Crystal Reports

SAPBO

One query can contain up to two structures which then lead to a situation where the Query Designer builds a well designed grid for the result set.

Figure 25: Multi-structure Query

The query in the above screen shot contains two structures: • •

The first structure is a grouping of characteristics into specified groups. The second structure contains three Key Figures, one of them defined as a Formula.

In addition, the query contains two additional characteristics in the Free Characteristic area. When creating a report based on a query with two structures Crystal Reports tries to resolve the structure containing the Key Figures into separate fields and the structure representing the special grouping becomes a single field in Crystal Reports.

Figure 26: Database Fields In Multi-structure Query

In the given example the structure for the specific grouping of characteristics appears as one field in Crystal Reports and the three Key Figures appear as separate fields. Note: SAP BW queries with two structures are only supported with the BW MDX Driver and are not supported with the BW Query driver.

54

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Crystal Reports Connectivity with SAP Netweaver BW

Crystal Reports against SAP BW InfoCubes When you create a report against a BW InfoCube directly, the list of available fields is often larger than the list of fields for an SAP BW query. This is because a query does not have to contain all the dimensions and key figures that have been used to create an InfoCube. Note: Accessing a BW InfoCube directly is only available for the BW MDX driver and only when using the Crystal Reports Data Connections dialog. This functionality is not available using the SAP toolbar.

Figure 27: Crystal Reports against SAP BW InfoCubes

The additional fields when connecting against an InfoCube are inherited from the fact that the report now contains: • • • •

All characteristics from the underlying InfoCube All available hierarchies for all characteristics. All display attributes All key figures

When connecting against an InfoCube directly, the following metadata is not available: • • • •

2009

Navigational attributes Restricted key figures Calculated key figures SAP variables

© 2010 SAP AG. All rights reserved.

55

Unit 3: Crystal Reports

SAPBO

Lesson Summary You should now be able to: • Explain the connectivity with SAP NetWeaver BW and Crystal Reports.

56

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

Lesson: Create a Report with Crystal Reports Lesson Overview The lesson consists out of a theoretical part, a demonstration part and an exercise part. The theoretical part and the demonstration part are delivered by the instructor, the exercise part is done by the participants of the class.

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

Create a Crystal Report based on a BW query using standard Crystal Reports components and methods.

Business Example The demonstration part shows how to create a report that determines the top five regions in Germany compared by revenue. The data are displayed as values and also visualized by a chart. The exercise part shows how to create a report that displays ordered materials by customers. The data are displayed as values organized in groups, summarized and formatted.

Report Creation Methods When you launch Crystal Reports, the Start Page appears at the top of the screen. The Start Page includes links to recent reports you’ve opened, report creation methods, the Help system, a search functionality, sample reports, and an update service.

2009

© 2010 SAP AG. All rights reserved.

57

Unit 3: Crystal Reports

SAPBO

Figure 28: Launch Crystal Reports

You can create a new report with Crystal Reports using these methods: •

Use one of the Report Wizards provided. A user who is unfamiliar with Crystal Reports, or someone who is familiar but is rushed, will find it easier to design a report using one of the Wizards, sometimes referred to as Experts. You step through the report-building process of a specific type of report when using an Expert

•

Construct the report manually, piece by piece. You can custom design a report using this method by starting with a blank report and building the elements of the report from “scratch.”

•

Create a report from another report. Another quick method to build a report is to create it from an existing report. This existing report can be used as a template since it may already contain much of the information and formatting you need. After you open the report you want to use as a template, save it to a new file using the Save As command on the File menu The Start Page also contains dynamic content from BusinessObjects. After you select the type of report you want to build from the Start Page, you choose the data source you will use to create the report.

Understanding the Design Window When creating a report, you begin in the Design window, also referred to as the Design tab.

58

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

Figure 29: Crystal Design Window

The Design tab is where you do most of the initial work when creating a report. It designates and labels the various sections of the report. You can do the initial formatting; place objects in the sections where you want them to appear; specify sorting, grouping, and totaling needs; and so forth. While working in the Design tab you manipulate “representatives” or placeholders of objects, not the objects themselves. The Design tab offers faster previewing of information and layout because you are not working with the actual data itself. When a field is placed on the report, the program uses a frame to identify the field on the tab; it does not retrieve the data. Thus, you can add and delete fields and other objects, move them around, set up complex formulas and more, without tying up the computer or network resources needed to gather the data. The report created in the Design tab is a kind of virtual report; it has the structure and instructions for creating the final report, but it is not the report itself. To turn the Design tab report into a final report or into a report that you can fine-tune, you add data. Data adding occurs whenever you preview the report, print it or output it in any other way. The actual data appears in the report. When you begin creating a report, Crystal Reports automatically creates five areas or sections in the Design window.

Figure 30: Crystal Reports Headers

•

2009

Report Header

© 2010 SAP AG. All rights reserved.

59

Unit 3: Crystal Reports

SAPBO

This section is used for the report title and other information you want to appear at the beginning of the report. It can also be used for charts and cross-tabs that include data for the entire report. Items placed in the Report Header print only on the first page of the report. Often the name of the report, the print date, company logo, or “title page” information is included in the Report Header. •

Page Header

This section is used for information that you want to appear at the top of each page. This can include such things as chapter names, the name of the document, and other similar information. This section can also be used to display field titles above the fields on a report. Objects in the Page Header print at the top of every page of the report. Column headings, print dates, and page numbers are common entries in the Page Header. •

Details

This section is used for the body of the report and is printed once per record. The bulk of the report data appears in this section. Place the data fields on which you want to report in this area. This information (database fields and text) prints for every record selected on the report. •

Report Footer

This section is used for information you want to appear only once at the end of the report (such as grand totals) and for charts and cross-tabs that include data for the entire report. Items placed here print only on the last page of the report. Grand totals, total number of pages, and other summary information are often placed here. •

Page Footer

This section usually contains the page number and any other information you want to appear on the bottom of each page. Objects placed here print at the bottom of every page. Page numbers are often placed in the Page Footer. Note: The names of the five areas can also be shortened to their abbreviated forms (RH, PH, D, RF, and PF). You set the Short Section Name option in the Design View area of the Layout tab in the Options dialog box from the File menu. You can also set this option by right-clicking on one of the section names and selecting Show Short Section Names from the shortcut menu. Each section is indicated by a section boundary. These lines indicate the separation of the areas and do not print to paper.

Figure 31: Section Boundary

60

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

You can move these bars to change the amount of space reserved for each section. You click and drag the section divider to the desired position; however, you can drag the bottom line only to affect the size of the section.

Interface and Workflow

Figure 32: Working with Crystal Reports - Interface and Workflow

Components and Methods

Figure 33: Working with Crystal Reports - Components and Methods

2009

© 2010 SAP AG. All rights reserved.

61

Unit 3: Crystal Reports

62

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

Exercise 1: Create a Report using Crystal Reports Exercise Objectives After completing this exercise, you will be able to: • Create a simple Crystal Report on a BW query and do basic formatting.

Business Example Task 1: Task 1: Create a Crystal Report for SAP BW data.

Figure 34: sample solution (preview)

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries.

2.

Create a new report from a BW Query. Connect to the SAP BW training system using the login information given to you by your instructor, then select the existing BW query T_SAPBO_Q01.

3.

Ensure that the field descriptions are shown in the Field Explorer instead of the technical field names. Continued on next page

2009

© 2010 SAP AG. All rights reserved.

63

Unit 3: Crystal Reports

SAPBO

4.

Place the fields Region (state, county) and Sales Volume EUR in the Details section of the design area with a small space between them

5.

Insert a Group on the Country of Sold-to Party field.

6.

Filter the records displayed in the report so that only records with an Sales Volume EUR value greater than zero are displayed.

Task 2: Task 2: Format the Crystal Report.

Figure 35: sample solution (preview)

1.

Insert a Group Summary for all levels for the field Sales Volume EUR.

2.

Remove decimal places from the Group Summary of Sales Volume EUR.

3.

Insert a single border above and double border line below the grand total summary figure.

4.

Move the Group Summary results from the Group Footer to the Group Header.

5.

Hide the Detail Section, remove the column heading Region (state, county) from the Page Header and insert a new text object with the text Country

Continued on next page

64

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

6.

Change the font style for the column headings to bold and underlined and change the font size to 12.

7.

Insert a title for the report Sales Volume per Country. Make the font color Navy and font size 16.

8.

Insert a print date below the title on the left side of the report

9.

Insert a page number in the center of the Page Footer.

10. Insert a pie chart in the Report Header. 11. Set the title font size to 14, add a border and a shadow to the pie chart. 12. Preview your report and check the results. Afterwards save the report to BusinessObjects Enterprise after logging on to the Enterprise Server (twdfxxxx) using the login information given to you by your instructor. Save your report in the folder SAP → 2.0 →CLNT800.with the name GR## Sales Volume per Country.

2009

© 2010 SAP AG. All rights reserved.

65

Unit 3: Crystal Reports

SAPBO

Solution 1: Create a Report using Crystal Reports Task 1: Task 1: Create a Crystal Report for SAP BW data.

Figure 36: sample solution (preview)

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. a)

Within the Windows Desktop, choose Start → Programs → Crystal Reports 2008 → Crystal Reports 2008.

b)

When the BusinessObjects Registration Wizard displays, press Register Later.

c)

Within Crystal Reports, choose SAP → Settings and mark the check box Use MDX Driver with support for Multiple structures. Note: You may notice that the check mark is not saved when you go back to review this setting. When you mark this setting, and press OK, the MDX indicator will be sent, but the check box is not updated.

Continued on next page

66

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

You must mark this check box, and press OK, even though the check box may not get updated with the check mark. This MDM setting will be effective during your session, even though you do not see it. You will have to recheck this box if you logout of Crystal Reports and come back in again. 2.

3.

Create a new report from a BW Query. Connect to the SAP BW training system using the login information given to you by your instructor, then select the existing BW query T_SAPBO_Q01. a)

Within Crystal Reports, choose SAP → Create New Report from a Query.

b)

Double-click on the assigned training system, enter your assigned login information, and then click OK. Field Name

Value

Client

800

User

SAPBO-## (## = group number)

Password

Assigned password (must be changed on first logon)

Language

Desired language code

c)

Click on the Find button. Check the Description box.

d)

Enter the query description SAPBO Query 01.

e)

Click OK. The technical name for this query is T_SAPBO_Q01.

Ensure that the field descriptions are shown in the Field Explorer instead of the technical field names. a)

Follow the menu path File → Options.

b)

Within the Options dialog, click the Database tab and choose the option and then click OK.

c)

Open the Field Explorer by selecting View → Field Explorer.

d)

Click the plus sign in front of Database fields.

e)

Click the plus sign in front of SAPBO Query 01 to see the field descriptions.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

67

Unit 3: Crystal Reports

4.

Place the fields Region (state, county) and Sales Volume EUR in the Details section of the design area with a small space between them a)

5.

6.

SAPBO

In the Field Explorer, drag Region (state, county) into the Details section. Expand the Key figures folder and drag Sales Volume EUR to the Details section of the report. Keep a slight distance between the fields.

Insert a Group on the Country of Sold-to Party field. a)

Open the Group Expert by selecting Report → Group Expert.

b)

Move the field Country of Sold-to Party to the right side of the dialog and click OK.

Filter the records displayed in the report so that only records with an Sales Volume EUR value greater than zero are displayed. a)

Select the menu path Report → Select Expert → Record.

b)

Within the Choose Field dialog select the Sales Volume EUR field and click OK.

c)

Select the Sales Volume EUR field/tab, choose “is greater than” as the operator and enter 0 as the value. Click OK.

Continued on next page

68

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

Task 2: Task 2: Format the Crystal Report.

Figure 37: sample solution (preview)

1.

2.

Insert a Group Summary for all levels for the field Sales Volume EUR. a)

Right-click the field Sales Volume EUR in the detail section and then choose Insert → Summary from the context menu.

b)

Choose Sales Volume EUR as the field, Sum as the summary function, and Grand Total in the summary location.

c)

Select the checkbox Add to all group levels and click OK.

Remove decimal places from the Group Summary of Sales Volume EUR. a)

Select the Sales Volume EUR summary field in the Group Footer #1 and Report Footer. Use the Ctrl key to select both fields.

b)

Within the formatting tool bar press the icon Decrease Decimals twice. (This is the last icon on the formatting tool bar.)

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

69

Unit 3: Crystal Reports

3.

4.

Insert a single border above and double border line below the grand total summary figure. a)

Right click the grand total of the field Sales Volume EUR in the Report Footer section and select the Format Field option. Click on the Border tab.

b)

Choose Top: Single, Bottom: Double.

c)

Click OK.

Move the Group Summary results from the Group Footer to the Group Header. a)

5.

6.

SAPBO

Click the Sales Volume EUR summary in the Group Footer and drag it to the Group Header.

Hide the Detail Section, remove the column heading Region (state, county) from the Page Header and insert a new text object with the text Country a)

Right-click on top of the Details heading in the Design View and select Section Expert →Hide (Drill-Down OK).

b)

Right-click Region (state, county) in the Page Header section and choose delete in the context menu.

c)

Make a right-click in the Page Header section and choose Insert Text Object from the context menu. Position the text object near the left border of the report and insert the text Country.

Change the font style for the column headings to bold and underlined and change the font size to 12. a)

Select both heading in the Page Header section. Use the Ctrl key to select and highlight both fields.

b)

Right click on top of one of the headings and select Format Objects from the sub menu.

c)

Click the Font tab and select bold from the Style drop down box and select 12 in the Size drop down box. Mark the check box underline.

d)

Click OK.

Continued on next page

70

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

7.

8.

9.

Insert a title for the report Sales Volume per Country. Make the font color Navy and font size 16. a)

Right click in the Report Header section and select Insert a text object from the context menu.

b)

With the left mouse button depressed, expand the text object to the size that is needed in the Report Header section.

c)

Double-click the text object and enter Sales Volume per Country.

d)

Highlight the text, then right-click and select Text Formatting from the sub menu.

e)

Select the Font tab and change the Style to Bold, the Size to 16, and the Color to Navy.

Insert a print date below the title on the left side of the report a)

Within the Field Explorer, click the plus sign before Special Fields.

b)

Drag the special field Print Date into the Report Header below the left side of the title.

Insert a page number in the center of the Page Footer. a)

Within the Field Explorer, click on the plus sign before Special Fields.

b)

Drag the special field Page Number into the center of the Report Footer.

10. Insert a pie chart in the Report Header. a)

Select the Insert option in the menu bar and click the Chart option.

b)

Drag the chart into the Report Header section.

c)

Right-click on the chart and select the Chart Expert from the sub menu.

d)

Click the Type tab and then select Pie from the Choose your chart type list and click OK.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

71

Unit 3: Crystal Reports

SAPBO

11. Set the title font size to 14, add a border and a shadow to the pie chart. a)

Right click on the chart and select the Chart Expert from the sub menu.

b)

Click the Text tab and then the Font button.

c)

Change the font size to 14.

d)

Click OK twice.

e)

Right click on the chart and select the Format Chart option from the sub menu.

f)

Click the Border tab and choose Top: Single, Bottom: Single, Left: Single, Right: Single.

g)

Click in the box next to Drop Shadow and select OK.

12. Preview your report and check the results. Afterwards save the report to BusinessObjects Enterprise after logging on to the Enterprise Server (twdfxxxx) using the login information given to you by your instructor. Save your report in the folder SAP → 2.0 →CLNT800.with the name GR## Sales Volume per Country.

72

a)

View the report by choosing View → Preview.

b)

Align the field size if required.

c)

Save your report. File→Save As. Press Enterprise. Select SAP → 2.0 →CLNT800. Enter the name GR## Sales Volume per Country.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Crystal Reports

Lesson Summary You should now be able to: • Create a Crystal Report based on a BW query using standard Crystal Reports components and methods.

2009

© 2010 SAP AG. All rights reserved.

73

Unit 3: Crystal Reports

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures. Lesson Overview In this lesson, you will learn about the connectivity of Crystal Reports with more complex SAP BW queries. In this lesson, you will learn how to create Crystal Reports using SAP BW queries containing variables, hierarchies and multiple structures.

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

Create a Crystal Report based on a BW query with variables. Describe the differences between BW MDX and BW Query driver in regards to hierarchies. Create a Crystal Report based on a BW query with hierarchies. Create a Crystal Report based on a BW query with a hierarchy variable. Create a Crystal Report based on a BW query with multiple structures.

Business Example You want to be able to leverage hierarchies from a SAP BW query in Crystal Report

Crystal Reports Based on BW Queries with Variables. SAP BW queries can contain SAP variables which turn into parameters for the report. SAP supports a large set of options for these variables, starting with the feature to have optional or mandatory prompting. Optional and mandatory SAP variables. In the scenario where the SAP variable is optional, Crystal Reports creates a prompt which is optional and the user has the capability to set the value to Null. When setting the value to Null, Crystal Reports removes the SAP variable from the underlying MDX statement that is sent to SAP BW. As a result SAP BW checks first for a personalized value for the particular user, second for an existing default value and third for any value that was entered.

74

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

The order of priority for the SAP Variable is: 1. Personalized Variable value. 2. Default Variable value. 3. Manually entered value. The SAP variable becomes a parameter in Crystal Reports and during the process of creating the report a list of possible values is loaded into the prompt definition. Based on the situation that the SAP variable is optional, the resulting parameter in Crystal Reports allows the user to set the parameter to Null.

Figure 38: Crystal Report Based on BW Query with Variable

In the case the SAP variable has a default value defined, the resultset will be based on the default value even though the user set the prompt to Null.

Crystal Reports Based on BW Queries with Hierarchies The activated hierarchy from the underlying SAP BW query will result in a parent-child relationship being represented in Crystal Reports.

2009

© 2010 SAP AG. All rights reserved.

75

Unit 3: Crystal Reports

SAPBO

Figure 39: Crystal Report Based on BW Query with Hierarchy.

BW MDX Driver vs. BW Query Driver In terms of hierarchical reporting the BW connectivity offers two different solutions. The BW Query driver connectivity offers each level of the hierarchy as a separate field and also offers parent child-relationship information.

Figure 40: Field Explorer in Crystal Reports: BW Query driver

76

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

The listing of the separate levels is a legacy feature and the recommendation is to use the new parent-child relationship and the hierarchical grouping functionality of Crystal Reports. Note: The BW MDX driver only offers a parent child relationship. Hierarchy variables allow the user to select a hierarchy each time the report is being viewed. Using the parent-child relationship in Crystal Reports the actual design of the report itself does not need to be changed in such a situation because Crystal Reports dynamically resolves the parent-child relationship.

Crystal Reports Based on BW Queries with Multiple Structures The BEx Query Designer supports queries with two structures. A structure is very similar to the specified grouping functionality of Crystal Reports. A structure can contain a definition of selections and formulas. One query can contain up to two structures, which builds a well designed grid for the result set.

Figure 41: Crystal Report Based on BW Query with Multiple Structures

When creating a report based on a query with two structures Crystal Reports tries to resolve the structure containing the key figures into separate fields and the structure representing the special grouping becomes a single field in Crystal Reports. The structure with keyfigures will get resolved into separate fields and the structure without keyfigures will be represented as a single field in the Field Explorer.

2009

© 2010 SAP AG. All rights reserved.

77

Unit 3: Crystal Reports

78

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Exercise 2: Create Crystal Reports Based on BW Queries with Variables. Exercise Objectives After completing this exercise, you will be able to: • Create a Crystal Report based on a BW query with Variables.

Business Example You have created BW queries with variables which enable you to customize queries flexibly (parameterize the query). You can set up variables as place holders (here: to restrict the result of a query to a particular customer). You want to use one BW query definition as the foundation that allows you to analyze the sales volumes for different customers in Crystal Reports.

Task 1: Create a Crystal report based on a BW query that has an optional variable.

Figure 42: sample solution (preview)

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. Open the BW query SAPBO optional variable (T_SAPBO_Q03).

2.

Expand parameters in the Field Explorer and check if there is a parameter field. Add the following fields to the Detail Section of your report: Sold-to party (Key) Sold-to Party (Medium Name) Material (Key) Material (Medium Name) Sales Volume EUR

3.

Preview the report and select the customer Becker Berlin. Refresh the report data and preview the report without selecting a customer.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

79

Unit 3: Crystal Reports

4.

SAPBO

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name:GR## Sales by Customer with variable 01

Task 2: Create a Crystal report based on a BW query that has a mandatory variable.

Figure 43: sample solution (preview)

80

1.

Open the BW query SAPBO mandatory variable (T_SAPBO_Q04).

2.

Expand parameters in the Field Explorer and check if there is a parameter field. Add the following fields to the Detail Section of your report: Sold-to party (Key) Sold-to Party (Medium Name) Material (Key) Material (Medium Name) Sales Volume EUR

3.

Preview the report and select the customer Lampen-Markt GmbH. Note that a value must be selected because the variable in the BW query is mandatory..

4.

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Sales by Customer with variable 02

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Solution 2: Create Crystal Reports Based on BW Queries with Variables. Task 1: Create a Crystal report based on a BW query that has an optional variable.

Figure 44: sample solution (preview)

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. Open the BW query SAPBO optional variable (T_SAPBO_Q03). a)

Choose Start → Programs → Crystal Reports 2008 → Crystal Reports 2008 Within Crystal Reports, choose SAP → Settings and mark the check box Use MDX Driver with support for Multiple structures. Press OK. Note: You may notice that the check mark is not saved when you go back to review this setting. When you mark this setting, and press OK, the MDX indicator will be sent, but the check box is not updated. Mark this check box, and press OK, even though the check box may not get updated with the check mark. This MDX setting will be effective during your session, even though you do not see it. You will have to recheck this box if you logout of Crystal Reports and come back in again.

b)

To create a new report from a BW Query, select SAP→Create New Report From Query. Connect to the SAP BW training system using the login information given to you by your instructor. Enter the System name then enter: Client

800

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

81

Unit 3: Crystal Reports

c)

SAPBO

User

SAPBO-##

Password

Enter your password

Language

EN

Click on the Find icon (Binoculars). Ensure that the Search In option has Description checked. In the Search String field, enter SAPBO optional variable. Press FIND.

d)

Select the query. Note the technical name is T_SAPBO_Q03. Press OK.

e)

To display field descriptions rather than technical names in the Field Explorer, select File → Options. Within the Options dialog, click the Database tab and check the option Show Description. Press OK.

2.

Expand parameters in the Field Explorer and check if there is a parameter field. Add the following fields to the Detail Section of your report: Sold-to party (Key) Sold-to Party (Medium Name) Material (Key) Material (Medium Name)

Continued on next page

82

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Sales Volume EUR a)

Open the Field Explorer by selecting View → Field Explorer.

b)

Expand the Database fields folder. Expand SAPBO Query 03 folder to see the field descriptions. Note: BW variables become parameters in Crystal Reports. During the process of creating the report, a list of possible values is loaded into the prompt definition.

3.

c)

Find the BW variable by expanding the Parameters. This Parameter (BW variable) represents Sold-to party (i.e. Customer).

d)

Expand the nodes Sold-to Party, Material and Key Figures in the Field Explorer and add the following fields to the Detail Section of your report: Sold-to party (Key) Sold-to Party (Medium Name) Material (Key) Material (Medium Name) Sales Volume EUR

Preview the report and select the customer Becker Berlin. Refresh the report data and preview the report without selecting a customer. a)

View the report by choosing View → Preview.

b)

Select Becker Berlin and Press OK. Only records for Becker Berlin are displayed in the report.

c)

Select Report→ Refresh Report Data.

d)

Select Prompt for New Parameter Values. Press OK.

e)

Because the SAP variable is optional, the resulting parameter in Crystal Reports has a check box option at run time, that allows the user to set the Parameter to Null. Check Set to Null and press OK. Note: All customers are displayed in the report because there is no personalization or default value defined for the variable in the BW query.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

83

Unit 3: Crystal Reports

4.

SAPBO

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name:GR## Sales by Customer with variable 01 a)

Select File→ Save As.

b)

Press Enterprise. Enter the Enterprise Login information given to you by your instructor.

c)

Select SAP→ 2.0 →CLNT800. In the Description field, enter the name GR## Sales by Customer with variable 01.

Continued on next page

84

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Task 2: Create a Crystal report based on a BW query that has a mandatory variable.

Figure 45: sample solution (preview)

1.

Open the BW query SAPBO mandatory variable (T_SAPBO_Q04). a)

To create a new report from a BW Query, select SAP→Create New Report From Query. If necessary connect to the SAP BW training system using the login information given to you by your instructor. Enter the System name then enter:

b)

Client

800

User

SAPBO-##

Password

(Enter your password)

Language

EN

Click on the Find icon (Binoculars). Ensure that the Search In option has Description checked. In the Search String field, enter SAPBO mandatory variable. Press FIND.

c) 2.

Select the query. Note the technical name is T_SAPBO_Q04. Press OK.

Expand parameters in the Field Explorer and check if there is a parameter field. Add the following fields to the Detail Section of your report: Sold-to party (Key) Sold-to Party (Medium Name) Material (Key) Material (Medium Name) Continued on next page

2009

© 2010 SAP AG. All rights reserved.

85

Unit 3: Crystal Reports

SAPBO

Sales Volume EUR a)

Open the Field Explorer by selecting View → Field Explorer.

b)

Expand the Database fields folder. Expand SAPBO Query 03 folder to see the field descriptions. Note: BW variables become parameters in Crystal Reports. During the process of creating the report, a list of possible values is loaded into the prompt definition.

3.

4.

86

c)

Find the BW variable by expanding the Parameters. This Parameter (BW variable) represents Sold-to party (i.e. Customer).

d)

Expand the nodes Sold-to Party, Material and Key Figures in the Field Explorer and add the following fields to the Detail Section of your report: Sold-to party (Key) Sold-to Party (Medium Name) Material (Key) Material (Medium Name) Sales Volume EUR

Preview the report and select the customer Lampen-Markt GmbH. Note that a value must be selected because the variable in the BW query is mandatory.. a)

View the report by choosing View → Preview.

b)

Select Lampenmarkt GmbH, choose > to add your selection to the Selected Values on the right. Press OK. Only records for Lampen-Markt GmbH are displayed in the report.

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Sales by Customer with variable 02 a)

Select File→ Save As.

b)

Press Enterprise. Enter the Enterprise Login information given to you by your instructor.

c)

Select SAP→ 2.0 →CLNT800. In the Description field, enter the name GR## Sales by Customer with variable 02.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Exercise 3: Create Crystal Reports Based on BW Queries with hierarchies. Exercise Objectives After completing this exercise, you will be able to: • Create a Crystal Report based on a BW query with hierarchies. • Create a Crystal Report with formulas for conditional formatting.

Business Example Your implementation requires that you create new Crystal reports based on BW queries with hierarchies.

Task 1: Create a Crystal Report based on a BW query with a hierarchy.

Figure 46: sample solution (preview, partial)

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. Open the BW query SAPBO simple hierarchy (T_SAPBO_Q07). Continued on next page

2009

© 2010 SAP AG. All rights reserved.

87

Unit 3: Crystal Reports

SAPBO

2.

Expand the database fields folder in in Field Explorer and notice the Node ID and Parent ID fields for Material. The activated hierarchy for Materials from the underlying SAP BW query will result in a parent-child relationship being represented in Crystal Reports.

3.

Create a group on Material Node ID, change the Group Options so that Material Medium Name is used as group name. Also change the Hierarchical Grouping Options. Use Material Parent Node ID as Parent ID field and set an Indent of 0.3 inches for the alignment of the hierarchy levels in your report. Preview your report.

4.

Add the Key Figure Sales Volume EUR Value to the Details Section of the report. Insert a Summary for Sales Volume into the Header of the Material Node ID group. Hide the Details Section and the Group Footer. Preview your report.

5.

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Material Hierarchy 01

Continued on next page

88

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Task 2: Use conditional formatting with a formula so that the group headings follow an indentation and the key figures stay aligned.

Figure 47: sample solution (preview, partial)

1.

Open the report GR## Material Hierarchy 01 from the previous exercise. If the report is still open just go to the design tab.

2.

Set the Indent for the Material Node ID in the Hierarchical Grouping Options to 0 and enter the following formula for the position of the group name on the X-Axis: HierarchyLevel (GroupingLevel ({Material Node ID} ))*150 Preview your report

3.

2009

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Material Hierarchy 02

© 2010 SAP AG. All rights reserved.

89

Unit 3: Crystal Reports

SAPBO

Solution 3: Create Crystal Reports Based on BW Queries with hierarchies. Task 1: Create a Crystal Report based on a BW query with a hierarchy.

Figure 48: sample solution (preview, partial)

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. Open the BW query SAPBO simple hierarchy (T_SAPBO_Q07). a)

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. From Citrix, choose Start → Programs → Crystal Reports 2008 → Crystal Reports 2008 Within Crystal Reports, choose SAP → Settings and mark the check box Use MDX Driver with support for Multiple structures. Press OK. Note: You may notice that the check mark is not saved when you go back to review this setting. When you mark this setting, and press OK, the MDX indicator will be sent, but the check box is not updated. Mark this check box, and press OK, even Continued on next page

90

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

though the check box may not get updated with the check mark. This setting will be effective during your session, even though you do not see it. You will have to recheck this box if you logout of Crystal Reports and come back in again. b)

To create a new report from a BW Query, select SAP→Create New Report From Query. Connect to the SAP BW training system using the login information given to you by your instructor. Enter the System name then enter:

c)

Client

800

User

SAPBO-##

Password

Enter your password

Language

EN

Click on the Find icon (Binoculars). Ensure that the Search In option has Description checked. In the Search String field, enter SAPBO simple hierarchy. Press FIND.

d)

Select the query. Note the technical name is T_SAPBO_Q07. Press OK.

e)

To display field descriptions rather than technical names in the Field Explorer, select File → Options. Within the Options dialog, click the Database tab and check the option Show Description. Press OK.

2.

Expand the database fields folder in in Field Explorer and notice the Node ID and Parent ID fields for Material. The activated hierarchy for Materials from the underlying SAP BW query will result in a parent-child relationship being represented in Crystal Reports. a)

Open the Field Explorer by selecting View → Field Explorer. Expand the Database Fields folder. Expand the SAPBO Query 07 folder to see the fields Material Node ID and Material Parent ID.

3.

Create a group on Material Node ID, change the Group Options so that Material Medium Name is used as group name.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

91

Unit 3: Crystal Reports

SAPBO

Also change the Hierarchical Grouping Options. Use Material Parent Node ID as Parent ID field and set an Indent of 0.3 inches for the alignment of the hierarchy levels in your report. Preview your report. a)

From the menu select Insert → Group. On the Insert Group dialog select the Common tab and select the Material Node Id from the dropdown list. Keep the default setting In Ascending Order. On the Options tab check Customize Group Name field. Select Material Medium Name. Press OK.

4.

b)

From the menu select Report → Hierarchical Grouping Options Check Sort Data Hierarchically. Select Material Parent Node ID as Parent ID Field.. In the Group Indent field, enter 0.3 inches. Press OK.

c)

Select the menu View → Preview.

Add the Key Figure Sales Volume EUR Value to the Details Section of the report. Insert a Summary for Sales Volume into the Header of the Material Node ID group.

Continued on next page

92

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Hide the Details Section and the Group Footer. Preview your report. a)

On the Design tab, add a key figure, Sales Volume EUR value, to the Details Section of the report.

b)

To add the Sum of Sales Volum EUR on the grouplevel select the Key Figure Sales Volume EUR in the details section and select Insert→ Summary. from the context menu. In order to calculate the Summary, select Sum. Select the group for the summary location, by choosing Group 1 from the drop down list. Press OK. Note: The option “Summarize across hierarchy” allows creating a group summary by adding values from the lower level of a hierarchy up to a higher aggregated level. An example would be to summarize salary figures from the lowest level of an organization hierarchy up to the top level of the hierarchy. In the case of an SAP BW query as a data source, the option “Summarize across hierarchy” is not necessary because the underlying SAP BW query returns the aggregated values for all hierarchy nodes to Crystal Reports

5.

c)

Move the summary to the Group Header #1 per drag & drop.

d)

Hide the Details section in the report design. From the context menu for the Details Section, select Hide (Drill-down ok).

e)

Hide the Group Footer #1 in the report design. From the context menu for the Footer, select Hide (Drill-down ok).

f)

View the report by choosing View → Preview.

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Material Hierarchy 01 a)

Select File→ Save As.

b)

Press Enterprise. Enter the BusinessObjects Enterprise Login information given to you by your instructor.

c)

Select SAP→ 2.0 →CLNT800. In the Description field, enter the name GR## Material Hierarchy 01.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

93

Unit 3: Crystal Reports

SAPBO

Task 2: Use conditional formatting with a formula so that the group headings follow an indentation and the key figures stay aligned.

Figure 49: sample solution (preview, partial)

1.

Open the report GR## Material Hierarchy 01 from the previous exercise. If the report is still open just go to the design tab. a)

2.

If necessary open the report from the previous exercise, GR## Material Hierarchy 01, by selecting File → Open . Now select Enterprise and open the folder SAP → 2.0 →CLNT800.

Set the Indent for the Material Node ID in the Hierarchical Grouping Options to 0 and enter the following formula for the position of the group name on the X-Axis: HierarchyLevel (GroupingLevel ({Material Node ID} ))*150

Continued on next page

94

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Preview your report a)

Select Report → Hierarchical Grouping Options.

b)

Set the option Group Indent to 0 and click OK.

c)

Right-click the Group #1 Name field. Select from the menu Size and Position.

d)

Click the icon next to the X-Axis for conditional formatting. Enter the following formula below. Hint: For the Hierarchy Node ID, drag and drop Material Node ID from the Report fields into the formula. HierarchyLevel (GroupingLevel ({Material Node ID} ))*150 For this formula the assumption is that the field “Hierarchy Parent Node ID” represents the grouping field for the hierarchical grouping in the report.

3.

2009

e)

Save and close. Press OK.

f)

Preview your report by selecting View → Preview.

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Material Hierarchy 02 a)

Select File→ Save As.

b)

Press Enterprise. Enter the Enterprise Login information given to you by your instructor.

c)

Select SAP→ 2.0 →CLNT800. In the Description field, enter the name GR## Sales by Customer with variable 02.

© 2010 SAP AG. All rights reserved.

95

Unit 3: Crystal Reports

96

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Exercise 4: Create Crystal Reports Based on BW Queries with Multiple Structures. Exercise Objectives After completing this exercise, you will be able to: • Create a Crystal Report based on a BW query with Multiple Structures.

Business Example Your implementation requires that you create new Crystal reports based on BW queries with multiple structures.

Task: Create a Crystal Report based on a BW query with Multiple Structures

Figure 50: sample solution (preview)

2009

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. Open the BW query SAPBO multi-structure (T_SAPBO_Q06).

2.

Notice in the Field Explorer that structures with key figures will get resolved into separate fields and structures without key figures will be represented as a single field in the Field Explorer. In this example, the Country Structure displays as one single field

3.

Insert the following fields into the Details Section and preview your report: Country Structure Order Entry Quantity Invoice Quantity % Share

4.

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Multiple Structures

© 2010 SAP AG. All rights reserved.

97

Unit 3: Crystal Reports

SAPBO

Solution 4: Create Crystal Reports Based on BW Queries with Multiple Structures. Task: Create a Crystal Report based on a BW query with Multiple Structures

Figure 51: sample solution (preview)

1.

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. Open the BW query SAPBO multi-structure (T_SAPBO_Q06). a)

Launch Crystal Reports 2008 and ensure you are using the MDX driver for mapping to SAP Queries. Choose Start → Programs → Crystal Reports 2008 → Crystal Reports 2008 Within Crystal Reports, choose SAP → Settings and mark the check box Use MDX Driver with support for Multiple structures. Press OK. Note: You may notice that the check mark is not saved when you go back to review this setting. When you mark this setting, and press OK, the MDX indicator will be sent, but the check box is not updated. Mark this check box, and press OK, even though the check box may not get updated with the check mark. This MDX setting will be effective during your session, even though you do not see it. You will have to recheck this box if you logout of Crystal Reports and come back in again. Note: SAP BW queries with two structures are only supported with the BW MDX Driver and are not supported with the BW Query driver.

b)

To create a new report from a BW Query, select SAP→Create New Report From Query. Continued on next page

98

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Connect to the training system using the login information given to you by your instructor. Enter the System name then enter:

c)

Client

800

User

SAPBO-##

Password

Enter your password.

Language

EN

Click on the Find icon (Binoculars). Ensure that the Search In option has Description checked. In the Search String field, enter SAPBO multi-structure. Press FIND.

d)

Select the query. Note the technical name is T_SAPBO_Q06. Press OK.

e)

To display field descriptions rather than technical names in the Field Explorer, select File → Options. Within the Options dialog, click the Database tab and check the option Show Description. Press OK.

2.

Notice in the Field Explorer that structures with key figures will get resolved into separate fields and structures without key figures will be represented as a single field in the Field Explorer. In this example, the Country Structure displays as one single field a)

Open the Field Explorer by selecting View → Field Explorer. Expand the Database Fields node. Expand the SAPBO multi-structure node to see the fields.

3.

Insert the following fields into the Details Section and preview your report: Country Structure Order Entry Quantity Invoice Quantity

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

99

Unit 3: Crystal Reports

SAPBO

% Share

4.

100

a)

Drag the following fields from Field Explorer to the Details section, expand the node Database Fields → SAPBO →Key Figures to find the Key Figure fields: Country Structure Order Entry Quantity Invoice Quantity % Share

b)

Preview your report. View → Preview.

Save your report in the Business Objects Enterprise folder SAP → 2.0 →CLNT800 with the name: GR## Multiple Structures a)

Select File→ Save As.

b)

Press Enterprise. Enter the Enterprise Login information given to you by your instructor.

c)

Select SAP→ 2.0 →CLNT800. In the Description field, enter the name GR## Multiple Structures.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create Crystal Reports Based on SAP BW Queries with Variables, Hierarchies, and Multiple Structures.

Lesson Summary You should now be able to: • Create a Crystal Report based on a BW query with variables. • Describe the differences between BW MDX and BW Query driver in regards to hierarchies. • Create a Crystal Report based on a BW query with hierarchies. • Create a Crystal Report based on a BW query with a hierarchy variable. • Create a Crystal Report based on a BW query with multiple structures.

2009

© 2010 SAP AG. All rights reserved.

101

Unit Summary

SAPBO

Unit Summary You should now be able to: • Explain the connectivity with SAP NetWeaver BW and Crystal Reports. • Create a Crystal Report based on a BW query using standard Crystal Reports components and methods. • Create a Crystal Report based on a BW query with variables. • Describe the differences between BW MDX and BW Query driver in regards to hierarchies. • Create a Crystal Report based on a BW query with hierarchies. • Create a Crystal Report based on a BW query with a hierarchy variable. • Create a Crystal Report based on a BW query with multiple structures.

102

© 2010 SAP AG. All rights reserved.

2009

Unit 4 Web Intelligence Unit Overview Two important elements of the SAP BusinessObjects tool set are discussed in this unit – Universes and Web Intelligence. You will complete exercises to both create your own Universes and to use those Universes as the basis for Web Intelligence reports.

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

Define what a Universe is and explain its use. Define an OLAP Universe. List the Data Sources for OLAP Universe. Explain how to create the new Universe. Differentiate between different terms used in SAP and BusinessObjects. Describe the mapping of objects used in SAP and BusinessObjects. Create OLAP Universes with SAP hierarchies. Create OLAP Universes with SAP hierarchies with variables. Explain the connectivity between SAP Netweaver BW and Web Intelligence. Describe the Web Intelligence concept. View report formats in Web Intelligence. Create Web intelligence reports.

Unit Contents Lesson: BusinessObjects Universe ..........................................104 Lesson: SAP BusinessObjects Terminology ................................ 116 Exercise 5: Universe Creation from SAP NetWeaver BW InfoCube 123 Lesson: SAP Hierarchies in OLAP Universes ..............................131 Lesson: Web Intelligence Connectivity with SAP Netweaver BW ........136 Lesson: Create a Report with Web Intelligence ............................139 Exercise 6: Create a Report with Web Intelligence ....................145

2009

© 2010 SAP AG. All rights reserved.

103

Unit 4: Web Intelligence

SAPBO

Lesson: BusinessObjects Universe Lesson Overview This lesson gives you a general introduction to Universe Designer, the tool which you use to build universes. It describes universes, what they contain, how they are created, and the role that universes have in your business environment

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

Define what a Universe is and explain its use. Define an OLAP Universe. List the Data Sources for OLAP Universe. Explain how to create the new Universe.

Business Example After analyzing reporting requirements, your company wants more user friendly and highly formatted reports, hence company has decided to set up a OLAP universe on the top of SAP BW. Your task is to check what are various data sources available for the reporting in company and to find out the way of universe creation from those data sources. Once your Universe will be created on the top of SAP BW system then report generation could be done by BusinessObjects family products

Concept of a Universe

Figure 52: Concept of a Universe

104

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Universe

BusinessObjects Universe Designer is a software tool that allows you to create universes for Web Intelligence and Desktop Intelligence users.

What is a Universe? A universe is a file that contains the following: • •

• •

Connection parameters for one or more database middleware. SAP BW cube structures called objects that map to actual cube structures in the BW system such as dimension and measures. Objects are grouped into classes. Objects and classes are both visible to Web Intelligence users. Objects are built from a cube and from a query based on cube Web Intelligence users connect to a universe, and run queries against a Universe . They can do data analysis and create reports using the objects in a universe, without seeing, or having to know anything about, the underlying data structures in the cubes

What is an OLAP Universe?

Figure 53: Universe Overview

Figure 54: Concept of an OLAP Universe

2009

© 2010 SAP AG. All rights reserved.

105

Unit 4: Web Intelligence

SAPBO

An OLAP universe is a BusinessObjects universe that has been generated from a OLAP cube or query. The universe is created automatically from a selected connection to a OLAP data source. Once the universe has been created it can be exported to the Central Management System (CMS) as any other universe, and is then available to Web Intelligence users to run queries and create reports. The universe creation process is automatic once you have selected the connection. OLAP structures are mapped directly to classes, measures, dimensions, details and filters (when necessary). The universe structure appears in the Universe pane. There is no table schema in the Structure pane. Once you have created the OLAP universe, you can modify any of the universe components as for any other universe.

Maintaining an OLAP Universe • • •

• • •

To generate an OLAP universe, first select the SAP BW data source. Define a connection to the data source using the New Connection wizard, and select the connection for a new universe. Designer generates the universe automatically. OLAP structures are mapped directly to classes, measures, dimensions, details, and filters in the universe. The universe structure appears in the Universe pane. You can save and export the OLAP universe to the CMS. You can modify any of the OLAP universe components. The Update OLAP Universe wizard allows you manage the life cycle of the OLAP universe. The wizard automatically refreshes the universe structure with changes made in the OLAP data source. The wizard can differentiate generated objects from objects added or modified manually, allowing you to preserve the manual changes made in Designer.

Tasks of the Universe Designer The Universe Designer is normally responsible for the following tasks: • • • •

Conducting user needs analysis Designing and creating the universe Distributing the universe Maintaining the universe

How do you use Designer to createUniverses? Designer provides a connection wizard that allows you to connect to your database middleware. You can create multiple connections with Designer, but only one connection can be defined for each universe. This database connection is saved

106

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Universe

with the universe. Designer provides a graphical interface that allows you to select and view tables in a database. The database tables are represented as table symbols in a schema diagram. You can use this interface to manipulate tables, create joins that link the tables, create alias tables, contexts, and solve loops in your schema. Web Intelligence users do not see this schema. Designer provides an object explorer view. You use the explorer tree to create objects that map to the columns and SQL structures that are represented in the schema view. Web Intelligence users manipulate these objects to run queries against a database. Designer allows you to distribute universes by importing and exporting universes to the Central Management System (CMS) repository

Data Sources for OLAP Universe

Figure 55: Connecting to BW (1 of 2)

When creating an OLAP universe based on an SAP BW (Business Warehouse) data source, you can build the universe based directly on an InfoCube/MultiProvider, or based on a BW Query enabled on top of any InfoProvider. An InfoProvider can be: • • • •

2009

an InfoCube a MultiProvider a DataStore Object (DSO) an InfoSet

© 2010 SAP AG. All rights reserved.

107

Unit 4: Web Intelligence

SAPBO

SAP BW InfoCubes as Data Sources The following types of InfoCubes are supported as data sources for building OLAP universes. • • •

Standard and Direct Update InfoCubes: Data and metadata are physically stored in the same SAP BW system. Remote InfoCube: Data is physically stored on a remote system. MultiProviders

All the characteristics, hierarchies, key figures, including time and unit, in the InfoCube are visible in the universe.

SAP BW Queries as Data Sources SAP BW customers use BW Queries to access SAP Business Explorer front-ends. All InfoObjects in the BW query selected as rows, columns, and free characteristics are visible in the universe. This includes characteristics, hierarchies, key figures, structures, and variables. Both InfoSets and DataStore Objects (DSO) can be exposed to universes via BW Queries.

BW Queries based on a DSO A DSO can be exposed to a universe via a BW Query. DSO objects are often used to manage detailed transaction-level data before it is aggregated into InfoCubes. Including DSO objects in the BW data store design is a way to minimize InfoCube size and improve loading and querying performance An DSO is usually a large, detailed relational structure. Accessing an DSO via the OLAP BAPI interface does not deliver ideal query performance. Consider these alternatives to meet end-user expectations for fast report delivery: • •

Create direct access to an DSO via BAPI calls. Access the DSO tables using direct SQL in Web Intelligence.

BW Queries based on an InfoSet An InfoSet can be exposed to a universe via a BW Query. InfoSets are sometimes defined in SAP BW to report master data. You can report master data by basing the universes on InfoCubes, eliminating the requirement to go through InfoSets and BW Queries. The key difference between the two approaches is that master data reported off InfoCubes limits data to valid transactions.

108

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Universe

Figure 56: Connecting to BW (2 of 2)

SAP BW Queries as Recommended Data Sources BW Queries are recommended as data sources for generating BusinessObjects universes for the following reasons: •

Not all BW metadata features can be retrieved on an InfoCube level, as summarized in the following table. SAP BW metadata feature

SAP OLAP BAPI support level

Characteristics (including Time and Unit) InfoCube/BW Query

• •

2009

Hierarchies

InfoCube/BW Query

Basic Key Figures

InfoCube/BW Query

Navigational Attributes

BW Query only

Display Attributes

InfoCube/BW Query

Calculated Key Figures / Formulas

BW Query only

Restricted Key Figures

BW Query only

Custom Structures

BW Query only

Variables

BW Query only

BW Queries offer a flexible extension to the data modeling environment. InfoCubes require more effort to change. BW Queries offer significant functionality to create customized data sources that meet end-user requirements.

© 2010 SAP AG. All rights reserved.

109

Unit 4: Web Intelligence

SAPBO

Although BW Queries have advantages as data sources, you do not need a BW Query for every report, nor do you need a universe for every existing BW Query. To minimize maintenance costs, focus the implementation strategy on limiting the final number of BW Queries and universes required to meet all the ad-hoc query and reporting needs. Keep in mind the following points to reduce the number of universes needed: • •

When Web Intelligence is the front-end tool, you are not restricted by the output format in the BW Query. There is no direct impact on performance when working with OLAP universes created from large BW Queries. OLAP universe objects not inserted in the Web Intelligence query have no direct impact on the query performance.

SAP BW Multilingual Universes With Web Intelligence, it is possible to leverage the multilingual capabilities of SAP BW. In order to implement a multilingual environment, the BW system must include multilingual metadata and multilingual data. You must create a universe for each language supported by the solution. The language in which the universe connection is created determines the language in which the universe is generated. The user's SAP authentication determines the language of the data returned to the query. The user must log into InfoView using SAP authentication and specify the desired language for results returned from the SAP server. The result-set language is dependent on SAP’s Unicode support. If the SAP system does not contain the data in the desired language, the data is not available in Web Intelligence in this language. Web Intelligence reverts to displaying technical names instead of descriptions when the descriptions are not translated in SAP BW.

How to Create a New Universe To generate a universe, you must first define a connection to the SAP BW data source. Define one connection for each Infocube or BW Query that you want to use to create a universe. Use the New Connection wizard to define the connection. The wizard leads you through the following steps in creating a connection. • • • • •

110

Starting the wizard in Designer. Naming the connection and selecting the database middleware. Defining the login details for the connection. Selecting the cube or query to use to define the universe. Defining the connection lifetime.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Universe

Defining a connection is the first step in creating an OLAP universe. Once you have defined the connection, Designer generates the universe automatically

To Start the New Connection Wizard in Designer To start the New Connection wizard in Universe Designer, do one of the following: Start From

Action

New Universe icon

Click the New Universe icon, then click New... on the "Definition" page of the "Universe Parameters" box.

File menu

From an empty Designer session, select File → Parameters, then click New... on the "Definition" page of the "Universe Parameters" box.

Quick Design wizard

Starts automatically when you start Designer.

Tools menu

Select Tools → Connections. Click Add... in the "Wizard Connection" dialog box.

On the "Database Middleware Selection" page of the New Connection wizard, enter a name for the connection, select the type and the database middleware for the connection. Database Middleware Description Selection parameter Connection Type

. • • •

Connection Name

Enter a name for the connection.

Filter Stored Procedures Network Layers

The Filter Stored Procedures Network Layers parameter is not used for OLAP connections.

List of available data access drivers

2009

Select Secured for controlled access to the connection (recommended). Select Shared to allow uncontrolled access to the connection to all users. Select Personal to restrict access to the universe creator. You can use personal connections to access personal data on a local machine only.

The page lists the databases and middleware that correspond to your data access driver key.

© 2010 SAP AG. All rights reserved.

111

Unit 4: Web Intelligence

SAPBO

Expand the node for your target database to show the supported middleware for that database. Expand the middleware node to show the BusinessObjects data access driver for the OLAP middleware. Select the data access driver.

Login Parameters for SAP BW Connections On the Login Parameters page of the New Connection wizard, specify the login details for connecting to the SAP BW database Login Parameter Authentication mode

Description Select Use Single Sign On when refreshing reports at view time to allow the user to benefit from SAP SSO. Select Use specified username and password to require the user to enter login information when using the connection. Select Use BusinessObjects credential mapping to use the user's BusinessObjects Enterprise login credentials for the connection.

User name

Enter the SAP User logon.

Password

Enter the SAP User password.

Client

Enter the SAP client number.

Language

Enter the connection language, for example EN for English (required).

Login mode

Select Application server to connect directly to the SAP server without using load balancing. Select Message server to benefit from SAP load balancing capabilities.

Application Server

Select or enter the name or IP address of the SAP application server (required for application server login mode).

System Number

Enter the system number, for example 00 (number required for application server login mode).

System ID, Enter the System ID , Logon Group, and Message Server Logon Group parameters (required for message server login mode). , Message Server

112

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Universe

Select Source Cube or Query for OLAP connections The Cube browser shows the OLAP Cubes available to the target server. Expand the Cube nodes to display the Cubes and queries available. The browser has the following tools to help you search: Cube Description Browser Tool Favorites

A folder that holds links to cubes that you select for quick access. To add a Cube to Favorites, right click a Cube in the OLAP Cube browser and select Add to Favorites from the contextual menu.

Search

Searches the names of available Cubes or queries for a text string. Type a string in the text box and click Search. Each found instance is highlighted. Click Search to continue searching.

$INFOCUBE folder

For SAP BW data sources, the InfoCubes and MultProviders are grouped in a folder called $INFOCUBE.

Select the cube or query to use to create the universe.

Configuration Parameters for OLAP Connections On the Configuration Parameters page of the New Connection wizard, define the connection parameters to manage the connection lifetime. You can accept the default settings when you create the connection and modify them later. Configuration Description

Parameter

Connection Pool You define the lifetime with the Connection Pool Mode and Mode Pool timeout parameters Pool timeout

By default, the Connection Pool Mode is set to Keep the connection alive for, with a default Pool timeout of 10 minutes The connection lifetime can have a significant impact when working with SAP BW. However, connection lifetime can also impact updating existing universes with changes in the BW Query. This is because the OLAP BAPI interface builds a metadata cache on the client side every time a connection to BW is established. This cache is only emptied when the connection closes. To minimize the risk of metadata cache being desynchronized with SAP BW Query updates, you can change the Pool timeout from 10 minutes to 1 minute. When working in parallel editing SAP BW Queries and mapping

2009

© 2010 SAP AG. All rights reserved.

113

Unit 4: Web Intelligence

SAPBO

new universes to these queries, it is recommended that you close Designer (so that universe connections are also closed and the metadata cache is emptied) before building any new universes to take into account changes that were just made on the SAP BW Query side Array fetch size , The Array fetch size, Array bind size, and Login timeout Array bind size, parameters are not used for OLAP connections. Login timeout

114

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Universe

Lesson Summary You should now be able to: • Define what a Universe is and explain its use. • Define an OLAP Universe. • List the Data Sources for OLAP Universe. • Explain how to create the new Universe.

2009

© 2010 SAP AG. All rights reserved.

115

Unit 4: Web Intelligence

SAPBO

Lesson: SAP BusinessObjects Terminology Lesson Overview When you create a universe from either an InfoCube or a BW Query, Designer maps BW OLAP structures to equivalent classes and objects in the universe. This chapter will give you the detailed overview of the of the mapping of SAP Objects in a BusinessObjects Universe.

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

Differentiate between different terms used in SAP and BusinessObjects. Describe the mapping of objects used in SAP and BusinessObjects.

Business Example You have created universes based on a SAP BW Query. Query elements like variables and calculated key figures are important for the users who create reports using BusinessObjects tools.

How SAP BW Objects are mapped in a Universe

Figure 57: Basic Elements of Universes

All InfoObjects in the BW Query set as rows, columns, free characteristics, and filters are exposed to the universe. This includes characteristics, hierarchies, key figures, structures and variables.

116

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Terminology

Figure 58: Terms in SAP Netweaver BW and BusinessObjects

Hierarchies are mapped, allowing Web Intelligence users to drill down according to BW hierarchies. For InfoCubes, all the dimensions, key figures and hierarchies are mapped. The following table shows the universe objects created for each BW object: BW object:

Universe objects created:

Dimension Group

Class

Characteristic

Subclass with dimension and detail objects

Characteristic with hierarchy

If data source is a BW Query: Subclass containing dimension and detail objects for each hierarchy level in the currently defined hierarchy. If data source is an InfoCube: Subclasses containing dimension and detail objects for each hierarchy level for all hierarchies defined for the characteristic.

Class with single dimension object for the structure Structure based on Characteristics (BW Queries only) Navigation attribute

Subclass with dimension and detail objects (same as Characteristic)

Display Attribute

Detail object for the dimension

Key Figure structure Class Key Figure

Measure object in the class for the Key Figure structure with dimension objects for units/currency.

Calculated Key Measure and dimension objects (same as Key Figure) Figure (BW Queries only)

2009

© 2010 SAP AG. All rights reserved.

117

Unit 4: Web Intelligence

SAPBO

Measure and dimension objects (same as Key Figure) Restricted Key Figure (BW Queries only) Variables (BW Queries only)

In the class for the dimension to which the variable applies, two dimension objects supporting the list of values, one for caption, one for description.

Key date variable (BW Queries only)

Universe parameters defining key date variable in the universe

Characteristics in the Filters section of the BW Query are not mapped in the universe. To avoid this limitation, use characteristics from the Filter section also in the Free Characteristics section. However, the filtering applies to the universe. The filter is also applied when running a Web Intelligence query on the universe.

Figure 59: Mapping SAP Netweaver BW and BusinessObjects

How SAP BW characteristics are mapped and used in a universe When no hierarchy is defined on the characteristic in the BW Query or InfoCube, Designer creates a class containing the characteristic as two dimension objects: Level 00 and Level 01. The Level 00 dimension represents the aggregation of the characteristic when all members are selected (the member returned from BW is All members). The Level 01 dimension contains all members for the characteristic as a flat list of values. For each dimension object, Designer creates a detail object for the key, up to three detail objects for the description (short, medium, and long descriptions), and a detail object for each display attribute.

118

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Terminology

The SELECT clause is defined using the technical name of the characteristic. Navigation attributes defined in the BW Query are mapped in the parent object class in the same way as characteristics are mapped.

How SAP BW key figures are mapped and used in a universe All key figures in the InfoCube or defined in the BW Query are included in the universe under a single object class called Key Figures. Most key figures are defined in BW with either a currency or a unit characteristic. For each key figure, Designer creates: • • •

A measure object with numeric format corresponding to the key figure without the unit. A dimension object with character format that contains the unit or currency. For example, 'USD', '€', 'km'. A dimension object with character format that contains the key figure and the unit (formatted value) based on user preferences configured on the SAP server. For example, '500 USD', '345 €', '85 km'.

The Key Figures class includes the calculated key figures and restricted key figures defined in the BW Query. The original calculation and restrictions are applied to the query, but are not exposed in the universe.

How SAP BW hierarchies are mapped and used in a universe Hierarchies are mapped to allow Web Intelligence users to drill down with SAP BW hierarchies in the same way as custom-made universe hierarchies. The Use Query Drill option in the Web Intelligence Document Properties dialog box significantly improves drill down performance. When a hierarchy is defined on a characteristic in the BW Query, Designer creates one hierarchical structure in the universe, with a subclass for each level in the hierarchy. The structure depends on the current BW Query definition: • •

If a hierarchy is defined in the BW Query, Designer creates this hierarchy structure in the universe. If a hierarchy variable is defined in the BW Query that allows the user to choose a hierarchy at run time, Designer creates a generic hierarchy in the universe. The structure has the highest number of levels defined for any of the hierarchy structures available for the characteristic.

When building a universe on top of an InfoCube, all hierarchies defined on the characteristic are exposed in the resulting universe. Designer creates subclasses for each hierarchical structure, each containing subclasses for the levels in that hierarchy.

2009

© 2010 SAP AG. All rights reserved.

119

Unit 4: Web Intelligence

SAPBO

In the universe, Level 00 of a hierarchy represents the top node of the structure. When multiple tops exist for the hierarchical structure, the Level 00 dimension contains all top nodes as a list of values. When the hierarchy attribute is set to not filter unassigned nodes, it is necessary to include Level 00 with the top node for unassigned members. Unassigned members are grouped at the lowest level of the hierarchy.

How SAP BW variables are mapped and used in a universe SAP variables can be interpreted as user prompts defined in the BW Query. Variables can be mandatory or optional, and can have default values. Variables for characteristics are used to filter values for a characteristic. Variables are populated with values when a query is executed. They can store characteristic values, hierarchies, hierarchy nodes, texts, and formula elements. BW variables apply to BW Queries only. The following types of SAP BW variables are supported in universes: • • • • • • •

Characteristic variables Hierarchy variables Hierarchy node variables Currency variables Formula variables Text variables (as replacement path) Key date variables

The following table shows universe support for user entry SAP BW variables. User entry variables can be mandatory or optional, and can have default values.

120

Variable Type

Support Level

Characteristic - Single value prompt

Supported

Characteristic - Multiple single value prompt

Supported

Characteristic - Interval prompt

Supported

Characteristic - Selection option prompt

Supported as interval prompt

Characteristic - Pre-calculated value set

Not supported

Text

Not supported

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Terminology

Formula

Price, quota, and numeric values supported

Hierarchy

Supported except for version variable

Hierarchy node

Supported

The following table shows universe support for other processing types. N/A means that the respective combination is not available in SAP BW. Not supported means that the combination is available in SAP BW but not supported in the Universe. Variable type

Replacement path

Authorization

Customer Exit

SAP Exit

Characteristic

supported

supported

supported without user entry

supported without user entry

Text

supported*

N/A

not supported

not supported

Formula

supported

N/A

supported without user entry

supported without user entry

Hierarchy

N/A

N/A

supported without user entry

supported without user entry

Hierarchy Node

N/A

supported

supported without user entry

supported without user entry

* The replacement path of a text variable must refer to a constant value in the query, it cannot refer to a value that is defined by another variable.

2009

© 2010 SAP AG. All rights reserved.

121

Unit 4: Web Intelligence

122

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Terminology

Exercise 5: Universe Creation from SAP NetWeaver BW InfoCube Exercise Objectives After completing this exercise, you will be able to: • Create a connection between SAP NetWeaver BW and the BusinessObjects system. • Create a Universe from an SAP NetWeaver BW InfoCube. • To understand the object structure in the Universe.

Business Example Before you begin universe creation from SAP NetWeaver BW system, you need to create a connection between SAP NetWeaver BW and the BusinessObjects System . The basic principles by building a Universe between the SAP NetWeaver BW and BusinessObjects is to generate the interface between both systems and to map the characteristic and key figures of SAP NetWeaver BW into a universe so that they can be used by BusinessObjects for reporting.

Task 1: Task 1: Review the BW InfoCube used for the report. 1.

Logon to the assigned BW system using the following details: Note:

2.

Field Name

Value

Client

800

User

SAPBO-##

Password

Enter your password

Language

Desired language key

Using transaction code RSA1, review the InfoCube on which you are going to develop the Universe. The description of the InfoCube is SAPBO Cube and the technical name is T_SAPBO1. Use Search within RSA1 to find the InfoCube.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

123

Unit 4: Web Intelligence

SAPBO

Task 2: Task 2: Create a Universe based on InfoCube T_SAPBO1 1.

Launch the Universe Designer and logon with the following details: Field Name

Value

System

twdfXXXX

User name

SAPBO-##

Password

Enter your password

Authentication

SAP

2.

Launch the Quick Design Wizard.

3.

Create a new connection using the following initial parameters, then proceed to the next step of the Quick Design Wizard.

4.

5.

Field Name

Value

Connection Type

Secured

Connection Name

T_SAPBO1_Connection_##

Database Middleware Selection

SAP → SAP Business Warehouse, then select SAP Client

Define the BW login parameters using the parameters below. Field Name

Value

User

SAPBO-##

Password

Enter your password

Client

800

Language

EN

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp ( = assigned SAP BW system ID)

System number

40

System ID



Select the InfoCube T_SAPBO1 within the $INFOCUBE folder, then proceed to the last screen and select Finish. Continued on next page

124

© 2010 SAP AG. All rights reserved.

2009

SAPBO

2009

Lesson: SAP BusinessObjects Terminology

6.

Enter the Universe name T_SAPBO1_UNIVERSE_## then complete the wizard steps until you see the completion message. Then review the created Universe.

7.

Save the Universe to the BusinessObjects Universes folder with the name T_SAPBO1_UNIVERSE_## .

8.

Export the universe to the BusinessObjects repository folder webi universes.

© 2010 SAP AG. All rights reserved.

125

Unit 4: Web Intelligence

SAPBO

Solution 5: Universe Creation from SAP NetWeaver BW InfoCube Task 1: Task 1: Review the BW InfoCube used for the report. 1.

Logon to the assigned BW system using the following details: Note:

2.

Field Name

Value

Client

800

User

SAPBO-##

Password

Enter your password

Language

Desired language key

a)

Select Start → SAP Logon. Highlight the assigned SAP BW system and click Log On.

b)

Enter the logon details given above and press Enter.

c)

On the System Messages pop up box, click on the Enter icon (green check mark).

Using transaction code RSA1, review the InfoCube on which you are going to develop the Universe. The description of the InfoCube is SAPBO Cube and the technical name is T_SAPBO1. Use Search within RSA1 to find the InfoCube. a)

In the command field (empty field on the icon bar), enter the transaction code RSA1 and press Enter.

b)

Select InfoProvider in the Modeling section in the left part of the screen. Open Object Search in the tree by clicking the icon with the binoculars and search for T_SAPBO1.

c)

Right-click the Cube T_SAPBO1 and select Display in the context menu.

d)

Review the structure of the InfoCube, identifying the key figures and characteristics within the dimensions. Expand the Customer dimension and view the Sold_to characteristic. Expand the Material dimension and view the Material characteristic. Expand the Key figures folder and view the key figures.

e)

Logoff of BW by closing the window. Continued on next page

126

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Terminology

Task 2: Task 2: Create a Universe based on InfoCube T_SAPBO1 1.

Launch the Universe Designer and logon with the following details: Field Name

Value

System

twdfXXXX

User name

SAPBO-##

Password

Enter your password

Authentication

SAP

a)

Select Start → Programs → Business Objects XI 3.1 → Business Objects Enterprise Client Tools → Designer.

b)

Enter your BOE system, twdf####. Enter the logon information in the task description above and press Logon.

2.

Launch the Quick Design Wizard. a)

3.

4.

Click on Begin.

Create a new connection using the following initial parameters, then proceed to the next step of the Quick Design Wizard. Field Name

Value

Connection Type

Secured

Connection Name

T_SAPBO1_Connection_##

Database Middleware Selection

SAP → SAP Business Warehouse, then select SAP Client

a)

Select the New button to create a new connection.

b)

Click on Next.

c)

Enter the parameters above.

d)

Click on Next.

Define the BW login parameters using the parameters below.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

127

Unit 4: Web Intelligence

Field Name

Value

User

SAPBO-##

Password

Enter your password

Client

800

Language

EN

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp ( = assigned SAP BW system ID)

System number

40

System ID



a) 5.

6.

7.

SAPBO

Enter the connection details above (remember to replace SID with your assigned BW system ID) then click Next.

Select the InfoCube T_SAPBO1 within the $INFOCUBE folder, then proceed to the last screen and select Finish. a)

Expand the node OLAP Cubes and scroll to the bottom of the list, highlight the $INFOCUBE folder and enter T_SAPBO1 in the search field then press the Search button to find the InfoCube.

b)

With the InfoCube highlighted, click Next and on the next screen select Finish.

Enter the Universe name T_SAPBO1_UNIVERSE_## then complete the wizard steps until you see the completion message. Then review the created Universe. a)

In the field Enter the universe name enter T_SAPBO1_UNIVERSE_## and select Next.

b)

Click Finish.

c)

Review the Universe by expanding the class and sub-class nodes to see the dimensions and measures.

Save the Universe to the BusinessObjects Universes folder with the name T_SAPBO1_UNIVERSE_## . a)

Select File → Save As.

b)

Ensure the destination folder is set to BusinessObjects Universes, and ensure the universe name is set to T_SAPBO1_UNIVERSE_##.UNV, then press Save.

Continued on next page

128

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP BusinessObjects Terminology

8.

2009

Export the universe to the BusinessObjects repository folder webi universes. a)

Select File → Export.

b)

Press the Browse button.

c)

Highlight the folder webi universes then press OK.

d)

Press OK to export the universe. The universe is now available for reporting.

© 2010 SAP AG. All rights reserved.

129

Unit 4: Web Intelligence

SAPBO

Lesson Summary You should now be able to: • Differentiate between different terms used in SAP and BusinessObjects. • Describe the mapping of objects used in SAP and BusinessObjects.

130

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP Hierarchies in OLAP Universes

Lesson: SAP Hierarchies in OLAP Universes Lesson Overview This lesson provide you with the overview of SAP hierarchies and how they are leveraged in OLAP universe.

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

Create OLAP Universes with SAP hierarchies. Create OLAP Universes with SAP hierarchies with variables.

Business Example You need to create a new Universe based on a BW query that has a variable.

Concept of hierarchies in OLAP universe Hierarchies are mapped to allow Web Intelligence users to drill down with SAP BW hierarchies in the same way as custom-made universe hierarchies. When a hierarchy is defined on a characteristic in the BW query, Designer creates one hierarchical structure in the universe with a subclass for each level in the hierarchy. The structure depends on the current BW query definition. • •

If a hierarchy is defined in the BW query, Designer creates this hierarchy structure in the universe. If a hierarchy variable is defined in the BW query that allows the user to choose a hierarchy at run time, Designer creates a generic hierarchy in the universe. The structure has the highest number of levels defined for any of the hierarchy structures available for the characteristic.

When building a universe on top of an InfoCube, all hierarchies defined on the characteristic are exposed in the resulting universe. Designer creates subclasses for each hierarchical structure, each containing subclasses for the levels in that hierarchy. In the case where a characteristic is configured with a hierarchy, the dimension object in the universe is created with one dimension object per level. This image shows the dimension Country is created with six levels, which is based on the number of levels for the hierarchy.

2009

© 2010 SAP AG. All rights reserved.

131

Unit 4: Web Intelligence

SAPBO

Figure 60: Dimension

OLAP Universe with hierarchy variables In the case of a hierarchy variable in the underlying SAP BW query, the universe is created with the maximum number of levels of all available hierarchies. Let’s assume the query has three available hierarchies. • • •

Hierarchy 1 with three levels. Hierarchy 2 with five levels. Hierarchy 3 with four levels.

In this scenario the Universe is generated with five levels for the characteristic. In the scenario where the user creates a report with all five available levels, but selects a hierarchy which does not include five levels, the undefined levels will stay empty in the report. When using a hierarchy variable in Web Intelligence, the number of levels showing data in Web Intelligence will depend on the selected hierarchy.

132

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP Hierarchies in OLAP Universes

Figure 61: OLAP Universe with Hierarchy Variables

OLAP Universe with hierarchy and hierarchy node variables In the case of a query with a hierarchy and hierarchy node variable, the universe is created with the maximum number of levels possible for the hierarchy. For the hierarchy node variable a list of values is created representing each level of all available hierarchies.

Figure 62: OLAP Universe with Hierarchy and Hierarchy Node Variables (1 of 2)

When using a universe with a hierarchy and hierarchy node variable, Web Intelligence prompts for the hierarchy variable and then prompts for the hierarchy node variable.

2009

© 2010 SAP AG. All rights reserved.

133

Unit 4: Web Intelligence

SAPBO

Web Intelligence will present all available hierarchy node values for all available hierarchies. When using a hierarchy and hierarchy node variable combination in Web Intelligence, the hierarchy node variable presents the user with a complete list of all available hierarchies. With the hierarchical structure, select the needed levels from the hierarchy and include them into the Result Objects.

Figure 63: OLAP Universe with Hierarchy and Hierarchy Node Variables (2 of 2)

134

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: SAP Hierarchies in OLAP Universes

Lesson Summary You should now be able to: • Create OLAP Universes with SAP hierarchies. • Create OLAP Universes with SAP hierarchies with variables.

2009

© 2010 SAP AG. All rights reserved.

135

Unit 4: Web Intelligence

SAPBO

Lesson: Web Intelligence Connectivity with SAP Netweaver BW Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain the connectivity between SAP Netweaver BW and Web Intelligence.

Business Example Connectivity with SAP Netweaver BW and Web Intelligence BusinessObjects Web Intelligence is a web-based query and analysis product that enables users to track, understand, and manage corporate data using a simple browser as their interface, while maintaining tight security over data access. Web Intelligence provides an easy-to-use interface with powerful query features. Users can ask spontaneous and iterative business questions of the company's data. The versatile semantic layer ensures controlled and secure information access, reducing the report backlog and ensuring business decisions are made in a timely manner. Web Intelligence delivers a unique, single web environment for both querying and analyzing information. Using the Web Intelligence interactive viewing framework, a wide range of users can access and explore secure information, significantly reducing the number of tools that must be deployed by a business. Web Intelligence improves the trust users have in their data by providing access to metadata such as the definition of measures used or filters applied.

136

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Web Intelligence Connectivity with SAP Netweaver BW

Figure 64: Web Intelligence Connectivity

2009

© 2010 SAP AG. All rights reserved.

137

Unit 4: Web Intelligence

SAPBO

Lesson Summary You should now be able to: • Explain the connectivity between SAP Netweaver BW and Web Intelligence.

138

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Web Intelligence

Lesson: Create a Report with Web Intelligence Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • • •

Describe the Web Intelligence concept. View report formats in Web Intelligence. Create Web intelligence reports.

Business Example You and your colleagues need quick, easy access to information. As part of your job, you make decisions all the time. That means you need the right information at your fingertips to help you make the right decisions. You want to access information using your everyday business vocabulary without having to understand anything about the technical way the information is stored. And once you’ve analyzed this information, you need to be able to share it with your colleagues.

Web Intelligence Concepts Web Intelligence is a tool for analyzing your organization's business information. With Web Intelligence, you can query your organization’s databases using your everyday business terms with an easy-to-use interface. You can create simple or very sophisticated reports, and share the information you display with colleagues throughout the enterprise. Web Intelligence allows you to access, analyze, and share corporate data over intranets and extranets for both relational databases (RDBMS) and online analytical processing (OLAP) servers. To access Web Intelligence, you can log into the BusinessObjects portal InfoView via your internet browser. You can then create and edit Web Intelligence documents and analyze the data displayed in them. Using InfoView, you can share documents with other users. Web Intelligence can also be used offline as Web Intelligence Rich Client, a standalone Microsoft Windows application that you can install on your computer. Web Intelligence Rich Client lets you continue to work with Web Intelligence documents (WID) when you are unable to connect to InfoView, when you want to perform calculations locally rather than on the server, or when your organization chooses to deploy Web Intelligence without installing BusinessObjects Enterprise servers or an application server. You can also use

2009

© 2010 SAP AG. All rights reserved.

139

Unit 4: Web Intelligence

SAPBO

Web Intelligence Rich Client while connected to the BusinessObjects Enterprise repository. This repository is known as the Central Management Server, or "the CMS". If you use Web Intelligence Rich Client while connected to the CMS, you are working in "connected" mode. In connected mode, you can export documents that you have created locally, so that InfoView users can access them in the CMS repository.

Understanding the Semantic Layer Web Intelligence allows you to access and analyze your organization's data by means of a semantic layer in one or more BusinessObjects universes. This semantic layer is a view of your organization's data, presented as one or more universes. Because universes are based on business terminology that is familiar to you and shared throughout the organization, they shield users from the technical complexities of the databases where your corporate information is stored. Web Intelligence uses universes to provide access to data. Using a universe's business-oriented view of the data, you can create queries in Web Intelligence and get information using your own everyday terms.

Quick and Easy Access to Information Business intelligence software offers tools for generating reports automatically whenever they are needed and provides easy analysis and querying to help with the decision-making business process. Many business intelligence platforms require the intervention of an information service to produce personalized OLAP cubes that are then used for reporting. Web Intelligence users on the other hand, have access directly to the source database allowing for robust query and analysis options. This helps in responding to everyday questions and in facing problems that are present when trying to make good decisions quickly. The Business Objects business intelligence platform separates users from the complexity and diversity of databases and associated technologies. It uses business terminology that is shared throughout the enterprise. Because it takes less time to gather information, users can concentrate on their analysis to make the best decisions.

Querying with Web Intelligence Web Intelligence allows you to perform querying, reporting and analysis tasks, all in a single tool. To gather the data you require, you begin by creating a Web Intelligence document and selecting the data source that will give you access to the appropriate data; for example, a BusinessObjects universe. Next, you use the Web Intelligence Query panel to add and organize the objects that interest you from the universe you selected. This image shows the Query panel from Web Intelligence Rich Client, one of the panels available for building queries and creating Web Intelligence documents.

140

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Web Intelligence

When you build a query in the Web Intelligence Query panel, you select the universe objects and query filters that represent your business question. The query is sent to the Web Intelligence server, if you are connected to the BusinessObjects Enterprise CMS, which generates the final Structured Query Language (SQL) statements, the language used to query the database. The SQL query is then sent to the database to retrieve the data mapped to the objects you selected. The database returns rows of data to the Web Intelligence server, which populates the data as a microcube, called a data provider. This information is then formatted and displayed in a Web Intelligence report as a simple table, or even a complex chart, ready for your analysis. A Web Intelligence document can contain multiple reports and each report may have been built using different queries. Once you run the query and retrieve the data that interests you, you can structure and organize the data as you wish in the Web Intelligence document.

Figure 65: Web Intelligence Query Panel

Reporting with Web Intelligence You can use Web Intelligence document features to create professional reports from the data you retrieve. Once you have the data you need, you can display or present it in multiple ways. • • •

2009

As a table (horizontal, vertical, form or cross tab) As a chart (bar, line, area, pie or radar) As a multiple-block report containing large amounts of data

© 2010 SAP AG. All rights reserved.

141

Unit 4: Web Intelligence

SAPBO

Figure 66: Web Intelligence Report Formats

Analyzing with Web Intelligence You can analyze your reports and switch your business perspective by dragging and dropping objects, inserting calculations, and changing the display to make the important information easy to see at a glance.

Figure 67: Analyzing Report in Web Intelligence

You can also perform multi-dimensional analysis by looking at results at a global level or drilling down to a more detailed level of information.

Figure 68: Report Drill Down in Web Intelligence

142

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Web Intelligence

Using Hierarchies in Web Intelligence When using hierarchies in Web Intelligence, the dimension objects can be used like any other dimension objects. Each level of the hierarchy is represented in the universe and can be used in the query.

Figure 69: Using Hierarchies in Web Intelligence

2009

© 2010 SAP AG. All rights reserved.

143

Unit 4: Web Intelligence

144

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Web Intelligence

Exercise 6: Create a Report with Web Intelligence Exercise Objectives After completing this exercise, you will be able to: • To create the report using Web Intelligence.

Business Example Task: Create a Web Intelligence Report from a Universe

Figure 70: sample solution (partial)

1.

Login into Web Intelligence Rich Client using the logon data given by your instructor.

2.

Select the universe you allready created with the name T_SAPBO1_UNIVERSE_##.

3.

Create a query with the dimensions L01 Sold-to party, L01 Material and the measure Sales Order Item (in that order) and execute it to view the results.

4.

Rename the Report Title to Sales Order Report. Continued on next page

2009

© 2010 SAP AG. All rights reserved.

145

Unit 4: Web Intelligence

146

SAPBO

5.

Rename the column heading L01 Sold to party to Customer.

6.

Rename the column heading L01 Material to Products.

7.

Create a section in the report according to the customers, then create a sum of Sales Order Item for each customer. (If you get a prompt to validate the formula, respond with Yes.)

8.

Save the report to the default folder with the name GR## Sales Order Report.WID. Afterwards export to CMS (i.e. BusinessObjects Enterprise Server). Export to folder: Public Folders → SAP → 2.0 → CLNT800.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Web Intelligence

Solution 6: Create a Report with Web Intelligence Task: Create a Web Intelligence Report from a Universe

Figure 71: sample solution (partial)

1.

Login into Web Intelligence Rich Client using the logon data given by your instructor. a)

Select Start → Programs → Business Objects XI 3.1 → Business Objects Enterprise Client Tools → Web Intelligence Rich Client.

b)

Use the following logon data: Field Name

Value

System

Your assigned BOE system

User name

SAPBO-##

Password

Your password

Authentication

SAP

Enter the details provided above then press Log On. Continued on next page

2009

© 2010 SAP AG. All rights reserved.

147

Unit 4: Web Intelligence

2.

3.

4.

Select the universe you allready created with the name T_SAPBO1_UNIVERSE_##. a)

Click on Browse for more data sources.

b)

Select the radio button alongside Universe and click Next.

c)

Highlight your universe T_SAPBO1_UNIVERSE_##. in the list and press OK.

Create a query with the dimensions L01 Sold-to party, L01 Material and the measure Sales Order Item (in that order) and execute it to view the results. a)

Expand the node Customer → Sold to Party and drag L01 Sold to Party into the Result Objects panel.

b)

Expand the node Material Class → Material02 → Material03 and drag L01 Material into Result Objects panel to the right of L01 Sold to Party.

c)

Expand the node Key Figures and drag the measure Sales Order Item into the Result Objects panel to the right of L01 Material.

d)

Click on Run Query.

Rename the Report Title to Sales Order Report. a)

5.

Double-click on the L01 Sold to party cell and enter Customer, then press Enter. (If you get a prompt to validate the formula, respond with Yes.)

Rename the column heading L01 Material to Products. a)

7.

Double-click on the report title and enter the name Sales Order Report then press Enter.

Rename the column heading L01 Sold to party to Customer. a)

6.

SAPBO

Double-click on the L01 Material cell and enter Products then press Enter.

Create a section in the report according to the customers, then create a sum of Sales Order Item for each customer. (If you get a prompt to validate the formula, respond with Yes.) a)

Highlight any value cell of Customer and drag and drop it above the column heading to create sections by customer.

b)

Highlight any empty customer value cell and press the right mouse button and select Remove → Remove Column.

c)

Highlight any value cell of Sales Order Item and select the Insert Sum button from the tool bar to create totals by customer. Continued on next page

148

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Report with Web Intelligence

8.

2009

Save the report to the default folder with the name GR## Sales Order Report.WID. Afterwards export to CMS (i.e. BusinessObjects Enterprise Server). Export to folder: Public Folders → SAP → 2.0 → CLNT800. a)

Select File → Save As → Web Intelligence Document (.WID) . Enter GR## Sales Order Report.WID . Click on Save.

b)

Select File → Export to CMS.... Select the folder: Public Folders → SAP → 2.0 → CLNT800 and click on Export

© 2010 SAP AG. All rights reserved.

149

Unit 4: Web Intelligence

SAPBO

Lesson Summary You should now be able to: • Describe the Web Intelligence concept. • View report formats in Web Intelligence. • Create Web intelligence reports.

150

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Unit Summary

Unit Summary You should now be able to: • Define what a Universe is and explain its use. • Define an OLAP Universe. • List the Data Sources for OLAP Universe. • Explain how to create the new Universe. • Differentiate between different terms used in SAP and BusinessObjects. • Describe the mapping of objects used in SAP and BusinessObjects. • Create OLAP Universes with SAP hierarchies. • Create OLAP Universes with SAP hierarchies with variables. • Explain the connectivity between SAP Netweaver BW and Web Intelligence. • Describe the Web Intelligence concept. • View report formats in Web Intelligence. • Create Web intelligence reports.

2009

© 2010 SAP AG. All rights reserved.

151

Unit Summary

152

SAPBO

© 2010 SAP AG. All rights reserved.

2009

Unit 5 Live Office Unit Overview With Live Office, you can connect SAP BusinessObjects analyses to familiar Microsoft Office applications to make it easy to extend the reach of BusinessObjects throughout your organization. In this unit you will be introduced to Live Office and complete an exercise to create a Live Office document from a Crystal Report.

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

Connect Live Office to BusinessObjects products. Create Live Office documents from Crystal Reports. Create a Live Office document from a Web Intelligence report.

Unit Contents Lesson: Live Office .............................................................154 Exercise 7: Create a Live Office Document from a Crystal Report. .159

2009

© 2010 SAP AG. All rights reserved.

153

Unit 5: Live Office

SAPBO

Lesson: Live Office Lesson Overview This lesson provides you with an overview and functionality of Live Office to retrieve SAP data.

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

Connect Live Office to BusinessObjects products. Create Live Office documents from Crystal Reports. Create a Live Office document from a Web Intelligence report.

Business Example You are a business user who has been using Microsoft Office products for a long time. You need to do analysis on Crystal Reports, but you are not familiar with Crystal Reports architecture. Live Office gives you access to Crystal Reports through Microsoft Office products. The SAP BusinessObjects Live Office application integrates with Microsoft Office, embedding up-to-the-minute corporate data in Microsoft PowerPoint, Excel, and Word documents. This releases you from your dependency on IT and provides self-service access to your trusted business intelligence (BI) within your familiar business tools.

154

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Live Office

Advantage of Live Office SAP BusinessObjects Live Office software provides the following features and functions: •

•

•

•

•

•

Self-service access – Access business intelligence (BI) content directly within Microsoft Office – no IT assistance required. Select data from a report from Crystal Reports software, an SAP BusinessObjects Web Intelligence document, or through ad hoc data selection – all within Microsoft Office. Trusted information – With SAP BusinessObjects Live Office, your Microsoft Office documents display data from the same trusted BI source that supports your organization's decision making and enterprise performance. BI in Microsoft Office Outlook – Embed business intelligence directly in your email messages using Microsoft Outlook. The underlying report automatically retains your security parameters to ensure that recipients see only the data they should be permitted to access. And security is maintained, even when you share the document outside your firewall. Secure, direct refresh – Automatically refresh a single data item – or all the data – in your Microsoft Office document. Instant refreshing and refiltering put the most accurate, up-to-date data at your fingertips for more confident decision making. Formatting and calculations – Once you have embedded your BI data, you can format and perform calculations using familiar features of Microsoft Excel, Microsoft PowerPoint, and Microsoft Word. All formatting and calculations are retained. Shared documents – Publish Microsoft Office documents to SAP BusinessObjects Enterprise software for instant access over the web, or email your live Microsoft Office documents. Security is maintained, even when you share the document outside your firewall.

Further Advantages of Live Office Create simple queries and summary reports based on verifiable, up-to-date, real-time information, to analyze data such as quarterly sales figures; answer important business questions, and make informed decisions. View, modify, and refresh existing queries quickly to suit your business needs. Share the results with your colleagues securely over the web or intranet for collaborative, strategic decision making. You can format the imported data by using standard Microsoft Excel functionality and the features of Live Office.

Crystal Reports and Live Office With Live Office, you can leverage the power, convenience and reliability of Crystal Reports functionality from within the Microsoft Office applications to make business decisions. With point and click ease, you can easily monitor

2009

© 2010 SAP AG. All rights reserved.

155

Unit 5: Live Office

SAPBO

financial trends or analyze quarterly sales figures from within Microsoft Office Excel, Word, Outlook, or PowerPoint, and share that analysis with your colleagues for improved decision making. In addition, you have the comfort of knowing that the data you are accessing is reliable, up-to-date, and easily refreshed on demand from the database. Crystal Reports content can be added from the Live Office menu or by using the Live Office toolbar. Both methods launch the easy to use "Live Office Insert Wizard" which easily guides you through how to choose a report, select Crystal Reports data objects, and insert them in your Microsoft applications as Live Office objects to share with your colleagues.

Figure 72: Live Office Insert Wizard

Live Office Toolbar The BusinessObjects Live Office toolbar provides you with quick access to some of the most common commands you will need to create and modify objects or run queries to answer your business questions.

Figure 73: Live Office Toolbar

It provides you with quick access to the Live Office objects in your Microsoft Office Excel, PowerPoint, Outlook, or Word documents. You can: • • • • •

156

Insert a report object Refresh all report objects Save an object to the BusinessObjects Enterprise repository Navigate to the source report for your Live Office object Access the Help for Live Office

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Live Office

Leveraging SAP data sources for Xcelsius Dashboard The following figure gives a general overview on the deployment option that enables Xcelsius Dashboards to be running on top of SAP data sources.

Figure 74: Solution Overview

This option uses Live Office functionality and enables Crystal Reports, Web Intelligence documents, and Universes to run on top of SAP ERP/ECC or BW data sources. This option best meets your business needs and requirements in the following areas: • • • •

Combine multiple Excel spreadsheets Currently use Crystal Reports or Web Intelligence and OLAP Universes against SAP ERP/ECC and/or BW Require quick generation of reports Reports must manage complex business logic

Architecture of Xcelsius Dashboards using Live Office The figure shown below shows the architecture of Live Office. After creating the Crystal Reports document, users can now build the Live Office document leveraging the existing Crystal Report object.

2009

© 2010 SAP AG. All rights reserved.

157

Unit 5: Live Office

SAPBO

Figure 75: Architecture

Software Requirements The table below highlights the software requirements for both client-side and server-side. When installing this software, the sequence of installation is the same as the sequence they are displayed in this table with the server-side software being installed first.

Figure 76: Software Requirement

Once you know how you can create Live Office document from Crystal Reports, then you can use Xcelsius to connect to a Live Office document with SAP data sources.

158

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Live Office

Exercise 7: Create a Live Office Document from a Crystal Report. Exercise Objectives After completing this exercise, you will be able to: • To create Live Office Document from a Crystal Report .

Business Example Your business requirements indicate that you need to create a new Live Office document. You must base this new Live Office document on an existing Crystal Report.

Task 1: In this exercise you need to create a Live Office Document from a Crystal Report with Microsoft Word. First log on to the Enterprise server then follow the Wizard mentioned in Task 2 step by step. 1.

Start Microsoft Word and insert Crystal Report Content from a BusinessObjects Enterprise folder. In oder to see the folder list log on with the following credentials: User Name

~800/SAPBO-##

Password

Enter your password.

Web Service UR

http://twdfXXXX:8080/dswsbobje/services/Session

System

twdfXXXX:6400

Authentication

SAP (Note that authentication can be changed to SAP after Web Service URL has been entered correctly)

Task 2: Once you are able to log on to Live office successfully go through the Wizard step by step according to this overview: Wizard page Choose Document

Task to Do Browse available reports.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

159

Unit 5: Live Office

160

SAPBO

Choose Data

Select the Crystal Reports parts or fields you want to use to create your Live Office object.

Set Filters

Select filters to apply to data that you insert as fields in your Live Office documents (No filters are required in this exercise)

Summary

Type the name of your Live Office object and verify its path in the repository before inserting it into your document.

1.

The first screen is Choose Document. Choose the CR document GR## Sales Volume per Country that you created in Unit 3.

2.

The next page of the Live Office Insert Wizard is the Choose Data page which prompts you to select the Parts or Fields of the report you want to include and insert into your Microsoft Office document. Choose Country of Sold-to party and Sum of (Sales Volume EUR, Country of Sold-to Party).Do not set a filter in this exercise.

3.

The "Summary" page is the last screen in the "Live Office Insert Wizard" before the current object is inserted into your Microsoft Office application. Enter GR## Live Office Dataset in the name field. Check the Document Path and finish the wizard.

4.

Save the Live Office document to the local My Documents folder, enter GR## Live Office Sales by Country as file name. Afterwards pubish it to BusinessObjects Enterprise with the same file name.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Live Office

Solution 7: Create a Live Office Document from a Crystal Report. Task 1: In this exercise you need to create a Live Office Document from a Crystal Report with Microsoft Word. First log on to the Enterprise server then follow the Wizard mentioned in Task 2 step by step. 1.

Start Microsoft Word and insert Crystal Report Content from a BusinessObjects Enterprise folder. In oder to see the folder list log on with the following credentials: User Name

~800/SAPBO-##

Password

Enter your password.

Web Service UR

http://twdfXXXX:8080/dswsbobje/services/Session

System

twdfXXXX:6400

Authentication

SAP (Note that authentication can be changed to SAP after Web Service URL has been entered correctly)

a)

Click Start → Programs → Microsoft Office → Microsoft Office Word

b)

Click LiveOffice, Click Insert and then select Crystal Report Content.

c)

Enter the BOE credentials that you find in the table above. Verify the information in the Web Service URL and System fields to ensure that the application is pointing to the correct Central Management System (CMS). Select an authentication method as SAP from the drop-down list, click Log On and then click OK. Also make sure that you are able to see Validation succeeded as a message at the bottom of the Screen

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

161

Unit 5: Live Office

SAPBO

Task 2: Once you are able to log on to Live office successfully go through the Wizard step by step according to this overview: Wizard page

Task to Do

Choose Document

Browse available reports.

Choose Data

Select the Crystal Reports parts or fields you want to use to create your Live Office object.

Set Filters

Select filters to apply to data that you insert as fields in your Live Office documents (No filters are required in this exercise)

Summary

Type the name of your Live Office object and verify its path in the repository before inserting it into your document.

1.

2.

The first screen is Choose Document. Choose the CR document GR## Sales Volume per Country that you created in Unit 3. a)

Click on choose document - In the left-hand pane of the "Choose Document" page, navigate to and double-click the folder that contains the report you want to use. Using the buttons above the left-hand pane, you can switch between Folder and Category views for easy navigating.

b)

Expand The folder Public Public → SAP → 2.0 → CLNT800 → GR## Sales Volume per Country

c)

In the right-hand pane of the "Choose Document" page, select the report you want to use, GR## Sales Volume per Country, and click Next.

The next page of the Live Office Insert Wizard is the Choose Data page which prompts you to select the Parts or Fields of the report you want to include and insert into your Microsoft Office document. Choose Country of Sold-to party and Sum of (Sales Volume EUR, Country of Sold-to Party).Do not set a filter in this exercise. a)

Click on the Button Switch to Fields to select the fields.

b)

In the Available Fields list, click the Country of Sold-to party field that you want to include in the Report object, and then click the right arrow (>). Do the same with Sum of (Sales Volume EUR, Country of Sold-to Party).

c)

Use the up and down arrows to change the order of the included fields, as required.

d)

Click Next.

e)

Skip the Set Filters screen by clicking Next. Continued on next page

162

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Live Office

3.

4.

2009

The "Summary" page is the last screen in the "Live Office Insert Wizard" before the current object is inserted into your Microsoft Office application. Enter GR## Live Office Dataset in the name field. Check the Document Path and finish the wizard. a)

From the "Summary" page, name your Live Office object and verify its path in the BusinessObjects repository

b)

Click Finish to insert your Live Office object into Word document.

c)

A progress bar appears as your Live Office object is inserted.

d)

At last you have a report in Microsoft Word which is created based on a Crystal Report.

Save the Live Office document to the local My Documents folder, enter GR## Live Office Sales by Country as file name. Afterwards pubish it to BusinessObjects Enterprise with the same file name. a)

Save your document by choosing File→ Save As → Folder: My Documents. Enter the file name:GR## Live Office Sales by Country.

b)

Publish your document to BusinessObjects Enterprise. Live Office→ Publish to BusinessObjects Enterprise→ Save As New to BusinessObjects Enterprise. Select from the folder list Public →SAP→ 2.0→ CLNT800. Enter the Description: GR## Live Office Sales by Country.

© 2010 SAP AG. All rights reserved.

163

Unit 5: Live Office

SAPBO

Lesson Summary You should now be able to: • Connect Live Office to BusinessObjects products. • Create Live Office documents from Crystal Reports. • Create a Live Office document from a Web Intelligence report.

164

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Unit Summary

Unit Summary You should now be able to: • Connect Live Office to BusinessObjects products. • Create Live Office documents from Crystal Reports. • Create a Live Office document from a Web Intelligence report.

2009

© 2010 SAP AG. All rights reserved.

165

Unit Summary

166

SAPBO

© 2010 SAP AG. All rights reserved.

2009

Unit 6 Xcelsius Unit Overview Xcelsius is the primary tool used to create analysis dashboards in SAP BusinessObjects. In this unit, you will learn about the connectivity between Xcelsius and SAP BW, Xcelsius functionality, and the role that Query as a Web Service plays in creating flexible analysis dashboards.

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

•

Describe the functionality of Xcelsius. Describe how to retrieve and make use of data from underlying SAP data sources (SAP ERP/ECC and SAP BW) and visualize the data with Xcelsius. Describe the functionality of Query as a Web Service. Describe how to create a new Query as a Web Service and make use of data from underlying SAP data sources (SAP ERP and SAP BW) and visualize the data with Xcelsius. Create a dashboard with Xcelsius.

Unit Contents Lesson: Xcelsius Connectivity with SAP Netweaver BW ..................168 Lesson: Query as a Web Service.............................................172 Exercise 8: Query as a Web Service ....................................175 Lesson: Create a Dashboard with Xcelsius .................................179 Exercise 9: Create an Xcelsius Dashboard with QAAWS. ............187 Exercise 10: Create a Dashboard with Xcelsius .......................193 Exercise 11: Create Xcelsius Dashboard with QAAWS and SAP Variables. ....................................................................201

2009

© 2010 SAP AG. All rights reserved.

167

Unit 6: Xcelsius

SAPBO

Lesson: Xcelsius Connectivity with SAP Netweaver BW Lesson Overview • This lesson provides a high-level overview of Xcelsius and explains how to visualize data from underlying SAP data sources (SAP ERP/ECC and SAP BW) in Xcelsius.

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

Describe the functionality of Xcelsius. Describe how to retrieve and make use of data from underlying SAP data sources (SAP ERP/ECC and SAP BW) and visualize the data with Xcelsius.

Business Example Xcelsius delivers next-generation data visualization tools that let users of different skill levels in small, midsize and large companies transform complex business data into actionable visual information. Xcelsius gives you the power of what-if analysis to shed light on any possible business decision. With Xcelsius, you can: • • • • • •

Build sophisticated dashboards and visualizations quickly. Customize your dashboards to meet the unique needs of your business environment. Connect your dashboards to any type of external data source. Maximize the value of your IT solution with visual front ends. Deploy your dashboards in Microsoft Office, Adobe PDF, portals, or on the web. Empower everyone to transform the way you run your business today with actionable visual information.

What is Xcelsius? Xcelsius bridges the gap between data analysis and visual presentations, empowering users to create interactive reports and applications. Xcelsius is intuitive enough for beginners and versatile enough for advanced users. It allows users to create reports without having to learn programming languages. With Xcelsius, pointing and clicking the mouse can create rich interactive presentations. Xcelsius integrates with Microsoft Corporation's Office products. This integration lets you attach your reports to Microsoft Outlook email messages or embed them into PowerPoint slides and Word documents. Xcelsius also integrates with Adobe Acrobat. This integration allows you to embed your reports in Adobe PDF files.

168

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Xcelsius Connectivity with SAP Netweaver BW

Connectivity with SAP Data Sources Xcelsius visualization technology can be integrated with SAP data sources. Xcelsius is able leverage the following sources for connectivity: • •

Live Office Web Services

Figure 77: Xcelsius Connectivity

Xcelsius is able to leverage Live Office for connectivity. You use Live Office to create Excel workbooks in combination with Crystal Reports and Web Intelligence that runs against universes connecting to SAP ERP/ECC and SAP BW. The data can be retrieved from pre-scheduled instances or on-demand inside of Excel using the Live Office capabilities. A benefit of this approach is that the Xcelsius dashboard could combine multiple Excel spreadsheets (even though they are Live Office documents) and data from multiple data sources. The resulting Live Office document (the Excel spreadsheet) can then be used inside the Designer. Live Office is able to leverage the following source documents: • • •

2009

Crystal Reports Web Intelligence Universes (including OLAP Universes)

© 2010 SAP AG. All rights reserved.

169

Unit 6: Xcelsius

SAPBO

The available SAP data sources for Live Office are (based on the source documents above): •

SAP ERP/ECC

•

1. Tables and cluster (Open SQL) 2. ABAP functions 3. Classic InfoSets 4. SAP queries and InfoSet queries SAP BW 1. 2. 3. 4.

170

Tables and clusters (Open SQL) ABAP Functions Direct DSO access (without the need for an SAP BW query) BW queries and BW InfoCubes

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Xcelsius Connectivity with SAP Netweaver BW

Lesson Summary You should now be able to: • Describe the functionality of Xcelsius. • Describe how to retrieve and make use of data from underlying SAP data sources (SAP ERP/ECC and SAP BW) and visualize the data with Xcelsius.

2009

© 2010 SAP AG. All rights reserved.

171

Unit 6: Xcelsius

SAPBO

Lesson: Query as a Web Service Lesson Overview This lesson provides a high-level overview of Query as a Web Service and explains how to create a Query as a Web Service on top of the Universe based on SAP data sources.

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

Describe the functionality of Query as a Web Service. Describe how to create a new Query as a Web Service and make use of data from underlying SAP data sources (SAP ERP and SAP BW) and visualize the data with Xcelsius.

Business Example You are a report designer who uses Xcelsius dashboard on top of an OLAP Universe based on an SAP data sources. You want to use Xcelsius to create a new Query as a Web Service on top of the Universe and then publish the web services.

Xcelsius with Query as a Web Service Query as a Web Service lets you create custom web services for specific queries using BusinessObjects Web Services. You access queries to build applications that use the same semantic layer as the rest of the BusinessObjects suite. Query as a Web Service provides new and easy ways to analyze information through user-driven client solutions for business. Business Intelligence (BI) content is usually bound to the user interface of specific BI tools. Query as a Web Service changes this by allowing BI content to be delivered to any user interface that can process Web Services. Using Query as a Web Service, business users define their own query from a universe, and then easily and securely publish that query as a standalone web service. Query as a Web Service provides new types of user-driven client solutions for businesses. For example, it enables Xcelsius to aggregate multiple disparate data sources into a trusted BI view.

172

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Query as a Web Service

Query as a Web Service also enables a range of client-side solutions in tools such as: • • • • •

Microsoft Office, Excel, and InfoPath SAP NetWeaver Open Office Business rules and process management applications Enterprise Service Bus platforms

Figure 78: Query As a Web Service

Query as a Web Service creates a query based on a universe and publishes the resulting data set as a Web Service. The result set can be consumed by Xcelsius, Crystal Reports, or any tool that can consume a Web Service. In addition, Query as a Web Services enables Xcelsius to aggregate multiple disparate data sources into a trusted BI view. Xcelsius is able leverage Query as a Web Service for connectivity. You run Query as a Web Service against Universes, in particular the OLAP Universes that connect to SAP BW. This approach allows you to combine multiple data sources inside Excel and these multiple Excel files can be used by multiple web services.

2009

© 2010 SAP AG. All rights reserved.

173

Unit 6: Xcelsius

SAPBO

Figure 79: Query As a Web Service Connectivity

The available SAP data sources for Query as a Web Service are: • •

174

SAP BW Queries BW MultiProviders and BW InfoCubes

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Query as a Web Service

Exercise 8: Query as a Web Service Exercise Objectives After completing this exercise, you will be able to: • To create a Query as a Web Service

Business Example Task: Create a QaaWS WSDL and Web Service 1.

2.

3.

2009

Launch Query as a Web Service application, and log on after you have created a host with the following credentials: Field Name .

Value

Name

twdfXXXX

URL

Accept the proposed value

CMS

twdfXXXX

User name

SAPBO-##

Authentication

SAP

Create a new web service and query. Enter the web service name SAPBO_QAAWS_## and a description of SAPBO## QAAWS web service based on SAP BW InfoCube. Select the T_SAPBO1_UNIVERSE_## that you created earlier, build and publish a query with the following objects: Field Name

Value

Dimension

L01 Distribution Channel

Measure

Net value of open orders in statistics currency

Query Filter

Net value of open orders in statistics currency with values greater than 0.

Open Notepad, copy the web service URL to the clipboard and paste it to Notepad. Save the Notepad file to the folder My Documents as GR##_SAPBO_QAAWS_URL.txt because it will be needed in the next exercise.

© 2010 SAP AG. All rights reserved.

175

Unit 6: Xcelsius

SAPBO

Solution 8: Query as a Web Service Task: Create a QaaWS WSDL and Web Service 1.

2.

Launch Query as a Web Service application, and log on after you have created a host with the following credentials: Field Name .

Value

Name

twdfXXXX

URL

Accept the proposed value

CMS

twdfXXXX

User name

SAPBO-##

Authentication

SAP

a)

Launch the Query as a Web Service application with the following path: Start → Programs → BusinessObjects XI 3.1 → Business Objects Enterprise Client Tools → Query As A Web Service.

b)

Click on the Host button and then the Add button. Enter the details in the table above

c)

Click on OK. Close.

d)

Enter your password and press OK.

Create a new web service and query. Enter the web service name SAPBO_QAAWS_## and a description of SAPBO## QAAWS web service based on SAP BW InfoCube. Select the T_SAPBO1_UNIVERSE_## that you created earlier, build and publish a query with the following objects:

Continued on next page

176

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Query as a Web Service

Field Name

Value

Dimension

L01 Distribution Channel

Measure

Net value of open orders in statistics currency

Query Filter

Net value of open orders in statistics currency with values greater than 0.

a)

Click on the New Query icon on the toolbar. Enter the web service name T_SAPBO_QAAWS_## Web Service with the description SAPBO## QAAWS web service based on SAP BW InfoCube. Select Next.

3.

2009

b)

Select the Universe T_SAPBO1_UNIVERSE_##. Select Next.

c)

Place the following objects in the Result Objects Area: Dimension - L01 Distribution Channel from the Sales Area Data Class, the Distribution Channel subclass. Measure - Net value of open orders in statistics currency from the Key Figures class, the Net value of open orders in statistics currency subclass.

d)

Drag the Net value of open orders in statistics currency measure into the Filter Objects Area. Change the filter’s operator from In List to greater than and enter a value of 0 in the operand portion.

e)

Click on the Next button. A preview of the result should appear. For this query, we will see four rows of data. Click Publish.

Open Notepad, copy the web service URL to the clipboard and paste it to Notepad. Save the Notepad file to the folder My Documents as GR##_SAPBO_QAAWS_URL.txt because it will be needed in the next exercise. a)

Click in the white box where the URL appears and press the To Clipboard button to copy the web service URL to the clipboard.

b)

Start →Programs →Accessories→ Notepad. In Notepad from the context menu select Paste. Now save your new document. Select File→ Save As. Browse for MyDocuments. Save your new document in MyDocuments. Enter the name GR##_SAPBO_QAAWS_URL.txt.

© 2010 SAP AG. All rights reserved.

177

Unit 6: Xcelsius

SAPBO

Lesson Summary You should now be able to: • Describe the functionality of Query as a Web Service. • Describe how to create a new Query as a Web Service and make use of data from underlying SAP data sources (SAP ERP and SAP BW) and visualize the data with Xcelsius.

178

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Lesson: Create a Dashboard with Xcelsius Lesson Overview Xcelsius Enterprise provides a simple, personalized view of your organization’s data to enable better understanding, insightful decision-making, and scenario evaluation. Business decisions require immediate answers – often, waiting on information is not an option. With the dynamic combination of Xcelsius Enterprise and the BusinessObjects platform, your decision-makers gain real-time insights to critical business data enabling business analysis on key data your users can trust and refresh instantly. The end result is an interactive dashboard with live data connectivity for accurate, consistent information, providing you with immediate and trusted results.

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

Create a dashboard with Xcelsius.

Business Example Concept of Dashboard A dashboard is a user interface that organizes and presents information in a way that is easy to read with a visually interesting look and feel. An Xcelsius dashboard is more likely to be interactive and user friendly. It is typically used by higher management.

Connectivity for Xcelsius Xcelsius Enterprise can connect to your BusinessObjects data in two ways. The visual model can connect directly to a BusinessObjects universe via web services created with an easy-to-use utility, Query as a Web Service. Secondly, Xcelsius visualization can leverage Live Office to connect to a Crystal Report, BusinessObjects Web Intelligence® document, or ad hoc query.

2009

© 2010 SAP AG. All rights reserved.

179

Unit 6: Xcelsius

SAPBO

Figure 80: Xcelsius Connectivity to SAP NetWeaver

Xcelsius is able to leverage the following sources of connectivity: • •

Web Services Live Office

Based on above list, the following data sources are available for Xcelsius; •

SAP ERP/ECC 1. 2. 3. 4.

•

SAP BW 1. 2. 3. 4.

180

Tables and Clusters ABAP Functions Classic InfoSets SAP Queries and InfoSet queries

Tables and Clusters ABAP Functions Direct DSO Access BW Queries and BW InfoCubes

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Xcelsius Dashboards via Crystal Reports or Web Intelligence Methods mentioned above will be discussed in another lessons. Here we are going to explain Xcelsius Dashboards via Crystal Reports or Web Intelligence. This option runs a Web Intelligence or Crystal Report to retrieve SAP ERP/ECC or BW data. That data is saved to a Microsoft Excel file which is then used by Xcelsius to create interactive dashboards. Have a look at the diagram below.

Figure 81: Solution Overview

• • • •

2009

The Xcelsius dashboard can combine multiple Excel spreadsheets. Offline data access capability. Data source (Excel files) is “static” and users have no capability of refreshing the data automatically. No row-level data security out-of-the-box.

© 2010 SAP AG. All rights reserved.

181

Unit 6: Xcelsius

SAPBO

Architecture

Figure 82: Architecture

Based on existing customer profiles, below are several characteristics generally present in customers who have found that this option best meets their needs, capabilities and technology: • • •

Offline Xcelsius dashboards are needed. Require quick generation of reports on top of SAP data. Reports must manage complex business logic.

Software Requirement The table below highlights the software requirements for both client-side and server-side components of the installation. When installing this software, the sequence of installation is the same as the sequence displayed in this table with the server-side software being installed first.

Figure 83: Software Requirement

182

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Make sure that all the software installed properly on both the sides.

Xcelsius and BI Consumer Services Connectivity When the following software requirements are met Xcelsius can access SAP BW Queries and Query Views directly without setting up a Universe or Live Office Connection: • •

Server side: Support Package 05 for SAP NetWeaver BW Release 7.01 ( 7.0 Enhancement Package 01) Client side (dashboard authors): – – –

Xcelsius 2008 SP2 BI 7.X AddOn SP901 or higher SAP GUI 7.10 or higher

Figure 84: Xcelsius Connectivity to SAP NetWeaver via BI Consumer Services

2009

© 2010 SAP AG. All rights reserved.

183

Unit 6: Xcelsius

SAPBO

The direct connector allows you to consume BW Queries in Xcelsius. Create a data connection in order to access BW data. All BW variable types are supported, including personalizations. BW authorization is enforced when query data is accessed. Xcelsius Dashboards can also be integrated to the NetWeaver platform: • • • • •

Dashboards can be saved in Favorites and Roles Transport capability within Data Warehousing Workbench Translation of texts within Dashboards Access through NetWeaver Portal using BEx iView A BusinessObjects Enterprise Server is not required

To create a connection via BI Consumer Services open the Data Manager in Xcelsius and choose SAP NetWeaver connection. After choosing a query the query elements appear as input values which can be filled with values (e.g. variables or filters) or output values. Cells or cell ranges in the embedded Excel sheet in Xcelsius can now be assigned to the input and output values.

Figure 85: Create a SAP NetWeaver BW connection in Xcelsius 1

184

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Figure 86: Create a SAP NetWeaver BW connection in Xcelsius 2

2009

© 2010 SAP AG. All rights reserved.

185

Unit 6: Xcelsius

186

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Exercise 9: Create an Xcelsius Dashboard with QAAWS. Exercise Objectives After completing this exercise, you will be able to: • Create Xcelsius Dashboard with QaaWS.

Business Example You already created a Query as a Web Service. Now you would like to create an Xcelsius dashboard with this QaaWS.

Task: Create an Xcelsius Dashboard with the Query as a Web Service that you created in the last lesson.

Figure 87: sample solution

1.

Launch Xcelsius, create a Query as a Web Service Data Connection using the WSDL URL you saved in the last exercise.

2.

Assign cell ranges in the spreadsheet to the output values provided by the web service. Use Range A1 to A4 for Distribution Channel and B1 to B4 for Net Value of open orders. Set the data connection to refresh on load.

3.

Insert a Pie Chart to visualize the Net Value of open orders by distribution channel.

4.

Save the Xcelsius file in your local folder My Documents, enter the file name GR## Xcelsius Sales by Distribution Channel. Preview your dashboard, log on with the following credentials: Continued on next page

2009

© 2010 SAP AG. All rights reserved.

187

Unit 6: Xcelsius

188

SAPBO

System

twdfXXXX

User

SAPBO-##

Password

Enter your password

Authentication

SAP

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Solution 9: Create an Xcelsius Dashboard with QAAWS. Task: Create an Xcelsius Dashboard with the Query as a Web Service that you created in the last lesson.

Figure 88: sample solution

1.

Launch Xcelsius, create a Query as a Web Service Data Connection using the WSDL URL you saved in the last exercise. a)

Launch Xcelsius. Start →Programs →Xcelsius→ Xcelsius 2008. If you receive a prompt regarding enabling Live Office, respond with No.

b)

With your cursor in A1 cell of the Excel spreadsheet, go to Data → Connections. Press the Add button.

c)

Choose Query as a Web Service. Name

T_SAPBO_QAAWS_##

WSDL URL

Enter the URL copied to Notepad from the last lesson.

Method

(Automatically populated after you press Import.)

Web Service URL

(Automatically populated after you press Import.)

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

189

Unit 6: Xcelsius

SAPBO

2.

3.

4.

Assign cell ranges in the spreadsheet to the output values provided by the web service. Use Range A1 to A4 for Distribution Channel and B1 to B4 for Net Value of open orders. Set the data connection to refresh on load. a)

In the Output Values area, select the output L01_Distribution_Channel. Select the icon next to the Insert In field.

b)

In the Excel sheet, select cell ranges A1 to A4 and press OK. (You could also type in the range Sheet!$A$1:$A$4.)

c)

Repeat the previous two steps for Net Value of Open Orders output to cells B1 to B4. Press OK. (You could also type in the range Sheet!$B$1:$B$4.)

d)

Go to the Usage tab. Check the option Refresh on Load. Close the Data Manager

Insert a Pie Chart to visualize the Net Value of open orders by distribution channel. a)

On the Xcelsius design screen, find Components → Categories →Charts on the left. Scroll down in Charts and find Pie chart. Drag Pie chart to the canvas area.

b)

Click on the Pie chart within the canvas area to change its properties. In the Properties area, change the chart title to Open Orders by Distribution Channel. Remove the subtitle.

c)

In the Data area select the icon net to the Values field and select the cells B1 to B4 (Sheet!$B$1:$B$4). Press OK.

d)

Select the icon net to the Labels field and select the cells A1 to A4 (Sheet!$A$1:$A$4). Press OK.

e)

Select the option Data In Columns.

Save the Xcelsius file in your local folder My Documents, enter the file name GR## Xcelsius Sales by Distribution Channel. Preview your dashboard, log on with the following credentials:

Continued on next page

190

© 2010 SAP AG. All rights reserved.

2009

SAPBO

2009

Lesson: Create a Dashboard with Xcelsius

System

twdfXXXX

User

SAPBO-##

Password

Enter your password

Authentication

SAP

a)

Save the Xcelsius file. File→ Save. Enter the file name GR## Xcelsius Sales by Distribution Channel.

b)

Go back to the main Xcelsius screen. Press the Preview button.

c)

Enter your system, assigned user and password.

d)

View your dashboard.

© 2010 SAP AG. All rights reserved.

191

Unit 6: Xcelsius

192

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Exercise 10: Create a Dashboard with Xcelsius Exercise Objectives After completing this exercise, you will be able to: • To create an Xcelsius dashboard.

Business Example Task: Create a more advanced dashboard using Excel data, please use the following illustration as an orientation

Figure 89: sample solution

1.

Start Xcelsius using the path Start→Programs→Xcelsius→Xcelsius 2008. Import the Excel model Xcelsius_Exercise.xls from the SAPBO folder in My Documents.

2.

Insert a Bar Chart that visualizes the projected computer sales data in 1.000$ with one bar per product line.

3.

Use a Horizontal Slider to give the Bar Chart what-if capabilities. You should be able to see the impact of a change of the Sales Growth Rate for Desktops in the Bar Chart now.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

193

Unit 6: Xcelsius

194

SAPBO

4.

Add more Horizontal Sliders to the Dashboard to give the Bar Chart what-if capabilities for the other product lines.

5.

Add a custom Gauge to visualize the total of Projected Sales for all product lines. Use alerts within the gauge to indicate bad, critical, and good values.

6.

Add a custom Pie Chart to that shows the Product Mix for 2009 for all product lines.

7.

Finalize the presentation by adding a title text field for the dashboard. Also label the sliders with a text field. Increase the font size of the text fields to highlight them. Add a background element to the canvas. Preview the dashboard.

8.

Save the dashboard in the local My Documents folder as GR## Computers Sales Projections. Export the dashboard to PowerPoint and save the PowerPoint in the My Documents folder. Start the presentation mode in PowerPoint.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Solution 10: Create a Dashboard with Xcelsius Task: Create a more advanced dashboard using Excel data, please use the following illustration as an orientation

Figure 90: sample solution

1.

Start Xcelsius using the path Start→Programs→Xcelsius→Xcelsius 2008. Import the Excel model Xcelsius_Exercise.xls from the SAPBO folder in My Documents. a)

On the Xcelsius tool bar, select Data → Import.

b)

Navigate to My Documents → SAPBO.

c)

Select the Excel file Xcelsius_Exercise.xls, and click Open. Hint: If you can not find the Excel file make sure that you have run the SAPBO Initialize Course script. Click on Start → Programs → Initialize Course → SAPBO → Initialize SAPBO

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

195

Unit 6: Xcelsius

SAPBO

2.

3.

196

Insert a Bar Chart that visualizes the projected computer sales data in 1.000$ with one bar per product line. a)

On the Components panel, select Charts.

b)

Drag the Bar Chart icon onto the canvas, and place it in the upper-left corner.

c)

Click the Bar chart component on the canvas to open its Properties panel.

d)

In the Titles area, delete the text in the Chart title and Chart subtitle fields.

e)

In the Chart title field, enter XYZ Computers.

f)

In the Chart subtitle field, enter Projected Sales: 2009.

g)

In the Values (X) Axis field, enter Projected Sales ($1,000s).

h)

In the Category (Y) Axis field, enter Product Lines.

i)

In the Data portion, click the By Series radio button.

j)

Click Add a New Series (+) button.

k)

Click the Cell Selector icon to the right of the Name field.

l)

Select the cell A5 in the imported spreadsheet. Click OK.

m)

Click the Values (X) Cell Selector icon, and select cells B5:F5 in the spreadsheet. Click OK.

n)

Click the Category Label (Y) Cell Selector icon, and select cells B2:F2. Click OK.

Use a Horizontal Slider to give the Bar Chart what-if capabilities. You should be able to see the impact of a change of the Sales Growth Rate for Desktops in the Bar Chart now. a)

On the Components panel, select the Single Value.

b)

Drag the Horizontal Slider icon onto the canvas, and click it to open its Properties panel.

c)

On the General tab, click the Title Cell Selector button, and select cell B2. Click OK.

d)

On the General tab, click the Data Cell Selector button, and select cell B4. Click OK.

e)

On the Appearance tab, click Text and check mark Title and Value.

f)

Click Preview. When you drag the pointer on the slider, the desktop sales data in the Bar chart will change. To return to the Design view, click the Preview button. Continued on next page

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

4.

Add more Horizontal Sliders to the Dashboard to give the Bar Chart what-if capabilities for the other product lines. a)

Select the Slider component, right-click and select Copy.

b)

Click Paste four times to create four more slider components.

c)

Drag Slider 2, Slider 3, Slider 4, and Slider 5 below Slider 1 until all five slider components are visible.

d)

Click Slider 2 to open its Properties panel.

e)

On the General tab, click the Title Cell Selector button, select cell C2, and click OK.

f)

On the General tab, click the Data Cell Selector button, select cell C4, and click OK.

g)

On the Appearance tab, click Text and check mark Title and Value

h)

Repeat the previous 4 steps for Slider 3, but for Title, select cell D2, and for Data, select cell D4.

i)

Repeat the same steps for Slider 4, but for Title, select cell E2, and for Data, select cell E4.

j)

Repeat the same steps for Slider 5, but for Title, select cell F2, and for Data, select cell F4.

k)

Drag a box around the five Slider components to select them all.

l)

On the Format menu, select Align, and click Center.

m)

On the Format menu, select Space Evenly, and click Down.

n)

Click Preview. To return to the Design view, click the Preview button.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

197

Unit 6: Xcelsius

SAPBO

5.

Add a custom Gauge to visualize the total of Projected Sales for all product lines. Use alerts within the gauge to indicate bad, critical, and good values. a)

On the Components panel, select the Single Value.

b)

Drag the Gauge icon onto the canvas, and place it in the lower-right corner.

c)

Use the control handles around the gauge component to increase its size.

d)

Click the Gauge component to open its Properties panel.

e)

On the General tab, click the Title Cell Selector button, select cell A1, and click OK.

f)

On the General tab, click the Data Cell Selector button, select cell G5. Click OK.

g)

On the General tab, in the Scale area, click Manual and type 10,000 in the Maximum Limit box.

h)

On the Appearance tab, click Text and check mark Title.

i)

In the Format Selected Text area, from the Position list, select Top Center.

j)

Set the font size to 18, and click Bold.

k)

In the table, select Value.

l)

In the Format Selected Text area, from the Position list, select Bottom Center.

m)

Set the font size to 14, and click Bold.

n)

On the Alerts tab, make sure Enable Alerts is selected.

o)

Select As Percent of Target radio button. Click Cell Selector button and select cell H5.

p)

In the Color Order area, click High values are good.

q)

Click Preview. When you drag the pointers on the sliders, the data in the bar chart will change and the gauge needle moves to reflect the new values. To return to the Design view, click the Preview button.

r)

Draw a box around the five slider components to select them all, and double-click the selected area.

s)

On the General tab in the Scale area, type 50 in the Maximum Value box, and press Enter.

Continued on next page

198

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

6.

Add a custom Pie Chart to that shows the Product Mix for 2009 for all product lines. a)

Drag the Pie Chart icon onto the canvas, and place it in the upper-right corner.

b)

On the General tab, delete the text in the Chart title and Chart subtitle boxes.

c)

In the Chart title field, type XYZ Computers, and press Enter.

d)

In the Chart subtitle field, type Product Mix: Enter.

e)

In the Data area, click the Value Cell Selector button, and select cells B5:F5 in the spreadsheet. Click OK.

f)

In the Data area, click the Labels Cell Selector button, and select cells B2:F2 in the spreadsheet. Click OK.

g)

Click Preview.

2009, and press

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

199

Unit 6: Xcelsius

SAPBO

7.

8.

Finalize the presentation by adding a title text field for the dashboard. Also label the sliders with a text field. Increase the font size of the text fields to highlight them. Add a background element to the canvas. Preview the dashboard. a)

On the Components panel, click on Text.

b)

Drag the Label icon onto the canvas, and place it at the top. Double-click the Label component to open its Properties panel.

c)

On the General tab, click the Enter Text radio button.

d)

In the Enter Text field, enter XYZ Computers Sales Projections 2009.

e)

On the Appearance tab, in the Text area, select center the text.

f)

Set the font size to 26, and click Bold.

g)

Drag another Label icon beneath the sliders and in the Enter Text box, enter Product Line Growth Rates, and set the font size to 18.

h)

On the Components panel, expand the Arts & Backgrounds folder.

i)

Drag the Background icon onto the canvas.

j)

Resize the background component until it covers the other components on the canvas.

k)

Make sure the background component is selected, and on the Format menu, select Order and click Send to Back.

l)

On the upper toolbar, click Fit canvas to components.

m)

Click Preview to see how your final presentation works. To return to the Design view, click the Preview button.

Save the dashboard in the local My Documents folder as GR## Computers Sales Projections. Export the dashboard to PowerPoint and save the PowerPoint in the My Documents folder. Start the presentation mode in PowerPoint. a)

Save the Xcelsius file. File→ Save. Enter the name GR## Computers Sales Projections.

b)

200

c)

Choose File → Export and click PowerPoint Slide.

d)

In the Export PowerPoint (PPT) dialog box, choose the My Documents folde to save the file to, enter the file name GR## Computers Sales Projections.ppt, and click Save.

e)

In PowerPoint, on the Slide Show menu, click View Show.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Exercise 11: Create Xcelsius Dashboard with QAAWS and SAP Variables. Exercise Objectives After completing this exercise, you will be able to: • Create Xcelsius Dashboard with QAAWS and SAP Variables.

Business Example You need to create an Xcelsius dashboard based on QAAWS with SAP Variables.

Task: Create a more complex Xceslius Dashboard that uses 2 Querys as Datasources. The first query will deliver a list of countries and provides a filter value (variable) for the second query. The second query shows regions for the country that has been selected in the first query. Both querys are connected via QAAWS.

Figure 91: sample solution (outline)

1.

Create a Universe T_SAPBO_Countries_Query_Universe_##based on the SAP Query with Countries T_SAPBO_Q16.

2.

Create a Universe T_SAPBO_Variable_Query_Universe_##based on the SAP Query with a Variable T_SAPBO_Q17.

3.

Create a Query as a Web Service T_SAPBO_QAAWS01_##on top of your Countries query Universe T_SAPBO_Countries_Query_Universe_##. The Web Service has to return L01 Sold_to Party Country Key and L01 Sold_to Party Country Description (name).

4.

Create a Query as a Web Service T_SAPBO_QAAWS02_##on top of your Variable query Universe T_SAPBO_Variable_Query_Universe_##. The Web Service has to return L01 Region and Sales Volume EUR. Continued on next page

2009

© 2010 SAP AG. All rights reserved.

201

Unit 6: Xcelsius

202

SAPBO

5.

Use a ListBox to display the countries delivered by the query as a web service T_SAPBO_QAAWS01_##. Prepare the ListBox so that a single Country can be selected.

6.

Use a Pie Chart to display the Sales Volume EUR for the regions of the country you have selected within the listbox. The values will be delivered by the query as a web service T_SAPBO_QAAWS02_##

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

Solution 11: Create Xcelsius Dashboard with QAAWS and SAP Variables. Task: Create a more complex Xceslius Dashboard that uses 2 Querys as Datasources. The first query will deliver a list of countries and provides a filter value (variable) for the second query. The second query shows regions for the country that has been selected in the first query. Both querys are connected via QAAWS.

Figure 92: sample solution (outline)

1.

Create a Universe T_SAPBO_Countries_Query_Universe_##based on the SAP Query with Countries T_SAPBO_Q16. a)

Start the Universe Designer: Start →Programs →Business Objects XI Release 3 →Business Objects Enterprise Client Tools →Designer.

b)

Enter the following. Press OK. System

twdfXXXX

User

SAPBO-##

Password

Enter your password.

Authentication

SAP

c)

Press Begin for the wizard.

d)

Press New to create a new connection. Enter T_SAPBO_Connection_Countries_##.

e)

Select SAP→ Business Warehouse→SAP Client from the list.

f)

Press Next.

g)

Enter the following: Continued on next page

2009

© 2010 SAP AG. All rights reserved.

203

Unit 6: Xcelsius

SAPBO

Application Mode

User Specified username and password

User name

SAPBO-##

Password

(Enter your password.)

Client

800

Language

EN

Login Mode

Application Server

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp

System Number

40

System ID



h)

Press Next.

i)

Open the list of available InfoCubes. Find SAPBO (T_SAPBO1). Expand the list of queries

j)

Open the list of available queries. Find BW Query SAPBO Xcelsius QAAWS 01, technical name T_SAPBO_Q16. This is a simple query listing Sold_To Party Country. Press Next. Finsh.

k)

Enter Universe name T_SAPBO_Countries_Query_Universe_##. Press Next. Finish.

l)

Save your universe. File → Save As. Export your universe to your BOE folder.

Continued on next page

204

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

2.

Create a Universe T_SAPBO_Variable_Query_Universe_##based on the SAP Query with a Variable T_SAPBO_Q17. a)

From the menu select File→New. Press New for the wizard.

b)

Press New to create a new connection. Enter SAPBO_Connection_Variable_##.

c)

Select SAP→ Business Warehouse→SAP Client from the list.

d)

Press Next.

e)

Enter the following: Application Mode

User Specified username and password

User name

SAPBO-##

Password

Enter your password

Client

800

Language

EN

Login Mode

Application Server

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp

System Number

40

System ID



f)

Press Next.

g)

Open the list of available InfoCubes. Find SAPBO (T_SAPBO1). Expand the list of queries

h)

Open the list of available queries. Find BW Query SAPBO Xcelsius QAAWS 02, technical name T_SAPBO_Q17. This is a query with a mandatory variable for Sold_To Party. Press Next. Expand the Sold_To Party folder to view the variable.

i)

Enter Universe name T_SAPBO_Variable_Query_Universe_##. Press Next.

j)

Save your universe. File → Save As. Export your universe to your BOE folder.

k)

File→ Close. File→ Exit.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

205

Unit 6: Xcelsius

SAPBO

3.

Create a Query as a Web Service T_SAPBO_QAAWS01_##on top of your Countries query Universe T_SAPBO_Countries_Query_Universe_##. The Web Service has to return L01 Sold_to Party Country Key and L01 Sold_to Party Country Description (name). a)

Start Query as a Web Service. Start →Programs →Business Objects XI Release 3 →Business Objects Enterprise → Business Objects Enterprise Client Tools →Query as a Web Service.

b)

Press Add. Enter Name and CMS. host

twdfXXXX

URL

Accept the proposed value

User

SAPBO-##

Authentication

SAP

c)

Enter User Name and Password.

d)

Select New Query. Enter Web Service name: T_SAPBO_QAAWS01_##. Enter a Description.

e)

Select the Countries universe, T_SAPBO_Countries_Query_Universe_##. Select the following fields from this universe: L01 Sold_to Party Country Key L01 Sold_to Party Country Description (name)

f)

Press Next. Press Publish. Then press To Clipboard.

g)

Open Notepad. Start →Programs →Accessories→ Notepad. From the context menu select Paste. Save your document, GR##QAAWS.txt, but leave it open.

Continued on next page

206

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

4.

Create a Query as a Web Service T_SAPBO_QAAWS02_##on top of your Variable query Universe T_SAPBO_Variable_Query_Universe_##. The Web Service has to return L01 Region and Sales Volume EUR. a)

Select New. Enter Web Service name: T_SAPBO_QAAWS02_##. Enter a description.

b)

Include the following fields in this universe: L01 Region Sales Volume EUR

c)

In this case the underlying universe has a prompt because it is based on a query that has a mandatory variable. The Web Service tool provides a list of values during the creation process. Select Germany and press >.

d)

Press Publish. Then press To Clipboard.

e)

Open Notepad and find your document, GR##QAAWS.txt. From the context menu select Paste. Paste this QAAWS url under the last url from the previous step.

f)

Go Back to QAAWS. Query→ Exit.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

207

Unit 6: Xcelsius

SAPBO

5.

Use a ListBox to display the countries delivered by the query as a web service T_SAPBO_QAAWS01_##. Prepare the ListBox so that a single Country can be selected. a)

Start Xcelsius Designer. Start Programs→ Xcelsius→Xselcius 2008.

b)

Select Data→Connections. Press Add→Query as a Web Service.

c)

Select the new connection. Paste the first QAAWS URL from your Notepad document into the field WSD URL. Press Import.

d)

The web service returns the data in a table format and shows that each row in this example returns a value for the Country Key and a value for the Country Name. Select the Row folder of the Output Values. Press the icon next to the Insert In.

e)

Mark the required range in the Excel spreadsheet. Press OK.

f)

Go to the Usage tab. Set the Refresh on Load property. Press Close.

g)

Add a List Box component to the Xcelsius canvas. Double click the List Box Component.

h)

Set the Insert Type option to Value.

i)

Select the range for the Source Data, key figure values.

j)

Select the range for the Labels, value description (Country Names).

k)

Set the Destination to a cell in the spreadsheet. Hint: Write down this cell because this cell will be used as a trigger cell. Another good way is it to color the excel cells in a specific color so that you can find them later.

6.

Use a Pie Chart to display the Sales Volume EUR for the regions of the country you have selected within the listbox. The values will be delivered by the query as a web service T_SAPBO_QAAWS02_## a)

Select from the menu Data →Connections. Press Add.

b)

Select Query as a Web Service.

c)

Select the new connection. Paste the URL from the second QaaWS web service into the WSD URL field. Press Import.

d)

This web service contains the variable. The variable is displayed in the list of required input values. Select the Row folder of the Output values. Continued on next page

208

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Create a Dashboard with Xcelsius

e)

Press the icon next to Insert In. Mark the required range in the Excel spreadsheet. These cells must be a different range than the cells for the previous web service, for Countries. Press OK.

f)

Select the item for the SAP variable in the list of Input Values. Press the icon next to Read From.

g)

Mark the required range in the Excel spreadsheet. This cell must be identical to the cell that is used as the Destination for the List Box.

h)

Go to the Usage tab. Select the icon next to Trigger Cell. Mark the required range in the Excel spreadsheet. This cell must be identical to the cell that is used as the Destination for the List Box.

i)

Select the option When Value Changes.

j)

Press Close.

k)

Drag and Drop a Pie Chart into the canvas. Select the Pie Chart to open the Properties.

l)

Select the icon next to the Data Values. Mark the complete range for the data values. In this example, the result set from the second web service. Press OK.

m)

Select the icon next to the Data Labels. Mark the complete range in for the labels.

n)

Go to the Behavior tab. Select the option Ignore Blank cells in Values.

o)

From the menu, select Preview. Each change in country value will return a different pie chart for a different list of regions.

p)

Select File→ Export →Business Objects Platform. When exporting to the Business Objects Platform the actual Xcelsius document is being stored on the platform. When selecting File Save As, the design of the Xcelsius document is being saved to Business Objects Enterprise.

q)

Select a folder on your Business Objects Enterprise system. Enter a file name, SAPBO_QAAWS_Variable_Dashboard_##.

r)

Save. View this Dashboard on InfoView using SAP Authentication. Start →Programs →Business Objects XI Release 3 →Business Objects Enterprise Client Tools →Business Objects Enterprise Java InfoView.

2009

© 2010 SAP AG. All rights reserved.

209

Unit 6: Xcelsius

SAPBO

Lesson Summary You should now be able to: • Create a dashboard with Xcelsius.

210

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Unit Summary

Unit Summary You should now be able to: • Describe the functionality of Xcelsius. • Describe how to retrieve and make use of data from underlying SAP data sources (SAP ERP/ECC and SAP BW) and visualize the data with Xcelsius. • Describe the functionality of Query as a Web Service. • Describe how to create a new Query as a Web Service and make use of data from underlying SAP data sources (SAP ERP and SAP BW) and visualize the data with Xcelsius. • Create a dashboard with Xcelsius.

2009

© 2010 SAP AG. All rights reserved.

211

Unit Summary

212

SAPBO

© 2010 SAP AG. All rights reserved.

2009

Unit 7 Special Themes Unit Overview This unit provides an overview of a wide range of topics ranging from administrative subjects such as authorization, auditing, scheduling and performance tuning to analysis topics such as the use of hierarchies, search techniques, BI Widgets and the BusinessObjects Explorer.

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

Describe authentication, authorization, and single sign-on support in BusinessObjects Enterprise Explain how to configure BusinessObjects Enterprise authentication for your SAP environment Perform simple search, advanced search, and content search in InfoView Describe the different search features and techniques available in content search Understand the BusinessObjects Explorer features. Create a report using the BusinessObjects Explorer. Explain how scheduling works in BusinessObjects Enterprise. Describe the best practices which may be taken to maximize the performance of Web Intelligence reports against BW. Describe the features in BI Widgets. Explain the business values of BI Widgets. Define auditing in BusinessObjects Enterprise. Describe the sample auditing reports.

Unit Contents Lesson: Lesson: Lesson: Lesson: Lesson:

2009

Authorization ..........................................................215 Intelligence Search ...................................................220 BusinessObjects Explorer (formerly Polestar) ....................229 Scheduling.............................................................236 Performance ..........................................................243

© 2010 SAP AG. All rights reserved.

213

Unit 7: Special Themes

SAPBO

Lesson: BI Widgets (Optional) ................................................248 Lesson: Auditing (Optional)....................................................252

214

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Authorization

Lesson: Authorization Lesson Overview This lesson explains how to authenticate and authorize SAP users to log on to BusinessObjects Enterprise

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

Describe authentication, authorization, and single sign-on support in BusinessObjects Enterprise Explain how to configure BusinessObjects Enterprise authentication for your SAP environment

Business Example SAP Authentication allows you to map your existing SAP roles and users to BusinessObjects Enterprise. It also enables BusinessObjects Enterprise to authenticate users against the SAP system, thereby providing single sign-on to your SAP users. As a result, once SAP users are logged on to the SAP system, they are recognized by BusinessObjects Enterprise as authenticated users.

Authentication and authorization Authentication is the process of verifying the identity of a user who attempts to access the system. This process is distinct from authorization. Authorization is the process of verifying that the user has been granted sufficient rights to perform the requested action upon the specified object. BusinessObjects Enterprise is fully customizable, therefore authentication processes can vary from system to system BusinessObjects Enterprise supports these methods of authentication • • • •

Enterprise authentication Windows NT authentication Lightweight Directory Access Protocol (LDAP) authentication Windows AD authentication

BusinessObjects Enterprise authentication The system default, BusinessObjects Enterprise authentication, is used in environments that prefer to maintain a distinct set of accounts for use with BusinessObjects Enterprise. BusinessObjects Enterprise authentication is always enabled; it cannot be disabled. Windows NT authentication

2009

© 2010 SAP AG. All rights reserved.

215

Unit 7: Special Themes

SAPBO

BusinessObjects Enterprise supports NT authentication with the Windows NT security plug-in, which is included by default when the product is installed on Windows. Support for NT authentication means that users or groups created with NT, Windows 2000 and Windows 2003 can be used to authenticate with BusinessObjects Enterprise. This allows you to map previously created NT user accounts and groups, instead of setting up each user and group within BusinessObjects Enterprise. LDAP authentication Lightweight Directory Access Protocol (LDAP) is a set of protocols used to access information stored in directories. A very common use for an LDAP directory is to maintain user and group account information. BusinessObjects Enterprise supports the use of an existing LDAP account directory, eliminating the need to recreate user and group accounts in BusinessObjects Enterprise. By mapping your LDAP groups to BusinessObjects Enterprise, users are able to log into Enterprise with their LDAP user name and password. Windows Active Directory authentication Windows AD security plug-in enables you to map user accounts and groups from your Windows 2000 Active Directory (AD) system to BusinessObjects Enterprise; it also enables BusinessObjects Enterprise to verify all login requests that specify Windows AD Authentication Single sign-on support The term single sign-on is used to describe a situation where a user can access two or more applications or systems while providing their login credentials only once, thus making it easier for users to interact with the system. Single sign-on to BusinessObjects Enterprise Single sign-on to BusinessObjects Enterprise means that once users have logged into the operating system they can access BusinessObjects Enterprise without having to provide their login credentials again. When they log into the operating system, a login token is created. The system uses this token to authenticate the users and grant them access to BusinessObjects Enterprise and its components. Single sign-on to database Once users are logged into BusinessObjects Enterprise, single sign-on to the database enables them to perform actions that require database access, in particular, viewing and refreshing reports, without having to provide their logon credentials again. Single sign-on to the database can be combined with single sign-on to BusinessObjects Enterprise, to provide users with even easier access to the resources they need End-to-end single sign-on

216

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Authorization

End-to-end single sign-on refers to a configuration where users have both single sign-on access to BusinessObjects Enterprise at the front end and single sign-on access to the databases at the back end. Thus, users need to provide their login credentials only once, when they log into the operating system, to have access to BusinessObjects Enterprise and to be able to perform actions that require database access, such as viewing reports Authenticating SAP users The SAP Authentication feature in BusinessObjects XI Integrations for SAP solutions enables you to verify user credentials against your SAP system on behalf of the CMS. When users log on to BusinessObjects Enterprise directly, they can choose SAP Authentication and provide their usual SAP user name and password. BusinessObjects Enterprise can also validate Enterprise Portal logon tickets against SAP systems. The SAP Authentication also offers other key benefits •

•

•

It facilitates account creation by allowing you to map roles from SAP to BusinessObjects Enterprise user groups, and it facilitates account management by allowing you to assign rights to users and groups in a consistent manner within BusinessObjects Enterprise. It dynamically maintains SAP role listings. So, once you map an SAP role to BusinessObjects Enterprise, all users who belong to that role can log on to BusinessObjects Enterprise. When you make subsequent changes to the SAP role membership, you need not update or refresh the listing in BusinessObjects Enterprise The SAP Authentication component includes a web application for configuring the plug-in. You can access this application in the "Authentication" area of the Central Management Console (CMC).

Figure 93: Central Management Console Authentication

2009

© 2010 SAP AG. All rights reserved.

217

Unit 7: Special Themes

SAPBO

Configuring SAP authentication for BusinessObjects Enterprise SAP authentication enables SAP users to log on to BusinessObjects Enterprise using their SAP user names and passwords, without storing these passwords in BusinessObjects Enterprise. SAP authentication also allows you to preserve information about user roles in SAP, and to use this role information within BusinessObjects Enterprise to assign rights to perform administrative tasks, or access content Creating a user account for BusinessObjects Enterprise The BusinessObjects Enterprise system requires an SAP user account that is authorized to access SAP role membership lists, authenticate SAP users, and so on. You will need this user name and its password when you connect BusinessObjects Enterprise to your SAP system

Importing SAP roles to BusinessObjects Enterprise By importing SAP roles into BusinessObjects Enterprise, you allow role members to log on to BusinessObjects Enterprise with their usual SAP credentials. In addition, Single Sign On (SSO) is enabled so that SAP users are logged on to BusinessObjects Enterprise automatically when they access reports from within the SAP GUI or an SAP Enterprise Portal. For each role that you import, BusinessObjects Enterprise generates a group. You can view the new groups in the "Users and Groups" management area of the CMC. You can also use these groups to define object security within "BusinessObjects Enterprise.

218

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Authorization

Lesson Summary You should now be able to: • Describe authentication, authorization, and single sign-on support in BusinessObjects Enterprise • Explain how to configure BusinessObjects Enterprise authentication for your SAP environment

2009

© 2010 SAP AG. All rights reserved.

219

Unit 7: Special Themes

SAPBO

Lesson: Intelligence Search Lesson Overview This lesson explains how to search for objects in InfoView.

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

Perform simple search, advanced search, and content search in InfoView Describe the different search features and techniques available in content search

Business Example You work in Finance. You know you have read a particular sales report in the past year, but you can't remember where you saw it. You think it was in a public folder or your BusinessObjects Enterprise inbox, and you know that it was uploaded by your manager sometime between the end of the last fiscal year and the end of the first month of this fiscal year. You remember that it was a Web Intelligence document. To find the report, you can indicate all of the above search parameters using advanced search, and only documents that meet all of the requirements will be returned.

Searching in InfoView You can perform several types of searches in InfoView. Simple searches match your search input to the keyword, title, description, and owner information about objects. After you perform a simple search, it is displayed in the "Tree" panel. This enables you to search within your search results and refer back to them during your InfoView session. You can also perform advanced searches. An advanced search works the same way as a simple search, except that you can indicate that all search results must meet other requirements. Advanced searches can enable you to search several top-level areas at once, and can be used to search all objects in InfoView. If you need to search the text within certain types of objects, you can do so using Content Search. Content Search looks for your search input in the fields that are searched during a simple or advanced search, as well as within the text and other information in certain types of objects.

220

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Intelligence Search

Searching for objects You can do a structured search to find objects in InfoView. This is the simplest kind of search, in which the text string you enter is matched to text strings in the specified field(s) of each object's properties. Note: Simple searches are executed on all the objects in the folder or category that you have selected in the Tree panel, including all child objects and folders/categories. You cannot perform a simple search on public folders/categories and personal folders/categories at the same time.

Figure 94: Simple Search

Performing advanced searches You can perform an advanced search on all documents in InfoView. Advanced searches allow you to perform more specific searches for objects based on their keywords, title, description, owner, type, or last modification time. You can combine these fields in any combination to create more complex searches that will return more useful information.

2009

© 2010 SAP AG. All rights reserved.

221

Unit 7: Special Themes

SAPBO

Figure 95: Advanced Search

Content Search Content Search is an optimized search tool that enables you to search within the content of objects managed by BusinessObjects Enterprise. These objects include Crystal reports, Web Intelligence and Desktop Intelligence documents, Microsoft Word, and Excel documents, RTF, PDF, and TXT files.

Figure 96: Content Search

Content Search also allows you to take advantage of several other features to make finding information easier, such as search result grouping, matched word highlighting, suggested searches, and multilingual searching.

222

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Intelligence Search

Searching within objects In addition to the options for search including Search keyword, Search title, and Search all fields, and Advanced search, you can now search for objects by using the Search content option in InfoView. Note: Content searches are performed on all objects in InfoView, unless they have been expressly excluded from Content Search by a user with the necessary rights.

Content Search features The following table outlines the list of new functions which comprise Content Search Features

Description

Search content

You can search within the content of objects by selecting the Search content option in InfoView.

Search within mixed-language objects

You can search within a mixed-language object by entering a search input which consists of multiple languages. The following are several examples of searches with more than one language. Results will be produced if the words in both languages are found in a document.

Search techniques

You can search using techniques similar to those used in other search engines.

Suggestions for alternate spelling

The system suggests up to five alternate spelling suggestions if a search input is misspelled or yields no results. The suggestion is made by substituting words in the original input with words from the system that are similar in spelling to the original one. For example, if you search for “Euroe sales trent”, the system recognizes the misspelled words and provides a suggestion of “Europe sales trend”. •

•

Features

2009

An alternate suggestion is made only if the original search input produced no results and the suggested search term will result in successful matches. An alternate suggestion is made only if the original search input produced no results and the suggested search term will result in successful matches. Description

© 2010 SAP AG. All rights reserved.

223

Unit 7: Special Themes

SAPBO

Suggested query

When a search is executed, the system automatically generates suggested new documents based on your search input. When you execute your search, you may realize that none of the result documents contain the information you wanted to find, or that there were no results. In this case, suggested documents generated by the system may answer your questions instead. Suggested documents are created by interpreting the search input and comparing it to the structure of the universes and data in existing documents. For example, if you search for “Mexico sales 2006”, Content Search may see that “sales” is a measure in a universe that houses all sales data for your company. It may also see that in another document, the field “country” was equal to “Mexico”, and use this to filter your data accordingly. It may also see that “2006” is a predefined filter. It will then create a document using the data from the universe, and the filters it identified. You can then view and edit the new document. You can click on the link Run Query to view this generated document and save it if desired. Clicking on Edit Query will open the document for editing, so that you can make further refine the query as needed. •

In this release of Content Search, suggested new documents will only be in the format of a Web Intelligence report.

Features Matched word highlighting Search result grouping

224

Description When the text you are searching for matches the words in an object’s title or description, the matched words will be highlighted in yellow. Some searches may return too many results to look at all of them easily. Content Search uses information in and about the results to classify them into groups, or facets. The various facets that search results can be classified by include document type, public category, data in reports, and aspects of the report content. You can select a group, and see the search results that are part of that group. For example, you may search for “2006 sales by employee”. The public category facet could include “HR Reports”, “Legal Documents” and “Sales reports”, because each of these categories has objects assigned to it that appear in

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Intelligence Search

your search results. You were looking for a sales report, so you click on “Sales report” to see only search results assigned to that category. Facets that are based on report content use fields or variables that exist in many documents to create the facets. For example, the variable “Product” might be used in many sales reports, and Content Search creates a facet for it. You would then be able to refine your search by product name to see only results related to that product. After you have refined your search, you can either close the refinement to return to the full list of results, or refine the list further by selecting options from other facets. All refinements currently in effect are displayed at the top of the search refinement panel. •

Features Search result ranking

Facet grouping by fields in report content is only available for Crystal reports and Web Intelligence documents. Description

Each object on the search result page is assigned a score ranging from 1 to 5 bars depending on its relevance to the search input. A score of 5 bars indicates the object is a strong match, while a score of 1 bar indicates a weak match.

What gets searched with Content Search? The table below outlines the main content that gets searched when using Content Search in the following objects

Object type

What gets searched

Crystal reports

Title, description, selection formula, saved data, text fields in any section, parameter values, and sub-reports (for saved data reports), and text in the title and axis of charts. Both reports with and without saved data are searchable.

Web Intelligence and Desktop Intelligence documents

Title, description, name of the Universe filters used in the report, constants in the filter condition locally defined in the report, name of the Universe measures used in the report, name of the Universe objects used in the report, data in record set, and static text in cells. Both reports with and without saved data are searchable.

2009

© 2010 SAP AG. All rights reserved.

225

Unit 7: Special Themes

SAPBO

Microsoft Excel documents

Data in cells, fields on the Summary page of the document properties (title, subject, author, manager, company, category, keywords and comments), and text in document headers and footers. For cells that use calculations or formulas, the value after the evaluation is searchable.

Microsoft Word documents

Text in all paragraphs and tables, fields on the Summary page of the document properties (title, subject, author, manager, company, category, keywords and comments), text in document headers and footers, and numerical text.

RTF, PDF, and TXT All text in these files is searchable. Files Note: You can search for the keyword, title, or description of these objects. • • • • • • •

Hyperlink Program Object Package Publication Single dashboard (My InfoView) EPM dashboard EPM analytics

Search techniques Content Search is an optimized search tool which allows you to execute a search by using techniques similar to that used in other search engines. The table below outlines the different ways a search can be executed using the Search content option. Note: Search content is NOT case sensitive. Entering a search term report will produce the same results as the term REPORT.

226

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Intelligence Search

Technique

Example

finance report Separating search terms with spaces

Description Search results will be produced only when all the words are found in the document. Separating search terms with a space implies an AND separation.

Enclosing search input in quotations

“total sales growth”

Search results will be produced only when the exact phrase is found in a document.

Preceding search terms with a +

episode +I

Search results will be produced only when all the words are found in the document. This technique is useful to search for words that are typically filtered out during search process. For example; a, for, by, is, the.

Preceding search terms with a -

Europe sales revenue

Search results will be produced only if the word immediately after the - sign is NOT found, and all other words are found.

bug OR defect count Separating search terms with report a capitalized OR Combining different search techniques

2009

Search results will be produced if any of the words used with OR are found in the document.

This example will produce results marketing OR sales -finance “increase OR if a document contains the word marketing or the word sales, and decrease trend” contains the phrase increase or decrease trend, but does not contain the word finance.

© 2010 SAP AG. All rights reserved.

227

Unit 7: Special Themes

SAPBO

Lesson Summary You should now be able to: • Perform simple search, advanced search, and content search in InfoView • Describe the different search features and techniques available in content search

228

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Explorer (formerly Polestar)

Lesson: BusinessObjects Explorer (formerly Polestar) Lesson Overview This lesson gives the basic overview of BusinessObjects Explorer (formerly Polestar).

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

Understand the BusinessObjects Explorer features. Create a report using the BusinessObjects Explorer.

Business Example You work in Finance. You know you have previously read a sales report for this year, but now you want to do analysis on the report and need to analyze the data in a different way very quickly. You want a simple and intuitive interface allowing you to get answers to your own questions. The result should be automatically visible in a graphical format.

What is BusinessObjects Explorer? SAP BusinessObjects Explorer is a web-based search and exploration application that enables business professionals to explore and search through business information. By selecting from available values, you can focus the data set to the set of KPIs that interests you for a specific business question.. BusinessObjects Explorer combines the simplicity and speed of search with the trust and analytical power of business intelligence (BI) to provide immediate answers to business questions. Users employ familiar keyword search to find information and explore directly on data.

2009

© 2010 SAP AG. All rights reserved.

229

Unit 7: Special Themes

SAPBO

Features of BusinessObjects Explorer • • • • • • • •

Brings self-service BI to business and casual users Get fast facts and answer investigative questions Explore and understand new data sources and unexamined parts of the business No need to understand the data, where it's located, or how it's structured Information is secure, trustworthy, and easily sharable Deploys in days - up and running in days, not months Fully leverages existing BI investments including metadata, security, and administrative services Further reduces IT and report author backlog

Why BusinessObjects Explorer? Increase BI Adoption • • • •

Understand your data without knowing the structure. Simple and intuitive interface allows non-power user to get answers to their own questions. Open access to all relevant corporate information No training required to get up and running

Get new insight into your data through new data search and guided navigation paradigms. High end user value at a low IT cost.

Figure 97: BusinessObjects Explorer

230

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Explorer (formerly Polestar)

Who should use BusinessObjects Explorer? Casual information workers, who are not served by existing BI tools, though they need access to corporate data to do their jobs efficiently and to make informed decisions. • • • •

They are not power users or analysts who work on the data in a daily basis. They do not run queries like other Business Intelligence users. BI tools that are available today do not serve their needs They may not have time for training or time to understand data sources and structures

Information workers are constantly on the search for Business intelligence tools that easily empower them to make fact-based decisions. They want simpler, more intuitive tools that allow them to search, explore an quickly answer important business questions like Internet search engines. The consequence of under serving casual information workers is an underperforming organization run by a poorly informed workforce, whose decisions are largely based on instinct.

BusinessObjects Explorer users Power users, with the Space Creator user profile, create the Information Spaces on top of corporate data providers. Space Creators make up a small percentage of the total SAP BusinessObjects Explorer user population. They understand the underlying data structures in the data providers consumed by the application and understand the business concerns of their Space Explorer collaborators. With this knowledge, Space Creators can build Information Spaces that contain contextually related sets of data, and so provide Space Explorers with a complete picture for a given business query. Space Explorers make up the majority of the SAP BusinessObjects Explorer user population. Their interactions with the application consist of searching for Information Spaces, navigating and analyzing the data within those Information Spaces and saving Information Spaces to other file formats. These users sometimes export Information Spaces to other applications to analyze the data further.

Functional Areas in the Product. Focused on flow and interactions. •

Search Full Text search : Comply with familiar search phrases Information space retrieval Data retrieval – cross category search Indexing Technology

•

2009

Explore

© 2010 SAP AG. All rights reserved.

231

Unit 7: Special Themes

SAPBO

Faceted Navigation - 360 degree view. Guided Navigation – relevance ranking contribution Insight on current exploration path – Facets breadcrumb •

Analyze No modeling required Next generation charts in Flash format. One click analysis – easily select/switch breakdown dimensions Chart recommendations – suggests chart of exploration context. In-chart analysis – value highlighting , value filtering , value grouping

•

Export Via bookmark and email

Information Space

Figure 98: Information Space

An Information Space is a collection of objects mapped to data for a specific business operation or activity. For example, an Information Space designed to provide information on regional retail outlets could contain objects mapped to data for Sales Revenue, Region, Store Name, Year, and so on. Power users with the Space Creator user profile create the Information Spaces on top of corporate data providers. Only one data provider can be selected when you create an Information Space. However, you can create multiple Information Spaces on a single data provider - each Information Space can contain a sub-set of the total data available, so that analysts can focus easily on a specific area of interest.

232

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Explorer (formerly Polestar)

Information Spaces can leverage data via the following corporate data providers: • •

BusinessObjects universes . NetWeaver Business Warehouse Accelerator indexes enabled for SAP BusinessObjects Explorer

These data providers can leverage data from operational applications, data warehouses, Relational DataBase Management Systems (RDBMS) and OnLine Analytical Processing (OLAP) sources.

Some Questions As Examples What exactly is the business need of the Space? •

If you know what the Space is going to be used for, then you can simply identify the related Universe objects. For example, the business need is for knowing the sales revenue last year for all of your European stores. You could select the Sales Revenue measure, the Country, City, and Store dimensions, and finally, the Last Year filter.

How many users are expected to access and explore the Space? •

If you know that the Space is for several users, select only necessary objects. If you select too many objects that have little use for the user, exploration and indexing can be impacted (due to a large data source). It can also cause confusion to users.

How SAP BusinessObjects Explorer works with SAP BusinessObjects Enterprise SAP BusinessObjects Explorer is an add-on to SAP BusinessObjects Enterprise XI. The servers, Information Spaces and users are managed by the BusinessObjects Enterprise Central Management Server (CMS) and Central Management Console (CMC). When you install SAP BusinessObjects Explorer, several servers are added to the BusinessObjects Enterprise Central Configuration Manager (CCM) and Central Management Console (CMC). See SAP BusinessObjects Explorer Installation, Deployment and Administration guide on help.sap.com => SAP BusinessObjects => All Products for detailed information.

2009

© 2010 SAP AG. All rights reserved.

233

Unit 7: Special Themes

SAPBO

Figure 99: BusinessObjects Explorer Architecture

234

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BusinessObjects Explorer (formerly Polestar)

Lesson Summary You should now be able to: • Understand the BusinessObjects Explorer features. • Create a report using the BusinessObjects Explorer.

2009

© 2010 SAP AG. All rights reserved.

235

Unit 7: Special Themes

SAPBO

Lesson: Scheduling Lesson Overview Scheduling ensures reports contain the most recent data and enables you to run resource-intensive reports during non-peak hours. Understanding scheduling helps you maximize the business intelligence potential of BusinessObjects Enterprise. This lesson explains how to schedule reports within BusinessObjects Enterprise.

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

Explain how scheduling works in BusinessObjects Enterprise.

Business Example The Crystal reports that you create can be refreshed against the current SAP data by any user who has installed the drivers along with Crystal Reports. You can also schedule these reports within BusinessObjects Enterprise, so your users can access customized reports with current data on a regular basis.

What is scheduling? Scheduling an object allows you to run it automatically at specified times. When a scheduled object runs successfully, an instance is created. An instance is a version of the object that contains data from the time that the object was run. You can see a list of instances by looking at an object's history, and you can view any of the instances. If you have the rights to view objects on demand, you can view and refresh any instance to retrieve the latest data from the data source. By scheduling and viewing instances, you can ensure that the objects have the most up-to-date information available for viewing, printing, and distributing.

236

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Scheduling

Figure 100: Scheduling an object

Scheduling in BusinessObjects InfoView SAP functionality is integrated into the standard BusinessObjects InfoView. Through BusinessObjects InfoView, you can access all of the Crystal reports that have been saved in your SAP BW roles and published to BusinessObjects Enterprise. In addition, you can carry out all of the reporting tasks such as scheduling and viewing instances that are supported by the standard InfoView. BusinessObjects InfoView provides a number of features that are specific to SAP reporting environments. These features include the ability to log on with your usual SAP user name and password, a My Groups folder that provides quick access to all of the Crystal reporting content that has been saved in your various SAP BW roles, and the ability to view and schedule reports in multiple languages. You can configure your BusinessObjects InfoView settings and save your favorite reports. Once you find the reports that you want to view, BusinessObjects InfoView offers report viewers with printing and exporting capabilities.

Working with My Groups When you log on to BusinessObjects InfoView with your SAP user credentials, the My Groups folder provides you with quick access to all of the Crystal reporting content that has been saved in your various SAP BW roles. Click the My Groups folder to access this view. Note: The My Groups folder is available only after your administrator has imported one or more of your roles that contain Crystal reports. Each of your SAP BW roles is represented in BusinessObjects InfoView as a folder that contains reports and/or additional subfolders. Search through the various folders to locate your reports. Depending on your rights, you may be able to schedule different reports and/or view their latest instances. In addition, you can copy or move reports to your Favorites view so they are easier to locate the next time you log on.

2009

© 2010 SAP AG. All rights reserved.

237

Unit 7: Special Themes

SAPBO

Parameters In BusinessObjects Integration for SAP Solutions, variables within reports are represented as parameters on BusinessObjects InfoView. Before users can view or schedule the report, they are prompted to choose a value from a dynamic pick list for each parameter. The values that are in the list are the values that were assigned to the variable in the SAP environment and filtered based on the rights the user has in the SAP system. From the "Enter Prompt Values" dialog box, you have the following options: • • • • •

Run the report with its default parameter values Select values from the dynamic pick lists and run the report with your chosen parameter values Enter a value for each parameter and run the report with those values Run the report with null values for the parameters Personalize a value for each parameter and run the report with those personalized values Note: Some options are available only if they are enabled in the report's referenced BW query or in BusinessObjects Enterprise.

Scheduling reports that contain parameters Aside from enabling users to view reports that prompt for parameter (variable) values, BusinessObjects Integration for SAP Solutions gives users the ability to schedule and distribute these reports over the web. Depending on your needs, you can schedule the report to run once or on a recurring basis. Recurrence pattern specifies a schedule for running an object. Each parameter in the Run object list has its own specific data entry requirements

238

Parameters

Description

Now

When you click Schedule, the object runs once (immediately).

Once

This option requires a start and end time parameter. The object runs once at the time that you specify. If you schedule the object with events, the object will run once if the event is triggered between the start and end times.

Hourly

This option requires information in hours and/or minutes for how frequently the object is run. Instances are created regularly to match the parameters that you enter. The first instance is created at the start time that you specify, and the object will cease to run on its hourly schedule at the end time that you specify.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Scheduling

Daily

This option requires a start and end time parameter. The object runs once every N days at the time that you specify. It will not be run after the end time that you specify.

Weekly

This option requires a start and end time parameter. Each week, the object runs on the selected days at the time that you specify. It will not be run after the end time that you specify.

Monthly

This option requires a start date and time, along with a recurrence interval in months. The object runs on the specified date and time every N months. It will not be run after the end time that you specify.

Nth Day of Month

This option requires a day of the month on which the object is run. Instances are created regularly each month on the day that you enter at the start time that you specify. The object will not be run after the end time that you specify.

1st Monday This option requires a start and end time parameter. An instance of Month is created on the first Monday of each month at the time that you specify. The object will not be run after the end time that you specify. Last Day of This option requires a start and end time parameter. An instance is Month created on the last day of each month at the time that you specify. The object will not be run after the end time that you specify. This option requires a start and end time parameter. An instance is X Day created monthly on a day of a week that you specify. The object of Nth Week of the will not be run after the end time that you specify. Month Calendar

This option allows you to select a calendar of dates. (Calendars are customized lists of schedule dates that are created by the BusinessObjects Enterprise administrator.) An instance is created on each day that is indicated in the calendar, beginning at the start time that you specify and continuing until the end time that you specify.

Personalized parameter values in scheduled reports When you set a recurring schedule for a report that contains a personalized parameter value, BusinessObjects Enterprise uses the personalized value to generate the report for all the times that it is scheduled to run. If you change the personalized value of the parameter, the scheduled report will still continue to display data that is based on the original personalized value even though it has been changed. This occurs because, upon personalizing a value, BusinessObjects

2009

© 2010 SAP AG. All rights reserved.

239

Unit 7: Special Themes

SAPBO

Enterprise saves the value and sets it as the permanent user-specific parameter value for the report. To change the personalized value of the parameter, you need to do one of the following: • •

Reschedule your report with the new parameter value of your choice. Schedule the report to run with null values for the parameter. This ensures that personalization values are evaluated when the report runs.

Null parameter values in scheduled reports When you schedule a report to run with null as a parameter value, upon execution, no value is passed to the query. The value that is used to run the report is either the preset default value or the preset personalized value of the variable (personalized values override default values). If you decide to change the parameter value that is being used to run the report, in BusinessObjects Enterprise, you can click the report and reschedule it with your new parameter. Because the report was initially scheduled to run with a null parameter value, no value is saved with the report. As a result, when the report is once again run, the new parameter value is used to generate the data.

Specifying an instance format Depending on the type of object that you choose to schedule, you can select the format in which the object's instance is saved when it is generated by BusinessObjects Enterprise You can select from the formats summarized in the following table:

Product

Format

Web Intelligence

Crystal Reports

240

• • • • •

Web Intelligence Microsoft Excel Adobe Acrobat Plain text Rich text

• • • • • • • •

Crystal Reports Microsoft Excel (97-2003) Microsoft Word (97-2003) PDF Rich Text Format (RTF) Microsoft Word (97-2003) — Editable (RTF) Plain Text Paginated Text

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Scheduling

• • •

Tab Separated Text (TTX) Separated Values (CSV) XML

Note: When you select a file format other than Crystal Reports, the program preserves as much of the formatting as the export format allows. However, you may lose some or all of the formatting that appears in the report. The difference between Excel and Excel (Data only) is that the Excel option preserves the look and feel of your original report, while the Excel (Data only) focuses on preserving data and does not merge cells. The Tab Separated Text format places a tab character between values and attempts to preserve the formatting of the report; the Separated Values format places a specified character between values and does not attempt to preserve formatting. The Microsoft Word (97-2003) format maintains as much formatting as possible, including graphics. Each object appears in an individual text field. Microsoft Word (97-2003) — Editable format does not preserve as much formatting; text is displayed in lines and images are placed in line with the text. Rich Text Format is similar to Microsoft Word (97-2003).

2009

© 2010 SAP AG. All rights reserved.

241

Unit 7: Special Themes

SAPBO

Lesson Summary You should now be able to: • Explain how scheduling works in BusinessObjects Enterprise.

242

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Performance

Lesson: Performance Lesson Overview This lesson aims to provide guidance for a successful deployment of SAP BusinessObjects Web Intelligence (WebI) XI 3.1 as a frontend to SAP NetWeaver Business Warehouse (BW). It is intended to guide you through the high-level concepts relevant to such an implementation, and to highlight the best practices to consider in the course of such a deployment.

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

Describe the best practices which may be taken to maximize the performance of Web Intelligence reports against BW.

Business Example You have multiple InfoCubes, DS0s, InfoSets, and hundreds BEx queries. Most of the BEx queries take long time to run; therefore you are trying to determine the best performance strategy for building reports that run over SAP BW data. You decide to use Web Intelligence and build universes around the InfoCubes for these hundreds of queries and you need to know the best practices in deploying this solution so that these universes built would serve the purpose for future reporting requirements.

Overall Recommendation A primary focus of this document is a set of practices and steps which may be taken to maximize the performance of Web Intelligence reports against BW. In this context, maximizing performance refers to a balance of minimizing: • • •

2009

The processing required (both in Web Intelligence and BW. The memory footprint required (both in Web Intelligence and BW). The report viewing user’s perceived response time.

© 2010 SAP AG. All rights reserved.

243

Unit 7: Special Themes

SAPBO

BEx Queries as recommended data sources BEx Queries are recommended as data sources for generating universes for the following reasons: • •

•

BEx Queries offer a flexible extension to the data modeling environment. InfoCubes require more effort to change BEx Queries offer significant functionality to create customized data sources that meet end-user requirements, such as Calculated Key Figures, Restricted Key Figures, Structures and SAP Variables. In the OLAP BAPI interface, not all BW metadata features can be retrieved on an InfoCube level, as summarized in the following table: BW metadata feature

OLAP BAPI availability

Characteristics (incl. Time and Unit)

InfoCube/BEx Query

Hierarchies

InfoCube/BEx Query

Basic Key Figures

InfoCube/BEx Query

Navigational Attributes

BEx Query only

Display Attributes

InfoCube/BEx Query

Calculated Key Figures / Formulas

BEx Query only

Restricted Key Figures

BEx Query only

Custom Structures

BEx Query only

Variables

BEx Query only

Although BEx Queries have advantages as data sources, you do not need a BEx Query for every report, nor do you need a universe for every existing BEx Query. To minimize maintenance costs, focus the implementation strategy on limiting the

244

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Performance

final number of BEx Queries and universes required to meet all the ad-hoc query and reporting needs. Keep in mind the following points to reduce the number of universes needed: • •

When Web Intelligence is the frontend tool, you are not restricted by the output format in the BEx Query. There is no direct impact on performance when working with OLAP universes created from large BEx Queries. OLAP universe objects not included in the Web Intelligence query have no direct impact on the query performance. Note: It is recommended to have a few BEx Queries – from a single one to a handful of them – for every InfoCube or MultiProvider that is in scope for ad-hoc query and reporting. Then build a universe on top of each of these BEx Queries. Note: Do not build one query per InfoProvider because elements can add processing time even though you not using them into the Web Intelligence report. Note: Set the property Use Selection of Structure Members in transaction RSRT for the query to ensure structure elements are sent to the database for processing.

Common Scenarios and Decisions While every implementation and individual reporting requirement is unique, most have common elements. The following section details several common scenarios you will come across and gives guidance on optimizing universe, Web Intelligence query, and BEx Query design for each scenario.

Customizing BW Universe Definition While the default universe generated for a BW query or InfoCube is usable, it contains a lot of elements which might not be required for most reporting needs, and other elements which may require some tuning based on the detailed requirements. For example, when a characteristic has no active hierarchy, the L00 node will be “All members”, and will not provide any reporting value. In this case, it is best to delete all L00 objects in order to simplify the report design experience.

Scheduling versus On-demand Reporting One of the first factors to consider when designing a report is whether it is necessary to have the report run on-demand or if the reporting need can be met by having users access scheduled instances of the report. In general, if is possible to

2009

© 2010 SAP AG. All rights reserved.

245

Unit 7: Special Themes

SAPBO

minimize the number of times a report is run against the BW system, it is desirable to do so. So, it is recommended to use scheduling when practical. The primary benefits of scheduling rather than viewing on-demand are: • •

Vastly improved viewing response time for the user. Overall reduction in burden on the BW system versus having many ad-hoc queries run.

Filtering In all but the most basic cases, it is necessary to filter the data exposed by an InfoCube or BEx Query in order to get the desired result. There are several methods which may be employed to filter the results. The method applied may have an impact on the overall performance of the reports. Generally, filtering requirements can be separated into two categories: static filtering, which will apply the same values each time the report is run, and dynamic filtering, which will filter results based on user or other input.

Reports with High Data Volume The OLAP BAPI interface is not optimized to run queries which return a high volume of data in a single request. This is due both to internal design within the OLAP processor and to the attending process which occurs before the data can be consumed by WebI. The volume of data returned can be measured by the number of cells returned. In general, it is desirable to reduce this number to the minimum required for the reporting requirement. This can be done by reducing the number of columns or rows returned in the request.

246

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Performance

Lesson Summary You should now be able to: • Describe the best practices which may be taken to maximize the performance of Web Intelligence reports against BW.

2009

© 2010 SAP AG. All rights reserved.

247

Unit 7: Special Themes

SAPBO

Lesson: BI Widgets (Optional) Lesson Overview BI Widgets makes it easy to find your BI content and quickly create widgets to display your data. This lesson provides a detailed explanation for BI Widgets.

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

Describe the features in BI Widgets. Explain the business values of BI Widgets.

Business Example BI Widgets delivers personalized and ambient Business Intelligence by allowing you access to lightweight, secure, and personalized desktop widgets at all times. You can easily access BI content, create personal dashboards on your desktop, and integrate BI content into other Windows applications, simply by using drag and drop operations.

BI Widgets BI Widgets is an application that delivers information to your desktop via widgets. The widget framework provides the following functionality: • • • • • • • • •

248

Instant information access through desktop widgets from Xcelsius files and Web Intelligence Report Parts Drag & drop of Web Intelligence Report Parts into desktop applications A Microsoft Vista look and feel including window transparency and shadowing Automated single sign on across multiple BI repositories Easy search for content across multiple BI repositories, with aggregate information from multiple repositories displayed a single personalized view RSS Inbox with popup notification Supports Windows Vista Sidebar gadgets Saving widgets to share and distribute Managing user rights and permissions in the Business Objects Enterprise Configuration Management Console

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BI Widgets (Optional)

Figure 101: BI Widgets: Always-on Personalized BI

Using BI Widgets, you can display dynamically updated BI report information in a small space, with less effort than accessing BI information through your browser. The following table outlines the benefits of deploying BI Widgets in your IT and business environment:

IT

Business

Reduce the cost of delivering Simplify access to BI and increase productivity BI by leveraging existing BI by having key information available at users’ fingertips platform investment Increase business user self-sufficiency—no IT involvement or training required

Expand and accelerate BI usage—no training is required to create and use BI Widgets

Maintain content control by leveraging existing security model

Provide the confidence that users will always have access to the most up-to-date information available

Leverage existing BI content Personalize frequently monitored information and metadata without IT assistance

How BI Widgets works BI Widgets connects content on Business Objects Enterprise and displays it as dynamically updating data using desktop widgets. Using widgets, you can have BI content easily available, while using only a small portion of your desktop

2009

© 2010 SAP AG. All rights reserved.

249

Unit 7: Special Themes

SAPBO

screen. As the information in your source files changes, BI Widgets automatically updates the widget on your desktop, providing you with up-to-the-minute data at your fingertips. You can quickly create desktop widgets from Xcelsius and Web Intelligence files. As a widget, an Xcelsius file can automatically update and use report-to-report linking. In addition, the widget gains the following features from the BI Widget framework: • • • • •

250

User controlled size and positioning Tabbed views Saved display Optional setting as the top application window Full BusinessObjects Enterprise security

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: BI Widgets (Optional)

Lesson Summary You should now be able to: • Describe the features in BI Widgets. • Explain the business values of BI Widgets.

2009

© 2010 SAP AG. All rights reserved.

251

Unit 7: Special Themes

SAPBO

Lesson: Auditing (Optional) Lesson Overview This lesson provides a detailed explanation for auditing in BusinessObjects Enterprise.

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

Define auditing in BusinessObjects Enterprise. Describe the sample auditing reports.

Business Example Auditing provides your organization with a detailed historical view of user and object interaction and of system usage. This allows you to fine-tune system performance, retire unused reports and provide business units with a comprehensive snapshot of their usage patterns. Auditing allows you to: • • •

Obtain information on who is using your system. Obtain information on which objects they are accessing. Better administer individual user accounts and reports.

This information allows you to be proactive in managing the operation and deployment of your BusinessObjects Enterprise system, and helps you to better evaluate the value that BusinessObjects Enterprise provides to your organization.

Defining auditing In BusinessObjects Enterprise, the Central Management Server (CMS) acts as the system auditor. The other BusinessObjects Enterprise servers that you monitor are the auditees. To audit an action in BusinessObjects Enterprise, you must first determine which server controls that action. Then you must enable auditing of that action in the Servers Management area of the Central Management Console. As the auditee, the BusinessObjects Enterprise server begins to record these audit actions in a local log file. The CMS periodically polls the audit log files to copy

252

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Auditing (Optional)

data to the auditing database. Once the data is in the auditing database, you can configure and run the sample audit reports that are included in the BusinessObjects Enterprise, or you can design custom reports to suit your own needs. Note: You must configure the auditing database on the CMS before you can begin to audit.

Auditable actions You can use auditing to: • • • •

Track the actions of individual users of BusinessObjects Enterprise as they interact with objects in the system. Monitor named and concurrent license usage. Monitor events. Monitor system actions (for example, the success or failure of a schedule for an object).

For each action, BusinessObjects Enterprise records: • • • •

The time of the action. The name and user group of the user who initiated the action. The server where it was performed. A variety of other parameters.

Tracking IP Address and Machine Name Auditing can track the IP addresses and the names of machines connecting to CMS. The audit database captures the following fields related to machine identification: • • • •

Reported IP address Resolved IP address Reported machine name Resolved machine name

Reference list of auditable actions This list contains a complete list of the audit actions that you can enable in BusinessObjects Enterprise. It is organized according to the types of actions that you can audit and to help you find the server where you enable auditing of these actions

2009

© 2010 SAP AG. All rights reserved.

253

Unit 7: Special Themes

SAPBO

Objects

Crystal reports

Action 1. 2. 3. 4. 5. 6.

A report has been viewed successfully. The scheduling of the report is successful. The scheduling of the report is not successful. The scheduling of the report is not successful but will try to run again. The delivery of the report to the destination is successful. The delivery of the report to the destination is not successful.

Retrieve document Web Intelligence •

A user has saved a Web Intelligence document within BusinessObjects.

Select universe Web Intelligence

•

A user has selected a universe as a new Web Intelligence document is created or edited.

Refresh document •

Objects

User manually refreshes a Web Intelligence document, or opens a Web Intelligence document that is set to "refresh on open", or schedules a Web Intelligence document.

Action Retrieve List of Values •

A list of values is retrieved from the database to populate a picklist associated with a prompt used to filter the data in a document.

Edit document Web Intelligence

•

User enters "Edit document" mode for an existing Web Intelligence document.

. Apply format •

User applies a formatting change to an existing Web Intelligence document in a query panel.

Generate SQL

254

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Auditing (Optional)

•

When a new Web Intelligence document is created, the server builds an SQL query for the document so that data can be retrieved from a database.

Drill out of scope •

User drills past the scope of the data currently in memory, and triggers a call to the database for more data.

Select prompt •

User enters or selects a value for a report prompt.

Save document •

User saves a Web Intelligence document within BusinessObjects Enterprise.

An object is created. An object is deleted. An object is modified (the name, location, or description of a folder is modified).

Objects

The rights on an object have been modified. An unresponsive scheduling of an object. Objects

Action Scheduling is successful.

Web Intelligence scheduling and publishing

Scheduling is not successful. Scheduling is not successful but will try to run again. The delivery to the destination is successful. The delivery to the destination is not successful.

Enabling auditing of user and system Events: You must enable auditing on the server from the Servers Management area of the Central Management Console (CMC) before you can collect data on auditing events.

Using sample audit reports BusinessObjects Enterprise is shipped with a complete set of prebuilt sample audit reports. These sample audit reports are part of the file store and may be accessed from the Auditor folder in InfoView. The reports are based on the activity.unv universe file, which contains joins and objects from the auditing tables in the auditing database. Before using these reports, a data connection must

2009

© 2010 SAP AG. All rights reserved.

255

Unit 7: Special Themes

SAPBO

be established using the proper authentication and middleware needed to connect to the auditing database. Once this connection is in place, the universe file named activity.unv can connect to your previously configured auditing database. This task can be completed using BusinessObjects Designer.

Figure 102: Sample audit reports

256

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Auditing (Optional)

The sample audit report are: • • • • • • • • • • • • • • • • • • • • • • • • • •

2009

Average Number of Users Logged In Average Refresh Time Average Session Duration, per Cluster, per User Document Information Detail Document Scheduling and Viewing Status IP Address Accessing My Cluster Job Services on the System Job Summary Jobs per Job Service Type, per User Last Login for User Least Accessed Documents Most Accessed Documents Most Active Users Most Popular Actions, per Document Number of User Sessions, Users in the System Operation on Documents Password Modifications Peak Usage Publishing Auditing Refresh and Edit Activities Right Modification Services in the Cluster Total Users Logged In by Day User Activity User Activity per Session Users Who Logged Off Incorrectly

© 2010 SAP AG. All rights reserved.

257

Unit 7: Special Themes

SAPBO

Lesson Summary You should now be able to: • Define auditing in BusinessObjects Enterprise. • Describe the sample auditing reports.

258

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Unit Summary

Unit Summary You should now be able to: • Describe authentication, authorization, and single sign-on support in BusinessObjects Enterprise • Explain how to configure BusinessObjects Enterprise authentication for your SAP environment • Perform simple search, advanced search, and content search in InfoView • Describe the different search features and techniques available in content search • Understand the BusinessObjects Explorer features. • Create a report using the BusinessObjects Explorer. • Explain how scheduling works in BusinessObjects Enterprise. • Describe the best practices which may be taken to maximize the performance of Web Intelligence reports against BW. • Describe the features in BI Widgets. • Explain the business values of BI Widgets. • Define auditing in BusinessObjects Enterprise. • Describe the sample auditing reports.

2009

© 2010 SAP AG. All rights reserved.

259

Unit Summary

260

SAPBO

© 2010 SAP AG. All rights reserved.

2009

Unit 8 Perspectives Unit Overview This unit focuses on the future integration roadmap for SAP BusinessObjects solutions.

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

Describe the product integration roadmap for SAP BusinessObjects solutions. Describe the product directions for SAP BusinessObjects BI solutions.

Unit Contents Lesson: Perspectives (Optional) ..............................................262

2009

© 2010 SAP AG. All rights reserved.

261

Unit 8: Perspectives

SAPBO

Lesson: Perspectives (Optional) Lesson Overview This lesson provides an overview of the future integration roadmaps for other SAP BusinessObjects BI solutions such as Pioneer, Xcelsius, and BusinessObjects Explorer (formerly Polestar).

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

Describe the product integration roadmap for SAP BusinessObjects solutions. Describe the product directions for SAP BusinessObjects BI solutions.

Business Example SAP NetWeaver Business Intelligence brings together powerful analysis tools, planning and simulation capabilities, and data-warehousing functionality delivered through user-centric enterprise portal technology. Use SAP NetWeaver Business Intelligence to integrate data and transform it into practical, timely business information to drive sound decision making, targeted action, and solid business results.

The Value of SAP NetWeaver with SAP BusinessObjects Intelligence Platform In any organization, it is common that all data sources (internal and external, structured and unstructured) need to be leveraged to create insight that is relevant for decision making and business performance optimization. In addition, people in the organization need ways to better collaborate in a given business context and better support for the way teams really work, and businesses need to leverage the transformation of their business networks as a new source of competitive advantage. SAP BusinessObjects Enterprise brings together SAP BW and BusinessObjects solutions to address your challenges in the following areas: Information fragmentation • • •

262

Information is locked away in application silos and heterogeneous sources. Integrating information requires expert knowledge. Disconnect between analytic and operational applications.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Perspectives (Optional)

Business Intelligence complexity • • •

End user is crucial to success of any BI initiative. Too many different tools with steep learning curves. Complex data models beyond the understanding of business.

Flexibility to respond to change • • •

Technology cannot keep up with the speed of thought. Data models quickly get out of sync with business models. Disconnect between business and IT leads to misunderstandings and long development cycles.

The combined solution of BusinessObjects and SAP enables open, user-centric, end-to-end BI solutions with high performance.

Figure 103: The combined solution of BusinessObjects and SAP

2009

© 2010 SAP AG. All rights reserved.

263

Unit 8: Perspectives

SAPBO

Figure 104: The Future of SAP NetWeaver Business Intelligence

Enterprise Reporting • •

•

•

264

With Crystal Reports, SAP can offer the de facto industry standard for enterprise reporting. Crystal Reports will be the flagship product for Formatted Reporting going forward. Beyond Release 7.0 EhP1, no further enhancements of the Report Designer are planned. Crystal Reports is already tightly integrated with the NetWeaver BW stack. The connectivity of Crystal Reports to SAP NetWeaver BW is achieved using NetWeaver BW's MDX based OLAP BAPI when accessing InfoCubes and queries. Connectivity to Data Store Objects works via the Open SQL driver. Crystal Reports also offers direct connectivity to SAP ERP and SAP Business Suite for operational reporting, that does not require a non-volatile, integrated, consolidated, time variant and high performance data store.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Perspectives (Optional)

OLAP Analysis/Pioneer •

• •

•

•

• •

•

The future tool of choice for OLAP analysis on SAP NetWeaver BW, codenamed Pioneer, will combine Voyager's intuitive user interface with the powerful OLAP capabilities of today's BEx OLAP tools. It will be available as web client as well as Excel client with tight integration between the two. Pioneer will be a new state-of-the art OLAP client based on Ajax (Web 2.0) technology and BI Consumer Services as universal access layer for SAP and non-SAP multidimensional data. Pioneer is a high-performance, componentized, next generation OLAP analysis client for SAP & non-SAP environments. It is adaptable to the needs of business analysts, can be embedded into SAP business processes and designed to extend the reach of advanced analytics. With this combination of high end analysis capabilities, with ease-of-use and elegant visualization control and personalization features, this will reduce the need for specialized design-time tools and enable business users to make simple design and user interface changes directly during data analysis. Pioneer will be available as a premium offering to SAP NetWeaver BW. Today’s BEx Analyzer and BEx Web Analyzer will remain as the base offering in the NetWeaver BW offering, and will continue to be shipped with NetWeaver. Feature extensions for BEx Analyzer and BEx Web Analyzer will be limited. BEx Analyzer 3.5 and 7.0 standard workbooks that do not contain VB coding can be upgraded to Pioneer. BEx 3.5 and 7.0 queries and query views can be consumed by Pioneer as long as the backend system has been technically upgraded to SAP NetWeaver BW 7.0. Voyager workspaces can be used in Pioneer.

BusinessObjects Explorer •

•

2009

BusinessObjects Explorer is an innovative search and explore tool that allows users to search within the content of Information Spaces (a collection data source objects, such as Universe objects, sharing a contextual meaning) managed by BusinessObjects Enterprise. Information Spaces are retrieved by using search keywords and appear in search results ranked in order of relevance. Benefits of BusinessObjects Explorer include self-service BI for knowledge workers, ability to answer investigative questions, ability to get fast facts, understand new data and further reduce IT and report author backlog.

© 2010 SAP AG. All rights reserved.

265

Unit 8: Perspectives

SAPBO

Ad-hoc Query and Reporting • • •

Web Intelligence is the flagship product for web-based ad-hoc query and reporting. The focus of Web Intelligence lies in the creation of light-weight reports in an ad hoc web environment based on BusinessObjects universes. At present, Ad-hoc Query and Reporting is not covered extensively by the SAP NetWeaver BW tools. WebI and BusinessObjects Explorer thus clearly extend the value of SAP NetWeaver BW by addressing business user needs for answering business questions in an agile and easy to use way.

Dashboards/Xcelsius •

•

Xcelsius will continue to be the tool of choice for the creation of single, standalone dashboards and as the visual content creation tool for the desktop or portal page. For the creation of composite dashboards that combine multiple BI content types, Xcelsius should be used in conjunction with BusinessObjects Dashboard Builder - for non-SAP NetWeaver customers or customers that have deployed the InfoView portal - ; or with SAP Composition Environment (Web Page Composer, Visual Composer) for those customers that have deployed the NetWeaver platform. Some of the enhancements for Xcelsius are: 1.

•

Integration with Pioneer. It will be possible to build Xcelsius dashboards seamlessly on Pioneer analyses (planned for 2010). 2. OLAP Selectors for SAP NetWeaver with hierarchy navigation (planned for 2010). 3. Improved data access to directly use BEx queries and query views with BI Consumer services just like the NetWeaver BW BEx tools do in SAP NetWeaver BW 7.0 (already available with SAP NetWeaver 7.01 SP 5 and Xcelsius 2008 SP2) Xcelsius is available as a premium offering to SAP NetWeaver BW. Connectivity works through "query as a web service" (QaaWS) based on the BusinessObjects Universe or Live Office or through SAP NetWeaver BW Connection which allows to access BW Query data directly. Beyond NetWeaver release 7.0 EhP1, only very limited enhancements to BEx Web Application Designer are planned. BEx Web Application Designer will remain in the NetWeaver offering as a base solution. SAP and BusinessObjects will provide a service-based offering to move from SAP NetWeaver BW to the BusinessObjects premium offering. Note: For more information about SAP Netweaver BW new features and directions, visit - https://www.sdn.sap.com/irj/sdn/nw-bi

266

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Perspectives (Optional)

Lesson Summary You should now be able to: • Describe the product integration roadmap for SAP BusinessObjects solutions. • Describe the product directions for SAP BusinessObjects BI solutions.

2009

© 2010 SAP AG. All rights reserved.

267

Unit Summary

SAPBO

Unit Summary You should now be able to: • Describe the product integration roadmap for SAP BusinessObjects solutions. • Describe the product directions for SAP BusinessObjects BI solutions.

268

© 2010 SAP AG. All rights reserved.

2009

Unit 9 Appendix Unit Overview In this Appendix you find additional exercises.

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

Manage different business scenarios

Unit Contents Lesson: Additional Exercises..................................................270 Exercise 12: Create a Crystal Report based on a BW Query with a Hierarchy Variable ..........................................................271 Exercise 13: Create Universe from SAP BW Query with Optional Variable.......................................................................277 Exercise 14: Create Universe from SAP BW Query with Hierarchy. 283 Exercise 15: Create a Report with Web Intelligence on Universe with Optional Variable............................................................289 Exercise 16: Create a Report with Web Intelligence on a Universe with Hierarchy. ....................................................................293 Exercise 17: Create a Live Office Document with a Filter. ............297 Exercise 18: Create a Live Office Document from a Web Intelligence Report. .......................................................................301 Exercise 19: Create Xcelsius Dashboard with Live Office ............307

2009

© 2010 SAP AG. All rights reserved.

269

Unit 9: Appendix

SAPBO

Lesson: Additional Exercises Lesson Overview This lesson provides additional exercises that can be used by the trainer / participants of the course.

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

Manage different business scenarios

Business Example This lesson provides additional exercises that can be used by the trainer / participants of the course.

Additional exercises

270

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 12: Create a Crystal Report based on a BW Query with a Hierarchy Variable Exercise Objectives After completing this exercise, you will be able to: • Create a Crystal Report with a SAP hierarchy variable.

Business Example You are a report designer and need to create a Crystal Report object using SAP BW hierarchies.

Task: Create a Crystal Report based on a BW query with a hierarchy variable. A hierarchy variable prompts for a specific hierarchy from a list of available hierarchies for that characteristic. 1.

Create a Crystal Report based on a BW query with a hierarchy variable. Base this report on the BW query, SAPBO Hierarchy Variable (technical name: T_SAPBO_Q08).

2.

Choose the SAPBO Hierarchy Variable query (technical name: T_SAPBO_Q08).

3.

Make sure that the field descriptions will be shown in the Field Explorer instead of the field names.

4.

Insert a group based on the Material parent-child relationship.

5.

Create a hierarchical grouping based on the Material parent-child relationship.

6.

Create a summary for the Sales Volume (EUR).

7.

Preview your report with different values for the hierarchy variable.

8.

Save the report to the BW and BusinessObjects Enterprise systems with the name GR## Hierarchy Variables. Note: In the case of an optional hierarchy variable and the user setting the prompt to Null, the underlying SAP BW query returns the non-hierarchical view of the actual characteristic.

2009

© 2010 SAP AG. All rights reserved.

271

Unit 9: Appendix

SAPBO

Solution 12: Create a Crystal Report based on a BW Query with a Hierarchy Variable Task: Create a Crystal Report based on a BW query with a hierarchy variable. A hierarchy variable prompts for a specific hierarchy from a list of available hierarchies for that characteristic. 1.

Create a Crystal Report based on a BW query with a hierarchy variable. Base this report on the BW query, SAPBO Hierarchy Variable (technical name: T_SAPBO_Q08). a)

From the Windows Desktop: Start → Programs → Crystal Reports 2008.

b)

Select the menu SAP → Settings.

c)

Select the check box Use MDX Driver with support for Multiple structures.

d)

Click OK.

e)

Select SAP →Create New Report from Query.

f)

Connect to the assigned BW training system using the credentials given to you by your instructor. Enter the assigned System, Client 800, User SAPBO-## and Password. Also select the desired language. Click OK.

2.

Choose the SAPBO Hierarchy Variable query (technical name: T_SAPBO_Q08). a)

Click the Find icon (binoculars) and search for the BW query SAPBO Hierarchy Variable, technical name,T_SAPBO_Q08

b)

Click OK.

Continued on next page

272

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

3.

4.

5.

Make sure that the field descriptions will be shown in the Field Explorer instead of the field names. a)

Change Crystal Reports Settings to: File → Options.

b)

Click the Database tab and choose the Option, Show Description.

c)

Click OK.

d)

Open the Field Explorer and look at the field descriptions: View → Field Explorer.

e)

Click the plus sign in front of Database fields.

f)

Click the plus sign in front of T_SAPBO1_T_SAPBO_Q08.

g)

Take a look at the field descriptions within the Field Explorer.

Insert a group based on the Material parent-child relationship. a)

Select the menu Insert → Group.

b)

Select the Node ID field from hierarchy. Material Node ID.

c)

Navigate to the Options tab.

d)

Select the Customize Group Name Field check box.

e)

Select from the existing field Medium Name as the description value of the hierarchy.

f)

Click OK.

Create a hierarchical grouping based on the Material parent-child relationship. a)

Select the menu Report → Hierarchical Grouping options.

b)

Select the Sort Data Hierarchy check box.

c)

Select the parent node ID field of the hierarchy. Material Parent Node ID.

d)

Define the Group Indent: 0.3 in.

e)

Click OK.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

273

Unit 9: Appendix

6.

7.

SAPBO

Create a summary for the Sales Volume (EUR). a)

Select the menu Insert → Summary.

b)

Select Sales Volume (EUR) value as the field to summarize.

c)

Select Sum as the calculation option.

d)

Select Group #1 for the summary location.

e)

Click OK.

f)

Move the summary to the Group Header #1. Expand the Summary field so that it will be large enough for the total Sales Volume. Select the Summary field and expand the field with left mouse.

g)

Hide the Group Footer #1 in the report design.

Preview your report with different values for the hierarchy variable. a)

Select the menu View → Print Preview.

b)

Based on the situation that the report contains a hierarchy variable you are prompted to select a hierarchy.

c)

Select a value for the prompt. Select Product Hierarchy for Material MARA.

d)

Click OK.

Figure 105: Report with hierarchy variable

Continued on next page

274

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

8.

Save the report to the BW and BusinessObjects Enterprise systems with the name GR## Hierarchy Variables. Note: In the case of an optional hierarchy variable and the user setting the prompt to Null, the underlying SAP BW query returns the non-hierarchical view of the actual characteristic. a)

2009

Select the folder SAPBO. Click the Save Report button in the SAP toolbar.

© 2010 SAP AG. All rights reserved.

275

Unit 9: Appendix

276

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 13: Create Universe from SAP BW Query with Optional Variable. Exercise Objectives After completing this exercise, you will be able to: • Create a connection between SAP NetWeaver BI and the BusinessObjects system. • Create a Universe from an SAP BW query with optional variable. • Describe the object structure in the Universe.

Business Example Before you begin universe creation from SAP BW system, you need to create a connection between SAP BW and the BusinessObjects System . The basic principles by building a Universe between the SAP BW and BusinessObjects is to generate the interface between both systems and to map the characteristic and key figures of SAP BW into a universe so that they can be used by BusinessObjects for reporting. In this example you will create the universe based on an SAP query with an optional variable.

Task: Create a Universe based on the BW Query, SAPBO Optional Query. This query has an optional variable. 1.

Launch the Universe Designer and logon with the following details: Field Name

Value

System

twdfXXXX

User name

SAPBO-##

Password

You password

Authentication

SAP

2.

Launch the Quick Design Wizard.

3.

Create a new connection using the following initial parameters, then proceed to the next step of the Quick Design Wizard.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

277

Unit 9: Appendix

4.

278

SAPBO

Field Name

Value

Connection Type

Secured

Connection Name

T_SAPQuery_Optional_Variable_Connection_##

Database Middleware Selection

SAP → SAP Business Warehouse, then select SAP Client

Define the BW login parameters using the parameters below (don’t forget to replace SID with your assigned BW server ID). Field Name

Value

User

SAPBO-##

Password

Assigned password

Client

800

Language

Desired language key

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp

System number

40

System ID

(assigned SAP BW system ID)

5.

Select the BW Query SAPBO optional variable, technical name T_SAPBO_Q03, then proceed to the last screen and select Finish.

6.

Enter the Universe name T_SAPBO_Optional_Variable_##. Complete the wizard steps until you see the completion message. Then review the created Universe.

7.

Save the Universe to the BusinessObjects Universes folder with the name T_SAPBO_Optional_Variable_##.

8.

Export the universe to the BusinessObjects repository folder webi universes.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Solution 13: Create Universe from SAP BW Query with Optional Variable. Task: Create a Universe based on the BW Query, SAPBO Optional Query. This query has an optional variable. 1.

Launch the Universe Designer and logon with the following details: Field Name

Value

System

twdfXXXX

User name

SAPBO-##

Password

You password

Authentication

SAP

a)

Select Start → Programs → Business Objects XI 3.1 → Business Objects Enterprise Client Tools → Designer. If you are already in the Designer, select File →New.

b) 2.

Launch the Quick Design Wizard. a)

3.

Enter the logon information above and click on OK.

Click on Begin.

Create a new connection using the following initial parameters, then proceed to the next step of the Quick Design Wizard. Field Name

Value

Connection Type

Secured

Connection Name

T_SAPQuery_Optional_Variable_Connection_##

Database Middleware Selection

SAP → SAP Business Warehouse, then select SAP Client

a)

Select the New button to create a new connection.

b)

Click on Next.

c)

Enter the parameters above.

d)

Click on Next.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

279

Unit 9: Appendix

4.

SAPBO

Define the BW login parameters using the parameters below (don’t forget to replace SID with your assigned BW server ID). Field Name

Value

User

SAPBO-##

Password

Assigned password

Client

800

Language

Desired language key

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp

System number

40

System ID

(assigned SAP BW system ID)

a) 5.

Enter the connection details above (remember to replace SID with your assigned BW system ID) then click Next.

Select the BW Query SAPBO optional variable, technical name T_SAPBO_Q03, then proceed to the last screen and select Finish. a)

Expand the node OLAP Cubes folder and find T_SAPBO1. Expand the folder for this InfoCube and find the BW Query, SAPBO optional variable (T_SAPBO_Q03).

b)

Select the query, SAPBO Optional Query. Press Next. Keep all the default settings on the next screen and presss Finish.

Continued on next page

280

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

6.

Enter the Universe name T_SAPBO_Optional_Variable_##. Complete the wizard steps until you see the completion message. Then review the created Universe. a)

On the Universe Parameters, Definition tab, In the field Enter the universe name enter T_SAPBO_Optional_Variable_##.

b)

Go to the Controls tab. Uncheck all the query limits settings.

c)

Press OK. Finish.

d)

Review the Universe by expanding the class and sub-class nodes to see the dimensions and measures. Note: Based on the fact that the underlying SAP BW query contains an optional variable, the Dimension object includes the List of value definition and in the filter area you receive a filter defined as optional. The reason for having two lists of value definitions is that the resulting prompt based on the SAP variable offers the key value and the value description and, therefore, there is the need to have two lists of value definitions. Based on the SAP variable definition, there is also a filter created in the OLAP Universe.

e)

Switch to the Filter view in the Universe. Click on the Filter object.

f)

Notice the in the Where statement, indicating the filter is optional. Note: The setting for the compulsory filter defines the behavior of the prompt during runtime when viewing or creating a report with Web intelligence. Apply on Universe: The filter is applied and offered to the user independent of the elements from the universe that are used. This means the optional variable is prompted for any query that is created based on the Universe. Apply on Class: The filter is only used when an object from the class of the filter is used.

g) 7.

Press OK.

Save the Universe to the BusinessObjects Universes folder with the name T_SAPBO_Optional_Variable_##. a)

Select File → Save As.

b)

Ensure the destination folder is set to BusinessObjects Universes, and ensure the universe name is set to T_SAPBO_Optional_Variable_##.unv, then press Save. Continued on next page

2009

© 2010 SAP AG. All rights reserved.

281

Unit 9: Appendix

8.

282

SAPBO

Export the universe to the BusinessObjects repository folder webi universes. a)

Select File → Export.

b)

Press the Browse button.

c)

Highlight the folder webi universes then press OK.

d)

Press OK to export the universe. The universe is now available for reporting.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 14: Create Universe from SAP BW Query with Hierarchy. Exercise Objectives After completing this exercise, you will be able to: • Create a connection between SAP NetWeaver BI and the BusinessObjects system. • Create a Universe from an SAP BW query with a hierarchy. • Describe the object structure in the Universe.

Business Example Before you begin universe creation from SAP BW system, you need to create a connection between SAP BW and the BusinessObjects System . The basic principles by building a Universe between the SAP BW and BusinessObjects is to generate the interface between both systems and to map the characteristic and key figures of SAP BW into a universe so that they can be used by BusinessObjects for reporting. In this example, you will connect to a BW Query with a hierarchy.

Task: Create a Universe based on the BW Query, SAPBO Optional Query. This query has an optional variable. 1.

Launch the Universe Designer and logon with the following details: Field Name

Value

System

twdf####

User name

SAPBO-##

Password

Assigned password

Authentication

SAP

2.

Launch the Quick Design Wizard.

3.

Create a new connection using the following initial parameters, then proceed to the next step of the Quick Design Wizard.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

283

Unit 9: Appendix

4.

284

SAPBO

Field Name

Value

Connection Type

Secured

Connection Name

T_SAPQuery_Hierarchy_Connection_##

Database Middleware Selection

SAP → SAP Business Warehouse, then select SAP Client

Define the BW login parameters using the parameters below (don’t forget to replace SID with your assigned BW server ID). Field Name

Value

User

SAPBO-##

Password

Your password

Client

800

Language

Desired language key

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp

System number

40

System ID

(assigned SAP BW system ID)

5.

Select the BW Query SAPBO simple hierarchy, technical name T_SAPBO_Q07, then proceed to the last screen and select Finish.

6.

Enter the Universe name T_SAPQuery_Hierarchy_Universe_##. Complete the wizard steps until you see the completion message. Then review the created Universe.

7.

Save the Universe to the BusinessObjects Universes folder with the name T_SAPQuery_Hierarchy_Universe_##.

8.

Export the universe to the BusinessObjects repository folder webi universes.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Solution 14: Create Universe from SAP BW Query with Hierarchy. Task: Create a Universe based on the BW Query, SAPBO Optional Query. This query has an optional variable. 1.

Launch the Universe Designer and logon with the following details: Field Name

Value

System

twdf####

User name

SAPBO-##

Password

Assigned password

Authentication

SAP

a)

Select Start → Programs → Business Objects XI 3.1 → Business Objects Enterprise Client Tools → Designer. If you are already in the Designer, select File→ New. (or press the New icon.)

b) 2.

Launch the Quick Design Wizard. a)

3.

Enter the logon information above and click on OK.

Click on Begin.

Create a new connection using the following initial parameters, then proceed to the next step of the Quick Design Wizard. Field Name

Value

Connection Type

Secured

Connection Name

T_SAPQuery_Hierarchy_Connection_##

Database Middleware Selection

SAP → SAP Business Warehouse, then select SAP Client

a)

Select the New button to create a new connection.

b)

Click on Next.

c)

Enter the parameters above.

d)

Click on Next. Continued on next page

2009

© 2010 SAP AG. All rights reserved.

285

Unit 9: Appendix

4.

SAPBO

Define the BW login parameters using the parameters below (don’t forget to replace SID with your assigned BW server ID). Field Name

Value

User

SAPBO-##

Password

Your password

Client

800

Language

Desired language key

Application Server

/H/tdcsaprouter.wdf.sap.corp /H/tdc00.wdf.sap.corp

System number

40

System ID

(assigned SAP BW system ID)

a) 5.

Enter the connection details above (remember to replace SID with your assigned BW system ID) then click Next.

Select the BW Query SAPBO simple hierarchy, technical name T_SAPBO_Q07, then proceed to the last screen and select Finish. a)

Expand the node OLAP Cubes folder and find T_SAPBO1. Expand the folder for this InfoCube and find the BW Query, SAPBO simple hierarchy (T_SAPBO_Q07).

b)

Select the query, SAPBO simple hierarchy. Press Next. Keep all the default settings on the next screen and press Finish.

Continued on next page

286

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

6.

Enter the Universe name T_SAPQuery_Hierarchy_Universe_##. Complete the wizard steps until you see the completion message. Then review the created Universe. a)

On the Universe Parameters, Definition tab, In the field Enter the universe name enter T_SAPQuery_Hierarchy_Universe_##.

b)

Go to the Controls tab. Uncheck all the query limits settings.

c)

Press OK. Finish.

d)

Review the Universe by expanding the class and sub-class nodes to see the dimensions and measures. Note: When a hierarchy is defined on a characteristic in the BW query, Designer creates one hierarchical structure in the universe, with a subclass for each level in the hierarchy. The structure depends on the current BW query definition. If a hierarchy is defined in the BW query, Designer creates this hierarchy structure in the universe.

e)

Switch to the Filter view in the Universe. Click on the Filter object.

f)

Designer creates subclasses for each hierarchical structure, each containing subclasses for the levels in that hierarchy. In the case where a characteristic is configured with a hierarchy, the dimension object in the universe is created with one dimension object per level.

g) 7.

8.

2009

Press OK.

Save the Universe to the BusinessObjects Universes folder with the name T_SAPQuery_Hierarchy_Universe_##. a)

Select File → Save As.

b)

Ensure the destination folder is set to BusinessObjects Universes, and ensure the universe name is set to T_SAPQuery_Hierarchy_Universe_##.unv, then press Save.

Export the universe to the BusinessObjects repository folder webi universes. a)

Select File → Export.

b)

Press the Browse button.

c)

Highlight the folder webi universes then press OK.

d)

Press OK to export the universe. The universe is now available for reporting.

© 2010 SAP AG. All rights reserved.

287

Unit 9: Appendix

288

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 15: Create a Report with Web Intelligence on Universe with Optional Variable. Exercise Objectives After completing this exercise, you will be able to: • To create a Web Intelligence report on a universe based on an SAP query with an optional variable.

Business Example Task: Task 1: Create a Web Intelligence Report from a Universe based on a query with an optional variable.

2009

1.

Login into Web Intelligence Rich Client using the details below.

2.

Select the universe you created in the previous task. It should be named T_SAPBO_Optional_Variable_##.

3.

Create a query with the dimensions L01 Sold-to party, L01 Materiall and the measure Sales Volume EUR Formatted Value (in that order) and execute it to view the results.

4.

Rename the Report Title to Sales Order Report.

5.

Rename the column heading L01 Sold to party to Customer.

6.

Rename the column heading L01 Material to Products.

7.

Save the report to the default folder with the name Sales Volume Report with Optional Prompt.

© 2010 SAP AG. All rights reserved.

289

Unit 9: Appendix

SAPBO

Solution 15: Create a Report with Web Intelligence on Universe with Optional Variable. Task: Task 1: Create a Web Intelligence Report from a Universe based on a query with an optional variable. 1.

Login into Web Intelligence Rich Client using the details below. a)

2.

Field Name

Value

System

twdfXXXX

User name

SAPBO-##

Password

Your password

Authentication

SAP

b)

Select Start → Programs → Business Objects XI 3.1 → Business Objects Enterprise Client Tools → Web Intelligence Rich Client.

c)

Enter the details provided above then press Log On.

Select the universe you created in the previous task. It should be named T_SAPBO_Optional_Variable_##. a)

Select New →Web Intelligence Document.

b)

Select your universe T_SAPBO_Optional_Variable_##.

Continued on next page

290

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

3.

Create a query with the dimensions L01 Sold-to party, L01 Materiall and the measure Sales Volume EUR Formatted Value (in that order) and execute it to view the results. a)

Expand the node Customer → Sold to Party and drag L01 Sold to Party into the Result Objects panel.

b)

Expand the node Material Class → Material02 and drag L01 Material into Result Objects panel to the right of L01 Sold to Party.

c)

Expand the node Key Figures and drag the measure Sales Volume EUR Formatted Value into the Result Objects panel to the right of L01 Material.

d)

Press Run Query. Do not select any values when prompted. Press Run Query. Note: An optional SAP variable now becomes an optional prompt in Web Intelligence. When left empty the optional prompt is removed from the actual WHERE clause that is sent to the underlying system. In the SAP BW case an empty optional variable could still result in the usage of a configured default value from the underlying SAP Variable or in the usage of a personalized variable value of the user.

4.

Rename the Report Title to Sales Order Report. a)

Press Edit Report. Double-click on the report title and enter the name Sales Volume Report with Optional Prompt then press Enter.

5.

Rename the column heading L01 Sold to party to Customer. a)

6.

Double-click on the L01 Sold to party cell and enter Customer, then press Enter.

Rename the column heading L01 Material to Products. a)

Double-click on the L01 Material cell and enter Products then press Enter.

b)

Press Run Query.

c)

Press Refresh Data. Select Becker Berlin and press > to move the selection to the right.

d)

Press Run Query. Only the details for the selected customer are displayed.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

291

Unit 9: Appendix

7.

SAPBO

Save the report to the default folder with the name Sales Volume Report with Optional Prompt. a)

292

Select File → Save As. Press Enterprise. Select SAP 2.0 CLNT800. Enter the description GR## Sales Order Report with Optional Prompt. Press Save. (Save as a Web Intelligence Report).

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 16: Create a Report with Web Intelligence on a Universe with Hierarchy. Exercise Objectives After completing this exercise, you will be able to: • To create a report using Web Intelligence that uses a Universe with a hierarchy.

Business Example Task: Task 1: Create a Web Intelligence Report from a Universe with a Hierarchy. 1.

Login into Web Intelligence Rich Client using the details below.

2.

Select the universe you created in the previous task. It should be named T_SAPQuery_Hierarchy_Universe_##.

3.

Create a query with the dimensions L01 Material, L02 Material L03 Material, L04 Material and the measure Sales Volume EUR (in that order). Note: When using hierarchies in Web Intelligence, the dimension objects can be used like any other dimension objects. Each level of the hierarchy is represented in the universe and can be used in the query.

2009

4.

Rename the Report Title to Sales Volume Report with Hierarchy.

5.

Save the report to the default folder with the name GR## Sales Volume Report with Hierarchy.wid.

6.

Create a new query with L00 Material and Sales Volume EUR. Drill down through all the levels.at query run time.

© 2010 SAP AG. All rights reserved.

293

Unit 9: Appendix

SAPBO

Solution 16: Create a Report with Web Intelligence on a Universe with Hierarchy. Task: Task 1: Create a Web Intelligence Report from a Universe with a Hierarchy. 1.

Login into Web Intelligence Rich Client using the details below. a)

2.

Field Name

Value

System

twdf####

User name

SAPBO-##

Password

Assigned password

Authentication

SAP

b)

Select Start → Programs → Business Objects XI 3.1 → Business Objects Enterprise Client Tools → Web Intelligence Rich Client.

c)

Enter the details provided above then press Log On.

d)

Select Document List. Then choose New→ Web Intelligence.

Select the universe you created in the previous task. It should be named T_SAPQuery_Hierarchy_Universe_##. a)

Select your universe T_SAPQuery_Hierarchy_Universe_## in the list and press OK.

Continued on next page

294

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

3.

Create a query with the dimensions L01 Material, L02 Material L03 Material, L04 Material and the measure Sales Volume EUR (in that order). Note: When using hierarchies in Web Intelligence, the dimension objects can be used like any other dimension objects. Each level of the hierarchy is represented in the universe and can be used in the query. a)

Select the needed levels from the hierarchy and include them into the Result Objects. Expand the node Material Class → Material02 → Material03 and drag L01 Material into Result Objects panel. Repeat for L02 Material, L03 Material, and L04 Material.

4.

b)

Expand the node Key Figures and drag the measure Sales Volume EUR into the Result Objects panel next to L04 Material.

c)

Click on Run Query.

Rename the Report Title to Sales Volume Report with Hierarchy. a)

5.

Double-click on the report title and enter the name Sales Volume Report with Hierarchy then press Enter.

Save the report to the default folder with the name GR## Sales Volume Report with Hierarchy.wid. a)

Select File → Save and in the File Name field enter Sales Order Report with Hierarchy and press Save.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

295

Unit 9: Appendix

6.

SAPBO

Create a new query with L00 Material and Sales Volume EUR. Drill down through all the levels.at query run time. a)

Select Edit Query→ Add Query. Hint: A Level 00 item, Not Assigned, includes elements that have not been assigned to the Hierarchy structure.

b)

Expand the node Material Class → Material02 → Material03 and drag L00 Material into Result Objects panel.

c)

Expand the node Key Figures and drag the measure Sales Volume EUR into the Result Objects panel next to L00 Material.

d)

Select Run Query.

e)

From the context menu of Report 1 tab at the bottom, select Document Properties.

f)

Ensure the property Use Query Drill is activated.

g)

From the context menu of Report 1 tab at the bottom, select Drill. Notice that Material now has an underline indicating Drill capability is activated.

296

h)

Double click on level L00 Material. Notice you now see level L01 Material. Drill down through all Material levels.

i)

Save the report select File→ Save As. Press Enterprise. Select SAP→ 2.0→clnt800. Enter the Description GR## Sales Volume Report with Hierarchy Drilldown.wid. Save as a Web Intelligences Report.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 17: Create a Live Office Document with a Filter. Exercise Objectives After completing this exercise, you will be able to: • Create a New Crystal Report. • Create a new Live Office document from this new Crystal Report. • Insert a filter for your new Live Office document.

Business Example Task: In this exercise you need to create a Live Office Document from a Crystal Report.

2009

1.

Create a new Crystal Report, Sales Volume by Region, based on the BW Query T_SAPBO_01 with the following fields: Region Key, Region Name, Sales Volume EUR formatted Value. Save you report to the Enterprise folder folder SAP→2.0→CLNT800 with the name GR## CR Sales by Region.

2.

Create a new Live Office Document in Microsoft Excel based on your Crystal Report, GR## CR Sales by Region. set a filter for Region Key between DE/02 and FR/91. Save to the local default folder as GR## Live Office Document with Region Filter and publish to the Enterprise folder SAP→2.0→CLNT800 with the same file name.

© 2010 SAP AG. All rights reserved.

297

Unit 9: Appendix

SAPBO

Solution 17: Create a Live Office Document with a Filter. Task: In this exercise you need to create a Live Office Document from a Crystal Report. 1.

Create a new Crystal Report, Sales Volume by Region, based on the BW Query T_SAPBO_01 with the following fields: Region Key, Region Name, Sales Volume EUR formatted Value. Save you report to the Enterprise folder folder SAP→2.0→CLNT800 with the name GR## CR Sales by Region. a)

Start Crystal Reports Designer. Start > Programs > Crystal Reports 2008 > Crystal Reports 2008.

b)

Select the menu SAP →Settings.

c)

Select the check box Use MDX Driver with support for Multiple Structures. Press OK.

d)

Select the menu SAP → Create New Report from a Query.

e)

Select the SAP server from the SAP Logon.

f)

Enter the needed details: Client, User, Password, and Language. Press OK.

g)

Select the BW Query T_SAPBO_Q01. Press OK.

h)

Select the following fields for your report from the Field Explorer. Region Key Region Name Sales Volume EUR formatted

i)

Preview your report.

j)

Save the report to BusinessObjects Enterprise. File→ Save As→ Enterprise, folder SAP→2.0→CLNT800. Name the report GR## CR Sales by Region.

k) 2.

Exit Crystal Reports.

Create a new Live Office Document in Microsoft Excel based on your Crystal Report, GR## CR Sales by Region. set a filter for Region Key between DE/02 and FR/91. Save to the local default folder as GR## Live Office Document with Region Filter and publish to the Enterprise folder SAP→2.0→CLNT800 with the same file name. a)

Start MicroSoft Excel and select Live Office. Continued on next page

298

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Start→Programs →Microsoft Office→ Excel. Select from the menu Live Office→Options. Select the Enterprise button. b)

Verify the option User Specified Logon Criteria is checked. System

twdfXXXX

Web Service URL

http://twdfXXXX:8080/dswsbobje/services/Session

Verify the information in the Web Service URL and System fields to ensure that the application is pointing to the correct Central Management System (CMS). c)

Select the authentication method as SAP from the drop-down list. Press Log On and OK.

d)

Select the menu LiveOffice → Insert → Crystal Reports content.

e)

Search for the previously created report from BusinessObjects Enterprise. At the top, in the first search field, choose All fields from the drop down list. In the second search field enter the name of your Crystal Report GR## CR Sales by Region. Press Search. Alternately, follow the path SAP→ 2.0 →CLNT800. Find your new Crystal Report. Press Next.

f)

Press Switch to Fields. Click on each field to add them to the list of selected fields. Press Next.

g)

The Set Filters page will only appear if you have inserted your data as fields. You can apply filters to all available fields in your Crystal Reports documents to restrict the data in your report. Press Add Filter. Filter on Region Key. Choose from the drop down list of operator, is between: DE/02 and FR/91. Press Next. View your report.

h)

Modify the filter. Select Live Office→ Modify Object→ filter setings → modify. Remove the filter values that begin with FR. Press OK.

i)

View your report. Publish your report.

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

299

Unit 9: Appendix

SAPBO

LiveOffice → Publish to BusinessObjects Enterprise → Save to BusinessObjects Enterprise. SAP 2.0 →CLNT800. Enter the Description GR## Live Office Document with Region Filter. Press Save.

300

j)

Select the menu LiveOffice → Properties for All Objects. Select the Crystal Reports object. Select the Refresh tab. Here you can define how the report will be refreshed with data.

k)

Press OK.

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 18: Create a Live Office Document from a Web Intelligence Report. Exercise Objectives After completing this exercise, you will be able to: • To create Live Office Document from a Web Intelligence Report .

Business Example Your business requirements indicate that you need to create a new Live Office document. You must base this new Live Office document on an existing Web Intelligence Report.

Task 1: In this exercise you need to create a Live Office Document from a Crystal Report. We will follow the Wizard mentioned in table below step by step. Wizard page

Task to Do

Choose Document

Browse available reports.

Choose Data

Select the Crystal Reports parts or fields you want to use to create your Live Office object.

Set Filters

Select filters to apply to data that you insert as fields in your Live Office documents.

Summary

Type the name of your Live Office object and Verify its path in the repository before inserting it into your document.

1.

Start the Live Office Application and insert the Web Intelligence Report. Enter with the BusinessObjects Enterprise credentials

2.

Verify the information in the Web Service URL and System fields User Name

~800/SAPBO-##

Password

Enter your password.

Web Service URL

http://twdfXXXX:8080/dswsbobje/services/session

System

twdfXXXX:6400 / Assigned System

Authentication

Enterprise Continued on next page

2009

© 2010 SAP AG. All rights reserved.

301

Unit 9: Appendix

SAPBO

Task 2: Once you able to logon to Live office successfully now its turn to go through the Wizard step by step. 1.

The first screen is Choose Document. Choose the following document. Expand The folder Public Public → SAP → 2.0 → CLNT800 → GR## Sales Order Report with Optional Prompt. This is one of the Web Intelligence reports that you created in Unit 4.

2.

The next page of the Live Office Insert Wizard is the Choose Data page. Select the entire query.

3.

Insert Wizard: Summary The "Summary" page is the last screen in the "Live Office Insert Wizard" before the current object is inserted into your Microsoft Office application

302

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Solution 18: Create a Live Office Document from a Web Intelligence Report. Task 1: In this exercise you need to create a Live Office Document from a Crystal Report. We will follow the Wizard mentioned in table below step by step. Wizard page

Task to Do

Choose Document

Browse available reports.

Choose Data

Select the Crystal Reports parts or fields you want to use to create your Live Office object.

Set Filters

Select filters to apply to data that you insert as fields in your Live Office documents.

Summary

Type the name of your Live Office object and Verify its path in the repository before inserting it into your document.

1.

Start the Live Office Application and insert the Web Intelligence Report. Enter with the BusinessObjects Enterprise credentials a)

Click Start → Programs → Microsoft Office

b)

Click LiveOffice, Click Insert and then select Web Intelligence Content.

c)

Enter your BusinessObjects Enterprise logon credentials in the fields of User name and Password

d)

It will prompt for Business object credentials, User name ~800/SAPBO-## and password. Note: For Live Office we must use Enterprise Authentication (not SAP). For this reason, an alias has been created for you on the BusinessObjects Enterprise system. The alias user is prefixed with ~800/SAPBO-##. For example, W4B~800/SAPBP-##.

2.

Verify the information in the Web Service URL and System fields

Continued on next page

2009

© 2010 SAP AG. All rights reserved.

303

Unit 9: Appendix

SAPBO

User Name

~800/SAPBO-##

Password

Enter your password.

Web Service URL

http://twdfXXXX:8080/dswsbobje/services/session

System

twdfXXXX:6400 / Assigned System

Authentication

Enterprise

a)

Verify the information in the Web Service URL and System fields to ensure that the application is pointing to the correct Central Management System (CMS).

b)

Select an authentication method as Enterprise from the drop-down list, click Log On and then click OK.

c)

Also make sure that you are able to see Validation succeeded as a message at the bottom of the Screen

Task 2: Once you able to logon to Live office successfully now its turn to go through the Wizard step by step. 1.

The first screen is Choose Document. Choose the following document. Expand The folder Public Public → SAP → 2.0 → CLNT800 → GR## Sales Order Report with Optional Prompt. This is one of the Web Intelligence reports that you created in Unit 4.

2.

a)

Click on choose document - In the left-hand pane of the "Choose Document" page, navigate to and double-click the folder that contains the report you want to use. Using the buttons above the left-hand pane, you can switch between Folder and Category views for easy navigating.

b)

Expand The folder Public Public → SAP → 2.0 → CLNT800 → GR## Sales Volume per Country

c)

In the right-hand pane of the "Choose Document" page, select the report you want to use, GR## Sales Order Report with Optional Prompt, and click Next.

The next page of the Live Office Insert Wizard is the Choose Data page. Select the entire query.

Continued on next page

304

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

3.

a)

Place your cursor on the results of the query. Double click to select the entire query.

b)

Press Next.

Insert Wizard: Summary The "Summary" page is the last screen in the "Live Office Insert Wizard" before the current object is inserted into your Microsoft Office application

2009

a)

From the "Summary" page, name your Live Office object and verify its path in the BusinessObjects repository

b)

Click Finish to insert your Live Office object into your Microsoft Office document.

c)

A progress bar appears as your Live Office object is inserted in your Microsoft Office document.

d)

You now have a report in Microsoft office Excel which is created from a Intelligence Report.

e)

Save your document. File→ Save As. Enter the Description: GR## Live Office Sales Orders from Web Intelligence Report.

f)

Publish your document to BusinessObjects Enterprise. Live Office→ Publish to BusinessObjects Enterprise→ Save As New to BusinessObjects Enterprise. Select from the folder list Public →SAP→ 2.0→ CLNT800. Enter the Description: GR## Live Office Sales Orders from Web Intelligence Report. .

© 2010 SAP AG. All rights reserved.

305

Unit 9: Appendix

306

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Exercise 19: Create Xcelsius Dashboard with Live Office Exercise Objectives After completing this exercise, you will be able to: • Create Xcelsius Dashboard with Live Office.

Business Example You need to create an Xcelsius dashboard with Live Office.

Task: Create Xcelsius Dashboard with Live Office. 1.

Logon to Xcelsius. Import the Live Office document you created previously in the Live Office unit, GR## Live Office Sales by Country. Add a Live Office Connection that is refreshed on load.

2.

Create Xcelsius Dashboard. Create a pie chart that shows Sales order amount per Country. Save as GR## Xcelsius Sales by Country to your local My Documents folder. Export to BusinessObjects Enterprise, to the folder SAP→2.0→CLNT800

2009

© 2010 SAP AG. All rights reserved.

307

Unit 9: Appendix

SAPBO

Solution 19: Create Xcelsius Dashboard with Live Office Task: Create Xcelsius Dashboard with Live Office. 1.

Logon to Xcelsius. Import the Live Office document you created previously in the Live Office unit, GR## Live Office Sales by Country. Add a Live Office Connection that is refreshed on load. a)

Start Xcelsius (Start → Programs → Xcelsius → Xcelsius 2008. When prompted about enabling Live Office, respond Yes.

b)

c)

Authenticate Business Objects Enterprise system: System

twdfXXXX

User

SAPBO-##

Password

Enter your password

Authentication

SAP

Select Data →Import from Enterprise, select GR## Live Office Sales by Country.. Note: The Live Office document will be displayed in the spreadsheet inside the Xcelsius.

d)

Select the menu Data → Connections.

e)

Press Add. Select Live Office Connections.

f)

Select the newly created connection.

g)

Replace the web server entry with your webserver name. For example: http://twdf####:8080/dswsbobje/services/Session

h)

Select the Usage tab. Set the property Refresh on Load. Close Data Manager.

2.

Create Xcelsius Dashboard. Create a pie chart that shows Sales order amount per Country.

Continued on next page

308

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Lesson: Additional Exercises

Save as GR## Xcelsius Sales by Country to your local My Documents folder. Export to BusinessObjects Enterprise, to the folder SAP→2.0→CLNT800 a)

Drag and drop a pie chart component onto the Xcelsius canvas.

b)

Double-click the pie chart to open the properties. Select the icon next to the Data Values. Mark the complete range in for the values. (B1 to B8) Press OK.

c)

Select the icon next to the Data Labels. Mark the complete range in for the labels. (A1 to A8) Press OK.

d)

Select Preview.

e)

Select the menu File → Export → BusinessObjects Platform. Select a folder on your BusinessObjects Enterprise system. Enter the file name GR## Xcelsius Sales by Country XCELSIUS. Note: When exporting to the BusinessObjects Platform the actual Xcelsius document is being stored on the platform. When selecting the menu File → Save as the design of the Xcelsius document is being stored to BusinessObjects Enterprise.

f)

Press Save. View the Xcelsius dashboard in InfoView using the SAP authentication. Start →Programs→ Business Objects Enterprise XI 3.1 →Business Objects Enterprise Client tools →Business Objects Enterprise Java Infoview.

2009

© 2010 SAP AG. All rights reserved.

309

Unit 9: Appendix

SAPBO

Lesson Summary You should now be able to: • Manage different business scenarios

310

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Unit Summary

Unit Summary You should now be able to: • Manage different business scenarios

2009

© 2010 SAP AG. All rights reserved.

311

Unit Summary

312

SAPBO

© 2010 SAP AG. All rights reserved.

2009

SAPBO

Course Summary

Course Summary You should now be able to: • • •

2009

Introduction of the reporting options with SAP Business Objects alongside with the product roadmap. Participants should learn about the strategic development of SAP Netweaver BW in combination with SAP Business Objects The tools in SAP Business Objects are introduced and participants gain practical experiences based on hands-on sessions

© 2010 SAP AG. All rights reserved.

313

Course Summary

314

SAPBO

© 2010 SAP AG. All rights reserved.

2009

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.

2009

© 2010 SAP AG. All rights reserved.

315