BO100 - Integration for SAP BW.pdf

SAP BusinessObjects XI Integration for SAP NetWeaver BW SAP NetWeaver

Date Training Center Instructors Education Website

Participant Handbook Course Version: 93 Revision A Course Duration: 5 Day(s) Material Number: 50099222

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

This Material is for the Exclusive Use of Registered Students in SAP Virtual Classroom Deliveries

BO100

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.

g20103222107


Copyright

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

BO100

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


2009


About This Handbook

Course Overview .............................................................................. ix Course Goals................................................................................. ix Course Objectives ........................................................................... ix

Unit 1: BusinessObjects XI Integration for SAP Solutions ...........................1 What's in SAP BusinessObjects Software................................................. 2 BusinessObjects Enterprise Architecture Overview...................................... 9 Components ................................................................................. 20

Unit 2: SAP Connectivity Overview ...................................................... 33 The SAP Business Objects Tools......................................................... 34 SAP connectivity options .................................................................. 39 Supported SAP specific features ......................................................... 50

Unit 3: Installation of BusinessObjects XI Integration for SAP Solutions....... 63 Prerequisites................................................................................ 65 Installing BusinessObjects XI Integration for SAP Solutions.......................... 80 Distributed Deployments .................................................................. 86 Client-side Components .................................................................. 89 Post-Installation steps ..................................................................... 92 Publishing Integration for Crystal Reports ............................................. 105

Unit 4: Query and Adhoc Reporting with Web Intelligence on BW ..............137 Query and Adhoc Reporting.............................................................. 138 Web Intelligence and SAP Business Explorer ......................................... 144

Unit 5: OLAP Universes on SAP BW - Part 1..........................................173 BW Variables .............................................................................. 175 Mandatory variables....................................................................... 190 SAP variables with default values ....................................................... 200 SAP variables with delegated search ................................................... 209 Hierarchies in OLAP Universes .......................................................... 218 Hierarchies and hierarchy node variables in OLAP Universes ...................... 220 Simple keydate scenarios ................................................................ 234 Keydate variable dependencies ......................................................... 239

2009


v


Contents

BO100

Unit 6: OLAP Universes on SAP BW - Part 2..........................................247 Multi-structure queries in OLAP Universes............................................. 248 Smart measures and calculations in OLAP Universes ............................... 261 Updating OLAP Universes................................................................ 279

Unit 7: Crystal Reports and SAP ERP ..................................................303 Crystal Reports Overview ................................................................ 304 Crystal Reports and SAP tables ......................................................... 308 Crystal Reports and ABAP Functions................................................... 319 Crystal Reports and Classic InfoSets ................................................... 330 Crystal Reports and InfoSets Queries .................................................. 335

Unit 8: Crystal Reports and SAP BW - Part 1 .........................................345 SAP BW Metadata in Crystal Reports .................................................. 346 Crystal Reports with simple SAP BW queries ......................................... 355 Crystal Reports against advanced SAP BW queries.................................. 364

Unit 9: Crystal Reports and SAP BW - Part 2 .........................................381 Crystal Reports with SAP BW queries with hierarchies .............................. 382 Crystal Reports against SAP BW cubes................................................ 394 Crystal Reports and keydate variables ................................................. 398 SAP variable personalization............................................................. 406

Unit 10: Voyager with SAP BW ...........................................................415 Creating connections to SAP BW with Voyager ....................................... 416 SAP BW metadata in Voyager ........................................................... 431 SAP Variables with Voyager.............................................................. 439

Unit 11: Xcelsius with Live Office........................................................461 Xcelsius with Live Office .................................................................. 462 Creating an Xcelsius dashboard with Live Office...................................... 481

Unit 12: Xcelsius with Query as a Web Service (QaaWS) on BW ................497 Query as a Web Service .................................................................. 498 Xcelsius and Query as a Web Service.................................................. 508

Unit 13: SAP Security Integration and Creating Publications.....................541 Server side trust and impersonation.................................................... 543 SAP server configuration ................................................................. 549

vi


2009


Contents

Contents

SAP BusinessObjects Enterprise Configuration ....................................... 559 Creating a publication ..................................................................... 596

Unit 14: Integrating with SAP Enterprise Portal ......................................623 Integrating BusinessObjects Enterprise content into SAP Enterprise Portal using iViews ................................................................................... 625 Portal System landscape for BusinessObjects Enterprise ........................... 632 Creating BusinessObjects Enterprise content iViews................................. 649 Creating portal pages ..................................................................... 662 Creating portal worksets .................................................................. 676 Creating portal roles....................................................................... 683 BusinessObjects Enterprise Repository Manager..................................... 700

Unit 15: Troubleshooting the SAP Connectivity .....................................745 Troubleshooting Connectivity ............................................................ 746 Performance................................................................................ 756

2009


vii


BO100

Contents

viii


2009


BO100

SAP BusinessObjects XI Integration for SAP NetWeaver BW is an instructor-led training that provides detailed knowledge on the implementation of SAP BusinessObjects Enterprise XI 3.1 tools within SAP NetWeaver 7.0. You will learn learn how to install and configure the SAP BusinessObjects Enterprise software and create your first report, ad-hoc analysis, or dashboard on top of your SAP data. In addition, you will learn how the metadata from the underlying SAP system is mapped to Crystal Reports, Web Intelligence, Query as a Web Service, Live Office, Voyager, and Xcelsius.

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

SAP Netweaver BW customers, system administrators, project team members, system integrators, and technical consultants

Course Prerequisites Required Knowledge •

Fundamental knowledge in SAP NetWeaver BW 7.0 and BusinessObjects Enterprise client tools and servers.

Course Goals This course will prepare you to: •

This is a 5-day instructor-led classroom training that provides you with hands-on experience in setting up BusinessObject XI Integration for SAP Solutions and your BusinessObjects environment to report from SAP data. You will also get a comprehensive overview of the SAP Business Objects solutions for SAP Netweaver BW.

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

2009

Describe the integration of SAP BusinessObjects software with SAP NetWeaver BW


ix


Course Overview

BO100

• •

Install and configure BusinessObjects XI Integration for SAP Solutions Describe how the SAP NetWeaver BW concepts are being mapped to SAP BusinessObjects software Describe Crystal Reports and SAP, Voyager and SAP Connectivity, Web Intelligence and OLAP Universes, Publication with SAP Security, Xcelsius, Live Office, Query as a Web Services, SAP Enterprise Portal, and troubleshooting best practices

•

x


2009


Course Overview

BusinessObjects XI Integration for SAP Solutions Unit Overview This unit introduces you the concepts of Business Intelligence and the various roles that are important in your organization when you implement your business intelligence strategies with SAP BusinessObjects software. Later this unit provides you with an overview of the components that are part of BusinessObjects XI Integration for SAP Solutions.

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 the architecture and technical requirements for BusinessObjects Enterprise front-end tools Describe the BusinessObjects Enterprise service groups and servers Describe the different components of the BusinessObjects XI Integration for SAP solutions

Unit Contents Lesson: What's in SAP BusinessObjects Software ............................... 2 Lesson: BusinessObjects Enterprise Architecture Overview .................... 9 Lesson: Components................................................................ 20

2009


1


Unit 1

BO100

Lesson: What's in SAP BusinessObjects Software Lesson Overview This lesson provides a high-level overview of the different client tools and applications in SAP BusinessObjects software.

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: • • • •

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

Benefits of Business Intelligence

2


2009


Unit 1: BusinessObjects XI Integration for SAP Solutions

Lesson: What’s in SAP BusinessObjects Software

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

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


3


BO100

BO100

Figure 1: BusinessObjects Enterprise Client Tools

Role

Tools

Description

A web-based interface that end users access to view, BusinessObjects En- schedule, and keep track of published reports. terprise 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 Query as a Web Service provides new and easy ways to Web Service 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


2009




Role

Tools

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

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.

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

Designer

2009

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


5


BO100

Role

Administrator

6

BO100

Tools

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

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 enables you to move BI resources from one system to another system without affecting


2009




Role

Data Manager

2009

Tools

Description 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 column- level 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 row- and 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


7


BO100

BO100

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

8


2009



Lesson: BusinessObjects Enterprise Architecture Overview

Lesson: BusinessObjects Enterprise Architecture Overview Lesson Overview In this lesson, you will review the architecture and components of BusinessObjects Enterprise.


Explain the architecture and technical requirements for 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

2009


9


BO100

BO100

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.

Figure 2: 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:

10


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 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

2009


11


BO100

BO100

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.

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. Business Objects web services provide a Java API accessed by rich clients in the user interaction tier, such as Live Office and Crystal Reports.

12


2009




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 Business Objects 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: •

Central Management Server (CMS)

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. •

2009

Server Intelligence Agent


13


BO100

BO100

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. •

Output File Repository Server

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.

14


2009




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.

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.

2009


15


BO100

BO100

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.

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

16


2009




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. 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:

2009

• • • • •

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

•

Search Server


17


BO100

BO100

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.

18


2009




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

2009


19


BO100

BO100

Lesson: Components Lesson Overview This lesson provides you with an overview of the components that are part of the BusinessObjects XI Integration for SAP solutions.

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

Describe the different components of the 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. 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 Information Warehouse (BW) and SAP ERP data and share it with users across the enterprise. In addition, SAP Authentication enables Single Sign On between your SAP system and BusinessObjects Enterprise

20


2009



Lesson: Components

What’s in the BusinessObjects XI Integration for SAP solutions BusinessObjects XI Integration for SAP solutions consists of several connectivity and authentication enhancements to the core BusinessObjects suite of products. • • • • •

Crystal Reports allows you to design reports off your SAP data Web Intelligence enables you to create queries and analyze the SAP data Voyager allows you to analyze and navigate around the multi-dimensional data that is stored in SAP Business Information Warehouse Xcelcius models and dashboards can be created using the SAP data BusinessObjects Enterprise provides the framework for managing, scheduling, and distributing your SAP content over the Web. The SAP security model can also be leveraged to allow users to access the content using the existing SAP user accounts.

BusinessObjects XI Integration for SAP Solutions also includes several add-on components to further integrate the Business Objects reporting technologies with existing SAP systems. The add-on components include

Data Access BusinessObjects XI Integration for SAP Solutions provides connectivity to your SAP data through six database drivers—the BW Query driver, the InfoSet driver, the DSO driver, the MDX driver, the Open SQL driver and the OLAP BAPI driver:

Reporting off BW queries, InfoSets, Operational Data Stores, 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 off 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 ERP 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.

2009


21


BO100

BO100

The SAP BW MDX Query driver introduces new flexibility when reporting off BW cubes and queries. By writing reports with the MDX Query driver, you gain direct access to BW cubes, display attributes, and multiple structures. Note: One advantage of these drivers is that they allow business users to report off 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.

Reporting off 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 easyto 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 using OLAP BAPI driver The BW Voyager has been specially designed to integrate the Online Analytical Processing (OLAP) viewing capabilities of Voyager and Crystal Reports with your SAP Business Information Warehouse (BW) system. Users can connect to multidimensional BW Info Cubes and generate reports that incorporate complex data analysis.

Crystal Reports SAP Toolbar Integrated within Crystal Reports, the SAP Tools toolbar facilitates tasks associated with reporting off 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.

22


2009



Lesson: Components

SAP Authentication This component allows you to 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).

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 Web.

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

2009


23


BO100

BO100

BW Content Administration Workbench This feature allows you to manage report publishing from with BW. You can identify roles in your 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.

Knowledge Management Console (KMC) 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.

24


2009



Lesson: Components

Figure 3: Architecture diagram for BusinessObjects XI Integration for SAP Solutions

2009


25


BO100

BO100

Lesson Summary You should now be able to: • Describe the different components of the BusinessObjects XI Integration for SAP solutions

26


2009



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 the architecture and technical requirements for BusinessObjects Enterprise front-end tools • Describe the BusinessObjects Enterprise service groups and servers • Describe the different components of the BusinessObjects XI Integration for SAP solutions

2009


27


BO100

Unit Summary

28


2009


BO100

Test Your Knowledge

Test Your Knowledge 1.

Which BusinessObjects product uses the OLAP BAPI driver to connect to the SAP BW InfoCube? Choose the correct answer(s).

□ □ □ □ 2.

A B C D

Crystal Reports using standard connection Web Intelligence Rich Client using a Local Data Source Web Intelligence Rich Client using OLAP Universe Crystal Reports using SAP Toolbar

Which of the following SAP data sources can be accessed using the Open SQL driver? Choose the correct answer(s).

□ □ □ □ □ 3.

A B C D E

Transparent Tables Pool tables Cluster Tables Views All of the above

Which BusinessObjects product displays the SAP toolbar after BusinessObjects XI Integration for SAP Solutions is installed? Choose the correct answer(s).

□ □ □ □

2009

A B C D

Universe Designer Web Intelligence Rich Client Xcelcius Crystal Reports


29


BO100

BO100

Answers 1.

Which BusinessObjects product uses the OLAP BAPI driver to connect to the SAP BW InfoCube? Answer: C Correct answer is C.

2.

Which of the following SAP data sources can be accessed using the Open SQL driver? Answer: E All of the above can be accessed using the OpenSQL driver.

3.

Which BusinessObjects product displays the SAP toolbar after BusinessObjects XI Integration for SAP Solutions is installed? Answer: D Crystal Reports

30


2009


Test Your Knowledge



Unit Summary

31


2009


BO100

Unit Summary

32


2009


BO100

SAP Connectivity Overview Unit Overview SAP BusinessObjects tools expand the scope of BW by providing a wide range of tools and applications. SAP BusinessObjects tools support businesses by optimizing the connection between people and information. This unit provides you with an overview of the various data connectivity options to SAP BW and SAP ERP for the SAP BusinessObjects products.

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

•

List the various BusinessObjects reporting tools Explain when each tool should be used and when it should be avoided Describe the SAP data sources connectivity options available to the following BusinessObjects BI consumers: Crystal Reports, Web Intelligence, Voyager, Analytics, Query as a Web Service, Live Office, and Xcelsius List the SAP specific features per client tool

Unit Contents Lesson: The SAP Business Objects Tools ....................................... 34 Lesson: SAP connectivity options ................................................. 39 Lesson: Supported SAP specific features ........................................ 50

2009


33


Unit 2

BO100

Lesson: The SAP Business Objects Tools Lesson Overview In this lesson you will learn the different tools in the SAP BusinessObjects Enterprise and understand when each tool should be used.


List the various BusinessObjects reporting tools Explain when each tool should be used and when it should be avoided

Business Example You are planning to implement a BusinessObjects Enterprise solution integrated with SAP NetWeaver BW and would like classify and position the various BusinessObjects reporting tools in your environment where business users require full information autonomy.

The SAP Business Objects Tools BusinessObjects Platform suite components for reporting include: • • • • • •

Crystal Reports Desktop Intelligence Web Intelligence Voyager Xcelsius Live Office Note: Desktop Intelligence functionality is being replaced by Web Intelligence and Web Intelligence Rich Client

These tools are suited for various user audiences and business solutions

34


2009


Unit 2: SAP Connectivity Overview

2009

Lesson: The SAP Business Objects Tools

Tool

Best Audience

Best Business Solution

Crystal Reports

Most business users

Static reporting, highly formatted reports, pixel perfect presentation, mass printing and distribution, relational databases, enterprise applications and data warehouse sourced data

Web Intelligence

Most casual business users Powerful query and ease of use adhoc reporting, self serve template based report creation and interactive analysis, enterprise distribution, with mostly relational and OLAP sourced data

Voyager

Analyst and business user

Multi dimensional analysis of information

Xcelsius

Most business users

Dashboard and presentation quality visualizations

Live Office

Analyst and casual users

Seamless MS Office integration with data retrieval, presentation and distribution


35


BO100

BO100

Figure 4: Baseline use cases and product mapping

As business users roles change during their business life from day to day, the type and appetite for information consumption also changes. A single user for this reason may consume data from different tools sets depending on their requirements. A cost center manager may consume a highly formatted report with exceptions on cost items that exceeded budget for the month as a Crystal Report exported to Excel attached in email. A brand manager may require advertising spend by campaign linked to sales for the month to determine marketing cost effectiveness using Web Intelligence to combine data from two different sub-systems; marketing and sales. A product manager may want to analyze product category margins by location across market for this year and last year using Voyager. A North American sales director is presenting to the board performance based sales by region and product in the form of a dashboard and PowerPoint presentation using Xcelsius and Live Office. The examples above demonstrate that there is a different solution based on user business needs. Query and adhoc reporting is best satisfied by Web Intelligence. Note: The component products will evolve and change as future components merge and are added within the BusinessObjects and SAP BW product platforms. For example Voyager will transform into Pioneer becoming a more powerful multi dimensional solution for power analysts.

36


2009



Lesson: The SAP Business Objects Tools

Figure 5: Product mapping with solution capabilities

2009


37


BO100

BO100

Lesson Summary You should now be able to: • List the various BusinessObjects reporting tools • Explain when each tool should be used and when it should be avoided

38


2009



Lesson: SAP connectivity options

Lesson: SAP connectivity options Lesson Overview In this lesson, you will learn about the SAP data source connectivity options available from the BusinessObjects product.


Describe the SAP data sources connectivity options available to the following BusinessObjects BI consumers: Crystal Reports, Web Intelligence, Voyager, Analytics, Query as a Web Service, Live Office, and Xcelsius

Business Example You are planning to implement a BusinessObjects Enterprise solution integrated with SAP NetWeaver BW and would like identify the connectivity options available to your business environment.

SAP connectivity for Crystal Reports The SAP data sources available from Crystal Reports are:

2009


39


BO100

BO100

Figure 6: SAP connectivity for Crystal Reports

•

SAP ERP

•

– Tables and cluster (Open SQL). – ABAP functions. – Classic InfoSets – SAP queries and InfoSet queries. SAP BW – – – –

Tables and cluster (Open SQL). ABAP Functions. Direct access to ODS tables (without the need for an SAP BW query). BW queries and BW cubes.

SAP connectivity for Web Intelligence The SAP data sources available from Web Intelligence are:

40


2009




Figure 7: SAP connectivity for Web Intelligence

•

SAP BW – –

BW queries and BW cubes (OLAP Universe via MDX). Direct access to BW fact, dimension and DSO tables (Relational Universe via SQL).^ Note: ^ New feature in BusinessObjects Enterprise XI 3.1 FixPack 1.1 via Data Federator XI 3.1 Netweaver BI connector.

SAP connectivity for Voyager The SAP data sources available from Voyager are:

2009


41


BO100

BO100

Figure 8: SAP connectivity for Voyager

•

SAP BW –

BW queries and BW cubes via MDX.

SAP connectivity for Analytics The SAP data sources available from Analytics are:

42


2009




Figure 9: SAP connectivity for Analytics

•

SAP BW – –

BW queries and BW cubes (OLAP Universe via MDX). Direct access to BW fact, dimension and DSO tables (Relational Universe via SQL).^

SAP connectivity for Query as a Web Service (QaaWS) The SAP data sources available from Query as a Web Service are:

2009


43


BO100

BO100

Figure 10: SAP connectivity for Query as a Web Service (QaaWS)

•

SAP BW – –

BW queries and BW cubes (OLAP Universe via MDX). Direct access to BW fact, dimension and DSO tables (Relational Universe via SQL). Note: Query as a Web Service results are retrieved from the BW server on demand. Query results always are up to date and conversely, the query results cannot be pre-scheduled for faster response time viewing. The query definition is saved in the BusinessObjects Enterprise repository, though query data is saved with the definition.

44


2009




SAP connectivity for Live Office Live Office is able to leverage data from the following documents and service providers: • • •

Crystal Reports. Web Intelligence. Universe Query (i.e OLAP and Relational Universes) Note: Crystal Reports and Web Intelligence documents can be optionally scheduled prior to view time usage in Live Office. Scheduling at an appropriate frequency allows query results to be pre-cached for faster loading at view time, especially for very large queries or for data that is not changing rapidly after being pre-cached; reporting load can be balanced across BOE servers, query load can be balanced on the BW server. Universe Query is similar to QaaWS, data query results are always up to date and run on demand. The Universe Query definition is embedded within the Live Office document.

Therefore, the SAP data sources available from Live Office are:

2009


45


BO100

BO100

Figure 11: SAP connectivity for Live Office

•

SAP ERP

•

– Tables and cluster (Open SQL). – ABAP functions. – Classic InfoSets – SAP queries and InfoSet queries. SAP BW – – – – –

Tables and cluster (Open SQL). ABAP Functions. Direct access to ODS tables (without the need for an SAP BW query). Direct access to BW fact, dimension and DSO tables (Relational Universe via SQL).^ BW queries and BW cubes.

SAP connectivity for Xcelsius Xcelsius is able to leverage data from the following documents and service providers:

46


2009




Figure 12: SAP connectivity for Xcelsius

• •

2009

Live Office. Web Services.


47


BO100

BO100

Therefore, the SAP data sources available from Xcelsius are: •

SAP ERP

•

– Tables and cluster (Open SQL). – ABAP functions. – Classic InfoSets – SAP queries and InfoSet queries. SAP BW – – – – –

Tables and cluster (Open SQL). ABAP Functions. Direct access to ODS tables (without the need for an SAP BW query). Direct access to BW fact, dimension and DSO tables (Relational Universe via SQL).^ BW queries and BW cubes. Note: As discussed, in Live Office, Crystal Reports and Web Intelligence documents can be optionally scheduled prior to view time usage . Scheduling at an appropriate frequency allows query results to be pre-cached for faster loading at view time, especially for very large queries or for data that is not changing rapidly after being pre-cached; reporting load can be balanced across BOE servers, query load can be balanced on the BW server. Live Office Universe Query is similar to QaaWS, data query results are always up to date and run on demand. QaaWS query definition can be designed on the fly and saved in the BusinessObjects Enterprise repository (no query data is saved with the definition) whilst Universe Query definition is imbedded within the Live Office document.

48


2009




Lesson Summary You should now be able to: • Describe the SAP data sources connectivity options available to the following BusinessObjects BI consumers: Crystal Reports, Web Intelligence, Voyager, Analytics, Query as a Web Service, Live Office, and Xcelsius

2009


49


BO100

BO100

Lesson: Supported SAP specific features Lesson Overview [Enter a brief overview of the lesson.]


List the SAP specific features per client tool

Business Example You are planning to implement a BusinessObjects Enterprise solution integrated with SAP NetWeaver BW and would like to list the supported features per each BusinessObjects client tool in your environment.

Supported features per client tool Crystal Reports BW Query Driver

Crystal OLAP Reports Universe BW MDX Driver

XI R2

XI XI XI R2 3.x R2

XI 3.x

NA

x

x

Voyager

Additional Comment

InfoProvider Support for InfoCube Direct Access

50

x

x


x

2009



Lesson: Supported SAP specific features

Crystal Reports BW Query Driver


Voyager

XI R2

XI XI XI R2 3.x R2

XI 3.x

Support for MultiCube Direct Access

NA

x

x

x

x

x

Support for RemoteCube Direct Access

NA

x

x

x

x

x

Support for BW Queries

x

x

x

x

x

x

Key

x

x

x

x

x

x

Short Descriptions

x

x

x

x

x

x

Medium Descriptions

NA

x

x

x

x

x

Long Descriptions

NA

x

x

x

x

x

Support for single Hierarchies

x

x

x

x

x

x

Support for single Hierarchies

x

x

x

x

x

x

Additional Comment

Characteristic Values

Query Features

2009


51


BO100

52

BO100



XI R2

XI XI XI R2 3.x R2

XI 3.x

Support for Free Characteristics

NA

x

x

x

x

x

Support for Calculated Keyfigures

x

x

x

x

x

x

Support for Restricted Keyfigures

x

x

x

x

x

x

Support for Currencies

x

x

x

_

x

x

Support for Units

x

x

x

_

x

x

Support for Multiple Structures

NA

x

x

x

x

x

Support for Formulas

x

x

x

x

x

x

Support for Selections

x

x

x

x

x

x

Support for Filter

x

x

x

x

x

x

Support for Display Attributes

x

x

x

x

x

_


Voyager

Additional Comment

2009






Voyager

XI R2

XI XI XI R2 3.x R2

XI 3.x

Support for Conditions

NA

NA NA NA

NA

NA

Support for Exceptions

NA

NA NA NA

NA

NA

Support for Navigational Attributes

x

x

x

x

x

x

Support for compounded characteristics

x

x

x

x

x

x

Support for unbalanced Hierarchies

x

x

x

x

x

x

Support for ragged Hierarchies

x

x

x

x

x

x

x

x

x

x

x

x

Additional Comment

Reason: Not supported/relevant to SAP BAPI interface. Possible Data Federator workaround: create a filter on the measure objects

Data Types Support for type "CHAR" (Characteristics)

2009


53


BO100

BO100



XI R2

XI XI XI R2 3.x R2

XI 3.x

x

x

x

_

x

x

_ Support for type "DATS" (Characteristics)

_

_

_

x

_

Support for type "TIMS" (Characteristics)

_

_

_

_

_

_

Support for type "Date" (Keyfigures)

x

x

x

_

_

x

Support for type "Time" (Keyfigures)

x

x

x

_

_

x

User Input

x

x

x

x

x

x

Authorization

x

x

x

x

x

x

Replacement Path

x

x

x

x

x

x

Support for type "NUMC" (Characteristics)

Voyager

Additional Comment

If not supported, then Characteristics are returned as STRING value If not supported, then Characteristics are returned as STRING value

SAP Variable Processing Type

54


2009






Voyager

XI R2

XI XI XI R2 3.x R2

XI 3.x

SAP Exit / Custom Exit

x

x

x

x

x

x

PreCalculated Value Set

x

x

x

x

x

x

Support for Optional vs Mandatory Variables

x

x

x

_

x

x

Support for Variable dependencies

_

x

x

_

_

x

Support for Keydate dependencies

x

_

x

Lim- x ited

x

Support for Default Values

x

x

x

_

x

x

Support for Personalized Values

x

x

x

_

_

_

Additional Comment

General features for Variables

SAP Variables - Variable Type

2009


55


BO100

56

BO100



Voyager

XI R2

XI XI XI R2 3.x R2

XI 3.x

Single Value

x

x

x

x

x

x

Multiple Single Value

x

x

x

x

x

x

Range Value

x

x

x

x

x

x

Complex Selection

x

x

x

Lim- Lim- x ited ited (x1) (x1)

Formula Variable

x

x

x

x

x

x

Hierarchy Variable

x

x

x

x

x

x

Hierarchy Node Variable

x

x

x

x

x

x

Text Variable NA

NA NA NA

NA

NA

Keydate Variable

x

_

x

x

x

x

Currency Variable

x

x

x

x

x

x

Hierarchy Version Variable

NA

NA NA NA

NA

NA


Additional Comment

x1 = Variables are turned into a single range value parameter

2009




Lesson Summary You should now be able to: • List the SAP specific features per client tool

2009


57


BO100

BO100

Unit Summary You should now be able to: • List the various BusinessObjects reporting tools • Explain when each tool should be used and when it should be avoided • Describe the SAP data sources connectivity options available to the following BusinessObjects BI consumers: Crystal Reports, Web Intelligence, Voyager, Analytics, Query as a Web Service, Live Office, and Xcelsius • List the SAP specific features per client tool

58


2009


Unit Summary

Test Your Knowledge


Help desk billing reports in PDF format need to be e-mailed each month to each cost center. The various cost centers' departments also need to be able to view these invoices online historically when needed. The report layout is a fairly fixed format and with transactions by grouped cost center and help desk service area. Which SAP BusinessObjects reporting tool would be the most appropriate to use? Choose the correct answer(s).

□ □ □ □

2009

A B C D

Web Intelligence Crystal Reports Voyager and/or SAP Business Explorer (BEx) Xcelsius


59


BO100

BO100

Answers 1.

Help desk billing reports in PDF format need to be e-mailed each month to each cost center. The various cost centers' departments also need to be able to view these invoices online historically when needed. The report layout is a fairly fixed format and with transactions by grouped cost center and help desk service area. Which SAP BusinessObjects reporting tool would be the most appropriate to use? Answer: B Crystal Reports - high quality fixed design contracted to BI consultant. Report bursting, PDF exporting and scheduled destinations possible.

60


2009


Test Your Knowledge



Unit Summary

61


2009


BO100

Unit Summary

62


2009


BO100

Installation of BusinessObjects XI Integration for SAP Solutions Unit Overview This unit provides you with the steps involved to install BusinessObjects XI Integration for SAP Solutions.

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

2009

Explain the technical prerequisites for BusinessObjects XI Integration for SAP Solutions Install BusinessObjects XI Integration for SAP Solutions Evaluate distributed deployment considerations Describe distributed scenarios and list the needed components Evaluate client side deployment considerations Describe client-side scenarios and list the needed components Configure the SAP authentication Configure global options for the SAP Authentication Import SAP users and roles Describe the publishing process Configure the BW Publisher service Create RFC destination Create a BusinessObjects Enterprise server definition Configure the SAP source parameters Configure the HTTP handler Configure the BusinessObjects Enterprise security for publishing


63


Unit 3

BO100

Unit Contents Lesson: Prerequisites ............................................................... 65 Procedure: To verify the patch level of the SAP server .................... 67 Procedure: To verify the transports ........................................... 69 Procedure: To verify the profile parameters.................................. 72 Procedure: To export the SAP Enterprise Portal certificate................ 74 Lesson: Installing BusinessObjects XI Integration for SAP Solutions ........ 80 Procedure: To install BusinessObjects XI Integration for SAP Solutions 81 Lesson: Distributed Deployments ................................................. 86 Lesson: Client-side Components .................................................. 89 Lesson: Post-Installation steps .................................................... 92 Procedure: To enable the SAP authentication............................... 93 Procedure: To configure the SAP authentication options ................. 95 Procedure: To import SAP roles to BusinessObjects Enterprise ......... 98 Exercise 1: Logging onto the systems........................................ 99 Lesson: Publishing Integration for Crystal Reports............................. 105 Procedure: To configure the BW Publisher service ........................ 110 Procedure: To create a new RFC destination .............................. 112 Procedure: To create a new BusinessObjects Enterprise server definition ......................................................................... 115 Procedure: To set the SAP source parameters............................. 122 Procedure: To configure the SAP HTTP request handler ................. 125 Procedure: To configure the rights in the Content Administration Workbench ...................................................................... 129 Procedure: To configure the rights in the Central Management Console 130

64


2009


Unit 3: Installation of BusinessObjects XI Integration for SAP Solutions

Lesson: Prerequisites

Lesson: Prerequisites Lesson Overview This lesson provides you with a checklist before you start the installation of BusinessObjects XI Integration for SAP Solutions.


Explain the technical prerequisites for BusinessObjects XI Integration for SAP Solutions

Business Example Before you install BusinessObjects XI Integration for SAP Solutions, you need to ensure the technical prerequisites and provide a checklist of things that will have impact on the installation of BusinessObjects XI Integration for SAP Solutions.

SAP GUI The SAP GUI is required for using the BusinessObjects XI Integration for SAP Solutions. The required version and the required patch level are listed in the list of supported platforms for the BusinessObjects Integration for SAP Solutions. When installing the SAP GUI you need to choose the following components: • • •

SAP GUI BW Add-On BI Add-On

SAP Java Connector The SAP Java Connector is required for the SAP authentication and for the SAP specific features in InfoView. The SAP Java Connector can be downloaded for free from SAP’s service marketplace http://service.sap.com.

2009


65


BO100

BO100

The following files need to be copied to the BusinessObjects Enterprise server: •

•

sapjco.jar needs to be copied to the shared library path of the application server. In the case of a default Tomcat deployment the path would be C:\Program Files\Business Objects\Tomcat55\shared\lib. librfc32.dll and sapjcorfc.dll need to be copied to the Windows\system32 directory. Note: In case the SAP GUI has been installed, the librfc32.dll doesn’t need to be copied. Note: If you are planning to integrate with an SAP BI 7 system, your SAP Java Connector must be version 2.1.6 at a minimum because SAP BI 7 allows passwords that are longer than 8 characters and this requires at a minimum the version 2.1.6 from the SAP JavaConnector.

SAP server patch level The SAP server side patch level needs to match the minimum requirements for BusinessObjects XI Integration for SAP Solutions.

66


2009




To verify the patch level of the SAP server 1.

Log onto the SAP Server.

2.

Select the menu System → Status.

Figure 13: System Status

3.

Click Component Information.

Continued on next page

2009


67


BO100

BO100

Figure 14: Component Information

Note: The patch level is displayed per component.

SAP transports BusinessObjects XI Integration for SAP Solutions includes transports as part of the product. These transports include functionality especially designed for the integration with SAP. The following is a list of functionality that requires SAP transports: • • • • • • • • •

Open SQL connectivity InfoSet connectivity BW MDX Driver connectivity BW ODS connectivity Row-level Security Definition editor Cluster Definition editor SAP authentication Content Administration Workbench BW Query parameter personalization Note: There are two different sets of the transports: Unicode compatible transports and ANSI transports. If the BASIS system is 6.20 or later, the Unicode compatible transports are recommended. If the BASIS system is earlier than 6.20, the ANSI transports are recommended.

68


2009




To verify the transports 1.


2.

Start transaction STMS (Transport Management System).

3.

Select the menu Overview → Imports (F5)..

4.

Double-click the system ID.

Figure 15: Import Queue

Note: The screen shows all imports for the SAP system. 5.

Double-click on one request number to receive the details.


2009


69


BO100

BO100

Figure 16: Display Object List

6.

Select the menu Goto → Transport Logs.

Figure 17: Transport Logs

70


2009




SAP single-sign-on To be able to use single-sign-on together with the BusinessObjects Enterprise system requires two main settings to be configured on the SAP side: 1. 2.

Profile parameters. Trust between SAP Enterprise Portal and SAP BW or SAP ERP.

Profile parameters Before you can enable ticket based single-sign-on between SAP and BusinessObjects Enterprise, you must set up your SAP system to accept and create logon tickets. This involves setting two related profile parameters on your SAP server: • •

login/accept_sso2_ticket login/create_sso2_ticket

Profile parameter

Value

Comment

login/create_sso2_ticket

1 or 2

Use the value 1 if the server possesses a public-key certificate signed by the SAP CA. Use the value 2 if the certificate is self-signed. If you are not sure, then use the value 2.

login/accept_sso2_ticket

1

Use the value 1 so that the system will also accept logon tickets.

Note: These settings require a restart of the SAP system.

2009


71


BO100

BO100

To verify the profile parameters 1.


2.

Start the profile maintenance with transaction RZ10.

Figure 18: Profile maintenance

3.

Select the instance profile for the SAP server.

4.

Select Extended maintenance.

5.

Click Display.


72


2009




Figure 19: Display Profile

6.

Verify the settings for the profile parameters.

Configure trust for the SAP Enterprise Portal This step involves exporting an SAP Enterprise Portal certificate and importing it to the SAP server (SAP BW or SAP ERP) so that these two systems establish a trusted relationship.

2009


73


BO100

BO100

To export the SAP Enterprise Portal certificate 1.

Log onto the SAP Enterprise Portal.

2.

Navigate to System Administration → System Configuration.

Figure 20: System Configuration

3.

Click Keystore Administration.


74


2009




Figure 21: Keystore Administration

4.

Click Download verify.der File.

5.

Save the file locally.

6.

Unzip the file.

7.

Log onto the SAP server (SAP BW or SAP ERP).

8.

Start transaction STRUSTSSO2 (Trust Manager).


2009


75


BO100

BO100

Figure 22: Trust Manager

9.

Select the menu Certificate → Import.


76


2009




Figure 23: Import Certificate

10. Enter the path to the unzipped file into File path and click Enter.

2009


77


BO100

BO100

BusinessObjects Enterprise server side requirements Before installing BusinessObjects XI Integration for SAP Solutions, these are the prerequisites for the BusinessObjects Enterprise server: •

The file saplogon.ini needs to be installed on machines with data access components. You can add the full path to the saplogon.ini file to the SAPLOGON_INI_FILE environment variable. Note: In case the SAP GUI has been installed the saplogon.ini file is installed on the client machine.

•

In case load balanced logon will be part of the deployment, the following entry must appear in the services file (found in %windir%\system32\drivers\etc\) on any BusinessObjects Enterprise machines running a CMS or data processing server component (for example, Crystal Reports Job Server): sapms [SAP System ID] [SAP tcp port number]/tcp Replace the SAP system ID with the system ID of the SAP system, and replace tcp port number with the port number of the message server that BusinessObjects Enterprise will log on to (for example, sapmsTB6 3600/tcp). Ensure also that a blank line follows the entry. This standard setting allows BusinessObjects Enterprise to log onto SAP with load balancing.

78


2009




Lesson Summary You should now be able to: • Explain the technical prerequisites for BusinessObjects XI Integration for SAP Solutions

2009


79


BO100

BO100

Lesson: Installing BusinessObjects XI Integration for SAP Solutions Lesson Overview In this lesson, you will learn about the installation procedure and configuration steps required for BusinessObjects XI Integration for SAP Solutions.


Install BusinessObjects XI Integration for SAP Solutions

Business Example You are the system administrator and need to install BusinessObjects XI Integration for SAP Solutions.

80


2009



Lesson: Installing BusinessObjects XI Integration for SAP Solutions

To install BusinessObjects XI Integration for SAP Solutions 1.

Double-click the setup.exe.

2.

Select the language and click OK. Click Next to continue. Note: The selected language is the language for the setup process – it is not the language for the product itself.

3.

Select the option I accept the License Agreement. Click Next.

4.

Enter the Full Name and organization.

5.

Enter the Product ID (license keycode) and click Next.

6.

Select the list of required languages for BusinessObjects XI Integration for SAP Solutions. Click Next.

7.

Select Custom and click Next.

8.

Select the necessary components and click Next.


2009


81


BO100

BO100

Figure 24: Components

Note: The above shows all components that are available for the installation. 9.

Enter the CMS Name and make sure the port number is correct. Enter the password for the Administrator account and click Next.

Figure 25: CMS Logon Information

Note: The reason for this CMS logon is that the SAP specific features for InfoView need to be implemented in the system database. 10. Complete the parameters for the BW Publisher and click Next.


82


2009




Figure 26: BW Publisher

Parameter Name

Description

Program ID Enter a name for the BW Report Publishing Service. This program ID identifies the service. The Program ID can take any value, but must be 64 characters or fewer, and may not contain spaces. The Program ID is case-sensitive. Gateway Host

Enter the fully qualified name of your SAP server. If you are using an SAP cluster environment, enter the name of the central instance here. Example: /H/tdcsaprouter.wdf.sap.corp/H/tdc00.wdf.sap.corp

Gateway Service

Enter the port number that the Gateway host is listening on. For example, type sapgw##, where ## represents the instance number of your SAP Gateway. If you don’t know how to get the Gateway Service, you just need to connect on the SAP NetWeaver BW server using SAP GUI and run the transaction SMGW. You then should see a column like TP NAME and the value is the Gateway Service. Continued on next page

2009


83


BO100

BO100

11. Determine how to deploy the web application. Select the check box Yes, automatically deploy the web application and click Next.

Figure 27: Deploying Web Application

12. Click Next to begin installation. The installation routine will start. As a verification step after the installation has finished you should see the SAP authentication as part of the available authentication options for SAP BusinessObjects InfoView.

84


2009




Lesson Summary You should now be able to: • Install BusinessObjects XI Integration for SAP Solutions

2009


85


BO100

BO100

Lesson: Distributed Deployments Lesson Overview In this lesson, you will learn about considerations for a distributed deployment of BusinessObjects XI Integration for SAP Solutions.


Evaluate distributed deployment considerations Describe distributed scenarios and list the needed components

Business Example You are a system designer and need to evaluate server-side deployment considerations.

Distributed deployment considerations In case of a distributed deployment of BusinessObjects Enterprise, the listed BusinessObjects XI Integration for SAP Solutions component needs to be installed on the appropriate machines. If you select a default server installation of BusinessObjects XI Integration for SAP Solutions, the setup program detects which elements of BusinessObjects Enterprise are present, and installs BusinessObjects XI Integration for SAP Solutions for SAP components.

Server-side components Component

BusinessObjects Enterprise service

Data access components (Crystal Reports)

Crystal Reports Processing Server Crystal Reports Job Server Report Application Server

Data access components (OLAP MDS Server BAPI) Web Intelligence Job Server

86


2009



Lesson: Distributed Deployments

Component

BusinessObjects Enterprise service Web Intelligence Processing Server Connection Server

BW Publisher service

Crystal Reports Processing Server Crystal Reports Job Server Report Application Server All machines that have the Business Objects Enterprise SDK installed

SAP authentication

Central Management Server (CMS) All machines that have the Business Objects Enterprise SDK installed

2009


87


BO100

BO100

Lesson Summary You should now be able to: • Evaluate distributed deployment considerations • Describe distributed scenarios and list the needed components

88


2009



Lesson: Client-side Components

Lesson: Client-side Components Lesson Overview In this lesson, you will learn about considerations for client side components of BusinessObjects XI Integration for SAP Solutions. After completing this lesson, you will be able to:


Evaluate client side deployment considerations Describe client-side scenarios and list the needed components

Business Example You are a system designer and need to evaluate client-side deployment considerations.

Client-side components The following table shows the components of BusinessObjects XI Integration for SAP Solutions which should be considered for the installation of clients like Crystal Reports Designer, Universe Designer, and Live Office. Client Crystal Reports

Components Data access components for SAP ERP Data access components for SAP BW SAP authentication SAP BW toolbar

Universe Design

2009

Data Access components for SAP BW (OLAP BAPI)


89


BO100

Client

BO100

Components SAP authentication

Live Office

Live Office retrieves the list of available authentications via web services and therefore the SAP authentication needs to be installed and deployed on the application server hosting the web services

Query as a Web Service (definition tool)

90

SAP authentication


2009



Lesson: Client-side Components

Lesson Summary You should now be able to: • Evaluate client side deployment considerations • Describe client-side scenarios and list the needed components

2009


91


BO100

BO100

Lesson: Post-Installation steps Lesson Overview [Enter a brief overview of the lesson.]

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

Configure the SAP authentication Configure global options for the SAP Authentication Import SAP users and roles

Business Example Upon installing the BusinessObjects XI Integration for SAP solutions, you need to ensure all the post-installation procedures are complete.

Enable SAP authentication The SAP authentication allows the administrator to leverage the SAP users and roles and it allows the end user to leverage functionality like single-sign-on with BusinessObjects Enterprise.

92


2009



Lesson: Post-Installation steps

To enable the SAP authentication 1.

Log onto the Central Management Console.

2.

Navigate to Authentication.

3.

Double-click SAP and select the Entitlement System tab.

Figure 28: SAP authentication

4.

Enter the system ID and client number from the SAP system.

5.

Enter Application Server name including SAP Router String Note: For example: ./H/tdcsaprouter.wdf.sap.corp/H/tdc00.wdf.sap.corp and System Number into the corresponding fields.

6.

2009

Enter SAP Usernam, Password, and Language.

7.

Click Update.

8.

The system ID and client number are combined and entered as an entry in the list of logical systems.


93


BO100

BO100

Configure global options for the SAP authentication The SAP authentication includes a number of options that you can customize when integrating BusinessObjects Enterprise with your SAP systems. For instance, you can enable/disable SAP authentication and/or configure BusinessObjects Enterprise to temporarily disable SAP authentication for SAP systems when they become unavailable.

94


2009




To configure the SAP authentication options 1.

Log onto the Central Management Console .

2.

Navigate to Authentication.

3.

Double-click SAP.

4.

Navigate to the Options tab.

Figure 29: SAP authentication options

•

Enable SAP Authentication Clear this check box if you want to disable SAP authentication completely. (To disable SAP authentication for specific SAP systems, select the system’s Disabled check box on the Entitlement Systems tab.)

•

Max failed entitlement system accesses and Keep entitlement system disabled [seconds]


2009


95


BO100

BO100

Use these fields together to configure how BusinessObjects Enterprise handles SAP entitlement systems that are temporarily unavailable. BusinessObjects Enterprise uses these settings to determine when to stop communicating with an SAP system that is unavailable, and when it should resume communication with that system. In the “Max failed entitlement system accesses” field, type the number of times that BusinessObjects Enterprise should re-attempt contacting an SAP system to fulfil authentication requests. Setting the value to -1 allows BusinessObjects Enterprise to attempt to contact the entitlement system an unlimited number of times before ceasing. Setting the value to 0 limits BusinessObjects Enterprise to making one attempt to contact the entitlement system. In the “Keep entitlement system disabled [seconds]” field, type the number of seconds that BusinessObjects Enterprise should wait before resuming attempts to authenticate users against the SAP system. For example, if you type 3 for “Max failed entitlement system accesses”, BusinessObjects Enterprise allows a maximum of 3 failed attempts to authenticate users against any particular SAP system; the fourth failed attempt results in BusinessObjects Enterprise ceasing its attempts to authenticate users against that system for the amount of time specified by “Keep entitlement system disabled [seconds].” •

Max concurrent connections per system Use this field to specify how many connections you want to keep open to your SAP system at the same time. For example, if you type 2 in this field, BusinessObjects Enterprise keeps 2 separate connections open to SAP.

•

Number of uses per connection Use this field to specify how many logons you want to allow to the SAP system per connection. For example, if you specified 2 for “Max concurrent connections per system” and 3 for “Number of uses per connection”, once there has been 3 uses on one connection, BusinessObjects Enterprise will close that connection and restart it. Note: Number of uses refers to actual transactions (or RFC calls) towards the SAP system.

•

Content folder root Continued on next page

96


2009




Use this field to specify where you want BusinessObjects Enterprise to begin replicating the BW folder structure in the CMC and InfoView. To change this value, you must change it both in the CMC and the Content Administration Workbench. This value is relevant for the publishing integration with Crystal Reports. •

Automatically import users Select this check box if you want BusinessObjects Enterprise to create user accounts and user folders for all role members when you actually import the roles. Clear the check box to have BusinessObjects Enterprise create user accounts and user folders dynamically, when users log on for the first time with valid SAP credentials.

•

Concurrent users / Named Users Use this option to specify if new user accounts are configured to use concurrent user licenses or named user licenses.

•

Default system In this list, select the SAP entitlement system that BusinessObjects Enterprise uses as the default system (that is, the system that is contacted to authenticate users who attempt to log on with SAP credentials but without specifying a particular SAP system).

5.

Define the SAP system you defined under the Entitlement System tab as the default system.

6.

Select the check box Automatically import users and click Update.

Import SAP users and roles By importing SAP roles into BusinessObjects Enterprise, you allow role members to log onto BusinessObjects Enterprise with their usual SAP credentials. In addition, single-sign-on is enabled so that SAP users can be logged onto BusinessObjects Enterprise automatically when they access reports from within the SAP GUI or an SAP Enterprise Portal. For each role that is imported BusinessObjects Enterprise generates a user group. Each group is named with the following naming convention: [SAP system ID]~[SAP client number]@[SAP role] You can view the new groups in the groups management area of the CMC. You can also use these groups to define object security within BusinessObjects Enterprise

2009


97


BO100

BO100

To import SAP roles to BusinessObjects Enterprise 1.

Navigate to the Role Import tab.

2.

Select the logical system for the SAP server.

3.

. Select the role(s) XXXXXXXX from the list of available roles, click Add > and then click Update.

Figure 30: Importing SAP roles

Note: After the import of the SAP roles has been completed, users that are members of these SAP roles are able to log on with their SAP account to BusinessObjects Enterprise. Note: The roles that have been imported to BusinessObjects Enterprise are now available for publishing Crystal Report objects.

98

4.

Close the above screen by click the X on the top right hand corner.

5.

Select Users and Groups from the drop down list. You should see the role you imported from SAP under Groups.


2009




Exercise 1: Logging onto the systems Exercise Objectives After completing this exercise, you will be able to: • Log into the SAP ERP/ECC system and change the user password • Log into the SAP BW system and change the user password • Log into SAP BusinessObjects software using SAP authentication • Log into SAP BusinessObjects software as administrators using Enterprise authentication

Business Example Before performing any task with the SAP systems and BusinessObjects servers, you need to be able to log into the software using the correct credentials.

Task 1: Adding SAP systems to your SAP Logon 1.

Launch SAP Logon from your computer.

Task 2: Logging into the SAP ERP/ECC system 1.

Use your SAP logon to access the provided SAP ECC/ERP system.

2.

Logging into the SAP ERP/ECC system using the following information: Field Name

Value

Client

800

User

Assigned User ID (For example: BO100-##)

Password

Assigned password (Default is INITIAL)

Language

EN

Task 3: Logging into the SAP BW system 1.

Use your SAP logon to access the provided SAP BW system.

2.

Logging into the SAP BW system using the following information:


2009


99


BO100

BO100

Field Name

Value

Client

900

User


Password


Language

EN

Task 4: Logging into the BusinessObjects Enterprise Java Infoview using SAP authentication 1.

Launch BusinessObjects Enterprise Java Infoview.

2.

Logging into InfoView using the following information: Field Name

Value

SAP System:

Assigned system ID

SAP Client:

900

User Name:

Assigned user ID (For example: BO100-##)

Password

Your new password from task 2

Authentication

SAP

Task 5: Logging into the BusinessObjects Enterprise Java Infoview as administrator using Enterprise authentication

100

1.

Launch BusinessObjects Enterprise Java Infoview.

2.


Value

User Name:

administrator

Password

Authentication

Enterprise


2009




Solution 1: Logging onto the systems Task 1: Adding SAP systems to your SAP Logon 1.

Launch SAP Logon from your computer. a)

Choose Start → Prorgrams → SAP Logon.

b)

Click New Item....

c)

Enter the assigned system in the Search for field and press Enter.

d)

Select the found SID and click Next.

e)

Ensure the group/server is set to SPACE and click Next.

f)

Set the SAProuter to /H/tdcsaprouter.wdf.sap.corp/H/.

g)

Click Finish.

Task 2: Logging into the SAP ERP/ECC system 1.

2.

Use your SAP logon to access the provided SAP ECC/ERP system. a)


b)

Double-click the assigned SID.

Logging into the SAP ERP/ECC system using the following information: Field Name

Value

Client

800

User


Password


Language

EN

a)

Logging into the SAP ERP/ECC system using the given information. Note: You will be prompted to change the password if this is your first attempt to log into the system.

b)

Enter your new password and remember this password for future reference.


2009


101


BO100

BO100

Task 3: Logging into the SAP BW system 1.

2.

Use your SAP logon to access the provided SAP BW system. a)


b)

Double-click the assigned SID.

Logging into the SAP BW system using the following information: Field Name

Value

Client

900

User


Password


Language

EN

a)

Logging into the SAP BW system using the given information. Note: You will be prompted to change the password if this is your first attempt to log into the system.

b)

Enter your new password and remember this password for future reference.

Task 4: Logging into the BusinessObjects Enterprise Java Infoview using SAP authentication 1.

Launch BusinessObjects Enterprise Java Infoview. a)

2.

Choose Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView..


Value

SAP System:

Assigned system ID

SAP Client:

900


102


2009




Field Name

Value

User Name:

Assigned user ID (For example: BO100-##)

Password

Your new password from task 2

Authentication

SAP

a)

Enter the given information in the login page and press Log On.

Task 5: Logging into the BusinessObjects Enterprise Java Infoview as administrator using Enterprise authentication 1.

Launch BusinessObjects Enterprise Java Infoview. a)

2.


Value

User Name:

administrator

Password

Authentication

Enterprise

a)

2009

Choose Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView..

Enter the given information in the login page and press Log On.


103


BO100

BO100

Lesson Summary You should now be able to: • Configure the SAP authentication • Configure global options for the SAP Authentication • Import SAP users and roles

104


2009



Lesson: Publishing Integration for Crystal Reports

Lesson: Publishing Integration for Crystal Reports Lesson Overview In this lesson, you will learn how to configure the publishing integration between BusinessObjects Enterprise and the SAP server.

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

Describe the publishing process Configure the BW Publisher service Create RFC destination Create a BusinessObjects Enterprise server definition Configure the SAP source parameters Configure the HTTP handler Configure the BusinessObjects Enterprise security for publishing

Business Example You are the system administrator and need to configure the publishing integration between BusinessObjects Enterprise and the SAP server.

Publishing integration with SAP NetWaver Business Warehouse The publishing process for Crystal Reports allows storing of Crystal Reports object into SAP NetWeaver Business Warehouse repository and then synchronizing them with your SAP BusinessObjects Enterprise system. This task can be done from within your SAP the Crystal Report designer tool or via the Content Administration Workbench as an administrative task. The main benefit of the publishing integration with SAP NetWaver Business Warehouse is the integration of the Crystal Reports objects into lifecycle management and translation integration with your SAP system. When stored in the SAP NetWeaver Business Warehouse system, the Crystal Report object becomes an object that can be transported between SAP systems. In addition, all translation-relevant objects are pushed into the translation-relevant tables as part of the publishing process.

2009


105


BO100

BO100

Describing the publishing process This image outlines the publishing process:

106


2009




Figure 31: Publishing process

•

•

When a user attempts to publish one or more Crystal reports, BW looks for a Remote Function Call (RFC) destination (of type TCP/IP) that is configured to connect to this BW Publisher. The TCP/IP destination provides SAP BW with the name and port number of the SAP Gateway that the BW Publisher is registered with. SAP BW then communicates over TCP/IP with the BW Publisher, and sends the following information across the network: –

•

The appropriate Crystal report file(s), with any required translated report strings. – A publishing command, if you are not using a local SAP Gateway. – The name of the appropriate Central Management Server (CMS). The SAP Gateway responds by executing the publishing command, thereby invoking the BW Publisher. The BW Publisher logs onto the specified CMS as the user, and checks to see if the user has the appropriate permissions in BusinessObjects Enterprise to publish reports. If the user’s rights are sufficient, the CMS allows the reports to be added to the system. Note: Before beginning to publish, you must configure SAP authentication in BusinessObjects Enterprise, define a folder structure for your content, and import SAP roles.

•

•

2009

When publishing a report from Crystal Reports the report is published with the configured preferred viewing language as master-language. Master-language in this case means that the string values from this report are stored in SAP translation tables with the configured language set as source language for the translation process. For each language selected in the content administration workbench for the BusinessObjects Enterprise system there will be an additional report file created with the language code (one digit letter) as the first digit of the technical report name.


107


BO100

BO100

Figure 32: Folder structure

When publishing, the top-level folder “SAP” and the folder underneath “3.0” (naming depends on the configuration in the Content Administration Workbench) are created automatically. Underneath the folder structure is created based on the values retrieved from SAP BW during the publishing process: • • • •

The Folder “SID” is replaced with the logical system name consisting of the SAP System ID and the SAP Client Number (for example, R37CLNT800). The role folder is created based on the technical name and description of the role that has been used to store the Crystal Report object on the SAP BW system. The report itself is saved to the actual role folder. For each language the report is made available in, one report object is created.

Configuring the BW Publish service The publisher service uses the configured settings that are stored in the registry. The path in the registry is: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\BW Publisher Service

108


2009




Figure 33: Registry

2009


109


BO100

BO100

To configure the BW Publisher service 1.

Click Start.

2.

Select Run.

3.

. Enter the command regedit.

4.

Click OK.

5.

. Navigate to the area in the registry for the BW Publisher service: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\BW Publisher Service

6.

Configure the values for the BW Publisher service. Enter the details based on the description shown in table below: Parameter Name

Description

Program ID Enter a name for the BW Report Publishing Service. This program ID identifies the service. The Program ID can take any value, but must be 64 characters or fewer, and may not contain spaces. The Program ID is case-sensitive. Gateway Host

Enter the fully qualified name of your SAP server. If you are using an SAP cluster environment, enter the name of the central instance here. Example: /H/tdcsaprouter.wdf.sap.corp/H/tdc00.wdf.sap.corp

Gateway Service

Enter the port number that the Gateway host is listening on. For example, type sapgw##, where ## represents the instance number of your SAP Gateway. If you don’t know how to get the Gateway Service, you just need to connect on the SAP NetWeaver BW server using SAP GUI and run the transaction SMGW. You then should see a column like TP NAME and the value is the Gateway Service.

7.

Close the registry editor.

8.

Start the Central Configuration Manager.

9.

Select the BW Publisher Service.


110


2009




10. Click Start. Note: To check that the BW Publisher has started on Windows ensure that the bwcepubsvc.exe and bcepub.exe processes are running on the machine

Creating an RFC destination To enable the BW Publisher, you must configure an RFC destination on your BW server to communicate with the BW Publisher service. If you have a BW cluster, configure the RFC destination on each server, using the central instance of BW as your Gateway Host in every case. If you wish to publish to multiple BusinessObjects Enterprise systems from BW, create a separate RFC destination for the BW Publisher service configured for each BusinessObjects Enterprise system. You must use unique Program IDs for each destination, but the same Gateway Host and Gateway service.

2009


111


BO100

BO100

To create a new RFC destination 1.

Log onto the SAP server.

2.

Start transaction SM59 (RFC Destinations).

Figure 34: RFC destination

3.

Click Create.


112


2009




Figure 35: RFC destination

4.

Enter a name for the RFC destination.

5.

Select T (Start External Program Using TCP/IP) as connection type.

6.

Enter a description for the RFC destination.

7.

Select Registered Server Program as Application Type.

8.

Enter the Program ID that was configured for the BW Publisher service as Program ID. Note: The Program ID name is case-sensitive.

9.

Enter 20 for the defined value in seconds


2009


113


BO100

BO100

10. Enter the Gateway Options: •

•

Gateway host: Type the name of your BW server. If you have a BW cluster, enter the name of the central instance of BW. You must use the same BW server name here that you specified when you configured the BW Publisher service. Gateway service: Type the port number that the Gateway host is listening on. For example, type sapgw##, where ## represents the instance number of your SAP Gateway.

11. Click Save.

Creating a BusinessObjects Enterprise server definition You must create a system definition within the Content Administration Workbench for each BusinessObjects Enterprise system to which you want to publish reports to. The BusinessObjects Enterprise system definition combines the previous configuration steps with additional settings like user roles and languages.

114


2009




To create a new BusinessObjects Enterprise server definition 1.


2.

Start transaction /CRYSTAL/RPTADMIN (Content Administration Workbench).

Figure 36: Content Administration Workbench

3.

Double-click Add new system.


2009


115


BO100

BO100

Figure 37: System tab

4.

Type a descriptive name in the Alias field. Note: Avoid using spaces or special characters.

5.

In the CMS name field, type the name of the machine that is running your BusinessObjects Enterprise Central Management Service. If you configured your CMS to listen on a port other than the default, type in the details in the following syntax: CMSNAME: PORT. For example: TWDFXXXX:6400

6.

Select Default system if you want to publish reports to this system from any role that has not been explicitly assigned to a BusinessObjects Enterprise system. Only one BusinessObjects Enterprise system can be the default system per SAP System.

7.

Navigate to the RFC Destinations tab.


116


2009




Figure 38: RFC Destination tab

8.

Click Insert Row to add the RFC Destination for the BusinessObjects Enterprise system that was created previously.

9.

Select the RFC Destination created previously from the list of available RFC destinations.

10. Click Verify BOE Definition. Note: This test verifies that BW can communicate to the specified BW Publisher, and can log onto the BusinessObjects Enterprise system. 11. Navigate to the HTTP tab.


2009


117


BO100

BO100

Figure 39: HTTP tab

12. Provide the details for the BusinessObjects Enterprise system: • •

•

•

Protocol: Type http (unless the web server that is connected to BusinessObjects Enterprise is configured to use https). Web server host and port: Type the fully qualified domain name or the IP address of the web server that hosts your BusinessObjects Enterprise InfoView or custom web application. For example: TWDFXXXX:8080 Path: This path is essentially the virtual path that your web server uses when referring to the SAP subfolder of your BusinessObjects Enterprise web content (or the path to any customer web application). Do not include a forward slash at the beginning or at the end of this entry. Viewer application: Type the name of the viewer application.

13. Click the Languages tab.


118


2009




14. Select the language that will be used to publish reports in multiple languages: • • •

Click Add all languages to add all for the SAP system configured languages. Select a language in the table and click Delete Row to remove a language. Click Insert Row to add a language.

15. Click the Roles tab.

Figure 40: Roles tab


2009


119


BO100

BO100

16. Select the roles that will be used for this BusinessObjects Enterprise system. •

To add a role:

•

1. Click Insert Row. 2. Select the role and set the check box. For example ZBO100. 3. Click Copy (Enter). To remove a role:

•

1. Select the role in the table. 2. Click Delete Row. To re-assign roles: 1.

Click Reassign Roles. Note: The selection screen offers roles that have been assigned to existing BusinessObjects Enterprise systems.

2. 3.

Select the role and set the check box. Click Copy (Enter).

17. Click the Layout tab.

Figure 41: Layout tab


120


2009




18. Define the default security settings and base folder for publishing. Note: Publishing Crystal Report objects from SAP BW to BusinessObjects Enterprise results in a report object and in a folder structure replicating the SAP role structure on the BusinessObjects Enterprise system. 19. Click OK (F8).

Result After you have finished all the settings, you can confirm your SAP BusinessObjects Enterprise system. You should now re-open your system definition and navigate to the RFC Destination tab. You can use the Verify BOE Definition button to validate that all involved components can communicate with each other. Keep in mind that this test is not performed in an actual publishing, it is only testing the communication.

Configuring the SAP source parameters Part of the publishing process is to set the correct data source settings for all the content being published from SAP BW to the BusinessObjects Enterprise system.

2009


121


BO100

BO100

To set the SAP source parameters 1.


2.

Start transaction /CRYSTAL/RPTADMIN (Content Administration Workbench).


3.

Navigate to the Publish reports folder.

4.

Open the folder SAP System Settings.

5.

Double-click Set BW source parameter.


122


2009




Figure 43: Parameter for Publishing on Crystal Enterprise

6.

Click New Entries.

7.

Depending on the system landscape you either need to provide the values for: • •

Application server and system number. Application server and logon group.

In this case, you will enter the values shown below: Property

Value

Application Server

/H/tdcsaprouter.wdf.sap.corp/H/tdc00.wdf.sap.corp

System number

50


2009


123


BO100

BO100

Figure 44: New Entries

8.

Click Save.

Configuring the SAP HTTP request handler To enable viewing of reports in BW via the role menu (for example, opening a Crystal Report from the SAP GUI), you must configure BW to use the HTTP request handler that is included as part of the Crystal Content Administration Workbench transport. Then, when a BW user opens a Crystal report from within the SAP GUI, BW is able to route the viewing request over the web appropriately to BusinessObjects Enterprise.

124


2009




To configure the SAP HTTP request handler 1.


2.

Start transaction SICF (Maintain services).

Figure 45: Maintain service

3.

Choose Execute or press F8

4.

Navigate to the folder default_host/SAP/BW.


2009


125


BO100

BO100

Figure 46: Maintain service

5.

Double-click ce_url.

6.

Navigate to the Handler List tab.

7.

Ensure the top entry is /CRYSTAL/CL_BW_HTTP_HANDLER. Note: In case the entry is not the top entry, the Insert Row and Delete Row option can be used to add/remove items.

8.

Click Save.

9.

Close the window.

10. Log off from the SAP server.

126


2009




BusinessObjects security configuration for publishing Based on the described details for the publishing process, consider three main categories of users when configuring BusinessObjects Enterprise for publishing, and when importing roles to BusinessObjects Enterprise: •

•

•

BusinessObjects Enterprise administrators: Enterprise administrators configure the BusinessObjects Enterprise system for publishing content from SAP. They import the appropriate roles, create necessary folders, and assign rights to those roles and folders in BusinessObjects Enterprise. Content publishers: Content publishers are those users who have rights to publish content into roles. The purpose of this category of user is to separate regular role members from those users with rights to publish reports. Role members: Role members are users who belong to “content bearing” roles. That is, these users belong to roles to which reports are published. They have rights to view and schedule content that has been published to the roles they are members of. However, regular role members cannot publish new content, nor can they publish updated versions of content. Note: You must import all content publishing and all content bearing roles to BusinessObjects Enterprise prior to publishing for the first time.

It is strongly recommended that you keep the activities of roles distinct. For example, while it is possible to publish from an administrator role, it is better practice to publish only from content publisher roles. Additionally, the function of content publishing roles is only to define which users can publish content. Thus, content publishing roles should not contain any content. Content publishers should publish to content bearing roles that are accessible to regular role members. The following are recommendations for the previously described BusinessObjects user groups:

Role Members BusinessObjects Enterprise imports a group for each role that is added to the entitlement system as defined in the CMC. To ensure that suitable default rights are granted to all members of a content bearing role, grant the following rights in the Content Administration Workbench for each entitlement system that is defined in BusinessObjects Enterprise: • •

2009

Default Security policy for reports = View Default security policy for role folders = View on Demand


127


BO100

BO100

Content Publisher Assign the following rights to a publisher role in the Central Management Console: • • • • • • •

Add objects to the folder. View objects. Edit objects. Modify the rights users have to objects. Delete objects. Delete instances. Copy objects to another folder. Note: These rights should be assigned on a folder level or on an SAP system level and should only be assigned to a role that focuses on publishing reports from SAP BW to BusinessObjects Enterprise.

128


2009




To configure the rights in the Content Administration Workbench 1.

Start the SAP Logon.

2.

Select the SAP server.

3.

Click Log on.

4.

Enter the User, Password, and Language.

5.

Press Enter.

6.

Enter the transaction code /CRYSTAL/RPTADMIN.

7.

Press Enter.

8.

Open the folder Enterprise system.


9.

Open the folder Available systems.

10. Double-click the entry for the BusinessObjects Enterprise system 11. Navigate to the Layout tab. 12. Configure the default security policy for reports and role folders. 13. Click OK.

2009


129


BO100

BO100

To configure the rights in the Central Management Console 1.


2.

Navigate to the Folders.

3.

Navigate to the SAP System ID folder.

4.

Select the folder.

5.

Select the menu Manage → User Security.

6.

Click Add Principals.

7.

Click Groups.

8.

Select the Content Publishing role from the SAP system.

9.

Click the right arrow to move the role to the list of selected users/groups.

10. Click Add and Assign Security. 11. Navigate to the Advanced tab. 12. Click Add/Remove rights. 13. Ensure the needed rights are granted 14. Click OK. 15. Click OK. 16. Click Close. Note: Based on this configuration the selected SAP role and member of this SAP role are able to publish content to any of the SAP roles for the selected SAP system.

130


2009




Lesson Summary You should now be able to: • Describe the publishing process • Configure the BW Publisher service • Create RFC destination • Create a BusinessObjects Enterprise server definition • Configure the SAP source parameters • Configure the HTTP handler • Configure the BusinessObjects Enterprise security for publishing

2009


131


BO100

BO100

Unit Summary You should now be able to: • Explain the technical prerequisites for BusinessObjects XI Integration for SAP Solutions • Install BusinessObjects XI Integration for SAP Solutions • Evaluate distributed deployment considerations • Describe distributed scenarios and list the needed components • Evaluate client side deployment considerations • Describe client-side scenarios and list the needed components • Configure the SAP authentication • Configure global options for the SAP Authentication • Import SAP users and roles • Describe the publishing process • Configure the BW Publisher service • Create RFC destination • Create a BusinessObjects Enterprise server definition • Configure the SAP source parameters • Configure the HTTP handler • Configure the BusinessObjects Enterprise security for publishing

132


2009


Unit Summary

Test Your Knowledge


Where do you need to install BusinessObjects XI Integration for SAP Solutions for if you want to refresh a LiveOffice document based on Crystal Report using SAP data? Choose the correct answer(s).

2.

□ □ □

A B C

□

D

Install where the Crystal Reports Job Server is running Install where the Crystal Reports Cache Server is running Install where the Crystal Reports Processing Server is running (CORRECT) Install on the Client PC

How do you add SAP users to BusinessObjects Enterprise? Choose the correct answer(s).

□ □ □ □ 3.

A B C D

Add the SAP Users using the SAP authentication tab Add the SAP Roles using the SAP authentication tab Add the SAP Groups using the SAP authentication tab Add the SAP Profiles using the SAP authentication tab

Which component needs to be installed and configured to allow Crystal Reports to be uploaded to SAP and BusinessObjects Enterprise? Choose the correct answer(s).

□ □ □ □

2009

A B C D

SAP Publisher BW Publisher SAP Request Handler BW Request Handler


133


BO100

BO100

Answers 1.

Where do you need to install BusinessObjects XI Integration for SAP Solutions for if you want to refresh a LiveOffice document based on Crystal Report using SAP data? Answer: C Correct answer is C.

2.

How do you add SAP users to BusinessObjects Enterprise? Answer: B Correct answer is B.

3.

Which component needs to be installed and configured to allow Crystal Reports to be uploaded to SAP and BusinessObjects Enterprise? Answer: B Correct answer is B.

134


2009


Test Your Knowledge



Unit Summary

135


2009


BO100

Unit Summary

136


2009


BO100

Query and Adhoc Reporting with Web Intelligence on BW Unit Overview Web Intelligence is one of a broad collection of tools offered in the SAP BusinessObjects Enterprise platform that provides a solution for creating, analyzing and distributing data stored in organizations data banks. In this unit we will review query and adhoc reporting capabilities, and the tools best suited for the job and compare these to the BEx suite in SAP NetWeaver BW.

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

Explain what query and adhoc reporting is. List the BusinessObjects tools that perform query and adhoc reporting. Explain when each tool should be used and when it should be avoided Explain when Web Intelligence and Business Explorer (BEx) should be used Provide an example where Web Intelligence and BEx co-exist and complement each other Describe Business Explorer queries Explain the relationship between BEx queries and Web Intelligence (via universes) Describe the elements of SAP BW OLAP Universes Describe how SAP BW objects are mapped and used in a universe

Unit Contents Lesson: Query and Adhoc Reporting ............................................ 138 Lesson: Web Intelligence and SAP Business Explorer ........................ 144 Exercise 2: Creating an OLAP Universe from a BEx Query .............. 157

2009


137


Unit 4

BO100

Lesson: Query and Adhoc Reporting Lesson Overview This lesson discusses the evaluation of the SAP BusinessObjects BI solutions. You will learn to choose the best tool to use for ad hoc reporting and understand why one should use one tool over another.


Explain what query and adhoc reporting is. List the BusinessObjects tools that perform query and adhoc reporting. Explain when each tool should be used and when it should be avoided

Business Example You are planning to implement a BusinessObjects Enterprise solution integrated with SAP NetWeaver BW and would like classify and position the various BusinessObjects reporting tools in your environment where business users require full information autonomy.

Query and Adhoc reporting An Adhoc Query is a query that cannot be determined prior to the moment the query is issued. It is created in order to get information when need arises and it consists of dynamically constructed SQL / MDX which is usually constructed by desktop / web resident query tools. This is in contrast to any query which is predefined and performed routinely. BusinessObjects Platform suite components for reporting include: • • • • • •

Crystal Reports Desktop Intelligence Web Intelligence Voyager Xcelsius Live Office Note: Desktop Intelligence functionality is being replaced by Web Intelligence and Web Intelligence Rich Client

138


2009


Unit 4: Query and Adhoc Reporting with Web Intelligence on BW

Lesson: Query and Adhoc Reporting

These tools are suited for various user audiences and business solutions

Tool

Best Audience

Best Business Solutions

Crystal Reports

Most business users

Static reporting, highly formatted reports, pixel perfect presentation, mass printing and distribution, relational databases, enterprise applications and data warehouse sourced data

Web Intelligence

Most casual business users Powerful query and ease of use adhoc reporting, self serve template based report creation and interactive analysis, enterprise distribution, with mostly relational and OLAP sourced data

Voyager

Analyst and business user

Multi dimensional analysis of information

Xcelsius

Most business users

Dashboard and presentation quality visualizations

Live Office

Analyst and casual users

Seamless MS Office integration with data retrieval, presentation and distribution.

BusinessObjects Explorer

Business users and casual users

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.

2009


139


BO100

Tool

Best Audience

BO100

Best Business Solutions Charts and relevant data automatically provided to user. Get new insight into your data through new data search and guided navigation paradigms. High end user value at a low IT cost.

Figure 48: BI Decision Tree

140


2009




Figure 49: Mapping the right tool to the right scenario

As business users roles change during their business life from day to day, the type and appetite for information consumption also changes. A single user for this reason may consume data from different tools sets depending on their requirements. A cost center manager may consume a highly formatted report with exceptions on cost items that exceeded budget for the month as a Crystal Report exported to Excel attached in email. A brand manager may require advertising spend by campaign linked to sales for the month to determine marketing cost effectiveness using Web Intelligence to combine data from two different sub-systems; marketing and sales. A product manager may want to analyze product category margins by location across market for this year and last year using Voyager. A North American sales director is presenting to the board performance based sales by region and product in the form of a dashboard and PowerPoint presentation using Xcelsius and Live Office. The examples above demonstrate that there is a different solution based on user business needs. Query and adhoc reporting is best satisfied by Web Intelligence. Note: The component products will evolve and change as future components merge and are added within the BusinessObjects and SAP BW product platforms. For example Voyager will transform into Pioneer becoming a more powerful multi dimensional solution for power analysts.

2009


141


BO100

BO100

Figure 50: Product mapping with solution capabilities

142


2009




Lesson Summary You should now be able to: • Explain what query and adhoc reporting is. • List the BusinessObjects tools that perform query and adhoc reporting. • Explain when each tool should be used and when it should be avoided

2009


143


BO100

BO100

Lesson: Web Intelligence and SAP Business Explorer Lesson Overview In this lesson SAP Business Explorer (BEx) is brought in for discussion. You will learn the use cases for both Web Intelligence and BEx with examples of how they can co-exist.

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

Explain when Web Intelligence and Business Explorer (BEx) should be used Provide an example where Web Intelligence and BEx co-exist and complement each other Describe Business Explorer queries Explain the relationship between BEx queries and Web Intelligence (via universes) Describe the elements of SAP BW OLAP Universes Describe how SAP BW objects are mapped and used in a universe

Business Example You plan to implement Web Intelligence with SAP BW access as your query and adhoc reporting solution. You need a comprehensive overview of how they integrate and complement each other. You need this information to understand the relationship between BEx queries and universes.

SAP Business Explorer Suite of products The Business Explorer (BEx) has evolved from its first incarnation as an Excel add-in that provided access to information stored in SAP BW into a suite of independent tools that support a wide range of usage types. The SAP BW capabilities of NetWeaver include support for: • • • • •

144

Formatted reporting Mobile devices HTML web based applications Ad-hoc analysis via a web browser Excel integration


2009



Lesson: Web Intelligence and SAP Business Explorer

You will notice that Business Explorer has the same capabilities as the BusinessObjects toolsets that needs further clarification. Business Explorer consists of several tools: • • • • • •

BEx Query Designer BEx Analyzer BEx Broadcaster BEx Web Application Designer BEx Report Designer BEx Web Analyzer

Figure 51: SAP Business Explorer Suite

2009


145


BO100

BO100

Figure 52: BEx Suite Cases Use Cases

When to use Web Intelligence and BEx Determining which tool to use between WEBI and BEX is taken as a use case basis with business considerations in mind.

146


2009




The flagship ad-hoc reporting and analysis product for casual business users is Web Intelligence. Web Intelligence should be seen as a complementary tool to leverage outputs from the deeper analysis achieved in BEx Analyzer. The following list of user requirements is associated with selecting Web Intelligence as the appropriate solution: • • • • • • • • • • •

Combination of ad-hoc reporting and analysis for casual business users Self-service thus autonomy from IT Adding and synchronizing BW data with other data sources such as Relational sources Scheduling and publishing to a wider user base through BusinessObjects Enterprise Ad-hoc creation and modification of reports over the web Easy and intuitive, drag and drop web interface Creating sections and breaks on repeating values from dimensions Defining reusable calculations Formatting headers and footers Fine-tuned chart and table formatting, more flexible conditional formatting Free-form positioning and absolute & relative positioning of charts and tables in the same reports

For OLAP analysis activities, BEx continues to be the tool of choice (until Pioneer is released). The following list of user requirements is associated with selecting BEx Analyzer as the appropriate solution: • • • • • • • •

Complex financial and business analysis High performance on large data volumes (cubes) Integrated analysis in Excel front-end Leverage multiple InfoProviders from BW Utilize existing modeling in BW Model and develop complex algorithms Option for Super Users to develop custom BEx Queries Maintain “status quo” for current BEx users Note: Both solutions can co-exist in environments that have requirements for both.

2009


147


BO100

BO100

Describe Business Explorer queries.

Figure 53: InfoProvider to Business Explorer flow

All multidimensional reporting and analysis performed in the BEx suite of tools is based on a query definition stored in the Meta Data Repository. Queries provide access to multidimensional information providers (InfoCubes), as well as flat information providers such as DataStore Objects (DSO) and master data. Query elements include characteristics, key figures, calculated key figures (formulas), restricted key figures, and reusable structures. Queries may have filters on characteristic values or filters on key figure values (conditions) assigned to select a certain slice of information from the InfoProvider. They may be parameterized by query variables. All characteristics, navigational attributes, and key figures available through an InfoProvider are available for use in the Query Designer. Upon selection of an InfoProvider, the designer will see a list of metadata defining the following elements: Structures: These are collections of selections and formulas that provide layout criteria for a row or column that may be used by queries for a particular InfoProvider. Structures may contain a combination of key figures, characteristics, and formulas. A reusable structure is a particular, commonly used collection of key figures or characteristics stored in the Meta Data Repository for reuse in multiple queries (for example, a plan/actual variance or a contribution margin schema). Filters: Predefined filter criteria for the whole query that may be reused in all queries for a particular InfoProvider. A filter may contain any combination of characteristics and their filter values. A filter specifies the size of the subcube, as well as the initial navigation state displayed at query startup.

148


2009




Key figures: A type of InfoObject used to record quantitative facts or measures. All of the key figures for a particular InfoProvider are available for queries. A calculated key figure is a formula consisting of basic, restricted, or other calculated key figures available in the InfoProvider stored in the Meta Data Repository for reuse in multiple queries (for example, an average discount rate). A restricted key figure has an associated filter on certain characteristic values stored in the Meta Data Repository for reuse in multiple queries (for example, year to date (YTD) sales of the previous year). A query consists of metadata elements arranged in rows, columns, and free characteristics. Dimensions: Dimensions refer to the grouping of characteristic InfoObjects in InfoCubes. A number of query elements that reach another level have an important place as it relates to universe object translation: • • • •

Designing queries with hierarchies Variables Restricting and calculating Key Figures (CKF and RKF) Exception aggregations

The relationship between BEx queries and Web Intelligence (via universes) BW Queries are recommended as data sources for generating Business Objects universes for the following reasons: 1.

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

2009

SAP BW Metadata Feature

SAP OLAP BAPI support level

Characteristics (incl. Time and Unit)

InfoCube/BW Query

Hierarchies

InfoCube/BW Query

Basic Key Figures

InfoCube/BW Query

Navigational Attributes

BW Query only

Display Attributes

InfoCube/BW Query


149


BO100

2. 3. 4. 5.

BO100

SAP BW Metadata Feature

SAP OLAP BAPI support level

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. 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. Note: The recommendations is to design as few BEx queries as possible to satisfy a particular subject area thus minimizing the number of universe that needs to designed and maintained.

150


2009




How SAP BW objects are mapped and used in a universe

Figure 54: Mapping SAP BW and Business Objects

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. 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.

2009

BI object

Universe objects created

Dimension Group

Class

Characteristic

Subclass with dimension and detail objects


151


BO100

BI object

BO100

Universe objects created

Characteristic with hierarchy

If data source is a BEx 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.

Structure based on Characteristics (BEx Queries only)

Class with single dimension object for the structure

Navigational attribute

Subclass with dimension and detail objects (identical to 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 Figure (BEx Queries only)

Measure and dimension objects (same as Key Figure)

Restricted Key Figure (BEx Queries only)

Measure and dimension objects (same as Key Figure)

Variables (BEx Queries only)

Filter mandatory in query 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 (BEx Queries only)

Universe parameters defining key date variable in the universe

Characteristics in the Filters section of the BW Query are not mapped. However, the filtering applies to the universe. If the filter has a fixed value, the filter is applied transparently when running the Web Intelligence query. If the characteristic has a variable defined, the variable is mapped with these limitations: • •

152

The variable always behaves like a mandatory variable. Hierarchy and hierarchy node variables are not supported.


2009




To avoid these limitations, Business Objects recommends moving the characteristic from the Filter section to the free section of the BW Query.

How BW characteristics and mapped and used in the universe •

•

•

When no hierarchy is defined on the characteristic in the BEx 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 BI 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. Navigational attributes leveraged in the BEx Query are mapped in the parent object class in the same way as characteristics are mapped. Note: A large number of navigational attributes defined in the underlying InfoProvider negatively impacts the overall performance (please refer back to SAP Best Practices for Data Modelling). Structures defined in the BEx Query that are based on characteristics are included in the universe as single-dimension objects with the elements of the structure as dimension members. Note: Objects in the universe can be renamed using the Universe API. For Example, objects with L00 in the name can be hidden and L01 objects can have the L00 in the named removed. An Excel macro can be used to speed up this processed and customize it based on customers requirements.

2009


153


BO100

BO100

How BI key figures are mapped and used in a universe All key figures in the InfoCube or defined in the BEx Query are included in the universe under a single object class called “Key Figures”. Most key figures are defined in BI with either a currency or a unit characteristic. Based on the details of the key figure, Designer creates up to three objects: • • •

A measure object with the numeric value 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, '200 USD', '345 €', '25 km'.

The Key Figures class includes the calculated key figures and restricted key figures defined in the BEx Query. The original calculation and restrictions are applied to the query, but are not exposed in the universe. Note: Having a large number of key figures in the BEx query will currently incur a significant performance penalty when running queries using Universe data access. This is regardless of whether the key figures are included in the Universe or used in the WebI query. It is therefore suggested to have only those key figures intended to be used for reporting included in the BEx query definition. This performance impact is due to time spent loading metadata for units, which is currently executed for all measures in the query. A fix for this issue may become available in the future.

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.

154


2009




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 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. Note: 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 reduce complexity for the report designing users (i.e., report developers). Even in cases where an active Hierarchy does exist, the “L00” objects may be unnecessary. In cases where there is only one top-level root of the Hierarchy, it may be desirable to remove the “L00” object for a Hierarchy, unless it is necessary to report members which are not assigned in 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. Note: BW variables apply to BW Queries only.

2009


155


BO100

BO100

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 and authorization processed variables) 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.

156

Variable Type

Support Level

Single value prompt

Supported

Multiple single value prompt

Supported

Interval prompt

Supported

Selection option prompt

Supported as interval prompt

Pre-calculated value set

Not supported

Formula

Price, quota, and numeric values supported

Hierarchy

Supported except for version variable

Hierarchy node

Supported


2009




Exercise 2: Creating an OLAP Universe from a BEx Query Exercise Objectives After completing this exercise, you will be able to: • Create an initial BEx query and OLAP universe for further updates

Business Example As a Universe Designer you are required to make changes to the universe to enhance adhoc reporting capabilities

Task: Create an initial BEx query which will be used for further updates in other exercises 1.

Use BEx Query designer and create a basic Query from InfoProvider T_BO1001, select “Sold_to party” and “Fiscal year/period” as rows or free characteristics and key figures “Incoming Orders” and “Invoiced quantity” as columns Note: Field Name

Value

System

Assigned system (for example: )

Client

900

User

Assigned user ID (for example: BO100-##)

Password

Assigned password

Language

Desired language key (for example: EN)

2.

Make sure that query is released for external access

3.

Save query as T_BO100_QLCM_001_##, where ## is your group number

4.

Launch Universe designer. Continued on next page

2009


157


BO100

5.

158

BO100

Create new connection and new universe from above query as T_BO100_QLCM_001_##, where ## is your group number Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language

Desired language key

Application Server


System number

50

System ID

Assigned system ID

6.

Configure universe parameters with summary information and no control limits

7.

Save and export universe

8.

Create a Web Intelligence rich client document, save and export to BOE Enterprise (CMS). Use name T_BO100_QLCM_001_##, where ## is you group number


2009




Solution 2: Creating an OLAP Universe from a BEx Query Task: Create an initial BEx query which will be used for further updates in other exercises 1.

Use BEx Query designer and create a basic Query from InfoProvider T_BO1001, select “Sold_to party” and “Fiscal year/period” as rows or free characteristics and key figures “Incoming Orders” and “Invoiced quantity” as columns Note:

a)

Field Name

Value

System

Assigned system (for example: )

Client

900

User

Assigned user ID (for example: BO100-##)

Password

Assigned password

Language

Desired language key (for example: EN)

Start Query Designer • • • • • • • •

Go to Start ->All Programs -> Business Explorer -> Query Designer Select System = , Click OK. Type is Client=900, User=BO100-##, Password= xxxxxx and Language=en, Click OK Select Query -> New on the menu toolbar Select Find, type in BO100, press enter select BO100 Cube [T_BO1001], Click Open. On the View Toolbar click Rows/Columns. From the InfoProvider, Key Figures drag and drop Incoming orders and Invoiced quantity to Columns area Expand Customer dimension and select Sold-to party and drop in Free Characteristics area Continued on next page

2009


159


BO100

•

BO100

Expand Time dimension and select Fiscal year/period and drop in Rows area

Figure 55: Initial Query Design

2.

Make sure that query is released for external access a)

3.

From menu toolbar select Query -> Properties. In the Properties area select advanced tab. Under "Release OLE DB for OLAP access" check the box "Allow external access to this query"

Save query as T_BO100_QLCM_001_##, where ## is your group number a)

From the menu toolbar, select check query and confirm the query is good. Save the query by clicking Query → Save As and type "T_BO100_QLCM_001_##“ for ”Description and technical Name.

b)

Save the query.

c)

Close Query Designer. From the toolbar menu, select Query → Exit


160


2009




4.

5.

Launch Universe designer. a)

To create a universe. Launch Designer. Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → Designer

b)

Enter the login information below and click OK.

Create new connection and new universe from above query as T_BO100_QLCM_001_##, where ## is your group number Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language



2009


161


BO100

BO100

Field Name

Value

Application Server


System number

50

System ID

Assigned system ID

a) Note: Cancel quick design wizard if necessary Select Menu File -> New. Select New button under connection, Click Next in the new connection Wizard window. Ensure Connection Type is "Secured". Type "T_BO100_QLCM_001_##" in connection Name. Select SAP, then expand to SAP Business Warehouse then expand to SAP Client in the Database Middleware Selection, click Next b)

Define new connection. In the Define new Connection Window specify: Authentication Mode = "Use specified username and password" User name: = BO100-## Password: = xxxxxx Client: = 900 Language: = EN Login Mode: = Application Server / Message Server (use Application server) Application Server:: = /H/tdcsaprouter.wdf.sap.corp/H/tdc00.wdf.sap.corp (for application server only) System Number: = 50 (for application server only) System ID: = Logon Group: = OPEN (for message server only) Message server: = (for message server only) Click Next In the Catalog / database parameters window, type in query name T_BO100_QLCM_001_## next to search button and click Search. Click Next when query is found. Keep all defaults and click finish


162


2009




6.

Configure universe parameters with summary information and no control limits a)

In the universe parameters window. Type universe name "T_BO100_QLCM_001_##". In the summary tab add Version Vn, reason for change, changed by xxxxxx and changed on yyy-mm-dd. In the Controls tab uncheck default options. In the SQL tab uncheck "Allow use of subqueries" and uncheck “Allow compex operations in query panel.”Click OK

Figure 56: Initial Universe Generation


2009


163


BO100

7.

BO100

Save and export universe a)

Save universe as "T_BO100_QLCM_001_##" to the default local folder. Folder name when universe is new is .../Universe...

b)

From menu Select File -> Export, click OK when prompted to save if not already saved, Click Browse for domain and select CMS folder T_BO100_LCM. If folder does not exist then select root folder then select Insert New Folder button and create a folder called T_BO100_LCM_## (## is your group number). Click OK to complete the export process.

Figure 57: Export Universe to BusinessObjects CMS

c) 8.

Exit Universe designer. Select File → Exit

Create a Web Intelligence rich client document, save and export to BOE Enterprise (CMS). Use name T_BO100_QLCM_001_##, where ## is you group number a)

Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → Web Intelligence Rich Client.

b)

Enter login Information and press logon. Continued on next page

164


2009




System: TWDFXXXX User Name: BO100-## Password: Assigned password c)

From Menu bar select File → New, on New Document window select Universe. Press Next>>

d)

Select universe T_BO100_QLCM_001_##, In the Create Query window, expand all folders and select Incoming Orders, L01 Sold-to party and L01 Fiscal year/period. Press run query.

Figure 58: Web Intelligence Query Creation


2009


165


BO100

BO100

Figure 59: Web intelligence Document after Refresh Query

e)

Save document to local drive and export to CMS. From Menu bar select File → Save, type in name as T_BO100_QLCM_##.wid

f)

Export to BOE, from menu bar, select File → Export to CMS. In save windows expand Public Folders then click on folder T_BO100_LCM_##. Press Export. Click close and exit rich client. Select File → Exit. Note: If folder does not exist, then create the folder by focusing on the Public Folder, then press the Create New Folder Button, Type in new folder T_BO100_LCM_##.

166


2009




Lesson Summary You should now be able to: • Explain when Web Intelligence and Business Explorer (BEx) should be used • Provide an example where Web Intelligence and BEx co-exist and complement each other • Describe Business Explorer queries • Explain the relationship between BEx queries and Web Intelligence (via universes) • Describe the elements of SAP BW OLAP Universes • Describe how SAP BW objects are mapped and used in a universe

2009


167


BO100

BO100

Unit Summary You should now be able to: • Explain what query and adhoc reporting is. • List the BusinessObjects tools that perform query and adhoc reporting. • Explain when each tool should be used and when it should be avoided • Explain when Web Intelligence and Business Explorer (BEx) should be used • Provide an example where Web Intelligence and BEx co-exist and complement each other • Describe Business Explorer queries • Explain the relationship between BEx queries and Web Intelligence (via universes) • Describe the elements of SAP BW OLAP Universes • Describe how SAP BW objects are mapped and used in a universe

168


2009


Unit Summary

Test Your Knowledge


Help desk management would like to empower a team to create ad-hoc reports against BW data. Objects/dimensions, key figures/measures and SLAs have been defined. A simple clear, business view of these data objects needs to be provided to design simple on the fly charting and grid reports to meet their operational team needs. The volume of help desk data being analyzed is daily, weekly and monthly. Which SAP BusinessObjects reporting tool would be the most appropriate to use? Choose the correct answer(s).

□ □ □ □

2009

A B C D

Web Intelligence on OLAP Universe Crystal Reports on OLAP Universe Crystal Reports on BW Queries Voyager and/or SAP Business Explorer (BEx)


169


BO100

BO100

Answers 1.

Help desk management would like to empower a team to create ad-hoc reports against BW data. Objects/dimensions, key figures/measures and SLAs have been defined. A simple clear, business view of these data objects needs to be provided to design simple on the fly charting and grid reports to meet their operational team needs. The volume of help desk data being analyzed is daily, weekly and monthly. Which SAP BusinessObjects reporting tool would be the most appropriate to use? Answer: A Web Intelligence on OLAP Universe is correct.

170


2009


Test Your Knowledge



Unit Summary

171


2009


BO100

Unit Summary

172


2009


BO100

OLAP Universes on SAP BW - Part 1 Unit Overview This unit provides you with an overview of SAP variables and how these are used in OLAP Universes and Web Intelligence.

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

Describe SAP BW variables Create OLAP Universes with an optional variable Leverage optional prompts in Web Intelligence Create OLAP Universes with mandatory SAP variables Leverage mandatory prompts in Web Intelligence Create an OLAP Universe with variables which have default values specified Leverage prompts with default values in Web Intelligence Create an OLAP Universe with variables which utilize delegated search Leverage prompts with delegated search enabled in Web Intelligence Create OLAP Universes with SAP hierarchies Leverage hierarchies in Web Intelligence Create OLAP Universes with SAP hierarchy variables Create OLAP Universes with SAP hierarchy and hierarchy node variables Use keydate variables in OLAP Universes and Web Intelligence Describe the dependencies of a keydate variable in OLAP Universes Create a Web Intelligence report with a keydate variable dependency

Unit Contents Lesson: BW Variables .............................................................. 175 Exercise 3: Creating a new OLAP Universe with optional variables..... 183 Lesson: Mandatory variables...................................................... 190

2009


173


Unit 5

BO100

Exercise 4: Creating a new OLAP Universe with mandatory variables . 193 Lesson: SAP variables with default values ...................................... 200 Exercise 5: Creating a new OLAP Universe with default value variables ......................................................................... 203 Lesson: SAP variables with delegated search .................................. 209 Exercise 6: Creating a new OLAP universe with variables using delegated search ............................................................................ 211 Lesson: Hierarchies in OLAP Universes......................................... 218 Lesson: Hierarchies and hierarchy node variables in OLAP Universes ..... 220 Exercise 7: Creating a new OLAP Universe with hierarchy and hierarchy node variables .................................................................. 225 Lesson: Simple keydate scenarios ............................................... 234 Procedure: To create a new Universe with a keydate variable .......... 235 Procedure: To use a keydate variable in Web Intelligence ............... 236 Lesson: Keydate variable dependencies ........................................ 239

174


2009


Unit 5: OLAP Universes on SAP BW - Part 1

Lesson: BW Variables

Lesson: BW Variables Lesson Overview In this lesson you will learn how to create an OLAP Universe using optional SAP Variables and leverage these as optional prompts in Web Intelligence reports.


Describe SAP BW variables Create OLAP Universes with an optional variable Leverage optional prompts in Web Intelligence

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 a variable.

BW Variables SAP Variables can be interpreted as user prompts defined in the BEx 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, Text, and Formula elements. BW Variables apply to BEx Queries only. The following types of BW Variables are supported in Universes: • • • • • • •

2009

Characteristic variables Hierarchy variables Hierarchy node variables Currency variables Formula variables Text variables (as replacement path and authorization processed variables) Key Date variables


175


BO100

BO100

The following table shows a detailed list of the Variable Type "User Entry / Default Value" only and how those are leveraged in a Universe. User Entry variables can be mandatory or optional, and can have default values. Optional Variables are defined as optional filters in the Universe, and become optional prompts in Web Intelligence. Mandatory Variables become mandatory prompts in Web Intelligence. Note: A mandatory filter is hidden and cannot be selected in the Query Panel in WebIntelligence.

Variables Type Characteristic

Single value prompt

Supported

Multiple single value prompt

Supported

Interval prompt

Supported

Selection option prompt

Supported as interval prompt

Pre-calculated value set

Supported

Text

Not Supported

Formula

Price, quota, and numeric values supported

Hierarchy

Supported

Hierarchy node

Supported

Hierarchy Version

Not Supported

Keydate

Supported

Currency

Supported

The following table shows Universe support for other processing types of BW Variables.

Variables Type

Characteristic

176

Processing Type User Entry/Default Value

Replacement path

Authorization

Customer exit

SAP exit

Supported

Supported

Supported

Supported

Supported


2009




Variables Type

Processing Type

Text

Not Supported

Supported

N/A

N/A

N/A

Formula

Supported

Supported

N/A

Supported

Supported

Hierarchy

Supported

N/A

N/A

Supported

Supported

Hierarchy node

Supported

N/A

N/A

Supported

Supported

Creating OLAP Universes with optional prompts Optional variables in SAP BEx reporting tools are used to offer the capability to limit the result set in terms of volume of data. In BEx Analyzer / BEx Web, when an optional variable is not used the result set is returned for all rows of data (as defined in rows/columns of BEx Query design) unless the underlying SAP BW query uses a default value or a personalized variable value. When creating an OLAP Universe on a BEx Query with optional variables, the variables are automatically added as optional prompts. In Web Intelligence, when the optional prompts are not used the result set is returned for all rows of data based on the WebI Query panel Results section (and NOT the BEx query definition). Note: Variables will only be added as prompts to an OLAP Universe if they are added to the Filter tab in the ‘Characteristic Restrictions’ area. Hint: To ensure the best possible performance, it is best to utilize SAP Variables to filter data returned from SAP BW. The other option would be to just leverage filtering capability in the Web Intelligence Query Panel Filter area – this would then add the filter criteria in the MDX statement passed to BW. In situations where there is not an @Prompt or SAP Variable defined this will work, but the data selection is BW will be inefficient and queries may run much longer than if an SAP Variable had been used. The difference in MDX terms is that the filter criteria will be passed in nested CROSSJOINs within the ROWS returned, rather than adding the filter to the WHERE clause of the MDX statement.

2009


177


BO100

BO100

Figure 60: Optional Prompts

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 list 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 list of value definitions.

178


2009




Figure 61: List of Value

Based on the SAP variable definition, there is also a filter created in the OLAP Universe.

Figure 62: Filter View in the Universe

The in the Where syntax indicates that the filter is optional

2009


179


BO100

BO100

Figure 63: Where syntax

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.

180


2009



BO100

2009

Figure 64: Run query


181




182


2009


BO100


Exercise 3: Creating a new OLAP Universe with optional variables Exercise Objectives After completing this exercise, you will be able to: • Create an OLAP universe and Web Intelligence report with option variables

Business Example Your business reporting group requires optional prompts in Web Intelligence reports.

Task: Create an OLAP universe and Web Intelligence document with optional variables (as optional prompts in the Universe and Web Intelligence document). 1.

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

Value

System

Assigned BusinessObjects Enterprise system (for example: TWDFXXXX)

User name

Assigned user name (for example: BO100-##)

Password

Assigned password

Authentication

SAP

2. Note: Cancel the Quick Design Wizard. Create a new OLAP Universe using the query ‘BO100 optional variable’ (technical name: T_BO1001/T_BO100_Q03_1). Field Name

Value

User

Assigned user

Password

Assigned password

Client

900 Continued on next page

2009


183


BO100

184

BO100

Field Name

Value

Language


Application Server


System number

50

System ID

Assigned system ID

3.

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

4.

Export the universe to the BusinessObjects repository folder webi universes.

5.

Create a new Web Intelligence report on top of the OLAP Universe.

6.

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.

7.

Select different values for the optional prompt and run the report with a selection to see the results.

8.

Save the report to the default folder with the name Sales Volume Report with Optional Prompt.


2009




Solution 3: Creating a new OLAP Universe with optional variables Task: Create an OLAP universe and Web Intelligence document with optional variables (as optional prompts in the Universe and Web Intelligence document). 1.

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

Value

System


User name


Password

Assigned password

Authentication

SAP

a)

Go to Start → Programs → BusinessObjects XI 3.1→ BusinessObjects Enterprise Client Tools.

b)

Click Designer.

c)

Logon with your username and password when prompted

2. Note: Cancel the Quick Design Wizard. Create a new OLAP Universe using the query ‘BO100 optional variable’ (technical name: T_BO1001/T_BO100_Q03_1). Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language



2009


185


BO100

BO100

Field Name

Value

Application Server


System number

50

System ID

Assigned system ID

a)

Click File > New.

b)

Click New to create a new connection.

c)

Click Next.

d)

Select SAP -> SAP Business Warehouse from the list.

e)

Enter a connection name.

f)

Click Next.

g)

Enter the User name, Password, and Language.

h)

Enter the Client, Application Server, and System Number based on the SAP server details. Note: The connection dialog allows you to select between an Application server and a Message server connection.

i)

Set the Authentication Mode to Use specified username and password.

j)

Click Next.

k)

Open the list of available cubes by clicking the plus sign next to OLAP Cubes.

l)

Navigate to BO100 cube and select ‘BO100 optional variable’ (technical name: T_BO1001/T_BO100_Q03_1).

m)

Select the required query and Click Next.

n)

Click Finish.

o)

Enter the Universe name T_BO100_Optional_Variable_##.

p)

Navigate to the Controls tab.

q)

Uncheck all Query Limits.

r)

Click OK.


186


2009




3.

4.

5.

Save the Universe to the BusinessObjects Universes folder with the name T_BO100_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_BO100_Optional_Variable_##.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)

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

Create a new Web Intelligence report on top of the OLAP Universe. a)

Start InfoView. Select Start → Programs → BusinessObjects XI 3.1→ BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView.

b)

Select SAP as Authentication type.

c)

Enter the SAP System, SAP Client, User name, and Password.

d)

Click Log On.

e)

Click Document List.

f)

Select the menu New > Web Intelligence.

g)

Select the universe you just created.

h)

Select the Dimensions and Measures you want to display in your Web Intelligence report.

i)

Click Run Query.


2009


187


BO100

6.

BO100

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.

7.

8.

188

Select different values for the optional prompt and run the report with a selection to see the results. a)

Click Refresh Data.

b)

Select a customer value and click > to bring it to the right window.

c)

Click Refresh Data.

Save the report to the default folder with the name Sales Volume Report with Optional Prompt. a)

Select File → Save As. Press Enterprise. Select SAP 2.0 CLNT900. Enter the description GR## Sales Order Report with Optional Prompt.

b)

Press Save.


2009




Lesson Summary You should now be able to: • Describe SAP BW variables • Create OLAP Universes with an optional variable • Leverage optional prompts in Web Intelligence

2009


189


BO100

BO100

Lesson: Mandatory variables Lesson Overview In this lesson you will learn how to create an OLAP Universe using mandatory SAP Variables and leverage these as mandatory prompts in Web Intelligence reports.


Create OLAP Universes with mandatory SAP variables Leverage mandatory prompts in Web Intelligence

Business Example Your business reporting group requires mandatory prompts in Web Intelligence reports to enforce data volume restrictions when querying against SAP BW InfoProviders.

Creating OLAP Universes with mandatory prompts Mandatory variables in SAP BEx reporting tools are used to offer the capability to force the user to be prompted for the entry of a data restriction. This will limit the amount of data the user can return in any given query they execute. This is especially important when the data volumes are very large – it is a best practice to enforce some variables/prompts to be entered in order to ensure the best possible performance. In BEx Analyzer / BEx Web, when an mandatory variable is used in a BEx Query the user must make an entry otherwise they cannot submit the query. When creating an OLAP Universe on a BEx Query with mandatory variables, the variables are automatically added as mandatory prompts. The Dimension object includes the List of value definition and in the filter area you receive a filter defined as mandatory (to be recognized by the missing syntax.

190


2009



Lesson: Mandatory variables

Figure 65: The missing syntax in the Where syntax indicates that the filter is mandatory

In Web Intelligence, when refreshing the data in the document these prompts will be enforced as mandatory as well.

2009


191


BO100

BO100

Figure 66: Mandatory Prompt

Note: Variables will only be added as prompts to an OLAP Universe if they are added to the Filter tab in the ‘Characteristic Restrictions’ area.

192


2009




Exercise 4: Creating a new OLAP Universe with mandatory variables Exercise Objectives After completing this exercise, you will be able to: • Create an OLAP universe and Web Intelligence report with mandatory variables

Business Example Your business reporting group requires mandatory prompts in Web Intelligence reports to enforce data volume restrictions when querying against SAP BW InfoProviders.

Task: Create an OLAP universe and Web Intelligence report with mandatory variables (as mandatory prompts in the Universe and WebI report). 1.

Start the Universe Designer.

2.

Create a new OLAP Universe using the query ‘BO100 mandatory variable’ (technical name: T_BO1001/T_BO100_Q04_1). Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language


Application Server


System number

50

System ID

Assigned system ID

3.

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

4.


5.

Create a new Web Intelligence report on top of the OLAP Universe. Continued on next page

2009


193


BO100

194

BO100

6.

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.

7.

Select different values for the mandatory prompt and try running without a selection in the prompt to see the results.

8.

Save the report to the default folder with the name Sales Volume Report with Mandatory Prompt.


2009




Solution 4: Creating a new OLAP Universe with mandatory variables Task: Create an OLAP universe and Web Intelligence report with mandatory variables (as mandatory prompts in the Universe and WebI report). 1.

2.

Start the Universe Designer. a)

Go to Start > Programs > BusinessObjects XI 3.1 > BusinessObjects Enterprise Client Tools

b)

Click Designer.

c)

Logon with your username and password when prompted.

Create a new OLAP Universe using the query ‘BO100 mandatory variable’ (technical name: T_BO1001/T_BO100_Q04_1). Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language


Application Server


System number

50

System ID

Assigned system ID

a) Note: Cancel the Quick Design Wizard. Click File > New. b)


c)

Click Next.

d)


e)

Enter a connection name. Continued on next page

2009


195


BO100

3.

4.

BO100

f)

Click Next.

g)


h)


i)


j)

Click Next.

k)


l)

Navigate to BO100 cube and select ‘BO100 mandatory variable’ (technical name: T_BO1001/T_BO100_Q04_1).

m)


n)

Click Finish.

o)

Enter a name for the Universe into the field Name.

p)


q)


r)

Click OK.

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


b)

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



b)


c)


d)

Click OK to export the universe. The universe is now available for reporting. Continued on next page

196


2009




5.

6.


Start InfoView Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView.

b)


c)


d)

Click Log On.

e)


f)


g)


h)

Select the Dimensions and Measures you want to display in your WebI report.

i)

Click Run Query.

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. Note: A mandatory SAP variable now becomes a mandatory prompt in Web Intelligence. You must select a value before executing the query.

7.

Select different values for the mandatory prompt and try running without a selection in the prompt to see the results. a)

Select values for the mandatory prompt.

b)

Click Run Query.


2009


197


BO100

8.

198

BO100

Save the report to the default folder with the name Sales Volume Report with Mandatory Prompt. a)

Select File → Save As. Press Enterprise. Select SAP 2.0 CLNT900. Enter the description GR## Sales Order Report with Mandatory Prompt.

b)

Press Save.


2009




Lesson Summary You should now be able to: • Create OLAP Universes with mandatory SAP variables • Leverage mandatory prompts in Web Intelligence

2009


199


BO100

BO100

Lesson: SAP variables with default values Lesson Overview In this lesson you will learn how to create an OLAP Universe using SAP Variables which have default values defined and see how these behave in Web Intelligence reports as prompts.


Create an OLAP Universe with variables which have default values specified Leverage prompts with default values in Web Intelligence

Business Example Your business reporting group requires prompts in Web Intelligence reports which have default values specified. This allows commonly used prompt values to be predefined so users do not have to enter them every time they refresh data or create a new report.

Default values in OLAP Universes Inside the query designer an SAP variable can contain a default value. This default value acts like an initial suggested value for all users viewing this particular BW query. The users are still able to select a different value if needed. The default value of an SAP variable is stored as part of the actual filter WHERE definition that is created in the OLAP Universe.

Figure 67: Default values in OLAP Universes

200


2009



Lesson: SAP variables with default values

Creating OLAP Universes with default value variables BEx Variables defined with default values can be leveraged in Web Intelligence. The benefit of defining the default values is that the end user does not have to repeatedly enter the prompt selection for commonly used values, however they still have the flexibility to adjust the prompt selection at refresh time. When generating an OLAP Universe based on a BEx Query which contains variables with default values, the prompt created for the variable will look like any other prompt on a variable – the difference is at run time the default values will be populated in the prompt value selection screen.

Figure 68: Default values in Web Intelligence

Note: Variables will only be added as prompts to an OLAP Universe if they are added to the Filter tab in the ‘Characteristic Restrictions’ area.

2009


201


BO100


202


2009


BO100


Exercise 5: Creating a new OLAP Universe with default value variables Exercise Objectives After completing this exercise, you will be able to: • Create an OLAP universe and Web Intelligence report with variables that have default values defined.

Business Example Your business reporting group requires prompts in Web Intelligence reports which have default values specified. This allows commonly used prompt values to be predefined so users do not have to enter them every time they refresh data or create a new report.

Task: Create an OLAP universe and Web Intelligence report with variables that have default values defined. 1.

1. Start the Universe Designer.

2.

Create a new OLAP Universe using the query ‘BO100 default value variable’ (technical name: T_BO1001/T_BO100_Q05_1).

3.

Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language


Application Server


System number

50

System ID

Assigned system ID

Save the Universe to the BusinessObjects Universes folder with the name T_BO100_Default_Values_##. Continued on next page

2009


203


BO100

204

BO100

4.


5.


6.

Run the WebI refresh with the default values, or override them with you own selection.

7.

Save the report to the default folder with the name Sales Volume Report with Default Values.


2009




Solution 5: Creating a new OLAP Universe with default value variables Task: Create an OLAP universe and Web Intelligence report with variables that have default values defined. 1.

2.

1. Start the Universe Designer. a)

Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools.

b)

Click Designer.

c)


Create a new OLAP Universe using the query ‘BO100 default value variable’ (technical name: T_BO1001/T_BO100_Q05_1). Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language


Application Server


System number

50

System ID

Assigned system ID

a) Note: Cancel the Quick Design Wizard. Click File > New. b)


c)

Click Next.

d)


e)

Enter a connection name. Continued on next page

2009


205


BO100

3.

4.

BO100

f)

Click Next.

g)


h)


i)


j)

Click Next.

k)


l)

Navigate to BO100 cube and select ‘BO100 default value variable’ (technical name: T_BO1001/T_BO100_Q05_1).

m)


n)

Click Finish.

o)


p)


q)


r)

Click OK.

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


b)

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



b)


c)


d)

Click OK to export the universe. The universe is now available for reporting. Continued on next page

206


2009




5.


Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView.

b)


c)


d)

Click Log On.

e)


f)


g)


h)

Select the Dimensions and Measures you want to display in your Web Intelligence report.

i)

Click Run Query. Note: When executing a report with a default value for prompting the default value is suggested as a value for the prompt but can be removed or changed.

6.

Run the WebI refresh with the default values, or override them with you own selection. a)

Use the default values for the prompt or select your own values.

b)

Click Run Query. Note: If you remove the default value from an optional variable and execute the query without any selected value, the default value will be used for data retrieval.

7.

2009

Save the report to the default folder with the name Sales Volume Report with Default Values. a)

Select File → Save As. Press Enterprise. Select SAP 2.0 CLNT900. Enter the description GR## Sales Order Report with Default Values.

b)

Press Save.


207


BO100

BO100

Lesson Summary You should now be able to: • Create an OLAP Universe with variables which have default values specified • Leverage prompts with default values in Web Intelligence

208


2009



Lesson: SAP variables with delegated search

Lesson: SAP variables with delegated search Lesson Overview In this lesson you will learn how to create an OLAP Universe using SAP Variables which utilize the delegated search feature in the Universe definition.


Create an OLAP Universe with variables which utilize delegated search Leverage prompts with delegated search enabled in Web Intelligence

Business Example Your business reporting group requires prompts in Web Intelligence reports on dimensions that have a large number of distinct values. Immediately presenting all values to the user for selection would not be ideal from a usability perspective and for performance reasons. A feature in Designer allows prompts to delegate the search of values to the database.

Creating OLAP Universes with variables with delegated search When utilizing prompts based on BEx Variables in an OLAP Universe, at runtime WebI retrieves all distinct values for the prompt from BW. In situations where the prompt is based on a dimension with a high number of distinct values (i.e. Customer or Material), performance may be quite poor and also not ideal from a usability perspective. Rather than sorting through thousands of values, the delegated search functionality will allow the user to search for the values they are interested in filtering on. Note: Variables will only be added as prompts to an OLAP Universe if they are added to the Filter tab in the ‘Characteristic Restrictions’ area.

2009


209


BO100


210


2009


BO100


Exercise 6: Creating a new OLAP universe with variables using delegated search Exercise Objectives After completing this exercise, you will be able to: • Create an OLAP universe and Web Intelligence report with delegated search prompts

Business Example Your business reporting group requires prompts in Web Intelligence reports on dimensions that have a large number of distinct values. Immediately presenting all values to the user for selection would not be ideal from a usability perspective and for performance reasons. A feature in Designer allows prompts to delegate the search of values to the database.

Task: Create an OLAP universe and Web Intelligence report with delegated search prompts

2009

1.


2.

Create a new OLAP Universe using the query ‘BO100 optional variable’ (technical name: T_BO1001/T_BO100_Q03_1).

3.

Change the prompt to utilize delegated search.

4.

Save and export the Universe.

5.


6.

Run the WebI refresh and specify a search pattern to find values for filter.


211


BO100

BO100

Solution 6: Creating a new OLAP universe with variables using delegated search Task: Create an OLAP universe and Web Intelligence report with delegated search prompts 1.


a. Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools.

b)

Click Designer.

c)



212


2009




2.

Create a new OLAP Universe using the query ‘BO100 optional variable’ (technical name: T_BO1001/T_BO100_Q03_1). a)

Click File → New.

b)


c)

Click Next.

d)


e)


f)

Click Next.

g)


h)


i)

Set the Authentication Mode to Use Single Sign On when refreshing reports at view time. Note: Using single-sign-on in combination with an SAP system requires the SAP authentication to be configured for the SAP system in the Central Management Console of BusinessObjects Enterprise.

j)

Click Next.

k)


l)

Navigate to BO100 cube and select ‘BO100 optional variable’ (technical name: T_BO1001/T_BO100_Q03_1).

m)


n)

Click Finish.

o)


p)


q)


r)

Click OK. Continued on next page

2009


213


BO100

3.

BO100

Change the prompt to utilize delegated search. a)

Find the prompt for Sold To Party. The prompt you want to change is the LOV ‘Base’ prompt. Note: In some situations the prompt may appear under the "Sales Area data" class.

b)

Double click on the prompt (filter icon).

c)

Click on the Properties tab and select ‘Delegate Search’ in the properties for the prompt.

Figure 69: Delegate Search

d)

Click OK.


214


2009




4.

Save and export the Universe. a)

Select the menu File > Export. Note: The Universe needs to be saved before it can be exported.

5.

b)

Click Save.

c)

Select a Domain.

d)

Select the Groups that should be assigned to the Universe.

e)

Click OK.

f)

Click OK.


Start InfoView. Select Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView.

b)


c)


d)


e)


f)


g)


h)

Select the Dimensions and Measures you want to display in your WebI report.

i)

Click Run Query.


2009


215


BO100

6.

BO100

Run the WebI refresh and specify a search pattern to find values for filter. a)

Specify the search pattern *100* and click the search icon.

b)

When the search result returns, select Becker Berlin and use the arrow icon to move it to the right side of the prompt.

c)

Click Run Query.

Figure 70: Search Criteria

216


2009




Lesson Summary You should now be able to: • Create an OLAP Universe with variables which utilize delegated search • Leverage prompts with delegated search enabled in Web Intelligence

2009


217


BO100

BO100

Lesson: Hierarchies in OLAP Universes Lesson Overview In this lesson you will learn how to create an OLAP universe using SAP hierarchies and leverage these hierarchies in Web Intelligence reports.


Create OLAP Universes with SAP hierarchies Leverage hierarchies in Web Intelligence

Business Example Your business requires group data and use drill down capability in Web Intelligence report. You need to leverage SAP hierarchy into OLAP universe.

Create OLAP Universes with hierarchies 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.

218


2009



Lesson: Hierarchies in OLAP Universes

Lesson Summary You should now be able to: • Create OLAP Universes with SAP hierarchies • Leverage hierarchies in Web Intelligence

2009


219


BO100

BO100

Lesson: Hierarchies and hierarchy node variables in OLAP Universes Lesson Overview This lesson provides you with an overview of SAP hierarchy and hierarchy node variable and how they are leveraged in OLAP Universes.


Create OLAP Universes with SAP hierarchy variables Create OLAP Universes with SAP hierarchy and hierarchy node variables

Business Example Your business requires flexible reports with free selection of different SAP hierarchies of an InfoObject. You need to utilize SAP hierarchy and hierarchy node variable into OLAP Universe.

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: • • •

220

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


2009



Lesson: Hierarchies and hierarchy node variables in OLAP Universes

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. Note: “”Note 1007048 - MDX: Filtering of variables in the hierarchy display“” needs to be applied in BW to access Hierarchy Variables via universe. Without the note fix universe cannot read BEx hierarchy variable directly. But universe can read hierarchy variable if the hierarchy variable is attached with a hierarchy node variable. Limitation of this workaround is that every WebI report will have both hierarchy variable and hierarchy node variable. To show only the hierarchy variable in WebI report, MDX of universe filter need to be modified manually. Note: Depending on the hierarchy that was selected and the defined hierarchy structure on the SAP BW side some of the selected levels might be empty. If nothing selected flat list will be returned. Note: Hierarchy Variable can use default values. If default value is used, always select the smallest hierarchy as the default value. If default value has more levels than the selected hierarchy in the run time, generated MDX statement will cause error. This is a bug and will be fixed in later release.

2009


221


BO100

BO100

Figure 71: Hierarchy Variable Prompt in WebI report

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.

222


2009




Figure 72: Hierarchy Node Variable in Universe

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


223


BO100

BO100

Figure 73: Hierarchy Node Variable Prompt

224


2009




Exercise 7: Creating a new OLAP Universe with hierarchy and hierarchy node variables Exercise Objectives After completing this exercise, you will be able to: • Create a new OLAP Universe with a hierarchy and hierarchy node variable • Create a new Web Intelligence report using the OLAP Universe

Business Example You are a report designer and need to create a new OLAP universe with a hierarchy and a hierarchy node variable.

Task: Create an OLAP universe and Web Intelligence report with hierarchy and hierarchy node variable. 1.

2.

Start the Universe Designer. Field Name

Value

System

Assigned system (for example: TWDFXXXX)

User Name

Assigned user name (for example: BO100-## )

Password

Assigned password

Authentication

SAP

Create a new OLAP Universe using the query BO100 hierarchy variable Workaround (technical name: T_BO1001/ T_BO100_Q08_1_W). Field Name

Value

User Name


Password

Assigned password

Client

900

Language



2009


225


BO100

3.

226

BO100

Field Name

Value

Application Server

/H/tdcsaprouter. wdf.sap.corp/H/tdc00.wdf.sap.corp

System number

50

System ID

Assigned system ID


4.


5.

Select different possible combinations of Hierarchy and Hierarchy node values.


2009




Solution 7: Creating a new OLAP Universe with hierarchy and hierarchy node variables Task: Create an OLAP universe and Web Intelligence report with hierarchy and hierarchy node variable. 1.

2.

Start the Universe Designer. Field Name

Value

System

Assigned system (for example: TWDFXXXX)

User Name


Password

Assigned password

Authentication

SAP

a)

Go to Start → Programs → BusinessObjects XI Release 3.1 → BusinessObjects Enterprise Client Tools

b)

Click Designer

c)

Logon with your username and password when prompted

Create a new OLAP Universe using the query BO100 hierarchy variable Workaround (technical name: T_BO1001/ T_BO100_Q08_1_W). Field Name

Value

User Name


Password

Assigned password

Client

900

Language


Application Server

/H/tdcsaprouter. wdf.sap.corp/H/tdc00.wdf.sap.corp

System number

50

System ID

Assigned system ID


2009


227


BO100

BO100

a)

Click File > New.

b)


c)

Click Next.

d)


e)


f)

Click Next.

g)


h)


i)


j)

Click Next.

k)


l)

Navigate to BO100 Cube and select BO100 hierarchy variable Workaround(technical name: T_BO1001/ T_BO100_Q08_1_W)

m)


n)

Click Finish.

o)


p)


q)


r)

Click OK.


228


2009




Figure 74: Generated Universe with Hierarchy variable and hierarchy node variable LOVs

3.


Select the menu File > Export. Note: The Universe needs to be saved before it can be exported.

b)

Click Save.

c)


d)


e)



2009


229


BO100

4.

BO100


Start InfoView (Start → Programs → BusinessObjects XI Release 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView).

b)


c)


d)

Click Log On.

e)


f)


g)


h)

Select all needed levels from the hierarchy and include them into the Result Objects. Expand the node Material → Material2 and drag L01 Material into Result Objects panel. Repeat for L02 Material, L03 Material, and L04 Material.

5.

i)

Expand the node Key Figures and drag the measures Sales Volume EUR into the Result Objects next to L04 Material.

j)

Click Run Query.

Select different possible combinations of Hierarchy and Hierarchy node values. a)

Select the hierarchy Product Hierarchy for material MARA from the hierarchy variable values and click > to bring to the right window.


230


2009




Figure 75: Hierarchy and Hierarchy node values

b)

For the Product Hierarchy Node, expand Product Hierarchy for material MARA and select a hierarchy node from hierarchy node variable


2009


231


BO100

BO100

Figure 76: Hierarchy and Hierarchy node variable

c)

Click Run Query.

Figure 77: Run Query

232


2009




Lesson Summary You should now be able to: • Create OLAP Universes with SAP hierarchy variables • Create OLAP Universes with SAP hierarchy and hierarchy node variables

2009


233


BO100

BO100

Lesson: Simple keydate scenarios Lesson Overview In this lesson, you will learn about the use of an SAP keydate variable in OLAP Universes.


Use keydate variables in OLAP Universes and Web Intelligence

Business Example Your business requires flexible reports with free selection of different SAP keydate variables. You need to utilize SAP keydate variable into OLAP Universe.

Keydate scenarios in Web Intelligence Keydate variables can influence several items in the underlying SAP BW source: • • •

Keydate variables can influence the actual master-data that is retrieved for dimensions.For example: a product description can change over time. Keydate variables can influence the list of hierarchies that is available for a dimension. Keydate variables can influence a hierarchical structure. For example : a specific cost center can be on level 1 of the hierarchy for the Year 2004 but on level 02 for the year 2005.

The generation process for OLAP Universes does not allow the user to provide a date for the keydate variable, which means the system date from the SAP BW server will be used for creating the OLAP Universe.In a scenario where the OLAP Universe is not generating enough levels for a hierarchy - which would mean the user would not be able to see all levels of the hierarchy when creating a Web Intelligence report - the user is able to create these levels manually in the universe. In case the OLAP Universe includes too many levels for a hierarchy, these levels will be empty in Web Intelligence for hierarchies that do have less levels. When the SAP BW query contains a keydate scenario a prompt is included into the universe. The prompt based on the keydate variable is available in the query panel to enable different options for this prompt.

234


2009



Lesson: Simple keydate scenarios

To create a new Universe with a keydate variable 1.


2.

Log onto the BusinessObjects Enterprise system.

3.

Select File → New to create a new connection.

4.

Select SAP Business Warehouse 3.x from the list and enter a connection name. Click Next to continue.

5.


6.


7.


8.

Click Next.

9.

Open the list of available cubes and navigate to the required cube. Select the required query and click Next.

10. Click Finish. 11. Enter a name for the Universe into the field Name. 12. Navigate to the Controls tab and uncheck all Query limits. Click OK . 13. Select the menu File → Export. 14. Save the universe. 15. Select a Domain and Groups that should be assigned to the Universe. Click OK.

Using a keydate variable in Web Intelligence When using a keydate variable in Web Intelligence, the user can specify the behavior of the prompting in Web Intelligence in the query panel.

2009


235


BO100

BO100

To use a keydate variable in Web Intelligence 1.

Start InfoView.

2.


3.


4.

Click Log On.

5.


6.

Select the menu New → Web Intelligence.

7.

Select the OLAP Universe based on the BW query with a keydate variable.

8.

Select the needed dimension objects for the Result Objects.

Figure 78: Web Intelligence Document

9.

Click Keydate Properties.


236


2009



Lesson: Simple keydate scenarios

Figure 79: Keydate Properties

10. Select the option Set a date. 11. Specify a date. 12. Click OK. Note: Depending on the settings for the table object in the report some rows might be combined into a "#MULTIVALUE" row. To avoid the situation you can change the "Avoid duplicate row aggregation" property of the table object. 13. Set the Avoid duplicate row aggregation property to Yes. 14. Click Refresh Data. 15. Specify a different value for the keydate variable. 16. Click OK.

2009


237


BO100

BO100

Lesson Summary You should now be able to: • Use keydate variables in OLAP Universes and Web Intelligence

238


2009



Lesson: Keydate variable dependencies

Lesson: Keydate variable dependencies Lesson Overview In this lesson you will learn about the dependencies of a keydate variable in OLAP Universes.


Describe the dependencies of a keydate variable in OLAP Universes Create a Web Intelligence report with a keydate variable dependency

Business Example Your business requires flexible reports with free selection of different SAP keydate variables. You need to utilize SAP keydate variable into OLAP Universe.

Keydate variable dependencies In the case where the underlying SAP BW query contains a keydate variable and other variables (like a hierarchy variable or a hierarchy node variable) the user is prompted twice and the value set for the keydate variable might influence the list of values for the second variable. Examples for such a scenario are: • •

A hierarchy node variable in combination with a keydate variable, where the keydate variable influences the hierarchical structure. A hierarchy variable in combination with a keydate variable, where the keydate variable influences the list of available hierarchies.

Using keydate variable dependencies in Web Intelligence When using a keydate variable in combination with other prompts the user will be prompted for the keydate variable first so that any dependency based on the keydate variable is set correctly.

2009


239


BO100

BO100

Lesson Summary You should now be able to: • Describe the dependencies of a keydate variable in OLAP Universes • Create a Web Intelligence report with a keydate variable dependency

240


2009



Unit Summary

Unit Summary You should now be able to: • Describe SAP BW variables • Create OLAP Universes with an optional variable • Leverage optional prompts in Web Intelligence • Create OLAP Universes with mandatory SAP variables • Leverage mandatory prompts in Web Intelligence • Create an OLAP Universe with variables which have default values specified • Leverage prompts with default values in Web Intelligence • Create an OLAP Universe with variables which utilize delegated search • Leverage prompts with delegated search enabled in Web Intelligence • Create OLAP Universes with SAP hierarchies • Leverage hierarchies in Web Intelligence • Create OLAP Universes with SAP hierarchy variables • Create OLAP Universes with SAP hierarchy and hierarchy node variables • Use keydate variables in OLAP Universes and Web Intelligence • Describe the dependencies of a keydate variable in OLAP Universes • Create a Web Intelligence report with a keydate variable dependency

2009


241


BO100

Unit Summary

242


2009


BO100

Test Your Knowledge


Number of dimensions created under a class containing hierarchy depends on the level of hierarchy. Determine whether this statement is true or false.

□ □ 2.

True False

"Not assigned" items under level 0 includes all elements that have not been assigned to actual hierarchy structure. Determine whether this statement is true or false.

□ □ 3.

True False

A BEx query have 5 hierarchies and the hierarchies have 3, 9, 5, 11 and 4 levels respectively. OLAP universe created on top of this BW query will have 9 dimensions created for this characteristic class. Determine whether this statement is true or false.

□ □ 4.

True False

Web Intelligence Report will present all available hierarchy node values for all available hierarchies. Determine whether this statement is true or false.

□ □

2009

True False


243


BO100

BO100

Answers 1.

Number of dimensions created under a class containing hierarchy depends on the level of hierarchy. Answer: True TRUE. For a hierarchy with 4 levels, L00 to L003 dimensions will be created under the universe class.

2.

"Not assigned" items under level 0 includes all elements that have not been assigned to actual hierarchy structure. Answer: True TRUE. In the case of hierarchies, a level 0 item called "not assigned" is used to include items that are not assigned to the BW hierarchy.

3.

A BEx query have 5 hierarchies and the hierarchies have 3, 9, 5, 11 and 4 levels respectively. OLAP universe created on top of this BW query will have 9 dimensions created for this characteristic class. Answer: False FALSE. Universe will create 11 (maximum) levels for the characteristic.

4.

Web Intelligence Report will present all available hierarchy node values for all available hierarchies. Answer: True TRUE. 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 nodes with the selected hierarchy structure.

244


2009


Test Your Knowledge



Unit Summary

245


2009


BO100

Unit Summary

246


2009


BO100

OLAP Universes on SAP BW - Part 2 Unit Overview This unit describes advanced topics in OLAP Universes on SAP BW such as multi-structure queries, smart measures, calculation, and life-cycle management

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

Use multi-structure queries in OLAP Universes and Web Intelligence Create smart measures in OLAP Universes Describe custom calculations in OLAP Universes Update the OLAP universe to reflect changes Create and update OLAP Universes Build a new SAP BEx query, and generate an OLAP universe Make changes to the BEx query to see impact on universe objects

Unit Contents Lesson: Multi-structure queries in OLAP Universes............................ 248 Procedure: To use a multi-structure query in Web Intelligence .......... 251 Exercise 8: Creating a new OLAP Universe based on multi-structure query ............................................................................. 253 Lesson: Smart measures and calculations in OLAP Universes .............. 261 Procedure: To create a new Universe with a database delegated measure.......................................................................... 264 Procedure: To use a smart measure in Web Intelligence ................ 266 Exercise 9: Creating a new Universe with a database delegated measure, and utilizing the database delegated summation in a Web Intelligence document ........................................................................ 269 Lesson: Updating OLAP Universes .............................................. 279 Exercise 10: OLAP Universe Update Part 1 ................................ 283 Exercise 11: OLAP Universe Update Part 2 ................................ 289

2009


247


Unit 6

BO100

Lesson: Multi-structure queries in OLAP Universes Lesson Overview In this lesson, you will learn about the use of multi-structure queries in OLAP Universes.


Use multi-structure queries in OLAP Universes and Web Intelligence

Business Example Your business reporting group requires a structured layout in a query. For instance they would like to display a Country Structure which displays countries United States, UK, and Germany. In addition they would like to see a structured set of Key Figures: Order Entry Qty, Invoiced Qty, and % Share to analyze the performance of these countries by.

OLAP Universes and BW query structures An SAP BW query can contain up to two structures. By creating such a query the end user defines a report with a grid type of layout. This image shows an SAP BW query in the query designer. This query contains two structures.

248


2009



Lesson: Multi-structure queries in OLAP Universes

Figure 80: Multi-structure query

The first structure (Country Structure) contains three elements - USA, Europe, and Asia Pacific - and the second structure (Structure) contains three elements - Order Quantity, Unit Price, and Position Price. A report created with SAP's reporting tools shows the resultset:

Figure 81: Resultset

When creating an OLAP Universe on top of an SAP BW query with multiple structures, the universe designer will try to identify the structure with characteristics and the structure with keyfigures.

2009


249


BO100

BO100

The structure with characteristics is turned into a single dimension object and the structure with keyfigures is turned into a keyfigure class with multiple measure objects. Leveraging the example mentioned above, the OLAP Universe will generate like shown below:

Figure 82: OLAP Universe

• •

The Country Structure is created as single dimension object. The second structure with keyfigures is created as a class named after the structure with the separate keyfigures.

Using a multi-structure query in Web Intelligence Based on the situation that the structure with the characteristic elements is turned into a single item, it is very simple to leverage the two structures in Web Intelligence for reporting.

250


2009




To use a multi-structure query in Web Intelligence 1.

Start InfoView.

2.


3.


4.

Click Log On.

5.


6.

Select the menu New → Web Intelligence .

7.

Select the OLAP Universe based on the BW query with two structures.

8.


9.

Include the element representing the characteristic structure.

10. Click Run Query. Note: Each element of the characteristic structure becomes a row in the Web Intelligence report.

2009


251


BO100


252


2009


BO100


Exercise 8: Creating a new OLAP Universe based on multi-structure query Exercise Objectives After completing this exercise, you will be able to: • Create a new OLAP Universe with multiple structures • Create a new Web Intelligence report using the OLAP Universe

Business Example Your business reporting group requires a structured layout in a query. In addition they would like to see a structured set of Key Figures.

Task: Create an OLAP universe and Web Intelligence report with variables that have default values defined. 1.


2.

Create a new OLAP Universe using the query ‘BO100 multi-structure’ (technical name: T_BO1001/T_BO100_Q06_1).

3.


4.


5.

Run the WebI refresh and add the Country Structure and Measures to the report layout. Note: Each element of the characteristic structure becomes a row in the Web Intelligence report.

2009


253


BO100

BO100

Solution 8: Creating a new OLAP Universe based on multi-structure query Task: Create an OLAP universe and Web Intelligence report with variables that have default values defined. 1.

2.


Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools .

b)

Click Designer.

c)


Create a new OLAP Universe using the query ‘BO100 multi-structure’ (technical name: T_BO1001/T_BO100_Q06_1). a)

Click File > New.

b)


c)

Click Next.

d)


e)



254


2009





f)

Click Next.

g)


h)


i)


j)

Click Next.

k)

Select the Multi Structure Query. Continued on next page

2009


255


BO100

BO100


l)

Change Connection Pool Mode to ‘Disconnect after each transaction’.


256


2009





m)

Click Finish and Generate the Universe.


2009


257


BO100

BO100



258


2009




3.


Review the generated Universe and see how the BEx Query Structures are translated into Dimensions and Measures.


4.


5.

Run the WebI refresh and add the Country Structure and Measures to the report layout. Note: Each element of the characteristic structure becomes a row in the Web Intelligence report. a)

2009


259


BO100

BO100

Lesson Summary You should now be able to: • Use multi-structure queries in OLAP Universes and Web Intelligence

260


2009



Lesson: Smart measures and calculations in OLAP Universes

Lesson: Smart measures and calculations in OLAP Universes Lesson Overview In this lesson, you will learn about the use of smart measures and calculations in OLAP Universes.


Create smart measures in OLAP Universes Describe custom calculations in OLAP Universes


Smart measures in OLAP Universes In a universe, any measure can hold a projection function (Sum, Min, Max, Count, and Avg). The projection function is used to aggregate the measure locally in Web Intelligence when the number of dimensions displayed in a report is smaller than the number of dimensions in the query resultset. Non-additive measures, such as ratio, average, and weight, can only be shown at the same aggregation level as the query resultset. Therefore, non-additive measures generally have their projection function set to None in the universe. The projection function Database delegated allows you to delegate the aggregation of a non-additive measure to the database server. These are called smart measures in Web Intelligence. A smart measure has its projection function set to Database delegated on the properties page of the object properties. For example: You have a report showing two dimensions - Country and Region - and the report shows three measures: Order Amount, Delivered Amount, % of Delivered Amount.

2009


261


BO100

BO100

Figure 88: Report

The image shows that the default aggregation results in a wrong value because the default aggregation summarizes the values. Right now the summary shows 499% delivered for the country Canada, where 99.99% would be the correct number. By configuring the measure object in the universe to leverage the projection function Database delegated, the correct summary becomes available after a second refresh of the report.

262


2009




Figure 89: Report

Smart Measures in Web Intelligence After the measure has been configured in the underlying universe to leverage the database delegated aggregation, this feature can easily be leveraged in Web Intelligence when creating a report.

2009


263


BO100

BO100

To create a new Universe with a database delegated measure 1.


2.

Log onto the BusinessObjects Enterprise system.

3.


4.

Select SAP Business Warehouse 3.x from the list and enter a connection name.

5.


6.


7.


8.

Click Next.

9.


10. Navigate to the required cube. Select the required query and click Next . 11. Click Finish . 12. Enter a name for the Universe into the field Name. 13. Navigate to the Controls tab. 14. Uncheck all Query Limits. 15. Click OK. 16. Open the folder Keyfigures. 17. Double-click the measure object. 18. Navigate to the Properties tab. 19. Set the Function to Database delegated . Continued on next page

264


2009




20. Click OK . 21. Save the universe and export it to BusinessObjects Enterprise system.

2009


265


BO100

BO100

To use a smart measure in Web Intelligence 1.

Start InfoView.

2.


3.


4.

Click Log On.

5.


6.

Select the menu New → Web Intelligence .

7.

Select the OLAP Universe based on the BW query with a database delegated measure.

8.


9.

Click Run Query.

10. Insert a section for the report. 11. Select the measure (the one that is being configured for database delegation). 12. Click Insert Sum. 13. Select Default aggregation. 14. Click Refresh Data.

Custom Calculations in OLAP Universes The user can create calculated measures in the universe. Calculated measures in OLAP universes are like definitions on the measure object in non-OLAP universes, except that you define the restriction using MDX functions embedded in XML tags rather than using SQL. Calculated measures can be used in filters or the WHERE clause. The syntax for a calculated measure consists of calculations embedded in the tags Universe designer functions are allowed in calculated measure expressions, such as: @SELECT @PROMPT @VARIABLE @WHERE

266


2009




Calculated measures can reference any OLAP metadata: • • • •

Measures Dimensions Dimension levels MDX expressions

The check integrity validates the XML syntax and any of the Designer functions. It is recommended you use @SELECT (measure name) as much as possible rather than the measure definition for multiple reasons: • • •

@SELECT is always resolved at query time. Calculated measures can reference other calculated measures. LifeCycle Management only ensures integrity with generated objects not with objects created by a user: @SELECT always guarantees the validity of the object.

In the given example you want to build a measure which calculates the Order Amount multiplied by Product Price. Example 1: [Measures].[AWUNOIYT142BYXSX5WBW4TU60]*[Measures].[AWUNOIYT142 BYXSX5WBW4TU60] Note: This calculation depends on the technical names of the measures. Example 2: @SELECT (Key Figures\Order Amount) *@SELECT (Key Figures\Product Price) Note: This calculation depends on the OLAP universe structure and elements, but not on the technical names.

2009


267


BO100


268


2009


BO100


Exercise 9: Creating a new Universe with a database delegated measure, and utilizing the database delegated summation in a Web Intelligence document Exercise Objectives After completing this exercise, you will be able to: • Create an OLAP universe with a database delegated measure and then utilize the database delegated summation in a Web Intelligence document.


Task: Create an OLAP universe with a database delegated measure and then utilize the database delegated summation in a Web Intelligence document. 1.


2.

Create a new OLAP Universe using the query ‘BO100 Smart Measures’ (technical name: T_BO1001/T_BO100_Q14_1).

3.

Change % Share measure properties to make the aggregation function Database Delegated.

4.


5.


6.

Run the WebI refresh and add all Dimensions and Measures to the report layout.

7.

Try adding a Sum on % Share and refresh the data to view the Sum. Note: Each element of the characteristic structure becomes a row in the Web Intelligence report.

2009


269


BO100

BO100

Solution 9: Creating a new Universe with a database delegated measure, and utilizing the database delegated summation in a Web Intelligence document Task: Create an OLAP universe with a database delegated measure and then utilize the database delegated summation in a Web Intelligence document. 1.

2.


Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools.

b)

Click Designer.

c)


Create a new OLAP Universe using the query ‘BO100 Smart Measures’ (technical name: T_BO1001/T_BO100_Q14_1). a)

Click File > New.

b)


c)

Click Next.

d)


e)



270


2009





f)

Click Next.

g)

Enter the Username, Password, and Language.

h)


i)


j)

Click Next.

k)

Select the Smart Measure Query. Continued on next page

2009


271


BO100

BO100


l)

Change Connection Pool Mode to ‘Disconnect after each transaction’.


272


2009





m)

Click Finish and Generate the Universe.


2009


273


BO100

BO100



274


2009




3.

Change % Share measure properties to make the aggregation function Database Delegated. a)

Double-click on the % Share measure and change the Aggregation Function to Database Delegated.



2009


275


BO100

4.

BO100


Create a WebI Report on the new Universe and test adding a Sum on the % Share measure.



276


2009




5.


Initially the Sum will be denoted as #TOREFRESH. This indicates that the summation must be delegated to the DB (upon refresh of data). Click Refresh Data to populate the Sum.


6.

Run the WebI refresh and add all Dimensions and Measures to the report layout. a)

7.

Try adding a Sum on % Share and refresh the data to view the Sum. Note: Each element of the characteristic structure becomes a row in the Web Intelligence report. a)

2009


277


BO100

BO100

Lesson Summary You should now be able to: • Create smart measures in OLAP Universes • Describe custom calculations in OLAP Universes

278


2009



Lesson: Updating OLAP Universes

Lesson: Updating OLAP Universes Lesson Overview This lesson provides you with an overview of OLAP Universe life cycle management (LCM). After completing this lesson you will be able to: • •

Create and update OLAP Universes Make changes in BEx queries that impacts universe object definition

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

Update the OLAP universe to reflect changes Create and update OLAP Universes Build a new SAP BEx query, and generate an OLAP universe Make changes to the BEx query to see impact on universe objects

Business Example Business Client has requested certain dimensional objects have the ability to be selected, sorted and grouped in the ad hoc query tool. You have determined that a refresh of the BEx query and thus the universe will provide this enhanced reporting functionality through enhanced navigation.

OLAP Universe life-cycle management As part of the life-cycle management feature, the user is able to update and edit OLAP Universes. The Update OLAP Universe Wizard allows you the refresh to structure of OLAP universes automatically 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. The wizard does not update objects added manually in Designer.

2009


279


BO100

BO100

The Update OLAP Universe Wizard compares the universe with the updated data source. It detects and updates: • • • • • •

280

New, modified and deleted dimensions. New, modified and deleted hierarchies. New, modified and deleted levels. New, modified and deleted measures. New, modified and deleted SAP BW variables. New, modified and deleted sub classes.


2009




OLAP Universe design guidelines Any changes to the BEx query or the underlying InfoCubes will impact universe object definition and thus any dependant reports. One very important guideline to ensure the integrity of BEx object UID and thus the internal Universe object ID. Follow these tips: •

Universe objects can be renamed to provide better business terms. For example: L00 Organization Unit is renamed to Company L01 Organization Unit is renamed to Business Unit

•

•

• •

•

•

•

2009

L02 Organization Unit is renamed to Division Always keep existing InfoObject BEx elements and never delete then re-create them. This changes the internal UID which impacts the existing universe object. A universe refresh will delete the object and create it again, impacting on existing reports that use that object. Always retain universe objects and never delete them if you intend to keep them. This step subsequently re-creates them after executing a refresh structure impacting reports that use them. Always follow a consistent process in the Universe Refresh wizard, such always uncheck “Keep Business Name” and always check “Delete obsolete objects” Consider using scripts to hide the L00 objects and rename the L01 prefixed objects that have no hierarchy active, making Web Intelligence easier to use and less cluttered. Navigational attributes used in the query definition map to individual classes each with dimension and detail objects Navigational attributes are identified by double underscore “__” in the technical name. Consider hiding attribute objects that match to these navigational objects. Use characteristic variables to narrow down records and speed up performance. In the BEx query create as many calculated and restricted key figures that will satisfy many reports and ad-hoc reporting requirements. Consider best practice implementation and performance guidelines


281


BO100


282


2009


BO100


Exercise 10: OLAP Universe Update Part 1 Exercise Objectives After completing this exercise, you will be able to: • Make changes to existing BEx query and noted the changes in the OLAP universe

Business Example As Universe Designer you require to make changes to universe to reflect modelling changes required by the business users

Task: Learner will make various changes to the BEx query and note the changes reflected in the OLAP universe 1.

Use BEx Query designer and modify the query T_BO100_QLCM_001_##, to add Material and Sold-to partyCountry characteristics, and add Sales Order Item key figure and remove characteristic Sold-to party

2.

Add characteristic “Material” (0MATERIAL) in the free area

3.

Add characteristic “Sold-to partyCountry”(0SOLD_TO__COUNTRY) to Free Characteristic area

4.

Add key figure “Sales Order Item”(0ORD_ITEMS) to columns

5.

Remove key figure Invoiced Quantity(0INVCD_QTY) from columns

6.

Remove characteristic “Sold-to party”(0SOLD_TO) from rows

7.

Check and Save query

8.

Launch universe designer to update universe

9.


10. Launch InfoView, modify report saved in previous exercise, T_BO100_QLCM_##_Part1

2009


283


BO100

BO100

Solution 10: OLAP Universe Update Part 1 Task: Learner will make various changes to the BEx query and note the changes reflected in the OLAP universe 1.

Use BEx Query designer and modify the query T_BO100_QLCM_001_##, to add Material and Sold-to partyCountry characteristics, and add Sales Order Item key figure and remove characteristic Sold-to party a)

Start Query Designer • • • •

2.

3.

Add characteristic “Material” (0MATERIAL) in the free area a)

On the View Toolbar click Rows/Columns.

b)

Expand Material dimension and select Material Characteristic and drop in Free Characteristics area

Add characteristic “Sold-to partyCountry”(0SOLD_TO__COUNTRY) to Free Characteristic area a)

4.

From Key Figures in the InfoProvider drag and drop Sales Order Item to the Columns area

Remove key figure Invoiced Quantity(0INVCD_QTY) from columns a)

6.

Expand Customer dimension and select Sold-to partyCountry and drop in Free Characteristics area

Add key figure “Sales Order Item”(0ORD_ITEMS) to columns a)

5.

Go to Start ->All Programs -> Business Explorer -> Query Designer Select System = , Click Ok Type is Client=900, User=BO100-##, Password= xxxxxx and Language=en, Click OK in the menu bar select Query -> Open, Press Find button, type in T_BO100_QLCM , click on query saved in Exercise 1 T_BO100_QLCM_001_##, press Open button.

Select the key figure, Invoiced Quantity(0INVCD_QTY) from the columns area and press delete

Remove characteristic “Sold-to party”(0SOLD_TO) from rows a)

Select Sold-to party from free Characteristic area and press delete Continued on next page

284


2009




7.

Check and Save query a)

From the menu bar, select check query and confirm query is good to continue saving, then Click Query -> Save. From the menu bar select File -> Exit

Figure 97: Modified BEx Query


2009


285


BO100

8.

9.

BO100

Launch universe designer to update universe a)

Go to Start -> All Programs -> BusinessObjects XI 3.1 -> BusinessObjects Enterprise Client Tools -> Designer

b)

Supply User identification System = tdc00:6400 User Name = <>SID~900/BO100-## Password = xxxxxx Authentication = SAP Click OK

c)

From menu File->Import, select universe saved in previous exercise, in folder T_BO100_LCM, universe T_BO100_QLCM_001_##, click OK, then OK when universe is successfully imported

d)

From menu, select View -> Refresh Structure, then Begin> button to continue with the Update OLAP Universe Wizard

e)

UnCheck Keep Business Names and Check Delete Obsolete Objects, Click OK to complete the change. (note deleted and new objects)


Save universe. From menu bar, select File -> Save

b)

From menu File->Export, select CMS folder T_BO100_LCM. Click OK to confirm export operation

c)

Exit Designer. Select File -> Exit

10. Launch InfoView, modify report saved in previous exercise, T_BO100_QLCM_##_Part1 a)

Launch Internet Explorer, type in URL = http://twdxxxx.wdf.sap.corp:8080/InfoViewApp/logon.jsp, click GO

b)

Enter login Information and press logon. Type SAP System: = SAP Client = 900 User Name: = BO100-## Password: = xxxxxx

c)

From InfoView click Document List, Expand Public Folders and click on folder T_BO100_LCM, select document to modify “T_BO100_QLCM_##_Part1”, Right click on document and select Modify. Click Refresh Data when document is open for editing


286


2009




Figure 98: Message when existing document is opened

d)

Press close when message “Some objects are no longer available in the universe.” Click Edit Query, Press close if message “The query contains unavailable objects” appears. Add additional objects to query panel and press Run Query


2009


287


BO100

BO100

Figure 99: Document after universe refresh

e)

288

Save as new document in CMS. From toolbar select Save button ->Save As, Expand folder Public Folders, then select T_BO100_LCM, type in name as T_BO100_QLCM_##_Part1. Click OK


2009




Exercise 11: OLAP Universe Update Part 2 Exercise Objectives After completing this exercise, you will be able to: • Make changes to existing BEx query and note the changes reflected in the OLAP universe

Business Example As a Universe Designer you require to make changes to universe to reflect modelling changes required by the business users

Task: Learner will make various changes to the BEx query and note changes reflected in the OLAP universe

2009

1.

Use BEx Query designer and modify the query T_BO100_QLCM_001_##, to add Sold-to party, Region(State. , and add a variable to Material

2.

Add characteristic “Sold-to party”(0SOLD_TO) in the free characteristic

3.

Add characteristic “Region (State. in the free area, rename description to “Region”

4.

Include additional variable “Material Variable” (T_MAT_V)

5.

Check and Save query

6.

Launch designer to update universe

7.


8.

Create new or use previous WEBI document

9.

Launch InfoView, modify report saved in previous exercise, T_BO100_QLCM_##_Part2


289


BO100

BO100

Solution 11: OLAP Universe Update Part 2 Task: Learner will make various changes to the BEx query and note changes reflected in the OLAP universe 1.

Use BEx Query designer and modify the query T_BO100_QLCM_001_##, to add Sold-to party, Region(State. , and add a variable to Material a)

Start Query Designer • • • •

2.

3.

Go to Start ->All Programs -> Business Explorer -> Query Designer Select System = , Click Ok Type is Client=900, User=BO100-##, Password= xxxxxx and Language=en, Click OK in the menu bar select Query -> Open, Press Find button, type in T_BO100_QLCM , click on query created earlier, T_BO100_QLCM_001_##. Press Open button.

Add characteristic “Sold-to party”(0SOLD_TO) in the free characteristic a)

On the View Toolbar click Rows/Columns.

b)

Expand Customer dimension and select Sold-to party(0SOLD_TO) Characteristic and drop in Free Characteristics area

Add characteristic “Region (State. in the free area, rename description to “Region” a)

Expand Customer dimension and select Region (Sold.(0SOLD_TO_0REGION)) Characteristic and drop in Free Characteristics area

b)

Click on the Region (State. characteristic and change the Description in the property window to Region


290


2009




4.

Include additional variable “Material Variable” (T_MAT_V) a)

On the View Toolbar click Filter.

b)

Drag Material characteristic in Default Values to Characteristic Restrictions

c)

Right click on the Material and select Restrict. Select variables from the Show drop down. Selelct variable [T_MAT_V] and click right arrow to select. Click OK

Figure 100: Add Material Variable

5.

Check and Save query a)

From the menu toolbar, select check query and confirm query is good to continue saving, then Click Query -> Save, then Query -> Exit to close the BEx Query Designer


2009


291


BO100

6.

BO100

Launch designer to update universe a)

Go to Start -> All Programs -> BusinessObjects XI 3.1 -> BusinessObjects Enterprise Client Tools -> Designer

b)

Supply User identification System = tdc00:6400 User Name = BO100-## Password = xxxxxx Authentication = SAP Click OK

c)

From menu File->Import, select universe saved in previous exercise, in folder T_BO100_LCM, universe T_BO100_QLCM_001_##, click OK, then OK when universe is successfully imported

d)

From menu, select View -> Refresh Structure, then Begin> button to continue with the Update OLAP Universe Wizard

e)

UnCheck

f)

Uncheck Keep Business Names and Check Delete Obsolete Objects, Click OK to complete the change. (note new objects)

Figure 101: Universe after refresh


292


2009




7.

8.


Save universe. From menu bar, select File -> Save

b)

From menu File->Export, select CMS folder T_BO100_LCM. Click OK to confirm export operation

c)

Exit Designer. Select File -> Exit

Create new or use previous WEBI document a)

9.

Launch InfoView, modify report saved in previous exercise, T_BO100_QLCM_##_Part2 a)

Launch Internet Explorer, type in URL = http://twdxxxx.wdf.sap.corp:8080/InfoViewApp/logon.jsp, click GO

b)

Enter login Information and press logon. Type SAP System: = SAP Client = 900 User Name: = BO100-## Password: = xxxxxx

c)

From InfoView click Document List, Expand Public Folders and click on folder T_BO100_LCM, select document to modify “T_BO100_QLCM_##_Part2”, Right click on document and select Modify. Click Refresh Data when document is open for editing

d)

Press Run Query


2009


293


BO100

BO100

Figure 102: Prompt Window when running Web Intelligence query

e)

294

Save as new document in CMS. From toolbar select Save button ->Save As, Expand folder Public Folders, then select T_BO100_LCM, type in name as T_BO100_QLCM_##_Part2, click OK


2009




Lesson Summary You should now be able to: • Update the OLAP universe to reflect changes • Create and update OLAP Universes • Build a new SAP BEx query, and generate an OLAP universe • Make changes to the BEx query to see impact on universe objects

2009


295


BO100

BO100

Unit Summary You should now be able to: • Use multi-structure queries in OLAP Universes and Web Intelligence • Create smart measures in OLAP Universes • Describe custom calculations in OLAP Universes • Update the OLAP universe to reflect changes • Create and update OLAP Universes • Build a new SAP BEx query, and generate an OLAP universe • Make changes to the BEx query to see impact on universe objects

296


2009


Unit Summary

Test Your Knowledge


Refresh Structure only changes classes and objects technical names. Determine whether this statement is true or false.

□ □ 2.

True False

The tool used for updating universes with connections to a BEx query based on changes made to the BEx query is (Choose the correct answer) Choose the correct answer(s).

□ □ □ □ □ 3.

A B C D E

The OLAP Universe update Wizard The refresh structure Wizard The update universe Wizard The classes and objects update Wizard The BEx Universe update Wizard

The Wizard can detect additions made to classes and objects made by the user in addition to those automatically added in the BEx query Determine whether this statement is true or false.

□ □ 4.

True False

Objects named with Prefix L00 should never be renamed as this will impact reports currently using them. Determine whether this statement is true or false.

□ □ 5.

True False

If a user requires a name change made in the BEx query to be reflected in the universe, choose the best option in the wizard. Choose the correct answer(s).

□ □ □ □

2009

A B C D

Check Keep business name, and check Hide obsolete objects UnCheck Keep business name, and check Hide obsolete objects Check Keep business name, and check Delete obsolete objects Check Keep business name, and check Delete obsolete objects


297


BO100

6.

BO100

Adding an additional key figure in BEx query, always creates three additional objects in a new class under Key Figures Determine whether this statement is true or false.

□ □ 7.

True False

Adding an additional object originally a display attribute and now is a navigational attribute, is marked for deletion by the update wizard. Determine whether this statement is true or false.

□ □

298

True False


2009


Test Your Knowledge

Test Your Knowledge

Answers 1.

Refresh Structure only changes classes and objects technical names. Answer: False Not only classes and objects are changed but also conditions or filters, class names, objects, where clauses and select clauses.

2.

The tool used for updating universes with connections to a BEx query based on changes made to the BEx query is (Choose the correct answer) Answer: A The OLAP Universe update Wizard is the name of the window that is launched from the Designer Menu View -> Refresh Structure.

3.

The Wizard can detect additions made to classes and objects made by the user in addition to those automatically added in the BEx query Answer: True The wizard can detect additional objects added by users in the universe

4.

Objects named with Prefix L00 should never be renamed as this will impact reports currently using them. Answer: False Objects can be renamed without impact to later updates

5.

If a user requires a name change made in the BEx query to be reflected in the universe, choose the best option in the wizard. Answer: B If the name changes in BEx, it is best to uncheck keep business name

2009


299


BO100

6.

BO100

Adding an additional key figure in BEx query, always creates three additional objects in a new class under Key Figures Answer: False key figures such as counts will not require all three objects, these measures do not get unit and formatted value objects

7.

Adding an additional object originally a display attribute and now is a navigational attribute, is marked for deletion by the update wizard. Answer: True the original object is deleted and the new navigational objects are created.

300


2009


Test Your Knowledge



Unit Summary

301


2009


BO100

Unit Summary

302


2009


BO100

Crystal Reports and SAP ERP Unit Overview This unit provides you with an overview on the connectivity for Crystal Reports against SAP ERP.


Explain the functionality of Crystal Reports and its connectivity with SAP systems Create reports against SAP tables Create reports against ABAP functions Create reports against SAP InfoSets Create reports against SAP queries (ABAP queries)

Unit Contents Lesson: Crystal Reports Overview ............................................... 304 Lesson: Crystal Reports and SAP tables ........................................ 308 Exercise 12: Creating a new Crystal Report against SAP tables ........ 313 Lesson: Crystal Reports and ABAP Functions.................................. 319 Exercise 13: Creating a new Crystal Report against a ABAP Function . 323 Lesson: Crystal Reports and Classic InfoSets .................................. 330 Procedure: To create a new report based on the InfoSet connectivity . 331 Lesson: Crystal Reports and InfoSets Queries ................................. 335 Procedure: To create a new report based on the InfoSet query connectivity .................................................................................... 336

2009


303


Unit 7

BO100

Lesson: Crystal Reports Overview Lesson Overview This lesson provides you with an overview of Crystal Reports and its connectivity with SAP systems.


Explain the functionality of Crystal Reports and its connectivity with SAP systems

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: • • • • • • •

304

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


2009


Unit 7: Crystal Reports and SAP ERP

Lesson: Crystal Reports Overview

Figure 103: Crystal Reports Business Value

BusinessObjects XI Integration for SAP Solutions includes components that integrate Crystal Reports with your existing SAP systems.

2009


305


BO100

BO100

Figure 104: Crystal Reports: Connectivity Overview

Figure 105: Crystal Reports: Connection Methods

306


2009



Lesson: Crystal Reports Overview

Lesson Summary You should now be able to: • Explain the functionality of Crystal Reports and its connectivity with SAP systems

2009


307


BO100

BO100

Lesson: Crystal Reports and SAP tables Lesson Overview This lesson provides you with an overview on the connectivity for Crystal Reports against SAP ERP. You will use SAP ERP as a data source for Crystal Reports.


Create reports against SAP tables

Business Example You are a report designer and want to access and present any data regardless of where it resides. You want to create management reports, financial statements, and customer billings and distribute them in just about any way you want.

Crystal Reports and SAP ERP/ECC Enterprise reporting is often a starting point for business intelligence in companies. Crystal Reports provides comprehensive functionality to design, explore, visualize, and deliver compelling reports. With Crystal Reports, you can access just about any data regardless of where it resides, from packaged ERP and CRM applications, to relational database, to log files and Outlook. You can then create just about any type of report in any format you need, such as management reports, financial statements, and customer billings. The report can be distributed through the web in a PDF document, via email, on a mobile phone, or embedded directory in Microsoft Office. BusinessObjects XI Integration for SAP Solutions includes components that integrate Crystal Reports with your existing SAP systems Available SAP ERP/ECC data sources for Crystal Reports are: SAP ERP/ECC • • • •

308

Classic Infosets SAP Queries and InfoSet queries ABAP Functions Tables and Cluster (Open SQL)


2009



Lesson: Crystal Reports and SAP tables

Figure 106: Connectivity Overview

Crystal Reports and SAP tables At the most basic level, SAP ERP data is stored in a standard relational database system such as Oracle or SQL Server. This data is then abstracted in ERP to represent the various entities used by the ERP applications. These definitions, with the exception of ABAP functions and ABAP data clusters, are stored in the ABAP dictionary. The SAP Tables, Function, and Cluster connectivity provides access to these entities for reporting. The ABAP dictionary is referenced by the SAP Tables, Function, and Cluster connectivity in order to retrieve the definitions for each of the entities described above excluding ABAP functions and ABAP data clusters. Definitions of the entities include the long text of tables such as "Sales Document: Item Data" instead of the more cryptic name VBAP, the long text of fields such as "Material" instead of MATNR, and finally the type of the field itself (for example, numeric, text, date, and so on). The dictionary also maintains these definitions for each language that is configured in the system and provides the appropriate description according to the language the user has specified at login. The SAP Tables, Function, and Cluster connectivity provides access to several low-level objects within SAP, for example: transparent tables, pool and cluster tables, views, and ABAP data clusters and functions.

2009


309


BO100

BO100

Transparent tables This type of database object is similar to the traditional database table. Transparent tables contain the majority of the SAP application data. Most SAP applications use one or more transparent tables to store and retrieve business transactions. You can link these tables to other transparent tables in order to pull information from other application areas of the SAP system.

Pool and cluster tables Pool and cluster tables are made up of a logical grouping of other database tables. They are primarily used to store application configuration and control information rather than the actual application data. Because these tables are only a logical view of several tables combined, they are accessible only through the SAP Tables, Function, and Cluster connectivity. Native database access does not provide the same view of this data.

Views A view appears as one table with a list of fields, but actually consists of several tables linked together. Views provide a more abstract view of the data and allow you to build reports without having to worry about linking multiple tables in a report. Views are maintained within SAP and need to be configured before you use them for reporting.

Client field and language field features The following client field and language field features are specific to SAP tables and are relevant when linking multiple tables:

Client field Most tables in SAP contain a client field (native field name is MANDT). Because individual SAP systems can be configured to hold data for multiple clients, the client field specifies which rows of data in a table are for which clients. The SAP Tables, Function, and Cluster connectivity automatically handles this configuration. When you connect to SAP, you are prompted to provide your client number: this information eliminates the need to create a selection formula that filters the clients. As well, if a report contains multiple tables, you do not need to include a link on the client field—this, too, is automatically handled by the connectivity.

310


2009




Language field Some tables in SAP, specifically those that contain text descriptions, have multiple entries—one for each language that is installed on the SAP system. Consequently, with these tables you must create a selection formula on the Language Key (native field name is SPRAS) and specify the language that you want to display. For example: {table.spras} = "EN".

Troubleshooting Tips and Tricks • • •

2009

You can check in transaction STMS if the transports are installed. You can use transaction SE16 or SE11 to see the data of tables inside the SAP server. You can use transaction SQVI to simulate table linking.


311


BO100


312


2009


BO100


Exercise 12: Creating a new Crystal Report against SAP tables Exercise Objectives After completing this exercise, you will be able to: • Create a new report against SAP tables

Business Example You are a report designer and need to create Crystal Report objects using SAP tables.

Task: Follow the following steps to create a new report against SAP tables.

2009

1.

Start Crystal Reports.

2.

Create a new report using the SAP Tables, Cluster and Function connectivity.

3.

Filter the tables inside Data Dictionary (DD).

4.

Select the required fields from the table.

5.

Save the report to BusinessObjects Enterprise using your SAP user account.

6.

Create a folder for your SAP reports on the BusinessObjects Enterprise server.

7.

View the report in InfoView using your SAP user account.


313


BO100

BO100

Solution 12: Creating a new Crystal Report against SAP tables Task: Follow the following steps to create a new report against SAP tables. 1.

Start Crystal Reports. a)

2.

Select Start → Program → Crystal Reports 2008 → Crystal Reports 2008.

Create a new report using the SAP Tables, Cluster and Function connectivity. a)

Select the menu File → New Report → Standard Report.

b)

Expand the folder Create New Connection.

c)

Select SAP Table, Cluster or Function.

d)

Select the SAP system given by the instructor and click Next. Note: The list of available SAP systems is retrieved from SAP Logon.

e)

Enter the Client, Username, Password and click Next.

f)

Leave the check box Generate RFC trace files unchecked and click Finish. Note: The SAP Table, Cluster or Function connectivity is broken into three areas. The Data Cluster (CL) entry provides access to ABAP clusters; the Data Dictionary (DD) entry offers access to the ABAP Dictionary; and the ABAP Function module (FN) offers access to ABAP Functions.


314


2009




3.

Filter the tables inside Data Dictionary (DD). a)

Right-click the entry Data Dictionary (DD) and select the menu Options.

b)

Select Show Both under Tables and Fields.

c)

Enter SFLI% in the text box Table name LIKE.

Figure 107: Database Options

d)

Click OK.

e)

Right-click the entry Data Dictionary (DD) and click Refresh (F5).

f)

Double-click the entry Data Dictionary (DD). Note: The list of available tables is filtered based on the settings from the Options dialog.

4.

Select the required fields from the table. a)

Select the table SFLIGHT(Flight).

b)

Click the right arrow to move the table to the right-hand screen and click Next. Continued on next page

2009


315


BO100

c)

BO100

Select the following fields. Click the right arrow to bring them to the Fields to Display window. • • • •

Airline Code (CARRID) Flight Connection Number (CONNID) Flight date (FLDATE) Airfare (PRICE)

d)

Click Next.

e)

Define grouping by Airline Code and click the right arrow. Click Next.

f)

Leave the sum of airfare as the summary information to the report and click Next.

g)

Sort the group based on CARRID and click Next.

h)

Select No Chart and click Next.

i)

Define a record selection based on Airfare that is less than 3000 and click Next.

j)

Select No Template and click Finish.

k)

Preview the output of your report.

Figure 108: Preview report


316


2009




5.

6.

7.

2009

Save the report to BusinessObjects Enterprise using your SAP user account. a)

Select File →Save As.

b)

Select Enterprise

c)

Specify the System name, user name, and password.

d)

Select SAP as the authentication.

e)

Click OK.

Create a folder for your SAP reports on the BusinessObjects Enterprise server. a)

From the Save As window, navigate to SAP → 2.0 → CLNT800

b)

Create your own report folder if it has not been created yet. You may want to use a unique group number to identify this folder . For example: .

c)

Enter the filename for your report.

d)

Click Save.

View the report in InfoView using your SAP user account. a)

Select Program Files → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView.

b)

Enter the SAP System, SAP Client, User Name, and Password.

c)


d)

Click Log On.

e)

Click Document List

f)

Navigate to Public Folders → SAP → 2.0 → CLNT800 and go to your report folder.

g)

Right-click your report.

h)

Select View. The report displays in the window.


317


BO100

BO100

Lesson Summary You should now be able to: • Create reports against SAP tables

318


2009



Lesson: Crystal Reports and ABAP Functions

Lesson: Crystal Reports and ABAP Functions Lesson Overview This lesson provides you with information on the connectivity for Crystal Reports against ABAP functions.


Create reports against ABAP functions

Business Example While technically not a table, an ABAP function is often used in ERP reporting to provide calculations and to retrieve data that is based on parameters passed into the function (for example, an employee number passed to a function that returns the employee’s address). For this reason, the SAP Tables, Cluster and Function connectivity provides the ability to call ABAP functions and use their results in a report. ABAP functions are also useful in situations where complex pre-processing of the data must occur before viewing or in circumstances where you may wish to further optimize the performance of a query.

ABAP Functions For functions to be used in Crystal Reports, they must meet two conditions: • •

Functions must have defined return types for each of the output parameters. Functions must not have whole tables as input parameters.

The following examples illustrate the different types of ABAP functions that can be called by the SAP Tables, Cluster and Function connectivity and show how they appear in Crystal Reports.

Function with values as inputs and outputs Function F Importing VALUE(NAME) TYPE C VALUE(DEPARTMENT) TYPE C

2009


319


BO100

BO100

Exporting VALUE(Years_of_service) TYPE I VALUE(Age) TYPE I

This function would appear as a table called "F" with the following schema:

Field

Type

Name

String

Department

String

Years_of_service

Integer

Age

Integer

The first two fields, Name and Department, are input parameters. You must either link to them from another table (or function), or specify them with a record-selection formula (for example, {F.Name} = "Richard"). If table “T” contains departments that are over budget, you can link {T.Department} to {F.Department} and have a record-selection formula that specifies {F.Name} = "Richard". This formula will retrieve the years of service and age of all people named Richard in departments over budget.

Functions with structures as inputs and outputs Function F IMPORTING VALUE(ADDRESS) LIKE S_ADDR STRUCTURE S_ADDR EXPORTING VALUE(CONTACTINFO) LIKE S_CINFO STRUCTURE S_CINFO S_CINFO is defined as: PHONE(20) TYPE C EMAIL(100) TYPE C S_ADDR is defined as: STREET(100) TYPE C ZIPCODE(6) TYPE N

This function would appear as a table called “F” with the following schema:

320


2009




Field

Type

Address.street

String

Address.zipcode

Integer

ContactInfo.Phone

String

ContactInfo.eMail

String

As before, you must either link the street and zip code fields to or from another table, or define them in a record-selection formula.

Functions with a table as their output Function F IMPORTING VALUE(NAME) TYPE C EXPORTING VALUE(GENDER) TYPE C TABLES POSITIONS STRUCTURE S_POSN S_POSN is defined as: TITLE(20) TYPE C STARTDATE TYPE D

In this case, the function takes a name as an argument and returns the age and position of that person. Suppose that Tom’s gender is male, and that the Positions table returned by F for Tom contains the following values:

Title

StartDate

Mail Clerk

01/01/1993

Manager, Mail

03/04/1995

VIP, Mail

07/12/1998

When the function is called, the result will be a table called “F” that contains:

2009


321


BO100

BO100

Name

Gender

Positions.Title

Positions.StartDate

Tom

M

Mail Clerk

01/01/1993

Tom

M

Manager, Mail

03/04/1995

Tom

M

VIP, Mail

07/12/1998


322

You can check in transaction STMS if the transports are installed. You can use transaction SE37 to execute the function inside the SAP Server . Is the function RFC enabled?


2009




Exercise 13: Creating a new Crystal Report against a ABAP Function Exercise Objectives After completing this exercise, you will be able to: • Create a new report against ABAP Functions

Business Example You are a report designer and need to create Crystal Report objects using ABAP functions.

Task: Follow the following steps to create Crystal Reports objects using ABAP functions.

2009

1.


2.

Create a new report using the SAP Tables, Cluster and Function connectivity.

3.

Create a report based on the function BAPI_FLIGHT_GETLIST (Find list of flights).

4.

Select the fields for the report.

5.

Create a record selection for the Airline code UA.

6.


7.

Create a folder for your SAP reports on the BusinessObjects Enterprise server.

8.

View the report in InfoView using your SAP user account.


323


BO100

BO100

Solution 13: Creating a new Crystal Report against a ABAP Function Task: Follow the following steps to create Crystal Reports objects using ABAP functions. 1.


2.

Select Start → Program → Crystal Reports 2008 → Crystal Reports 2008.

Create a new report using the SAP Tables, Cluster and Function connectivity. a)


b)

Expand the folder Create New Connection.

c)

Select SAP Table, Cluster or Function.

d)

Select the SAP system given by the instructor and click Next. Note: The list of available SAP systems is retrieved from SAP Logon.

e)

Enter the Client, Username, Password and click Next.

f)

Leave the check box Generate RFC trace files unchecked and click Finish. Note: The SAP Table, Cluster or Function connectivity is broken into three areas. The Data Cluster (CL) entry provides access to ABAP clusters; the Data Dictionary (DD) entry offers access to the ABAP Dictionary; and the ABAP Function module (FN) offers access to ABAP Functions.


324


2009




3.

Create a report based on the function BAPI_FLIGHT_GETLIST (Find list of flights). a)

Right-click the entry FN (ABAP Function modules) and select the menu Options.

b)

Select Show Both under Tables and Fields.

c)

Enter BAPI_FLIGHT% in the text box Table name LIKE.

d)

Click OK.

e)

Right-click the entry FN (ABAP Function modules) and click Refresh (F5).

f)

Expand the entry FN (ABAP Function modules).

g)

Double-click the entry BAPI_FLIGHT_GETLIST. Note: The list of available tables is filtered based on the settings from the Options dialog.


2009


325


BO100

4.

BO100

Select the fields for the report. a)

Select the following fields. Click the right arrow to bring them to the Fields to Display window. • • • • • •

Airline Code (T_FLIGHT_LIST.AIRLINEID). Flight Connection Number (T_FLIGHT_LIST.CONNECTID). Flight Date (T_FLIGHT_LIST.FLIGHTDATE). Departure Airport (T_FLIGHT_LIST.AIRPORTFR). Destination Airport (T_FLIGHT_LIST.AIRPORTTO). Standard Listed airfare for flight (T_FLIGHT_LIST.PRICE).

Figure 109: Standard Report Creation Wizard

b)

Click Next.

c)

Skip the Grouping page and click Next.


326


2009




5.

Create a record selection for the Airline code UA. a)

Select BAPI_FLIGHT_GETLIST.T_FLIGHT_LIST.AIRLINEID(Airline Code) and click > to move it to the right window.

b)

Select is equal to from the selection list.

c)

Enter UA in the text box.

d)

Click Finish.


e) 6.

Preview the output of your report.



b)

Select Enterprise

c)


d)


e)

Click OK.


2009


327


BO100

7.

8.

328

BO100

Create a folder for your SAP reports on the BusinessObjects Enterprise server. a)


b)

Create your own report folder if it has not been created yet. You may want to use a unique group number to identify this folder . For example: .

c)


d)

Click Save.

View the report in InfoView using your SAP user account. a)


b)


c)


d)

Click Log On.

e)

Click Document List

f)

Navigate to Public Folders → SAP → 2.0 → CLNT800 and go to your report folder.

g)

Right-click on your report.

h)



2009




Lesson Summary You should now be able to: • Create reports against ABAP functions

2009


329


BO100

BO100

Lesson: Crystal Reports and Classic InfoSets Lesson Overview This lesson provides you with information on the connectivity for Crystal Reports with SAP InfoSets.


Create reports against SAP InfoSets

Business Example The combined InfoSet/ABAP query driver allows you to use an existing SAP query or InfoSet as a data source for a Crystal Report object. The SAP query or InfoSet is built within SAP by a content expert, who then makes the data available to the business user. Through the Crystal Reports connectivity the user can design multiple reports by quickly referencing the same query or InfoSet. Because an InfoSet can be built on top of a logical database in SAP, it can inherit all of the business logic and security that is programmed into the logical database.

Crystal Reports and Classic InfoSets Reports that are based on SAP queries and InfoSets behave similarly to reports that are based on stored procedures in mainstream databases. You can insert subreports that are based on different queries or InfoSets into the main report as well. Note: If you want to join two or more InfoSets or SAP queries, you should consider creating a brand new InfoSet or SAP query instead. The new join will be processed on the SAP server allowing the report to respond faster. Note: Your SAP queries and InfoSets may contain parameters that you can use to limit the data that is returned from the SAP system. For example, you might specify a date range to get data for only a certain period. If parameters are included in the SAP query or InfoSet, Crystal Reports prompts you to specify the values that you want to include in the query.

330


2009



Lesson: Crystal Reports and Classic InfoSets

To create a new report based on the InfoSet connectivity 1.

Start Crystal Reports

2.


3.

Open the folder Create New connection.

4.

Select SAP InfoSets from the list of available data sources.

5.

Specify the required SAP server in the list of available SAP systems.

6.

Enter the Client, User name, and Password.

7.

Click Finish.

8.

Select the newly created server entry


2009


331


BO100

BO100

Figure 111: Classic InfoSets

Note: The SAP InfoSet connectivity offers the connectivity with Classic InfoSets and SAP Queries. Classic InfoSets can be assigned to a Global or a Local environment. The Global environment means that the InfoSet is available across all SAP clients from the underlying SAP system. The Local environment means that the InfoSet is only available on the client the InfoSet was created. 9.

Select Classic InfoSet.

10. Double-click the Global (G) entry. 11. Click the right arrow to move the InfoSet to the right-hand screen. 12. Click Next. 13. Select the needed fields and click the right arrow. Click Next to continue. 14. If required, define grouping by selecting the field and clicking the right arrow. Click Next to continue. 15. If required, define a record selection. Click Next to continue. 16. Click Finish.

332


2009



Lesson: Crystal Reports and Classic InfoSets


2009

You can check in transaction STMS if the transports are installed. You can verify the InfoSet in transaction SQ02. You can verify if the InfoSet and your user are in the correct user groups in transaction SQ03.


333


BO100

BO100

Lesson Summary You should now be able to: • Create reports against SAP InfoSets

334


2009



Lesson: Crystal Reports and InfoSets Queries

Lesson: Crystal Reports and InfoSets Queries Lesson Overview This lesson provides you with information on the connectivity for Crystal Reports against SAP queries (ABAP queries).


Create reports against SAP queries (ABAP queries)

Business Example Crystal Reports is able to leverage the outcome of the SAP query tool with the combined InfoSet and SAP query connectivity.

Crystal Reports and InfoSet queries The SAP query tool allows you to create SAP queries and InfoSet queries in a single tool. The query itself leverages the InfoSet as a data source, therefore the InfoSet needs to be created and be assigned to the proper user groups before you start creating the SAP query. The difference between an InfoSet query and an SAP query is the actual tool itself and the output format. The InfoSet query tool is a single-screen tool whereas the SAP query tool is a screen-byscreen approach. On the output format the SAP query offers more capabilities like a ranked and statistical list than the InfoSet query which only offers a basic list output. Crystal Reports is able to leverage the outcome of the SAP query tool with the combined InfoSet and SAP query connectivity.

2009


335


BO100

BO100

To create a new report based on the InfoSet query connectivity 1.

Start Crystal Reports

2.


3.

Open the folder Create New connection.

4.

Select SAP InfoSets from the list of available data sources.

5.

Specify the required SAP server in the list of available SAP systems.

6.

Enter the Client, User name, and Password.

7.

Click Finish.

8.

Select the newly created server entry Note: The SAP InfoSet connectivity offers the connectivity with Classic InfoSets and SAP Queries. Classic InfoSets can be assigned to a Global or a Local environment. The Global environment means that the InfoSet is available across all SAP clients from the underlying SAP system. The Local environment means that the InfoSet is only available on the client the InfoSet was created.

9.

Select SAP Query.


336


2009



Lesson: Crystal Reports and InfoSets Queries

Figure 112: SAP Query

10. Double-click the Global (G) entry. 11. Click the right arrow to move the InfoSet to the right-hand screen. 12. Click Next. 13. Select the needed fields and click the right arrow. Click Next to continue. 14. If required, define grouping by selecting the field and clicking the right arrow. Click Next to continue. 15. If required, define a record selection. Click Next to continue. 16. Click Finish.


2009

You can check in transaction STMS if the transports are installed. You can verify the SAP Query in transaction SQ01. You can verify if the InfoSet and your user are in the correct user groups in transaction SQ03.


337


BO100

BO100

Lesson Summary You should now be able to: • Create reports against SAP queries (ABAP queries)

338


2009



Unit Summary

Unit Summary You should now be able to: • Explain the functionality of Crystal Reports and its connectivity with SAP systems • Create reports against SAP tables • Create reports against ABAP functions • Create reports against SAP InfoSets • Create reports against SAP queries (ABAP queries)

2009


339


BO100

Unit Summary

340


2009


BO100

Test Your Knowledge


Which of the following areas can be found under the SAP Table, Cluster or Function connectivity in Crystal Reports? Choose the correct answer(s).

2.

□

A

□ □ □

B C D

CL (Data Clusters), DD (Data Dictionary), and FN (ABAP Function modules) CL (Cluster Lists), DD (Data Dictionary), and FN (Function Nodes) I (Classic Infoset), and Q (SAP Query) G (Global, client independent, objects), and L (Local, client dependent, objects)

What is the primary use of ABAP function in ERP reporting? Choose the correct answer(s).

2009

□

A

□

B

□

C

□

D

To maintain the definitions for each language that is configured in the system. To provide calculations to retrieve data that is based on parameters into the function. To provide access to several low-level objects within SAP such as transparent tables, pool and cluster tables. To provide a more abstract view of the data and allow you to build reports without having to worry about linking multiple tables in a report.


341


BO100

BO100

Answers 1.

Which of the following areas can be found under the SAP Table, Cluster or Function connectivity in Crystal Reports? Answer: A Correct answer is A.

2.

What is the primary use of ABAP function in ERP reporting? Answer: B Correct answer is B.

342


2009


Test Your Knowledge



Unit Summary

343


2009


BO100

Unit Summary

344


2009


BO100

Crystal Reports and SAP BW - Part 1 Unit Overview This unit provides you with an overview of the connectivity for Crystal Reports against SAP BW. You will learn SAP BW metadata and how to use SAP BW queries in Crystal Reports.

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

Describe the metadata from SAP BW inside Crystal Reports Create reports against SAP BW queries Create reports against SAP BW queries with SAP variables Create reports against SAP BW queries with multiple structures

Unit Contents Lesson: SAP BW Metadata in Crystal Reports ................................. 346 Lesson: Crystal Reports with simple SAP BW queries ........................ 355 Exercise 14: Creating a new report against a BW Query with display attributes ......................................................................... 359 Lesson: Crystal Reports against advanced SAP BW queries ................ 364 Exercise 15: Creating a new report against an SAP BW query with a mandatory SAP variable ....................................................... 369

2009


345


Unit 8

BO100

Lesson: SAP BW Metadata in Crystal Reports Lesson Overview This lesson provides you with an overview of Crystal Reports in combination with SAP BW queries.


Describe the metadata from SAP BW inside 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.

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

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

For SAP BW, Crystal Reports can directly access ODS, as well as use Open SQL, BEx Queries, and InfoCubes. In other words, Crystal Reports provides flexibility for delivery information and data at multiple levels.

346


2009


Unit 8: Crystal Reports and SAP BW - Part 1

Lesson: SAP BW Metadata in Crystal Reports

Figure 113: Connectivity Overview

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

2009

BW Query element

Crystal Reports 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.)

Restricted Key Figure

Measure element in the folder Keyfigure (Information about the details of the restricted keyfigure is not available in Crystal Reports.)

Filter

Filters will be applied to the underlying query but are not visible in the Crystal Reports designer.


347


BO100

BO100

BW Query element

Crystal Reports element


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 114: SAP BW query in the BEx Query Designer

The rows of this query include several characteristics and the columns several keyfigures. On the left side, the actual cube structure is shown with the cube dimensions (not to be confused with characteristics).

348


2009




In the image you can identify one dimension and tree characteristics. The dimension is Customer and the characteristics are Region, Sold-to party, Sold-toPartyCountry Building a Crystal Report on top of such an SAP BW query will result in the following elements:

Figure 115: Field Explorer in Crystal Reports

• • •

Each characteristic in the query will result in an element in the field explorer with a key and a description item (For example: Region Key and Region Name). Each characteristic will also generate a Node ID and a Parent Node ID which can be used for hierarchical reporting. Each characteristic will also generate a Member Unique Name field which represents the technical key value.

Display attributes and navigational attributes Display attributes are InfoObjects which are logically assigned or subordinated to a characteristic. For example, the characteristic Sold-to party has two attributes: • •

2009

Country Postal Code


349


BO100

BO100

In SAP reporting tools the display attributes can only be used in combination with the actual characteristic. This means the attribute Postal Code can only be shown in the SAP reporting tool in combination with the characteristic customer. Characteristics can be defined as navigational attributes in the BW cube, which then makes these attributes available for navigational purposes in the reporting tools. Navigational attributes are treated identically to a characteristic. The following screen shows an SAP BW query in the BEx Query Designer.

Figure 116: Display attributes in BEx Query Designer

The row structure includes a characteristic Customer (Sold-to party) with four display attributes (Country, Postal Code, City Name, Account group, Customer Classific.). In addition the BW query contains two navigational attributes in the rows: Region, Sold-toPartyCountry. Note: A navigational attribute can easily be identified by the double underscore (“__”) in the technical name of the navigational attribute. Building a Crystal Report object on top of such an SAP BW query will result in the following elements:

350


2009




Figure 117: Field Explorer in Crystal Reports with navigational attributes

Note: • •

•

Each characteristic in the query will result in an element in the field explorer with a key and a description field. Each navigational attribute in the query will result in an element in the field explorer with a key and a description item (for example Region, Sold-toPartyCountry). Crystal Reports will include all available display attributes for the characteristic and not only the display attributes that are included in the SAP BW query.

Keyfigures, units, and currencies Each keyfigure used in an SAP BW query can have up to three elements: • • •

Numeric value of the keyfigure Unit or currency information Formatted value, representing the user-specific formatting

The image shows the result of two keyfigures in Crystal Reports:

2009


351


BO100

BO100

Figure 118: Two keyfigures in Crystal Reports

Note: • • •

Each keyfigure is represented with a field in a group called Key Figures In the case the keyfigure is configured in SAP BW with a unit, an additional field will be added representing the unit information The formatted value represents the numeric value formatted as a string value following the user-specific formatting settings

Hierarchies Hierarchies can be activated for characteristics in the BEx Query Designer and offer the user 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.

352


2009




Figure 119: Field Explorer in Crystal Reports with hierarchy

Note: •

2009

A hierarchy results in a parent-child relationship


353


BO100

BO100

Lesson Summary You should now be able to: • Describe the metadata from SAP BW inside Crystal Reports

354


2009



Lesson: Crystal Reports with simple SAP BW queries

Lesson: Crystal Reports with simple SAP BW queries Lesson Overview In this lesson, you will learn about the connectivity of Crystal Reports with simple SAP BW queries.


Create reports against SAP BW queries

Business Example You are a report designer and need to create a Crystal Report object on top of an SAP BW query.

Simple SAP BW queries with Crystal Reports When creating new reports against SAP BW there are two options: • •

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 off 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:

2009


355


BO100

BO100

Figure 120: 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 121: BW MDX Driver

Note: The SAP BW MDX Query connectivity is the more enhanced version of the Crystal Reports connectivity with SAP BW cubes and SAP BW queries. 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.

356


2009




Using the Database Explorer Crystal Reports lists the two SAP BW query connectivities in the standard Database Explorer.

Crystal Reports and display attributes Display attributes are used in SAP BW to provide additional information but this information is not available for a typical OLAP navigation (slice-and-dice) in the SAP reporting tools. The information can only be displayed as part of the result in combination with the actual characteristic itself. For example: The characteristic customer is configured with a display attribute Country. Country can be displayed only in combination with the characteristic customer and Country cannot be used for navigation. In Crystal Reports these display attributes result in fields underneath the corresponding characteristic. Display attributes can be used as standalone without the need to display the actual characteristic in the report.

2009


357


BO100

BO100

Figure 122: Display attributes

Note: The technical names of display attributes follow a naming convention: [1XXXX] represents the short description. [2XXXX] represents the key value. [4XXXX] represents the long description. [5XXXX] represents the medium description. “XXXX” in this content needs to be replaced with the technical name of the characteristic therefore [50MATERIAL] would be the medium description of the characteristic 0MATERIAL (Customer).

358


2009




Exercise 14: Creating a new report against a BW Query with display attributes Exercise Objectives After completing this exercise, you will be able to: • Create a new report against an SAP BW query with display attributes

Business Example You are a report designer and need to create a Crystal Report object on top of an SAP BW query.

Task: Follow the following steps to create a new report against an SAP BW query with display attributes: 1.


2.

Create a new report using the SAP BW MDX query connectivity.

3.

Select the menu SAP → Create New Report from a Query.

4.

Connect to the Training-System using the credentials given to you by your instructor.

5.

Select the BO100 Query 01 (technical name: BO100_Q01_1) query.

6.

Make sure that the field descriptions will be shown in the Field Explorer instead of the field names.

7.

Create a report that includes attributes for Sold-to (Key, Name), Sales Organization (Company Code), Material Medium Name (Name, Weight).

8.

Preview the report.

9.

Publish the report to your BusinessObjects Enterprise system

10. View the report with the SAP account in InfoView.

2009


359


BO100

BO100

Solution 14: Creating a new report against a BW Query with display attributes Task: Follow the following steps to create a new report against an SAP BW query with display attributes: 1.

2.

3.


Double-click on SAP Logon Pad and make sure that you have a entry for the BW system

b)

From the Windows Desktop: Start → Programs → Crystal Reports 2008.

Create a new report using the SAP BW MDX query connectivity. a)

Select the menu SAP → Settings.

b)

Select the check box Use MDX Driver with support for Multiple structures.

c)

Click OK.

Select the menu SAP → Create New Report from a Query. a)

4.

5.

Connect to the Training-System using the credentials given to you by your instructor. a)

Enter Client, Username, and Password. Select the desired language.

b)

The SAP standard open/save dialog will show up and offer the user to select a query from roles and InfoAreas.

Select the BO100 Query 01 (technical name: BO100_Q01_1) query. a)

Click the Find icon and search for T_BO100_Q01_1.

b)

Click OK.


360


2009




6.

Make sure that the field descriptions will be shown in the Field Explorer instead of the field names. a)

Change Crystal Reports Settings: File → Options.

b)

Click the Database tab and choose the option Show Both.

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_Q01.

g)

Take a look at the field descriptions within the Field Explorer. Note: The technical names of display attributes follow a naming convention: • • • •

[1XXXX] represents the short description. [2XXXX] represents the key value. [4XXXX] represents the long description. [5XXXX] represents the medium description. “XXXX” in this content needs to be replaced with the technical name of the characteristic therefore [50SOLD_TO] would be the medium description of the characteristic 0SOLD_TO (Customer).

7.

Create a report that includes attributes for Sold-to (Key, Name), Sales Organization (Company Code), Material Medium Name (Name, Weight). a)

8.

Drag the fields from the Field Explorer to the details section of the report.

Preview the report. a)

SelectView → Preview.


2009


361


BO100

9.

BO100

Publish the report to your BusinessObjects Enterprise system a)


b)

Select the Enterprise tab

c)

Select the user folder where you want to save the report. Select SAP → 2.0 →CLNT900 .

d)

Create your won report folder GR## if it has not yet been created.

e)

Enter the filename for your report GR##_SalesOrderReport

f)

Click Save.

10. View the report with the SAP account in InfoView.

362

a)

Lauch Infoview from Programs → BusinessObjects XI 3.1 → BuinessObjects Enterprise Client Tools →BusinessObjects Enterprise Java InfoView.

b)

Enter the user name and password given by the instructor. Select SAP as the authentication type.

c)


d)

Double-click your report to view its content.


2009




Lesson Summary You should now be able to: • Create reports against SAP BW queries

2009


363


BO100

BO100

Lesson: Crystal Reports against advanced SAP BW queries Lesson Overview In this lesson, you will learn about the connectivity of Crystal Reports against more complex SAP BW queries.


Create reports against SAP BW queries with SAP variables Create reports against SAP BW queries with multiple structures

Business Example You are a report designer and need to create a Crystal Report object on top of an SAP BW query with mandatory SAP variables.

Crystal Reports and SAP 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 send 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. The order of priority for the SAP Variable is: 1. 2. 3.

364

Personalized Variable value. Default Variable value. Manually entered value.


2009



Lesson: Crystal Reports against advanced SAP BW queries

For example: Crystal Reports created a report with an optional prompt based on an SAP BW query with an optional variable and the user is setting the value to Null. 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.

Figure 123: Crystal Report Based on BW Query with Variable

Crystal Reports and multi-structure queries The BEx Query Designer allows creating a query that contains 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 then lead to a situation where the query design builds a well designed grid for the result set.

2009


365


BO100

BO100

Figure 124: Multi-structure queries

The query in the figure above contains two structures: • • •

The first structure is a grouping of countries into specified groups: USA, UK, and Germany. The second structure contains three keyfigures, one of them 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 keyfigures into separate fields and the structure representing the special grouping becomes a single field in Crystal Reports.

366


2009




Figure 125: Multi-structure in Crystal Reports

In the given example the structure for the specific grouping of countries appears as one field in Crystal Reports and the three keyfigures 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.

2009


367


BO100


368


2009


BO100


Exercise 15: Creating a new report against an SAP BW query with a mandatory SAP variable Exercise Objectives After completing this exercise, you will be able to: • Create a new report against an SAP BW query with a mandatory prompt

Business Example You are a report designer and need to create a Crystal Report object on top of an SAP BW query with mandatory SAP variables.

Task: Follow the following steps to create a new report against an SAP BW query with mandatory prompting: 1.

Start the SAP BW Query Designer.

2.

Open the BO100 mandatory variable T_BO100_Q04_1 (technical name: T_BO100_Q04_1) query. Note: These two steps are for information purposes to compare the retrieved metadata in Crystal Reports.

3.


4.


5.


6.

Select the BO100 Mandatory variable (technical name: T_BO100_Q04_1) query.

7.


8.

Create a report that includes attributes for Sold-to party (Key), Sold-to party (Medium Name), Material (Key), Material (Medium Name), Sales Volume (MC) Value, and Sales Volume EUR Formatted Value.

9.

Preview the report with different values for the prompt. Continued on next page

2009


369


BO100

BO100

10. Save the report to BusinessObjects Enterprise using your SAP user account. 11. Create a folder for your SAP reports on the BusinessObjects Enterprise server. 12. View the report in InfoView using your SAP user account.

370


2009




Solution 15: Creating a new report against an SAP BW query with a mandatory SAP variable Task: Follow the following steps to create a new report against an SAP BW query with mandatory prompting: 1.

Start the SAP BW Query Designer. a)

2.

Open the BO100 mandatory variable T_BO100_Q04_1 (technical name: T_BO100_Q04_1) query. Note: These two steps are for information purposes to compare the retrieved metadata in Crystal Reports. a)

3.

4.

5.


Double-click on SAP Logon Pad and make sure that you have a entry for the BW system.

b)




b)


c)

Click OK.

d)




b)



2009


371


BO100

6.

BO100

Select the BO100 Mandatory variable (technical name: T_BO100_Q04_1) query. a)

Click the Find icon and search for BO100 mandatory variable.

b)

Click OK. Note: 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.

7.

8.



b)

Click the Database tab and select the Show Description option.

c)

Click OK.

d)


e)


f)

Click the plus sign in front of BO100 Mandatory variable.

g)

Take a look at the field descriptions within the Field Explorer.

Create a report that includes attributes for Sold-to party (Key), Sold-to party (Medium Name), Material (Key), Material (Medium Name), Sales Volume (MC) Value, and Sales Volume EUR Formatted Value. a)

9.

Select the fields from the Field Explorer and drag them to the report detail area.

Preview the report with different values for the prompt. a)

Select the menu View → Print Preview.

b)

Select a value for the prompt.

c)

Click OK.


372


2009




10. Save the report to BusinessObjects Enterprise using your SAP user account. a)


b)

Select Enterprise

c)


d)


e)

Click OK.

11. Create a folder for your SAP reports on the BusinessObjects Enterprise server. a)


b)

Create your own report folder GR## if it has not been created yet.

c)


d)

Click Save.

12. View the report in InfoView using your SAP user account.

2009

a)


b)


c)


d)

Click Log On.

e)

Click Document List

f)

Navigate to Public Folders → SAP → 2.0 → CLNT900.

g)


h)



373


BO100

BO100

Lesson Summary You should now be able to: • Create reports against SAP BW queries with SAP variables • Create reports against SAP BW queries with multiple structures

374


2009



Unit Summary

Unit Summary You should now be able to: • Describe the metadata from SAP BW inside Crystal Reports • Create reports against SAP BW queries • Create reports against SAP BW queries with SAP variables • Create reports against SAP BW queries with multiple structures

2009


375


BO100

Unit Summary

376


2009


BO100

Test Your Knowledge


Which of the following SAP BW data sources can Crystal Reports directly access? Choose the correct answer(s).

□ □ □ □ 2.

A B C D

BEx Queries and BW cubes only ODS tables and BW queries only Tables and cluster (Open SQL) and BEx Queries only ODS, Tables and cluster (Open SQL), BEx Queries, and InfoCubes.

What is the main advantages of the MDX when comparing it to the older query driver for accessing BW queries. Choose the correct answer(s).

2009

□

A

□ □

B C

□

D

Access to Display attributes, quieres with 2 structures, and enhanced treatment of hierarchies. Export the Crystal Report to SAP BusinessObjects Enterprise system. Start and restart SAP BusinessObjects Enterprise Central Management Server. Authenticate report designers using single-sign on SAP account.


377


BO100

BO100

Answers 1.

Which of the following SAP BW data sources can Crystal Reports directly access? Answer: D Correct answer is D.

2.

What is the main advantages of the MDX when comparing it to the older query driver for accessing BW queries. Answer: A Correct answer is A.

378


2009


Test Your Knowledge



Unit Summary

379


2009


BO100

Unit Summary

380


2009


BO100

Crystal Reports and SAP BW - Part 2 Unit Overview This unit explains how to use SAP BW queries with hierarchies and variables in Crystal Reports.

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

Describe the differences between BW MDX and BW Query driver in regards to hierarchies Create simple reports with SAP hierarchies Use formulas for hierarchical reporting Create reports with a hierarchy variable Create reports with a hierarchy node variable Create reports against a BW cube directly Create reports with keydate variables Describe variable personalization

Unit Contents Lesson: Crystal Reports with SAP BW queries with hierarchies ............. 382 Exercise 16: Creating a new report with hierarchy variable .............. 387 Lesson: Crystal Reports against SAP BW cubes............................... 394 Lesson: Crystal Reports and keydate variables ................................ 398 Exercise 17: Creating a new report with a keydate variable.............. 399 Lesson: SAP variable personalization ........................................... 406

2009


381


Unit 9

BO100

Lesson: Crystal Reports with SAP BW queries with hierarchies Lesson Overview In this lesson, you will learn about the connectivity of Crystal Reports using SAP BW queries containing hierarchies.

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

Describe the differences between BW MDX and BW Query driver in regards to hierarchies Create simple reports with SAP hierarchies Use formulas for hierarchical reporting Create reports with a hierarchy variable Create reports with a hierarchy node variable

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 Hierarchies The activated hierarchy from the underlying SAP BW query will result in a parent-child relationship being represented in Crystal Reports.

382


2009



Lesson: Crystal Reports with SAP BW queries with hierarchies

Figure 126: 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.

2009


383


BO100

BO100

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

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. The BW MDX driver only offers a parent child relationship.

Formulas for hierarchical reporting Crystal Reports offers some additional formulas and functions that allow the user to create a better report design and provide conditional formatting even in the context of a hierarchy.

Formula Hierarchy Level The first formula for hierarchical reporting is the formula HierarchyLevel(). The formula HierarchyLevel() allows retrieving the level of the hierarchical grouping. The formula needs a GroupLevel as input. The following is an example for the formula syntax assuming Material Node ID is the grouping field in the report: HierarchyLevel ( GroupingLevel ( {Material Node ID}) )

384


2009




Count Hierarchical Children The second formula is CountHierarchicalChildren() which allows counting the number of children of a hierarchy level. The formula needs a GroupLevel as input. The following is an example for the formula syntax assuming Material Node ID is the grouping field in the report: CountHierarchicalChildren ( GroupingLevel ({Material Node ID}) )

The count of children refers to the number of children in the hierarchy level.

Conditional formatting with hierarchy level With the formulas the report can be conditionally formatted so that the group headings follow an indentation and the keyfigures stay aligned.

Crystal Reports with hierarchy variables 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 with hierarchy node variables Hierarchy node variables allow the user to select a specific node of the chosen hierarchy and use the hierarchy node as a filter for the data that is being returned from the SAP BW query.

2009


385


BO100


386


2009


BO100


Exercise 16: Creating a new report with hierarchy variable Exercise Objectives After completing this exercise, you will be able to: • Create a new report with a hierarchy variable

Business Example You are a report designer and need to create a Crystal Report object using SAP BW hierarchies variables.

Task: Follow the following steps to create a new report with a hierarchy variable: 1.

Launch Crystal Reports to create an empty report. Make sure you have a entry for SAP system in SAP Logon Pad.

2.


3.

Choose the BO100 hierarchy variable (technical name: T_BO100_Q08_1) query.

4.


5.

Insert a group based on the Material parent-child relationship.

6.

Create a hierarchical grouping based on the Material parent-child relationship.

7.

Create a summary for the Sales Volume (MC).

8.

Preview your report with different values for the hierarchy and hierarchy node variable.

9.


10. Create a folder for your SAP reports on the BusinessObjects Enterprise server. 11. View the report in InfoView using your SAP user account.

2009


387


BO100

BO100

Solution 16: Creating a new report with hierarchy variable Task: Follow the following steps to create a new report with a hierarchy variable: 1.

2.

3.

Launch Crystal Reports to create an empty report. Make sure you have a entry for SAP system in SAP Logon Pad. a)

Double-click SAP Logon Pad and make sure that you have a entry for the BW system

b)




b)


c)

Click OK.

d)

Select SAP → Create New Report from Query.

e)

Connect to the assigned BW training system using the credentials: Client 900, User BO100-## and assigned password.

f)

Click OK.

Choose the BO100 hierarchy variable (technical name: T_BO100_Q08_1) query. a)

Click the Find icon and search for T_BO100_Q08_1.

b)

Click OK.


388


2009




4.

5.

6.


Change Crystal Reports Settings to: File → Options.

b)

Click the Database tab and choose the Option Show Description.

c)

Click OK.

d)


e)


f)

Click the plus sign in front of BO100 Hierarchy variable.

g)


Insert a group based on the Material parent-child relationship. a)

Select the menu Insert → Group.

b)

Select the Material Node ID field.

c)


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.


2009


389


BO100

7.

BO100

Create a summary for the Sales Volume (MC). a)

Select the menu Insert → Summary.

b)

Select Sales Volume (MC) as the field to summarize.

c)

Select Sum as the calculation option.

d)

Select Group #1 for the summary location. 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. Note: 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.

e)

Click OK.

f)

Move the summary to the Group Header #1.

g)

Hide the Group Footer #1 in the report design.


390


2009




8.

Preview your report with different values for the hierarchy and hierarchy node 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. Note: Select Product Hierarchy for Material MARA.

d)

Click OK.


9.



b)

Select Enterprise

c)


d)


e)

Click OK.


2009


391


BO100

BO100



b)

Create your own report folder if it has not been created yet.

c)


d)

Click Save.


392

a)


b)


c)


d)

Click Log On.

e)

Click Document List

f)


g)


h)



2009




Lesson Summary You should now be able to: • Describe the differences between BW MDX and BW Query driver in regards to hierarchies • Create simple reports with SAP hierarchies • Use formulas for hierarchical reporting • Create reports with a hierarchy variable • Create reports with a hierarchy node variable

2009


393


BO100

BO100

Lesson: Crystal Reports against SAP BW cubes Lesson Overview In this lesson, you will learn how to create Crystal reports against a BW cube.


Create reports against a BW cube directly

Business Example Your business reporting group requires a report that queries against a BW cube.

Crystal Reports against SAP BW cubes When creating a report against a BW cube directly the list of available fields will be larger than the list of fields for an SAP BW query. Note: Accessing a BW cube directly is only available for the BW MDX driver and only when using the Crystal Reports Standard report export. This functionality is not available using the SAP toolbar. The additional fields when connecting against a cube are inherited from the fact that the report now contains:

394


2009



Lesson: Crystal Reports against SAP BW cubes

Figure 129: SAP BW cubes

• • • •

2009

All characteristics from the underlying cube. All available hierarchies for all characteristics. All display attributes. All keyfigures.


395


BO100

BO100

Figure 130: Field Explorer in Crystal Reports

The figure shows how a characteristic and all its hierarchies will be displayed in the Field Explorer in Crystal Reports. The characteristic Material is represented with nine hierarchies which are grouped underneath the actual characteristic. The key and description values underneath the actual characteristic represent the non-hierarchical display. When connecting against a cube directly, the following metdata is not available: • • • •

396

Navigational attributes Restricted keyfigures Calculated keyfigures SAP variables


2009



Lesson: Crystal Reports against SAP BW cubes

Lesson Summary You should now be able to: • Create reports against a BW cube directly

2009


397


BO100

BO100

Lesson: Crystal Reports and keydate variables Lesson Overview In this lesson, you will learn how a keydate variable is used in the Crystal Reports designer.


Create reports with keydate variables

Business Example You are a report designer and need to create a report against an SAP BW system with keydate variables.

Keydate variables in Crystal Reports A keydate variable can influence the following metadata and data of the underlying SAP BW system: • • •

Master data. List of available hierarchies. Hierarchy structures.

A keydate variable in Crystal Reports is shown as a date variable with a calendar control and each time the user changes the date entry, Crystal Reports will send the new keydate to the underlying SAP BW server to retrieve the correct data.

398


2009



Lesson: Crystal Reports and keydate variables

Exercise 17: Creating a new report with a keydate variable Exercise Objectives After completing this exercise, you will be able to: • Create a report against an SAP BW query with a keydate variable

Business Example You are a report designer and need to create a Crystal Report object using an SAP BW query with a keydate variable.

Task: Follow the following steps to create a new report against an SAP BW query with display attributes: 1.


2.


3.


4.


5.

Select the BO100 keydate variable (technical name: BO100_Q11_1) query.

6.


7.

Create a hierarchical grouping for the Material characteristic.

8.

Include the Sales Volume (MC) and build a summary for the group.

9.

Preview the report.

10. Enter different dates for the keydate variable. 11. Save the report to BusinessObjects Enterprise using your SAP user account. 12. Create a folder for your SAP reports on the BusinessObjects Enterprise server. 13. View the report in InfoView using your SAP user account.

2009


399


BO100

BO100

Solution 17: Creating a new report with a keydate variable Task: Follow the following steps to create a new report against an SAP BW query with display attributes: 1.

2.

3.


Double-click on SAP Logon Pad and make sure that you have a entry for the BW system

b)




b)


c)

Click OK.

Select the menu SAP → Create New Report from a Query. a)

4.

5.



b)


Select the BO100 keydate variable (technical name: BO100_Q11_1) query. a)

Click the Find icon and search for BOO100 keydate variable query.

b)

Click OK.


400


2009




6.

7.



b)

Click the Database tab and choose the Option .

c)

Click OK.

d)


e)


f)

Click the plus sign in front of T_BO1001_T_BO100_Q11_1.

g)


Create a hierarchical grouping for the Material characteristic. a)

Select the menu Insert → Group.

b)

Sorted the group by Material.

c)


d)

Select the Customize Group Name Field check box.

e)

Select the material medium name.


2009


401


BO100

8.

BO100

Include the Sales Volume (MC) and build a summary for the group. a)

Select the menu Insert → Summary.

b)

Select Sales Volume (MC) as the field to summarize.

c)

Select Sum as the calculation option.

d)

Select Group #1 for the summary location. 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. Note: 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.

e)

Click OK.

f)

Move the summary to the Group Header #1.

g)

Hide the Group Footer #1 in the report design.


402


2009




9.

Preview the report. a)

SelectView → Preview.

Figure 131: Keydate variable

10. Enter different dates for the keydate variable. a)

Enter a date value for the keydate variable.

b)

Click OK.

c)

Select the menu Report → Refresh Report Data.

d)

Enter a different date value for the keydate variable.

e)

Click OK.

11. Save the report to BusinessObjects Enterprise using your SAP user account. a)


b)

Select Enterprise

c)


d)


e)

Click OK.


2009


403


BO100

BO100



b)

Create your own report folder if it has not been created yet.

c)


d)

Click Save.


404

a)


b)


c)


d)

Click Log On.

e)

Click Document List

f)


g)


h)



2009




Lesson Summary You should now be able to: • Create reports with keydate variables

2009


405


BO100

BO100

Lesson: SAP variable personalization Lesson Overview In this lesson, you will learn about variable personalization and how this feature is used in Crystal Reports and SAP BusinessObjects Enterprise.


Describe variable personalization

Business Example Your business reporting group requires variable personalization in Crystal reports when querying against SAP BW InfoProviders.

What is personalization? Reports that are based on BW queries potentially make use of variables, which contain the values that BW queries use to limit or specify the data that they return. Typically, you run reports with variables in two ways: • •

If the query allows the variable to accept input, you can provide the value that will be used to run the report. If the query does not allow the variable to accept input, you are only allowed to select from a list of predefined values—one of which will be used to run the report.

In SAP Business Explorer (BEx), personalization enables users to enter a value for the variable and save it as their personal default value. As a result, when the report is run, the data that is generated is based on the variable value of their choice. If, in the future, the users want to run the same report, their saved personalized values are available for them to use. Personalized values are user-specific—that is, the personalized values that users set for themselves are not implemented onto other users. Other users who work with the same report can set their own personalized values, or use any of the preset values that are given to the variable.

406


2009



Lesson: SAP variable personalization

Personalization is a supported feature of BusinessObjects XI Integration for SAP Solutions. Reports based on SAP BW queries can leverage this functionality in InfoView. The user is able to read and write personalized values in the prompting interface by using the personalization icon.

2009


407


BO100

BO100

Lesson Summary You should now be able to: • Describe variable personalization

408


2009



Unit Summary

Unit Summary You should now be able to: • Describe the differences between BW MDX and BW Query driver in regards to hierarchies • Create simple reports with SAP hierarchies • Use formulas for hierarchical reporting • Create reports with a hierarchy variable • Create reports with a hierarchy node variable • Create reports against a BW cube directly • Create reports with keydate variables • Describe variable personalization

2009


409


BO100

Unit Summary

410


2009


BO100

Test Your Knowledge


Which of the following is true describing the functionality of BW MDX driver? Choose the correct answer(s).

2.

□

A

□ □ □

B C D

It offers each level of the hierarchy as a separate field and also offers parent child-relationship information. It only offers multiple levels of the hierarchy as a single field. It only offers each level of hierarchy as a separate field. It only offers a parent child relationship.

When creating a report based on a query with two structures Crystal Reports tries to resolve the structure containing the keyfigures and the structure representing the special grouping into one single field? Determine whether this statement is true or false.

□ □

2009

True False


411


BO100

BO100

Answers 1.

Which of the following is true describing the functionality of BW MDX driver? Answer: D Correct answer is D.

2.

When creating a report based on a query with two structures Crystal Reports tries to resolve the structure containing the keyfigures and the structure representing the special grouping into one single field? Answer: False

412


2009


Test Your Knowledge



Unit Summary

413


2009


BO100

Unit Summary

414


2009


BO100

Voyager with SAP BW Unit Overview This unit provides you with an overview of the SAP connectivity for Voyager.


Create a connection towards SAP BW for Voyager Describe the available information from SAP BW inside Voyager Describe how to create a simple Voyager Workspace with various types of SAP variables

Unit Contents Lesson: Creating connections to SAP BW with Voyager ...................... 416 Procedure: To create a new connection towards SAP BW ............... 417 Procedure: To use the connectivity in Voyager ............................ 423 Lesson: SAP BW metadata in Voyager .......................................... 431 Lesson: SAP Variables with Voyager ............................................ 439 Procedure: To create a new Voyager connection using SAP variables . 440 Procedure: To use the connectivity in Voyager ............................ 442 Procedure: To use the connectivity in Voyager with a hierarchy and hierarchy node variable ........................................................ 446 Procedure: To use the connectivity in Voyager with a keydate variable 448 Procedure: To use more than one connection in a Voyager Workspace: 450 Exercise 18: Creating a new Voyager workspace using an SAP BW query with variables.................................................................... 451

2009


415


Unit 10

BO100

Lesson: Creating connections to SAP BW with Voyager Lesson Overview In this lesson, you will learn how to establish a connection to SAP BW for Voyager.


Create a connection towards SAP BW for Voyager

Business Example With SAP BusinessObjects Voyager, your business analysts can explore online analytical processing (OLAP) data using a tool designed specifically for them – one that delivers a full range of functions for the analysis of multidimensional data sets. Analysts can quickly answer business questions and then share their analysis and workspace with others, spreading knowledge beyond the confines of a single department or group

What is in Voyager? SAP BusinessObjects Voyager offers analysts a modern and advanced user interface and enables them to: • • • •

• •

Discover trends, outliers, and details stored in their financial systems without the help of a database administrator. Get answers to business questions while viewing multidimensional data sets quickly and efficiently. Access the full range of OLAP data sources available within the organization and share results using a simple, intuitive Web interface. Access multiple different OLAP sources in the same report to get a comprehensive view of the business and the cross-impact that one trend may have on another. Interrogate, analyze, compare, and forecast business drivers. Use a comprehensive range of business and time calculations.

Creating a Voyager connection for SAP BW Voyager connections are stored in the Central Management Console (CMC) and need to be defined in the CMC before the user can leverage them in the Voyager client.

416


2009


Unit 10: Voyager with SAP BW

Lesson: Creating connections to SAP BW with Voyager

To create a new connection towards SAP BW 1.

Start the Central Management Console.

2.

Log onto the system with an administrative account.

Figure 132: Log on

3.

Click Voyager Connections.

Figure 133: Voyager Connections

4.

Click New Connection. Continued on next page

2009


417


BO100

BO100

Figure 134: New Connection

5.

Select SAP Business Information Warehouse in the list of Provider.


418


2009




Figure 135: Voyager Connections

6.

Enter a Name and Description for the connection.

7.

Enter the System, Server, System Number, Client and Language. Note: The connection can be built on an application server based configuration or a message server based configuration. This can be switched with the property Server Type.

8.

Click Connect. Note: The Save Language option allows you to define if the language should be saved with the connection or if the preferred viewing local from the user preferences should be used.


2009


419


BO100

BO100

Figure 136: Connect

9.

Enter the User and Password to authenticate against the SAP BW server.

10. Click OK.


420


2009




Figure 137: OK

Note: The Cube Browser shows the BW cubes and queries that can be used for a Voyager connection. You can choose between the Caption (Description in BW term) and the Name (Technical Name in BW term) of the objects. 11. Select the SAP BW query from the Cube Browser. 12. Click Select.


2009


421


BO100

BO100

Figure 138: Select

13. Define the Authentication. Note: You can choose between Prompt, SSO, SNC, and User Specified. The options SSO and SNC require specific configuration steps for the SAP server and the BusinessObjects Enterprise system. The option User Specified allows to define a user and password that will be shared by all users leveraging this connection. 14. Click Save.

Figure 139: Save

422


2009




To use the connectivity in Voyager 1.

Start InfoView (Start > Programs > BusinessObjects XI Release 3 > BusinessObjects Enterprise > BusinessObjects Enterprise Java InfoView).

Figure 140: Start InfoView

2.

Select SAP as Authentication.


2009


423


BO100

BO100

Figure 141: SAP as Authentication

3.


4.

Click Log On.


424


2009




Figure 142: InfoView

5.


6.

Select the menu New → Voyager Workspace.


2009


425


BO100

BO100

Figure 143: Voyager Workspace

7.

Select the connection.


426


2009




Figure 144: Connection

8.

Click OK.

9.

Enter User Credentials for the connection and click OK.


2009


427


BO100

BO100



428


2009





Note: The available items from the underlying SAP BW query will be shown in the Voyager Workspace.

2009


429


BO100

BO100

Lesson Summary You should now be able to: • Create a connection towards SAP BW for Voyager

430


2009



Lesson: SAP BW metadata in Voyager

Lesson: SAP BW metadata in Voyager Lesson Overview In this lesson, you will learn about the available metadata from SAP BW and how this is used in Voyager.


Describe the available information from SAP BW inside Voyager

Business Example You plan to implement Voyager with SAP BW access. You need a comprehensive overview of how they integrate and complement each other. You need this information to understand the relationship between BEx queries and Voyager.

SAP BW metadata in Voyager The following table shows an outline of the available metadata from SAP BW and how this is made available in a Voyager workspace.

2009

BW query element

Voyager

Characteristic

Dimension

Hierarchy

Each available hierarchy is represented as a dimension

Keyfigure

Measure

Calculated keyfigure

Measure element in the folder Keyfigure (Information about the calculation is not available in Voyager)

Restricted keyfigure

Measure element in the folder Keyfigure (Information about the calculation is not available in Voyager)

Filter

Filters will be applied to the underlying query but are not visible in the Voyager Workspace


431


BO100

BO100

BW query element

Voyager


Dimension

Display attribute

Display Attributes are not available in Voyager except the short, medium and long description of a dimension

SAP variables

Parameters that can be used in the Voyager Workspace

Characteristics This image shows a simple SAP BW query in the SAP BW Query Designer:

Figure 147: BW query

The query contains 2 characteristics (Sold-to party and Material) and two Keyfigures (Sales Voume (MC) and Sales Volume EUR). All characteristics available in the Rows or Free Characteristics will be available to utilize in Voyager. In addition, any SAP Variables will be utilized as Prompts. When creating a Voyager workspace based on this SAP BW query, the list of items will show as in the image.

432


2009




Figure 148: List of items

• •

• •

For characteristic Material, each available hierarchy is shown even though the SAP BW query did not include a specific hierarchy. The non-hierarchical display for characteristic Material is listed as an option as well and can be identified based on the name of the characteristic (for example, Material). The other characteristics are presented as standard dimensions. The key figures are presented in one group called Key Figures.

When using a characteristic in a Voyager Workspace the user can choose how to display the characteristic.

2009


433


BO100

BO100

Figure 149: Choose how to display the characteristic

Note: The availability of a short, medium, and long description depends on the data modeling in SAP BW.

Key figures, units, and currencies All key figures from the underlying SAP BW query are represented in Voyager in a group called Key Figures and can be used as a group or individually in the Voyager Workspace.

434


2009




Figure 150: Key figures

When the key figures are used in the Voyager Workspace, the key figure is presented together with the configured formatting and unit information.

2009


435


BO100

BO100

Figure 151: Key figure presented

The image above shows that the key figures Sales Volume (MC) and Sales Volume EUR are presented with the currency information and all key figures are presented based on the user’s preference for formatting. In case the user wants to switch to a different formatting the SAP BW based formatting can be disabled in the standard Format cell values dialog box.

436


2009





2009


437


BO100

BO100

Lesson Summary You should now be able to: • Describe the available information from SAP BW inside Voyager

438


2009



Lesson: SAP Variables with Voyager

Lesson: SAP Variables with Voyager Lesson Overview In this lesson, you will learn about the usage of SAP BW variables in a Voyager Workspace.


Describe how to create a simple Voyager Workspace with various types of SAP variables

Business Example You plan to implement Voyager with SAP BW access. You need to create a new Voyager connection using SAP variables.

Voyager and simple SAP variables Voyager offers a very similar prompting experience compared to the BEx Analyzer and BEx Web reporting. When creating a Voyager Workspace based on an SAP BW query with variables, each variable becomes a prompt in the Voyager Workspace.

2009


439


BO100

BO100

To create a new Voyager connection using SAP variables Note: This procedure is the same as creating connections without variables 1.


2.


3.


4.

Click New Connection.

5.

Select SAP Business Information Warehouse in the list for Provider.

6.


7.

Enter the System, Server, System Number, Client and Language. Note: The connection can be built on an application server based configuration or a message server based configuration. This can be switched with the property Server Type.

8.

Click Connect. Note: The Save Language option allows you to define if the language should be saved with the connection or if the preferred viewing local from the user preferences should be used.

9.


10. Click OK. Note: The Cube Browser shows the BW cubes and queries that can be used for a Voyager connection. You can choose between the Caption and the Name of the objects. 11. Select the SAP BW query from the Cube Browser. 12. Click Select.


440


2009




13. Define the Authentication. Note: You can choose between Prompt, SSO, SNC, and User Specified. The options SSO and SNC require specific configuration steps for the SAP server and the BusinessObjects Enterprise system. The option User Specified allows you to define a user and password that will be shared by all users leveraging this connection. 14. Click Save.

2009


441


BO100

BO100

To use the connectivity in Voyager 1.

Start InfoView

2.


3.


4.

Click Log On.

5.


6.


7.


8.

Click OK.

Figure 153: SAP BW query contains an SAP variable

Note: Because the underlying SAP BW query contains an SAP variable, Voyager asks you to provide a value before providing a list of dimensions. Continued on next page

442


2009




9.

Open the member selector to pick the From Value.

Figure 154: Member Selector

10. Open the member selector to pick the To Value.


2009


443


BO100

BO100

Figure 155: Member Selector

11. Select the required values. 12. Click OK.


444


2009




Figure 156: SAP BW query contains an SAP variable

Note: Because the underlying SAP BW query contains variables, Voyager offers the Edit SAP Variables values option as part of the Data tab.

Using hierarchy and hierarchy node variables in Voyager Hierarchy and hierarchy node variables can depend on each other in the case where the hierarchy and hierarchy node variable are based on the identical characteristic and hierarchy. This situation results in prompts depending on each other in Voyager. You first create a new Voyager connection with a hierarchy and hierarchy node variable following the same steps as you were creating a new Voyager connection using SAP variables before. Then you are ready to use the connectivity in Voyager.

2009


445


BO100

BO100

To use the connectivity in Voyager with a hierarchy and hierarchy node variable 1.

Start InfoView

2.


3.


4.

Click Log On.

5.


6.


7.


8.

Click OK. Note: The two variables are dependent on each other which can be recognized based on the situation that the second variable is indented. The second variable is not active and you cannot choose a value before setting a value for the first variable. Note: Each time the user changes the value for the hierarchy variable the list of available hierarchy nodes is refreshed.

9.

Select the values for the variables.

10. Click OK. 11. Move the hierarchy to the rows area. Note: When a hierarchy is selected, the workspace will only include the selected or fixed hierarchy (not all hierarchies as in the case when no hierarchy or hierarchy variable is involved with the BW query). 12. Move the keyfigures to the columns area. 13. Open the member selector for the hierarchy. Note: Based on the hierarchy node variable, the member selector will only show elements that have been selected with the hierarchy node variable.

446


2009




Voyager and SAP keydate variables A keydate variable can influence the following metadata and data of the underlying SAP BW system: • • •

Master data records can be time-dependent. Lists of available hierarchies for a characteristic can be time-dependent. Hierarchy structures can be time-dependent.

Voyager supports a keydate variable for the workspace with a dynamic refresh for the list of values of time-dependent variables. Each time the user changes the value for the keydate variable Voyager removes the existing values for any other variable and refreshes the list of values. You first create a new Voyager connection with a keydate variable following the same steps as you were creating a new Voyager connection using SAP variables before. Then you are ready to use the connectivity in Voyager.

2009


447


BO100

BO100

To use the connectivity in Voyager with a keydate variable 1.

Start InfoView

2.


3.


4.

Click Log On.

5.


6.


7.


8.

Click OK. Note: The keydate variable allows you to enter the value via a calendar control.

9.

Enter a value for the keydate variable.

10. Click OK.

Figure 157: Keydate Variable.

11. Define the rows and columns. 12. Refresh the report with different keydate variables.

448


2009




Multiple connections in one Voyager Workspace Voyager can leverage multiple connections in a single workspace. For SAP this means the user can have multiple queries or the same query with different variables in an identical workspace.

2009


449


BO100

BO100

To use more than one connection in a Voyager Workspace: 1.

Start InfoView.

2.


3.


4.

Click Log On.

5.


6.


7.


8.

Click OK.

9.

Click Add connection to workspace.

10. Click Insert a crosstab. 11. Use elements from the first query on Crosstab1. 12. Use elements from the second query on Crosstab2. 13. Save the workspace to BusinessObjects Enterprise. 14. View the workspace in InfoView. Note: Based on the capabilities of multiple connections in one workspace the user is able to leverage different sets of prompts (including keydate variables) for the same query in one workspace.

450


2009




Exercise 18: Creating a new Voyager workspace using an SAP BW query with variables Exercise Objectives After completing this exercise, you will be able to: • Create a new Voyager Workspace using an SAP BW query with SAP variables

Business Example You are a report designer and need to create a Voyager Workspace using an SAP BW query.

Task: [Enter a high level description of the task the learner will perform in this exercise.]

2009

1.


2.

Log onto BusinessObjects Enterprise and create a new connection using the query BO100 keydate variable (technical name: T_BO1001/‘T_BO100_Q11_1).

3.

Save the connection.

4.

Create a new report with Voyager using the connection.

5.

Define the rows and columns.

6.

Refresh the variables and change the value for the keydate variable.

7.

Create another Voyager Workspace using a BW query with hierarchy and hierarchy node variable.


451


BO100

BO100

Solution 18: Creating a new Voyager workspace using an SAP BW query with variables Task: [Enter a high level description of the task the learner will perform in this exercise.] 1.

Start the Central Management Console. a)

2.

3.

Select Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Central Management Console.

Log onto BusinessObjects Enterprise and create a new connection using the query BO100 keydate variable (technical name: T_BO1001/‘T_BO100_Q11_1). a)


b)


c)

Click New Connection.

d)

Select SAP Business Information Warehouse in the list for Provider.

e)


f)

Enter the System, Server, System Number, Client and Language.

g)

Click Connect.

h)


i)

Click OK.

j)

Select the SAP BW query from the Cube Browser.

k)

Click Select .

Save the connection. a)


452


2009




4.

Create a new report with Voyager using the connection. a)

Start InfoView.

b)


c)


d)

Click Log On.

e)


f)


g)


h)

Click OK.

i)

The keydate variable allows you to enter the value via a calendar control. Enter a value for the keydate variable.

Figure 158: Calender control

5.

6.

Define the rows and columns. a)

Select the Product Hierarchy 1 for the rows.

b)

Select the keyfigures for the columns.

Refresh the variables and change the value for the keydate variable. a) Continued on next page

2009


453


BO100

7.

BO100

Create another Voyager Workspace using a BW query with hierarchy and hierarchy node variable. a)

454


2009




Lesson Summary You should now be able to: • Describe how to create a simple Voyager Workspace with various types of SAP variables

2009


455


BO100

BO100

Unit Summary You should now be able to: • Create a connection towards SAP BW for Voyager • Describe the available information from SAP BW inside Voyager • Describe how to create a simple Voyager Workspace with various types of SAP variables

456


2009


Unit Summary

Test Your Knowledge


The IT Director needs a BI consultant to analyze the last few years help desk transactions by service team utilization, season/time of year trends, cost center usage, response times per service area. What tool should the consultant use? feeding into the dashboard remains unchanged until the end of the current business day. During the day, the financial analyst team are constantly running BW queries to perform financial modeling which places a lot of peak load on the same BW server during daytime hours, and Customer Support and Help desk run on demand operational Webi queries on their call queues. The BW server has BI Accelerator added on (BIA). Over 500 hundred employees. Choose the correct answer(s).

□ □ □ □

2009

A B C D

Web Intelligence Crystal Reports Voyager and/or SAP Business Explorer (BEx) Xcelsius


457


BO100

BO100

Answers 1.

The IT Director needs a BI consultant to analyze the last few years help desk transactions by service team utilization, season/time of year trends, cost center usage, response times per service area. What tool should the consultant use? feeding into the dashboard remains unchanged until the end of the current business day. During the day, the financial analyst team are constantly running BW queries to perform financial modeling which places a lot of peak load on the same BW server during daytime hours, and Customer Support and Help desk run on demand operational Webi queries on their call queues. The BW server has BI Accelerator added on (BIA). Over 500 hundred employees. Answer: C Voyager - slice and dice, hierarchies, expert view on BEx query or BW InfoCube.

458


2009


Test Your Knowledge



Unit Summary

459


2009


BO100

Unit Summary

460


2009


BO100

Xcelsius with Live Office Unit Overview This unit provides you with an overview of using Xcelsius with Live Office to retrieve SAP data. You will learn how to connect Live Office to SAP data sources and create an Xcelsius dashboard using Live Office with Web Intelligence and Crystal Report as a data source

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

Connect Live Office to BusinessObjects products. Create a Live Office document with Crystal Reports based on SAP data sources Create a Live Office document from a Web Intelligence report based on SAP data sources Create an Xcelsius dashboard with Live Office

Unit Contents Lesson: Xcelsius with Live Office ................................................. 462 Exercise 19: Creating a new Live Office document based on Crystal Reports........................................................................... 467 Exercise 20: Create a Live Office Document from a Web Intelligence Report ............................................................................ 475 Lesson: Creating an Xcelsius dashboard with Live Office .................... 481 Exercise 21: Creating a new Xcelsius dashboard with Live Office ...... 483

2009


461


Unit 11

BO100

Lesson: Xcelsius with Live Office Lesson Overview In this lesson, you will learn how to use Live Office to connect to SAP data sources.


Connect Live Office to BusinessObjects products. Create a Live Office document with Crystal Reports based on SAP data sources Create a Live Office document from a Web Intelligence report based on SAP data sources

Business Example You are a business user who needs to transform complex business data into actionable visual information. You need to create rich interactive presentations for your business needs.

What is in Live Office SAP BusinessObjects Live Office software provides you with the following features and functions: •

• • •

462

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. Format the imported data by using standard Microsoft Excel functionality and the features of Live Office.


2009


Unit 11: Xcelsius with Live Office

Lesson: Xcelsius with 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.

What is Xcelsius? Xcelsius 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. With Xcelsius, 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. The end result is an interactive dashboard with live data connectivity for accurate, consistent information, providing you with immediate and trusted results.

2009


463


BO100

BO100

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

Connectivity for Xcelsius Xcelsius can connect to your SAP data sources in two ways. Xcelsius visualization can leverage Live Office to connect to a Crystal report or Web Intelligence document. In addition, the visual model can connect directly to an universe via Web services created with Query as a Web Service.

Figure 159: Xcelsius Connectivity to SAP data sources

464


2009




Leveraging Crystal Reports and Web Intelligence Live Office is able to leverage Crystal Reports documents, Web Intelligence documents and Universes for building new Live Office documents. 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 regional sales 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. To leverage SAP data sources in Live Office, you first need to create a Crystal report or Web Intelligence document based on the SAP data sources.

2009


465


BO100


466


2009


BO100


Exercise 19: Creating a new Live Office document based on Crystal Reports Exercise Objectives After completing this exercise, you will be able to: • Create a new Live Office document using Crystal Reports as a source

Business Example You are a report designer who needs to create a LiveOffice document using an existing Crystal Report document as a source.

Task: In this exercise you need to create a Live Office Document from a Crystal Report. You will follow the wizard mentioned in table below. Workflow in Live Office Insert Wizard

Tasks

Choose Document

Browse available reports.

Choose Data

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

Set Filters

Select filters to apply to the data 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 Microsoft Excel.

2.

Enter the information in the Web Service URL and System fields:


2009


467


BO100

468

BO100

User Name

BO100-##

Password

Assigned password

Web Service URL

http://twdfXXXX:8080/dswsbobje/services/session

System

TWDFXXXX

Authentication

SAP

3.

Once you log onto Live office successfully, go through the Live Office Insert Wizard to insert Crystal Reports Content.

4.

Choose the available fields in the report.

5.

Set Filter- 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. Select sales values that are greater than 10000 as filter.

6.

Complete the summary page in the Insert Wizard. This is the last screen in Live Office Insert Wizard before the current object is inserted into your Microsoft Office application

7.

Save the Live Office document to SAP BusinessObjects Enterprise

8.

Modify the report so that it refreshes on demand.


2009




Solution 19: Creating a new Live Office document based on Crystal Reports Task: In this exercise you need to create a Live Office Document from a Crystal Report. You will follow the wizard mentioned in table below. Workflow in Live Office Insert Wizard

Tasks

Choose Document


Choose Data

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

Set Filters

Select filters to apply to the data 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 Microsoft Excel. a)

2.

Select Microsoft Excel: Programs → Microsoft Office → Microsoft Office Excel 2003.

Enter the information in the Web Service URL and System fields: User Name

BO100-##

Password

Assigned password

Web Service URL


System

TWDFXXXX

Authentication

SAP

a)

Select the menu LiveOffice → Options.

b)

Navigate to the Enterprise tab.

c)

Select the check box Use specified logon criteria.

d)

Enter the user name and password given by the instructor Continued on next page

2009


469


BO100

3.

BO100

e)

Enter the information in the Web Service URL and System fields.

f)

Select SAP as Authentication and click Logon.

g)

Click OK.

Once you log onto Live office successfully, go through the Live Office Insert Wizard to insert Crystal Reports Content. a)

Select the menu LiveOffice →Insert → Crystal Reports Content.

b)

Select the previously created report from BusinessObjects Enterprise. For example BO100 Live Office Sample.rpt

c)

Click Next.

Figure 160: Live Office Insert Wizard


470


2009




4.

Choose the available fields in the report. a)

Click Switch to Fields.

b)

In the Available Fields list, click both fields to include in the Report object, and then click the right arrow >.


c)

Use the up and down arrows to change the order of the included fields, as required. Note: The buttons to change the order of the fields are on the right side of the window.

d)

Click Next.


2009


471


BO100

5.

BO100

Set Filter- 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. Select sales values that are greater than 10000 as filter. a)

In the Set Filters page of the Live Office Insert Wizard, click the field that you want to filter. Select Sales Values.

b)

Select a operator is greater than from the Operators drop-down list on the right.

c)

Enter the value 1000000.


d) 6.

Click Next.

Complete the summary page in the Insert Wizard. This is the last screen in Live Office Insert Wizard before the current object is inserted into your Microsoft Office application


472


2009




a)

Review the information on the summary page and add GR## in the beginning of the object name. Note: This is the name of the imbedded object, not the finished live office enabled workbook. The workbook will be saved in the next step.


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)

The Live Office document will be displayed in the spreadsheet inside the Xcelsius.


2009


473


BO100

BO100


7.

Save the Live Office document to SAP BusinessObjects Enterprise a)

Select the menu LiveOffice → Publish to BusinessObjects Enterprise → Save to BusinessObjects Enterprise.

b)

Enter the file name of your Live Office document. Note: Enter specific file name 'GR## Live Office with Crystal' and save it under SAP → 2.0 → CLNT900.

c) 8.

474

Click Save.

Modify the report so that it refreshes on demand. a)

Select the menu LiveOffice → Properties of All Objects.

b)

Select the Crystal Reports object.

c)

Select the Refresh tab.

d)

Define the report to be refreshed on demand.

e)

Click OK.

f)

Close Microsoft Excel.


2009




Exercise 20: 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


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


2009


475


BO100

BO100

User Name

BO100##

Password

Assigned Password

Web Service URL


System

twdfXXXX:6400

Authentication

SAP

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 → CLNT900 → GR## Sales Order Report with Optional Prompt. This is one of the Web Intelligence reports that you created earlier..

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

476


2009




Solution 20: 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


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.

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

Verify the information in the Web Service URL and System fields


2009


477


BO100

BO100

User Name

BO100##

Password

Assigned Password

Web Service URL


System

twdfXXXX:6400

Authentication

SAP

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 SAP 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 → CLNT900 → GR## Sales Order Report with Optional Prompt. This is one of the Web Intelligence reports that you created earlier..

2.

a)

Navigate to 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 navigation.

b)

Expand The folder Public → SAP → 2.0 → CLNT900

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.


478


2009




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→ CLNT900. Enter the Description: GR## Live Office Sales Orders from Web Intelligence Report. .


479


BO100

BO100

Lesson Summary You should now be able to: • Connect Live Office to BusinessObjects products. • Create a Live Office document with Crystal Reports based on SAP data sources • Create a Live Office document from a Web Intelligence report based on SAP data sources

480


2009



Lesson: Creating an Xcelsius dashboard with Live Office

Lesson: Creating an Xcelsius dashboard with Live Office Lesson Overview Previously you created a Crystal Report document retrieving data from SAP BW and used Live Office to show the data in Microsoft Excel. As a next step, you will use the Live Office document as a source for the Xcelsius dashboard.


Create an Xcelsius dashboard with Live Office

Business Example You are a report designer who needs to create interactive dashboards from a Live Office document with SAP datasources. The dashboards enable you to monitor business performance, identify critical data relationships, and use what-if scenarios to understand potential performance.

What is Dashboard? Dashboard is a user interface that organizes and presents information in a way that is easy to read with a great look and feel. A Xcelsius dashboard is more likely to be interactive and user friendly. It is used by higher management To create Xcelsius dashboard, you run a Crystal Report to retreive SAP ERP or BW data. The data is saved to a Microsoft Excel file which is tehn used by Xcelsius to create interactive dashboards. Note: • • • •

2009

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


481


BO100


482


2009


BO100


Exercise 21: Creating a new Xcelsius dashboard with Live Office Exercise Objectives After completing this exercise, you will be able to: • Build a new Xcelsius dashboard using Live Office as a source

Business Example You are a report designer creating an Xcelsius dashboard and building the underlying Crystal Report and LiveOffice documents.

Task:

2009

1.

Start Xcelsisu to create a new Xcelsius dashboard using the previously created Live Office document as a source.

2.

Configure the LiveOffice connectivity to refresh on each load.

3.

Show a pie chart with the amount of order per region.

4.

View the dashboard with Single-Sign-On in InfoView and save the Xcelsius file to BusinessObjects Enterprise.

5.

View the dashboard with Single-Sign-On in InfoView.


483


BO100

BO100

Solution 21: Creating a new Xcelsius dashboard with Live Office Task: 1.

Start Xcelsisu to create a new Xcelsius dashboard using the previously created Live Office document as a source. a)

Select Start → Programs → Xcelsius → Xcelsius 2008. Note: You might be prompted with two information windows. For the first window about running in Live Office compatibility mode, click Yes to proceed. For the second window about aborting the Xcelsius startup, click No.

b)

Select Data → Import from Enterprise.

c)

Enter the system credentials: Note: Xcelsius currently does not support SAP authentication. This feature will be available in SP2. Use administartor to log into Enterprise here.

2.

System

TWDFXXXX

User name

administrator

Password

Assigned password for administrator

Authentication

Enterprise

d)

Click yes on the prompt message

e)

Navigate to the SAP → 2.0 → CLNT900

f)

Select the Live Office document you created previously.

g)

Click Open. The Live Office document will be displayed in the spreadsheet inside the Xcelsius.

Configure the LiveOffice connectivity to refresh on each load. a)

Select the menu Data → Connections.

b)

Click Add.

c)

Select the existing Live Office Connections. Continued on next page

484


2009




Figure 165: Data Manager

d)

Replace the entry with the name of the assigned server.


2009


485


BO100

BO100


e)

Click the Usage tab.

f)

Set the Refresh on Load property.


486


2009





g) 3.

Close the Data Manager.

Show a pie chart with the amount of order per region. a)

Find a pie chart from the charts category. Drag and drop a pie chart component onto the Xcelsius canvas.


2009


487


BO100

BO100

Figure 168: Pie Chart

b)

Double-click the pie chart to open the properties.

c)

Click on the icon next to the Data Values and mark the range for the values: $B$2:$B$10.

d)

Click OK.

e)

Select the Data in Columns check box.

f)

Click on the icon next to the Data Labels and mark the range for the labels: $A$2:$A$10.


488


2009




Figure 169: Pie Chart


2009


489


BO100

4.

BO100

View the dashboard with Single-Sign-On in InfoView and save the Xcelsius file to BusinessObjects Enterprise. a)

Select File → Preview. Note: Because you are not authenticated against BusinessObjects Enterprise at this time a logon mask will come up and ask for BusinessObjects Enterprise credentials. Use the SAP Authentication and the SAP credentials to leverage Single-Sign-On from the Xcelsius Dashboard to LiveOffice and Crystal Reports.

b)

Select the menu File → Export → Business Objects Platform.... Note: When exporting to the Business Objects Platform the actual Xcelsius document (runtime flash 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.

5.

490

c)

Navigate to SAP → 2.0 → CLNT900 in your BusinessObjects Enterprise system.

d)

Enter a file name GR## Xcelsius dashboard with Live Office.

e)

Click Save.

View the dashboard with Single-Sign-On in InfoView. a)

Select Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → BusinessObjects Enterprise Java InfoView.

b)

Enter the BusinessObjects Enterprise Server name twdfXXXX.

c)


d)


e)

Click Log On.

f)

Click Document List

g)

Navigate to SAP → 2.0 → CLNT900 in your BusinessObjects Enterprise system.

h)

View your Xcelsius dashboard flash file in InfoView.


2009




Lesson Summary You should now be able to: • Create an Xcelsius dashboard with Live Office

2009


491


BO100

BO100

Unit Summary You should now be able to: • Connect Live Office to BusinessObjects products. • Create a Live Office document with Crystal Reports based on SAP data sources • Create a Live Office document from a Web Intelligence report based on SAP data sources • Create an Xcelsius dashboard with Live Office

492


2009


Unit Summary

Test Your Knowledge


Which of the following tools allow you to insert Web Intelligence Content directly into excel? Choose the correct answer(s).

□ □ □ □

2009

A B C D

Web Intelligence Content Wizard Universe Insert Wizard Live Office Insert Wizard Web Intelligence Insert Wizard


493


BO100

BO100

Answers 1.

Which of the following tools allow you to insert Web Intelligence Content directly into excel? Answer: C Correct answer is C.

494


2009


Test Your Knowledge



Unit Summary

495


2009


BO100

Unit Summary

496


2009


BO100

Xcelsius with Query as a Web Service (QaaWS) on BW Unit Overview This unit provides you with an overview of using Query as a Web Service (QaaWS) to connect to SAP data sources. Also you will learn how to use Xcelsius to connect to a QaaWS web service with SAP variables.


Create a Query as a Web Service against SAP data sources with variables Use Xcelsius with Query as a Web Service Connect Xcelsius with Query as a Web Service with SAP variables

Unit Contents Lesson: Query as a Web Service................................................. 498 Exercise 22: Creating a new Query as a Web Service .................... 501 Lesson: Xcelsius and Query as a Web Service................................. 508 Exercise 23: Creating a new Xcelsius dashboard using Query as a Web Service ........................................................................... 511 Exercise 24: Creating a new Xcelsius dashboard based on QaaWS with SAP variables ................................................................... 517

2009


497


Unit 12

BO100

Lesson: Query as a Web Service Lesson Overview In this lesson, you will learn about how you can use QaaWS to connect to SAP data sources.


Create a Query as a Web Service against SAP data sources with variables

Business Example Query as a Web Service lets you create custom web services for specific queries using Business Objects Web Services. You access queries to build applications that use the same semantic layer as the rest of the BusinessObjects suite. Business Intelligence (BI) content is usually bound to a specific user interface of 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. Query as a Web Service also enables a range of client-side solutions in tools such as: • • • • •

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

OLAP Universe with SAP data sources 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.

498


2009


Unit 12: Xcelsius with Query as a Web Service (QaaWS) on BW

Lesson: Query as a Web Service

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 datasources inside Excel and these multiple Excel files can be used by multiple web services. The first step is to build a new OLAP Universe on top of an SAP BW query. After creating the OLAP Universe, you can create the web service on top of the OLAP Universe.

Figure 170: Query as a Web Service

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

2009

SAP BW Queries BW MultiProviders BW InfoCubes


499


BO100

500


BO100

2009




Exercise 22: Creating a new Query as a Web Service Exercise Objectives After completing this exercise, you will be able to: • Build a new OLAP Universe based on an SAP BW query with variables • Create a Query as a Web Service on top of the OLAP Universe.

Business Example Your business reporting group requires a Query as a Web Service when querying against SAP BW InfoProviders.

Task: Create a new OLAP Universe based on the BW Query with variables. Then create a new QaaWS based on the OLAP Universe. Publish the web service after you create the QaaWS. 1.

Create a new OLAP Universe based on the BW Query BO100 Xcelsius QaaWs 01 (technical name: T_BO100_Q16_1). Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language


Application Server


System number

50

System ID

Assigned system ID

2.

Save the OLAP Universe and export it to BusinessObjects Enterprise.

3.


4.

Launch Query as a Web Service.

5.

Enter the host definition. Continued on next page

2009


501


BO100

6.

Create a new web service

7.

Select the universe on which to build your query.

8.

Use the query panel to create the query for the web service.

9.

Create a filter object to filter Sales Volumes that are not equal to 0.

BO100

10. Publish the web service.

502


2009




Solution 22: Creating a new Query as a Web Service Task: Create a new OLAP Universe based on the BW Query with variables. Then create a new QaaWS based on the OLAP Universe. Publish the web service after you create the QaaWS. 1.

Create a new OLAP Universe based on the BW Query BO100 Xcelsius QaaWs 01 (technical name: T_BO100_Q16_1). Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language


Application Server


System number

50

System ID

Assigned system ID

a)

Start Designer from Start → Programs → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → Designer.

b)

Enter the user name and password using the following information. Field Name

Value

System


User name


Password

Assigned password

Authentication

SAP

c)

Click File > New.

d)

Click New to create a new connection. Continued on next page

2009


503


BO100

2.

BO100

e)

Click Next.

f)


g)


h)

Click Next.

i)


j)


k)


l)

Click Next.

m)


n)

Navigate to BO100 cube and select ‘BO100 Xcelsius QaaWs 01 (technical name: T_BO100_Q16_1)'.

o)


p)

Click Finish.

q)

Enter the Universe name T_BO100_Xcelsius_QaaWS01_##.

r)


s)


t)

Click OK.

Save the OLAP Universe and export it to BusinessObjects Enterprise. a)


b)

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


504


2009




3.

4.



b)


c)


d)


Launch Query as a Web Service. a)

5.

Select Program → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools→ Query as a Web Service.

Enter the host definition. a)

Click Add.

b)

Create QaaWS with the following credentials. Name

(For example: twdfXXXX)

URL

CMS

(For example: twdfXXXX)

User

c)

Click OK.

d)

Click Close.

e)

Enter the password and click OK.


2009


505


BO100

6.

7.

Create a new web service a)

Select the menu New → Query...

b)

Enter a name for the web service.

c)

Click Advanced Parameters.

d)

Select secSAPR3 as Authentication mode if you are using SAP authentication. Note: To be able to select the SAP Authentication it requires the SAP authentication JAR file (secSAPR3.jar) to be deployed with the web services.

e)

Click OK.

f)

Click Next.

Select the universe on which to build your query. a)

8.

9.

BO100

Click the universe T_BO100_Xcelsius_QaaWS01_GR##.unv.

Use the query panel to create the query for the web service. a)

Expand all classes (folders).

b)

Drag the following objects to the Result Objects window. Customer:

L01 Sold-to Party_country

Key Figures:

Sales Volume EUR

Create a filter object to filter Sales Volumes that are not equal to 0. a)

Drag the Sales volume EUR from the Results Objects area to the Filter Objects area.

b)

Change the filter type from In list to Not Equal to and enter the value 0.

c)

Click Next. A preview of the result should appear.

10. Publish the web service.

506

a)

Click Publish.

b)

Copy the URL to the clipboard so that it can be used later on in Xcelsius.


2009




Lesson Summary You should now be able to: • Create a Query as a Web Service against SAP data sources with variables

2009


507


BO100

BO100

Lesson: Xcelsius and Query as a Web Service Lesson Overview You have learned how to create a QaaWS on top of an OLAP Universe based on an SAP query. In this lesson, you will learn how you can use Xcelisus to connect to a QaaWS web service with SAP data sources.


Use Xcelsius with Query as a Web Service Connect Xcelsius with Query as a Web Service with SAP variables

Business Example You are a report designer who uses Xcelsius dashboard on top of an OLAP Universe based on an SAP data sources. You have created a new Query as a Web Service on top of the Universe and then publish the web service. Now you are ready to create a dashboard using this web service.

Connectivity for Xcelsius Xcelsius can connect directly to a BusinessObjects universe Query as a Web Service. The following data sources are available for Xcelsius: SAP BW • • • •

508

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


2009



Lesson: Xcelsius and Query as a Web Service

Figure 171: Xcelsius Connectivity to SAP NetWeaver

Xcelsius and QaaWS After creating the OLAP Universe and the web service based on top of the OLAP Universe, you can now create the Xcelsius dashboard using the web service.

2009


509


BO100

510


BO100

2009




Exercise 23: Creating a new Xcelsius dashboard using Query as a Web Service Exercise Objectives After completing this exercise, you will be able to: • Build a new Xcelsius dashboard using QaaWS on top of an OLAP Universe based on an SAP BW query.

Business Example You are a report designer and need to create an Xcelsius dasboard based on an existing web service.

Task: Build a new Xcelsius dashboard using QaaWS on top of an OLAP Universe based on an SAP BW query.

2009

1.

Launch Xcelsius and use the existing QaaWS.

2.

Create a pie chart that demonstrate the sales value of customer in different region.

3.

Preview the dashboard in Xcelsius.

4.

Save the Xcelisus report to Enterprise and view the report using SAP authentication.


511


BO100

BO100

Solution 23: Creating a new Xcelsius dashboard using Query as a Web Service Task: Build a new Xcelsius dashboard using QaaWS on top of an OLAP Universe based on an SAP BW query. 1.

Launch Xcelsius and use the existing QaaWS. a)

Select Start → Programs → Xcelsius → Xcelsius 2008. Note: You might be prompted with two information windows. For the first window about running in Live Office compatibility mode, click Yes to proceed. For the second window about aborting the Xcelsius startup, click No.

b)

Select Data → Connections.


c)

Click Add.

d)

Select Query as a Web Service.


512


2009




Figure 173: Query as a Web Service

e)

Select the newly created QaaWs connection. Note: The existing QaaWS connection might have been selected by default.

f)

Paste the URL from the created QaaWs web service into the field WSD URL.

g)

Click Import. Note: The web service returns the data in a table format and shows that each row in this example returns a value for the Country and a value for the Order Amount.

h)

Click the row folder of the Return Values.

i)

Click the red arrow icon next to the range.

j)

Mark the range (A1:B10) in the Excel spreadsheet by selecting A1 and then using the shift key to select B10.

k)

Click OK.

l)

Navigate to the Usage tab.

m)

Set the Refresh on Load property. Continued on next page

2009


513


BO100

n) 2.

BO100

Click Close.

Create a pie chart that demonstrate the sales value of customer in different region. a)

Drag and drop a pie chart onto the canvas.

b)


c)

Click the red arrow icon next to the Data Values.

d)

Mark the range (B1:B10) in the Excel spreadsheet by selecting B1 and then using the shift key to select B10

e)

Click OK.

f)

Click the red arrow icon next to the Data Labels.

g)

Mark the range (A1:A10) in the Excel spreadsheet by selecting A1 and then using the shift key to select A10

Figure 174: Pie chart


514


2009




3.

Preview the dashboard in Xcelsius. a)

Click Preview.

Figure 175: Customer sales value

Note: Because you are not authenticated against BusinessObjects Enterprise at this time a logon mask will come up and ask for BusinessObjects Enterprise credentials. Use the SAP Authentication and the SAP credentials to leverage Single-Sign-On from the Xcelsius Dashboard to LiveOffice and Crystal Reports.


2009


515


BO100

4.

BO100

Save the Xcelisus report to Enterprise and view the report using SAP authentication. a)

Select the menu File → Export → BusinessObjects Platform. Note: When exporting to the BusinessObjects Platform the actual Xcelsius runtime flash 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.

516

b)

Select a folder on your BusinessObjects Enterprise system. Navigate to SAP → 2.0 → CLNT900 in your BusinessObjects Enterprise system.

c)

Enter a file name GR## Xcelsius QaaWS01.

d)

Click Save.

e)

View the Xcelsius dashboard in InfoView using the SAP authentication.


2009




Exercise 24: Creating a new Xcelsius dashboard based on QaaWS with SAP variables Exercise Objectives After completing this exercise, you will be able to: • Build two OLAP Universes based on an SAP BW query with variables • Build two new QaaWS service using the OLAP Universes • Build a new Xcelisus dashboard based on the QaaWS.

Business Example You created a web service which delivers a list of countries and you have a web service which will retrieve the list of regions based on a selected country represented by an SAP variable. As a next step, you will create Xcelsius components to provide a list of values and a chart showing the actual data based on the selected value.

Task 1: Build the first OLAP Universe based on BW Query BO100 Xcelsius QaaWs 01 Build two new QaaWS service using OLAP Universes as the source. The first QaaWS will be used for the prompting the list of values and the second QaaWS will be used for the actual data retrieval. 1.

Use the OLAP Universe based on the BW Query BO100 Xcelsius QaaWs 01 (technical name: T_BO100_Q16_1). Note: This OLAP Universe will be used for the prompting as the List of Values.

Task 2: Build the second OLAP Universe based on BW Query BO100 Xcelsius QaaWs 02 1.

Create a new OLAP Universe based on the BW Query BO100 Xcelsius QaaWs 02 (technical name: T_BO100_Q17_1). Note: This OLAP Universe will be used for the actual data retrieval.

2.

Save the OLAP Universe and export it to BusinessObjects Enterprise. Continued on next page

2009


517


BO100

BO100

Task 3: Create a new QaaWS using the first Universe 1.

Create a new QaaWS web service using the OLAP Universe (BO100 Xcelsius QaaWS 01).

2.

Include the following fields from universe: Sold-toPartyCountry Key and Sold-toPartyCountry Description.

Task 4: Create a new QaaWS using the second Universe 1.

Create the second QaaWS and include the following fields from universe T_BO100_Xcelsius_QaaWS02_GR##.unv: Region and Sales Volume EUR

Task 5: Creating a new Xcelsius based on the two Query as a Web Services You have created a web service which delivers a list of countries and you have a web service which will retrieve the list of regions based on a selected country represented by an SAP variable. As a next step, you will create Xcelsius components to provide a list of values and a chart showing the actual data based on the selected value.

518

1.

Launch Xcelsius and create a data connection using the first QaaWS.

2.

Add a list box component to the Xcelsius canvas and connect it to the first QaaWS. This list box is used to retrieve the values from the QaaWS. Later you will configure the component with trigger cells to interact with another component.

3.

Create another data connection in Xelsius using the second Query as a Web Service.

4.

Create a pie chart onto the canvas and link it to the second QaaWS.

5.

Preview the Xcelsius file and see how the components interact with each other.

6.

Save the Xcelisus document to Enterprise and view the flash document using SAP authentication.


2009




Solution 24: Creating a new Xcelsius dashboard based on QaaWS with SAP variables Task 1: Build the first OLAP Universe based on BW Query BO100 Xcelsius QaaWs 01 Build two new QaaWS service using OLAP Universes as the source. The first QaaWS will be used for the prompting the list of values and the second QaaWS will be used for the actual data retrieval. 1.

Use the OLAP Universe based on the BW Query BO100 Xcelsius QaaWs 01 (technical name: T_BO100_Q16_1). Note: This OLAP Universe will be used for the prompting as the List of Values. a)

This OLAP Universe, T_BO100_Xcelsius_QaaWS01_GR##.unv, should have been created from an earlier exercise. Check that this universe is available in Designer.

b)


c)

Select File → Open.

d)

Navigate to BusinessObjects Universes folder and ensure T_BO100_Xcelsius_QaaWS01_GR##.unv is there.

Task 2: Build the second OLAP Universe based on BW Query BO100 Xcelsius QaaWs 02 1.

Create a new OLAP Universe based on the BW Query BO100 Xcelsius QaaWs 02 (technical name: T_BO100_Q17_1). Note: This OLAP Universe will be used for the actual data retrieval. a)


b)

Enter the user name and password using the following information. Field Name

Value Continued on next page

2009


519


BO100

BO100

Field Name

Value

System


User name


Password

Assigned password

Authentication

SAP

c)

Click File > New.

d)


e)

Click Next.

f)


g)


h)

Click Next.

i)

Enter the User name, Password, and Language. Field Name

Value

User

Assigned user

Password

Assigned password

Client

900

Language


Application Server


System number

50

System ID

Assigned system ID

j)


k)

Set the Authentication Mode to Use specified username and password. Continued on next page

520


2009




2.

l)

Click Next.

m)


n)

Navigate to BO100 cube and select ‘BO100 Xcelsius QaaWs 02 (technical name: T_BO100_Q17_1)'.

o)


p)

Click Finish.

q)

Enter the Universe name T_BO100_Xcelsius_QaaWS02_##.

r)


s)


t)

Click OK.

Save the OLAP Universe and export it to BusinessObjects Enterprise. a)


b)

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

c)


d)


e)


f)



2009


521


BO100

BO100

Task 3: Create a new QaaWS using the first Universe 1.

Create a new QaaWS web service using the OLAP Universe (BO100 Xcelsius QaaWS 01). a)

Select Program → BusinessObjects XI 3.1 → BusinessObjects Enterprise Client Tools → Query as a Web Service. Note: Since you have already created a Query as a Web Service, you don't have to add the host anymore. Ensure the following credentials are on the login screen: Field Name

Value

Host


System


User

Assigned User ID (for example: BO100-##)

b)

Enter your assigned password

c)

Click the New Query icon, or select the menu Query → New → Query...

d)

Enter a name of the web service. For exmaple GR##_QaaWS_01

e)

Click Advanced Parameters.

f)

Select secSAPR3 as Authentication mode. Note: To be able to select the SAP Authentication it requires the SAP authentication JAR file (secSAPR3.jar) to be deployed with the web services.

g)

Click OK.

h)

Click Next.


522


2009




2.

Include the following fields from universe: Sold-toPartyCountry Key and Sold-toPartyCountry Description. a)

Select the OLAP universe (BO100 Xcelsius QaaWS 01) T_BO100_Xcelsius_QaaWS01_GR##.unv you created earlier.

b)

Click Next.

c)


d)

Click Next.

e)

Expand all the folder. Select L01 Sold-toPartyCountry Key and L01 Sold-toPartyCountry Name and drag them to the Result Objects window.

f)

Click Next. Note: A preview of the data is shown including the output parameters.

g)

Click Publish.

h)

Copy the URL to the clipboard so that it can be used later in Xcelsius.


2009


523


BO100

BO100

Task 4: Create a new QaaWS using the second Universe 1.

Create the second QaaWS and include the following fields from universe T_BO100_Xcelsius_QaaWS02_GR##.unv: Region and Sales Volume EUR a)

Click the New Query icon, or select the menu Query → New → Query...

b)

Enter a name of the web service. For exmaple GR##_QaaWS_02

c)

Select the OLAP universe (BO100 Xcelsius QaaWS 02) T_BO100_Xcelsius_QaaWS02_GR##.unv you created earlier.

d)

Click Next.

e)


f)

Click Next.

g)

Select L01 Region and Sales Volume EUR and drag them to the Result Objects window.

h)

Click Next. Note: In case the underlying OLAP Universe includes a prompt the web service tool will provide a list of values during the creation process.

i)

Double-click a value.

j)

Click OK. Note: A preview of the data is shown including the output parameters.

k)

Click Publish.

l)

Copy the URL to the clipboard so that it can be used later in Xcelsius.

m)

Click Close.

Task 5: Creating a new Xcelsius based on the two Query as a Web Services You have created a web service which delivers a list of countries and you have a web service which will retrieve the list of regions based on a selected country represented by an SAP variable. As a next step, you will create Xcelsius components to provide a list of values and a chart showing the actual data based on the selected value. 1.

Launch Xcelsius and create a data connection using the first QaaWS. Continued on next page

524


2009




a)

Select Start → Program → Xcelsius → Xcelsius 2008. Note: You might be prompted with two information windows. For the first window about running in Live Office compatibility mode, click Yes to proceed. For the second window about aborting the Xcelsius startup, click No.

b)



c)

Click Add.

d)

Select Query as a Web Service.

e)

Select the newly created connection.

f)

Paste the URL from the first created QaaWS web service into the field WSD URL. Note: Find the URL for GR##_QaaWS_01. If the URL is not in the clipboard, go the Query as a Web Service and select the GR##_QaaWS_01. Click To Clipboard.

g)

Click Import. Note: The web service returns the data in a table format and shows that each row in this example returns a value for the County Key and a value for the Country Name

h)

Click the row folder of the Return Values. Continued on next page

2009


525


BO100

BO100

i)

Click the icon next to the range.

j)

Mark the excel range A1:B10 by selecting A1 and then using the shift key to select B10.

k)

Click OK.

l)


m)

Set the Refresh on Load property.

Figure 177: Refresh on Load

n) 2.

Click Close.

Add a list box component to the Xcelsius canvas and connect it to the first QaaWS. This list box is used to retrieve the values from the QaaWS. Later you will configure the component with trigger cells to interact with another component. a)

Drag and drop a list box onto the canvas. Note: Choose the selectors category button and scroll down to find the list box.


526


2009




Figure 178: List box

b)

Double-click the list box component.

c)

Set the Insertion Type option to Value.


2009


527


BO100

BO100

Figure 179: Insertion Type

3.

d)

Select the red arrow icon next to source data and choose the excel range for the country keys (A1:A10) by selecting A1 then holding Shift key and selecting A10. Choose OK.

e)

select the red arrow icon next to labels area and choose the excel range for the country descriptions (B1:B10) by selecting B1 then holding Shift key and selecting B10. Choose OK.

f)

Set the Destination to a cell in the spreadsheet. Select the red arrow icon next to the Destination Cell and choose cell F1 in Excel. Choose OK. Note: Remember this cell because this cell will be used as trigger cell.

Create another data connection in Xelsius using the second Query as a Web Service. a)


b)

Click Add.

c)

Select Query as a Web Service. Continued on next page

528


2009




d)

Select the newly created connection.

Figure 180: New connection

e)

Paste the URL from the second created QaaWS web service into the field WSD URL. Note: Find the URL for GR##_QaaWS_02. If the URL is not in the clipboard, go the Query as a Web Service and select the GR##_QaaWS_02. Click To Clipboard.

f)

Click Import. Note: The web service will also show the SAP variable in the list of required input values.

g)

Click the row folder of the Return Values.

h)

Click the icon next to Insert In.

i)

Mark the required range C1: D50 in the excel spreadsheet. Note: The cells need to be different than the cells from the previous web service.

j)

Click OK.

k)

Click on the item for the SAP variable (desired Country) in the list of Input Values

l)

Click the icon next to Read From.

m)

Mark the cell F1 in the excel spreadsheet Note: This cell needs to be identical to step 2 (the cell that is used as destination from the list box). Continued on next page

2009


529


BO100

n)


o)

Click the icon next to Trigger Cell.

p)

Mark the cell F1 in the excel spreadsheet

BO100

Note: This cell needs to be identical to step 2 (the cell that is used as destination from the list box). q)

Select the option When Value Changes.

Figure 181: Trigger cell when value changes

r) 4.

Click Close.

Create a pie chart onto the canvas and link it to the second QaaWS. a)

Drag and drop a pie chart onto the canvas.


530


2009




Figure 182: Pie chart

b)


c)

Click the red arrow icon next to the Data Values.

d)

Mark the excel range D1:D50 by selecting D1 and then using the shift key to select D50. Note: In this example the result set is from the second web service.

e)

Click OK.

f)

Click the red arrow icon next to the Data Labels.

g)

Mark the excel range C1:C50 by selecting C1 and then using the shift key to select C50

h)

Navigate to the Behavior tab.


2009


531


BO100

BO100

Figure 183: Ignore Blank cells in Values

i)

Select the option Ignore Blank cells in Values.


532


2009




Figure 184: Design

5.

Preview the Xcelsius file and see how the components interact with each other. a)

Click Preview. Note: Each change of the country value will return a different pie chart for a different list of regions.

6.

Save the Xcelisus document to Enterprise and view the flash document using SAP authentication. a)

Select the menu File → Export → BusinessObjects Platform. Note: When exporting to the BusinessObjects Platform the actual runtime flash 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.

2009

b)

Select a folder on your BusinessObjects Enterprise system. Navigate to SAP → 2.0 → CLNT900 in your BusinessObjects Enterprise system.

c)

Enter a file name.

d)

Enter a file name GR## Xcelsius QaaWS03.

e)

Click Save.

f)

View the Xcelsius dashboard in InfoView using the SAP authentication.


533


BO100

BO100

Lesson Summary You should now be able to: • Use Xcelsius with Query as a Web Service • Connect Xcelsius with Query as a Web Service with SAP variables

534


2009



Unit Summary

Unit Summary You should now be able to: • Create a Query as a Web Service against SAP data sources with variables • Use Xcelsius with Query as a Web Service • Connect Xcelsius with Query as a Web Service with SAP variables

2009


535


BO100

Unit Summary

536


2009


BO100

Test Your Knowledge


Through Xcelsius you can combine multiple datasources inside Excel and these multiple excel files can be used by multiple web services. Determine whether this statement is true or false.

□ □

2009

True False


537


BO100

BO100

Answers 1.

Through Xcelsius you can combine multiple datasources inside Excel and these multiple excel files can be used by multiple web services. Answer: True

538


2009


Test Your Knowledge



Unit Summary

539


2009


BO100

Unit Summary

540


2009


BO100

SAP Security Integration and Creating Publications Unit Overview This unit provides you with an overview of how existing data level security of an SAP system can be leveraged for a publication. In this unit, you will learn about:

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

Describe the concept of server side trust Describe the components of server side trust Configure the SAP server for server side trust Configure the SAP BusinessObjects Enterprise system as a trusted system with SAP Configure the SAP BusinessObjects Enterprise services Create a publication for Crystal Reports Describe the workflow for a publication with server side trust

Unit Contents Lesson: Server side trust and impersonation ................................... 543 Procedure: Steps to configure server side trust ............................ 547 Lesson: SAP server configuration ................................................ 549 Procedure: SAP Cryptographic Library download ......................... 550 Procedure: SAP Instance Profile parameters .............................. 552 Lesson: SAP BusinessObjects Enterprise Configuration...................... 559 Procedure: Prerequisites ...................................................... 561 Procedure: Deploying SAP Cryptographic Library to BusinessObjects Enterprise server ............................................................... 562 Procedure: Generating BusinessObjects Enterprise PSE file on BusinessObjects Enterprise Server .......................................... 564

2009


541


Unit 13

BO100

Procedure: Importing the generated BusinessObjects Enterprise PSE file into SAP system ................................................................ 567 Procedure: Exporting a SAP server certificate from the SAP server .... 570 Procedure: Working with the SNC Access Control List ................... 572 Procedure: Linking the exported SAP certificate to the BusinessObjects Enterprise PSE File ............................................................ 574 Procedure: Adding a Server Intelligence Agent ............................ 577 Procedure: Granting OS access to the BusinessObjects Enterprise PSE File................................................................................ 590 Procedure: Configuring SNC options in the Central Management Console (CMC) ............................................................................ 592 Lesson: Creating a publication .................................................... 596 Procedure: Creating a publication for Crystal Reports .................... 597 Exercise 25: Establishing Secure Network Communication (SNC) and Creating a publication .......................................................... 605

542


2009


Unit 13: SAP Security Integration and Creating Publications

Lesson: Server side trust and impersonation

Lesson: Server side trust and impersonation Lesson Overview In this unit you will learn about the concept of SAP server side trust (SNC) and the involved components.


Describe the concept of server side trust Describe the components of server side trust

Business Example You are planning to implement a BusinessObjects Enterprise solution integrated with SAP NetWeaver BW and need to ensure that the server side trust and impersonation is configured correctly in your environment.

Server side trust In combination with BusinessObjects Enterprise the concept of server side trust will be used to schedule reports for a defined set of SAP users or user groups and to use the server side trust to then impersonate during the scheduling process. In this way the scheduling process can be executed for multiple SAP accounts and the SAP data level security for each user is used. Impersonation is a technique that allows a system to act on behalf of a different user or security context. Entity A grants entity B the trust to authenticate with different users in a password-less authentication. In other words, entity B leverages the granted trust to use the impersonation function and is able to execute the application on behalf of a different set of users. In the example of a publishing process of a report the goal is to schedule a report for a defined set of users and user groups while ensuring data-level security. Based on the impersonation and the trust configuration options between BusinessObjects and the SAP server, the SAP server is granting the BusinessObjects processing servers the right to use the impersonation and authentication with the set of users on the SAP server without the need for a password.

2009


543


BO100

BO100

In order for a component to impersonate an SAP account without providing a password, the component must have identified itself with the SAP server using an authentication method stronger than a username and password. The component is required to run under credentials that are authenticated using a Secure Network Communication (SNC) provider and the credentials are required to be configured to allow impersonation without the use of a password. In the case of BusinessObjects Enterprise the processing servers like Crystal Reports Job and Page server and the Web Intelligence Processing server need to be configured to run under such an SNC account.

Components of server side trust This image shows the involved components and the required steps to configure trust between the SAP system and SAP BusinessObjects Enterprise system.

544


2009




Figure 185: Components and the required steps to configure trust between BusinessObjects Enterprise and the SAP system

1. 2. 3. 4. 5. 6. 7.

Deploy and configure the SAP Cryptographic Library on your SAP system. Deploy and configure the SAP Cryptographic Library on your SAP BusinessObjects Enterprise system Generate a PSE file and a certificate from your SAP BusinessObjects Enterprsie system Import the certificate file from the SAP BusinessObjects Enterprise system to the trust manager of your SAP system. Export a certificate from your SAP system. Import the certificate file from your SAP system to the PSE file from your SAP BusinessObjects Enterprise system. Grant the credentials being used to run the SAP BusinessObjects Enterprise services access to the PSE file from the SAP BusinessObjects Enterprise system.

SAP Cryptographic Library The SAP cryptographic library is delivered separately from the core SAP product, It is the default security product for performing encryption functions in SAP Systems. For example, you can use it for providing Secure Network Communications (SNC) between various SAP server components, for Secure store and Forward (SSF) use, or for using the Secure Sockets Layer (SSL) protocol with the SAP Web Application Server. Here we are only interested in its use for SNC purposes.

2009


545


BO100

BO100

Caution: Restrictions: The SAP Cryptographic Library’s usage agreement restricts its use to server to server configurations only, i.e for server side trust SNC setups. If you want to use SNC with frontend components (for example, SAP GUI for Windows), i.e for client-side SNC setups, then you must purchase an SNC-certified partner product. Please see SAP Notes 597059 and 397195. Note: Other SAP certified security products can also be used to configure server side SNC trust between BOE and SAP servers. In these lessons, we only document a configuration that uses the SAP cryptographic library security product. See SAP Help on SNC and the section External Security Products (http://help.sap.com/saphelp_nw70/helpdata/EN/e6/56f466e99a11d1a5b00000e835363f/frameset.htm ).

Personal Security Environment A Personal Security Environment store (PSE file) contains (a) the private-key certificate of the owner or component that created the PSE file and (b) a list of any public-key certificates of other components/parties that have been identified as trusted components/parties. A PSE file is password protected to prevent illegal certificates being added or valid certificates being removed by anyone who is not the PSE owner. In addition though, an Operating System credential can be identified to the PSE store and granted passwordless usage of the PSE file and its certificates.

546


2009




Steps to configure server side trust 1.

The SAP Cryptographic library is deployed and configured on the SAP system.

2.

The SAP Cryptographic library is deployed and configured on the processing components of the BusinessObjects Enterprise (BOE) system.

3.

A PSE file is generated for the BOE system.

4.

A public certificate is exported from the BOE PSE file and imported to the SAP system PSE.

5.

Note: SAP PSE file was also generated as part of step 1.

6.

A public certificate is exported from the SAP PSE file and imported into the PSE file for the BOE system.

7.

The OS credentials used to running the BOE reporting service(s) are identified to the PSE file for the BOE system.

Result After these steps, the BusinessObjects Enterprise system and the SAP system have exchanged certificates and are now both aware of each other and identify the other as a trusted system. In particular, the BOE server can now be configured the right on the SAP server to impersonate one or more SAP user credentials on this SAP system without an SAP user password.

2009


547


BO100

BO100

Lesson Summary You should now be able to: • Describe the concept of server side trust • Describe the components of server side trust

548


2009



Lesson: SAP server configuration

Lesson: SAP server configuration Lesson Overview In this lesson you will learn the required steps on the SAP server to establish trust between the SAP server and BusinessObjects Enterprise.


Configure the SAP server for server side trust

Business Example You are planning to implement a BusinessObjects Enterprise solution integrated with SAP NetWeaver BW and need to ensure that the server side trust and impersonation is configured correctly in your environment.

2009


549


BO100

BO100

SAP Cryptographic Library download Use As a first step you need to download the SAP Cryptographic library. The file can be downloaded from the SAP service marketplace.

Procedure 1.

Open the URL http://service.sap.com/SWDC (Software Distribution Center).

2.

Provide the user name and password to get access to the website.

3.

Navigate to Download → SAP Cryptographic Software.

Figure 186: SAP Cryptographic Software

4.

Download the SAP crypto library files for the relevant hardware and platforms that BOE and SAP servers are running on.

5.

Unpack the downloaded file with the SAPCAR tool.


550


2009




Result • • •

2009

The SAP Cryptographic Library (sapcrypto.dll for Windows or libsapcrypto.ext for UNIX, where ext=Unix file extension). A license ticket file (ticket). The configuration tool (sapgenpse.exe).


551


BO100

BO100

SAP Instance Profile parameters Use You can now configure the SAP server to make use of the SAP Cryptographic Library.

Prerequisites • •

SAP Cryptographic Library downloaded and expanded for all relevant platforms SAP Administrator's credentials inside SAP as well as Administrator rights to the operating system on which SAP server runs

Procedure 1.

Log onto the operating system of the SAP server.

2.

Copy the SAP Cryptographic Library file to the directory :\usr\sap\\SYS\exe\uc\ on Windows. Note: Replace with the System ID and with the for your SAP server. On older systems this directory was: :\usr\sap\\SYS\exe\run

3.

Copy the “ticket” file to the directory: :\usr\sap\\\sec.

4.

Create an environment variable SECUDIR that refers to the ticket's filepath from the previous step. This environment variable needs to be accessible to the user account that is used to execute the Dispatcher process for the SAP system.

5.

Log onto the SAP server from SAP GUI

6.

Start transaction RZ10.


552


2009




Figure 187: Edit Profiles

7.

Select the Instance profile.

8.

Select the option Extended maintenance.

9.

Click Change to edit.

10. Add the following profile parameters: Profile parameter

Value

ssf/name

SAPSECULIB

ssf/ssfapi_lib

Enter the full path to the SAP Cryptographic library


2009


553


BO100

BO100

sec/libsapsecu


snc/gssapi_lib


snc/identity/as

Distinguished name (DN) for your SAP system

Note: The Distinguished name (DN) for your SAP system should follow the LDAP naming convention: Tag

Meaning

Description

CN

Common name

Name of the certificate proprietor

OU

Organizational Unit

Name of the organizational unit

O

Organization

Name of the organization

C

Country

Country in which the proprietor resides

Examples: •

Example: For a system ZTE this might defined in as: p:CN=ZTE, OU=KPS, O=SAP-AG, C=DE

Note: The prefix “p:” is required for the SAP Cryptographic library when referring to the DN of the SAP system.


554


2009




Figure 188: For example:

11. After adding these values restart the SAP system. 12. Once the system is up and running again start transaction STRUST. Note: You should be able to identify entries for SNC and SSL after the previous configuration steps.


2009


555


BO100

BO100

Figure 189: Example STRUST view:

13. Right-click the folder entry SNC SAP Cryptolib. 14. Select Create. Note: The configured Distinguished Name you specified in RZ10 should show up. 15. Click OK. 16. Click Password. 17. Assign a password to the PSE file. Note: Do not lose this password as you will be prompted for this password every time you view or edit the PSE in transaction STRUST. 18. Click Save. Caution: If you leave out step 17 and step 18 your SAP server won’t start after activating SNC! Continued on next page

556


2009




19. Start transaction RZ10. 20. Select the Instance profile. 21. Select the option Extended maintenance. 22. Click Change. 23. Add the following profile parameters: Profile parameter

Value

snc/accept_insecure_rfc

1

snc/accept_insecure_r3int_rfc

1

snc/accept_insecure_gui

1

snc/accept_insecure_cpic

1

snc/permit_insecure_start

1

snc/data_protection/min

1

snc/data_protection/max

3

snc/enable

1

Note: The snc/accept_insecure_* parameters and values are set to 1 ensure that previous, unsecure, communication methods are still permitted. The snc/data_protection is set to the minimum value (1) for authentication and to the maximum value (3) for privacy. 24. Restart the SAP system.

2009


557


BO100

BO100

Lesson Summary You should now be able to: • Configure the SAP server for server side trust

558


2009



Lesson: SAP BusinessObjects Enterprise Configuration

Lesson: SAP BusinessObjects Enterprise Configuration Lesson Overview In this lesson you will learn the necessary steps on the SAP BusinessObjects Enterprise system to establish trust between the SAP BusinessObjects Enterprise system and the SAP server.


Configure the SAP BusinessObjects Enterprise system as a trusted system with SAP Configure the SAP BusinessObjects Enterprise services

Business Example The main motivation for configuring server side trust using SNC (Secure Network Connection) between BusinessObjects Enterprise Servers and SAP Server is to allow passwordless impersonation by a BusinessObjects reporting server of one or more SAP users when running a data query for each user against SAP server. This scenario would be required when: • •

report bursting / publications are being scheduled on behalf of different/multiple SAP users BusinessObjects Enterprise client session has been authenticated using a non-SAP authentication method or SAP credentials from another SAP entitlement system; and passwordless single sign-on is required using an aliased SAP logon required when the BOE reporting server refreshes against this a different SAP server. using SAP authentication using the same SAP entitlement credentials. – –

•

2009

AD or LDAP authentication of client session SAP server is a different entitlement system/logical system to the SAP credentials used to login to BOE client session. i.e running a SAP report on a different SAP server in the landscape. BOE client session authenticated using Single sign on using SAP token (Enterprise Portal) and SAP reports are being scheduled at a future point in time (after token expiry date).


559


BO100

BO100

Objective 1 Overview: Establishing trust between BusinessObjects Enterprise and SAP After downloading and unzipping the SAP Cryptographic Library, you can now configure the BusinessObjects Enterprise server to make use of the file by following the following procedures: • • • • • •

560

Configure BusinessObjects Enterprise server side environment Generate the PSE file for BusinessObjects Enterprise and export the certificate, and Import this certificate to the SAP system Trust Manager to establish the trust. Next, export a SAP server certificate from the SAP server and Import the certificate from the SAP server into the PSE file for BusinessObjects Enterprise server Create a System ID for the BusinessObjects Enterprise system allowing password-less impersonation.


2009




Prerequisites 1.

2009

We assume that the SAP server has been enabled for server side trust using SNC.


561


BO100

BO100

Deploying SAP Cryptographic Library to BusinessObjects Enterprise server Use To configure SAP Cryptographic Library on the BusinessObjects Enterprise server

Procedure 1.

Logon to the operating system of the BusinessObjects server.

2.

Create a folder :\Program Files\SAP\CRYPTO. Note: The above mentioned folder path is an example. This folder can be on a different drive and the folder can have a different location and name.

3.

Add this folder location to the environment variable PATH.

4.

Copy the SAP Cryptographic Library to this folder :\Program files\SAP\CRYPTO.

5.

Copy the PSE maintenance tool (sapgenpse.exe) to the same folder :\Program files\SAP\CRYPTO.

6.

Add a system wide-environment variable SNC_LIB pointing to the full path of the SAP Cryptographic library (for example, ::\Program Files\SAP\CRYPTO\sapcrypto.dll).

7.

Create a subfolder called SEC in the folder (for example, :\Program Files\SAP\CRYPTO\SEC).

8.

Add a system wide environment variable SECUDIR pointing to the subfolders SEC.

9.

Copy the ticket file from SAP Cryptographic Library to the SEC sub-folder.

Tips and common mistakes: • •

562

Check spelling as it is case sensitive. To add/edit the environment, click Start → Control Panel → System. Click Advanced and select Environment Variables.


2009




Validation tests: • •

2009

In command line, type sapgenpse -h. You should get a help screen. In command line, type set snc_lib or set secudir to confirm the path. You should not get any errors.


563


BO100

BO100

Generating BusinessObjects Enterprise PSE file on BusinessObjects Enterprise Server Use In order for SAP to accept a BusinessObjects Enterprise system as a trusted entity, the relevant BusinessObjects Enterprise server needs to have access to a PSE file and this file needs to be associated with the SAP system. This link, whereby the SAP system trusts BusinessObjects Enterprise and BusinessObjects Enterprise trusts the SAP system is established by sharing a public version of each other’s certificate. To generate the PSE file for BusinessObjects Enterprise (on Windows):

Procedure 1.

Log onto the operating system of the BusinessObjects server.

2.

Click Start → Run.

3.

Enter CMD.

4.

Click OK.

5.

Navigate to the folder where it contains the PSE maintenance tool. Note: For example :\Program Files\SAP\CRYPTO.

6.

Use the following command to create a PSE file: sapgenpse.exe gen_pse –v –p TWDFXXXX.pse Note: TWDFXXXX.pse represents your BOE machine ID. This will become the file for your BOE PSE file.


564


2009




Figure 190: Command Prompt

7.

Enter a PIN. Note: Remember this PIN as you will be asked to reenter it later.

8.

Press Enter.

9.

Re-enter the PIN.

10. Press Enter. 11. Enter a distinguished name for your BusinessObjects Enterprise system. For example: CN=TWDFXXXX, OU=KPS, O=BOBJ, C=CA. Note: The Distinguished name (DN) for your SAP system should follow the LDAP naming convention: Tag

Meaning

Description

CN

Common name

Name of the certificate proprietor

OU

Organizational Unit

Name of the organizational unit

O

Organization

Name of the organization

C

Country

Country in which the proprietor resides Continued on next page

2009


565


BO100

BO100

12. Press Enter. 13. To export the certificate of the PSE file use the following command: sapgenpse.exe export_own_cert –v –p TWDFXXXX.pse –o myTWDFXXXX.cert Note: TWDFXXXX.pse represents the filename for the PSE file and myTWDFXXX.cert represents the name for the exported certificate from the TWDFXXXX.pse certificate store.


14. Enter the PIN that was entered previously. 15. Press Enter.

Tips and common mistakes: • • •

Check spelling as it is case sensitive. .pse files are not accepted by SAP STRUST transaction, so .cert file must be used. Make sure you start in the CRYPTO folder, or else you won’t find the .cert file for uploading in STRUST later.

Validation tests: Look for the .pse and .cert files in the folder below: • •

566

:\Program Files\SAP\CRYPTO should contain the .cert file. :\Program Files\SAP\CRYPTO\SEC should contain the .pse file.


2009




Importing the generated BusinessObjects Enterprise PSE file into SAP system Use Now that you have created the PSE file and exported the certificate, you need to import the certificate to the SAP system Trust Manager to establish the trust. To configure the trust on the SAP server:

Procedure 1.

Log onto SAP server.

2.

Start transaction STRUST .

3.

Open the folder SNC (SAP Cryptolib)in the left hand frame:

Figure 192: SNC (SAP Cryptolib)

4.

Double-click the entry inside the folder.

5.

Enter the password that was defined earlier in RZ10 (see previous lesson). Continued on next page

2009


567


BO100

6.

BO100

Click Import Certificate (left button)

Figure 193: Import Certificate

7.

Select the option Base64.

8.

Enter the path to the certificate file myTWDFXXXX.cert generated earlier from the BusinessObjects Enterprise system.

Figure 194: Enter

9.

Click Enter.

10. Click Add to Certificate List. Continued on next page

568


2009




Figure 195: Add

11. Click Save.

2009


569


BO100

BO100

Exporting a SAP server certificate from the SAP server Use Now that you have imported the PSE file from BusinessObjects Enterprise to the SAP system, you need to: 1. 2.

Export a SAP server certificate from the SAP server. Import it to the BusinessObjects Enterprise system.

To export the certificate from the SAP server

Procedure 1.


2.

Start transaction STRUST.

3.

Open the folder SNC (SAP Cryptolib).

4.

Double-click the entry.

5.

Enter the password that was defined earlier.

6.

Double-click the entry for the Own Certificate of the SAP server.

Figure 196: Double Click

7.

Click Export certificate.

8.

Select the option Base64.

9.

Enter a filename SAP_TWDFXXXX.cert for the certificate.

10. Click Enter. 11. Close transaction STRUST.

570


2009





•

2009

Make sure to choose the SNC (SAP Cryptolib) folder, not the System PSE folder. Import your .cert, NOT .pse file. Don’t forget to add and save immediately. Make sure to recognize the certificate name change at the bottom half of the screen when you double click the SAP Owner. Don’t re-export what you just imported. Don’t forget to save.


571


BO100

BO100

Working with the SNC Access Control List Use Now that you have exported the certificate from the SAP server, you have two outstanding tasks. You need to 1. 2.

Import the certificate from the SAP server to the PSE file from BusinessObjects Enterprise and Create a system ID in the SNC Access Control List (ACL).

To create the system ID:

Procedure 1.


2.

Start transaction SNC0.

Figure 197: SNC: Access Control List (ACL) for Systems

572

3.

Click New Entries.

4.

Enter the name of your BusinessObjects Server as System ID (this is just a descriptive identifying name)

5.

Enter the exact SNC name (distinguished name) that was entered when creating the BusinessObjects Enterprise PSE file in the SNC name field with a prefix “p:”. Continued on next page


2009




6.

Select the checkboxes Entry for RFC activated and Entry for ext ID activated. Uncheck all others.

7.

Click Save. Note: If correctly entered, you will get a green check and the message Canonical Name Determined.

Result After the configuration steps of the above procedure, the configured System ID is allowed to leverage the SNC configuration and to logon via an external ID and use impersonation.

Tips and common mistakes: •

STRUST and SNC0 are a one user at a time transaction

Validation tests: Look for the new files created in your folder: •

2009

:\Program Files\SAP\CRYPTO should contain the SAP_TWDFXXXX.cert file.


573


BO100

BO100

Linking the exported SAP certificate to the BusinessObjects Enterprise PSE File Use As a final step you need to import the certificate of the SAP system to the PSE file for the BusinessObjects Enterprise system to identify the SAP system as a trusted partner. To import the certificate from the SAP server to BusinessObjects Enterprise (on Windows):

Procedure 1.

Log onto the operating system of the BusinessObjects server.

2.

Click Start

3.

Click Run.

4.

Enter CMD

5.

Click OK.

6.

Navigate to the folder for the PSE maintenance tool. Note: In this example workflow, the folder is :\Program Files\SAP\CRYPTO.

7.

Copy the certificate file created from the SAP server to this folder.

8.

Now enter the following command: sapgenpse.exe maintain_pk –v –a SAP_TWDFXXXX.cert -p TWDFXXXX.pse Note: TWDFXXXX.pse denotes the placeholder for the filename for the PSE file on the BusinessObjects Enterprise server. SAP_TWDFXXXX.cert is a placeholder for actual the filename of the SAP server certificate file.


574


2009






The link is between the SAP .cert file and BOE .pse file, not .cert to .cert. Type sapgenpse maintain_pk –h for help on this command. You must reconfigure the BusinessObjects Enterprise services after this procedure and restart the BusinessObjects Enterprise servers.

Objective 1 Summary: Establish trust between BusinessObjects Enterprise and SAP In summary, after the previous configuration steps, you achieved the following: • • • •

2009

The SAP Cryptographic library is deployed and configured on the SAP server. The SAP Cryptographic library is deployed and configured on the BusinessObjects Enterprise server. Certificates have been exchanged between BusinessObjects Enterprise and the SAP server to establish trust between these two systems. A System ID has been created on the SAP server for the BusinessObjects Enterprise system entity (i.e. distinguished name or DN) allowing it password-less impersonation against the SAP server.


575


BO100

BO100

Objective 2 Overview: Configure BusinessObjects Enterprise services With the trust established between BusinessObjects Enterprise and the SAP server, you can now configure the processing tier from BusinessObjects Enterprise to leverage this configuration so that in a next step you can use the trust to configure a publication for a report object. Unless all Web Intelligence, Crystal Reports and Voyager processing services are running under credentials that have access to the PSE file from the BusinessObjects Enterprise system, the administrator has three options for the configuration: 1.

2.

3.

A single Server Intelligence Agent is given access via the operating credentials used to execute the service to the BusinessObjects Enterprise PSE file. This is the simplest option, but this results in all services of the BusinessObjects Enterprise system having access to the BusinessObjects Enterprise PSE file. An additional Server Intelligence Agent is created and the Web Intelligence, Crystal Reports and Voyager processing services are added to the new service. In this way only specific configured services are granted access to the BusinessObjects Enterprise PSE file. An additional Server Intelligence Agent is created and the Web Intelligence, Crystal Reports and Voyager processing services are added to the new service. In addition, Server Groups are created and associated with the content. Note: •

For the purpose of this lesson, we will continue with option 2, i.e:

•

1. Add a Server Intelligence Agent. 2. Grant access to the PSE File to the appropriate user accounts. 3. Configure SNC options in the Central Management Console (CMC) In addition to the processing tier, the Application Server (by default, Tomact) needs to have access to the PSE file. When creating a Server Group (i.e. Option 3), you need to also add the Publication Job Server, Destination Job Server, Adaptive Job Server, and Adaptive Processing Servers also needs to be added to the server group.

•

576


2009




Adding a Server Intelligence Agent Use To configure the processing tier from BusinessObjects Enterprise:

Procedure 1.

Start the Central Configuration Manager: Start → Programs → BusinessObjects XI Release 3 → Central Configuration Manager.

Figure 199: CCM

2.

Click Add Server Intelligence Agent.


2009


577


BO100

BO100

Figure 200: Add Server Intel Agent

3.

Click Next.


578


2009




Figure 201: Next

4.

Enter the Name and Port for the new Server Intelligence Agent

5.

Click Next


2009


579


BO100

BO100

Figure 202: Next

6.

Enter the name of the CMS, an administrative account and the password.

7.

Click Next.


580


2009




Figure 203: Next

8.

Click Finish.

Figure 204: Finish

9.

Select the newly created Server Intelligence Agent and click Properties.


2009


581


BO100

BO100

Figure 205: Properties

10. Uncheck the System Account option.


582


2009




Figure 206: System Account

11. Enter the account which has granted access to the PSE file with password. 12. Click OK. 13. Select the newly created Server Intelligence Agent and click Start. 14. Select the Apache Tomcat server in the Central Configuration Manager. 15. Click Stop. 16. Select the Apache Tomcat Server and click Properties


2009


583


BO100

BO100

Figure 207: Properties

17. Uncheck the System Account option.


584


2009




Figure 208: System Account

18. Enter the account which has granted access to the PSE file with password. 19. Click OK. 20. Select the Apache Tomcat server and click Start. 21. Log onto the Central Management Console.


2009


585


BO100

BO100

Figure 209: CMC

22. Navigate to the Servers area.

Figure 210: Servers Area

23. Select the menu Manage → New → New Server.


586


2009




Figure 211: New Server

Note: Depending on which services are required for the deployment, select the required option in the service category. For this general procedure, you will configure a Crystal Reports Scheduling Server and Crystal Reports Processing Server as an example. 24. Select Crystal Reports as Service Category. 25. Select Crystal Reports Scheduling Service as Service.

Figure 212: Service


2009


587


BO100

BO100

26. Click Next. 27. Select Destination Configuration Service from Available Additional Services and click > to bring it to Selected Services. 28. Click Next. 29. Select the newly created Server Intelligence Agent from the list of Nodes. 30. Click Create. 31. Select the menu Manage → New → New Server. 32. Select Crystal Reports as Service Category. 33. Select Crystal Reports Processing Service as Service. 34. Click Next. 35. Select Single Sign-On Service from Available Additional Services and click > to bring it to Selected Services.

Figure 213: Single Sign-On

36. Click Next. 37. Select the newly created Server Intelligence Agent from the list of Nodes. 38. Click Create.


588


2009




39. Select the newly created server from the list of servers and start the service. Note: Based on this configuration the newly created processing service uses the same account that is being used for the Server Intelligence Agent.


2009

In the CMC, make sure the new added services are enabled and running.


589


BO100

BO100

Granting OS access to the BusinessObjects Enterprise PSE File Use At this point, you need to associate the BusinessObjects Enterprise PSE file with the credentials that are being used to execute the BusinessObjects processing services (for example, Web Intelligence Report Server, Crystal Reports Job Server, MDAS Server). To associate the PSE File with the credentials (Windows):

Procedure 1.

Log onto the operating system of the BusinessObjects service with the credentials that are used to execute the services.

2.

Click Start.

3.

Click Run.

4.

Enter CMD.

5.

Click OK.

6.

Navigate to the folder for the PSE maintenance tool.

7.

Enter the following command: sapgenpse.exe seclogin –p TWDFXXXX.pse Note: TWDFXXXX.pse denotes the file name for the PSE file of the BusinessObjects Enterprise service. Hint: If no additional options the tool assumes the currently logged on user account will receive access to the PSE file. If To grant access to another user, e.g domainName\userName, use the following command line: sapgenpse.exe seclogin –p TWDFXXXX.pse –O domainName\userName


590


2009





8.

Enter the following command to verify passwordless access to the content of the PSE file: sapgenpse.exe maintain_pk –l When running this command, the important outcome should be that the output is listed without any prompt to enter a PIN. Note: If no PIN prompted, then the credentials have been passed between SAP and BOE successfully.


You can now type sapgenpse get_my_name –p TWDFXXXX.pse to get the DN

Validation tests: Look for a file called cred_v2 in the SEC folder. If you get errors with the sapgenpse seclogin command, you can always delete this file and try again copying the certificates from the SAP system and BOE system and link them together again for troubleshooting, without having to start completely over again.

2009


591


BO100

BO100

Configuring SNC options in the Central Management Console (CMC) Use After configuring all the above relevant steps, you can enable SNC for the entitlement system in the Central Management Console. To configure SNC for the entitlement system:

Procedure 1.

Log onto Central Management Console.

2.

Click Authentication.

3.

Double-click SAP.

4.

Navigate to the SNC Settings tab

5.

Select the required entitlement system.

Figure 215: SNC


592


2009




6.

Check the option Enable Secure Network Communication (SNC) in the category Basic settings.

7.

Select Authentication in the category Quality of Protection

8.

Enter the full path of the SNC library. Note: This is identical to the SNC_LIB environment variable.

9.

Enter the SNC name of the SAP system for the Mutual authentication settings with a prefix “p:”. Note: Enter the Distinguished Name (DN) that you get from the command line sapgenpse maintain_pk –l, with a p: prefix.

10.

Enter the SNC name of the BusinessObjects Enterprise system for the Trust settings with a prefix “p:”. Note: Enter the Distinguished Name (DN) that you get from the command line sapgenpse get_my_name –p TWDFXXXX.pse, with a p:prefix.

Figure 216: SNC

11. Click Update.

2009


593


BO100

BO100

Objective 2 Summary: Configure BusinessObjects Enterprise services In order to leverage SNC in the BusinessObjects Enterprise services, we covered the three procedures needed to create an additional Server Intelligence Agent configured only for specific BusinessObjects processing tier services running under a credential that has access to the PSE file and how to enable SNC in the Crystal Management Console. 1. 2. 3.

594

Adding a Server Intelligence Agent. Granting access to the PSE File to the appropriate user accounts. Configuring SNC options in the Central Management Console (CMC)


2009




Lesson Summary You should now be able to: • Configure the SAP BusinessObjects Enterprise system as a trusted system with SAP • Configure the SAP BusinessObjects Enterprise services

2009


595


BO100

BO100

Lesson: Creating a publication Lesson Overview In this lesson you will learn how to create a publication for a Crystal Reports or SAP BusinessObjects Web Intelligence object..


Create a publication for Crystal Reports Describe the workflow for a publication with server side trust

Business Example You need to implement a scheduling process for distributing reports to a large set of users and users groups

Publications A publication allows you to schedule an object for a large set of user groups or a set of users and define specific rules about the output format and delivery to each of the recipients. In combination with the server-side trust, you can use a publication to schedule a Crystal Reports or SAP BusinessObjects Web Intelligence object by keeping the data-level security from your SAP system without the need to replicate it, because the SAP BusinessObjects Enterprise system can now act on behalf of the SAP users in a password-free way and thus schedule the report of each SAP user (multipass bursting). Note: For those who are more familiar with the SAP products than the SAP BusinessObjects products, you can compare a publication with the Information Broadcasting functionality offered as part of SAP NetWeaver Business Warehouse.

596


2009



Lesson: Creating a publication

Creating a publication for Crystal Reports Use A publication allows the administrator to configure a scheduling process for a large set of users and user groups and define how the outcome of the scheduling process is distributed to the users. To create a publication in BusinessObjects Enterprise:

Procedure 1.


Figure 217: CMC

2.

Click Folders.


2009


597


BO100

BO100

Figure 218: Click Folders

3.

Navigate to the folder of your report

4.

Select the menu Manage →New → Publication .

Figure 219: Select the Menu

5.

Enter the Title and Description for the publication.

6.

Click Source Documents. Continued on next page

598


2009




Figure 220: Click Source Documents

7.

Click Add.

Figure 221: Click Add

8.

Navigate to the folder for the report object.


2009


599


BO100

BO100

Figure 222: Navigate to the folder for the report object

9.

Select the report.

10. Click OK.

Figure 223: Click OK


600


2009




11. Click Enterprise Recipients.

Figure 224: Click Enterprise Recipients

12. Click Groups List. 13. Select the required groups from the list of available groups. 14. Click the right arrow and move the groups to the list of selected groups. Note: The workflow for adding users is identical. In this example, you will continue with the user groups. 15. Click Destination.


2009


601


BO100

BO100

Figure 225: Click Destination

16. Select the option Business Objects Inbox. 17. Click Additional Options and select Advanced. 18. Select the option One database fetch per recipient (recommended when using row level security within Universes or Business Views). 19. Click Save & Close.

Figure 226: Click OK

20. Select the newly created publication. 21. Select the menu Actions → Schedule . Continued on next page

602


2009




Figure 227: Select

22. Click Enterprise Recipients to verify the settings from the publication. 23. Click Schedule. Note: After a successful scheduling process you should be able to see the result in InfoView for the users that have been configured as recipients.

Workflow for publication with server side trust This image briefly outlines the workflow of publication and the scheduling process resulting out of the publication leveraging the granted server side trust to achieve impersonation.

2009


603


BO100

BO100

Figure 228: Publication and Scheduling Workflow with SNC and Impersonation

604


2009




Exercise 25: Establishing Secure Network Communication (SNC) and Creating a publication Exercise Objectives After completing this exercise, you will be able to: • Create a PSE File for the BusinessObjects Enterprise system • Import a BusinessObjects Enterprise public certificate • Export an SAP public certificate • Configuring the SNC Access list • Import the SAP public certificate • Create a publication

Business Example You are an administrator and need to configure server side trust between SAP BusinessObjects Enterprise and the SAP system before you create a publication for Crystal Reports.

Task 1: Create a PSE File for the BusinessObjects Enterprise system Note: Launch the simulation Create a PSE file.htm in a web browser to practice this exercise Note: In the exercise, replace XX with your staff or training number 1.

Install the SAP Cryptographic Library on the BusinessObjects Enterprise server.

2.

Create a PSE file for the BusinessObjects Enterprise server called TRAINXX.pse. Enter your staff or training number as the PIN Enter the distinguished name:CN=TRAINXX,OU=EDUC,O=SAP,C=CA

3.

Export a public certificate of the owner's user certificate from PSE TRAINXX.pse and call it myTRAINXX.crt

4.

NOTE: Another useful command: To display the distinguished name (DN) of the user certificate inside a PSE: Continued on next page

2009


605


BO100

BO100

sapgenpse.exe get_my_name –p

Task 2: Import a BusinessObjects Enterprise public certificate Importing theBusinessObjects Enterprise certificate into the SAP server PSE Note: Launch the simulation Import a BOE certificate to SAP.htm in a web browser to practice this exercise 1.

Use transaction STRUST to import the public certificate of your BusinessObjects Enterprise system: myTRAINXX.crt

Task 3: Export an SAP public certificate Exporting a public certificate from the SAP server. Note: Launch the simulation Export the SAP certificate.htm in a web browser to practice this exercise 1.

Use transaction STRUST to export a public certificate of the SAP server and name it: SAP_TRAINXX.crt .

Task 4: Configure the SNC Access list Note: Launch the simulation Configure the SNC Access List.htm in a web browser to practice this exercise 1.

Using transaction SNC0, create a new Access Control List (ACL) entry for your BusinessObject Enterprise system with the details: system id: TRAINXX SNC name p:CN=TRAINXX,OU=EDUC,O=SAP,C=CA Enable SNC options: Entry for RFC Activated and Entry for ext. ID Activated


606


2009




Task 5: Import the SAP public certificate Importing the SAP server's public certificate into the BusinessObjects Enterprise PSE Note: Launch the simulation Import the SAP public certificate.htm in a web browser to practice this exercise 1.

Copy the exported SAP pubic certificate SAP_TRAINXX.crt from the previous exercise to the Cryptographic Library's root directory.

2.

Import the SAP public certificate or key SAP_TRAINXX.crt into the BusinessObjects Enterprise TRAINXX.pse store.

Task 6: Add a new Server Intelligence Agent Note: Launch the simulation Add a new SIA.htm in a web browser to practice this exercise 1.

Create an additional Server Intelligence Agent (SIA).

2.

Assign a new Crystal Reports Scheduling Service, Crystal Reports Processing Service, Crystal Reports Cache Service, Crystal Reports Viewing and Modification Service, Web Intelligence Processing Service, and Web Intelligence Scheduling and Publishing Service to the new SIA.

3.

Ensure that the new Server Intelligence Agent and the Tomcat server services are running under the (OS) user account which has password-less access to the TRAINXX.pse PSE file.

Task 7: Grant access to the BusinessObjects Enterprise PSE file Note: Launch the simulation Grant Access to the PSE.htm in a web browser to practice this exercise 1.

Log onto the operating system of your BusinessObjects Enterprise system using the OS user account for SNC use and PSE access that will be used by the SIA and Tomcat services.

2.

From the command line prompt, navigate to the root folder of the SAP Cryptographic library.

3.

Add this OS user account credentials as a user that has SSO or password-less access to the BusinessObjects Enterprise PSE, TRAINXX.pse.


2009


607


BO100

4.

BO100

Run the sapgenpse command to list the public keys in PSE TRAINXX.pse. Ensure that your are not prompted for the PSE pin when running this command (i.e. that the OS user credential now has passwordless access to the BusinessObjects Enterprise PSE)

Task 8: Configure SNC in the Central Management Console Note: Launch the simulation Configure SNC.htm in a web browser to practice this exercise Enabling and configuring SNC in the Central Management Console 1.

Log on to the Central Management Console.

2.

Enable SNC for the specific SAP entitlement system CLNT

3.

Enter the full path to the SAP Cryptographic Library

4.

Enter the SNC name (i.e. Distinguished Name) of the SAP system with a prefixed by “p:” under Mutual authentication settings as configured on the SAP server in STRUST.

5.

Enter the Distinguished Name of your BusinessObjects Enterprise system prefixed by “p:” under Trust settings.

Task 9: Create a publication with a Crystal Reports document. Note: Launch the simulation Create a publication.htm in a web browser to practice this exercise 1.

Log on to Central Management Console of your SAP BusinessObjects system.

2.

Navigate to the Folders area.

3.

Navigate to the folder of the report and create a new publication.

4.

Enter a title and description of your new publication.

5.

Select the Crystal Reports document that you created on the changed BW query.

6.

Click Enterprise Recipients and add the ZBO100 user groups as recipients to the selected area.

7.

Click Destination and check BusinessObjects Inbox check box so that each recipient will receive the output directory to the Inbox folder in the SAP BusinessObjects system. Continued on next page

608


2009




8.

Open the Additional Options and select Scheduling Server Group. Select the server group that you created earlier.

9.

Select Advanced and click One Database Fetch Per Recipient.

10. Save the publication and click schedule to start the process of your publication.

2009


609


BO100

BO100

Solution 25: Establishing Secure Network Communication (SNC) and Creating a publication Task 1: Create a PSE File for the BusinessObjects Enterprise system Note: Launch the simulation Create a PSE file.htm in a web browser to practice this exercise Note: In the exercise, replace XX with your staff or training number 1.

Install the SAP Cryptographic Library on the BusinessObjects Enterprise server. a)

2.

Create a PSE file for the BusinessObjects Enterprise server called TRAINXX.pse. Enter your staff or training number as the PIN Enter the distinguished name:CN=TRAINXX,OU=EDUC,O=SAP,C=CA a)

3.

Export a public certificate of the owner's user certificate from PSE TRAINXX.pse and call it myTRAINXX.crt a)

4.

sapgenpse.exe gen_pse –v –p TRAINXX.pse

sapgenpse.exe export_own_cert –v –p TRAINXX.pse –o myTRAINXX.crt

NOTE: Another useful command: To display the distinguished name (DN) of the user certificate inside a PSE: sapgenpse.exe get_my_name –p a)


610


2009




Task 2: Import a BusinessObjects Enterprise public certificate Importing theBusinessObjects Enterprise certificate into the SAP server PSE Note: Launch the simulation Import a BOE certificate to SAP.htm in a web browser to practice this exercise 1.

Use transaction STRUST to import the public certificate of your BusinessObjects Enterprise system: myTRAINXX.crt a)

Task 3: Export an SAP public certificate Exporting a public certificate from the SAP server. Note: Launch the simulation Export the SAP certificate.htm in a web browser to practice this exercise 1.

Use transaction STRUST to export a public certificate of the SAP server and name it: SAP_TRAINXX.crt . a)

Task 4: Configure the SNC Access list Note: Launch the simulation Configure the SNC Access List.htm in a web browser to practice this exercise 1.

Using transaction SNC0, create a new Access Control List (ACL) entry for your BusinessObject Enterprise system with the details: system id: TRAINXX SNC name p:CN=TRAINXX,OU=EDUC,O=SAP,C=CA Enable SNC options: Entry for RFC Activated and Entry for ext. ID Activated a)


2009


611


BO100

BO100

Task 5: Import the SAP public certificate Importing the SAP server's public certificate into the BusinessObjects Enterprise PSE Note: Launch the simulation Import the SAP public certificate.htm in a web browser to practice this exercise 1.

Copy the exported SAP pubic certificate SAP_TRAINXX.crt from the previous exercise to the Cryptographic Library's root directory. a)

2.

Copy SAP_TRAINXX.crt to the directory where sapcrypto.dll is located. This is directory path is part of the environment variable SNCLIB.

Import the SAP public certificate or key SAP_TRAINXX.crt into the BusinessObjects Enterprise TRAINXX.pse store. a)

sapgenpse.exe maintain_pk –v –a SAP_TRAINXX.cert -p TRAINXX.pse

Task 6: Add a new Server Intelligence Agent Note: Launch the simulation Add a new SIA.htm in a web browser to practice this exercise 1.

Create an additional Server Intelligence Agent (SIA). a)

2.

Assign a new Crystal Reports Scheduling Service, Crystal Reports Processing Service, Crystal Reports Cache Service, Crystal Reports Viewing and Modification Service, Web Intelligence Processing Service, and Web Intelligence Scheduling and Publishing Service to the new SIA. a)

3.

Ensure that the new Server Intelligence Agent and the Tomcat server services are running under the (OS) user account which has password-less access to the TRAINXX.pse PSE file. a)


612


2009




Task 7: Grant access to the BusinessObjects Enterprise PSE file Note: Launch the simulation Grant Access to the PSE.htm in a web browser to practice this exercise 1.

Log onto the operating system of your BusinessObjects Enterprise system using the OS user account for SNC use and PSE access that will be used by the SIA and Tomcat services. a)

2.

From the command line prompt, navigate to the root folder of the SAP Cryptographic library. a)

3.

Add this OS user account credentials as a user that has SSO or password-less access to the BusinessObjects Enterprise PSE, TRAINXX.pse. a)

4.

sapgenpse.exe seclogin –p TRAINXX.pse

Run the sapgenpse command to list the public keys in PSE TRAINXX.pse. Ensure that your are not prompted for the PSE pin when running this command (i.e. that the OS user credential now has passwordless access to the BusinessObjects Enterprise PSE) a)

sapgenpse.exe maintain_pk –l

Task 8: Configure SNC in the Central Management Console Note: Launch the simulation Configure SNC.htm in a web browser to practice this exercise Enabling and configuring SNC in the Central Management Console 1.

Log on to the Central Management Console. a)

2.

Enable SNC for the specific SAP entitlement system CLNT a)

3.

Enter the full path to the SAP Cryptographic Library a)

e.g C:\Program Files \SAP\Crypto\sapcrypto.dll , i,e, as referenced in the SNC_LIB environment variable. Continued on next page

2009


613


BO100

4.

Enter the SNC name (i.e. Distinguished Name) of the SAP system with a prefixed by “p:” under Mutual authentication settings as configured on the SAP server in STRUST. a)

5.

BO100

i.e. As configured in transaction STRUST instance profile, under extended maintenance parameter snc/identity/as

Enter the Distinguished Name of your BusinessObjects Enterprise system prefixed by “p:” under Trust settings. a)

p:CN=TRAINXX, OU=EDUC, O=SAP, C=CA

Task 9: Create a publication with a Crystal Reports document. Note: Launch the simulation Create a publication.htm in a web browser to practice this exercise 1.

Log on to Central Management Console of your SAP BusinessObjects system. a)

2.

Navigate to the Folders area. a)

3.

Navigate to the folder of the report and create a new publication. a)

4.

Enter a title and description of your new publication. a)

5.

Select the Crystal Reports document that you created on the changed BW query. a)

6.

Click Enterprise Recipients and add the ZBO100 user groups as recipients to the selected area. a)

7.

Click Destination and check BusinessObjects Inbox check box so that each recipient will receive the output directory to the Inbox folder in the SAP BusinessObjects system. a)


614


2009




8.

Open the Additional Options and select Scheduling Server Group. Select the server group that you created earlier. a)

9.

Select Advanced and click One Database Fetch Per Recipient. a)

10. Save the publication and click schedule to start the process of your publication. a)

2009


615


BO100

BO100

Lesson Summary You should now be able to: • Create a publication for Crystal Reports • Describe the workflow for a publication with server side trust

616


2009



Unit Summary

Unit Summary You should now be able to: • Describe the concept of server side trust • Describe the components of server side trust • Configure the SAP server for server side trust • Configure the SAP BusinessObjects Enterprise system as a trusted system with SAP • Configure the SAP BusinessObjects Enterprise services • Create a publication for Crystal Reports • Describe the workflow for a publication with server side trust

2009


617


BO100

Unit Summary

618


2009


BO100

Test Your Knowledge


With server side SNC trust is configured and user impersonation granted between SAP server (entity A) and a trusted entity B, entity B can only impersonate exactly one and only one specified SAP user credential without the need of any password. Determine whether this statement is true or false.

□ □ 2.

True False

The SAP Cryptographic Library is the only External Security Product that can be used to configure server side SNC trust between BusinessObjects Enterprise system and an SAP System. Determine whether this statement is true or false.

□ □ 3.

True False

In Secure Network Connection (SNC) terminology, the acronym PSE stands for Page Storage Extension. Determine whether this statement is true or false.

□ □

2009

True False


619


BO100

BO100

Answers 1.

With server side SNC trust is configured and user impersonation granted between SAP server (entity A) and a trusted entity B, entity B can only impersonate exactly one and only one specified SAP user credential without the need of any password. Answer: False False. Entity A can impersonate one or more SAP user credentials that exist on on Entity B without the need of any password.

2.

The SAP Cryptographic Library is the only External Security Product that can be used to configure server side SNC trust between BusinessObjects Enterprise system and an SAP System. Answer: False False. Any External Security Product that supports the following requirements and is certified by SAP can be used. See SAP SNC help: Requirements: To use a security product with SAP systems, the product must meet the following requirements:· • • • •

3.

The product must provide the entire range of functions defined in the GSS-API V2 interface The functions must be dynamically loadable. The product must be available on platforms supported by SAP systems. The product must be certified for use by SAP. The SAP Partner Program certifies external products for use with SAP system.

In Secure Network Connection (SNC) terminology, the acronym PSE stands for Page Storage Extension. Answer: False False. PSE stands for Personal Security Environment - secure store or file containing amongst other items, a private-key certificate identifying the user or owner entity; and a list of imported public-key certificates that identify other parties or entities.

620


2009


Test Your Knowledge



Unit Summary

621


2009


BO100

Unit Summary

622


2009


BO100

Integrating with SAP Enterprise Portal Unit Overview This unit provides you with the steps to integrate BusinessObjects Enterprise with the SAP Enterprise Portal.

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

Import the BusinessObjects Enterprise iView template to the Enterprise Portal Create a new system for the BusinessObjects Enterprise system Create new iViews for BusinessObjects Enterprise content Create a portal page Define the content and layout of portal pages Create portal Worksets Assign content to portal Worksets Create portal roles Assign portal worksets to portal roles Assign a portal role to a portal user Configure the Repository Manager for BusinessObjects Enterprise Use the Repository Manager for reporting Use collaboration features Create an iView for the Repository Manager

Unit Contents Lesson: Integrating BusinessObjects Enterprise content into SAP Enterprise Portal using iViews ................................................................. 625 Procedure: To upload the iView template ................................... 628 Lesson: Portal System landscape for BusinessObjects Enterprise .......... 632 Procedure: To create the portal system landscape ........................ 633

2009


623


Unit 14

BO100

Exercise 26: Creating a new report portal system entry for BusinessObjects Enterprise........................................................................ 643 Lesson: Creating BusinessObjects Enterprise content iViews................ 649 Procedure: To create a new iView ........................................... 650 Exercise 27: Creating iViews for BusinessObjects content ............... 657 Lesson: Creating portal pages .................................................... 662 Procedure: To create a new portal Page .................................... 663 Exercise 28: Creating a portal Page and adding an iView to the Page . 671 Lesson: Creating portal worksets ................................................. 676 Procedure: To create a new portal workset ................................. 677 Exercise 29: Creating a portal Workset ..................................... 679 Lesson: Creating portal roles...................................................... 683 Procedure: To create a new portal Role ..................................... 684 Procedure: To assign the portal Role to a portal User..................... 689 Exercise 30: Creating a portal Role .......................................... 693 Exercise 31: Assigning the portal user to the portal Role ................. 697 Lesson: BusinessObjects Enterprise Repository Manager.................... 700 Procedure: To install the Knowledge Management integration........... 701 Procedure: To verify the installation.......................................... 703 Procedure: To create a new repository manager integration with your BusinessObjects Enterprise system ......................................... 707 Procedure: To use the Repository Manager ................................ 714 Procedure: To use the collaboration features............................... 719 Procedure: To create a new iView ........................................... 723 Exercise 32: Create a new BusinessObjects Repository Manager ...... 727 Exercise 33: Creating a Knowledge Management iView ................. 733

624


2009


Unit 14: Integrating with SAP Enterprise Portal

Lesson: Integrating BusinessObjects Enterprise content into SAP Enterprise Portal using iViews

Lesson: Integrating BusinessObjects Enterprise content into SAP Enterprise Portal using iViews Lesson Overview SAP Enterprise Portal uses iViews as the fundamental building blocks to create portal content. Enterprise Portal comes with many predefined iViews (templates) so portal content administrators can easily create content. BusinessObjects Integration Kit for SAP delivers an iView template for integration of Crystal Reports into the Enterprise Portal. In this lesson you will find how to import the BusinessObjects Enterprise iView template to the SAP Enterprise Portal.


Import the BusinessObjects Enterprise iView template to the Enterprise Portal

Business Example You need to describe the process and steps for displaying BusinessObjects content in the SAP Enterprise Portal.

Portal Objects and Terms

Figure 229: SAP Enterprise Portal

2009


625


BO100

BO100

Figure 230: Portal Objects and Terms

Portal landscape Portal landscape contains portal System objects, which are sets of properties, such as system name, client , or Server. Portal systems Portal systems provide links to any source of information or data that are accessed by SAP Enterprise Portal. System Alias A pointer to the actual portal system to enable flexible creation of IVIEW in a Development >Test>Production scenario. Portal Archive File (PAR) A compressed format for the packaging and delivery of portal objects (mostly supplied by SAP)

BusinessObjects Enterprise iView template The iView template as part of the BusinessObjects XI Integration for SAP Solutions is delivered as a portal archive file and needs to be uploaded to the portal server before it is available to the users.

626


2009




The BusinessObjects portal iView template allows BusinessObjects content to be displayed in the SAP Enterprise portal. The template contains the properties required to configure and display a BusinessObjects Enterprise based report or document, including Crystal Reports, Web Intelligence and Voyager Workspaces. BusinessObjects XI Integration for SAP Solutions includes 3 iViews: iView

Description

Alert iView

This is a sample iview used to display alerts of Crystal Report reports. This is specific to CR reports that are designed with alerts.

Thumbnail iView

This is a sample a iview that displays reports from BusinessObjects Enterprise as thumbnail.

iView Template

This iView template allows EP content administrators create new iViews of the type BusinessObjects Enterprise Report. This is the iView template you use to integrate Crystal Reports into EP. You should not use it to integrate Web Intelligence Reports as this iView template was created specifically for Crystal Reports

There are 2 configuration steps you have to perform before you can create iviews from the BOE iView template: 1. 2.

2009

Import BOE iView template into Enterprise Portal Create a System Landscape in Enterprise Portal


627


BO100

BO100

To upload the iView template Use The iView template that comes with BOE Integration Kit for SAP is a portal archive file that needs to be uploaded to EP before it is available.

Procedure 1.

Log onto the SAP Enterprise Portal. URL: http://portal--800.wdf.sap.corp:50000/irj/portal

2.

Navigate to System Administration > Support.

Figure 231: Support

3.

Click Portal Runtime.


628


2009




Figure 232: Portal Runtime

4.

Click Administration Console.


2009


629


BO100

BO100

Figure 233: Administration Console

5.

Click Browse next to the Archive Uploader. Note: The master iView is installed by default in the following folder: ///Program Files/Business Objects/BusinessObjects Enterprise 12.0/Web Content/Enterprise12/sap/iviews/import/ep The filename is com.businessobjects.pct.masteriview.par.

6.

Select the file.

7.

Click Upload.

Result Uploading the BOE iView template adds the "BusinessObjects Integration Kit -iView template" into the list of templates available when you are creating a new iView from a template.

630


2009




Lesson Summary You should now be able to: • Import the BusinessObjects Enterprise iView template to the Enterprise Portal

2009


631


BO100

BO100

Lesson: Portal System landscape for BusinessObjects Enterprise Lesson Overview In this lesson, you will learn how to create a new system as part of the Enterprise Portal landscape.


Create a new system for the BusinessObjects Enterprise system


Create a new portal system landscape for BusinessObjects Enterprise When creating a new iView for BusinessObjects Enterprise, one of the required parameters is a defined system inside the Enterprise Portal. This system definition includes the details of the BusinessObjects Enterprise system that will be used to host the content displayed inside the an iView.

632


2009



Lesson: Portal System landscape for BusinessObjects Enterprise

To create the portal system landscape 1.


2.

Navigate to System Administration > System Configuration.

Figure 234: System Administration>System Configuration

3.

Click System Landscape.

4.

Navigate to the Portal Content.

5.

Right-click the Portal Content folder.


2009


633


BO100

BO100

Figure 235: Portal Content

6.

Select New > Folder.

Figure 236: New>Folder


634


2009




7.

Enter Folder Name, Folder ID and Folder ID Prefix. Note: The folder name is the display name that appears in the Portal Content, the Folder ID is a unique identifier for the folder.

8.

Click Finish.

Figure 237: Finish

9.

Click OK to close the wizard.

10. Navigate to the new folder. 11. Right-click the folder.


2009


635


BO100

BO100

Figure 238: Folder

12. Select New > System (from template).


636


2009




Figure 239: New>System

13. Select the option SAP system using dedicated application server. 14. Click Next.


2009


637


BO100

BO100

Figure 240: Next

15. Enter the System Name, System ID, and System ID Prefix. 16. Click Next.

Figure 241: Next

17. Click Finish. Continued on next page

638


2009




Figure 242: Finish

18. Ensure the default selection Open the object for editing is selected. 19. Click OK. 20. Select Crystal Enterprise Server as Property Category. Note: Here is where you will specify the information regarding the BOE system that hosts the report and the Web App Server that should be used to redirect the BOE iview requests.

Figure 243: Crystal Enterprise Server


2009


639


BO100

BO100

21. Enter the host name for the Crystal Enterprise server with the port. Note: Enter the fully qualified domain name of the BOE Web Application Server including the port. For example :8080. Hint: If you don't specify fully qualified name for BOE App Server, it may happen that Enterprise Portal determines that not all the machines are on the same DSN domain, causing the following error when trying to view the report through the BOE iview:: "Session Manager will not work Check DSM log for details" 22. Enter the path to the SAP specific applications on the BusinessObjects Enterprise server. Note: This is the virtual directory on the Web Application Server that hosts the BOE applications. By default this virtual directory is /SAP. 23. Select http to be the protocol that is used for the BusinessObjects Enterprise server.

Figure 244: Select Protocol

24. Click Save. 25. Select the Property Category User Management. Here you will configure the authentication method to use. Continued on next page

640


2009




Figure 245: User Management

26. Set the Logon Method property to SAPLOGONTICKET. Note: This is assuming that SAP logon tickets are being leveraged for authentication purposes. 27. Set the Authentication Ticket Type to SAP Logon Ticket. 28. Select the Property Category Connector. Here you will be entering the information of the SAP ABAP system that will be validating the users. This is the system that you have defined previously as an entitlement system in CMC.

Figure 246: Connector


2009


641


BO100

BO100

29. Configure the values for Application Host, Gateway Host, Gateway Service and Logical System Name according to the SAP system. Note: If you don't know how to get the Gateway Service, you just need to connect on the SAP NetWeaver BW server using SAP GUI and run the transaction SMGW. You then should see a column like TP NAME and the value is the Gateway Service. 30. Configure the values for SAP Client, SAP System ID (SID), and SAP System Number according to the SAP system. Note: The entries entered here are the values derived from the used SAP system. 31. Click Save. 32. Select System Aliases in the Display list box. This is the name you will reference to, when creating the iviews. 33. Enter the Alias Name SAP_BW. 34. Click Add.

Figure 247: Add

35. Click Save. 36. Click Close.

642


2009




Exercise 26: Creating a new report portal system entry for BusinessObjects Enterprise Exercise Objectives After completing this exercise, you will be able to: • Review critical settings used in the creation of a portal system for Business Objects Enterprise • Create a Folder in the portal to be used in further portal exercises

Business Example Your instructor is in the role of the portal administrator he has already created a portal system pointing to Business Objects Enterprise. You want to verify that it is pointing to the correct system and what alias was used. You will need this alias to build IViews for BusinessObjects reports. In addition you want to create your own portal folder for organizational purposes using the following information:

Task 1: Review the settings 1.

Log onto the Enterprise Portal.

2.

Verify critical settings were made by your “administrator” (instructor). Note: •

You should be aware that in this case the administrator originally built the system using the “System from template option”. The template chosen was “SAP system using dedicated application server”.

• 3.

Do not change anything.

Now review the system alias. This XX alias is again the one that all students will use in building portal IViews in a follow on exercise. Note: System aliases are used to allow easy changes to underlying systems without the need to change IViews Continued on next page

2009


643


BO100

BO100

Task 2: Create your portal folder Create you own portal folder. This folder could be used to organize new portal systems or as you will be using it, to store portal IViews, pages, work sets and roles in later exercises. 1.

644

Create your own portal folder. Using the information below: Data

Data Value

Folder Name

BO100-XX

Folder ID

BO100-XX

Prefix

COM.SAP


2009




Solution 26: Creating a new report portal system entry for BusinessObjects Enterprise Task 1: Review the settings 1.

Log onto the Enterprise Portal. a)

To easily access portal, locate the link that begins with “http://portal-XXX” It is located in the user menu of client 900 in your assigned system. Click this link and change the XXX to your assigned system id. Log on the portal using your BO100-XX user and password. Do not change the client in the link leave it 800.

2.

Verify critical settings were made by your “administrator” (instructor). Note: •

You should be aware that in this case the administrator originally built the system using the “System from template option”. The template chosen was “SAP system using dedicated application server”.

•

Do not change anything.

a)


b)


c)


d)

Expand the Portal Content , and the BO100 folder to access the BO100-XX system. This XX system is the system all students will use in this class.

e)

Use the context menu (right click) to on the BO100-XX system Open> Object. Now select the appropriate property category (using the drop down box) in the list below and verify that your assigned training systems and clients are set correctly. Note: Do not change anything.


2009


645


BO100

BO100

Property Category : Crystal Enterprise Sever Host Name of Crystal Enterprise Server

: TWDFXXXX.WDF.SAP.CORP:8080)

Path of Crystal Enterprise Server

/SAP

Protocol of Crystal Enterprise Server

http

Property Category : User Management Authentication Ticket Type

SAP Logon Ticket

Logon Method

SAPLOGONTICKET

Property Category : Connector Application Host

SAP application server (For example: tdc00.wdf.sap.corp)

Gateway Host

SAP application server (For example: tdc00.wdf.sap.corp)

Gateway Service

sapgwXX (e.g.:SAPGW50)

Logical System Name

CLNT900

SAP Client

900

SAP System ID

SAP System Number

50

System Type

SAP_BW


646


2009




3.

Now review the system alias. This XX alias is again the one that all students will use in building portal IViews in a follow on exercise. Note: System aliases are used to allow easy changes to underlying systems without the need to change IViews a)

Select System Aliases in the Display list box (top right)

b)

Record the existing Alias Name TRAINING_SYSTEM_XX (case sensitive) on a note pad. You will need this information later.

c)

Click the Close button.

Task 2: Create your portal folder Create you own portal folder. This folder could be used to organize new portal systems or as you will be using it, to store portal IViews, pages, work sets and roles in later exercises. 1.

Create your own portal folder. Using the information below: Data

Data Value

Folder Name

BO100-XX

Folder ID

BO100-XX

Prefix

COM.SAP

a)

Navigate to System Administration → System Configuration.

b)


c)


d)

Right-click the Portal Content folder.

e)

Select New > Folder.

f)

Enter Folder Name, Folder ID and Folder ID Prefix Use: BO100-XX for both name and ID, and com.sap for the prefix.

2009

g)

Click Finish.

h)

Click OK, and remain in the portal system for future exercises.


647


BO100

BO100

Lesson Summary You should now be able to: • Create a new system for the BusinessObjects Enterprise system

648


2009



Lesson: Creating BusinessObjects Enterprise content iViews

Lesson: Creating BusinessObjects Enterprise content iViews Lesson Overview In this lesson, you will learn how to create iViews displaying BusinessObjects Enterprise content.


Create new iViews for BusinessObjects Enterprise content


Create a new iView for BusinessObjects Enterprise content BusinessObjects Enterprise content can be hosted by providing the content specific parameters when creating a new iView based on the imported BusinessObjects Enterprise iView template.

2009


649


BO100

BO100

To create a new iView 1.


2.

Navigate to Content Administration > Portal Content.

3.

Open the folder Portal Content.

4.

Navigate to the folder you created previously when creating the System Landscape.

5.

Right-click the folder.

Figure 248: Folder

6.

Select the menu New > iView.


650


2009




Figure 249: New>iView

7.

Ensure the option iView template is selected.

8.

Click Next.

9.

Select BusinessObjects XI Integration for SAP Solutions– iView template option.

10. Click Next.

Figure 250: Next

11. Enter the following details: iView Name Continued on next page

2009


651


BO100

BO100

This is a display name that appears in the Portal Catalog, Dialog Box and Window that displays a list of iViews. The iView name may contain up to 40 characters of any type, including spaces, but not apostrophes and quotation marks. iView ID This is the unique identifier registered in the Portal Content Directory. This ID appears within the portal administrator environment. The iView ID may contain 40 characters and include alphanumeric characters, underscores (_), dashes (-), dots (.) exclamation point (!), tilde (~) and parentheses. Other special characters and spaces are not permitted. iView ID Prefix If you want all your iViews to follow a specific naming convention, making them easier to locate, you can add a uniform prefix to each system you create. 12. Click Next.

Figure 251: Next

13. Select the option Standard BusinessObjects Enterprise Report. Note: This step allows you to choose between a standard report stored to BusinessObjects Enterprise or a report that has been published via the publishing integration between SAP BW and Crystal Reports. 14. Click Next. Continued on next page

652


2009




Figure 252: Click Next

15. Enter the SAP system alias that was created earlier. 16. Enter the report number into the field BusinessObjects Enterprise Report ID. Note: The report ID is shown as part of the object properties in InfoView and the Central Management Console (CMC). If you specify an ID that does not exist, later when viewing the iview you will just get a blank page without any errors. 17. Enter the following into the Application Parameters: cms_name=:

where

is replaced with your name of the Central Management Server and

is replaced with the port configured for the Central Management Server. For example: cms_name = TWDFXXXX:6400 18. In Viewer Application Page, specify reportView.do


2009


653


BO100

BO100

19. Select the BusinessObjects Enterprise Viewer and a BusinessObjects viewing type. 20. Click Next.

Figure 253: Next

21. Select the option Open for editing when wizard completes. 22. Click Finish.


654


2009




Figure 254: Finish

23. Click Preview. You can now add this iView to any page in the portal. Open the page where you want to add this iView (If you don't have a page, right-click on a folder and select New Page), right click on the iView you want to add and select Add iView to Page > Delta link.

2009


655


BO100


656


2009


BO100


Exercise 27: Creating iViews for BusinessObjects content Exercise Objectives After completing this exercise, you will be able to: • Create iViews for content from BusinessObjects Enterprise

Business Example You are a portal administrator and need to create a new iView to show Crystal Report content from your BusinessObjects Enterprise system.

Task: You will create an IVIEW to directly present a Crystal report to users using SAP Enterprise portal. The IVIEW will point to an existing crystal report using the report's id, a serial number assigned to the report when it was saved to the Enterprise repository. 1.


2.

Create a new iView for a Crystal Report object displaying data from the SAP BW system. Use the following details: Field Name

Value

iView Name

Crystal Reports iView XX

iView ID

IVIEW_01_XX (XX is replaced with your user number)

iView ID Prefix

com.sap

System Alias

TRAINING_SYSTEM_XX (Do not replace the XX)

Hint: The IVIEW template used to hold the settings for the iview is installed as a Portal archive (par) file on the BOBJ server where the Integration Kit is installed. The PAR file must be uploaded by the portal administrator to be available to be used to build IVIEWs. The path for this as shown in the presentation slides was System Administration > Support>Portal Runtime>Administration Console.

2009


657


BO100

BO100

Solution 27: Creating iViews for BusinessObjects content Task: You will create an IVIEW to directly present a Crystal report to users using SAP Enterprise portal. The IVIEW will point to an existing crystal report using the report's id, a serial number assigned to the report when it was saved to the Enterprise repository. 1.


You should already be logged in, but if not, to easily access portal, locate the link that begins with “http://portal-XXX” It is located in the user menu of client 900 in your assigned system. Click this link and change the XXX to your assigned system id. Log on the portal using your BO100-XX user and password. Do not change the client in the link leave it 800.

2.

Create a new iView for a Crystal Report object displaying data from the SAP BW system. Use the following details: Field Name

Value

iView Name

Crystal Reports iView XX

iView ID

IVIEW_01_XX (XX is replaced with your user number)

iView ID Prefix

com.sap

System Alias

TRAINING_SYSTEM_XX (Do not replace the XX)

Hint: The IVIEW template used to hold the settings for the iview is installed as a Portal archive (par) file on the BOBJ server where the Integration Kit is installed. The PAR file must be uploaded by the portal administrator to be available to be used to build IVIEWs. The path for this as shown in the presentation slides was System Administration > Support>Portal Runtime>Administration Console. a)

Navigate to Content Administration > Portal Content. Continued on next page

658


2009




b)


c)

Navigate to the previously created folder BO100-XX.

d)

Use the Context Menu (Right-click the folder).

e)


f)


g)

Click Next.

h)

Select BusinessObjects Enterprise Integration Kit – for the iView template option.

i)

Click Next.

j)

Enter IView Name: Crystal reports IView XX

k)

Enter iView ID: IVIEW_01_XX (replace XX with your ID)

l)

Enter iView ID Prefix:com.sap

m)

Click Next.

n)

Select the option Standard BusinessObjects Enterprise Report.

o)

Click Next.

p)

Enter the SAP system alias all students are sharing TRAINING_SYSTEM_XX. It was created by the instructor. (DO NOT REPLACE THE XX)

q)

Enter the report number for your Crystal report GR##_Sales_OrderReport into the field BusinessObjects Enterprise Report ID field on the IVIEW. Note: The report ID can be found by accessing the document in the Enterprise InfoView and selecting the object properties. It is a 4 digit number. Note: If time is short, ask the Instructor for the ID of the report he used.

r)

Enter the following into the Application Parameters (include all the text below except replace XXXX): cms_name=TWDFXXXX:6400 This is the name of the Central Management Server and its port.

s)

Leave the default for the BusinessObjects Enterprise Viewer and the viewing type. Continued on next page

2009


659


BO100

660

BO100

t)

Click Next.

u)

Select the option Open for editing when wizard completes.

v)

Click Finish.

w)

Select Property Category = Appearance / Size and change the property Height Type to “FULL PAGE.”

x)

Click Save

y)

Click Preview. To review the linked crystal report.

z)

Click Close but remain in the portal for subsequent exercises.


2009




Lesson Summary You should now be able to: • Create new iViews for BusinessObjects Enterprise content

2009


661


BO100

BO100

Lesson: Creating portal pages Lesson Overview In this lesson, you will learn about SAP portal pages. You will learn how to create new portal Pages and how to define the content displayed on these portal Pages.


Create a portal page Define the content and layout of portal pages


Portal Pages A portal Page can organize and display the content that is presented to the end user. The content can be organized according to topics, Roles, and various other categories. A portal Page can contain iViews and other Pages containing iViews.

662


2009



Lesson: Creating portal pages

To create a new portal Page 1.


2.

Navigate to the Content Administration tab.

3.

Navigate to the required folder in the Portal Content directory.

4.

Right-click on the folder.

Figure 255: Right-click

5.

Select New > Page.


2009


663


BO100

BO100

Figure 256: New>Page

6.

Complete the following fields: • •

•

• • 7.

Page Name The Page name is a display name that appears in the portal content catalog. Page ID Enter a unique identifier up to 100 characters for the page. The Page ID may include alphanumeric characters, underscores (_), dashes (-), percent signs (%), tildes (~) and parentheses. Other special characters and spaces are not permitted. Page ID Prefix Enter a prefix for the Page name. This option is useful if you want all your portal Pages to follow a specific naming convention, thus making them easier to locate since they contain a uniform prefix. Master Language Choose the master language for metadata defined in the new portal Page. Description Enter a brief description of the portal Page.

Click Next.


664


2009




Figure 257: Next

Note: The Default Page Template creates a Page based on the regular portal Page template. The Web Dynpro Proxy Page creates a Page based on Web Dynpro technology. 8.

Select Default Page Template.

9.

Click Next.

Figure 258: Next


2009


665


BO100

BO100

10. Select the page layout and add it to the Selected Layouts list. 11. Click Next. 12. Click Finish.

Figure 259: Finish

13. Ensure the option Open the object for editing is selected. 14. Click OK. 15. Right-click the iView.


666


2009




Figure 260: iView

16. Select Add iView to Page > Delta Link.

Figure 261: Add iView to Page>Delta Link

17. Click Page Layout for the portal Page. Continued on next page

2009


667


BO100

BO100

Figure 262: Page Layout

18. Click the iView placeholder appearing in the layout. 19. Select Appearance – size in the Property Category of the Property Editor.

Figure 263: Appearance-Size

20. Set the Height Type option to FULL_PAGE. Continued on next page

668


2009




21. Click Save. 22. Click Page Content for the portal Page.

Figure 264: Page Content

23. Select the iView and click Properties. Note: The Property Editor now displayes the properties of the selected iView. 24. Select Appearance – size in the Property Category of the Property Editor. 25. Set the Height Type option to FULL_PAGE. 26. Click Save. 27. Click Preview.

2009


669


BO100


670


2009


BO100


Exercise 28: Creating a portal Page and adding an iView to the Page Exercise Objectives After completing this exercise, you will be able to: • Create a new portal Page • Add a portal iView to the portal Page

Business Example You are a portal content administrator and need to create a new portal Page containing a portal iView that will display the content to your end users.

Task: Create a portal page and adding an iView to the page. 1.


2.


3.

Create a new portal Page with the following details:

4.

2009

Field

Value

Portal Page Name:

TrainXX_PAGE

Page ID:

TrainXX_PAGE

Page ID Prefix

com.sap

Add the previously created iView to the portal Page. You will also set both the IView with in the page and the page itself to the size “FULL PAGE.”


671


BO100

BO100

Solution 28: Creating a portal Page and adding an iView to the Page Task: Create a portal page and adding an iView to the page. 1.

Log onto the SAP Enterprise Portal. a)

You should already be in the portal system, but if not, access portal, locate the link that begins with “http://portal-XXX” It is located in the user menu of client 900 in your assigned system. Click this link and change the XXX to your assigned system id. Log on the portal using your BO100-XX user and password. Do not change the client in the link leave it 800.

2.

Navigate to Content Administration > Portal Content. a)

3.



672


2009




Field

Value

Portal Page Name:

TrainXX_PAGE

Page ID:

TrainXX_PAGE

Page ID Prefix

com.sap

a)

Navigate to your BO100-XX folder in the Portal Content directory.

b)


c)

Select New > Page.

d)

Complete the following fields: Page Name:TRAINXX_PAGE Page ID: TRAINXX_PAGE Prefix: com.sap Page Description: Enter what ever text you would like

e)

Click Next.

f)


g)

Click Next.

h)

Select the page layout 1 Column Full Width and add it to the Selected Layouts list.

i)

Click Next.

j)

Click Finish.

k)

Ensure the option Open the object for editing is selected.

l)

Click OK.


2009


673


BO100

4.

BO100

Add the previously created iView to the portal Page. You will also set both the IView with in the page and the page itself to the size “FULL PAGE.” a)

Right-click the iView Crystal Reports IViewXX .

b)

Select Add iView to Page > Delta Link.

c)

Ensure the Page Content radio button is selected and then select the check box for the only iView in your page.

d)

Click the Properties button and then on the right side of the screen select Appearance- Size in the Property Category of the Property Editor. Change the Height Type property to FULL PAGE

e)

Click Save

f)

Now change or verify that the Page Itself is set to SIZE = FULL PAGE. Select the hyperlink Show 'TrainXX_PAGE' Properties. Again in the Property Category of the Property Editor (this time for the whole page), find the Appearance-Size category and set or verify that the Height Type property is FULLPAGE.

g)

674

Click Preview then close your page and remain in the portal for your next exercise.


2009




Lesson Summary You should now be able to: • Create a portal page • Define the content and layout of portal pages

Related Information •

2009

[Enter an optional reference using the URL or CrossReference tag to additional information that learner may find useful. Examples include websites or whitepapers. Delete if not used.]


675


BO100

BO100

Lesson: Creating portal worksets Lesson Overview In this lesson, you will learn about SAP portal Worksets. You will learn how to create new portal Workset and how to assign portal Pages and portal iViews to Workset.


Create portal Worksets Assign content to portal Worksets


Portal Worksets Worksets allow the content administrator to combine iViews and Pages. Worksets are reusable structures that are added to a portal Role. A Workset cannot be assigned to users directly.

676


2009



Lesson: Creating portal worksets

To create a new portal workset 1.


2.


3.


4.


5.

Select New > Workset.

6.

Complete the following fields: •

•

•

• •

Workset Name The Workset name is a display name that appears in the Portal Content Catalog. Workset ID Enter a unique identifier for the Workset here. The Page ID may include alphanumeric characters, underscores (_), dashes (-), percent signs (%), tilde (~) and parentheses. Other special characters or spaces are not permitted. Workset ID Prefix Enter a prefix for the Workset name. This option is useful if you want all your portal content objects to follow a specific naming convention, thus making them easier to locate since they contain a uniform prefix. Master Language Choose the master language for metadata defined in the new Workset. Description Enter a brief description of the Workset.

7.

Click Next.

8.

Click Finish.

9.


10. Click OK. Note: At this point the Workset does not contain any portal content. 11. Click New Folder. 12. Enter the Folder Name and Folder ID. 13. Click Create New Folder. Continued on next page

2009


677


BO100

BO100

14. Right-click the Page to be added to the Workset. 15. Select Add Page to Workset > Delta Link. 16. Click the folder in the Workset. 17. Right-click the portal Page. 18. Select Add Page to Workset > Delta Link. Note: The step is repeated here to show the different appearance in the Enterprise Portal. 19. Click Close. Note: You have created a Workset that includes the portal Page and, therefore, the portal iView. A Workset on its own does not have a preview mode.

678


2009




Exercise 29: Creating a portal Workset Exercise Objectives After completing this exercise, you will be able to: • Create a new portal Workset • Add a portal Page to the Workset

Business Example You are a portal content administrator and need to create a new portal Workset containing a portal Page that will display the content to your end users.

Task: In this task you will create a portal work set which is basically a collection of portal pages. Within the work set you create a folder for even more organization of pages. 1.


2.


3.

Create a new portal Workset: Field

Value

Workset Name:

TrainXX_WORKSET

Workset ID:

TrainXX_WKS

Workset ID Prefix

com.sap

Description

Collection of Portal Pages for BO100

Note: Replace XX with your user number. 4.

2009

Add the previously created portal Page to the folder you just created in the workset.


679


BO100

BO100

Solution 29: Creating a portal Workset Task: In this task you will create a portal work set which is basically a collection of portal pages. Within the work set you create a folder for even more organization of pages. 1.



2.


3.

Create a new portal Workset:


680


2009




Field

Value

Workset Name:

TrainXX_WORKSET

Workset ID:

TrainXX_WKS

Workset ID Prefix

com.sap

Description

Collection of Portal Pages for BO100

Note: Replace XX with your user number. a)


b)


c)

Select New > Workset.

d)

Complete the following fields: • Workset Name: TrainXX WORKSET • Workset ID:TrainXX_WKS • Workset ID Prefix:com.sap • Description : “Collection of Portal Pages for BO100.”

e)

Click Next.

f)

Click Finish.

g)


h)

Click OK.

i)

Inside the workset object, click New Folder. Note: A workset folder is yet another grouping level for portal pages with in a work set and ultimately within a portal role.

4.

2009

j)

Enter TrainXX_WSF as both the Folder Name and Folder ID.

k)

Click Create New Folder.

Add the previously created portal Page to the folder you just created in the workset. a)

Click the page you just created and then right-click the page to add it to the Workset. Choose Add Page to Workset > Delta Link.

b)

Click Close. Stay in the portal system.


681


BO100

BO100

Lesson Summary You should now be able to: • Create portal Worksets • Assign content to portal Worksets

682


2009



Lesson: Creating portal roles

Lesson: Creating portal roles Lesson Overview In this lesson, you will learn about SAP portal Roles. You will learn how to create new portal Roles and how to assign portal Worksets to portal Roles.


Create portal roles Assign portal worksets to portal roles Assign a portal role to a portal user


Portal Roles A portal Role can organize and display the content that is being displayed to the end user.

2009


683


BO100

BO100

To create a new portal Role 1.


2.


3.

Navigate to Portal Content tab.

4.


Figure 265: folder

5.

Select New > Role.


684


2009




Figure 266: New>Role

6.

Complete the following fields: • •

•

• •

Role Name The Role name is a display name that appears in the Portal Content Catalog. Role ID Enter a unique identifier for the Role here. The Role ID may include alphanumeric characters, underscores (_), dashes (-), percent signs (%), tilde (~) and parentheses. Other special characters or spaces are not permitted. Role ID Prefix Enter a prefix for the Role ID. This option is useful if you want all your portal content objects to follow a specific naming convention, thus making them easier to locate since they contain a uniform prefix. Master Language Choose the master language for metadata defined in the new Role. Description Enter a brief description of the Workset.

7.

Click Next.

8.

Click Finish.


2009


685


BO100

BO100

Figure 267: Finish

9.


10. Click OK. 11. Right-click the Workset.


686


2009




Figure 268: Workset

12. Select Add Workset to Role > Delta Link. 13. Select the Portal Role. 14. Right-click Properties. 15. Select Navigation in the Property Category list box of the Property Editor.


2009


687


BO100

BO100

Figure 269: Navigation

16. Set the Entry Point property to Yes. 17. Click Save. 18. Click Close. Note: You have now created a Role which contains the portal content. As a next step, you need to assign the Role to the relevant port users.

Assign a portal Role to a portal User Portal User Administration By assigning a user to a portal Role, the user is granted access to the content and rights assigned to the Role.

688


2009




To assign the portal Role to a portal User 1.


2.

Navigate to User Administration tab.

Figure 270: User Administration

3.

Search for the portal user.


2009


689


BO100

BO100

Figure 271: portal user

4.

Click the Logon ID.

Figure 272: Logon ID

5.

Click the Assigned Roles tab. Continued on next page

690


2009




6.

Click Modify.

7.

Search for the portal Role in the left screen.

Figure 273: Search for portal Role

8.

Select the available Role by clicking the table grid (left-hand side).

9.

Click Add.

10. Click Save. 11. Refresh the browser Page. Note: Based on the configuration steps and the setting that the portal Role is an entry point, the created portal Role should now appear in the top-level navigation.

2009


691


BO100


692


2009


BO100


Exercise 30: Creating a portal Role Exercise Objectives After completing this exercise, you will be able to: • Create a new portal Role • Add a Page to the portal Role

Business Example You are a portal content administrator and need to create a new portal Role containing a portal Workset that will display the content to your end users.

Task: In this task you will create a portal roll which consist of a collection of Worksets which in turn contain pages and ultimately Iviews with content. 1.


2.


3.

Create a new portal Role with the following details: Field

Value

Role Name:

TrainXX_ROLE

Rolet ID:

TrainXX_ROLE

Role ID Prefix

com.sap

Note: Replace XX with your user number.

2009

4.

Add the previously created Workset to the portal Role.

5.

Set the portal Role to become an entry point.


693


BO100

BO100

Solution 30: Creating a portal Role Task: In this task you will create a portal roll which consist of a collection of Worksets which in turn contain pages and ultimately Iviews with content. 1.



2.


3.

Create a new portal Role with the following details:


694


2009




Field

Value

Role Name:

TrainXX_ROLE

Rolet ID:

TrainXX_ROLE

Role ID Prefix

com.sap

Note: Replace XX with your user number.

4.

5.

a)

Navigate to Portal Content tab.

b)


c)

Select New > Role.

d)

Complete the following fields: • Role Name • Role ID • Role ID Prefix • Master Language • Description

e)

Click Next.

f)

Click Finish.

g)


h)

Click OK.

Add the previously created Workset to the portal Role. a)

Right-click the Workset.

b)

Select Add Workset to Role > Delta Link.

c)

Select the Portal Role (the highest level in the hierarchy) by clicking on it.

Set the portal Role to become an entry point. a)

Right-click Properties.

b)

Select Navigation in the Property Category list box of the Property Editor.

c)

Set the Entry Point property to Yes.

d)

Click Save.

e)

Click Close. Say in the portal system for the next exercise.

2009


695


BO100


696


2009


BO100


Exercise 31: Assigning the portal user to the portal Role Exercise Objectives After completing this exercise, you will be able to: • Assign a portal User to a portal Role

Business Example You are a portal content administrator and need to assign a portal Role to a portal User. Hint: There are many objects in the SAP world with the term role. In most cases they mean basically the same thing- a collection of transactions, reports or links to perform a specific job with in a company. But be clear when discussing roles what role object you are talking about. In our case a role assigned to a user in Enterprise Portal.

Task: In the exercise you will assign your role to your user id and then test it to see if the crystal report can be accessed form the portal.

2009

1.


2.

Assign the your Portal User BO100-XX to the previously created portal Role TRAINXX_ROLE.

3.

Refresh your browser window to view the Role and the iView.


697


BO100

BO100

Solution 31: Assigning the portal user to the portal Role Task: In the exercise you will assign your role to your user id and then test it to see if the crystal report can be accessed form the portal. 1.



2.

3.

Assign the your Portal User BO100-XX to the previously created portal Role TRAINXX_ROLE. a)

Navigate to User Administration tab.

b)

Search for the portal user BO100-XX.

c)

Click the Logon ID.

d)

Click the Assigned Roles tab.

e)

Click Modify.

f)

Search for the portal Role TrainXX_ROLE in the left screen. Use *trainXX* for quick search.

g)

Select the available role by clicking the table grid (left-hand side).

h)

Click Add.

i)

Click Save.

Refresh your browser window to view the Role and the iView. a)

698

Refresh the browser by pressing F5. Navigate to you the new tab TrainXX_Role at the top of the screen, since no workset or pages were set as the entry point, you must expand the folders on the left side to access your page and iView.


2009




Lesson Summary You should now be able to: • Create portal roles • Assign portal worksets to portal roles • Assign a portal role to a portal user

2009


699


BO100

BO100

Lesson: BusinessObjects Enterprise Repository Manager Lesson Overview In this lesson, you will learn how to configure the BusinessObjects Enterprise Repository Manager to integrate your system with the Knowledge Management part from the SAP Enterprise Portal.


Configure the Repository Manager for BusinessObjects Enterprise Use the Repository Manager for reporting Use collaboration features Create an iView for the Repository Manager

Business Example BusinessObjects XI Integration for SAP Solutions delivers integration with the Knowledge Management part of SAP Enterprise Portal where the administrator can create repository integration with the Knowledge Management and leverage functionality like subscriptions, discussion and feedback to enhance the information provided by the BusinessObjects Enterprise repository.

Configuring the BusinessObjects Repository Manager The Knowledge Management integration is delivered as a portal archive (PAR) file. The administrator needs to configure the BusinessObjects Enterprise specific values for each BusinessObjects Enterprise server after the portal archive has been uploaded.

700


2009



Lesson: BusinessObjects Enterprise Repository Manager

To install the Knowledge Management integration 1.

Log onto the SAP Enterprise Portal system.

2.

Navigate to System Administration > Support.

Figure 274: System Administration>Support

3.

Click Portal Runtime.

Figure 275: Portal Runtime


2009


701


BO100

4.

BO100

Select Administration Console.

Figure 276: Administration Console

5.

Click Browse from the Archive Uploader.

6.

Select the Repository Manager archive file. Note: By default the file is located in the directory \Program Files\Business Objects\BusinessObjects Enterprise 12.0\java\applications. The filename is BusinessObjectsKM.par

7.

Click Upload. After a successful deployment of the portal archive file you will find an instance of the BusinessObjects Enterprise repository manager.

702


2009




To verify the installation 1.


2.


Figure 277: System Administration>System Configuration

3.

Open the folder Knowledge Management.


2009


703


BO100

BO100

Figure 278: Knowledge Management

4.

Click Content Management.


704


2009




Figure 279: Content Management

5.

Click Repository Managers.

6.

Select the BusinessObjects Repository Manager (com.businessobjects.kmc.manager.).

7.

Select the entry and view the definition.


2009


705


BO100

BO100

Figure 280: View the Definition

Note: The Enterprise Portal system is now configured to create new BusinessObjects Enterprise based repositories.

706


2009




To create a new repository manager integration with your BusinessObjects Enterprise system 1.


2.


3.


4.


Figure 281: Content Management

5.


6.

Click Business Objects Repository.

7.

Click New.


2009


707


BO100

BO100

Figure 282: New

8.

Enter a name and description for the repository. Note: Enter the name of your BOE repository as you want it to be displayed in the BusinessObjects Repository list. Name and Description can be configured without restrictions.

9.

Enter a Prefix for the repository. Note: This needs to start with a "/" sign and is the name that will be used to show the repository in the Knowledge Management content,


708


2009




10. Select the required Repository Services. Note: Select from the following: • • • • • • • •

Comment Discussions Feedback Layout Personal note Properties Rating Subscription

11. Enter the name of your CMS with port into CMS Host and Port. Note: For example: :8080 12. Replace the placeholder %WEB_SERVER_AND_PORT% for the field Dispatch URL with values from your BusinessObjects Enterprise system. Note: For example: http://:8080/SAP/jsp/Action_Dispatch/dispatch.jsp 13. Replace the placeholder %WEB_SERVER_AND_PORT% for the field OpenDoc URL with values from your BusinessObjects Enterprise system. Note: For example: http://:8080/OpenDocument/opendoc/openDocument.jsp 14. Replace the placeholder %SAP_CLIENT% for the field SAP Client with the value of the SAP system that will be used in combination with your BusinessObjects Enterprise system. 15. Replace the placeholder %SAP_SYSID% for the field SAP System ID with the value of the SAP system that will be used in combination with your BusinessObjects Enterprise system. 16. Replace the placeholder %WEB_SERVER_AND_PORT% for the field URL to Logoff BOE with values from your BusinessObjects Enterprise system. Note: For example: http://:8080/PartnerPlatformService/service/app/logoff.do Continued on next page

2009


709


BO100

BO100

17. Replace the placeholder %WEB_SERVER_AND_PORT% for the field Web Service URL with values from your BusinessObjects Enterprise system. Note: For example: http://:8080/dswsbobje/services/ 18. Click OK. Note: The newly created repository manager should appear in the list of available repository managers after this step. In order to make BusinessObjects-specific properties and commands available, the layout set of your configured BusinessObjects Enterprise repository needs to be changed into the BusinessObjects specific layout, which is named BOBJELayout. 19. Navigate to Content Administration > KM Content > KM Content.

Figure 283: KM Content

Note: The newly created repository should appear in the list. 20. Click on the context menu symbol of the repository. Continued on next page

710


2009




Figure 284: Content menu symbol

21. Select Details.

Figure 285: Details

22. Select the menu Settings > Presentation.


2009


711


BO100

BO100

Figure 286: Settings>Presentation

23. Click Select Profile.


712


2009




Figure 287: Select Profile

24. Select the option Layout Set. 25. Select BOBJELayout from the list box. 26. Click OK. 27. Select the option Apply settings to all subfolders. 28. Click Save. 29. Click Close.

Using the BusinessObjects Repository Manager After configuration of the Repository Manager you can use the newly created entry for viewing and creating reports, providing feedback and ranking of reports and several other collaboration features. After the successful configuration of the Repository Manager you can leverage the full functionality of BusinessObjects Enterprise inside the SAP Enterprise Portal.

2009


713


BO100

BO100

To use the Repository Manager 1.


2.

Navigate to Content Administration > KM Content > KM Content.


Note: The newly created repository should appear in the list. 3.

Click on the repository.


714


2009




Figure 289: Repository

Menu View The menu item View allows you to switch between a view by Folders or by Category.

Figure 290: Menu item view

Menu Folder The menu Folder > New allows you to create new documents in the same way you can create new content in InfoView.


2009


715


BO100

BO100

Figure 291: Menu folder

The other options in the menu Folder are to view the detailed properties of the selected object and to fresh the folder structure manually. Menu Selection The menu Selection allows you to copy, move, and delete objects inside the repository.

Figure 292: Menu selection

Menu Go To Continued on next page

716


2009




With the menu Go To you can navigate to InfoView and the recently used objects.

Figure 293: Menu Go To

Menu BusinessObjects The menu item BusinessObjects allows you to navigate to InfoView.

Figure 294: Menu BusinessObjects

Context menus Each object part of the repository offers a context menu that, depending on the object type, allows you to use certain functions. In the image below, the context menu of a Crystal Report object is shown. Continued on next page

2009


717


BO100

BO100

Figure 295: Context menu

Using collaboration features The Repository Manager as part of Knowledge Management also allows the user to use some collaboration features.

718


2009




To use the collaboration features 1.


2.

Navigate to Content Administration > KM Content > KM Content.


Note: The newly created repository should appear in the list. 3.

Click on the repository.


2009


719


BO100

BO100

Figure 297: Repository

4.

Navigate to a report object following your folder structure.

Figure 298: Report object

5.

Open the context menu of the object.


720


2009




Figure 299: Context menu

6.

Select Details.

Figure 300: Details

7.

Select Collaboration > Give Feedback to provide feedback for the report.

8.

Select Collaboration > Rate this document to provide a ranking for the report.

9.

Select Collaboration > Write a review to create a review for the report.

10. Click Close.


2009


721


BO100

BO100

Figure 301: Close

Note: The changes made will appear as part of the display.

Creating an iView for the Repository Manager SAP Enterprise Portal delivers several iView templates for the Knowledge Management area. For this purposes, use the standard Knowledge Management Navigation iView.

722


2009




To create a new iView 1.


2.


3.


4.

Navigate to the previously created folder.

5.


Figure 302: Folder

6.



2009


723


BO100

BO100

Figure 303: iView

7.


8.

Click Next.

9.

Select the KM Navigation iView.

10. Click Next.

Figure 304: Next

11. Enter the following details: iView Name Continued on next page

724


2009




This is a display name that appears in the Portal Catalog, Dialog Box and Window that displays a list of iViews. The iView name may contain up to 40 characters of any type, including spaces, but not apostrophes and quotation marks. iView ID This is the unique identifier registered in the Portal Content Directory. This ID appears within the portal administrator environment. The iView ID may contain 40 characters and include alphanumeric characters, underscores (_), dashes (-), dots (.) exclamation point (!), tilde (~) and parentheses. Other special characters and spaces are not permitted. iView ID Prefix If you want all your iViews to follow a specific naming convention, making them easier to locate, you can add a uniform prefix to each system you create. 12. Click Next. 13. Click Finish. 14. Select the option Open the object for editing. 15. Click OK. 16. Select the Property Category Show All. 17. Set the property Path to Initially Displayed Folder and Path to Root Folder for Navigation to the prefix of your Repository Manager. 18. Click Save. 19. Click Preview. 20. Click Close.

2009


725


BO100


726


2009


BO100


Exercise 32: Create a new BusinessObjects Repository Manager Exercise Objectives After completing this exercise, you will be able to: • Create a new BusinessObjects Repository Manager

Business Example You are a portal content administrator and need to create a new Repository Manager for your BusinessObjects Enterprise system. This is the first step in allowing access to the folder hierarchy of Business Objects Infoview, within the portal environment. Hint: The repository manager allows portal to link to and use external file management software via the common portal interface. Examples in addition to BOBJ Infoview include SharePoint and Lotus Domino as well as others.

Task: In this task you will create your own repository manager which is basically an object to provide the technical settings needed to expose a document management software inside of portal. Note: Prior to the this step the it is required that the Business Objects Repository manager integration for knowledge management be installed. On our system this was accomplished already by up loading a portal archive (PAR) file called BusinessObjectsKM.PAR. This file was stored on the BOBJ Enterprise server during the installation of the Integartion Kit. It was previously uploaded via the path Systems Administration>Support>Portal Runtime>Administration Console >Browse. 1.


2.

Navigate to System Administration > System Configuration > Knowledge Management.

3.

Create a new Repository Manager for your BusinessObjects Enterprise system. Use the following details: -Name and Description: TRAINXX (replace XX with your user number). Continued on next page

2009


727


BO100

BO100

- Prefix: /TRAINXX (replace XX with your user number) Note:Please be careful with the prefix. it must be preceded by a “/ Also note that on our small training box, parts of this exercise take a few minutes to execute.”

728

4.

Replace the required parameters with values for your BusinessObjects Enterprise system.

5.

Configure the Layout of the new repository to the AdminExplorerBOE layout.


2009




Solution 32: Create a new BusinessObjects Repository Manager Task: In this task you will create your own repository manager which is basically an object to provide the technical settings needed to expose a document management software inside of portal. Note: Prior to the this step the it is required that the Business Objects Repository manager integration for knowledge management be installed. On our system this was accomplished already by up loading a portal archive (PAR) file called BusinessObjectsKM.PAR. This file was stored on the BOBJ Enterprise server during the installation of the Integartion Kit. It was previously uploaded via the path Systems Administration>Support>Portal Runtime>Administration Console >Browse. 1.



2.

3.

Navigate to System Administration > System Configuration > Knowledge Management. a)


b)


Create a new Repository Manager for your BusinessObjects Enterprise system. Use the following details: -Name and Description: TRAINXX (replace XX with your user number). - Prefix: /TRAINXX (replace XX with your user number)


2009


729


BO100

BO100

Note:Please be careful with the prefix. it must be preceded by a “/ Also note that on our small training box, parts of this exercise take a few minutes to execute.” a)


b)


c)

Click Business Objects Repository.

d)

Click New.

e)

Enter a name and description for the repository. Use TRAINXX for both.

f)

Enter a Prefix for the repository. Use /TRAINXX.

g)

Select the following Repository Services. In addition to the defaulted services, ensure that the following services are selected Comment Rating Layout Discussion Simple Feedback Personal note

h)

Enter the name of your CMS with port (TWDFXXXX:6400) into CMS Host and Port object property.


730


2009




4.

5.

2009

Replace the required parameters with values for your BusinessObjects Enterprise system. a)

Replace the placeholder %WEB_SERVER_AND_PORT% for the field Dispatch URL with values TWDFXXXX:8080.

b)

Replace the placeholder %WEB_SERVER_AND_PORT% for the field OpenDoc URL with TWDFXXXX:8080

c)

Replace the placeholder %SAP_CLIENT% for the field SAP Client with 900.

d)

Replace the placeholder %SAP_SYSID% for the field SAP System ID with your assigned SAP system that will be used in combination with your BusinessObjects Enterprise system.

e)

Replace the placeholder %WEB_SERVER_AND_PORT% for the field URL to Logoff BOE with TWDFXXXX:8080

f)

Replace the placeholder %WEB_SERVER_AND_PORT% for the field Web Service URL with TWDFXXXX:8080.

g)

Click OK.

Configure the Layout of the new repository to the AdminExplorerBOE layout. a)

Navigate to Content Administration > KM Content.

b)

Select the KM Content in the Detailed Navigation area. You should be able to see your repository in the list in the middle of the screen.

c)

Click on the context menu symbol of the repository.

d)

Select Details.

e)

Select the menu Settings > Presentation.

f)

Click Select Profile.

g)

Select the option Layout Set.

h)

Select BOEJELayout from the list box.

i)

Click OK.

j)

Select the option Apply Settings to all Subfolders.

k)

Click Save.

l)

Click Close.


731


BO100


732


2009


BO100


Exercise 33: Creating a Knowledge Management iView Exercise Objectives After completing this exercise, you will be able to: • Create an iView for the BusinessObjects Repository Manager

Business Example You are a portal administrator and need to create a new iView to show the content from the BusinessObjects Repository Manager.

Task: In this task you will create and preview a Repository Manager Iview. Optionally you can attempt to add this Iview to a new portal page and include it in your existing portal work set. 1.


2.

Create a new iView using the Knowledge Management Navigation iView template. Use the following details: Field

Value

iView Name:

Repository Manager IViewXX.

iView ID:

IVIEW_RM_XX (XX is replaced with your user number). com.sap

iView ID Prefix: 3.

Create a new portal Page with the following details: Field

Value

Portal Page Name

TrainXX_Page2

Page ID:

TrainXX_Page2

Page ID Prefix:

com.sap


2009


733


BO100

4.

734

BO100

Add the previously created repository manager iView to the portal Page. You will also set the IView within the page “to FULL PAGE.”


2009




Solution 33: Creating a Knowledge Management iView Task: In this task you will create and preview a Repository Manager Iview. Optionally you can attempt to add this Iview to a new portal page and include it in your existing portal work set. 1.



2.

Create a new iView using the Knowledge Management Navigation iView template. Use the following details:


2009


735


BO100

BO100

Field

Value

iView Name:

Repository Manager IViewXX.

iView ID:

IVIEW_RM_XX (XX is replaced with your user number). com.sap

iView ID Prefix: a)


b)


c)

Navigate to your BO100-XX folder.

d)


e)


f)


g)

Click Next.

h)

Select the KM Navigation IView template.

i)

Click Next.

j)

Enter the following details: iView Name: Repository Manager IViewXX iView ID: IVIEW_RM_XX (XX is replaced with your user number) iView Prefix: com.sap

3.

k)

Click Next.

l)

Click Finish.



736


2009




Field

Value

Portal Page Name

TrainXX_Page2

Page ID:

TrainXX_Page2

Page ID Prefix:

com.sap

a)

Navigate to your BO100-XX folder in the Portal Content directory.

b)


c)

Select New > Page.

d)

Complete the following fields: Page Name:TrainXX_PAGE2 Page ID: TrainXX_PAGE2 Prefix: com.sap Page Description: Enter what ever text you would like

e)

Click Next.

f)


g)

Click Next.

h)

Select the page layout 1 Column (Full Width) and add it to the Selected Layouts list.

i)

Click Next.

j)

Click Finish.

k)


l)

Click OK.


2009


737


BO100

4.

BO100

Add the previously created repository manager iView to the portal Page. You will also set the IView within the page “to FULL PAGE.” a)

Right-click the Repository Manager IVIEWXX .

b)

Select Add iView to Page > Delta Link.

c)

Ensure the Page Content radio button is selected and then select the check box for the iView in your page.

d)

Click the Properties Button (bottom left) to change the properties of the iView. On the right side of the screen select Appearance - Size in the Property Category of the Property Editor. Change the Height Type property to FULL PAGE

e)

Change the Property Category to Show ALL and change both the Path to Initially Displayed Folder and the Path to Root Folder for Navigation to /TRAINXX

f)

Click Save.

g)

Click Preview then close your page. Note: The page might take a minute to open as the object has never been used before, and it must access all the document folders on InfoView.

h)

738

*Optional * Add the page to your existing WorkSet, using instructions from prior exercise if necessary.


2009




Lesson Summary You should now be able to: • Configure the Repository Manager for BusinessObjects Enterprise • Use the Repository Manager for reporting • Use collaboration features • Create an iView for the Repository Manager

2009


739


BO100

BO100

Unit Summary You should now be able to: • Import the BusinessObjects Enterprise iView template to the Enterprise Portal • Create a new system for the BusinessObjects Enterprise system • Create new iViews for BusinessObjects Enterprise content • Create a portal page • Define the content and layout of portal pages • Create portal Worksets • Assign content to portal Worksets • Create portal roles • Assign portal worksets to portal roles • Assign a portal role to a portal user • Configure the Repository Manager for BusinessObjects Enterprise • Use the Repository Manager for reporting • Use collaboration features • Create an iView for the Repository Manager

740


2009


Unit Summary

Test Your Knowledge


How many Crystal Reports can be displayed in a BusinessObjects iView template? Choose the correct answer(s).

□ □ □ □ 2.

A B C D

1 2 1 or more None

An iView can be added to a Page and Workset? Determine whether this statement is true or false.

□ □ 3.

True False

An iView can be added to a Page and Workset? Determine whether this statement is true or false.

□ □

2009

True False


741


BO100

BO100

Answers 1.

How many Crystal Reports can be displayed in a BusinessObjects iView template? Answer: A Correct answer is 1.

2.

An iView can be added to a Page and Workset? Answer: True True, an iView can be added to a Page and Workse.

3.

An iView can be added to a Page and Workset? Answer: False An iView cannot be added to a Page and Workset?

742


2009


Test Your Knowledge



Unit Summary

743


2009


BO100

Unit Summary

744


2009


BO100

Troubleshooting the SAP Connectivity Unit Overview [Enter a brief overview of the unit.]hugo


Describe the steps to validate the configuration Describe the steps to validate the data connectivity Describe the steps to validate metadata Describe the steps to validate the results. Describe the best practices which may be taken to maximize the performance from your system.

Unit Contents Lesson: Troubleshooting Connectivity ........................................... 746 Procedure: To activate the connectivity trace for Web Intelligence ...... 749 Procedure: To activate the connectivity trace for Crystal Reports ....... 751 Lesson: Performance .............................................................. 756

2009


745


Unit 15

BO100

Lesson: Troubleshooting Connectivity Lesson Overview This lesson provides you information and steps you can use to troubleshoot issues you might face and some tips to improve the performance of running SAP BusinessObjects client tools with SAP NetWeaver Business Warehouse (BW).


Describe the steps to validate the configuration Describe the steps to validate the data connectivity Describe the steps to validate metadata Describe the steps to validate the results.

Business Example You need to verify the connectivity you are using in the SAP BusinessObjects client tools and which tools are available to you for troubleshooting.

Validating the Configuration The following is a list of steps you can take to verify your configuration: 1. 2.

3. 4.

Verify all required ABAP transports have been imported correctly to your SAP system. Use Transaction STMS to verify the transports. Verify the user has authorization to perform the required task. Use Transaction ST01 to create an authorization trace that wil show you any missing authorization. Use Transcations SQ01, SQ02, and SQ03 to verify that the InfoSet is assigned to the global or local environment and the InfoSet is assigned to a user group. Verify the underlying BW query has been marked for external access in the SAP Business Explorer (BEx) Query Designer by setting the property Allow external access.

Tracing For tracing the data connectivity you can use the registry (on a Windows environment). For SAP BusinessObjects Web Intelligence you need to set the registry keys and values according to the following table:

746


2009


Unit 15: Troubleshooting the SAP Connectivity

Lesson: Troubleshooting Connectivity

Registry Branch

Registry Key

Value

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\MDA\Log\Modules\SAPMODULE

Verbosity

A decimal value from 0 (no tracing) to 10 (most details)

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\MDA\Log\Modules\SAPMODULE

MDX Query Log

Path to the MDX logfile

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\MDA\Log

LogFile

Path to the general logfile Example: C:\SAP_SOFA.log These settings will generate two logfiles: •

•

2009


A MDA logfile that includes all steps that have been performed on the SAP server side. A MDX logfile that includes all executed MDX statements.

747


BO100

BO100

Figure 305: Registry Editor

Note: Some of these registry branches, keys, and values are not part of the installation routine, so you have to create them manually. The resulting traces provide you with a high level of detail. These trace also contain information about the metadata that has been retrieved, the statement that was used for data retrieval, and in some cases the actual data that has been retrieved. Note: After setting the registry value the corresponding services from BusinessObjects Enterprise need to be restarted (Web Intelligence services, Connection Server, Multi Dimensional Analysis Server). Hint: • •

•

748

Use Transaction ST01 to create several kinds of traces. Most importantly, you can use Transaction ST01 to create authorization traces. Use Transaction ST05 to create remote funcation call (RFC) and Structured Query Language (SQL) traces, which are especially helpful for the connectivity with the SAP ERP system. Use Transaction RSTT and RSRTRACE to generate an OLAP trace, which can be repeated by any time.


2009




To activate the connectivity trace for Web Intelligence 1.

Click Start.

2.

Select Run.

3.

Click regedit.

4.

Click OK.

5.

Navigate to the following path : HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\MDA\Log\Modules\SAPMODULE.

6.

Set the value for the Verbosity to 10 decimal.

7.

Set the value MDX Query Log to “C:\Logfiles\mdx.log”.

8.

Start Web Intelligence.

9.

Create a new report based on an OLAP Universe.

Tracing and troubleshooting the Crystal Reports connectivity To be able to trace the SAP connectivity for Crystal Reports the necessary registry entries need to be configured. The entries can be found in the following part of the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP. Underneath this entry in the registry, each connectivity has its own folder. Each of the connectivity registry keys has a value called Trace which accepts a Yes or No as a value. In addition to the Trace value, the user needs to configure the trace directory. The location of the trace files can be configured by the registry key called TraceDir in the registry folder HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP, which points to the folder for the logfiles.

2009


749


BO100

BO100

Figure 306: Registry key SAP

Note: The registry entry TraceDir is not created during the installation and needs to be created manually.

750


2009




To activate the connectivity trace for Crystal Reports 1.

Click Start.

2.

Select Run.

3.

Click regedit.

4.

Click OK.

5.

Navigate to the following path : HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP.

6.

Set the value for the TraceDir.

7.

Set the value Trace to Yes for the driver.

8.

Start Crystal Reports Designer.

9.

Create a new report based on the connectivity that will be traced.

Validating Metadata You can validate the metadata that you retreived in the client tools such as Crystal Report ,SAP BusinessObjects Web Intelligence, and Universe Designer by using a set of SAP tools: • •

•

For the InfoSet connectivity you can use Transaction SQ02 to validate the metadata that you received with the actual InfoSet in your SAP system. For the Open SQL connectivity providing access to tables, views, and ABAP functions, you can use Transaction SE11 and Transaction SE37 to compare the metadata from your SAP system with the metadata in your SAP NetWeaver Business Warehouse system. For the BW connectivity you can use Transaction SE37 and call the BAPI functions manually to retrieve the metadata. You can then compare the result in Transaction SE37 with the meta in Crystal Reports or the Universe Designer.

The BAPI function listed below are the basis for the metadata retrieval in an SAP NetWeaver Business Warehouse scenario. You can use these functions in Transaction SE37 to retrieve the metadata directly from the SAP NetWeaver Business Warehouse system without any additional software.

2009


751


BO100

BO100

OLAP BAPI Function

Metadata Being Retrieved

BAPI_MDPROVIDER_GET_CATALOGS

List of cubes

BAPI_MDPROVIDER_GET_CUBES

List of queries

BAPI_MDPROVIDER_GET_DIMENSIONS

List of dimensions

BAPI_MDPROVIDER_GET_HIERARCHYS

List of hierarchies

BAPI_MDPROVIDER_GET_LEVELS

List of levels for hierarchies

BAPI_MDPROVIDER_GET_MEASURES

List of key figures

BAPI_MDPROVIDER_GET_PROPERTIES

List of display attributes

Note: More information can be found in the ADDITIONAL DEVELOPMENT TECHNIQUES area of the SAP NetWeaver Business Warehouse documentation (http://help.sap.com). This image below shows the process flow for creating an OLAP Universe on top of an SAP BW query or cube. The process flow also mentions the OLAP BAPI functions that are being used.

752


2009




Figure 307: Creating an OLAP Universe

Validating the Results If you need to validate the actual data being retrieved, there is a set of tools that you can use: •

•

•

•

2009

For the InfoSet connectivity for Crystal Reports you can easily create a query on top of your InfoSet using Transaction SQ01 and simulate the connectivity without any additional software being involved. For the connectivity with tables for Crystal Reports you can use the QuickViewer (Transaction SQVI) to create the linkage between the tables and see the actual result set. In addition, you can use Transaction ST05 to enable an RFC and SQL trace on your SAP system to see further details. If you are using connectivity with your SAP NetWeaver Business Warehouse system, you can use Transaction MDXTEST to validate the result set. The MDX that is being sent from the client tools or from your SAP BusinessObjects Enterprise system is part of the trace files. Other options to validate the data are to execute the underlying BW query with the SAP BEx toolset or to execute the query in Transaction RSFT.


753


BO100

BO100

Steps to validate the publishing integration of Crystal Reports The following is a list of items for you to check if you have troubles with the publishing integration of Crystal Reports with SAP NetWeaver Business Warehouse. •

• • • • •

Ensure that the role you are trying to use on the SAP NetWeaver Business Warehouse side has been imported to your SAP BusinessObjects Enterprise system and has been assigned in transaction /CRYSTAL/RPTADMIN as the role to your SAP BusinessObjects Enterprise server definition. Ensure that the role has valid description in all languages you want to use. This can be done in transaction PFCG. Ensure that your RFC destination in transaction SM59 is working properly. Ensure that the user publishing a report has all the necessary rights in the SAP BusinessObjects Enterprise system. Ensure that the imported users and the user type based on the SAP roles match your licensing type. You can use transcation SMGW to look for error messages from the SAP Gateway.

Tracing You can trace the activity of the publishing service by setting the key Trace in the registry branch HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\BW Publisher Service to the value Yes. The path for the trace files has been configured by the registry key TraceDir in the registry branch HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP. The SAP NetWeaver Business Warehouse Publisher itself can be traced by setting the key Trace in the branch HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\BWPublisher to Yes.

754


2009




Lesson Summary You should now be able to: • Describe the steps to validate the configuration • Describe the steps to validate the data connectivity • Describe the steps to validate metadata • Describe the steps to validate the results.

2009


755


BO100

BO100

Lesson: Performance Lesson Overview [Enter a brief overview of the lesson.]


Describe the best practices which may be taken to maximize the performance from your system.

Business Example You have multiple Infocubes, DSO, Infosets, and hundreds BEx querie. 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.

General considerations A primary focus in this lesson is to understand the steps which may be taken to maximize the performance of Web Intelligence reports running on top of BW. In this context, maximizing performance refers to a balance of minimizing: • • •

756

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.


2009



Lesson: Performance

BEx Queries as recommended data sources BEx Queries are recommended as data sources for generating universes for the following reasons: 1. 2.

3.

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 final number of BEx Queries and universes required to meet all the ad-hoc query and reporting needs.

2009


757


BO100

BO100

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 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 MultiCube that is in scope for ad-hoc query and reporting. Then build a universe on top of each of these BEx Queries. Do not build one query per InfoProvider because elements can add processing time even though you not using them into the Web Intelligence report. 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 defniition While the default universe generated for a BW query or cube 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 VS on-demand reporting One of the 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 minimize the

758


2009



Lesson: Performance

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 2 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 designed 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 flattening 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.

2009


759


BO100

BO100

Lesson Summary You should now be able to: • Describe the best practices which may be taken to maximize the performance from your system.

760


2009



Unit Summary

Unit Summary You should now be able to: • Describe the steps to validate the configuration • Describe the steps to validate the data connectivity • Describe the steps to validate metadata • Describe the steps to validate the results. • Describe the best practices which may be taken to maximize the performance from your system.

2009


761


BO100

Unit Summary

762


2009


BO100



Test Your Knowledge

763


2009


BO100

BO100

Course Summary You should now be able to: • • • •

764

Describe the integration of SAP BusinessObjects software with SAP NetWeaver BW Install and configure BusinessObjects XI Integration for SAP Solutions Describe how the SAP NetWeaver BW concepts are being mapped to SAP BusinessObjects software Describe Crystal Reports and SAP, Voyager and SAP Connectivity, Web Intelligence and OLAP Universes, Publication with SAP Security, Xcelsius, Live Office, Query as a Web Services, SAP Enterprise Portal, and troubleshooting best practices


2009


Course Summary

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


765


Feedback

BO100 - Integration for SAP BW.pdf

Recommend Documents