BO100 - SAP Business Objects XI Integration for SAP NetWeaver BW

BO100SAP BusinessObjects XI

Integration for SAP NetWeaver BWSAP NetWeaver

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 93Course Duration: 5 Day(s)Material Number: 50095220

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

Copyright

Copyright © 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered 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 trademarksof Citrix Systems, Inc.

• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide 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.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESEMATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g200992041238

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2009 © 2009 SAP AG. All rights reserved. iii

About This Handbook BO100

Icons in Body TextThe 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'spresentation.

iv © 2009 SAP AG. All rights reserved. 2009

ContentsCourse Overview .......................................................... ix

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

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

Unit 2: SAP Connectivity Overview.................................. 29The SAP Business Objects Tools.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30SAP connectivity options... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Supported SAP specific features ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Unit 3: Installation of BusinessObjects XI Integration for SAPSolutions ................................................................... 55

Prerequisites .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Installing BusinessObjects XI Integration for SAP Solutions ... . 69Distributed Deployments .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Client-side Components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Post-Installation steps ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Publishing Integration for Crystal Reports .. . . . . . . . . . . . . . . . . . . . . . . 93

Unit 4: Query and Adhoc Reporting with Web Intelligence onBW.......................................................................... 115

Query and Adhoc Reporting... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Web Intelligence and SAP Business Explorer .. . . . . . . . . . . . . . . . . .121

Unit 5: OLAP Universes on SAP BW - Part 1 ..................... 147BW Variables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Mandatory variables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160SAP variables with default values ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168SAP variables with delegated search ... . . . . . . . . . . . . . . . . . . . . . . . . . .176Hierarchies in OLAP Universes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183Hierarchies and hierarchy node variables in OLAP Universes 185Simple keydate scenarios.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Keydate variable dependencies... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

2009 © 2009 SAP AG. All rights reserved. v

Contents BO100

Unit 6: OLAP Universes on SAP BW - Part 2 ..................... 207Multi-structure queries in OLAP Universes ... . . . . . . . . . . . . . . . . . . . .208Smart measures and calculations in OLAP Universes... . . . . . . .220Updating OLAP Universes... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234

Unit 7: Crystal Reports and SAP ERP.............................. 255Crystal Reports Overview... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256Crystal Reports and SAP tables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260Crystal Reports and ABAP Functions ... . . . . . . . . . . . . . . . . . . . . . . . . . .271Crystal Reports and Classic InfoSets .. . . . . . . . . . . . . . . . . . . . . . . . . . . .281Crystal Reports and InfoSets Queries.. . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Unit 8: Crystal Reports and SAP BW - Part 1..................... 293SAP BW Metadata in Crystal Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . .294Crystal Reports with simple SAP BW queries.. . . . . . . . . . . . . . . . . . .303Crystal Reports against advanced SAP BW queries.. . . . . . . . . . .312

Unit 9: Crystal Reports and SAP BW - Part 2..................... 327Crystal Reports with SAP BW queries with hierarchies... . . . . . .328Crystal Reports against SAP BW cubes ... . . . . . . . . . . . . . . . . . . . . . . .338Crystal Reports and keydate variables... . . . . . . . . . . . . . . . . . . . . . . . . .342SAP variable personalization... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349

Unit 10: Voyager with SAP BW ...................................... 355Creating connections to SAP BW with Voyager .. . . . . . . . . . . . . . . .356SAP BW metadata in Voyager .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365SAP Variables with Voyager .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371

Unit 11: Xcelsius with Live Office ................................... 389Xcelsius with Live Office ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390Creating an Xcelsius dashboard with Live Office ... . . . . . . . . . . . . .409

Unit 12: Xcelsius with Query as a Web Service (QaaWS) onBW.......................................................................... 421

Query as a Web Service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .422Xcelsius and Query as a Web Service ... . . . . . . . . . . . . . . . . . . . . . . . . .432

Unit 13: SAP Security Integration and Creating Publications 461Server side trust and impersonation ... . . . . . . . . . . . . . . . . . . . . . . . . . . .463SAP server configuration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468BusinessObjects Enterprise configuration ... . . . . . . . . . . . . . . . . . . . . .476Creating a publication ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .510

vi © 2009 SAP AG. All rights reserved. 2009

BO100 Contents

Unit 14: Integrating with SAP Enterprise Portal ................. 523Integrating BusinessObjects Enterprise content into SAP

Enterprise Portal using iViews ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525Portal System landscape for BusinessObjects Enterprise ... . .530Creating BusinessObjects Enterprise content iViews ... . . . . . . . .543Creating portal pages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .553Creating portal worksets .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .563Creating portal roles .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .571BusinessObjects Enterprise Repository Manager .. . . . . . . . . . . . . .584

Unit 15: Troubleshooting the SAP Connectivity ................. 613Troubleshooting Web Intelligence connectivity .. . . . . . . . . . . . . . . . .614Troubleshooting Crystal Reports connectivity.. . . . . . . . . . . . . . . . . . .622Additional troubleshooting tools.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .627

2009 © 2009 SAP AG. All rights reserved. vii

Contents BO100

viii © 2009 SAP AG. All rights reserved. 2009

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

Target AudienceThis course is intended for the following audiences:

• SAP Netweaver BW customers, system administrators, project teammembers, system integrators, and technical consultants

Course PrerequisitesRequired Knowledge

• Fundamental knowledge in SAP NetWeaver BW 7.0 and BusinessObjectsEnterprise client tools and servers.

Course GoalsThis course will prepare you to:

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

Course ObjectivesAfter completing this course, you will be able to:

• Describe the integration of SAP BusinessObjects software with SAPNetWeaver BW

• Install and configure BusinessObjects XI Integration for SAP Solutions• Describe how the SAP NetWeaver BW concepts are being mapped to SAP

BusinessObjects software

2009 © 2009 SAP AG. All rights reserved. ix

Course Overview BO100

• 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, andtroubleshooting best practices

x © 2009 SAP AG. All rights reserved. 2009

Unit 1BusinessObjects XI Integration for

SAP Solutions

Unit OverviewThis unit introduces you the concepts of Business Intelligence and the variousroles that are important in your organization when you implement your businessintelligence strategies with SAP BusinessObjects software. Later this unitprovides you with an overview of the components that are part of BusinessObjectsXI Integration for SAP Solutions.

Unit ObjectivesAfter 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 ContentsLesson: What's in SAP BusinessObjects Software ... . . . . . . . . . . . . . . . . . . . . . . . .2Lesson: BusinessObjects Enterprise Architecture Overview ... . . . . . . . . . . . . .9Lesson: Components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2009 © 2009 SAP AG. All rights reserved. 1

Unit 1: BusinessObjects XI Integration for SAP Solutions BO100

Lesson: What's in SAP BusinessObjects Software

Lesson OverviewThis lesson provides a high-level overview of the different client tools andapplications in SAP BusinessObjects software.

Lesson ObjectivesAfter completing this lesson, you will be able to:

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

Business ExampleWhat is Business Intelligence?

By understanding Business Intelligence (BI), you will better comprehend how aBusinessObjects 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 accessingand exploring information, analyzing this information, and developing insightsand understanding that lead to improved and informed decision making. BIusage crosses the spectrum of users, both internally and externally throughoutany enterprise, and includes rank-and-file workers, executives, analysts, andknowledge 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


BO100 Lesson: What’s in SAP BusinessObjects Software

Business Intelligence can help organizations to:

• Identify and track key performance metric against their direct competitorsand 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 EnterpriseBusinessObjects Enterprise brings together features from across theBusinessObjects product line to meet the diverse needs of users, from reportingquery and analysis, dashboards and visualization to predictive analysis.BusinessObjects Enterprise ensures that all people within an organization get theright interface and level of interactivity necessary for their role

DescribingBusinessObjects Enterprise client application by roleBusinessObjects Enterprise includes and/or interacts with most BusinessObjectsclient tools. Depending on the job role, different client tools are used. The majorfour roles in BusinessObjects Enterprise are:

• Administrator• Business User• Data Manager• Designer

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



Figure 1: BusinessObjects Enterprise Client Tools

Role Tools Description

Busines-sObjectsEnterpriseInfoView

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

WebIntelligence

A web-based tool that provides query, reporting, andanalysis functionality for relational data sources in asingle web-based product. Web Intelligence allowsusers to create reports, perform ad hoc queries, analyzedata, and apply report formatting.

WebIntelligencerich client

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

Live Office BusinessObjects Live Office integrates with theMicrosoft Office environment, allowing for dynamicallyupdated data to be embedded within MicrosoftPowerPoint, Excel, and Word documents. In addition,you can share your documents with others over the webfor collaborative decision-making.

Query asa WebService

Query as a Web Service provides new and easy ways toanalyze information through user-driven client solutionsfor businesses. Business Intelligence (BI) content isusually bound to a specific user interface of BI tools.Query as a Web Service changes this by allowing BIcontent to be delivered to any user interface that canprocess web services.

Busi-nessUser




Voyager Voyager is an AJAX-based online analytical processing(OLAP) web client designed for business and financialanalysts. It not only provides access to a wide rangeof OLAP databases, but also allows users to combineinformation from different systems within a singlework space. Voyager offers a comprehensive range ofbusiness and time calculations, and includes featuressuch as time sliders to analyze OLAP data.

DashboardBuilder

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

Perfor-manceManager

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

CrystalReports

A Windows-based reporting tool that is the industrystandard. Used to create and integrate powerful reportsin BusinessObjects Enterprise.

WebIntelligence

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

DashboardManager

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

DesktopIntelligence

A Windows-based reporting tool that installs withBusinessObjects Enterprise. Designers can createreports, then publish them to InfoView where they canbe viewed and scheduled. Users can share and distributeDesktop Intelligence documents by exporting them indifferent formats.

De-signer

Xcelsius Xcelsius is an intuitive application that uses a Windowsinterface to allow you to build interactive models of dataand formulas from Excel spreadsheets. These modelscan then be exported in multiple formats to meet yourspecific business needs and be used by other individualsin your organization.




CentralManage-ment Con-sole Ad-ministrator(CMC)

A web-based interface that allows you to perform usermanagement tasks such as setting up authenticationand adding users and groups. It also allows you topublish, organize, and set security levels for all of yourBusinessObjects Enterprise content and enables you tomanage servers and create server groups.

CentralConfigura-tion Man-ager Ad-ministrator(CCM)

The CCM is a Windows based application thatallows you to create and configure SIA nodes andstart/restart your Web Applications Server. In addition,the CCM allows you to configure Windows specificnetworking parameters (such as SSL encryption).These configuration parameters apply to all the serverscontained in the node. The CCM can also be usedfor limited system administration such as starting andstopping servers.

PublishingWizard

A locally-installed Windows application that enablesboth administrators and end users to add reports toBusinessObjects Enterprise. It can be used for masspublishing of reports.

ReportConversionTool

The Report Conversion Tool converts DesktopIntelligence reports to the Web Intelligence format andpublishes the converted reports to the CMS.

ImportWizard

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

RepositoryDiagnosticTool

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

Ad-minis-trator

Life CycleManager

BusinessObjects Enterprise Life Cycle Manager (theLCM tool) is a web-based application that provides acentralized view to monitor the progress of the entirelife cycle process. It enables you to move BI resourcesfrom one system to another system without affectingthe dependencies of these resources. It also enablesyou to manage different versions of BI resources, mapdependencies of BI resources, and roll back a promotedresource to restore the destination system to its previousstate.




UniverseDesigner

A Windows-based tool that allows users to buildsemantic layer objects that simplify underlying databasecomplexity, and set row- and column- level security.The objects (such as filters) set row-level security. Thissemantic layer is the foundation for empowering endusers to customize query and analysis. It abstracts thecomplexity of data by using business language ratherthan data language to access, manipulate, and organizedata.

BusinessViewManager

A Windows-based tool that allows users to buildsemantic layer objects that simplify underlying databasecomplexity, and set row- and column-level security.The objects (such as filters) set row-level security.You can simplify data access for report designers byinsulating them from the raw data structures. You canbuild connections to multiple data sources, join tables,alias field names, create calculated fields, and thenutilize this simplified structure as a Business View inBusinessObjects Enterprise. Report designers can thenuse the Business View as the basis for their reports,rather than accessing the data directly and building theirown queries.

DataMan-ager

DataServices

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



Lesson Summary

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


BO100 Lesson: BusinessObjects Enterprise Architecture Overview

Lesson: BusinessObjects Enterprise ArchitectureOverview

Lesson OverviewIn this lesson, you will review the architecture and components of BusinessObjectsEnterprise.


• Explain the architecture and technical requirements for BusinessObjectsEnterprise front-end tools

• Describe the BusinessObjects Enterprise service groups and servers

Business ExampleEnd users log in, create, edit, and interact with reports and documents usingspecialized 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 thatinclude:

• 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 tointegrate BusinessObjects Enterprise into other enterprise systems, and to sharedynamically updated documents with users on separate networks.

When certain tasks are performed in BusinessObjects Enterprise, such as loggingin, scheduling a report, or viewing a report, information flows through the systemand the various servers communicate with each other. BusinessObjects Enterpriseserver architecture consists of web, management, processing, and storage services.Understanding this architecture will help you visualize how actions performed inclient applications are processed by the services.



BusinessObjects Enterprise architectureA full deployment of BusinessObjects Enterprise is made up of client applications,BusinessObjects Enterprise services, and the organization’s relational and/orOLAP data sources.

Figure 2: BusinessObjects XI 3.1 Architecture

Describing BusinessObjects Enterprise servicegroups and serversThe BusinessObjects Enterprise system can be installed on a single machine,spread across different machines in an intranet, or separated over a wide areanetwork (WAN). For learning purposes, BusinessObjects Enterprise services canbe grouped as follows:



Servicegroup

Servers

Webservices

Web Application Server, Business Process BI Services

Manage-ment ser-vices

Central Management Server, Event Server, Destination Job Server

Storageservices

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

Processingservices

Adaptive Processing Server, Adaptive Job Server, Program JobServer, Crystal Reports Job Server, Web Intelligence Job Server,Web Intelligence Processing Server, List of Values (LOV) Server,Desktop Intelligence Job Server, Desktop Intelligence ProcessingServer, 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 tofacilitate learning in this course by grouping servers together that sharesimilar operating behavior. In reality, BusinessObjects Enterprise webservices must interact with management and processing services, storageservices must interact with management and processing services, andso forth.

Enterprise InfrastructureThe Enterprise Infrastructure provides the basic messaging mechanism needed forBusinessObjects Enterprise components to communicate with one another. TheEnterprise Infrastructure is a series of services that are designed to communicatevia CORBA (Common Object Request Broker Architecture), which runs overTCP/IP.

Some CORBA applications use a Name server. The Name server service is afacility of the underlying CORBA architecture that binds the BusinessObjectsEnterprise servers together. The Name server provides a directory of the serversregistered in the BusinessObjects Enterprise environment and helps establish



connections between clients and these servers. The Name server service is a partof the Central Management Server. The Enterprise Infrastructure establishesconnections between clients and servers.

1. It is the centerpiece of BusinessObjects Enterprise technology whichfacilitates communication between servers.

2. A client object can transparently make requests to server objects using theEnterprise Infrastructure.

• A server object is a server that participates in serving requests to clientobjects.

• A client object is a client that makes requests to servers on theEnterprise Infrastructure.

Note: In the BusinessObjects Enterprise environment, most servicesact as clients and servers to each other during transactions between theservers. When a BusinessObjects Enterprise server starts, it registers itselfwith the Name server in the CMS. The server provides information aboutitself, such as its IP address, TCP port, and description of the server, to theName Server. Each individual server polls the CMS every 60 seconds toget an updated list of available servers in the system.

BusinessObjects Enterprise web servicesThe web services are server-side components that process requests from clientapplications and communicate these requests to the appropriate server. Theyinclude support for report viewing, and logic to understand and direct web requeststo the appropriate BusinessObjects Enterprise server.

BusinessObjects Enterprise web services include:

• Web Application Server

The Web Application Server uses the BusinessObjects Enterprise SDK to interfacewith the rest of the BusinessObjects Enterprise services. The Web ApplicationServer acts as a gateway between the browser and the rest of the components inBusinessObjects Enterprise.

Note: When configuring servers using the Central Management Console,the CMS holds the configuration settings and the CMS communicateswith all BusinessObjects Enterprise servers.

Business Objects web services provide a Java API accessed by rich clients in theuser interaction tier, such as Live Office and Crystal Reports.

Web Services consists of software components that can be called remotely usingthe Simple Object Access Protocol (SOAP). SOAP is a protocol for exchanginginformation that is not dependent on a specific platform, object model, orprogramming language.



BusinessObjects Enterprise Web Services includes functionality in the followingareas:

• Session: Authentication and user privilege management.• BI platform: Exposes advanced platform features such as scheduling, search,

user and group administration, server administration, platform events, andcalendars.

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

BusinessObjects Enterprise management servicesThe management services manage the BusinessObjects Enterprise system. Theseservices maintain all security information, send requests to the appropriateservices, manage auditing information, and maintain a record of each and everyinstance and its location.

The management services are:

• Central Management Server (CMS)

The CMS is responsible for authenticating users and groups, and keeping track ofthe availability of the other BusinessObjects Enterprise services. It also maintainsthe BusinessObjects Enterprise system database, which includes information aboutusers, groups, security levels, BusinessObjects Enterprise content, and services.The CMS also maintains a separate audit database of information about useractions 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. Itallows for extra auditing and tracking of some system information.

• Server Intelligence Agent

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

• Event Server



The Event Server manages file-based events. It monitors the directory youspecified when setting up a file-based event. When the appropriate file appears inthe 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 instanceor object to a specified destination (Inbox, Email, FTP, disk location) independentof any schedules related to those instances or objects. It can also send a shortcut toa user’s inbox. For example, the server updates the shortcut in the CMS databaseto 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 servicesThe storage services are responsible for storing objects and object instances. Thestorage services are:

• Input File Repository Server

The Input File Repository Server manages all of the report and program objectsthat 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 generatedby the Crystal Reports Job Server and the program instances generated by theProgram Job Server. It also manages instances generated by the Web IntelligenceProcessing Server and the LOV Job Server.

It can store the following files: .rpt, .csv, .xls, .doc, .rtf, .txt, .pdf, .wid, .rep.

Note: .rpt and .wid files are stored as reports/documents with saved data.

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

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



BusinessObjects Enterprise processing servicesThe processing services access the data and generate reports. This is the only tierthat interacts directly with the databases that contain report data.

Which services become involved in processing an object is determined by whetherthe object is being scheduled or viewed on demand. Viewer choice also plays arole in determining which servers are involved in object processing.

The processing services are:

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

Crystal Reports Job ServerThe 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 Serverretrieve the file to be run from the Input File Repository Server, run thereport or program, and then save the processed file to the Output FileRepository Server as an instance.

Adaptive Job ServerThe Adaptive Job Server receives scheduling Web Intelligence documents requestsfrom the CMS and then forwards them to the processing servers for processing.

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

Web Intelligence Processing ServerThe Web Intelligence Processing Server processes Web Intelligence Documentrequests.

List of Values (LOV) Job ServerThe List of Values Job Server receives scheduling requests from the BusinessView manager and processes scheduled List of Values objects to populate themwith values retrieved from a database.



Desktop Intelligence Job ServerThe Desktop Intelligence Job Server processes scheduling requests received fromthe CMS for Desktop Intelligence documents and generates the instance of theDesktop Intelligence document.

Desktop Intelligence Processing ServerThe Desktop Intelligence Processing Server processes viewing requests forDesktop Intelligence documents and generates the Desktop Intelligence document.

Connection ServerThe Connection Server is a service that can be administered and configuredthrough the CMC (Central Management Console). The Connection Server isresponsible for the database connectivity to access data. It is invoked when userswant to edit and view Desktop Intelligence documents through InfoView in 3-tiermode. It is also used by some EPM services.

Note: The Connection Server libraries are present on the WebIntelligence Processing Server, and Desktop Intelligence ProcessingServer. These libraries allow services to query the database directlywithout communicating with the Connection Server service. The viewingprocessing services are.

• Crystal Reports Processing Server

The Crystal Reports Processing Server is responsible for responding to filesrequests by processing reports and generating Encapsulated Page Format (.epf)files. The Crystal Reports Processing Server retrieves data for the report from thelatest instance or directly from that database. After it generates the report, theProcessing Server converts the requested data to one or more EPF files. Thesefiles 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 fromthe Web Application Server and then communicates with the Input File RepositoryServer in order to obtain a copy of the Web Intelligence Document (WID) file andthe universe definition. When viewing an existing instance of a WID, the WebIntelligence Processing Server communicates with the Output File RepositoryServer to obtain an existing historical instance of a WID.

• Report Application Server

Report Application Server resolves Dynamic Recipient Lists at design time andRuntime in Publishing, as well as with LiveOffice. The RAS also provides thead hoc reporting capabilities that allow users to create and modify reports overthe Web. As with the Crystal Reports Processing Server, the RAS supports Java



viewer SDKs. The Report Application Server also includes an SDK for reportcreation and modification, providing you with tools for building custom reportinteraction interfaces.

• Multi-Dimensional Analysis Server

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

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

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

• Search Server

The Search Server processes search requests and executes the indexing. Yourdeployment can include multiple Search servers, and search requests are activelyprocessed by all available servers. However, only one Search server performsthe indexing process.



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


BO100 Lesson: Components

Lesson: Components

Lesson OverviewThis lesson provides you with an overview of the components that are part of theBusinessObjects XI Integration for SAP solutions.


• Describe the different components of the BusinessObjects XI Integrationfor SAP solutions

Business ExampleThe management executives in Company A felt that they did not have enoughvisibility 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 gethighly summarized monthly data, displaying various aspects of their business.BusinessObjects XI Integration for SAP Solutions provides you with powerfulreport-design tools and a framework for managing, scheduling, and distributingyour reports over the Web. Also it enables you to extract additional value fromyour SAP Business Information Warehouse (BW) and SAP ERP data and share itwith users across the enterprise. In addition, SAP Authentication enables SingleSign On between your SAP system and BusinessObjects Enterprise

What’s in the BusinessObjects XI Integration for SAPsolutionsBusinessObjects XI Integration for SAP solutions consists of several connectivityand 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 SAPsecurity model can also be leveraged to allow users to access the contentusing the existing SAP user accounts.



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

Data AccessBusinessObjects XI Integration for SAP Solutions provides connectivity to yourSAP 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 DataStores, and MDX cubesBusinessObjects XI Integration for SAP Solutions provides connectivity to yourSAP 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 reportoff your BW queries within Crystal Reports. The toolbar also allows you to savereports to BW and publish them directly to BusinessObjects Enterprise .

The InfoSet driver provides Crystal Reports with another means of accessingSAP data sources: this driver can access ERP InfoSets (previously known asFunctional Areas) and ABAP Queries. You access this driver through the DataExplorer in Crystal Reports .

The DataStore Objects (DSO) driver allows you to use existing DSO objects fromyour BW Data Warehouse as a data source in Crystal Reports.

The SAP BW MDX Query driver introduces new flexibility when reporting offBW cubes and queries. By writing reports with the MDX Query driver, you gaindirect access to BW cubes, display attributes, and multiple structures.

Note: One advantage of these drivers is that they allow business usersto report off predefined views of your SAP data. Tables and fields arefirst logically grouped by an SAP content expert into queries, infoSets,and so on. You then make these data sources accessible to users who aredesigning reports with Crystal Reports.



Reporting off other SAP data sourcesBusinessObjects XI Integration for SAP Solutions also includes the Open SQLdriver, which allows you to report off additional SAP data sources within CrystalReports, 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 flexibilityit provides for accessing data in SAP. This flexibility, however, results in ahigher level of complexity than with the InfoSet driver.

When you create reports that use the Open SQL driver, you gain easy accessto SAP.s transparent tables, pool tables, cluster tables, and views. Userswho are currently involved with the production of ABAP reports will find iteasyto build reports quickly with this driver.

Advanced functionality in the driver also allows reporting against ABAPfunctions and ABAP data clusters. ABAP developers can use these featuresto 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 OnlineAnalytical Processing (OLAP) viewing capabilities of Voyager and CrystalReports with your SAP Business Information Warehouse (BW) system.Users can connect to multidimensional BW Info Cubes and generate reportsthat incorporate complex data analysis.

Crystal Reports SAP ToolbarIntegrated within Crystal Reports, the SAP Tools toolbar facilitates tasksassociated with reporting off BW queries. It allows you to log on to BW and workwith its data sources, save reports to BW, and publish reports immediately toBusinessObjects Enterprise via BW.



SAP AuthenticationThis component allows you to expand and customize the ways in whichBusinessObjects Enterprise authenticates users. This SAP security plug-in offersseveral key benefits:

• It acts as an authentication provider that verifies user credentials againstyour SAP system on behalf of the BusinessObjects Enterprise CentralManagement Server (CMS). When users log onto BusinessObjects Enterprisedirectly, they can choose SAP Authentication and provide their usual SAPuser name and password. BusinessObjects Enterprise can also validateEnterprise Portal logon tickets against SAP systems.

• It facilitates account creation by allowing you to map roles from SAPto BusinessObjects Enterprise user groups, and it facilitates accountmanagement by allowing you to assign rights to users and groups in aconsistent manner within BusinessObjects Enterprise.

• It dynamically maintains SAP role listings. Therefore, once you map an SAProle to BusinessObjects Enterprise, all users who belong to that role canlog onto BusinessObjects Enterprise. When you make subsequent changesto the SAP role membership, you need not update or refresh the listing inBusinessObjects Enterprise.

• The SAP Authentication component includes a web applicationfor configuring the plug-in. You can access this application in the"Authentication" area of the Central Management Console (CMC).

BW PublisherThis component allows you to publish reports individually or in batches from BWto BusinessObjects Enterprise.

Web contentThis component includes BusinessObjects Enterprise InfoView. InfoView allowsusers to organize and view their Crystal reports in multiple languages over theWeb.

Transport filesYou use these transport files to connect to SAP through Crystal Reports andBusinessObjects Enterprise.

BW Content Administration WorkbenchThis feature allows you to manage report publishing from with BW. You canidentify roles in your BW with specific BusinessObjects Enterprise systems,publish reports, and synchronize between BW and a BusinessObjects Enterprisesystem



Sample reportsThe sample reports demonstrate a variety of ways in which you can extract valuefrom SAP data using different database drivers.

Sample iViewsSample iViews illustrate how BusinessObjects Enterprise SAP Edition can beimplemented with SAP Enterprise Portal version 6 and later. These iViewsdemonstrate sample functionality for alerts, and thumbnail views inside SAPEnterprise Portal.

Knowledge Management Console (KMC)The Knowledge Management interface enables third-parties to integrateany repository into the SAP Enterprise Portal. The KMC allows users tointegrate BusinessObjects Enterprise into the SAP Enterprise Portal, When theBusinessObjects Enterprise repository is integrated into the KMC framework,the objects in the repository are accessible for different work flows like thecollaboration features of the SAP Enterprise Portal.

Integrated architectureThe following diagram illustrates how each of the BusinessObjects XI Integrationfor SAP Solutions components expands upon the multi-tier framework ofBusinessObjects Enterprise.



Figure 3: Architecture diagram for BusinessObjects XI Integration for SAPSolutions



Lesson Summary

You should now be able to:• Describe the different components of the BusinessObjects XI Integration

for SAP solutions


Unit Summary BO100

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


BO100 Test Your Knowledge

Test Your Knowledge

1. Which BusinessObjects product uses the OLAP BAPI driver to connectto the SAP BW InfoCube?Choose the correct answer(s).□ A Crystal Reports using standard connection□ B Web Intelligence Rich Client using a Local Data Source□ C Web Intelligence Rich Client using OLAP Universe□ D Crystal Reports using SAP Toolbar

2. Which of the following SAP data sources can be accessed using the OpenSQL driver?Choose the correct answer(s).□ A Transparent Tables□ B Pool tables□ C Cluster Tables□ D Views□ E All of the above

3. Which BusinessObjects product displays the SAP toolbar afterBusinessObjects XI Integration for SAP Solutions is installed?Choose the correct answer(s).□ A Universe Designer□ B Web Intelligence Rich Client□ C Xcelcius□ D Crystal Reports


Test Your Knowledge BO100

Answers

1. Which BusinessObjects product uses the OLAP BAPI driver to connectto the SAP BW InfoCube?

Answer: C

Correct answer is C.

2. Which of the following SAP data sources can be accessed using the OpenSQL driver?

Answer: E

All of the above can be accessed using the OpenSQL driver.

3. Which BusinessObjects product displays the SAP toolbar afterBusinessObjects XI Integration for SAP Solutions is installed?

Answer: D

Crystal Reports


Unit 2SAP Connectivity Overview

Unit OverviewSAP BusinessObjects tools expand the scope of BW by providing a wide rangeof tools and applications. SAP BusinessObjects tools support businesses byoptimizing the connection between people and information. This unit providesyou with an overview of the various data connectivity options to SAP BW andSAP ERP for the SAP BusinessObjects products.


• 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 ContentsLesson: The SAP Business Objects Tools .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Lesson: SAP connectivity options ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Lesson: Supported SAP specific features ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43


Unit 2: SAP Connectivity Overview BO100

Lesson: The SAP Business Objects Tools

Lesson OverviewIn this lesson you will learn the different tools in the SAP BusinessObjectsEnterprise 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 ExampleYou are planning to implement a BusinessObjects Enterprise solution integratedwith SAP NetWeaver BW and would like classify and position the variousBusinessObjects reporting tools in your environment where business users requirefull information autonomy.

The SAP Business Objects ToolsBusinessObjects Platform suite components for reporting include:

• Crystal Reports• Desktop Intelligence• Web Intelligence• Voyager• Xcelsius• Live Office

Note: Desktop Intelligence functionality is being replaced by WebIntelligence and Web Intelligence Rich Client

These tools are suited for various user audiences and business solutions


BO100 Lesson: The SAP Business Objects Tools

Tool Best Audience Best Business Solution

Crystal Reports Most business users Static reporting, highlyformatted reports, pixelperfect presentation,mass printing anddistribution, relationaldatabases, enterpriseapplications and datawarehouse sourced data

Web Intelligence Most casual businessusers

Powerful query and easeof use adhoc reporting,self serve templatebased report creationand interactive analysis,enterprise distribution,with mostly relationaland OLAP sourced data

Voyager Analyst and businessuser

Multi dimensionalanalysis of information

Xcelsius Most business users Dashboard andpresentation qualityvisualizations

Live Office Analyst and casual users Seamless MS Officeintegration with dataretrieval, presentationand distribution

Figure 4: Baseline use cases and product mapping



As business users roles change during their business life from day to day, thetype and appetite for information consumption also changes. A single userfor this reason may consume data from different tools sets depending on theirrequirements.

A cost center manager may consume a highly formatted report with exceptionson cost items that exceeded budget for the month as a Crystal Report exported toExcel attached in email.

A brand manager may require advertising spend by campaign linked to sales forthe month to determine marketing cost effectiveness using Web Intelligence tocombine data from two different sub-systems; marketing and sales.

A product manager may want to analyze product category margins by locationacross market for this year and last year using Voyager.

A North American sales director is presenting to the board performancebased sales by region and product in the form of a dashboard and PowerPointpresentation using Xcelsius and Live Office.

The examples above demonstrate that there is a different solution based on userbusiness needs. Query and adhoc reporting is best satisfied by Web Intelligence.

Note: The component products will evolve and change as futurecomponents merge and are added within the BusinessObjects and SAPBW product platforms. For example Voyager will transform into Pioneerbecoming a more powerful multi dimensional solution for power analysts.

Figure 5: Product mapping with solution capabilities


BO100 Lesson: The SAP Business Objects Tools

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



Lesson: SAP connectivity options

Lesson OverviewIn this lesson, you will learn about the SAP data source connectivity optionsavailable from the BusinessObjects product.


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

Business ExampleYou are planning to implement a BusinessObjects Enterprise solution integratedwith SAP NetWeaver BW and would like identify the connectivity optionsavailable to your business environment.

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


BO100 Lesson: SAP connectivity options

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 IntelligenceThe SAP data sources available from Web Intelligence are:



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 viaData Federator XI 3.1 Netweaver BI connector.

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

Figure 8: SAP connectivity for Voyager

• SAP BW

– BW queries and BW cubes via MDX.

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



Figure 9: SAP connectivity for Analytics

• SAP BW


Universe via SQL).^

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



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

• SAP BW


Universe via SQL).

Note: Query as a Web Service results are retrieved from the BW server ondemand. Query results always are up to date and conversely, the queryresults cannot be pre-scheduled for faster response time viewing. Thequery definition is saved in the BusinessObjects Enterprise repository,though query data is saved with the definition.

SAP connectivity for Live OfficeLive Office is able to leverage data from the following documents and serviceproviders:

• Crystal Reports.• Web Intelligence.• Universe Query (i.e OLAP and Relational Universes)

Note: Crystal Reports and Web Intelligence documents can be optionallyscheduled prior to view time usage in Live Office. Scheduling at anappropriate frequency allows query results to be pre-cached for fasterloading at view time, especially for very large queries or for data that is notchanging rapidly after being pre-cached; reporting load can be balancedacross BOE servers, query load can be balanced on the BW server.

Universe Query is similar to QaaWS, data query results are always up todate and run on demand. The Universe Query definition is embeddedwithin the Live Office document.

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



Figure 11: SAP connectivity for Live Office

• SAP ERP


• 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 XcelsiusXcelsius is able to leverage data from the following documents and serviceproviders:



Figure 12: SAP connectivity for Xcelsius

• Live Office.• Web Services.



Therefore, the SAP data sources available from Xcelsius are:

• SAP ERP


• 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 Intelligencedocuments can be optionally scheduled prior to view time usage. Scheduling at an appropriate frequency allows query results to bepre-cached for faster loading at view time, especially for very largequeries or for data that is not changing rapidly after being pre-cached;reporting load can be balanced across BOE servers, query load can bebalanced on the BW server.

Live Office Universe Query is similar to QaaWS, data query results arealways up to date and run on demand. QaaWS query definition can bedesigned on the fly and saved in the BusinessObjects Enterprise repository(no query data is saved with the definition) whilst Universe Querydefinition is imbedded within the Live Office document.



Lesson Summary

You should now be able to:• Describe the SAP data sources connectivity options available to the following



BO100 Lesson: Supported SAP specific features

Lesson: Supported SAP specific features

Lesson Overview[Enter a brief overview of the lesson.]



Business ExampleYou are planning to implement a BusinessObjects Enterprise solution integratedwith SAP NetWeaver BW and would like to list the supported features per eachBusinessObjects client tool in your environment.

Supported features per client tool

Crys-tal Re-portsBWQueryDriver

Crys-tal Re-portsBWMDXDriver

OLAPUni-verse

Voy-ager

Addi-tionalCom-ment

XI R2 XI R2 XI 3.x XI R2 XI 3.x

Info-Provider

Support forInfoCubeDirectAccess

NA x x x x x

Support forMultiCubeDirectAccess

NA x x x x x

Support forRemote-Cube DirectAccess

NA x x x x x





OLAPUni-verse

Voy-ager

Addi-tionalCom-ment

Support forBW Queries

x x x x x x

Character-istic Values

Key x x x x x x

ShortDescriptions

x x x x x x

MediumDescriptions

NA x x x x x

LongDescriptions

NA x x x x x

QueryFeatures

Supportfor singleHierarchies

x x x x x x

Supportfor singleHierarchies

x x x x x x

Support forFree Charac-teristics

NA x x x x x

Support forCalculatedKeyfigures

x x x x x x

Support forRestrictedKeyfigures

x x x x x x

Support forCurrencies

x x x _ x x

Support forUnits

x x x _ x x





OLAPUni-verse

Voy-ager

Addi-tionalCom-ment

Support forMultipleStructures

NA x x x x x

Support forFormulas

x x x x x x

Support forSelections

x x x x x x

Support forFilter

x x x x x x

Supportfor DisplayAttributes

x x x x x _

Support forConditions

NA NA NA NA NA NA Rea-son:Notsup-ported/rel-evantto SAPBAPIinter-face.Pos-sibleDataFed-eratorworkaround:createa filteron themea-sureobjects

Support forExceptions

NA NA NA NA NA NA





OLAPUni-verse

Voy-ager

Addi-tionalCom-ment

Support forNaviga-tional At-tributes

x x x x x x

Supportfor com-poundedcharacter-istics

x x x x x x

Support forunbalancedHierarchies

x x x x x x

Supportfor raggedHierarchies

x x x x x x

Data Types

Supportfor type"CHAR"(Character-istics)

x x x x x x

Supportfor type"NUMC"(Character-istics)

x x x _ x x

Supportfor type"DATS"(Character-istics)

_ _ _ _ x _ If notsup-ported,thenChar-acter-isticsare re-turned





OLAPUni-verse

Voy-ager

Addi-tionalCom-ment

asSTRINGvalue

Support fortype "TIMS"(Character-istics)

_ _ _ _ _ _ If notsup-ported,thenChar-acter-isticsare re-turnedasSTRINGvalue

Support fortype "Date"(Keyfigures)

x x x _ _ x

Support fortype "Time"(Keyfigures)

x x x _ _ x

SAPVariable -ProcessingType

User Input x x x x x x

Authoriza-tion

x x x x x x

Replace-ment Path

x x x x x x

SAP Exit /Custom Exit

x x x x x x

PreCalcu-lated ValueSet

x x x x x x





OLAPUni-verse

Voy-ager

Addi-tionalCom-ment

Generalfeatures forVariables

Support forOptional vsMandatoryVariables

x x x _ x x

Support forVariable de-pendencies

_ x x _ _ x

Support forKeydate de-pendencies

x _ x Lim-ited

x x

Supportfor DefaultValues

x x x _ x x

Support forPersonalizedValues

x x x _ _ _

SAPVariables- VariableType

Single Value x x x x x x

MultipleSingle Value

x x x x x x

Range Value x x x x x x





OLAPUni-verse

Voy-ager

Addi-tionalCom-ment

ComplexSelection

x x x Lim-ited(x1)

Lim-ited(x1)

x x1 =Vari-ablesareturnedinto asinglerangevalueparam-eter

FormulaVariable

x x x x x x

HierarchyVariable

x x x x x x

HierarchyNodeVariable

x x x x x x

TextVariable

NA NA NA NA NA NA

KeydateVariable

x _ x x x x

CurrencyVariable

x x x x x x

HierarchyVersionVariable

NA NA NA NA NA NA



Lesson Summary

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


BO100 Unit Summary

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




Unit Summary BO100



Test Your Knowledge

1. Help desk billing reports in PDF format need to be e-mailed each month toeach cost center. The various cost centers' departments also need to be ableto view these invoices online historically when needed. The report layout isa fairly fixed format and with transactions by grouped cost center and helpdesk service area. Which SAP BusinessObjects reporting tool would bethe most appropriate to use?Choose the correct answer(s).□ A Web Intelligence□ B Crystal Reports□ C Voyager and/or SAP Business Explorer (BEx)□ D Xcelsius



Answers

1. Help desk billing reports in PDF format need to be e-mailed each month toeach cost center. The various cost centers' departments also need to be ableto view these invoices online historically when needed. The report layout isa fairly fixed format and with transactions by grouped cost center and helpdesk service area. Which SAP BusinessObjects reporting tool would bethe most appropriate to use?

Answer: B

Crystal Reports - high quality fixed design contracted to BI consultant.Report bursting, PDF exporting and scheduled destinations possible.


Unit 3Installation of BusinessObjects XI

Integration for SAP Solutions

Unit OverviewThis unit provides you with the steps involved to install BusinessObjects XIIntegration for SAP Solutions.


• Explain the technical prerequisites for BusinessObjects XI Integration forSAP 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

Unit ContentsLesson: Prerequisites .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Procedure: To verify the patch level of the SAP server .. . . . . . . . . . . . . . . 59Procedure: To verify the transports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


Unit 3: Installation of BusinessObjects XI Integration for SAP Solutions BO100

Procedure: To verify the profile parameters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Procedure: To export the SAP Enterprise Portal certificate.. . . . . . . . . . . 65

Lesson: Installing BusinessObjects XI Integration for SAP Solutions ... . 69Procedure: To install BusinessObjects XI Integration for SAPSolutions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Lesson: Distributed Deployments .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Lesson: Client-side Components .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Lesson: Post-Installation steps ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Procedure: To enable the SAP authentication... . . . . . . . . . . . . . . . . . . . . . . . . 82Procedure: To configure the SAP authentication options ... . . . . . . . . . . 83Procedure: To import SAP roles to BusinessObjects Enterprise ... . . 86Exercise 1: Logging onto the systems... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Lesson: Publishing Integration for Crystal Reports.. . . . . . . . . . . . . . . . . . . . . . . . . 93Procedure: To configure the BW Publisher service ... . . . . . . . . . . . . . . . . . . 96Procedure: To create a new RFC destination ... . . . . . . . . . . . . . . . . . . . . . . . . 97Procedure: To create a new BusinessObjects Enterprise serverdefinition ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Procedure: To set the SAP source parameters.. . . . . . . . . . . . . . . . . . . . . . . .104Procedure: To configure the SAP HTTP request handler .. . . . . . . . . . . .106Procedure: To configure the rights in the Content AdministrationWorkbench ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Procedure: To configure the rights in the Central ManagementConsole .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110


BO100 Lesson: Prerequisites

Lesson: Prerequisites

Lesson OverviewThis lesson provides you with a checklist before you start the installation ofBusinessObjects XI Integration for SAP Solutions.


• Explain the technical prerequisites for BusinessObjects XI Integration forSAP Solutions

Business ExampleBefore you install BusinessObjects XI Integration for SAP Solutions, you need toensure the technical prerequisites and provide a checklist of things that will haveimpact on the installation of BusinessObjects XI Integration for SAP Solutions.

SAP GUIThe SAP GUI is required for using the BusinessObjects XI Integration for SAPSolutions. The required version and the required patch level are listed in the list ofsupported platforms for the BusinessObjects Integration for SAP Solutions. Wheninstalling the SAP GUI you need to choose the following components:

• SAP GUI• BW Add-On• BI Add-On

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


http://service.sap.com


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 applicationserver. In the case of a default Tomcat deployment the path would beC:\Program Files\Business Objects\Tomcat55\shared\lib.

• librfc32.dll and sapjcorfc.dll need to be copied to the Windows\system32directory.

Note: In case the SAP GUI has been installed, the librfc32.dll doesn’tneed to be copied.

Note: If you are planning to integrate with an SAP BI 7 system, your SAPJava Connector must be version 2.1.6 at a minimum because SAP BI 7allows passwords that are longer than 8 characters and this requires at aminimum the version 2.1.6 from the SAP JavaConnector.

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



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.

Figure 14: Component Information

Note: The patch level is displayed per component.



SAP transportsBusinessObjects XI Integration for SAP Solutions includes transports as part ofthe product. These transports include functionality especially designed for theintegration with SAP. The following is a list of functionality that requires SAPtransports:

• 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 compatibletransports and ANSI transports. If the BASIS system is 6.20 or later, theUnicode compatible transports are recommended. If the BASIS system isearlier than 6.20, the ANSI transports are recommended.



To verify the transports


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.

Figure 16: Display Object List

Continued on next page



6. Select the menu Goto → Transport Logs.

Figure 17: Transport Logs

SAP single-sign-onTo be able to use single-sign-on together with the BusinessObjects Enterprisesystem requires two main settings to be configured on the SAP side:

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

Profile parametersBefore you can enable ticket based single-sign-on between SAP andBusinessObjects Enterprise, you must set up your SAP system to accept andcreate logon tickets. This involves setting two related profile parameters on yourSAP server:

• login/accept_sso2_ticket• login/create_sso2_ticket

Profile parameter Value Comment

login/cre-ate_sso2_ticket

1 or 2 Use the value 1 if the server possesses apublic-key certificate signed by the SAPCA. Use the value 2 if the certificate isself-signed. If you are not sure, then usethe value 2.

login/ac-cept_sso2_ticket

1 Use the value 1 so that the system willalso accept logon tickets.

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



To verify the profile parameters


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.

Figure 19: Display Profile

6. Verify the settings for the profile parameters.



Configure trust for the SAP Enterprise PortalThis step involves exporting an SAP Enterprise Portal certificate and importingit to the SAP server (SAP BW or SAP ERP) so that these two systems establisha trusted relationship.



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.

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




Figure 22: Trust Manager

9. Select the menu Certificate → Import.

Figure 23: Import Certificate

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



BusinessObjects Enterprise server side requirementsBefore installing BusinessObjects XI Integration for SAP Solutions, these are theprerequisites for the BusinessObjects Enterprise server:

• The file saplogon.ini needs to be installed on machines with data accesscomponents. You can add the full path to the saplogon.ini file to theSAPLOGON_INI_FILE environment variable.

Note: In case the SAP GUI has been installed the saplogon.ini file isinstalled on the client machine.

• In case load balanced logon will be part of the deployment, the following entrymust appear in the services file (found in %windir%\system32\drivers\etc\)on any BusinessObjects Enterprise machines running a CMS or dataprocessing 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, andreplace tcp port number with the port number of the message server thatBusinessObjects Enterprise will log on to (for example, sapmsTB6 3600/tcp).Ensure also that a blank line follows the entry. This standard setting allowsBusinessObjects Enterprise to log onto SAP with load balancing.



Lesson Summary

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

SAP Solutions


BO100 Lesson: Installing BusinessObjects XI Integration for SAP Solutions

Lesson: Installing BusinessObjects XI Integration forSAP Solutions

Lesson OverviewIn this lesson, you will learn about the installation procedure and configurationsteps required for BusinessObjects XI Integration for SAP Solutions.


• Install BusinessObjects XI Integration for SAP Solutions

Business ExampleYou are the system administrator and need to install BusinessObjects XIIntegration for SAP Solutions.



To install BusinessObjects XI Integration for SAPSolutions

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 forSAP Solutions. Click Next.

7. Select Custom and click Next.

8. Select the necessary components and click Next.

Figure 24: Components

Note: The above shows all components that are available for theinstallation.




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

Figure 25: CMS Logon Information

Note: The reason for this CMS logon is that the SAP specificfeatures for InfoView need to be implemented in the system database.

10. Complete the parameters for the BW Publisher and click Next.




Figure 26: BW Publisher

• Program ID

Type a descriptive string to identify the BW Publisher service. TheProgram ID can take any value, but must be 64 characters or fewer, andmay not contain spaces. The Program ID is case-sensitive.

• Gateway Host

Type the name of your BW server. If you have a BW cluster, enter thename of the central instance of BW.

• Gateway Service

Type the port number that the Gateway Host is listening on. Forexample, type 33##, where ## represents the instance number of yourSAP Gateway. Usually, the instance number is 00, and the value forthis field is 3300.

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. Asa verification step after the installation has finished you should see theSAP authentication as part of the available authentication options for SAPBusinessObjects InfoView.



Lesson Summary

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


BO100 Lesson: Distributed Deployments

Lesson: Distributed Deployments

Lesson OverviewIn this lesson, you will learn about considerations for a distributed deployment ofBusinessObjects XI Integration for SAP Solutions.


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

Business ExampleYou are a system designer and need to evaluate server-side deploymentconsiderations.

Distributed deployment considerationsIn case of a distributed deployment of BusinessObjects Enterprise, the listedBusinessObjects XI Integration for SAP Solutions component needs to beinstalled on the appropriate machines. If you select a default server installationof BusinessObjects XI Integration for SAP Solutions, the setup programdetects which elements of BusinessObjects Enterprise are present, and installsBusinessObjects 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 BAPI) MDS Server

Web Intelligence Job Server

Web Intelligence Processing Server



Component BusinessObjects Enterprise service

Connection Server

BW Publisher service Crystal Reports Processing Server

Crystal Reports Job Server

Report Application Server

All machines that have the Business ObjectsEnterprise SDK installed

SAP authentication Central Management Server (CMS)

All machines that have the Business ObjectsEnterprise SDK installed


BO100 Lesson: Distributed Deployments

Lesson Summary

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



Lesson: Client-side Components

Lesson OverviewIn this lesson, you will learn about considerations for client side components ofBusinessObjects 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 ExampleYou are a system designer and need to evaluate client-side deploymentconsiderations.

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

Client Components

Crystal Reports Data access components for SAP ERP

Data access components for SAP BW

SAP authentication

SAP BW toolbar

Universe Design Data Access components for SAP BW (OLAPBAPI)


BO100 Lesson: Client-side Components

Client Components

SAP authentication

Live Office Live Office retrieves the list of availableauthentications via web services and thereforethe SAP authentication needs to be installedand deployed on the application server hostingthe web services

Query as a Web Service(definition tool) SAP authentication



Lesson Summary

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


BO100 Lesson: Post-Installation steps

Lesson: Post-Installation steps



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

Business ExampleUpon installing the BusinessObjects XI Integration for SAP solutions, you need toensure all the post-installation procedures are complete.

Enable SAP authenticationThe SAP authentication allows the administrator to leverage the SAP users androles and it allows the end user to leverage functionality like single-sign-on withBusinessObjects Enterprise.



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 <SID> and client number from the SAP system.

5. Enter Application Server name including SAP Router String

Note: For example: ./H/tdc-saprouter.wdf.sap.corp/H/<sid>tdc00.wdf.sap.corp and SystemNumber into the corresponding fields.

6. Enter SAP Usernam, Password, and Language.

7. Click Update.

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

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



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 authenticationcompletely. (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 systemdisabled [seconds]

Use these fields together to configure how BusinessObjects Enterprisehandles SAP entitlement systems that are temporarily unavailable.BusinessObjects Enterprise uses these settings to determine when tostop communicating with an SAP system that is unavailable, and whenit should resume communication with that system.

In the “Max failed entitlement system accesses” field, type the numberof times that BusinessObjects Enterprise should re-attempt contactingan SAP system to fulfil authentication requests. Setting the value to -1allows BusinessObjects Enterprise to attempt to contact the entitlement




system an unlimited number of times before ceasing. Setting the valueto 0 limits BusinessObjects Enterprise to making one attempt to contactthe entitlement system.

In the “Keep entitlement system disabled [seconds]” field, type thenumber of seconds that BusinessObjects Enterprise should wait beforeresuming attempts to authenticate users against the SAP system.

For example, if you type 3 for “Max failed entitlement systemaccesses”, BusinessObjects Enterprise allows a maximum of 3 failedattempts to authenticate users against any particular SAP system; thefourth failed attempt results in BusinessObjects Enterprise ceasing itsattempts to authenticate users against that system for the amount oftime specified by “Keep entitlement system disabled [seconds].”

• Max concurrent connections per system

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

• Number of uses per connection

Use this field to specify how many logons you want to allow to theSAP system per connection.

For example, if you specified 2 for “Max concurrent connections persystem” and 3 for “Number of uses per connection”, once there hasbeen 3 uses on one connection, BusinessObjects Enterprise will closethat connection and restart it.

Note: Number of uses refers to actual transactions (or RFCcalls) towards the SAP system.

• Content folder root

Use this field to specify where you want BusinessObjects Enterprise tobegin replicating the BW folder structure in the CMC and InfoView. Tochange this value, you must change it both in the CMC and the ContentAdministration Workbench. This value is relevant for the publishingintegration with Crystal Reports.

• Automatically import users

Select this check box if you want BusinessObjects Enterprise tocreate user accounts and user folders for all role members when youactually import the roles. Clear the check box to have BusinessObjectsEnterprise create user accounts and user folders dynamically, whenusers 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 useconcurrent user licenses or named user licenses.

• Default system

In this list, select the SAP entitlement system that BusinessObjectsEnterprise uses as the default system (that is, the system that iscontacted to authenticate users who attempt to log on with SAPcredentials but without specifying a particular SAP system).

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

6. Select the check box Automatically import users and click Update.

Import SAP users and rolesBy importing SAP roles into BusinessObjects Enterprise, you allow role membersto log onto BusinessObjects Enterprise with their usual SAP credentials. Inaddition, single-sign-on is enabled so that SAP users can be logged ontoBusinessObjects Enterprise automatically when they access reports from withinthe 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 canalso use these groups to define object security within BusinessObjects Enterprise



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, usersthat are members of these SAP roles are able to log on with theirSAP account to BusinessObjects Enterprise.

Note: The roles that have been imported to BusinessObjectsEnterprise are now available for publishing Crystal Report objects.

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 roleyou imported from SAP under Groups.



Exercise 1: Logging onto the systems

Exercise ObjectivesAfter 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 ExampleBefore 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 Logon1. Launch SAP Logon from your computer.

Task 2: Logging into the SAP ERP/ECC system1. 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 isINITIAL)

Language EN

Task 3: Logging into the SAP BW system1. Use your SAP logon to access the provided SAP BW system.

2. Logging into the SAP BW system using the following information:




Field Name Value

Client 900



Language EN

Task 4: Logging into the BusinessObjects EnterpriseJava Infoview using SAP authentication1. 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 EnterpriseJava Infoview as administrator using Enterpriseauthentication1. Launch BusinessObjects Enterprise Java Infoview.


Field Name Value

User Name: administrator

Password <Given by the instructor>

Authentication Enterprise



Solution 1: Logging onto the systemsTask 1: Adding SAP systems to your SAP Logon1. 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 system1. Use your SAP logon to access the provided SAP ECC/ERP system.


b) Double-click the assigned SID.

2. Logging into the SAP ERP/ECC system using the following information:

Field Name Value

Client 800



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 isyour first attempt to log into the system.

b) Enter your new password and remember this password for futurereference.




Task 3: Logging into the SAP BW system1. Use your SAP logon to access the provided SAP BW system.


b) Double-click the assigned SID.

2. Logging into the SAP BW system using the following information:

Field Name Value

Client 900



Language EN

a) Logging into the SAP BW system using the given information.

Note: You will be prompted to change the password if this isyour first attempt to log into the system.

b) Enter your new password and remember this password for futurereference.

Task 4: Logging into the BusinessObjects EnterpriseJava Infoview using SAP authentication1. Launch BusinessObjects Enterprise Java Infoview.

a) Choose Start → Programs → BusinessObjects XI 3.1 →BusinessObjects Enterprise Client Tools → BusinessObjects EnterpriseJava InfoView..


Field Name Value

SAP System: Assigned system ID

SAP Client: 900




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 EnterpriseJava Infoview as administrator using Enterpriseauthentication1. Launch BusinessObjects Enterprise Java Infoview.

a) Choose Start → Programs → BusinessObjects XI 3.1 →BusinessObjects Enterprise Client Tools → BusinessObjects EnterpriseJava InfoView..


Field Name Value

User Name: administrator

Password <Given by the instructor>


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



Lesson Summary

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


BO100 Lesson: Publishing Integration for Crystal Reports

Lesson: Publishing Integration for Crystal Reports

Lesson OverviewIn this lesson, you will learn how to configure the publishing integration betweenBusinessObjects Enterprise and the SAP server.


• 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 ExampleYou are the system administrator and need to configure the publishing integrationbetween BusinessObjects Enterprise and the SAP server.

Describing the publishing processThis image outlines the publishing process:



Figure 31: Publishing process

• When a user attempts to publish one or more Crystal reports, BW looks for aRemote Function Call (RFC) destination (of type TCP/IP) that is configuredto connect to this BW Publisher. The TCP/IP destination provides SAP BWwith the name and port number of the SAP Gateway that the BW Publisher isregistered with.

• SAP BW then communicates over TCP/IP with the BW Publisher, and sendsthe following information across the network:

– The appropriate Crystal report file(s), with any required translatedreport 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, therebyinvoking the BW Publisher. The BW Publisher logs onto the specified CMSas the user, and checks to see if the user has the appropriate permissionsin BusinessObjects Enterprise to publish reports. If the user’s rights aresufficient, the CMS allows the reports to be added to the system.

Note: Before beginning to publish, you must configure SAPauthentication in BusinessObjects Enterprise, define a folderstructure for your content, and import SAP roles.

• When publishing a report from Crystal Reports the report is publishedwith the configured preferred viewing language as master-language.Master-language in this case means that the string values from this report arestored in SAP translation tables with the configured language set as sourcelanguage for the translation process.

• For each language selected in the content administration workbench forthe BusinessObjects Enterprise system there will be an additional reportfile created with the language code (one digit letter) as the first digit of thetechnical report name.

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 fromSAP BW during the publishing process:

• The Folder “SID” is replaced with the logical system name consisting of theSAP System ID and the SAP Client Number (for example, R37CLNT800).

• The role folder is created based on the technical name and description of therole that has been used to store the Crystal Report object on the SAP BWsystem.

• 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 serviceThe 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\BWPublisher Service

Figure 33: Registry



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\Suite12.0\SAP\BW Publisher Service

6. Configure the values for the BW Publisher service.

• Program ID: Type a descriptive string to identify the BW Publisherservice. The Program ID can take any value, but must be 64 charactersor fewer, and may not contain spaces. The Program ID is case-sensitive.

• Gateway Host: Type the name of your BW server. If you have a BWcluster, enter the name of the central instance of BW.

• Gateway Service: Type the port number that the Gateway Host islistening on. For example, type 33##, where ## represents the instancenumber of your SAP Gateway. Usually, the instance number is 00,and the value for this field is 3300.

7. Close the registry editor.

8. Start the Central Configuration Manager.

9. Select the BW Publisher Service.

10. Click Start.

Note: To check that the BW Publisher has started on Windowsensure that the bwcepubsvc.exe and bcepub.exe processes arerunning on the machine

Creating an RFC destinationTo enable the BW Publisher, you must configure an RFC destination on your BWserver 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 BWas 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 foreach BusinessObjects Enterprise system. You must use unique Program IDs foreach destination, but the same Gateway Host and Gateway service.



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.

Figure 35: RFC destination

4. Enter a name for the RFC destination.

5. Select TCP/IP as connection type.

6. Enter a description for the RFC destination.




7. Click Save.

8. Select Registered Server Program as Application Type.

9. Enter the Program ID that was configured for the BW Publisher serviceas Program ID.

Note: The Program ID name is case-sensitive.

10. Enter the Gateway Options:

• Gateway host: Type the name of your BW server. If you have a BWcluster, enter the name of the central instance of BW. You must use thesame BW server name here that you specified when you configuredthe BW Publisher service.

• Gateway service: Type the port number that the Gateway host islistening on. For example, type sapgw##, where ## represents theinstance number of your SAP Gateway. Often, the instance number is00, and the value for this field is sapgw00.

11. Click Save.

Creating a BusinessObjects Enterprise serverdefinitionYou must create a system definition within the Content Administration Workbenchfor each BusinessObjects Enterprise system to which you want to publish reportsto. The BusinessObjects Enterprise system definition combines the previousconfiguration steps with additional settings like user roles and languages.



To create a new BusinessObjects Enterprise serverdefinition


2. Start transaction /CRYSTAL/RPTADMIN (Content AdministrationWorkbench).

Figure 36: Content Administration Workbench

3. Double-click Add new system.

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 yourBusinessObjects Enterprise Central Management Service. If you configuredyour CMS to listen on a port other than the default, type in the details inthe following syntax:

CMSNAME: PORT.

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

7. Navigate to the RFC Destinations tab.

Figure 38: RFC Destination tab

8. Click Insert Row to add the RFC Destination for the BusinessObjectsEnterprise system that was created previously.

9. Select the RFC Destination created previously from the list of availableRFC destinations.

10. Click Verify CE Definition.

Note: This test verifies that BW can communicate to the specifiedBW Publisher, and can log onto the BusinessObjects Enterprisesystem.

11. Navigate to the HTTP tab.




Figure 39: HTTP tab

12. Provide the details for the BusinessObjects Enterprise system:

• Protocol: Type http (unless the web server that is connected toBusinessObjects Enterprise is configured to use https).

• Web server host and port: Type the fully qualified domain nameor the IP address of the web server that hosts your BusinessObjectsEnterprise InfoView or custom web application.

• Path: This path is essentially the virtual path that your web server useswhen referring to the SAP subfolder of your BusinessObjects Enterpriseweb content (or the path to any customer web application). Do notinclude 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.

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

• Select a language in the table and click Delete Row to remove alanguage.

• Click Insert Row to add a language.

15. Click the Roles tab.




Figure 40: Roles tab

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.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 beenassigned to existing BusinessObjects Enterprise systems.

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

17. Click the Layout tab.




Figure 41: Layout tab

18. Define the default security settings and base folder for publishing.

Note: Publishing Crystal Report objects from SAP BW toBusinessObjects Enterprise results in a report object and in a folderstructure replicating the SAP role structure on the BusinessObjectsEnterprise system.

19. Click OK (F8).

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



To set the SAP source parameters


2. Start transaction /CRYSTAL/RPTADMIN (Content AdministrationWorkbench).


3. Navigate to the SAP System settings in the Publish reports area.

4. Open the folder of SAP System Settings.

5. Double-click Set BW source parameter.

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.

Figure 44: New Entries

8. Set the correct values for the SAP server.

9. Click Save.

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



To configure the SAP HTTP request handler


2. Start transaction SICF (Maintain services).

Figure 45: Maintain service

3. Open the folder default_host.

4. Open the folder SAP.

5. Open the folder bw

Figure 46: Maintain service

6. Double-click service ce_url.

7. Navigate to the Handler List tab.




8. Click Change.

9. Ensure the top entry is /CRYSTAL/CL_BW_HTTP_HANDLER.

10. In case the entry is not the top entry the Insert Row and Delete Row optionscan be used to add/remove items.

11. Click Save.

12. Close the window.

13. Log off from the SAP server.

BusinessObjects security configuration for publishingBased on the described details for the publishing process, consider three maincategories of users when configuring BusinessObjects Enterprise for publishing,and when importing roles to BusinessObjects Enterprise:

• BusinessObjects Enterprise administrators: Enterprise administratorsconfigure the BusinessObjects Enterprise system for publishing content fromSAP. They import the appropriate roles, create necessary folders, and assignrights to those roles and folders in BusinessObjects Enterprise.

• Content publishers: Content publishers are those users who have rights topublish content into roles. The purpose of this category of user is to separateregular 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 theroles they are members of. However, regular role members cannot publishnew content, nor can they publish updated versions of content.

Note: You must import all content publishing and all content bearingroles to BusinessObjects Enterprise prior to publishing for the firsttime.

It is strongly recommended that you keep the activities of roles distinct. Forexample, while it is possible to publish from an administrator role, it is betterpractice to publish only from content publisher roles. Additionally, the function ofcontent publishing roles is only to define which users can publish content. Thus,content publishing roles should not contain any content. Content publishers shouldpublish to content bearing roles that are accessible to regular role members.

The following are recommendations for the previously described BusinessObjectsuser groups:



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

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

Content PublisherAssign 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 SAPsystem level and should only be assigned to a role that focuses onpublishing reports from SAP BW to BusinessObjects Enterprise.



To configure the rights in the Content AdministrationWorkbench

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.



To configure the rights in the Central ManagementConsole

1. . Log onto the Central Management Console.

2. Navigate to the Folders.

3. Navigate to the SAP System ID folder.

4. . Select the folder.

5. Select the menu Manage > Security > 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 memberof this SAP role are able to publish content to any of the SAP rolesfor the selected SAP system.



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


Unit Summary BO100

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



Test Your Knowledge

1. Where do you need to install BusinessObjects XI Integration for SAPSolutions for if you want to refresh a LiveOffice document based on CrystalReport using SAP data?Choose the correct answer(s).□ A Install where the Crystal Reports Job Server is running□ B Install where the Crystal Reports Cache Server is running□ C Install where the Crystal Reports Processing Server is running

(CORRECT)□ D Install on the Client PC

2. How do you add SAP users to BusinessObjects Enterprise?Choose the correct answer(s).□ A Add the SAP Users using the SAP authentication tab□ B Add the SAP Roles using the SAP authentication tab□ C Add the SAP Groups using the SAP authentication tab□ D Add the SAP Profiles using the SAP authentication tab

3. Which component needs to be installed and configured to allow CrystalReports to be uploaded to SAP and BusinessObjects Enterprise?Choose the correct answer(s).□ A SAP Publisher□ B BW Publisher□ C SAP Request Handler□ D BW Request Handler



Answers

1. Where do you need to install BusinessObjects XI Integration for SAPSolutions for if you want to refresh a LiveOffice document based on CrystalReport using SAP data?

Answer: 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 CrystalReports to be uploaded to SAP and BusinessObjects Enterprise?

Answer: B



Unit 4Query and Adhoc Reporting with Web

Intelligence on BW

Unit OverviewWeb Intelligence is one of a broad collection of tools offered in the SAPBusinessObjects Enterprise platform that provides a solution for creating,analyzing and distributing data stored in organizations data banks. In this unit wewill review query and adhoc reporting capabilities, and the tools best suited for thejob and compare these to the BEx suite in SAP NetWeaver BW.


• 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 ContentsLesson: Query and Adhoc Reporting ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Lesson: Web Intelligence and SAP Business Explorer .. . . . . . . . . . . . . . . . . . .121

Exercise 2: Creating an OLAP Universe from a BEx Query ... . . . . . . .133


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

Lesson: Query and Adhoc Reporting

Lesson OverviewIn this lesson we will describe query and adhoc reporting, which tool in theBusinessObjects Enterprise platform is best suited for query and adhoc reportingand explain when each tool should be used.


• 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 ExampleYou are planning to implement a BusinessObjects Enterprise solution integratedwith SAP NetWeaver BW and would like classify and position the variousBusinessObjects reporting tools in your environment where business users requirefull information autonomy.

Query and Adhoc reportingAn Adhoc Query is a query that cannot be determined prior to the moment thequery is issued. It is created in order to get information when need arises and itconsists of dynamically constructed SQL / MDX which is usually constructedby desktop / web resident query tools. This is in contrast to any query whichis predefined and performed routinely.

BusinessObjects Platform suite components for reporting include:

• Crystal Reports• Desktop Intelligence• Web Intelligence• Voyager• Xcelsius• Live Office


BO100 Lesson: Query and Adhoc Reporting

Figure 48: How Business Objects Tools Expand the Scope of BW

Note: Desktop Intelligence functionality is being replaced by WebIntelligence and Web Intelligence Rich Client

These tools are suited for various user audiences and business solutions


Crystal Reports Most business users Static reporting, highlyformatted reports, pixelperfect presentation,mass printing anddistribution, relationaldatabases, enterpriseapplications and datawarehouse sourced data

Web Intelligence Most casual businessusers

Powerful query and easeof use adhoc reporting,self serve templatebased report creationand interactive analysis,enterprise distribution,with mostly relationaland OLAP sourced data

Voyager Analyst and businessuser

Multi dimensionalanalysis of information




Xcelsius Most business users Dashboard andpresentation qualityvisualizations

Live Office Analyst and casual users Seamless MS Officeintegration with dataretrieval, presentationand distribution

BusinessObjectsExplorer

Business users and casualusers Increase BI Adoption

Understand your datawithout knowing thestructure.

Simple and intuitiveinterface allowsnon-power user to getanswers to their ownquestions.

Charts and relevant dataautomatically providedto user.

Get new insight intoyour data through newdata search and guidednavigation paradigms.High end user value at alow IT cost.

Figure 49: Baseline use cases and product mapping

As business users roles change during their business life from day to day, thetype and appetite for information consumption also changes. A single userfor this reason may consume data from different tools sets depending on theirrequirements.

A cost center manager may consume a highly formatted report with exceptionson cost items that exceeded budget for the month as a Crystal Report exported toExcel attached in email.

A brand manager may require advertising spend by campaign linked to sales forthe month to determine marketing cost effectiveness using Web Intelligence tocombine data from two different sub-systems; marketing and sales.

A product manager may want to analyze product category margins by locationacross market for this year and last year using Voyager.

A North American sales director is presenting to the board performancebased sales by region and product in the form of a dashboard and PowerPointpresentation using Xcelsius and Live Office.


BO100 Lesson: Query and Adhoc Reporting

The examples above demonstrate that there is a different solution based on userbusiness needs. Query and adhoc reporting is best satisfied by Web Intelligence.

Note: The component products will evolve and change as futurecomponents merge and are added within the BusinessObjects and SAPBW product platforms. For example Voyager will transform into Pioneerbecoming a more powerful multi dimensional solution for power analysts.

Figure 50: Product mapping with solution capabilities



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


BO100 Lesson: Web Intelligence and SAP Business Explorer

Lesson: Web Intelligence and SAP Business Explorer

Lesson OverviewIn this lesson SAP Business Explorer (BEx) is brought in for discussion. Youwill learn the use cases for both Web Intelligence and BEx with examples ofhow they can co-exist.


• Explain when Web Intelligence and Business Explorer (BEx) should be used• Provide an example where Web Intelligence and BEx co-exist and



Business ExampleYou plan to implement Web Intelligence with SAP BW access as your queryand adhoc reporting solution. You need a comprehensive overview of how theyintegrate and complement each other. You need this information to understandthe relationship between BEx queries and universes.

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

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



You will notice that Business Explorer has the same capabilities as theBusinessObjects toolsets that needs further clarification. Business Explorerconsists 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

Figure 52: BEx Suite Cases Use Cases



When to use Web Intelligence and BExDetermining which tool to use between WEBI and BEX is taken as a use casebasis with business considerations in mind.

The flagship ad-hoc reporting and analysis product for casual business users isWeb Intelligence. Web Intelligence should be seen as a complementary toolto leverage outputs from the deeper analysis achieved in BEx Analyzer. Thefollowing list of user requirements is associated with selecting Web Intelligence asthe 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 Pioneeris released).

The following list of user requirements is associated with selecting BEx Analyzeras 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 requirementsfor both.



Describe Business Explorer queries.

Figure 53: InfoProvider to Business Explorer flow

All multidimensional reporting and analysis performed in the BEx suite of tools isbased on a query definition stored in the Meta Data Repository. Queries provideaccess to multidimensional information providers (InfoCubes), as well as flatinformation 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 havefilters on characteristic values or filters on key figure values (conditions) assignedto select a certain slice of information from the InfoProvider. They may beparameterized by query variables.

All characteristics, navigational attributes, and key figures available through anInfoProvider are available for use in the Query Designer. Upon selection ofan InfoProvider, the designer will see a list of metadata defining the followingelements:

Structures: These are collections of selections and formulas that providelayout criteria for a row or column that may be used by queries for a particularInfoProvider. Structures may contain a combination of key figures, characteristics,and formulas. A reusable structure is a particular, commonly used collection of keyfigures or characteristics stored in the Meta Data Repository for reuse in multiplequeries (for example, a plan/actual variance or a contribution margin schema).

Filters: Predefined filter criteria for the whole query that may be reused in allqueries for a particular InfoProvider. A filter may contain any combination ofcharacteristics and their filter values. A filter specifies the size of the subcube, aswell as the initial navigation state displayed at query startup.



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. Acalculated key figure is a formula consisting of basic, restricted, or other calculatedkey figures available in the InfoProvider stored in the Meta Data Repository forreuse in multiple queries (for example, an average discount rate). A restricted keyfigure has an associated filter on certain characteristic values stored in the MetaData Repository for reuse in multiple queries (for example, year to date (YTD)sales of the previous year). A query consists of metadata elements arranged inrows, columns, and free characteristics.

Dimensions: Dimensions refer to the grouping of characteristic InfoObjects inInfoCubes.

A number of query elements that reach another level have an important place as itrelates 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 WebIntelligence (via universes)BW Queries are recommended as data sources for generating Business Objectsuniverses for the following reasons:

1. Not all BW metadata features can be retrieved on an InfoCube level, assummarized in the following table.

Note:

SAP BWMetadata Feature SAP OLAP BAPI supportlevel

Characteristics (incl. Time andUnit)

InfoCube/BW Query

Hierarchies InfoCube/BW Query

Basic Key Figures InfoCube/BW Query

Navigational Attributes BW Query only

Display Attributes InfoCube/BW Query

Calculated Key Figures /Formulas

BW Query only



SAP BWMetadata Feature SAP OLAP BAPI supportlevel

Restricted Key Figures BW Query only

Custom Structures BW Query only

Variables BW Query only

2. BW Queries offer a flexible extension to the data modeling environment.InfoCubes require more effort to change.

3. BW Queries offer significant functionality to create customized data sourcesthat meet end-user requirements.

4. When Web Intelligence is the front-end tool, you are not restricted by theoutput format in the BW Query.

5. There is no direct impact on performance when working with OLAPuniverses created from large BW Queries. OLAP universe objects notinserted in the Web Intelligence query have no direct impact on the queryperformance.

Note: The recommendations is to design as few BEx queries as possibleto satisfy a particular subject area thus minimizing the number of universethat needs to designed and maintained.

How SAP BW objects are mapped and used in auniverse

Figure 54: Mapping SAP BW and Business Objects



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

Hierarchies are mapped, allowing Web Intelligence users to drill down accordingto 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.

BI object Universe objects created

Dimension Group Class

Characteristic Subclass with dimension and detailobjects

Characteristic with hierarchy If data source is a BEx Query:Subclass containing dimension anddetail objects for each hierarchy levelin the currently defined hierarchy.

If data source is an InfoCube:Subclasses containing dimension anddetail objects for each hierarchy levelfor all hierarchies defined for thecharacteristic.

Structure based on Characteristics(BEx Queries only)

Class with single dimension object forthe structure

Navigational attribute Subclass with dimension and detailobjects (identical to characteristic)

Display Attribute Detail object for the dimension

Key Figure Structure Class

Key Figure Measure object in the class for theKey Figure structure with dimensionobjects for units/currency

Calculated Key Figure (BEx Queriesonly)

Measure and dimension objects (sameas Key Figure)



BI object Universe objects created

Restricted Key Figure (BEx Queriesonly)

Measure and dimension objects (sameas Key Figure)

Variables (BEx Queries only) Filter mandatory in query In theclass for the dimension to whichthe variable applies, two dimensionobjects supporting the list of values,one for caption, one for description.

Key date variable (BEx Queries only) Universe parameters defining key datevariable 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 filteris applied transparently when running the Web Intelligence query. If thecharacteristic has a variable defined, the variable is mapped with these limitations:

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

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

How BW characteristics and mapped and used in theuniverse• When no hierarchy is defined on the characteristic in the BEx Query or

InfoCube, Designer creates a class containing the characteristic as twodimension objects: Level 00 and Level 01. - The Level 00 dimensionrepresents the aggregation of the characteristic when all members areselected (the member returned from BI is All members). The Level 01dimension 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 longdescriptions), and a detail object for each display attribute.

• Navigational attributes leveraged in the BEx Query are mapped in the parentobject class in the same way as characteristics are mapped.

Note: A large number of navigational attributes defined in the underlyingInfoProvider negatively impacts the overall performance (please referback to SAP Best Practices for Data Modelling). Structures defined



in the BEx Query that are based on characteristics are included in theuniverse as single-dimension objects with the elements of the structure asdimension members.

Note: Objects in the universe can be renamed using the Universe API. ForExample, objects with L00 in the name can be hidden and L01 objects canhave the L00 in the named removed. An Excel macro can be used to speedup this processed and customize it based on customers requirements.

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

• A measure object with the numeric value corresponding to the key figurewithout 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 andthe unit (formatted value) based on user preferences configured on the SAPserver. For example, '200 USD', '345 €', '25 km'.

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

Note: Having a large number of key figures in the BEx query willcurrently incur a significant performance penalty when running queriesusing Universe data access. This is regardless of whether the key figuresare included in the Universe or used in the WebI query. It is thereforesuggested to have only those key figures intended to be used for reportingincluded in the BEx query definition. This performance impact is due totime spent loading metadata for units, which is currently executed forall measures in the query. A fix for this issue may become available inthe future.

How SAP BW hierarchies are mapped and used in auniverseHierarchies are mapped to allow Web Intelligence users to drill down with SAPBW hierarchies in the same way as custom-made universe hierarchies.

The Use Query Drill option in the Web Intelligence Document Properties dialogbox significantly improves drill down performance.



When a hierarchy is defined on a characteristic in the BW Query, Designer createsone hierarchical structure in the universe, with a subclass for each level in thehierarchy. The structure depends on the current BW Query definition:

• If a hierarchy is defined in the BW Query, Designer creates this hierarchystructure in the universe.

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

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

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 dimensioncontains all top nodes as a list of values. When the hierarchy attribute is set to notfilter unassigned nodes, it is necessary to include Level 00 with the top nodefor unassigned members. Unassigned members are grouped at the lowest levelof the hierarchy.

Note: When a Characteristic has no active Hierarchy, the “L00” node willbe All Members, and will not provide any reporting value. In this case, itis best to delete all “L00” objects in order to reduce complexity for thereport designing users (i.e., report developers). Even in cases where anactive Hierarchy does exist, the “L00” objects may be unnecessary. Incases where there is only one top-level root of the Hierarchy, it may bedesirable to remove the “L00” object for a Hierarchy, unless it is necessaryto report members which are not assigned in the Hierarchy

How SAP BW variables are mapped and used in auniverseSAP 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. Variablesare populated with values when a query is executed. They can store characteristicvalues, hierarchies, hierarchy nodes, texts, and formula elements.

Note: BW variables apply to BW Queries only.



The following types of SAP BW variables are supported in universes:

• Characteristic variables• Hierarchy variables• Hierarchy node variables• Currency variables• Formula variables• Text variables (as replacement path 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.

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

Pre-calculated value set Not supported

Formula Price, quota, and numeric valuessupportedHierarchy Supported except for version variable

Hierarchy node Supported





Exercise 2: Creating an OLAP Universefrom a BEx Query

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create an initial BEx query and OLAP universe for further updates

Business ExampleAs a Universe Designer you are required to make changes to the universe toenhance adhoc reporting capabilities

Task:Create an initial BEx query which will be used for further updates in otherexercises

1. Use BEx Query designer and create a basic Query from InfoProviderT_BO1001, select “Sold_to party” and “Fiscal year/period” as rows or freecharacteristics and key figures “Incoming Orders” and “Invoiced quantity”as columns

Note:

Field Name Value

System Assigned system (for example:<SID>)

Client 900

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

Password Assigned password

Language Desired language key (forexample: 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.




5. Create new connection and new universe from above query asT_BO100_QLCM_001_##, where ## is your group number

Note:

Field Name Value

User Assigned user


Client 900

Language Desired language key

ApplicationServer

/H/tdc-saprouter.wdf.sap.corp/H/<SID>tdc00.wdf.sap.corp

System number 50

System ID Assigned system ID

6. Configure universe parameters with summary information and no controllimits

7. Save and export universe

8. Create a Web Intelligence rich client document, save and export to BOEEnterprise (CMS). Use name T_BO100_QLCM_001_##, where ## is yougroup number



Solution 2: Creating an OLAP Universefrom a BEx QueryTask:Create an initial BEx query which will be used for further updates in otherexercises

1. Use BEx Query designer and create a basic Query from InfoProviderT_BO1001, select “Sold_to party” and “Fiscal year/period” as rows or freecharacteristics and key figures “Incoming Orders” and “Invoiced quantity”as columns

Note:

Field Name Value

System Assigned system (for example:<SID>)

Client 900

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


Language Desired language key (forexample: EN)

a) Start Query Designer

• Go to Start ->All Programs -> Business Explorer -> QueryDesigner

• Select System = <SID>, 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




• Expand Time dimension and select Fiscal year/period and dropin Rows area

Figure 55: Initial Query Design

2. Make sure that query is released for external access

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

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

a) From the menu toolbar, select check query and confirm the queryis 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

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




5. Create new connection and new universe from above query asT_BO100_QLCM_001_##, where ## is your group number

Note:

Field Name Value

User Assigned user


Client 900


ApplicationServer

/H/tdc-saprouter.wdf.sap.corp/H/<SID>tdc00.wdf.sap.corp

System number 50


a)

Note: Cancel quick design wizard if necessary

Select Menu File -> New. Select New button under connection, ClickNext in the new connection Wizard window. Ensure Connection Typeis "Secured". Type "T_BO100_QLCM_001_##" in connection Name.Select SAP, then expand to SAP Business Warehouse then expand toSAP 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: = xxxxxxClient: = 900Language: = ENLogin Mode: = Application Server / Message Server (use Applicationserver)Application Server:: = /H/tdc-saprouter.wdf.sap.corp/H/<SID>tdc00.wdf.sap.corp (for applicationserver only)System Number: = 50 (for application server only)System ID: = <SID>Logon Group: = OPEN (for message server only)Message server: = <SID> (for message server only)Click Next In the Catalog / database parameters window, type in queryname T_BO100_QLCM_001_## next to search button,click search. Click next when query is found.




Keep defaults as shown in the Configuration parameters. Click finish

Figure 56: Connection Login Parameters




6. Configure universe parameters with summary information and no controllimits

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 operationsin query panel.”Click OK

Figure 57: Initial Universe Generation





a) Save universe as "T_BO100_QLCM_001_##" to the default localfolder. Folder name when universe is new is .../Universe...

b) From menu Select File -> Export, click OK when prompted to saveif not already saved, Click Browse for domain and select CMSfolder T_BO100_LCM. If folder does not exist then select rootfolder then select Insert New Folder button and create a folder calledT_BO100_LCM_## (## is your group number). Click OK to completethe export process.

Figure 58: Export Universe to BusinessObjects CMS

c) Exit Universe designer. Select File → Exit

8. Create a Web Intelligence rich client document, save and export to BOEEnterprise (CMS). Use name T_BO100_QLCM_001_##, where ## is yougroup number

a) Go to Start → Programs → BusinessObjects XI 3.1 → BusinessObjectsEnterprise Client Tools → Web Intelligence Rich Client.

b) Enter login Information and press logon.System: TWDFXXXXUser Name: BO100-##Password: Assigned password

c) From Menu bar select File → New, on New Document window selectUniverse. Press Next>>




d) Select universe T_BO100_QLCM_001_##, In the Create Querywindow, expand all folders and select Incoming Orders, L01 Sold-toparty and L01 Fiscal year/period. Press run query.

Figure 59: Web Intelligence Query Creation

Figure 60: Web intelligence Document after Refresh Query

e) Save document to local drive and export to CMS. From Menu bar selectFile → 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 folderT_BO100_LCM_##. Press Export. Click close and exit rich client.Select File → Exit.

Note: If folder does not exist, then create the folder by focusingon the Public Folder, then press the Create New Folder Button,Type in new folder T_BO100_LCM_##.



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




Unit Summary BO100

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





Test Your Knowledge

1. Help desk management would like to empower a team to create ad-hocreports against BW data. Objects/dimensions, key figures/measures andSLAs have been defined. A simple clear, business view of these dataobjects needs to be provided to design simple on the fly charting and gridreports to meet their operational team needs. The volume of help desk databeing analyzed is daily, weekly and monthly. Which SAP BusinessObjectsreporting tool would be the most appropriate to use?Choose the correct answer(s).□ A Web Intelligence on OLAP Universe□ B Crystal Reports on OLAP Universe□ C Crystal Reports on BW Queries□ D Voyager and/or SAP Business Explorer (BEx)



Answers

1. Help desk management would like to empower a team to create ad-hocreports against BW data. Objects/dimensions, key figures/measures andSLAs have been defined. A simple clear, business view of these dataobjects needs to be provided to design simple on the fly charting and gridreports to meet their operational team needs. The volume of help desk databeing analyzed is daily, weekly and monthly. Which SAP BusinessObjectsreporting tool would be the most appropriate to use?

Answer: A

Web Intelligence on OLAP Universe is correct.


Unit 5OLAP Universes on SAP BW - Part 1

Unit OverviewThis unit provides you with an overview of SAP variables and how these are usedin OLAP Universes and Web Intelligence.


• 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 ContentsLesson: BW Variables... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Exercise 3: Creating a new OLAP Universe with optional variables.153Lesson: Mandatory variables... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Exercise 4: Creating a new OLAP Universe with mandatoryvariables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

Lesson: SAP variables with default values ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168


Unit 5: OLAP Universes on SAP BW - Part 1 BO100

Exercise 5: Creating a new OLAP Universe with default valuevariables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Lesson: SAP variables with delegated search ... . . . . . . . . . . . . . . . . . . . . . . . . . . .176Exercise 6: Creating a new OLAP universe with variables usingdelegated search ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Lesson: Hierarchies in OLAP Universes... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183Lesson: Hierarchies and hierarchy node variables in OLAP Universes .185

Exercise 7: Creating a new OLAP Universe with hierarchy andhierarchy node variables... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Lesson: Simple keydate scenarios .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Procedure: To create a new Universe with a keydate variable .. . . . .198Procedure: To use a keydate variable in Web Intelligence ... . . . . . . . .199

Lesson: Keydate variable dependencies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202


BO100 Lesson: BW Variables

Lesson: BW Variables

Lesson OverviewIn this lesson you will learn how to create an OLAP Universe using optional SAPVariables 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 ExampleBefore you begin universe creation from SAP BW system, you need to createa connection between SAP BW and the BusinessObjects System . The basicprinciples by building a Universe between the SAP BW and BusinessObjects is togenerate the interface between both systems and to map the characteristic and keyfigures of SAP BW into a universe so that they can be used by BusinessObjectsfor reporting. In this example you will create the universe based on an SAPquery with a variable.

BW VariablesSAP Variables can be interpreted as user prompts defined in the BEx Query.Variables can be mandatory or optional, and can have default values. Variablesfor Characteristics are used to filter values for a Characteristic. Variables arepopulated with values when a query is executed. They can store Characteristicvalues, Hierarchies, Hierarchy Nodes, Text, and Formula elements. BW Variablesapply to BEx Queries only. The following types of BW Variables are supportedin 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 a detailed list of the Variable Type "User Entry /Default Value" only and how those are leveraged in a Universe. User Entryvariables can be mandatory or optional, and can have default values. Optional



Variables are defined as optional filters in the Universe, and become optionalprompts in Web Intelligence. Mandatory Variables become mandatory prompts inWeb Intelligence.

Note: A mandatory filter is hidden and cannot be selected in the QueryPanel in WebIntelligence.

Variables Type

Characteris-tic

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

VariablesType

Processing Type

User En-try/DefaultValue

Replace-ment path

Authoriza-tion

Customerexit

SAP exit

Character-istic

Supported Supported Supported Supported Supported

Text NotSupported

Supported N/A N/A N/A

Formula Supported Supported N/A Supported Supported

Hierarchy Supported N/A N/A Supported Supported

Hierarchynode

Supported N/A N/A Supported Supported



Creating OLAP Universes with optional promptsOptional variables in SAP BEx reporting tools are used to offer the capabilityto 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 SAPBW query uses a default value or a personalized variable value. When creatingan OLAP Universe on a BEx Query with optional variables, the variables areautomatically added as optional prompts. In Web Intelligence, when the optionalprompts are not used the result set is returned for all rows of data based on theWebI Query panel Results section (and NOT the BEx query definition).

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

Hint: To ensure the best possible performance, it is best to utilize SAPVariables to filter data returned from SAP BW. The other option wouldbe to just leverage filtering capability in the Web Intelligence QueryPanel Filter area – this would then add the filter criteria in the MDXstatement passed to BW. In situations where there is not an @Prompt orSAP Variable defined this will work, but the data selection is BW will beinefficient and queries may run much longer than if an SAP Variable hadbeen used. The difference in MDX terms is that the filter criteria will bepassed in nested CROSSJOINs within the ROWS returned, rather thanadding the filter to the WHERE clause of the MDX statement.

Figure 61: Optional Prompts





Exercise 3: Creating a new OLAP Universewith optional variables

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create an OLAP universe and Web Intelligence report with option variables

Business ExampleYour business reporting group requires optional prompts in Web Intelligencereports.

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 BusinessObjectsEnterprise system (for example:TWDFXXXX)

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


Authentication SAP

2.Note: Cancel the Quick Design Wizard.

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

Field Name Value

User Assigned user


Client 900





Field Name Value

Application Server /H/tdc-saprouter.wdf.sap.corp/H/<SID>tdc00.wdf.sap.corp

System number 50


3. Save the Universe to the BusinessObjects Universes folder with the nameT_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 themeasure Sales Volume EUR Formatted Value (in that order) and executeit to view the results.

7. Select different values for the optional prompt and run the report with aselection to see the results.

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



Solution 3: Creating a new OLAP Universewith optional variablesTask: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




Authentication SAP

a) Go to Start → Programs → BusinessObjects XI 3.1→ BusinessObjectsEnterprise 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’ (technicalname: T_BO1001/T_BO100_Q03_1).

Field Name Value

User Assigned user


Client 900





Field Name Value


System number 50


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 theSAP server details.

Note: The connection dialog allows you to select between anApplication server and a Message server connection.

i) Set the Authentication Mode to Use specified username andpassword.

j) Click Next.

k) Open the list of available cubes by clicking the plus sign next to OLAPCubes.

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.




3. Save the Universe to the BusinessObjects Universes folder with the nameT_BO100_Optional_Variable_##.

a) Select File → Save As.

b) Ensure the destination folder is set to BusinessObjects Universes, andensure the universe name is set to T_BO100_Optional_Variable_##.unv,then press Save.


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


a) Start InfoView. Select Start → Programs → BusinessObjects XI 3.1→BusinessObjects Enterprise Client Tools → BusinessObjects EnterpriseJava 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 WebIntelligence report.

i) Click Run Query.





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

b) Expand the node Material Class → Material02 and drag L01 Materialinto Result Objects panel to the right of L01 Sold to Party.

c) Expand the node Key Figures and drag the measure Sales VolumeEUR Formatted Value into the Result Objects panel to the right ofL01 Material.

d) Press Run Query.

Do not select any values when prompted. Press Run Query.

Note: An optional SAP variable now becomes an optionalprompt in Web Intelligence. When left empty the optionalprompt is removed from the actual WHERE clause that issent to the underlying system. In the SAP BW case an emptyoptional variable could still result in the usage of a configureddefault value from the underlying SAP Variable or in the usageof a personalized variable value of the user.

7. Select different values for the optional prompt and run the report with aselection 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.

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

a) Select File → Save As. Press Enterprise. Select SAP 2.0<SID>CLNT900. Enter the description GR## Sales Order Report withOptional Prompt.

b) Press Save.



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



Lesson: Mandatory variables

Lesson OverviewIn this lesson you will learn how to create an OLAP Universe using mandatorySAP Variables and leverage these as mandatory prompts in Web Intelligencereports.


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

Business ExampleYour business reporting group requires mandatory prompts in Web Intelligencereports to enforce data volume restrictions when querying against SAP BWInfoProviders.

Creating OLAP Universes with mandatory promptsMandatory variables in SAP BEx reporting tools are used to offer the capability toforce the user to be prompted for the entry of a data restriction. This will limitthe amount of data the user can return in any given query they execute. This isespecially important when the data volumes are very large – it is a best practice toenforce some variables/prompts to be entered in order to ensure the best possibleperformance. In BEx Analyzer / BEx Web, when an mandatory variable is usedin a BEx Query the user must make an entry otherwise they cannot submitthe query. When creating an OLAP Universe on a BEx Query with mandatoryvariables, the variables are automatically added as mandatory prompts. In WebIntelligence, when refreshing the data in the WebI report these prompts will beenforced as mandatory as well.



BO100 Lesson: Mandatory variables

Exercise 4: Creating a new OLAP Universewith mandatory variables

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create an OLAP universe and Web Intelligence report with mandatory

variables

Business ExampleYour business reporting group requires mandatory prompts in Web Intelligencereports to enforce data volume restrictions when querying against SAP BWInfoProviders.

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


Client 900



System number 50


3. Save the Universe to the BusinessObjects Universes folder with the nameT_BO100_Mandatory_Variable_##.







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

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



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


a) Go to Start > Programs > BusinessObjects XI 3.1 > BusinessObjectsEnterprise Client Tools

b) Click Designer.

c) Logon with your username and password when prompted.

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


Client 900





Field Name Value


System number 50


a)

Note: Cancel the Quick Design Wizard.

Click File > New.


c) Click Next.



f) Click Next.





j) Click Next.


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


n) Click Finish.

o) Enter a name for the Universe into the field Name.



r) Click OK.




3. Save the Universe to the BusinessObjects Universes folder with the nameT_BO100_Mandatory_Variable_##.


b) Ensure the destination folder is set to BusinessObjects Universes,and ensure the universe name is set to T_BO100_Mandatory_Vari-able_##.unv, then press Save.







a) Start InfoView Start → Programs → BusinessObjects XI 3.1 →BusinessObjects Enterprise Client Tools → BusinessObjects EnterpriseJava InfoView.



d) Click Log On.




h) Select the Dimensions and Measures you want to display in your WebIreport.

i) Click Run Query.





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

b) Expand the node Material Class → Material02 and drag L01 Materialinto Result Objects panel to the right of L01 Sold to Party.

c) Expand the node Key Figures and drag the measure Sales VolumeEUR Formatted Value into the Result Objects panel to the right ofL01 Material.

d) Press Run Query.

Note: A mandatory SAP variable now becomes a mandatoryprompt in Web Intelligence. You must select a value beforeexecuting the query.

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

a) Select values for the mandatory prompt.

b) Click Run Query.

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

a) Select File → Save As. Press Enterprise. Select SAP 2.0<SID>CLNT900. Enter the description GR## Sales Order Report withMandatory Prompt.

b) Press Save.



Lesson Summary

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



Lesson: SAP variables with default values

Lesson OverviewIn this lesson you will learn how to create an OLAP Universe using SAP Variableswhich have default values defined and see how these behave in Web Intelligencereports as prompts.


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

Business ExampleYour business reporting group requires prompts in Web Intelligence reports whichhave default values specified. This allows commonly used prompt values to bepredefined so users do not have to enter them every time they refresh data orcreate a new report.

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



BO100 Lesson: SAP variables with default values

Exercise 5: Creating a new OLAP Universewith default value variables

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create an OLAP universe and Web Intelligence report with variables that

have default values defined.

Business ExampleYour business reporting group requires prompts in Web Intelligence reports whichhave default values specified. This allows commonly used prompt values to bepredefined so users do not have to enter them every time they refresh data orcreate a new report.

Task:Create an OLAP universe and Web Intelligence report with variables that havedefault 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).

Field Name Value

User Assigned user


Client 900



System number 50


3. Save the Universe to the BusinessObjects Universes folder with the nameT_BO100_Default_Values_##.






6. Run the WebI refresh with the default values, or override them with youown selection.

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



Solution 5: Creating a new OLAP Universewith default value variablesTask:Create an OLAP universe and Web Intelligence report with variables that havedefault values defined.

1. 1. Start the Universe Designer.

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

b) Click Designer.


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


Client 900





Field Name Value


System number 50


a)

Note: Cancel the Quick Design Wizard.

Click File > New.


c) Click Next.



f) Click Next.





j) Click Next.


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


n) Click Finish.




r) Click OK.




3. Save the Universe to the BusinessObjects Universes folder with the nameT_BO100_Default_Values_##.


b) Ensure the destination folder is set to BusinessObjects Universes, andensure the universe name is set to T_BO100_Default_Values_##.unv,then press Save.







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



d) Click Log On.




h) Select the Dimensions and Measures you want to display in your WebIntelligence report.

i) Click Run Query.

Note: When executing a report with a default value forprompting the default value is suggested as a value for theprompt but can be removed or changed.

6. Run the WebI refresh with the default values, or override them with youown 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 variableand execute the query without any selected value, the defaultvalue will be used for data retrieval.




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

a) Select File → Save As. Press Enterprise. Select SAP 2.0<SID>CLNT900. Enter the description GR## Sales Order Report withDefault Values.

b) Press Save.



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



Lesson: SAP variables with delegated search

Lesson OverviewIn this lesson you will learn how to create an OLAP Universe using SAP Variableswhich 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 ExampleYour business reporting group requires prompts in Web Intelligence reports ondimensions that have a large number of distinct values. Immediately presentingall values to the user for selection would not be ideal from a usability perspectiveand for performance reasons. A feature in Designer allows prompts to delegatethe search of values to the database.

Creating OLAP Universes with variables withdelegated searchWhen utilizing prompts based on BEx Variables in an OLAP Universe, at runtimeWebI retrieves all distinct values for the prompt from BW. In situations wherethe 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 froma usability perspective. Rather than sorting through thousands of values, thedelegated search functionality will allow the user to search for the values theyare interested in filtering on.



BO100 Lesson: SAP variables with delegated search

Exercise 6: Creating a new OLAP universewith variables using delegated search

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create an OLAP universe and Web Intelligence report with delegated search

prompts

Business ExampleYour business reporting group requires prompts in Web Intelligence reports ondimensions that have a large number of distinct values. Immediately presentingall values to the user for selection would not be ideal from a usability perspectiveand for performance reasons. A feature in Designer allows prompts to delegatethe search of values to the database.

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


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.


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



Solution 6: Creating a new OLAP universewith variables using delegated searchTask:Create an OLAP universe and Web Intelligence report with delegated searchprompts


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

b) Click Designer.





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

a) Click File → New.


c) Click Next.



f) Click Next.




i) Set the Authentication Mode to Use Single Sign On when refreshingreports at view time.

Note: Using single-sign-on in combination with an SAPsystem requires the SAP authentication to be configuredfor the SAP system in the Central Management Console ofBusinessObjects Enterprise.

j) Click Next.


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


n) Click Finish.




r) Click OK.




3. Change the prompt to utilize delegated search.

a) Find the prompt for Sold To Party. The prompt you want to change isthe 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 theproperties for the prompt.

Figure 62: Delegate Search

d) Click OK.


a) Select the menu File > Export.

Note: The Universe needs to be saved before it can be exported.

b) Click Save.

c) Select a Domain.

d) Select the Groups that should be assigned to the Universe.

e) Click OK.

f) Click OK.





a) Start InfoView. Select Start → Programs → BusinessObjects XI 3.1 →BusinessObjects Enterprise Client Tools → BusinessObjects EnterpriseJava InfoView.



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




h) Select the Dimensions and Measures you want to display in your WebIreport.

i) Click Run Query.

6. 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 arrowicon to move it to the right side of the prompt.

c) Click Run Query.

Figure 63: Search Criteria



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


BO100 Lesson: Hierarchies in OLAP Universes

Lesson: Hierarchies in OLAP Universes

Lesson OverviewIn this lesson you will learn how to create an OLAP universe using SAPhierarchies and leverage these hierarchies in Web Intelligence reports.


• Create OLAP Universes with SAP hierarchies• Leverage hierarchies in Web Intelligence

Business ExampleYour business requires group data and use drill down capability in WebIntelligence report. You need to leverage SAP hierarchy into OLAP universe.

Create OLAP Universes with hierarchiesHierarchies are mapped to allow Web Intelligence users to drill down with SAPBW hierarchies in the same way as custom-made universe hierarchies.

When a hierarchy is defined on a characteristic in the BW query, Designer createsone hierarchical structure in the universe, with a subclass for each level in thehierarchy. The structure depends on the current BW query definition:

• If a hierarchy is defined in the BW query, Designer creates this hierarchystructure in the universe.

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

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



Lesson Summary

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


BO100 Lesson: Hierarchies and hierarchy node variables in OLAP Universes

Lesson: Hierarchies and hierarchy node variables inOLAP Universes

Lesson OverviewThis lesson provides you with an overview of SAP hierarchy and hierarchy nodevariable 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 ExampleYour business requires flexible reports with free selection of different SAPhierarchies of an InfoObject. You need to utilize SAP hierarchy and hierarchynode variable into OLAP Universe.

OLAP Universe with hierarchy variablesIn the case of a hierarchy variable in the underlying SAP BW query the universe iscreated with the maximum number of levels of all available hierarchies

Let’s assume the query has three available hierarchies:

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



In this scenario the Universe is generated with five levels for the characteristic.In the scenario where the user creates a report with all five available levels, butselects a hierarchy which does not include five levels, the undefined levels willstay empty in the report.

Note: “”Note 1007048 - MDX: Filtering of variables in the hierarchydisplay“” needs to be applied in BW to access Hierarchy Variablesvia universe. Without the note fix universe cannot read BEx hierarchyvariable directly. But universe can read hierarchy variable if the hierarchyvariable is attached with a hierarchy node variable. Limitation of thisworkaround is that every WebI report will have both hierarchy variableand hierarchy node variable. To show only the hierarchy variable in WebIreport, MDX of universe filter need to be modified manually.

Note: Depending on the hierarchy that was selected and the definedhierarchy structure on the SAP BW side some of the selected levels mightbe 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 valuehas more levels than the selected hierarchy in the run time, generatedMDX statement will cause error. This is a bug and will be fixed in laterrelease.

Figure 64: Hierarchy Variable Prompt in WebI report



OLAP Universe with hierarchy and hierarchy nodevariablesIn the case of a query with a hierarchy and hierarchy node variable the universe iscreated with the maximum number of levels possible for the hierarchy. For thehierarchy node variable a list of values is created representing each level of allavailable hierarchies.

Figure 65: Hierarchy Node Variable in Universe

When using a universe with a hierarchy and hierarchy node variable, WebIntelligence prompts for the hierarchy variable and then prompts for the hierarchynode variable.



Figure 66: Hierarchy Node Variable Prompt



Exercise 7: Creating a new OLAP Universewith hierarchy and hierarchy nodevariables

Exercise ObjectivesAfter 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 ExampleYou are a report designer and need to create a new OLAP universe with a hierarchyand a hierarchy node variable.

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


Field Name Value

System Assigned system (for example: TWDFXXXX)

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


Authentica-tion

SAP

2. Create a new OLAP Universe using the query BO100 hierarchy variableWorkaround (technical name: T_BO1001/ T_BO100_Q08_1_W).

Field Name Value



Client 900





Field Name Value

ApplicationServer

/H/tdcsaprouter. wdf.sap.corp/H/<SID>tdc00.wdf.sap.corp

Systemnumber

50




5. Select different possible combinations of Hierarchy and Hierarchy nodevalues.



Solution 7: Creating a new OLAP Universewith hierarchy and hierarchy nodevariablesTask:Create an OLAP universe and Web Intelligence report with hierarchy andhierarchy node variable.


Field Name Value

System Assigned system (for example: TWDFXXXX)



Authentica-tion

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

2. Create a new OLAP Universe using the query BO100 hierarchy variableWorkaround (technical name: T_BO1001/ T_BO100_Q08_1_W).

Field Name Value



Client 900


ApplicationServer

/H/tdcsaprouter. wdf.sap.corp/H/<SID>tdc00.wdf.sap.corp

Systemnumber

50



b) Click New to create a new connection.Continued on next page



c) Click Next.



f) Click Next.






j) Click Next.


l) Navigate to BO100 Cube and select BO100 hierarchy variableWorkaround(technical name: T_BO1001/ T_BO100_Q08_1_W)


n) Click Finish.




r) Click OK.




Figure 67: Generated Universe with Hierarchy variable andhierarchy node variable LOVs


a) Select the menu File > Export.

Note: The Universe needs to be saved before it can be exported.

b) Click Save.

c) Press the Browse button.

d) Highlight the folder webi universes then press OK.

e) Click OK to export the universe. The universe is now available forreporting.





a) Start InfoView (Start → Programs → BusinessObjects XI Release3.1 → BusinessObjects Enterprise Client Tools → BusinessObjectsEnterprise Java InfoView).



d) Click Log On.




h) Select all needed levels from the hierarchy and include them into theResult Objects.

Expand the node Material → Material2 and drag L01 Material intoResult Objects panel.

Repeat for L02 Material, L03 Material, and L04 Material.

i) Expand the node Key Figures and drag the measures Sales VolumeEUR into the Result Objects next to L04 Material.

j) Click Run Query.

5. Select different possible combinations of Hierarchy and Hierarchy nodevalues.

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




Figure 68: Hierarchy and Hierarchy node values

b) For the Product Hierarchy Node, expand Product Hierarchy formaterial MARA and select a hierarchy node from hierarchy nodevariable

Figure 69: Hierarchy and Hierarchy node variable

c) Click Run Query.

Figure 70: Run Query



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


BO100 Lesson: Simple keydate scenarios

Lesson: Simple keydate scenarios

Lesson OverviewIn this lesson, you will learn about the use of an SAP keydate variable in OLAPUniverses.


• Use keydate variables in OLAP Universes and Web Intelligence

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

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

• Keydate variables can influence the actual master-data that is retrieved fordimensions.For example: a product description can change over time.

• Keydate variables can influence the list of hierarchies that is available fora dimension.

• Keydate variables can influence a hierarchical structure.

For example : a specific cost center can be on level 1 of the hierarchy forthe Year 2004 but on level 02 for the year 2005.

The generation process for OLAP Universes does not allow the user to providea date for the keydate variable, which means the system date from the SAP BWserver will be used for creating the OLAP Universe.In a scenario where the OLAPUniverse is not generating enough levels for a hierarchy - which would mean theuser would not be able to see all levels of the hierarchy when creating a WebIntelligence 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 levelswill 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 intothe universe. The prompt based on the keydate variable is available in the querypanel to enable different options for this prompt.



To create a new Universe with a keydate variable


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 connectionname. Click Next to continue.

5. Enter the User name, Password, and Language.

6. Enter the Client, Application Server, and System Number based on the SAPserver details.


7. Set the Authentication Mode to Use Single Sign On when refreshing reportsat view time.

Note: Using single-sign-on in combination with an SAP systemrequires the SAP authentication to be configured for the SAP systemin the Central Management Console of BusinessObjects Enterprise.

8. Click Next.

9. Open the list of available cubes and navigate to the required cube. Selectthe 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. ClickOK.

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



To use a keydate variable in Web Intelligence

1. Start InfoView.

2. Select SAP as Authentication type.

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

4. Click Log On.

5. Click Document List.

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 71: Web Intelligence Document

9. Click Keydate Properties.




Figure 72: 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 reportsome rows might be combined into a "#MULTIVALUE" row.To avoid the situation you can change the "Avoid duplicate rowaggregation" 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.



Lesson Summary

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



Lesson: Keydate variable dependencies

Lesson OverviewIn this lesson you will learn about the dependencies of a keydate variable inOLAP Universes.


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

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

Keydate variable dependenciesIn the case where the underlying SAP BW query contains a keydate variable andother variables (like a hierarchy variable or a hierarchy node variable) the useris prompted twice and the value set for the keydate variable might influence thelist of values for the second variable.

Examples for such a scenario are:

• A hierarchy node variable in combination with a keydate variable, where thekeydate variable influences the hierarchical structure.

• A hierarchy variable in combination with a keydate variable, where thekeydate variable influences the list of available hierarchies.

Using keydate variable dependencies in WebIntelligenceWhen using a keydate variable in combination with other prompts the user willbe prompted for the keydate variable first so that any dependency based on thekeydate variable is set correctly.


BO100 Lesson: Keydate variable dependencies

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


Unit Summary BO100

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



Test Your Knowledge

1. Number of dimensions created under a class containing hierarchy dependson the level of hierarchy.Determine whether this statement is true or false.□ True□ False

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

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

4. Web Intelligence Report will present all available hierarchy node valuesfor all available hierarchies.Determine whether this statement is true or false.□ True□ False



Answers

1. Number of dimensions created under a class containing hierarchy dependson the level of hierarchy.

Answer: True

TRUE. For a hierarchy with 4 levels, L00 to L003 dimensions will be createdunder the universe class.

2. "Not assigned" items under level 0 includes all elements that have not beenassigned to actual hierarchy structure.

Answer: True

TRUE. In the case of hierarchies, a level 0 item called "not assigned" is usedto 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 4levels respectively. OLAP universe created on top of this BW query willhave 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 valuesfor all available hierarchies.

Answer: True

TRUE. When using a hierarchy and hierarchy node variable combinationin Web Intelligence the hierarchy node variable presents the user with acomplete list of all available hierarchies nodes with the selected hierarchystructure.


Unit 6OLAP Universes on SAP BW - Part 2

Unit OverviewThis unit describes advanced topics in OLAP Universes on SAP BW such asmulti-structure queries, smart measures, calculation, and life-cycle management


• 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 ContentsLesson: Multi-structure queries in OLAP Universes... . . . . . . . . . . . . . . . . . . . . .208

Procedure: To use a multi-structure query in Web Intelligence ... . . .211Exercise 8: Creating a new OLAP Universe based on multi-structurequery .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Lesson: Smart measures and calculations in OLAP Universes ... . . . . . . .220Procedure: To create a new Universe with a database delegatedmeasure... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222Procedure: To use a smart measure in Web Intelligence ... . . . . . . . . .223Exercise 9: Creating a new Universe with a database delegatedmeasure, and utilizing the database delegated summation in a WebIntelligence document.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Lesson: Updating OLAP Universes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234Exercise 10: OLAP Universe Update Part 1 .. . . . . . . . . . . . . . . . . . . . . . . . . . .237Exercise 11: OLAP Universe Update Part 2 .. . . . . . . . . . . . . . . . . . . . . . . . . . .243



Lesson: Multi-structure queries in OLAP Universes

Lesson OverviewIn this lesson, you will learn about the use of multi-structure queries in OLAPUniverses.


• Use multi-structure queries in OLAP Universes and Web Intelligence

Business ExampleYour business reporting group requires a structured layout in a query. For instancethey would like to display a Country Structure which displays countries UnitedStates, UK, and Germany. In addition they would like to see a structured setof Key Figures: Order Entry Qty, Invoiced Qty, and % Share to analyze theperformance of these countries by.

OLAP Universes and BW query structuresAn SAP BW query can contain up to two structures. By creating such a query theend user defines a report with a grid type of layout.

This image shows an SAP BW query in the query designer. This query containstwo structures.


BO100 Lesson: Multi-structure queries in OLAP Universes

Figure 73: Multi-structure query

The first structure (Country Structure) contains three elements - USA, Europe, andAsia Pacific - and the second structure (Structure) contains three elements - OrderQuantity, Unit Price, and Position Price.

A report created with SAP's reporting tools shows the resultset:

Figure 74: Resultset

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

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



Figure 75: 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 IntelligenceBased on the situation that the structure with the characteristic elements isturned into a single item, it is very simple to leverage the two structures in WebIntelligence for reporting.



To use a multi-structure query in Web Intelligence

1. Start InfoView.



4. Click Log On.


6. Select the menu New → Web Intelligence .

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


9. Include the element representing the characteristic structure.

10. Click Run Query.

Note: Each element of the characteristic structure becomes a rowin the Web Intelligence report.





Exercise 8: Creating a new OLAP Universebased on multi-structure query

Exercise ObjectivesAfter 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 ExampleYour business reporting group requires a structured layout in a query. In additionthey would like to see a structured set of Key Figures.

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


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



5. Run the WebI refresh and add the Country Structure and Measures to thereport layout.




Solution 8: Creating a new OLAP Universebased on multi-structure queryTask:Create an OLAP universe and Web Intelligence report with variables that havedefault values defined.


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

b) Click Designer.


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



c) Click Next.







f) Click Next.






j) Click Next.

k) Select the Multi Structure Query.





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





m) Click Finish and Generate the Universe.






a) Review the generated Universe and see how the BEx Query Structuresare translated into Dimensions and Measures.



5. Run the WebI refresh and add the Country Structure and Measures to thereport layout.




Lesson Summary

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



Lesson: Smart measures and calculations in OLAPUniverses

Lesson OverviewIn this lesson, you will learn about the use of smart measures and calculations inOLAP Universes.


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


Smart measures in OLAP UniversesIn 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 WebIntelligence when the number of dimensions displayed in a report is smaller thanthe number of dimensions in the query resultset. Non-additive measures, such asratio, average, and weight, can only be shown at the same aggregation level as thequery resultset. Therefore, non-additive measures generally have their projectionfunction set to None in the universe.

The projection function Database delegated allows you to delegate the aggregationof a non-additive measure to the database server. These are called smart measuresin Web Intelligence. A smart measure has its projection function set to Databasedelegated 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.


BO100 Lesson: Smart measures and calculations in OLAP Universes

Figure 81: Report

The image shows that the default aggregation results in a wrong value because thedefault 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 projectionfunction Database delegated, the correct summary becomes available after asecond refresh of the report.

Figure 82: Report

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



To create a new Universe with a database delegatedmeasure


2. Log onto the BusinessObjects Enterprise system.

3. Click New to create a new connection.

4. Select SAP Business Warehouse 3.x from the list and enter a connectionname.

5. Enter the User name, Password, and Language.

6. Enter the Client, Application Server, and System Number based on the SAPserver details.


7. Set the Authentication Mode to Use Single Sign On when refreshingreports at view time.

Note: Using single-sign-on in combination with an SAP systemrequires the SAP authentication to be configured for the SAP systemin the Central Management Console of BusinessObjects Enterprise.

8. Click Next.

9. Open the list of available cubes by clicking the plus sign next to OLAPCubes.

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 .

20. Click OK .

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



To use a smart measure in Web Intelligence

1. Start InfoView.



4. Click Log On.


6. Select the menu New → Web Intelligence .

7. Select the OLAP Universe based on the BW query with a database delegatedmeasure.


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 UniversesThe user can create calculated measures in the universe. Calculated measuresin OLAP universes are like definitions on the measure object in non-OLAPuniverses, except that you define the restriction using MDX functions embeddedin XML tags rather than using SQL.

Calculated measures can be used in filters or the WHERE clause. Thesyntax for a calculated measure consists of calculations embedded in the tags<EXPRESSION></EXPRESSION>

Universe designer functions are allowed in calculated measure expressions, suchas:

@SELECT

@PROMPT

@VARIABLE

@WHERE



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 ratherthan 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 validityof the object.

In the given example you want to build a measure which calculates the OrderAmount multiplied by Product Price.

Example 1:

<EXPRESSION>[Measures].[AWUNOIYT142BYXSX5WBW4TU60]*[Mea-sures].[AWUNOIYT142 BYXSX5WBW4TU60]</EXPRESSION>

Note: This calculation depends on the technical names of the measures.

Example 2:

<EXPRESSION>@SELECT (Key Figures\Order Amount) *@SELECT (KeyFigures\Product Price)</EXPRESSION>

Note: This calculation depends on the OLAP universe structure andelements, but not on the technical names.



Exercise 9: Creating a new Universe with adatabase delegated measure, and utilizingthe database delegated summation in aWeb Intelligence document

Exercise ObjectivesAfter 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 thedatabase delegated summation in a Web Intelligence document.


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



6. Run the WebI refresh and add all Dimensions and Measures to the reportlayout.

7. Try adding a Sum on % Share and refresh the data to view the Sum.




Solution 9: Creating a new Universe with adatabase delegated measure, and utilizingthe database delegated summation in aWeb Intelligence documentTask:Create an OLAP universe with a database delegated measure and then utilize thedatabase delegated summation in a Web Intelligence document.


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

b) Click Designer.


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



c) Click Next.







f) Click Next.

g) Enter the Username, Password, and Language.





j) Click Next.

k) Select the Smart Measure Query.





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





m) Click Finish and Generate the Universe.





3. Change % Share measure properties to make the aggregation functionDatabase Delegated.

a) Double-click on the % Share measure and change the AggregationFunction to Database Delegated.






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






a) Initially the Sum will be denoted as #TOREFRESH. This indicates thatthe 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 reportlayout.

7. Try adding a Sum on % Share and refresh the data to view the Sum.




Lesson Summary

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



Lesson: Updating OLAP Universes

Lesson OverviewThis lesson provides you with an overview of OLAP Universe life cyclemanagement (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


• 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 ExampleBusiness Client has requested certain dimensional objects have the ability to beselected, sorted and grouped in the ad hoc query tool. You have determined thata refresh of the BEx query and thus the universe will provide this enhancedreporting functionality through enhanced navigation.

OLAP Universe life-cycle managementAs part of the life-cycle management feature, the user is able to update and editOLAP Universes.

The Update OLAP Universe Wizard allows you the refresh to structure of OLAPuniverses automatically with changes made in the OLAP data source. The wizardcan differentiate generated objects from objects added or modified manually,allowing you to preserve the manual changes made in Designer. The wizard doesnot update objects added manually in Designer.


BO100 Lesson: Updating OLAP Universes

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

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

OLAP Universe design guidelinesAny changes to the BEx query or the underlying InfoCubes will impact universeobject definition and thus any dependant reports. One very important guidelineto ensure the integrity of BEx object UID and thus the internal Universe objectID. Follow these tips:

• Universe objects can be renamed to provide better business terms. Forexample:

L00 Organization Unit is renamed to CompanyL01 Organization Unit is renamed to Business UnitL02 Organization Unit is renamed to Division

• Always keep existing InfoObject BEx elements and never delete thenre-create them. This changes the internal UID which impacts the existinguniverse 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 keepthem. This step subsequently re-creates them after executing a refreshstructure impacting reports that use them.

• Always follow a consistent process in the Universe Refresh wizard, suchalways uncheck “Keep Business Name” and always check “Delete obsoleteobjects”

• Consider using scripts to hide the L00 objects and rename the L01 prefixedobjects that have no hierarchy active, making Web Intelligence easier touse and less cluttered.

• Navigational attributes used in the query definition map to individual classeseach with dimension and detail objects Navigational attributes are identifiedby double underscore “__” in the technical name. Consider hiding attributeobjects that match to these navigational objects.

• Use characteristic variables to narrow down records and speed upperformance. In the BEx query create as many calculated and restricted keyfigures that will satisfy many reports and ad-hoc reporting requirements.

• Consider best practice implementation and performance guidelines





Exercise 10: OLAP Universe Update Part 1

Exercise ObjectivesAfter completing this exercise, you will be able to:• Make changes to existing BEx query and noted the changes in the OLAP

universe

Business ExampleAs Universe Designer you require to make changes to universe to reflect modellingchanges required by the business users

Task:Learner will make various changes to the BEx query and note the changesreflected 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 SalesOrder 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) toFree 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


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



Solution 10: OLAP Universe Update Part 1Task:Learner will make various changes to the BEx query and note the changesreflected 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 SalesOrder Item key figure and remove characteristic Sold-to party



• Select System = <SID>, 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.

2. 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 dropin Free Characteristics area

3. Add characteristic “Sold-to partyCountry”(0SOLD_TO__COUNTRY) toFree Characteristic area

a) Expand Customer dimension and select Sold-to partyCountry and dropin Free Characteristics area

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

a) From Key Figures in the InfoProvider drag and drop Sales Order Itemto the Columns area

5. Remove key figure Invoiced Quantity(0INVCD_QTY) from columns

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

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

a) Select Sold-to party from free Characteristic area and press delete





a) From the menu bar, select check query and confirm query is good tocontinue saving, then Click Query -> Save. From the menu bar selectFile -> Exit

Figure 90: Modified BEx Query

8. 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 = <SID>tdc00:6400 User Name= <>SID~900/BO100-## Password = xxxxxx Authentication = SAPClick OK

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

d) From menu, select View -> Refresh Structure, then Begin> button tocontinue 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)





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

b) From menu File->Export, select CMS folder T_BO100_LCM. ClickOK to confirm export operation

c) Exit Designer. Select File -> Exit


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. TypeSAP System: = <SID>SAP Client = 900User Name: = BO100-##Password: = xxxxxx

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

Figure 91: Message when existing document is opened

d) Press close when message “Some objects are no longer available inthe universe.” Click Edit Query, Press close if message “The querycontains unavailable objects” appears. Add additional objects to querypanel and press Run Query




Figure 92: Document after universe refresh

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





Exercise 11: OLAP Universe Update Part 2

Exercise ObjectivesAfter completing this exercise, you will be able to:• Make changes to existing BEx query and note the changes reflected in the

OLAP universe

Business ExampleAs a Universe Designer you require to make changes to universe to reflectmodelling changes required by the business users

Task:Learner will make various changes to the BEx query and note changes reflectedin 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

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

3. Add characteristic “Region (State. in the free area, rename descriptionto “Region”

4. Include additional variable “Material Variable” (T_MAT_V)


6. Launch designer to update universe


8. Create new or use previous WEBI document




Solution 11: OLAP Universe Update Part 2Task:Learner will make various changes to the BEx query and note changes reflectedin 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



• Select System = <SID>, 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.

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

3. Add characteristic “Region (State. in the free area, rename descriptionto “Region”

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

b) Click on the Region (State. characteristic and change the Description inthe property window to Region




4. Include additional variable “Material Variable” (T_MAT_V)

a) On the View Toolbar click Filter.

b) Drag Material characteristic in Default Values to CharacteristicRestrictions

c) Right click on the Material and select Restrict. Select variables fromthe Show drop down. Selelct variable [T_MAT_V] and click rightarrow to select. Click OK

Figure 93: Add Material Variable


a) From the menu toolbar, select check query and confirm query is goodto continue saving, then Click Query -> Save, then Query -> Exit toclose the BEx Query Designer




6. 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 = <SID>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_##, clickOK, then OK when universe is successfully imported

d) From menu, select View -> Refresh Structure, then Begin> button tocontinue 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 94: Universe after refresh


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

b) From menu File->Export, select CMS folder T_BO100_LCM. ClickOK to confirm export operation

c) Exit Designer. Select File -> Exit

8. Create new or use previous WEBI document





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. TypeSAP System: = <SID>SAP Client = 900User Name: = BO100-##Password: = xxxxxx

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

d) Press Run Query

Figure 95: Prompt Window when running Web Intelligence query

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



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


BO100 Unit Summary

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


Unit Summary BO100



Test Your Knowledge

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

2. The tool used for updating universes with connections to a BEx query basedon changes made to the BEx query is (Choose the correct answer)Choose the correct answer(s).□ A The OLAP Universe update Wizard□ B The refresh structure Wizard□ C The update universe Wizard□ D The classes and objects update Wizard□ E The BEx Universe update Wizard

3. The Wizard can detect additions made to classes and objects made by theuser in addition to those automatically added in the BEx queryDetermine whether this statement is true or false.□ True□ False

4. Objects named with Prefix L00 should never be renamed as this will impactreports currently using them.Determine whether this statement is true or false.□ True□ False

5. If a user requires a name change made in the BEx query to be reflected inthe universe, choose the best option in the wizard.Choose the correct answer(s).□ A Check Keep business name, and check Hide obsolete objects□ B UnCheck Keep business name, and check Hide obsolete objects□ C Check Keep business name, and check Delete obsolete objects□ D Check Keep business name, and check Delete obsolete objects



6. Adding an additional key figure in BEx query, always creates three additionalobjects in a new class under Key FiguresDetermine whether this statement is true or false.□ True□ False

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



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, classnames, objects, where clauses and select clauses.

2. The tool used for updating universes with connections to a BEx query basedon 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 islaunched from the Designer Menu View -> Refresh Structure.

3. The Wizard can detect additions made to classes and objects made by theuser 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 impactreports 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 inthe universe, choose the best option in the wizard.

Answer: B

If the name changes in BEx, it is best to uncheck keep business name

6. Adding an additional key figure in BEx query, always creates three additionalobjects in a new class under Key Figures

Answer: False

key figures such as counts will not require all three objects, these measuresdo not get unit and formatted value objects



7. Adding an additional object originally a display attribute and now is anavigational attribute, is marked for deletion by the update wizard.

Answer: True

the original object is deleted and the new navigational objects are created.


Unit 7Crystal Reports and SAP ERP

Unit OverviewThis unit provides you with an overview on the connectivity for Crystal Reportsagainst SAP ERP.


• Explain the functionality of Crystal Reports and its connectivity with SAPsystems

• Create reports against SAP tables• Create reports against ABAP functions• Create reports against SAP InfoSets• Create reports against SAP queries (ABAP queries)

Unit ContentsLesson: Crystal Reports Overview ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256Lesson: Crystal Reports and SAP tables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

Exercise 12: Creating a new Crystal Report against SAP tables ... .265Lesson: Crystal Reports and ABAP Functions... . . . . . . . . . . . . . . . . . . . . . . . . . . .271

Exercise 13: Creating a new Crystal Report against a ABAPFunction... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

Lesson: Crystal Reports and Classic InfoSets .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .281Procedure: To create a new report based on the InfoSet connectivity.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282

Lesson: Crystal Reports and InfoSets Queries .. . . . . . . . . . . . . . . . . . . . . . . . . . . .285Procedure: To create a new report based on the InfoSet queryconnectivity .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286


Unit 7: Crystal Reports and SAP ERP BO100

Lesson: Crystal Reports Overview

Lesson OverviewThis lesson provides you with an overview of Crystal Reports and its connectivitywith SAP systems.


• Explain the functionality of Crystal Reports and its connectivity with SAPsystems

Business ExampleYou want to access your organization’s data and transform it into actionableinformation to improve performance. By delivering the most-requested piecesof information reliably and securely – via the web or embedded in enterpriseapplications – reports can serve as the foundation of a successful businessintelligence (BI) strategy. Crystal Reports software enables you to easily designinteractive reports and connect them to virtually any data source. Your users canbenefit from on-report sorting and filtering – giving them the power to executedecisions instantly.

Advantages of Crystal ReportsCrystal 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


BO100 Lesson: Crystal Reports Overview

Figure 96: Crystal Reports Business Value

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

Figure 97: Crystal Reports: Connectivity Overview



Figure 98: Crystal Reports: Connection Methods


BO100 Lesson: Crystal Reports Overview

Lesson Summary

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

systems



Lesson: Crystal Reports and SAP tables

Lesson OverviewThis lesson provides you with an overview on the connectivity for Crystal Reportsagainst SAP ERP. You will use SAP ERP as a data source for Crystal Reports.


• Create reports against SAP tables

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

Crystal Reports and SAP ERP/ECCEnterprise 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 accessjust about any data regardless of where it resides, from packaged ERP and CRMapplications, to relational database, to log files and Outlook. You can then createjust about any type of report in any format you need, such as management reports,financial statements, and customer billings. The report can be distributed throughthe web in a PDF document, via email, on a mobile phone, or embedded directoryin Microsoft Office.

BusinessObjects XI Integration for SAP Solutions includes components thatintegrate Crystal Reports with your existing SAP systems Available SAPERP/ECC data sources for Crystal Reports are:

SAP ERP/ECC

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


BO100 Lesson: Crystal Reports and SAP tables

Figure 99: Connectivity Overview

Crystal Reports and SAP tablesAt the most basic level, SAP ERP data is stored in a standard relational databasesystem such as Oracle or SQL Server. This data is then abstracted in ERP torepresent the various entities used by the ERP applications. These definitions,with the exception of ABAP functions and ABAP data clusters, are stored in theABAP dictionary. The SAP Tables, Function, and Cluster connectivity providesaccess to these entities for reporting.

The ABAP dictionary is referenced by the SAP Tables, Function, and Clusterconnectivity in order to retrieve the definitions for each of the entities describedabove excluding ABAP functions and ABAP data clusters. Definitions of theentities 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 configuredin the system and provides the appropriate description according to the languagethe user has specified at login.

The SAP Tables, Function, and Cluster connectivity provides access to severallow-level objects within SAP, for example: transparent tables, pool and clustertables, views, and ABAP data clusters and functions.

Transparent tablesThis type of database object is similar to the traditional database table. Transparenttables contain the majority of the SAP application data. Most SAP applicationsuse one or more transparent tables to store and retrieve business transactions. Youcan link these tables to other transparent tables in order to pull information fromother application areas of the SAP system.



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

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

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

Client fieldMost tables in SAP contain a client field (native field name is MANDT). Becauseindividual 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 thisconfiguration. When you connect to SAP, you are prompted to provide your clientnumber: this information eliminates the need to create a selection formula thatfilters the clients. As well, if a report contains multiple tables, you do not needto include a link on the client field—this, too, is automatically handled by theconnectivity.

Language fieldSome tables in SAP, specifically those that contain text descriptions, have multipleentries—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 (nativefield name is SPRAS) and specify the language that you want to display. Forexample:

{table.spras} = "EN".



Troubleshooting Tips and Tricks• 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.





Exercise 12: Creating a new CrystalReport against SAP tables

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new report against SAP tables

Business ExampleYou are a report designer and need to create Crystal Report objects using SAPtables.

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

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

7. View the report in InfoView using your SAP user account.



Solution 12: Creating a new Crystal Reportagainst SAP tablesTask:Follow the following steps to create a new report against SAP tables.


a) Select Start → Program → Crystal Reports 2008 → Crystal Reports2008.


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

e) Enter the Client, Username, Password and click Next.

f) Leave the check box Generate RFC trace files unchecked and clickFinish.

Note: The SAP Table, Cluster or Function connectivity isbroken into three areas. The Data Cluster (CL) entry providesaccess to ABAP clusters; the Data Dictionary (DD) entryoffers access to the ABAP Dictionary; and the ABAP Functionmodule (FN) offers access to ABAP Functions.




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

a) Right-click the entry Data Dictionary (DD) and select the menuOptions.

b) Select Show Both under Tables and Fields.

c) Enter SFLI% in the text box Table name LIKE.

Figure 100: 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 thesettings 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 andclick Next.

c) Select the following fields. Click the right arrow to bring them to theFields 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 andclick 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 andclick Next.

j) Select No Template and click Finish.

k) Preview the output of your report.

Figure 101: Preview report





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.


a) From the Save As window, navigate to SAP → 2.0 → <SID>CLNT800

b) Create your own report folder if it has not been created yet. Youmay want to use a unique group number to identify this folder . Forexample: <Group##Folder>.

c) Enter the filename for your report.

d) Click Save.


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

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

c) Select SAP as the authentication.

d) Click Log On.

e) Click Document List

f) Navigate to Public Folders → SAP → 2.0 → <SID>CLNT800 and goto your report folder.

g) Right-click your report.

h) Select View. The report displays in the window.



Lesson Summary

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


BO100 Lesson: Crystal Reports and ABAP Functions

Lesson: Crystal Reports and ABAP Functions

Lesson OverviewThis lesson provides you with information on the connectivity for Crystal Reportsagainst ABAP functions.


• Create reports against ABAP functions

Business ExampleWhile technically not a table, an ABAP function is often used in ERP reportingto provide calculations and to retrieve data that is based on parameters passedinto the function (for example, an employee number passed to a function thatreturns the employee’s address). For this reason, the SAP Tables, Cluster andFunction connectivity provides the ability to call ABAP functions and use theirresults in a report. ABAP functions are also useful in situations where complexpre-processing of the data must occur before viewing or in circumstances whereyou may wish to further optimize the performance of a query.

ABAP FunctionsFor 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 canbe called by the SAP Tables, Cluster and Function connectivity and show howthey appear in Crystal Reports.

Function with values as inputs and outputs

Function F

Importing

VALUE(NAME) TYPE C

VALUE(DEPARTMENT) TYPE C

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 musteither link to them from another table (or function), or specify them with arecord-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 thatspecifies {F.Name} = "Richard". This formula will retrieve the years of serviceand 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:

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 anothertable, 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 andposition of that person. Suppose that Tom’s gender is male, and that the Positionstable 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:

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

Troubleshooting Tips and Tricks• 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?





Exercise 13: Creating a new CrystalReport against a ABAP Function

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new report against ABAP Functions

Business ExampleYou are a report designer and need to create Crystal Report objects using ABAPfunctions.

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



3. Create a report based on the function BAPI_FLIGHT_GETLIST (Find list offlights).

4. Select the fields for the report.

5. Create a record selection for the Airline code UA.






Solution 13: Creating a new Crystal Reportagainst a ABAP FunctionTask:Follow the following steps to create Crystal Reports objects using ABAPfunctions.


a) Select Start → Program → Crystal Reports 2008 → Crystal Reports2008.


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

e) Enter the Client, Username, Password and click Next.

f) Leave the check box Generate RFC trace files unchecked and clickFinish.

Note: The SAP Table, Cluster or Function connectivity isbroken into three areas. The Data Cluster (CL) entry providesaccess to ABAP clusters; the Data Dictionary (DD) entryoffers access to the ABAP Dictionary; and the ABAP Functionmodule (FN) offers access to ABAP Functions.




3. Create a report based on the function BAPI_FLIGHT_GETLIST (Find list offlights).

a) Right-click the entry FN (ABAP Function modules) and select themenu 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 thesettings from the Options dialog.

4. Select the fields for the report.

a) Select the following fields. Click the right arrow to bring them to theFields 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 102: Standard Report Creation Wizard

b) Click Next.

c) Skip the Grouping page and click Next.




5. Create a record selection for the Airline code UA.

a) Select BAPI_FLIGHT_GETLIST.T_FLIGHT_LIST.AIR-LINEID(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) Preview the output of your report.






e) Click OK.



b) Create your own report folder if it has not been created yet. Youmay want to use a unique group number to identify this folder . Forexample: <Group##Folder>.


d) Click Save.








d) Click Log On.


f) Navigate to Public Folders → SAP → 2.0 → <SID>CLNT800 and goto your report folder.

g) Right-click on your report.




Lesson Summary

You should now be able to:• Create reports against ABAP functions


BO100 Lesson: Crystal Reports and Classic InfoSets

Lesson: Crystal Reports and Classic InfoSets

Lesson OverviewThis lesson provides you with information on the connectivity for Crystal Reportswith SAP InfoSets.


• Create reports against SAP InfoSets

Business ExampleThe combined InfoSet/ABAP query driver allows you to use an existing SAPquery or InfoSet as a data source for a Crystal Report object. The SAP query orInfoSet is built within SAP by a content expert, who then makes the data availableto the business user. Through the Crystal Reports connectivity the user can designmultiple reports by quickly referencing the same query or InfoSet. Because anInfoSet can be built on top of a logical database in SAP, it can inherit all of thebusiness logic and security that is programmed into the logical database.

Crystal Reports and Classic InfoSetsReports that are based on SAP queries and InfoSets behave similarly to reports thatare based on stored procedures in mainstream databases. You can insert subreportsthat 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 shouldconsider creating a brand new InfoSet or SAP query instead. The new joinwill be processed on the SAP server allowing the report to respond faster.

Note: Your SAP queries and InfoSets may contain parameters that you canuse 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. Ifparameters are included in the SAP query or InfoSet, Crystal Reportsprompts you to specify the values that you want to include in the query.



To create a new report based on the InfoSetconnectivity

1. Start Crystal Reports

2. Select the menu File → New Report → Standard Report.

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

Figure 104: Classic InfoSets

Note: The SAP InfoSet connectivity offers the connectivity withClassic InfoSets and SAP Queries. Classic InfoSets can be assignedto a Global or a Local environment. The Global environmentmeans that the InfoSet is available across all SAP clients from theunderlying SAP system. The Local environment means that theInfoSet 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.



BO100 Lesson: Crystal Reports and Classic InfoSets

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 rightarrow. Click Next to continue.

15. If required, define a record selection. Click Next to continue.

16. Click Finish.

Troubleshooting Tips and Tricks• 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.



Lesson Summary

You should now be able to:• Create reports against SAP InfoSets


BO100 Lesson: Crystal Reports and InfoSets Queries

Lesson: Crystal Reports and InfoSets Queries

Lesson OverviewThis lesson provides you with information on the connectivity for Crystal Reportsagainst SAP queries (ABAP queries).


• Create reports against SAP queries (ABAP queries)

Business ExampleCrystal Reports is able to leverage the outcome of the SAP query tool with thecombined InfoSet and SAP query connectivity.

Crystal Reports and InfoSet queriesThe SAP query tool allows you to create SAP queries and InfoSet queries in asingle tool. The query itself leverages the InfoSet as a data source, therefore theInfoSet needs to be created and be assigned to the proper user groups before youstart creating the SAP query.

The difference between an InfoSet query and an SAP query is the actual tool itselfand the output format. The InfoSet query tool is a single-screen tool whereas theSAP query tool is a screen-byscreen approach. On the output format the SAPquery offers more capabilities like a ranked and statistical list than the InfoSetquery which only offers a basic list output.

Crystal Reports is able to leverage the outcome of the SAP query tool with thecombined InfoSet and SAP query connectivity.



To create a new report based on the InfoSet queryconnectivity

1. Start Crystal Reports

2. Select the menu File → New Report → Standard Report.

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 withClassic InfoSets and SAP Queries. Classic InfoSets can be assignedto a Global or a Local environment. The Global environmentmeans that the InfoSet is available across all SAP clients from theunderlying SAP system. The Local environment means that theInfoSet is only available on the client the InfoSet was created.

9. Select SAP Query.

Figure 105: SAP Query

10. Double-click the Global (G) entry.

11. Click the right arrow to move the InfoSet to the right-hand screen.



BO100 Lesson: Crystal Reports and InfoSets Queries

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 rightarrow. Click Next to continue.

15. If required, define a record selection. Click Next to continue.

16. Click Finish.

Troubleshooting Tips and Tricks• 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.



Lesson Summary

You should now be able to:• Create reports against SAP queries (ABAP queries)


BO100 Unit Summary

Unit SummaryYou 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)


Unit Summary BO100



Test Your Knowledge

1. Which of the following areas can be found under the SAP Table, Cluster orFunction connectivity in Crystal Reports?Choose the correct answer(s).□ A CL (Data Clusters), DD (Data Dictionary), and FN (ABAP

Function modules)□ B CL (Cluster Lists), DD (Data Dictionary), and FN (Function

Nodes)□ C I (Classic Infoset), and Q (SAP Query)□ D G (Global, client independent, objects), and L (Local, client

dependent, objects)

2. What is the primary use of ABAP function in ERP reporting?Choose the correct answer(s).□ A To maintain the definitions for each language that is configured

in the system.□ B To provide calculations to retrieve data that is based on parameters

into the function.□ C To provide access to several low-level objects within SAP such as

transparent tables, pool and cluster tables.□ D To provide a more abstract view of the data and allow you to build

reports without having to worry about linking multiple tables in areport.



Answers

1. Which of the following areas can be found under the SAP Table, Cluster orFunction connectivity in Crystal Reports?

Answer: A

Correct answer is A.

2. What is the primary use of ABAP function in ERP reporting?

Answer: B



Unit 8Crystal Reports and SAP BW - Part 1

Unit OverviewThis unit provides you with an overview of the connectivity for Crystal Reportsagainst SAP BW. You will learn SAP BW metadata and how to use SAP BWqueries in Crystal Reports.


• 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 ContentsLesson: SAP BW Metadata in Crystal Reports .. . . . . . . . . . . . . . . . . . . . . . . . . . . .294Lesson: Crystal Reports with simple SAP BW queries .. . . . . . . . . . . . . . . . . . .303

Exercise 14: Creating a new report against a BW Query with displayattributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307

Lesson: Crystal Reports against advanced SAP BW queries .. . . . . . . . . . .312Exercise 15: Creating a new report against an SAP BW query with amandatory SAP variable .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317


Unit 8: Crystal Reports and SAP BW - Part 1 BO100

Lesson: SAP BW Metadata in Crystal Reports

Lesson OverviewThis lesson provides you with an overview of Crystal Reports in combinationwith SAP BW queries.


• Describe the metadata from SAP BW inside Crystal Reports

Business ExampleYou want to access your organization's data and transform it into actionableinformation to improve performance. By delivering the most-requested piecesof information reliably and securely - via the Web or embedded in enterpriseapplications - reports can serve as the foundation of a successful businessintelligence (BI) strategy. Crystal Reports software enables you to easily designinteractive reports and connect them to virtually any data source. Your users canbenefit from on-report sorting and filtering giving them the power to executedecisions instantly.

Overview of Crystal ReportsCrystal 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 flexibilityfor delivery information and data at multiple levels.


BO100 Lesson: SAP BW Metadata in Crystal Reports

Figure 106: Connectivity Overview

SAP BW metadata in Crystal ReportsWhen you connect to an SAP BW query in Crystal Reports, the underlyingmetadata from the SAP BW query is leveraged and matched to Crystal Reportselements The table below shows how SAP BWmetadata is used in Crystal Reports

BW Queryelement

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 Keyfigure can have up to three elements: numeric value, unit,and formatted value.

Calculated KeyFigure

Measure element in the folder Key figure. (Informationabout the details of the calculated key figure is not availablein Crystal Reports.)

Restricted KeyFigure

Measure element in the folder Keyfigure (Information aboutthe details of the restricted keyfigure is not available inCrystal Reports.)

Filter Filters will be applied to the underlying query but are notvisible in the Crystal Reports designer.

Navigationalattribute

Separate fields for key and description per navigationalattribute.

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

SAP variables Parameters.



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

Figure 107: SAP BW query in the BEx Query Designer

The rows of this query include several characteristics and the columns severalkeyfigures. On the left side, the actual cube structure is shown with the cubedimensions (not to be confused with characteristics).

In the image you can identify one dimension and tree characteristics. Thedimension 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 thefollowing elements:



Figure 108: Field Explorer in Crystal Reports

• Each characteristic in the query will result in an element in the field explorerwith a key and a description item (For example: Region Key and RegionName).

• Each characteristic will also generate a Node ID and a Parent Node ID whichcan be used for hierarchical reporting.

• Each characteristic will also generate a Member Unique Name field whichrepresents the technical key value.

Display attributes and navigational attributesDisplay attributes are InfoObjects which are logically assigned or subordinated toa characteristic. For example, the characteristic Sold-to party has two attributes:

• Country• Postal Code

In SAP reporting tools the display attributes can only be used in combination withthe actual characteristic. This means the attribute Postal Code can only be shownin the SAP reporting tool in combination with the characteristic customer.

Characteristics can be defined as navigational attributes in the BW cube, whichthen makes these attributes available for navigational purposes in the reportingtools. Navigational attributes are treated identically to a characteristic.

The following screen shows an SAP BW query in the BEx Query Designer.



Figure 109: Display attributes in BEx Query Designer

The row structure includes a characteristic Customer (Sold-to party) with fourdisplay attributes (Country, Postal Code, City Name, Account group, CustomerClassific.).

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 doubleunderscore (“__”) in the technical name of the navigational attribute.

Building a Crystal Report object on top of such an SAP BW query will result inthe following elements:



Figure 110: Field Explorer in Crystal Reports with navigational attributes

Note:

• Each characteristic in the query will result in an element in the fieldexplorer with a key and a description field.

• Each navigational attribute in the query will result in an element inthe field explorer with a key and a description item (for exampleRegion, Sold-toPartyCountry).

• Crystal Reports will include all available display attributes for thecharacteristic and not only the display attributes that are included inthe SAP BW query.

Keyfigures, units, and currenciesEach 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:



Figure 111: Two keyfigures in Crystal Reports

Note:

• Each keyfigure is represented with a field in a group called KeyFigures

• In the case the keyfigure is configured in SAP BW with a unit, anadditional field will be added representing the unit information

• The formatted value represents the numeric value formatted as astring value following the user-specific formatting settings

HierarchiesHierarchies can be activated for characteristics in the BEx Query Designer andoffer the user the capability to navigate along a hierarchical structure. The imageshows the field explorer in Crystal Reports based on an SAP BW query with ahierarchy.



Figure 112: Field Explorer in Crystal Reports with hierarchy

Note:

• A hierarchy results in a parent-child relationship



Lesson Summary

You should now be able to:• Describe the metadata from SAP BW inside Crystal Reports


BO100 Lesson: Crystal Reports with simple SAP BW queries

Lesson: Crystal Reports with simple SAP BW queries

Lesson OverviewIn this lesson, you will learn about the connectivity of Crystal Reports with simpleSAP BW queries.


• Create reports against SAP BW queries

Business ExampleYou are a report designer and need to create a Crystal Report object on top of anSAP BW query.

Simple SAP BW queries with Crystal ReportsWhen creating new reports against SAP BW there are two options:

• Using the SAP toolbar.• Using the Database Explorer.

Using the SAP toolbarIntegrated within Crystal Reports, the SAP Tools toolbar facilitates tasksassociated with reporting off BW queries. It allows you to log onto BW, workwith its data sources, save reports to BW, and publish reports immediately toBusinessObjects Enterprise via BW. The SAP specific toolbar and the SAPspecific menu items offer you the typical SAP open and save dialogs that are alsoused in the Business Explorer. Also they allow you to store the Crystal Reportobject directly into SAP BW roles.

The following table shows all available menu options of the SAP toolbar:



Figure 113: SAP Toolbar

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

Figure 114: BW MDX Driver

Note: The SAP BW MDX Query connectivity is the more enhancedversion of the Crystal Reports connectivity with SAP BW cubes and SAPBW queries.

Note: It is highly recommended to use the BW MDX driver. The BWQuery driver does not support multiple structures of a BW query anddoes not support display attributes.

Using the Database ExplorerCrystal Reports lists the two SAP BW query connectivities in the standardDatabase Explorer.



Crystal Reports and display attributesDisplay attributes are used in SAP BW to provide additional information but thisinformation is not available for a typical OLAP navigation (slice-and-dice) in theSAP reporting tools. The information can only be displayed as part of the resultin combination with the actual characteristic itself.

For example: The characteristic customer is configured with a display attributeCountry. Country can be displayed only in combination with the characteristiccustomer and Country cannot be used for navigation.

In Crystal Reports these display attributes result in fields underneath thecorresponding characteristic. Display attributes can be used as standalone withoutthe need to display the actual characteristic in the report.

Figure 115: Display attributes

Note: The technical names of display attributes follow a namingconvention: [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 nameof the characteristic therefore [50MATERIAL] would be the mediumdescription of the characteristic 0MATERIAL (Customer).





Exercise 14: Creating a new report againsta BW Query with display attributes

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new report against an SAP BW query with display attributes

Business ExampleYou are a report designer and need to create a Crystal Report object on top of anSAP BW query.

Task:Follow the following steps to create a new report against an SAP BW query withdisplay attributes:


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

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 Explorerinstead of the field names.

7. Create a report that includes attributes for Sold-to (Key, Name), SalesOrganization (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.



Solution 14: Creating a new report againsta BW Query with display attributesTask:Follow the following steps to create a new report against an SAP BW query withdisplay attributes:


a) Double-click on SAP Logon Pad and make sure that you have a entryfor the BW system

b) From the Windows Desktop: Start → Programs → Crystal Reports2008.


a) Select the menu SAP → Settings.

b) Select the check box Use MDX Driver with support for Multiplestructures.

c) Click OK.



a) Enter Client, Username, and Password. Select the desired language.

b) The SAP standard open/save dialog will show up and offer the user toselect a query from roles and InfoAreas.

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





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 anaming 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 withthe technical name of the characteristic therefore[50SOLD_TO] would be the medium description of thecharacteristic 0SOLD_TO (Customer).

7. Create a report that includes attributes for Sold-to (Key, Name), SalesOrganization (Company Code), Material Medium Name (Name, Weight).

a) Drag the fields from the Field Explorer to the details section of thereport.


a) SelectView → Preview.




9. Publish the report to your BusinessObjects Enterprise system


b) Select the Enterprise tab

c) Select the user folder where you want to save the report. Select SAP →2.0 →<SID>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.

a) Lauch Infoview from Programs → BusinessObjects XI 3.1 →BuinessObjects Enterprise Client Tools →BusinessObjects EnterpriseJava InfoView.

b) Enter the user name and password given by the instructor. Select SAPas the authentication type.

c) Click Document List.

d) Double-click your report to view its content.



Lesson Summary

You should now be able to:• Create reports against SAP BW queries



Lesson: Crystal Reports against advanced SAP BWqueries

Lesson OverviewIn this lesson, you will learn about the connectivity of Crystal Reports againstmore complex SAP BW queries.


• Create reports against SAP BW queries with SAP variables• Create reports against SAP BW queries with multiple structures

Business ExampleYou are a report designer and need to create a Crystal Report object on top of anSAP BW query with mandatory SAP variables.

Crystal Reports and SAP variablesSAP BW queries can contain SAP variables which turn into parameters for thereport. SAP supports a large set of options for these variables, starting with thefeature to have optional or mandatory prompting.

Optional and mandatory SAP variablesIn the scenario where the SAP variable is optional, Crystal Reports creates aprompt 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 fromthe 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. Theorder of priority for the SAP Variable is:

1. Personalized Variable value.2. Default Variable value.3. Manually entered value.


BO100 Lesson: Crystal Reports against advanced SAP BW queries

For example: Crystal Reports created a report with an optional prompt based onan SAP BW query with an optional variable and the user is setting the value toNull. In the case the SAP variable has a default value defined, the resultset will bebased on the default value even though the user set the prompt to Null.

Figure 116: Crystal Report Based on BW Query with Variable

Crystal Reports and multi-structure queriesThe BEx Query Designer allows creating a query that contains two structures. Astructure is very similar to the specified grouping functionality of Crystal Reports.A structure can contain a definition of selections and formulas. One query cancontain up to two structures which then lead to a situation where the query designbuilds a well designed grid for the result set.



Figure 117: 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 Reportstries to resolve the structure containing the keyfigures into separate fields andthe structure representing the special grouping becomes a single field in CrystalReports.



Figure 118: Multi-structure in Crystal Reports

In the given example the structure for the specific grouping of countries appears asone field in Crystal Reports and the three keyfigures appear as separate fields.

Note: SAP BW queries with two structures are only supported with theBW MDX Driver and are not supported with the BW Query driver.





Exercise 15: Creating a new report againstan SAP BW query with a mandatory SAPvariable

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new report against an SAP BW query with a mandatory prompt

Business ExampleYou are a report designer and need to create a Crystal Report object on top of anSAP BW query with mandatory SAP variables.

Task:Follow the following steps to create a new report against an SAP BW query withmandatory 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 theretrieved metadata in Crystal Reports.




6. Select the BO100 Mandatory variable (technical name: T_BO100_Q04_1)query.


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.









Solution 15: Creating a new report againstan SAP BW query with a mandatory SAPvariableTask:Follow the following steps to create a new report against an SAP BW query withmandatory 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 theretrieved metadata in Crystal Reports.


a) Double-click on SAP Logon Pad and make sure that you have a entryfor the BW system.





c) Click OK.

d) Select the menu SAP → Create New Report from a Query.







6. 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 CrystalReports and during the process of creating the report a list ofpossible values is loaded into the prompt definition.



b) Click the Database tab and select the Show Description option.

c) Click OK.



f) Click the plus sign in front of BO100 Mandatory variable.


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.

a) Select the fields from the Field Explorer and drag them to the reportdetail area.

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






e) Click OK.






b) Create your own report folder GR## if it has not been created yet.


d) Click Save.





d) Click Log On.


f) Navigate to Public Folders → SAP → 2.0 → <SID>CLNT900.





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


BO100 Unit Summary

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


Unit Summary BO100



Test Your Knowledge

1. Which of the following SAP BW data sources can Crystal Reports directlyaccess?Choose the correct answer(s).□ A BEx Queries and BW cubes only□ B ODS tables and BW queries only□ C Tables and cluster (Open SQL) and BEx Queries only□ D ODS, Tables and cluster (Open SQL), BEx Queries, and

InfoCubes.

2. What is the main advantages of the MDX when comparing it to the olderquery driver for accessing BW queries.Choose the correct answer(s).□ A Access to Display attributes, quieres with 2 structures, and

enhanced treatment of hierarchies.□ B Export the Crystal Report to SAP BusinessObjects Enterprise

system.□ C Start and restart SAP BusinessObjects Enterprise Central

Management Server.□ D Authenticate report designers using single-sign on SAP account.



Answers

1. Which of the following SAP BW data sources can Crystal Reports directlyaccess?

Answer: D

Correct answer is D.

2. What is the main advantages of the MDX when comparing it to the olderquery driver for accessing BW queries.

Answer: A

Correct answer is A.


Unit 9Crystal Reports and SAP BW - Part 2

Unit OverviewThis unit explains how to use SAP BW queries with hierarchies and variables inCrystal Reports.


• Describe the differences between BWMDX and BW Query driver in regardsto 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 ContentsLesson: Crystal Reports with SAP BW queries with hierarchies ... . . . . . .328

Exercise 16: Creating a new report with hierarchy variable .. . . . . . . . .331Lesson: Crystal Reports against SAP BW cubes... . . . . . . . . . . . . . . . . . . . . . . . .338Lesson: Crystal Reports and keydate variables ... . . . . . . . . . . . . . . . . . . . . . . . . .342

Exercise 17: Creating a new report with a keydate variable.. . . . . . . . .343Lesson: SAP variable personalization ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349



Lesson: Crystal Reports with SAP BW queries withhierarchies

Lesson OverviewIn this lesson, you will learn about the connectivity of Crystal Reports using SAPBW queries containing hierarchies.


• Describe the differences between BWMDX and BW Query driver in regardsto 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 ExampleYou want to be able to leverage hierarchies from a SAP BW query in CrystalReport

Crystal Reports Based on BW Queries with HierarchiesThe activated hierarchy from the underlying SAP BW query will result in aparent-child relationship being represented in Crystal Reports.


BO100 Lesson: Crystal Reports with SAP BW queries with hierarchies

Figure 119: Crystal Report Based on BW Query with Hierarchy

BW MDX driver vs. BW Query driverIn terms of hierarchical reporting the BW connectivity offers two differentsolutions. The BW Query driver connectivity offers each level of the hierarchy asa separate field and also offers parent child-relationship information.

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

The listing of the separate levels is a legacy feature and the recommendation is touse the new parent-child relationship and the hierarchical grouping functionalityof Crystal Reports.

The BW MDX driver only offers a parent child relationship.



Formulas for hierarchical reportingCrystal Reports offers some additional formulas and functions that allow the userto create a better report design and provide conditional formatting even in thecontext of a hierarchy.

Formula Hierarchy LevelThe first formula for hierarchical reporting is the formula HierarchyLevel(). Theformula HierarchyLevel() allows retrieving the level of the hierarchical grouping.The formula needs a GroupLevel as input. The following is an example for theformula syntax assuming Material Node ID is the grouping field in the report:

HierarchyLevel (

GroupingLevel ( {Material Node ID})

)

Count Hierarchical ChildrenThe second formula is CountHierarchicalChildren() which allows counting thenumber of children of a hierarchy level. The formula needs a GroupLevel as input.The following is an example for the formula syntax assuming Material NodeID 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 levelWith the formulas the report can be conditionally formatted so that the groupheadings follow an indentation and the keyfigures stay aligned.

Crystal Reports with hierarchy variablesHierarchy variables allow the user to select a hierarchy each time the report isbeing viewed. Using the parent-child relationship in Crystal Reports the actualdesign of the report itself does not need to be changed in such a situation becauseCrystal Reports dynamically resolves the parent-child relationship.

Crystal Reports with hierarchy node variablesHierarchy node variables allow the user to select a specific node of the chosenhierarchy and use the hierarchy node as a filter for the data that is being returnedfrom the SAP BW query.



Exercise 16: Creating a new report withhierarchy variable

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new report with a hierarchy variable

Business ExampleYou are a report designer and need to create a Crystal Report object using SAPBW 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 aentry for SAP system in SAP Logon Pad.


3. Choose theBO100 hierarchy variable (technical name: T_BO100_Q08_1)query.


5. Insert a group based on the Material parent-child relationship.

6. Create a hierarchical grouping based on the Material parent-childrelationship.

7. Create a summary for the Sales Volume (MC).

8. Preview your report with different values for the hierarchy and hierarchynode variable.






Solution 16: Creating a new report withhierarchy variableTask: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 aentry for SAP system in SAP Logon Pad.

a) Double-click SAP Logon Pad and make sure that you have a entryfor the BW system





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.

3. Choose theBO100 hierarchy variable (technical name: T_BO100_Q08_1)query.

a) Click the Find icon and search for T_BO100_Q08_1.

b) Click OK.





a) Change Crystal Reports Settings to: File → Options.

b) Click the Database tab and choose the Option Show Description.

c) Click OK.



f) Click the plus sign in front of BO100 Hierarchy variable.


5. Insert a group based on the Material parent-child relationship.

a) Select the menu Insert → Group.

b) Select theMaterial Node ID field.

c) Navigate to the Options tab.

d) Select the Customize Group Name Field check box.

e) Select from the existing fieldMedium Name as the description valueof the hierarchy.

f) Click OK.

6. Create a hierarchical grouping based on the Material parent-childrelationship.

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

d) Define the Group Indent: 0.3 in.

e) Click OK.




7. 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” allowscreating a group summary by adding values from the lowerlevel of a hierarchy up to a higher aggregated level. An examplewould be to summarize salary figures from the lowest level ofan organization hierarchy up to the top level of the hierarchy.

Note: In the case of an SAP BW query as a data source theoption “Summarize across hierarchy” is not necessary becausethe underlying SAP BW query returns the aggregated valuesfor 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.




8. Preview your report with different values for the hierarchy and hierarchynode variable.

a) Select the menu View → Print Preview.

b) Based on the situation that the report contains a hierarchy variable youare prompted to select a hierarchy.

c) Select a value for the prompt.

Note: Select Product Hierarchy for Material MARA.

d) Click OK.







e) Click OK.



b) Create your own report folder if it has not been created yet.


d) Click Save.








d) Click Log On.







Lesson Summary

You should now be able to:• Describe the differences between BWMDX 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



Lesson: Crystal Reports against SAP BW cubes

Lesson OverviewIn this lesson, you will learn how to create Crystal reports against a BW cube.


• Create reports against a BW cube directly

Business ExampleYour business reporting group requires a report that queries against a BW cube.

Crystal Reports against SAP BW cubesWhen creating a report against a BW cube directly the list of available fields willbe larger than the list of fields for an SAP BW query.

Note: Accessing a BW cube directly is only available for the BW MDXdriver 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 factthat the report now contains:


BO100 Lesson: Crystal Reports against SAP BW cubes

Figure 122: SAP BW cubes

• All characteristics from the underlying cube.• All available hierarchies for all characteristics.• All display attributes.• All keyfigures.

Figure 123: Field Explorer in Crystal Reports



The figure shows how a characteristic and all its hierarchies will be displayed inthe Field Explorer in Crystal Reports. The characteristic Material is representedwith nine hierarchies which are grouped underneath the actual characteristic.The key and description values underneath the actual characteristic representthe non-hierarchical display.

When connecting against a cube directly, the following metdata is not available:

• Navigational attributes• Restricted keyfigures• Calculated keyfigures• SAP variables


BO100 Lesson: Crystal Reports against SAP BW cubes

Lesson Summary

You should now be able to:• Create reports against a BW cube directly



Lesson: Crystal Reports and keydate variables

Lesson OverviewIn this lesson, you will learn how a keydate variable is used in the Crystal Reportsdesigner.


• Create reports with keydate variables

Business ExampleYou are a report designer and need to create a report against an SAP BW systemwith keydate variables.

Keydate variables in Crystal ReportsA keydate variable can influence the following metadata and data of the underlyingSAP BW system:

• Master data.• List of available hierarchies.• Hierarchy structures.

A keydate variable in Crystal Reports is shown as a date variable with a calendarcontrol and each time the user changes the date entry, Crystal Reports will sendthe new keydate to the underlying SAP BW server to retrieve the correct data.


BO100 Lesson: Crystal Reports and keydate variables

Exercise 17: Creating a new report with akeydate variable

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a report against an SAP BW query with a keydate variable

Business ExampleYou are a report designer and need to create a Crystal Report object using anSAP BW query with a keydate variable.

Task:Follow the following steps to create a new report against an SAP BW query withdisplay attributes:





5. Select the BO100 keydate variable (technical name: BO100_Q11_1) query.


7. Create a hierarchical grouping for the Material characteristic.

8. Include the Sales Volume (MC) and build a summary for the group.


10. Enter different dates for the keydate variable.






Solution 17: Creating a new report with akeydate variableTask:Follow the following steps to create a new report against an SAP BW query withdisplay attributes:


a) Double-click on SAP Logon Pad and make sure that you have a entryfor the BW system





c) Click OK.





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






b) Click the Database tab and choose the Option <Show Description>.

c) Click OK.



f) Click the plus sign in front of T_BO1001_T_BO100_Q11_1.


7. Create a hierarchical grouping for the Material characteristic.

a) Select the menu Insert → Group.

b) Sorted the group by Material.

c) Navigate to the Options tab.

d) Select the Customize Group Name Field check box.

e) Select the material medium name.




8. 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” allowscreating a group summary by adding values from the lowerlevel of a hierarchy up to a higher aggregated level. An examplewould be to summarize salary figures from the lowest level ofan organization hierarchy up to the top level of the hierarchy.

Note: In the case of an SAP BW query as a data source theoption “Summarize across hierarchy” is not necessary becausethe underlying SAP BW query returns the aggregated valuesfor 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.


a) SelectView → Preview.

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









e) Click OK.



b) Create your own report folder if it has not been created yet.


d) Click Save.





d) Click Log On.







Lesson Summary

You should now be able to:• Create reports with keydate variables


BO100 Lesson: SAP variable personalization

Lesson: SAP variable personalization

Lesson OverviewIn this lesson, you will learn about variable personalization and how this feature isused in Crystal Reports and SAP BusinessObjects Enterprise.


• Describe variable personalization

Business ExampleYour business reporting group requires variable personalization in Crystal reportswhen querying against SAP BW InfoProviders.

What is personalization?Reports that are based on BW queries potentially make use of variables, whichcontain 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 valuethat will be used to run the report.

• If the query does not allow the variable to accept input, you are only allowedto select from a list of predefined values—one of which will be used to runthe report.

In SAP Business Explorer (BEx), personalization enables users to enter a value forthe variable and save it as their personal default value. As a result, when the reportis 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 personalizedvalues are available for them to use.

Personalized values are user-specific—that is, the personalized values that usersset for themselves are not implemented onto other users. Other users who workwith the same report can set their own personalized values, or use any of the presetvalues that are given to the variable.

Personalization is a supported feature of BusinessObjects XI Integration for SAPSolutions. Reports based on SAP BW queries can leverage this functionalityin InfoView.

The user is able to read and write personalized values in the prompting interfaceby using the personalization icon.



Lesson Summary

You should now be able to:• Describe variable personalization


BO100 Unit Summary

Unit SummaryYou should now be able to:• Describe the differences between BWMDX 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 Summary BO100



Test Your Knowledge

1. Which of the following is true describing the functionality of BW MDXdriver?Choose the correct answer(s).□ A It offers each level of the hierarchy as a separate field and also

offers parent child-relationship information.□ B It only offers multiple levels of the hierarchy as a single field.□ C It only offers each level of hierarchy as a separate field.□ D It only offers a parent child relationship.

2. When creating a report based on a query with two structures Crystal Reportstries to resolve the structure containing the keyfigures and the structurerepresenting the special grouping into one single field?Determine whether this statement is true or false.□ True□ False



Answers

1. Which of the following is true describing the functionality of BW MDXdriver?

Answer: D

Correct answer is D.

2. When creating a report based on a query with two structures Crystal Reportstries to resolve the structure containing the keyfigures and the structurerepresenting the special grouping into one single field?

Answer: False


Unit 10Voyager with SAP BW

Unit OverviewThis 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 ContentsLesson: Creating connections to SAP BW with Voyager .. . . . . . . . . . . . . . . . .356

Procedure: To create a new connection towards SAP BW .... . . . . . . .357Procedure: To use the connectivity in Voyager .. . . . . . . . . . . . . . . . . . . . . . .361

Lesson: SAP BW metadata in Voyager .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365Lesson: SAP Variables with Voyager .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371

Procedure: To create a new Voyager connection using SAPvariables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372Procedure: To use the connectivity in Voyager .. . . . . . . . . . . . . . . . . . . . . . .373Procedure: To use the connectivity in Voyager with a hierarchy andhierarchy node variable .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376Procedure: To use the connectivity in Voyager with a keydatevariable.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378Procedure: To use more than one connection in a VoyagerWorkspace: .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380Exercise 18: Creating a new Voyager workspace using an SAP BWquery with variables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381


Unit 10: Voyager with SAP BW BO100

Lesson: Creating connections to SAP BW with Voyager

Lesson OverviewIn this lesson, you will learn how to establish a connection to SAP BW for Voyager.


• Create a connection towards SAP BW for Voyager

Business ExampleWith SAP BusinessObjects Voyager, your business analysts can explore onlineanalytical processing (OLAP) data using a tool designed specifically for them –one that delivers a full range of functions for the analysis of multidimensionaldata sets. Analysts can quickly answer business questions and then share theiranalysis and workspace with others, spreading knowledge beyond the confines ofa single department or group

What is in Voyager?SAP BusinessObjects Voyager offers analysts a modern and advanced userinterface and enables them to:

• Discover trends, outliers, and details stored in their financial systems withoutthe help of a database administrator.

• Get answers to business questions while viewing multidimensional datasets quickly and efficiently.

• Access the full range of OLAP data sources available within the organizationand share results using a simple, intuitive Web interface.

• Access multiple different OLAP sources in the same report to get acomprehensive view of the business and the cross-impact that one trendmay 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 BWVoyager connections are stored in the Central Management Console (CMC) andneed to be defined in the CMC before the user can leverage them in the Voyagerclient.


BO100 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 125: Log on

3. Click Voyager Connections.

Figure 126: Voyager Connections

4. Click New Connection.

Figure 127: New Connection




5. Select SAP Business Information Warehouse in the list of Provider.

Figure 128: 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 basedconfiguration or a message server based configuration. This can beswitched with the property Server Type.

8. Click Connect.

Note: The Save Language option allows you to define if thelanguage should be saved with the connection or if the preferredviewing local from the user preferences should be used.

Figure 129: Connect

9. Enter the User and Password to authenticate against the SAP BW server.Continued on next page



10. Click OK.

Figure 130: OK

Note: The Cube Browser shows the BW cubes and queries that canbe used for a Voyager connection. You can choose between theCaption (Description in BW term) and the Name (Technical Name inBW term) of the objects.

11. Select the SAP BW query from the Cube Browser.

12. Click Select.

Figure 131: Select




13. Define the Authentication.

Note: You can choose between Prompt, SSO, SNC, and UserSpecified. The options SSO and SNC require specific configurationsteps for the SAP server and the BusinessObjects Enterprise system.The option User Specified allows to define a user and password thatwill be shared by all users leveraging this connection.

14. Click Save.

Figure 132: Save



To use the connectivity in Voyager

1. Start InfoView (Start > Programs > BusinessObjects XI Release 3 >BusinessObjects Enterprise > BusinessObjects Enterprise Java InfoView).

Figure 133: Start InfoView

2. Select SAP as Authentication.

Figure 134: SAP as Authentication


4. Click Log On.




Figure 135: InfoView


6. Select the menu New → Voyager Workspace.

Figure 136: Voyager Workspace

7. Select the connection.

Figure 137: Connection

8. Click OK.

9. Enter User Credentials for the connection and click OK.






Note: The available items from the underlying SAP BW query willbe shown in the Voyager Workspace.



Lesson Summary

You should now be able to:• Create a connection towards SAP BW for Voyager


BO100 Lesson: SAP BW metadata in Voyager

Lesson: SAP BW metadata in Voyager

Lesson OverviewIn this lesson, you will learn about the available metadata from SAP BW andhow this is used in Voyager.


• Describe the available information from SAP BW inside Voyager

Business ExampleYou plan to implement Voyager with SAP BW access. You need a comprehensiveoverview of how they integrate and complement each other. You need thisinformation to understand the relationship between BEx queries and Voyager.

SAP BW metadata in VoyagerThe following table shows an outline of the available metadata from SAP BW andhow this is made available in a Voyager workspace.

BW query element Voyager

Characteristic Dimension

Hierarchy Each available hierarchy is representedas a dimension

Keyfigure Measure

Calculated keyfigure Measure element in the folderKeyfigure (Information about thecalculation is not available in Voyager)

Restricted keyfigure Measure element in the folderKeyfigure (Information about thecalculation is not available in Voyager)

Filter Filters will be applied to the underlyingquery but are not visible in the VoyagerWorkspace



BW query element Voyager

Navigational attribute Dimension

Display attribute Display Attributes are not available inVoyager except the short, medium andlong description of a dimension

SAP variables Parameters that can be used in theVoyager Workspace

CharacteristicsThis image shows a simple SAP BW query in the SAP BW Query Designer:

Figure 140: BW query

The query contains 2 characteristics (Sold-to party and Material) and twoKeyfigures (Sales Voume (MC) and Sales Volume EUR). All characteristicsavailable 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 ofitems will show as in the image.



Figure 141: List of items

• For characteristic Material, each available hierarchy is shown even thoughthe SAP BW query did not include a specific hierarchy.

• The non-hierarchical display for characteristic Material is listed as an optionas well and can be identified based on the name of the characteristic (forexample, 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 howto display the characteristic.



Figure 142: Choose how to display the characteristic

Note: The availability of a short, medium, and long description dependson the data modeling in SAP BW.

Key figures, units, and currenciesAll key figures from the underlying SAP BW query are represented in Voyagerin a group called Key Figures and can be used as a group or individually in theVoyager Workspace.

Figure 143: Key figures

When the key figures are used in the Voyager Workspace, the key figure ispresented together with the configured formatting and unit information.



Figure 144: Key figure presented

The image above shows that the key figures Sales Volume (MC) and Sales VolumeEUR are presented with the currency information and all key figures are presentedbased on the user’s preference for formatting.

In case the user wants to switch to a different formatting the SAP BW basedformatting can be disabled in the standard Format cell values dialog box.




Lesson Summary

You should now be able to:• Describe the available information from SAP BW inside Voyager


BO100 Lesson: SAP Variables with Voyager

Lesson: SAP Variables with Voyager

Lesson OverviewIn this lesson, you will learn about the usage of SAP BW variables in a VoyagerWorkspace.


• Describe how to create a simple Voyager Workspace with various typesof SAP variables

Business ExampleYou plan to implement Voyager with SAP BW access. You need to create a newVoyager connection using SAP variables.

Voyager and simple SAP variablesVoyager offers a very similar prompting experience compared to the BEx Analyzerand BEx Web reporting. When creating a Voyager Workspace based on anSAP BW query with variables, each variable becomes a prompt in the VoyagerWorkspace.



To create a new Voyager connection using SAPvariables

Note: This procedure is the same as creating connections withoutvariables


2. Log onto the system with an administrative account.

3. Click Voyager Connections.

4. Click New Connection.

5. Select SAP Business Information Warehouse in the list for Provider.

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 basedconfiguration or a message server based configuration. This can beswitched with the property Server Type.

8. Click Connect.

Note: The Save Language option allows you to define if thelanguage should be saved with the connection or if the preferredviewing local from the user preferences should be used.

9. Enter the User and Password to authenticate against the SAP BW server.

10. Click OK.

Note: The Cube Browser shows the BW cubes and queries that canbe used for a Voyager connection. You can choose between theCaption and the Name of the objects.

11. Select the SAP BW query from the Cube Browser.

12. Click Select.

13. Define the Authentication.

Note: You can choose between Prompt, SSO, SNC, and UserSpecified. The options SSO and SNC require specific configurationsteps for the SAP server and the BusinessObjects Enterprise system.The option User Specified allows you to define a user and passwordthat will be shared by all users leveraging this connection.

14. Click Save.



To use the connectivity in Voyager

1. Start InfoView



4. Click Log On.




8. Click OK.

Figure 146: SAP BW query contains an SAP variable

Note: Because the underlying SAP BW query contains an SAPvariable, Voyager asks you to provide a value before providing alist of dimensions.

9. Open the member selector to pick the From Value.




Figure 147: Member Selector

10. Open the member selector to pick the To Value.

Figure 148: Member Selector




11. Select the required values.

12. Click OK.

Figure 149: 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 theData tab.

Using hierarchy and hierarchy node variables inVoyagerHierarchy and hierarchy node variables can depend on each other in the casewhere the hierarchy and hierarchy node variable are based on the identicalcharacteristic and hierarchy. This situation results in prompts depending on eachother in Voyager.

You first create a new Voyager connection with a hierarchy and hierarchy nodevariable following the same steps as you were creating a new Voyager connectionusing SAP variables before. Then you are ready to use the connectivity in Voyager.



To use the connectivity in Voyager with a hierarchyand hierarchy node variable

1. Start InfoView2. Select SAP as Authentication.


4. Click Log On.




8. Click OK.

Note: The two variables are dependent on each other which canbe recognized based on the situation that the second variable isindented. The second variable is not active and you cannot choose avalue before setting a value for the first variable.

Note: Each time the user changes the value for the hierarchy variablethe 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 includethe selected or fixed hierarchy (not all hierarchies as in the case whenno 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 selectorwill only show elements that have been selected with the hierarchynode variable.



Voyager and SAP keydate variablesA keydate variable can influence the following metadata and data of the underlyingSAP 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 forthe list of values of time-dependent variables.

Each time the user changes the value for the keydate variable Voyager removesthe existing values for any other variable and refreshes the list of values.

You first create a new Voyager connection with a keydate variable following thesame steps as you were creating a new Voyager connection using SAP variablesbefore. Then you are ready to use the connectivity in Voyager.



To use the connectivity in Voyager with a keydatevariable

1. Start InfoView



4. Click Log On.




8. Click OK.

Note: The keydate variable allows you to enter the value via acalendar control.

9. Enter a value for the keydate variable.

10. Click OK.

Figure 150: Keydate Variable.

11. Define the rows and columns.

12. Refresh the report with different keydate variables.



Multiple connections in one Voyager WorkspaceVoyager can leverage multiple connections in a single workspace. For SAPthis means the user can have multiple queries or the same query with differentvariables in an identical workspace.



To use more than one connection in a VoyagerWorkspace:

1. Start InfoView.2. Select SAP as Authentication.


4. Click Log On.




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 oneworkspace the user is able to leverage different sets of prompts(including keydate variables) for the same query in one workspace.



Exercise 18: Creating a new Voyagerworkspace using an SAP BW query withvariables

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new Voyager Workspace using an SAP BW query with SAP

variables

Business ExampleYou are a report designer and need to create a Voyager Workspace using anSAP BW query.

Task:[Enter a high level description of the task the learner will perform in this exercise.]


2. Log onto BusinessObjects Enterprise and create a new connectionusing 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.


6. Refresh the variables and change the value for the keydate variable.

7. Create another Voyager Workspace using a BW query with hierarchy andhierarchy node variable.



Solution 18: Creating a new Voyagerworkspace using an SAP BW query withvariablesTask:[Enter a high level description of the task the learner will perform in this exercise.]


a) Select Start→ Programs→BusinessObjects XI 3.1→BusinessObjectsEnterprise Client Tools → BusinessObjects Central ManagementConsole.

2. Log onto BusinessObjects Enterprise and create a new connectionusing the query BO100 keydate variable (technical name:T_BO1001/‘T_BO100_Q11_1).

a) Log onto the system with an administrative account.

b) Click Voyager Connections.

c) Click New Connection.

d) Select SAP Business Information Warehouse in the list for Provider.

e) Enter a Name and Description for the connection.

f) Enter the System, Server, System Number, Client and Language.

g) Click Connect.

h) Enter the User and Password to authenticate against the SAP BW server.

i) Click OK.

j) Select the SAP BW query from the Cube Browser.

k) Click Select .

3. Save the connection.




4. Create a new report with Voyager using the connection.

a) Start InfoView.

b) Select SAP as Authentication.


d) Click Log On.


f) Select the menu New → Voyager Workspace.

g) Select the connection.

h) Click OK.

i) The keydate variable allows you to enter the value via a calendarcontrol. Enter a value for the keydate variable.

Figure 151: Calender control


a) Select the Product Hierarchy 1 for the rows.

b) Select the keyfigures for the columns.

6. Refresh the variables and change the value for the keydate variable.

7. Create another Voyager Workspace using a BW query with hierarchy andhierarchy node variable.



Lesson Summary

You should now be able to:• Describe how to create a simple Voyager Workspace with various types

of SAP variables


BO100 Unit Summary

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


Unit Summary BO100



Test Your Knowledge

1. The IT Director needs a BI consultant to analyze the last few years helpdesk transactions by service team utilization, season/time of year trends,cost center usage, response times per service area. What tool should theconsultant use? feeding into the dashboard remains unchanged until the endof the current business day. During the day, the financial analyst team areconstantly running BW queries to perform financial modeling which places alot of peak load on the same BW server during daytime hours, and CustomerSupport and Help desk run on demand operational Webi queries on theircall queues. The BW server has BI Accelerator added on (BIA). Over 500hundred employees.Choose the correct answer(s).□ A Web Intelligence□ B Crystal Reports□ C Voyager and/or SAP Business Explorer (BEx)□ D Xcelsius



Answers

1. The IT Director needs a BI consultant to analyze the last few years helpdesk transactions by service team utilization, season/time of year trends,cost center usage, response times per service area. What tool should theconsultant use? feeding into the dashboard remains unchanged until the endof the current business day. During the day, the financial analyst team areconstantly running BW queries to perform financial modeling which places alot of peak load on the same BW server during daytime hours, and CustomerSupport and Help desk run on demand operational Webi queries on theircall queues. The BW server has BI Accelerator added on (BIA). Over 500hundred employees.

Answer: C

Voyager - slice and dice, hierarchies, expert view on BEx query or BWInfoCube.


Unit 11Xcelsius with Live Office

Unit OverviewThis unit provides you with an overview of using Xcelsius with Live Office toretrieve SAP data. You will learn how to connect Live Office to SAP data sourcesand create an Xcelsius dashboard using Live Office with Web Intelligence andCrystal Report as a data source


• 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 ContentsLesson: Xcelsius with Live Office... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390

Exercise 19: Creating a new Live Office document based on CrystalReports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Exercise 20: Create a Live Office Document from a Web IntelligenceReport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403

Lesson: Creating an Xcelsius dashboard with Live Office ... . . . . . . . . . . . . .409Exercise 21: Creating a new Xcelsius dashboard with Live Office ..411


Unit 11: Xcelsius with Live Office BO100

Lesson: Xcelsius with Live Office

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


SAP data sources

Business ExampleYou are a business user who needs to transform complex business data intoactionable visual information. You need to create rich interactive presentationsfor your business needs.

What is in Live OfficeSAP BusinessObjects Live Office software provides you with the followingfeatures and functions:

• Create simple queries and summary reports based on verifiable, up-to-date,real-time information, to analyze data such as quarterly sales figures; answerimportant business questions; and make informed decisions.

• View, modify, and refresh existing queries quickly to suit your businessneeds.

• Share the results with your colleagues securely over the web or intranet forcollaborative, strategic decision making.

• Format the imported data by using standard Microsoft Excel functionalityand the features of Live Office.


BO100 Lesson: Xcelsius with Live Office

Advantage of Live OfficeSAP BusinessObjects Live Office software provides the following features andfunctions:

• Self-service access – Access business intelligence (BI) content directlywithin Microsoft Office – no IT assistance required. Select data from a reportfrom Crystal Reports software, an SAP BusinessObjects Web Intelligencedocument, or through ad hoc data selection – all within Microsoft Office.

• Trusted information – With SAP BusinessObjects Live Office, yourMicrosoft Office documents display data from the same trusted BI source thatsupports your organization’s decision making and enterprise performance.

• BI in Microsoft Office Outlook – Embed business intelligence directlyin your email messages using Microsoft Outlook. The underlying reportautomatically retains your security parameters to ensure that recipients seeonly 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 thedata – in your Microsoft Office document. Instant refreshing and refilteringput the most accurate, up-to-date data at your fingertips for more confidentdecision making.

• Formatting and calculations – Once you have embedded your BI data, youcan format and perform calculations using familiar features of MicrosoftExcel, Microsoft PowerPoint, and Microsoft Word. All formatting andcalculations are retained.

• Shared documents – Publish Microsoft Office documents to SAPBusinessObjects Enterprise software for instant access over the web, oremail your live Microsoft Office documents. Security is maintained, evenwhen you share the document outside your firewall.

What is Xcelsius?Xcelsius provides a simple, personalized view of your organization's data toenable better understanding, insightful decision-making, and scenario evaluation

Business decisions require immediate answers. With Xcelsius, yourdecision-makers gain real-time insights to critical business data enabling businessanalysis on key data your users can trust and refresh instantly The end resultis an interactive dashboard with live data connectivity for accurate, consistentinformation, 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.



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 XcelsiusXcelsius can connect to your SAP data sources in two ways. Xcelsius visualizationcan leverage Live Office to connect to a Crystal report or Web Intelligencedocument. In addition, the visual model can connect directly to an universe viaWeb services created with Query as a Web Service.

Figure 152: Xcelsius Connectivity to SAP data sources

Leveraging Crystal Reports and Web IntelligenceLive Office is able to leverage Crystal Reports documents, Web Intelligencedocuments and Universes for building new Live Office documents. With LiveOffice, you can leverage the power, convenience, and reliability of Crystal Reportsfunctionality from within the Microsoft Office applications to make businessdecisions. 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 improveddecision making. In addition, you have the comfort of knowing that the datayou are accessing is reliable, up-to-date, and easily refreshed on demand fromthe database. Crystal Reports content can be added from the Live Office menuor by using the Live Office toolbar. Both methods launch the easy to use "LiveOffice Insert Wizard" which easily guides you through how to choose a report,select Crystal Reports data objects, and insert them in your Microsoft applicationsas Live Office objects to share with your colleagues.

To leverage SAP data sources in Live Office, you first need to create a Crystalreport or Web Intelligence document based on the SAP data sources.





Exercise 19: Creating a new Live Officedocument based on Crystal Reports

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new Live Office document using Crystal Reports as a source

Business ExampleYou are a report designer who needs to create a LiveOffice document using anexisting 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 LiveOffice Insert Wizard

Tasks

Choose Document Browse available reports.

Choose Data Select the Crystal Reports fields you want to use tocreate your Live Office object.

Set Filters Select filters to apply to the data in your Live Officedocuments.

Summary Type the name of your Live Office object and verifyits path in the repository before inserting it into yourdocument.

1. Start Microsoft Excel.

2. Enter the information in the Web Service URL and System fields:

User Name BO100-##


Web Service URL http://twdfXXXX:8080/dsws-bobje/services/session

System TWDFXXXX

Authentication SAP




3. Once you log onto Live office successfully, go through the Live Office InsertWizard 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 yourdata as fields. You can apply filters to all available fields in your CrystalReports documents to restrict the data in your report. Select sales valuesthat are greater than 10000 as filter.

6. Complete the summary page in the Insert Wizard. This is the last screenin Live Office Insert Wizard before the current object is inserted into yourMicrosoft Office application

7. Save the Live Office document to SAP BusinessObjects Enterprise

8. Modify the report so that it refreshes on demand.



Solution 19: Creating a new Live Officedocument based on Crystal ReportsTask: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 LiveOffice Insert Wizard

Tasks

Choose Document Browse available reports.

Choose Data Select the Crystal Reports fields you want to use tocreate your Live Office object.

Set Filters Select filters to apply to the data in your Live Officedocuments.

Summary Type the name of your Live Office object and verifyits path in the repository before inserting it into yourdocument.

1. Start Microsoft Excel.

a) Select Microsoft Excel: Programs → Microsoft Office → MicrosoftOffice Excel 2003.

2. Enter the information in the Web Service URL and System fields:

User Name BO100-##


Web Service URL http://twdfXXXX:8080/dsws-bobje/services/session

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

e) Enter the information in the Web Service URL and System fields.

f) Select SAP as Authentication and click Logon.




g) Click OK.

3. Once you log onto Live office successfully, go through the Live Office InsertWizard 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 153: Live Office Insert Wizard




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 Reportobject, 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 theright side of the window.

d) Click Next.




5. Set Filter- The Set Filters page will only appear if you have inserted yourdata as fields. You can apply filters to all available fields in your CrystalReports documents to restrict the data in your report. Select sales valuesthat are greater than 10000 as filter.

a) In the Set Filters page of the Live Office Insert Wizard, click the fieldthat you want to filter. Select Sales Values.

b) Select a operator is greater than from the Operators drop-down liston the right.

c) Enter the value 1000000.


d) Click Next.

6. Complete the summary page in the Insert Wizard. This is the last screenin Live Office Insert Wizard before the current object is inserted into yourMicrosoft Office application

a) Review the information on the summary page and add GR## in thebeginning of the object name.

Note: This is the name of the imbedded object, not the finishedlive office enabled workbook. The workbook will be saved inthe next step.





b) Click Finish to insert your Live Office object into your Microsoft Officedocument.

c) A progress bar appears as your Live Office object is inserted in yourMicrosoft Office document.

d) The Live Office document will be displayed in the spreadsheet insidethe Xcelsius.





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 → <SID>CLNT900.

c) Click Save.

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



Exercise 20: Create a Live OfficeDocument from a Web Intelligence Report

Exercise ObjectivesAfter completing this exercise, you will be able to:• To create Live Office Document from a Web Intelligence Report

Business ExampleYour business requirements indicate that you need to create a new Live Officedocument. You must base this new Live Office document on an existing WebIntelligence 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

ChooseDocument

Browse available reports.

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

Set Filters Select filters to apply to data that you insert as fields in yourLive Office documents.

Summary Type the name of your Live Office object and Verify its pathin the repository before inserting it into your document.

1. Start the Live Office Application and insert the Web Intelligence Report.

Enter with the BusinessObjects Enterprise credentials

2. Verify the information in the Web Service URL and System fields

User Name BO100##

Password Assigned Password

Web Service URL http://twdfXXXX:8080/dswsbobje/services/ses-sion

System twdfXXXX:6400

Authentication SAP




Task 2:Once you able to logon to Live office successfully now its turn to go throughthe Wizard step by step.

1. The first screen is Choose Document. Choose the following document.

Expand The folder Public Public → SAP → 2.0 → <SID>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



Solution 20: Create a Live OfficeDocument from a Web Intelligence ReportTask 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

ChooseDocument

Browse available reports.

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

Set Filters Select filters to apply to data that you insert as fields in yourLive Office documents.

Summary Type the name of your Live Office object and Verify its pathin the repository before inserting it into your document.

1. Start the Live Office Application and insert the Web Intelligence Report.

Enter with the BusinessObjects Enterprise credentials

a) Click Start → Programs → Microsoft Office

b) Click LiveOffice, Click Insert and then select Web Intelligence Content.

c) Enter your BusinessObjects Enterprise logon credentials in the fields ofUser name and Password

2. Verify the information in the Web Service URL and System fields




User Name BO100##

Password Assigned Password

Web Service URL http://twdfXXXX:8080/dswsbobje/services/ses-sion

System twdfXXXX:6400

Authentication SAP

a) Verify the information in the Web Service URL and System fieldsto ensure that the application is pointing to the correct CentralManagement System (CMS).

b) Select an authentication method as SAP from the drop-down list, clickLog On and then click OK.

c) Also make sure that you are able to see Validation succeeded as amessage at the bottom of the Screen

Task 2:Once you able to logon to Live office successfully now its turn to go throughthe Wizard step by step.

1. The first screen is Choose Document. Choose the following document.

Expand The folder Public Public → SAP → 2.0 → <SID>CLNT900 →GR## Sales Order Report with Optional Prompt.

This is one of the Web Intelligence reports that you created earlier..

a) Navigate to the folder that contains the report you want to use. Usingthe buttons above the left-hand pane, you can switch between Folderand Category views for easy navigation.

b) Expand The folder Public → SAP → 2.0 → <SID>CLNT900

c) In the right-hand pane of the "Choose Document" page, select thereport you want to use, GR## Sales Order Report with OptionalPrompt, and click Next.

2. The next page of the Live Office Insert Wizard is the Choose Data page.Select the entire query.

a) Place your cursor on the results of the query. Double-click to selectthe entire query.

b) Press Next.

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

a) From the "Summary" page, name your Live Office object and verify itspath in the BusinessObjects repository

b) Click Finish to insert your Live Office object into your Microsoft Officedocument.

c) A progress bar appears as your Live Office object is inserted in yourMicrosoft Office document.

d) You now have a report in Microsoft office Excel which is created froma 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. LiveOffice→ Publish to BusinessObjects Enterprise→ Save As New toBusinessObjects Enterprise. Select from the folder list Public →SAP→2.0→ <SID>CLNT900. Enter the Description: GR## Live OfficeSales Orders from Web Intelligence Report. .



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


SAP data sources


BO100 Lesson: Creating an Xcelsius dashboard with Live Office

Lesson: Creating an Xcelsius dashboard with Live Office

Lesson OverviewPreviously you created a Crystal Report document retrieving data from SAP BWand used Live Office to show the data in Microsoft Excel. As a next step, you willuse the Live Office document as a source for the Xcelsius dashboard.


• Create an Xcelsius dashboard with Live Office

Business ExampleYou are a report designer who needs to create interactive dashboards from aLive Office document with SAP datasources. The dashboards enable you tomonitor business performance, identify critical data relationships, and use what-ifscenarios to understand potential performance.

What is Dashboard?Dashboard is a user interface that organizes and presents information in a way thatis easy to read with a great look and feel. A Xcelsius dashboard is more likely tobe interactive and user friendly. It is used by higher management

To create Xcelsius dashboard, you run a Crystal Report to retreive SAP ERPor BW data. The data is saved to a Microsoft Excel file which is tehn used byXcelsius to create interactive dashboards.

Note:

• 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





Exercise 21: Creating a new Xcelsiusdashboard with Live Office

Exercise ObjectivesAfter completing this exercise, you will be able to:• Build a new Xcelsius dashboard using Live Office as a source

Business ExampleYou are a report designer creating an Xcelsius dashboard and building theunderlying Crystal Report and LiveOffice documents.

Task: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 Xcelsiusfile to BusinessObjects Enterprise.

5. View the dashboard with Single-Sign-On in InfoView.



Solution 21: Creating a new Xcelsiusdashboard with Live OfficeTask: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 compatibilitymode, click Yes to proceed. For the second window aboutaborting 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 loginto Enterprise here.

System TWDFXXXX

User name administrator

Password Assigned password foradministrator


d) Click yes on the prompt message

e) Navigate to the SAP → 2.0 → <SID>CLNT900

f) Select the Live Office document you created previously.

g) Click Open. The Live Office document will be displayed in thespreadsheet inside the Xcelsius.

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




Figure 158: Data Manager

d) Replace the <webserver> entry with the name of the assigned server.


e) Click the Usage tab.

f) Set the Refresh on Load property.





g) Close the Data Manager.

3. 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 chartcomponent onto the Xcelsius canvas.




Figure 161: 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 thevalues: $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 thelabels: $A$2:$A$10.

Figure 162: Pie Chart




4. View the dashboard with Single-Sign-On in InfoView and save the Xcelsiusfile to BusinessObjects Enterprise.

a) Select File → Preview.

Note: Because you are not authenticated againstBusinessObjects Enterprise at this time a logon mask will comeup and ask for BusinessObjects Enterprise credentials. Usethe SAP Authentication and the SAP credentials to leverageSingle-Sign-On from the Xcelsius Dashboard to LiveOfficeand Crystal Reports.

b) Select the menu File → Export → Business Objects Platform....

Note: When exporting to the Business Objects Platform theactual Xcelsius document (runtime flash document) is beingstored on the platform. When selecting the menu File → Saveas the design of the Xcelsius document is being stored toBusinessObjects Enterprise.

c) Navigate to SAP → 2.0 → <SID>CLNT900 in your BusinessObjectsEnterprise system.

d) Enter a file name GR## Xcelsius dashboard with Live Office.

e) Click Save.

5. View the dashboard with Single-Sign-On in InfoView.

a) Select Programs → BusinessObjects XI 3.1 → BusinessObjectsEnterprise Client Tools → BusinessObjects Enterprise Java InfoView.

b) Enter the BusinessObjects Enterprise Server name twdfXXXX.

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


e) Click Log On.

f) Click Document List

g) Navigate to SAP → 2.0 → <SID>CLNT900 in your BusinessObjectsEnterprise system.

h) View your Xcelsius dashboard flash file in InfoView.



Lesson Summary

You should now be able to:• Create an Xcelsius dashboard with Live Office


Unit Summary BO100

Unit SummaryYou should now be able to:• Connect Live Office to BusinessObjects products.• Create a Live Office document with Crystal Reports based on SAP data


SAP data sources• Create an Xcelsius dashboard with Live Office



Test Your Knowledge

1. Which of the following tools allow you to insert Web Intelligence Contentdirectly into excel?Choose the correct answer(s).□ A Web Intelligence Content Wizard□ B Universe Insert Wizard□ C Live Office Insert Wizard□ D Web Intelligence Insert Wizard



Answers

1. Which of the following tools allow you to insert Web Intelligence Contentdirectly into excel?

Answer: C



Unit 12Xcelsius with Query as a Web Service

(QaaWS) on BW

Unit OverviewThis 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 Xcelsiusto 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 ContentsLesson: Query as a Web Service... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .422

Exercise 22: Creating a new Query as a Web Service ... . . . . . . . . . . . . .425Lesson: Xcelsius and Query as a Web Service... . . . . . . . . . . . . . . . . . . . . . . . . . .432

Exercise 23: Creating a new Xcelsius dashboard using Query as aWeb Service... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435Exercise 24: Creating a new Xcelsius dashboard based on QaaWSwith SAP variables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .441


Unit 12: Xcelsius with Query as a Web Service (QaaWS) on BW BO100

Lesson: Query as a Web Service

Lesson OverviewIn this lesson, you will learn about how you can use QaaWS to connect to SAPdata sources.


• Create a Query as a Web Service against SAP data sources with variables

Business ExampleQuery as a Web Service lets you create custom web services for specific queriesusing Business Objects Web Services. You access queries to build applicationsthat use the same semantic layer as the rest of the BusinessObjects suite.

Business Intelligence (BI) content is usually bound to a specific user interfaceof BI tools. Query as a Web Service changes this by allowing BI content to bedelivered to any user interface that can process Web Services.

Using Query as a Web Service, business users define their own query from auniverse, and then easily and securely publish that query as a standalone webservice.

Query as a Web Service provides new types of user-driven client solutions forbusinesses. For example, it enables Xcelsius to aggregate multiple disparate datasources into a trusted BI view.

Query as a Web Service also enables a range of client-side solutions in toolssuch as:

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

OLAP Universe with SAP data sourcesQuery as a Web Service creates a query based on a universe and publishes theresulting 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, Queryas a Web Services enables Xcelsius to aggregate multiple disparate data sourcesinto a trusted BI view.


BO100 Lesson: Query as a Web Service

Xcelsius is able leverage Query as a Web Service for connectivity. You run Queryas a Web Service against Universes, in particular the OLAP Universes that connectto SAP BW. This approach allows you to combine multiple datasources insideExcel and these multiple Excel files can be used by multiple web services. The firststep is to build a new OLAP Universe on top of an SAP BW query. After creatingthe OLAP Universe, you can create the web service on top of the OLAP Universe.

Figure 163: Query as a Web Service

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

• SAP BW Queries• BW MultiProviders• BW InfoCubes





Exercise 22: Creating a new Query as aWeb Service

Exercise ObjectivesAfter 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 ExampleYour business reporting group requires a Query as a Web Service when queryingagainst SAP BW InfoProviders.

Task:Create a new OLAP Universe based on the BW Query with variables. Then createa new QaaWS based on the OLAP Universe. Publish the web service after youcreate the QaaWS.

1. Create a new OLAP Universe based on the BW Query BO100 XcelsiusQaaWs 01 (technical name: T_BO100_Q16_1).

Field Name Value

User Assigned user


Client 900



System number 50


2. Save the OLAP Universe and export it to BusinessObjects Enterprise.


4. Launch Query as a Web Service.

5. Enter the host definition.

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.

10. Publish the web service.



Solution 22: Creating a new Query as aWeb ServiceTask:Create a new OLAP Universe based on the BW Query with variables. Then createa new QaaWS based on the OLAP Universe. Publish the web service after youcreate the QaaWS.

1. Create a new OLAP Universe based on the BW Query BO100 XcelsiusQaaWs 01 (technical name: T_BO100_Q16_1).

Field Name Value

User Assigned user


Client 900



System number 50


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




Authentication SAP

c) Click File > New.

d) Click New to create a new connection.

e) Click Next.




f) Select SAP -> SAP Business Warehouse from the list.

g) Enter a connection name.

h) Click Next.

i) Enter the User name, Password, and Language.

j) Enter the Client, Application Server, and System Number based on theSAP server details.


k) Set the Authentication Mode to Use specified username andpassword.

l) Click Next.

m) Open the list of available cubes by clicking the plus sign next to OLAPCubes.

n) Navigate to BO100 cube and select ‘BO100 Xcelsius QaaWs 01(technical name: T_BO100_Q16_1)'.

o) Select the required query and Click Next.

p) Click Finish.

q) Enter the Universe name T_BO100_Xcelsius_QaaWS01_##.

r) Navigate to the Controls tab.

s) Uncheck all Query Limits.

t) Click OK.



b) Ensure the destination folder is set to BusinessObjects Universes,and ensure the universe name is set to T_BO100_Xcel-sius_QaaWS01_GR##.unv, then press Save.









4. Launch Query as a Web Service.

a) Select Program → BusinessObjects XI 3.1 → BusinessObjectsEnterprise Client Tools→ Query as a Web Service.

5. Enter the host definition.

a) Click Add.

b) Create QaaWS with the following credentials.

Name <Computer name assigned by the instructor> (Forexample: twdfXXXX)

URL <Auto populated>

CMS <Computer name assigned by the instructor> (Forexample: twdfXXXX)

User <Assigned user name>

c) Click OK.

d) Click Close.

e) Enter the password and click OK.

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

Note: To be able to select the SAP Authentication it requiresthe SAP authentication JAR file (secSAPR3.jar) to be deployedwith the web services.

e) Click OK.

f) Click Next.

7. Select the universe on which to build your query.

a) Click the universe T_BO100_Xcelsius_QaaWS01_GR##.unv.




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

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

a) Click Publish.

b) Copy the URL to the clipboard so that it can be used later on in Xcelsius.



Lesson Summary

You should now be able to:• Create a Query as a Web Service against SAP data sources with variables



Lesson: Xcelsius and Query as a Web Service

Lesson OverviewYou have learned how to create a QaaWS on top of an OLAP Universe based onan SAP query. In this lesson, you will learn how you can use Xcelisus to connectto 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 ExampleYou are a report designer who uses Xcelsius dashboard on top of an OLAPUniverse based on an SAP data sources. You have created a new Query as a WebService on top of the Universe and then publish the web service. Now you areready to create a dashboard using this web service.

Connectivity for XcelsiusXcelsius can connect directly to a BusinessObjects universe Query as a WebService. The following data sources are available for Xcelsius:

SAP BW

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


BO100 Lesson: Xcelsius and Query as a Web Service

Figure 164: Xcelsius Connectivity to SAP NetWeaver

Xcelsius and QaaWSAfter creating the OLAP Universe and the web service based on top of the OLAPUniverse, you can now create the Xcelsius dashboard using the web service.





Exercise 23: Creating a new Xcelsiusdashboard using Query as a Web Service

Exercise ObjectivesAfter 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 ExampleYou are a report designer and need to create an Xcelsius dasboard based on anexisting web service.

Task:Build a new Xcelsius dashboard using QaaWS on top of an OLAP Universe basedon an SAP BW query.

1. Launch Xcelsius and use the existing QaaWS.

2. Create a pie chart that demonstrate the sales value of customer in differentregion.

3. Preview the dashboard in Xcelsius.

4. Save the Xcelisus report to Enterprise and view the report using SAPauthentication.



Solution 23: Creating a new Xcelsiusdashboard using Query as a Web ServiceTask:Build a new Xcelsius dashboard using QaaWS on top of an OLAP Universe basedon an SAP BW query.

1. Launch Xcelsius and use the existing QaaWS.

a) Select Start → Programs → Xcelsius → Xcelsius 2008.


b) Select Data → Connections.


c) Click Add.

d) Select Query as a Web Service.




Figure 166: Query as a Web Service

e) Select the newly created QaaWs connection.

Note: The existing QaaWS connection might have beenselected by default.

f) Paste the URL from the created QaaWs web service into the fieldWSD URL.

g) Click Import.

Note: The web service returns the data in a table format andshows that each row in this example returns a value for theCountry 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 andthen using the shift key to select B10.

k) Click OK.

l) Navigate to the Usage tab.

m) Set the Refresh on Load property.

n) Click Close.




2. Create a pie chart that demonstrate the sales value of customer in differentregion.

a) Drag and drop a pie chart onto the canvas.


c) Click the red arrow icon next to the Data Values.

d) Mark the range (B1:B10) in the Excel spreadsheet by selecting B1 andthen 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 andthen using the shift key to select A10

Figure 167: Pie chart




3. Preview the dashboard in Xcelsius.

a) Click Preview.

Figure 168: Customer sales value

Note: Because you are not authenticated againstBusinessObjects Enterprise at this time a logon mask will comeup and ask for BusinessObjects Enterprise credentials. Usethe SAP Authentication and the SAP credentials to leverageSingle-Sign-On from the Xcelsius Dashboard to LiveOfficeand Crystal Reports.

4. Save the Xcelisus report to Enterprise and view the report using SAPauthentication.

a) Select the menu File → Export → BusinessObjects Platform.

Note: When exporting to the BusinessObjects Platform theactual Xcelsius runtime flash document is being stored on theplatform. When selecting the menu File > Save as the designof the Xcelsius document is being stored to BusinessObjectsEnterprise.

b) Select a folder on your BusinessObjects Enterprise system. Navigateto SAP → 2.0 → <SID>CLNT900 in your BusinessObjects Enterprisesystem.

c) Enter a file name GR## Xcelsius QaaWS01.

d) Click Save.

e) View the Xcelsius dashboard in InfoView using the SAP authentication.





Exercise 24: Creating a new Xcelsiusdashboard based on QaaWS with SAPvariables

Exercise ObjectivesAfter 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 ExampleYou created a web service which delivers a list of countries and you have aweb service which will retrieve the list of regions based on a selected countryrepresented by an SAP variable. As a next step, you will create Xcelsiuscomponents to provide a list of values and a chart showing the actual data basedon the selected value.

Task 1: Build the first OLAP Universe based on BWQuery BO100 Xcelsius QaaWs 01Build two new QaaWS service using OLAP Universes as the source. The firstQaaWS will be used for the prompting the list of values and the second QaaWSwill 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 theList of Values.

Task 2: Build the second OLAP Universe based on BWQuery BO100 Xcelsius QaaWs 021. 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.





Task 3: Create a new QaaWS using the first Universe1. Create a new QaaWS web service using the OLAP Universe (BO100

Xcelsius QaaWS 01).

2. Include the following fields from universe: Sold-toPartyCountry Key andSold-toPartyCountry Description.

Task 4: Create a new QaaWS using the secondUniverse1. 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 twoQuery as a Web ServicesYou have created a web service which delivers a list of countries and youhave a web service which will retrieve the list of regions based on a selectedcountry represented by an SAP variable. As a next step, you will create Xcelsiuscomponents to provide a list of values and a chart showing the actual data basedon the selected value.

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 firstQaaWS. This list box is used to retrieve the values from the QaaWS. Lateryou will configure the component with trigger cells to interact with anothercomponent.

3. Create another data connection in Xelsius using the second Query as a WebService.

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

6. Save the Xcelisus document to Enterprise and view the flash document usingSAP authentication.



Solution 24: Creating a new Xcelsiusdashboard based on QaaWS with SAPvariablesTask 1: Build the first OLAP Universe based on BWQuery BO100 Xcelsius QaaWs 01Build two new QaaWS service using OLAP Universes as the source. The firstQaaWS will be used for the prompting the list of values and the second QaaWSwill 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 theList of Values.

a) This OLAP Universe, T_BO100_Xcelsius_QaaWS01_GR##.unv,should have been created from an earlier exercise. Check that thisuniverse is available in Designer.

b) Start Designer from Start → Programs → BusinessObjects XI 3.1 →BusinessObjects Enterprise Client Tools → Designer.

c) Select File → Open.

d) Navigate to BusinessObjects Universes folder and ensureT_BO100_Xcelsius_QaaWS01_GR##.unv is there.

Task 2: Build the second OLAP Universe based on BWQuery BO100 Xcelsius QaaWs 021. 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) 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





Field Name Value



Authentication SAP

c) Click File > New.

d) Click New to create a new connection.

e) Click Next.

f) Select SAP -> SAP Business Warehouse from the list.

g) Enter a connection name.

h) Click Next.

i) Enter the User name, Password, and Language.

Field Name Value

User Assigned user


Client 900



System number 50


j) Enter the Client, Application Server, and System Number based on theSAP server details.


k) Set the Authentication Mode to Use specified username andpassword.

l) Click Next.

m) Open the list of available cubes by clicking the plus sign next to OLAPCubes.

n) Navigate to BO100 cube and select ‘BO100 Xcelsius QaaWs 02(technical name: T_BO100_Q17_1)'.




o) Select the required query and Click Next.

p) Click Finish.

q) Enter the Universe name T_BO100_Xcelsius_QaaWS02_##.

r) Navigate to the Controls tab.

s) Uncheck all Query Limits.

t) Click OK.



b) Ensure the destination folder is set to BusinessObjects Universes,and ensure the universe name is set to T_BO100_Xcel-sius_QaaWS02_GR##.unv, then press Save.

c) Select File → Export.

d) Press the Browse button.

e) Highlight the folder webi universes then press OK.

f) Click OK to export the universe. The universe is now available forreporting.

Task 3: Create a new QaaWS using the first Universe1. Create a new QaaWS web service using the OLAP Universe (BO100

Xcelsius QaaWS 01).

a) Select Program → BusinessObjects XI 3.1 → BusinessObjectsEnterprise Client Tools → Query as a Web Service.

Note: Since you have already created a Query as a WebService, you don't have to add the host anymore. Ensure thefollowing credentials are on the login screen:

Field Name Value

Host Assigned BusinessObjectsEnterprise system (forexample: TWDFXXXX)

System Assigned BusinessObjectsEnterprise system (forexample: TWDFXXXX)

User Assigned User ID (forexample: 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 requiresthe SAP authentication JAR file (secSAPR3.jar) to be deployedwith the web services.

g) Click OK.

h) Click Next.

2. Include the following fields from universe: Sold-toPartyCountry Key andSold-toPartyCountry Description.

a) Select the OLAP universe (BO100 Xcelsius QaaWS 01)T_BO100_Xcelsius_QaaWS01_GR##.unv you created earlier.

b) Click Next.

c) Use the query panel to create the query for the web service.

d) Click Next.

e) Expand all the folder. Select L01 Sold-toPartyCountry Key and L01Sold-toPartyCountry Name and drag them to the Result Objectswindow.

f) Click Next.

Note: A preview of the data is shown including the outputparameters.

g) Click Publish.

h) Copy the URL to the clipboard so that it can be used later in Xcelsius.




Task 4: Create a new QaaWS using the secondUniverse1. 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) Use the query panel to create the query for the web service.

f) Click Next.

g) Select L01 Region and Sales Volume EUR and drag them to the ResultObjects window.

h) Click Next.

Note: In case the underlying OLAP Universe includes aprompt the web service tool will provide a list of values duringthe creation process.

i) Double-click a value.

j) Click OK.

Note: A preview of the data is shown including the outputparameters.

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 twoQuery as a Web ServicesYou have created a web service which delivers a list of countries and youhave a web service which will retrieve the list of regions based on a selectedcountry represented by an SAP variable. As a next step, you will create Xcelsiuscomponents to provide a list of values and a chart showing the actual data basedon the selected value.

1. Launch Xcelsius and create a data connection using the first QaaWS.




a) Select Start → Program → Xcelsius → Xcelsius 2008.


b) Select Data → Connections.


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

Note: Find the URL for GR##_QaaWS_01. If the URL is notin the clipboard, go the Query as a Web Service and select theGR##_QaaWS_01. Click To Clipboard.

g) Click Import.

Note: The web service returns the data in a table format andshows that each row in this example returns a value for theCounty Key and a value for the Country Name

h) Click the row folder of the Return Values.

i) Click the icon next to the range.

j) Mark the excel range A1:B10 by selecting A1 and then using the shiftkey to select B10.

k) Click OK.




l) Navigate to the Usage tab.

m) Set the Refresh on Load property.

Figure 170: Refresh on Load

n) Click Close.

2. Add a list box component to the Xcelsius canvas and connect it to the firstQaaWS. This list box is used to retrieve the values from the QaaWS. Lateryou will configure the component with trigger cells to interact with anothercomponent.

a) Drag and drop a list box onto the canvas.

Note: Choose the selectors category button and scroll down tofind the list box.




Figure 171: List box

b) Double-click the list box component.

c) Set the Insertion Type option to Value.

Figure 172: Insertion Type




d) Select the red arrow icon next to source data and choose the excel rangefor the country keys (A1:A10) by selecting A1 then holding Shift keyand selecting A10. Choose OK.

e) select the red arrow icon next to labels area and choose the excel rangefor the country descriptions (B1:B10) by selecting B1 then holdingShift key and selecting B10. Choose OK.

f) Set the Destination to a cell in the spreadsheet. Select the red arrow iconnext to the Destination Cell and choose cell F1 in Excel. Choose OK.

Note: Remember this cell because this cell will be used astrigger cell.

3. Create another data connection in Xelsius using the second Query as a WebService.

a) Select Data → Connections.

b) Click Add.

c) Select Query as a Web Service.

d) Select the newly created connection.

Figure 173: New connection

e) Paste the URL from the second created QaaWS web service into thefield WSD URL.

Note: Find the URL for GR##_QaaWS_02. If the URL is notin the clipboard, go the Query as a Web Service and select theGR##_QaaWS_02. Click To Clipboard.

f) Click Import.

Note: The web service will also show the SAP variable in thelist 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 theprevious web service.

j) Click OK.

k) Click on the item for the SAP variable (desired Country) in the listof 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 isused as destination from the list box).

n) Navigate to the Usage tab.

o) Click the icon next to Trigger Cell.

p) Mark the cell F1 in the excel spreadsheet

Note: This cell needs to be identical to step 2 (the cell that isused as destination from the list box).

q) Select the option When Value Changes.

Figure 174: Trigger cell when value changes

r) Click Close.

4. Create a pie chart onto the canvas and link it to the second QaaWS.

a) Drag and drop a pie chart onto the canvas.




Figure 175: Pie chart


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 shiftkey to select D50.

Note: In this example the result set is from the second webservice.

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 shiftkey to select C50

h) Navigate to the Behavior tab.




Figure 176: Ignore Blank cells in Values

i) Select the option Ignore Blank cells in Values.

Figure 177: Design

5. Preview the Xcelsius file and see how the components interact with eachother.

a) Click Preview.

Note: Each change of the country value will return a differentpie chart for a different list of regions.




6. Save the Xcelisus document to Enterprise and view the flash document usingSAP authentication.

a) Select the menu File → Export → BusinessObjects Platform.

Note: When exporting to the BusinessObjects Platform theactual runtime flash Xcelsius document is being stored on theplatform. When selecting the menu File > Save as the designof the Xcelsius document is being stored to BusinessObjectsEnterprise.

b) Select a folder on your BusinessObjects Enterprise system. Navigateto SAP → 2.0 → <SID>CLNT900 in your BusinessObjects Enterprisesystem.

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.



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


BO100 Unit Summary

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


Unit Summary BO100



Test Your Knowledge

1. Through Xcelsius you can combine multiple datasources inside Excel andthese multiple excel files can be used by multiple web services.Determine whether this statement is true or false.□ True□ False



Answers

1. Through Xcelsius you can combine multiple datasources inside Excel andthese multiple excel files can be used by multiple web services.

Answer: True


Unit 13SAP Security Integration and Creating

Publications

Unit OverviewThis unit provides you with an overview of how existing data level security of anSAP system can be leveraged for a publication. In this unit, you will learn about:


• Describe the concept of server side trust• Describe the components of server side trust• Configure the SAP server for server side trust• Configure the BusinessObjects Enterprise system as a trusted system with

SAP• Configure BusinessObjects Enterprise services• Create a publication for Crystal Reports• Describe the workflow for a publication with server side trust

Unit ContentsLesson: Server side trust and impersonation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . .463

Procedure: Steps to configure server side trust .. . . . . . . . . . . . . . . . . . . . . . .466Lesson: SAP server configuration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468

Procedure: SAP Cryptographic Library download ... . . . . . . . . . . . . . . . . . .469Procedure: SAP Instance Profile parameters .. . . . . . . . . . . . . . . . . . . . . . . . .470

Lesson: BusinessObjects Enterprise configuration ... . . . . . . . . . . . . . . . . . . . . .476Procedure: Prerequisites .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .478Procedure: Deploying SAP Cryptographic Library to BusinessObjectsEnterprise server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .479Procedure: Generating BusinessObjects Enterprise PSE file onBusinessObjects Enterprise Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .480Procedure: Importing the generated BusinessObjects Enterprise PSEfile into SAP system ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483Procedure: Exporting a SAP server certificate from the SAP server 485


Unit 13: SAP Security Integration and Creating Publications BO100

Procedure: Working with the SNC Access Control List . . . . . . . . . . . . . . .486Procedure: Linking the exported SAP certificate to the BusinessObjectsEnterprise PSE File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .488Procedure: Adding a Server Intelligence Agent .. . . . . . . . . . . . . . . . . . . . . . .491Procedure: Granting OS access to the BusinessObjects EnterprisePSE File.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .499Procedure: Configuring SNC options in the Central ManagementConsole (CMC) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .501Exercise 25: Establishing trust between BusinessObjects Enterpriseand SAP ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .503

Lesson: Creating a publication... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .510Procedure: Creating a publication for Crystal Reports .. . . . . . . . . . . . . . .511


BO100 Lesson: Server side trust and impersonation

Lesson: Server side trust and impersonation

Lesson OverviewIn this unit you will learn about the concept of SAP server side trust (SNC) andthe involved components.


• Describe the concept of server side trust• Describe the components of server side trust

Business ExampleYou are planning to implement a BusinessObjects Enterprise solution integratedwith SAP NetWeaver BW and need to ensure that the server side trust andimpersonation is configured correctly in your environment.

Server side trustIn combination with BusinessObjects Enterprise the concept of server side trustwill be used to schedule reports for a defined set of SAP users or user groups andto use the server side trust to then impersonate during the scheduling process. Inthis way the scheduling process can be executed for multiple SAP accounts andthe SAP data level security for each user is used.

Impersonation is a technique that allows a system to act on behalf of a differentuser or security context.

Entity A grants entity B the trust to authenticate with different users in apassword-less authentication. In other words, entity B leverages the granted trustto use the impersonation function and is able to execute the application on behalfof a different set of users.

In the example of a publishing process of a report the goal is to schedule a reportfor a defined set of users and user groups while ensuring data-level security. Basedon the impersonation and the trust configuration options between BusinessObjectsand the SAP server, the SAP server is granting the BusinessObjects processingservers the right to use the impersonation and authentication with the set of userson the SAP server without the need for a password.

In order for a component to impersonate an SAP account without providing apassword, the component must have identified itself with the SAP server using anauthentication method stronger than a username and password.



The component is required to run under credentials that are authenticated using aSecure Network Communication (SNC) provider and the credentials are requiredto be configured to allow impersonation without the use of a password.

In the case of BusinessObjects Enterprise the processing servers like CrystalReports Job and Page server and the Web Intelligence Processing server need to beconfigured to run under such an SNC account.

Components of server side trustThis image shows the involved components and the required steps to configuretrust between BusinessObjects Enterprise and the SAP system.

Figure 178: Components and the required steps to configure trust betweenBusinessObjects Enterprise and the SAP system

SAP Cryptographic LibraryThe SAP cryptographic library is delivered separately from the core SAPproduct, It is the default security product for performing encryption functionsin SAP Systems. For example, you can use it for providing Secure NetworkCommunications (SNC) between various SAP server components, for Secure storeand Forward (SSF) use, or for using the Secure Sockets Layer (SSL) protocolwith the SAP Web Application Server. Here we are only interested in its usefor SNC purposes.

Caution: Restrictions: The SAP Cryptographic Library’s usageagreement restricts its use to server to server configurations only, i.efor 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 SNCsetups, then you must purchase an SNC-certified partner product. Pleasesee SAP Notes 597059 and 397195.

Note: Other SAP certified security products can also be used to configureserver side SNC trust between BOE and SAP servers. In these lessons,we only document a configuration that uses the SAP cryptographiclibrary security product. See SAP Help on SNC and the sectionExternal Security Products (http://help.sap.com/saphelp_nw70/help-data/EN/e6/56f466e99a11d1a5b00000e835363f/frameset.htm ).

Personal Security EnvironmentA Personal Security Environment store (PSE file) contains(a) the private-key certificate of the owner or component that created the PSEfile and(b) a list of any public-key certificates of other components/parties that have beenidentified as trusted components/parties.

A PSE file is password protected to prevent illegal certificates being added orvalid certificates being removed by anyone who is not the PSE owner. In additionthough, an Operating System credential can be identified to the PSE store andgranted passwordless usage of the PSE file and its certificates.



Steps to configure server side trust

1. The SAP Cryptographic library is deployed and configured on the SAPsystem.

2. The SAP Cryptographic library is deployed and configured on the processingcomponents 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 theSAP 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 thePSE file for the BOE system.

7. The OS credentials used to running the BOE reporting service(s) areidentified to the PSE file for the BOE system.

ResultAfter these steps, the BusinessObjects Enterprise system and the SAP system haveexchanged certificates and are now both aware of each other and identify the otheras a trusted system. In particular, the BOE server can now be configured the righton the SAP server to impersonate one or more SAP user credentials on this SAPsystem without an SAP user password.



Lesson Summary

You should now be able to:• Describe the concept of server side trust• Describe the components of server side trust



Lesson: SAP server configuration

Lesson OverviewIn this lesson you will learn the required steps on the SAP server to establish trustbetween the SAP server and BusinessObjects Enterprise.


• Configure the SAP server for server side trust

Business ExampleYou are planning to implement a BusinessObjects Enterprise solution integratedwith SAP NetWeaver BW and need to ensure that the server side trust andimpersonation is configured correctly in your environment.


BO100 Lesson: SAP server configuration

SAP Cryptographic Library downloadUseAs a first step you need to download the SAP Cryptographic library. The file canbe downloaded from the SAP service marketplace.

Procedure1. 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 179: SAP Cryptographic Software

4. Download the SAP crypto library files for the relevant hardware andplatforms that BOE and SAP servers are running on.

5. Unpack the downloaded file with the SAPCAR tool.

Result

• The SAP Cryptographic Library (sapcrypto.dll for Windows orlibsapcrypto.ext for UNIX, where ext=Unix file extension).

• A license ticket file (ticket).• The configuration tool (sapgenpse.exe).



SAP Instance Profile parametersUseYou can now configure the SAP server to make use of the SAP CryptographicLibrary.

Prerequisites

• SAP Cryptographic Library downloaded and expanded for all relevantplatforms

• SAP Administrator's credentials inside SAP as well as Administrator rightsto the operating system on which SAP server runs

Procedure1. Log onto the operating system of the SAP server.

2. Copy the SAP Cryptographic Library file to the directory<DRIVE>:\usr\sap\<SID>\SYS\exe\uc\<os_platform> onWindows.

Note: Replace <SID> with the System ID and <os_platform>with the for your SAP server. On older systems this directory was:<DRIVE>:\usr\sap\<SID>\SYS\exe\run

3. Copy the “ticket” file to the directory:<DRIVE>:\usr\sap\<SID>\<instance>\sec.

4. Create an environment variable SECUDIR that refers to the ticket's filepathfrom the previous step. This environment variable needs to be accessible tothe user account that is used to execute the Dispatcher process for the SAPsystem.

5. Log onto the SAP server from SAP GUI

6. Start transaction RZ10.




Figure 180: 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 Cryptographiclibrary




sec/libsapsecu Enter the full path to the SAP Cryptographiclibrary

snc/gssapi_lib Enter the full path to the SAP Cryptographiclibrary

snc/identity/as Distinguished name (DN) for your SAP system

Note: The Distinguished name (DN) for your SAP system shouldfollow the LDAP naming convention:

Tag Meaning Description

CN Common name Name of the certificateproprietor

OU Organizational Unit Name of the organizationalunit

O Organization Name of the organization

C Country Country in which theproprietor 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 librarywhen referring to the DN of the SAP system.

Figure 181: 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 afterthe previous configuration steps.

Figure 182: Example STRUST view:

13. Right-click the folder entry SNC SAP Cryptolib.

14. Select Create.

Note: The configured Distinguished Name you specified in RZ10should 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 forthis password every time you view or edit the PSE in transactionSTRUST.

18. Click Save.

Caution: If you leave out step 17 and step 18 your SAP server won’tstart after activating SNC!




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 to1 ensure that previous, unsecure, communication methods are stillpermitted.

The snc/data_protection is set to the minimum value (1) forauthentication and to the maximum value (3) for privacy.

24. Restart the SAP system.



Lesson Summary

You should now be able to:• Configure the SAP server for server side trust



Lesson: BusinessObjects Enterprise configuration

Lesson OverviewIn this lesson you will learn the necessary steps on the BusinessObjects Enterprisesystem to establish trust between the BusinessObjects Enterprise system and theSAP server.


• Configure the BusinessObjects Enterprise system as a trusted system withSAP

• Configure BusinessObjects Enterprise services

Business ExampleThe main motivation for configuring server side trust using SNC (Secure NetworkConnection) between BusinessObjects Enterprise Servers and SAP Server is toallow passwordless impersonation by a BusinessObjects reporting server of one ormore 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 ofdifferent/multiple SAP users

• BusinessObjects Enterprise client session has been authenticated usinga non-SAP authentication method or SAP credentials from another SAPentitlement system; and passwordless single sign-on is required using analiased SAP logon required when the BOE reporting server refreshes againstthis a different SAP server.

using SAP authentication using the same SAP entitlement credentials.

– 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 SAPreport 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 intime (after token expiry date).


BO100 Lesson: BusinessObjects Enterprise configuration

Objective 1 Overview: Establishing trust betweenBusinessObjects Enterprise and SAPAfter downloading and unzipping the SAP Cryptographic Library, you cannow configure the BusinessObjects Enterprise server to make use of the file byfollowing the following procedures:

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



Prerequisites

1. We assume that the SAP server has been enabled for server side trust usingSNC.



Deploying SAP Cryptographic Library toBusinessObjects Enterprise serverUseTo configure SAP Cryptographic Library on the BusinessObjects Enterprise server

Procedure1. Logon to the operating system of the BusinessObjects server.

2. Create a folder <Drive>:\Program Files\SAP\CRYPTO.

Note: The above mentioned folder path is an example. This foldercan be on a different drive and the folder can have a differentlocation and name.

3. Add this folder location to the environment variable PATH.

4. Copy the SAP Cryptographic Library to this folder <Drive>:\Programfiles\SAP\CRYPTO.

5. Copy the PSE maintenance tool (sapgenpse.exe) to the same folder<Drive>:\Program files\SAP\CRYPTO.

6. Add a system wide-environment variable SNC_LIB pointing to the fullpath of the SAP Cryptographic library (for example, <DRIVE>::\ProgramFiles\SAP\CRYPTO\sapcrypto.dll).

7. Create a subfolder called SEC in the folder (for example, <Drive>:\ProgramFiles\SAP\CRYPTO\SEC).

8. Add a system wide environment variable SECUDIR pointing to thesubfolders SEC.

9. Copy the ticket file from SAP Cryptographic Library to the SEC sub-folder.

Tips and common mistakes:• Check spelling as it is case sensitive.• To add/edit the environment, click Start → Control Panel → System. Click

Advanced and select Environment Variables.

Validation tests:• 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.



Generating BusinessObjects Enterprise PSE file onBusinessObjects Enterprise ServerUseIn 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 fileand this file needs to be associated with the SAP system.

This link, whereby the SAP system trusts BusinessObjects Enterprise andBusinessObjects Enterprise trusts the SAP system is established by sharing apublic version of each other’s certificate.

To generate the PSE file for BusinessObjects Enterprise (on Windows):

Procedure1. 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 <Drive>:\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 willbecome the file for your BOE PSE file.

Figure 183: 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. Forexample: CN=TWDFXXXX, OU=KPS, O=BOBJ, C=CA.

Note: The Distinguished name (DN) for your SAP system shouldfollow the LDAP naming convention:

Tag Meaning Description

CN Common name Name of the certificateproprietor

OU Organizational Unit Name of the organizationalunit

O Organization Name of the organization

C Country Country in which theproprietor resides

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 –omyTWDFXXXX.cert

Note: TWDFXXXX.pse represents the filename for the PSE file andmyTWDFXXX.cert represents the name for the exported certificatefrom 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:

• <Drive>:\Program Files\SAP\CRYPTO should contain the .cert file.• <Drive>:\Program Files\SAP\CRYPTO\SEC should contain the .pse file.



Importing the generated BusinessObjects EnterprisePSE file into SAP systemUseNow that you have created the PSE file and exported the certificate, you need toimport the certificate to the SAP system Trust Manager to establish the trust.

To configure the trust on the SAP server:

Procedure1. Log onto SAP server.

2. Start transaction STRUST .

3. Open the folder SNC (SAP Cryptolib)in the left hand frame:

Figure 185: SNC (SAP Cryptolib)

4. Double-click the entry inside the folder.

5. Enter the password that was defined earlier in RZ10 (see previous lesson).

6. Click Import Certificate (left button)

Figure 186: Import Certificate

7. Select the option Base64.

8. Enter the path to the certificate file myTWDFXXXX.cert generated earlierfrom the BusinessObjects Enterprise system.




Figure 187: Enter

9. Click Enter.

10. Click Add to Certificate List.

Figure 188: Add

11. Click Save.



Exporting a SAP server certificate from the SAP serverUseNow that you have imported the PSE file from BusinessObjects Enterprise tothe SAP system, you need to:

1. Export a SAP server certificate from the SAP server.2. Import it to the BusinessObjects Enterprise system.

To export the certificate from the SAP server


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



Working with the SNC Access Control ListUseNow that you have exported the certificate from the SAP server, you have twooutstanding tasks. You need to

1. Import the certificate from the SAP server to the PSE file fromBusinessObjects Enterprise and

2. Create a system ID in the SNC Access Control List (ACL).

To create the system ID:


2. Start transaction SNC0.

3. Click New Entries.

4. Enter the name of your BusinessObjects Server as System ID (this is just adescriptive identifying name)

5. Enter the exact SNC name (distinguished name) that was entered whencreating the BusinessObjects Enterprise PSE file in the SNC name field witha prefix “p:”.

6. Select the checkboxes Entry for RFC activated and Entry forext ID activated. Uncheck all others.

7. Click Save.

Note: If correctly entered, you will get a green check and themessage Canonical Name Determined.

ResultAfter the configuration steps of the above procedure, the configured System IDis allowed to leverage the SNC configuration and to logon via an external IDand use impersonation.



Tips and common mistakes:• STRUST and SNC0 are a one user at a time transaction• 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 whatyou just imported.

• Don’t forget to save.

Validation tests:Look for the new files created in your folder:

• <Drive>:\Program Files\SAP\CRYPTO should contain theSAP_TWDFXXXX.cert file.



Linking the exported SAP certificate to theBusinessObjects Enterprise PSE FileUseAs a final step you need to import the certificate of the SAP system to the PSEfile for the BusinessObjects Enterprise system to identify the SAP system asa trusted partner.

To import the certificate from the SAP server to BusinessObjects Enterprise (onWindows):

Procedure1. 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 <DRIVE>:\ProgramFiles\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 forthe PSE file on the BusinessObjects Enterprise server.

SAP_TWDFXXXX.cert is a placeholder for actual the filenameof the SAP server certificate file.





Tips and common mistakes:• 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 betweenBusinessObjects Enterprise and SAPIn summary, after the previous configuration steps, you achieved the following:

• The SAP Cryptographic library is deployed and configured on the SAPserver.

• The SAP Cryptographic library is deployed and configured on theBusinessObjects Enterprise server.

• Certificates have been exchanged between BusinessObjects Enterprise andthe SAP server to establish trust between these two systems.

• A System ID has been created on the SAP server for the BusinessObjectsEnterprise system entity (i.e. distinguished name or DN) allowing itpassword-less impersonation against the SAP server.

Objective 2 Overview: Configure BusinessObjectsEnterprise servicesWith the trust established between BusinessObjects Enterprise and the SAP server,you can now configure the processing tier from BusinessObjects Enterprise toleverage this configuration so that in a next step you can use the trust to configurea publication for a report object.



Unless all Web Intelligence, Crystal Reports and Voyager processing services arerunning under credentials that have access to the PSE file from the BusinessObjectsEnterprise system, the administrator has three options for the configuration:

1. A single Server Intelligence Agent is given access via the operatingcredentials used to execute the service to the BusinessObjects EnterprisePSE file. This is the simplest option, but this results in all services of theBusinessObjects Enterprise system having access to the BusinessObjectsEnterprise PSE file.

2. An additional Server Intelligence Agent is created and the Web Intelligence,Crystal Reports and Voyager processing services are added to the newservice. In this way only specific configured services are granted access tothe BusinessObjects Enterprise PSE file.

3. An additional Server Intelligence Agent is created and the Web Intelligence,Crystal Reports and Voyager processing services are added to the newservice. In addition, Server Groups are created and associated with thecontent.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 JobServer, and Adaptive Processing Servers also needs to be added tothe server group.



Adding a Server Intelligence AgentUseTo configure the processing tier from BusinessObjects Enterprise:

Procedure1. Start the Central Configuration Manager: Start → Programs →

BusinessObjects XI Release 3 → Central Configuration Manager.

Figure 191: CCM

2. Click Add Server Intelligence Agent.

Figure 192: Add Server Intel Agent

3. Click Next.




Figure 193: Next

4. Enter the Name and Port for the new Server Intelligence Agent

5. Click Next

Figure 194: Next

6. Enter the name of the CMS, an administrative account and the password.

7. Click Next.




Figure 195: Next

8. Click Finish.

Figure 196: Finish

9. Select the newly created Server Intelligence Agent and click Properties.

Figure 197: PropertiesContinued on next page



10. Uncheck the System Account option.

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

Figure 199: Properties

17. Uncheck the System Account option.




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

Figure 201: CMC

22. Navigate to the Servers area.




Figure 202: Servers Area

23. Select the menu Manage → New → New Server.

Figure 203: New Server

Note: Depending on which services are required for thedeployment, select the required option in the service category.For this general procedure, you will configure a CrystalReports Scheduling Server and Crystal ReportsProcessing Server as an example.

24. Select Crystal Reports as Service Category.




25. Select Crystal Reports Scheduling Service as Service.

Figure 204: Service

26. Click Next.

27. Select Destination Configuration Service from AvailableAdditional 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 Servicesand click > to bring it to Selected Services.




Figure 205: Single Sign-On

36. Click Next.

37. Select the newly created Server Intelligence Agent from the list of Nodes.

38. Click Create.

39. Select the newly created server from the list of servers and start the service.

Note: Based on this configuration the newly created processingservice uses the same account that is being used for the ServerIntelligence Agent.

Tips and common mistakes:• In the CMC, make sure the new added services are enabled and running.



Granting OS access to the BusinessObjects EnterprisePSE FileUseAt this point, you need to associate the BusinessObjects Enterprise PSE file withthe credentials that are being used to execute the BusinessObjects processingservices (for example, Web Intelligence Report Server, Crystal Reports JobServer, MDAS Server).

To associate the PSE File with the credentials (Windows):

Procedure1. 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 theBusinessObjects Enterprise service.

Hint: If no additional options the tool assumes the currently loggedon user account will receive access to the PSE file. If To grant accessto another user, e.g domainName\userName, use the followingcommand line:

sapgenpse.exe seclogin –p TWDFXXXX.pse –OdomainName\userName





8. Enter the following command to verify passwordless access to the contentof the PSE file:

sapgenpse.exe maintain_pk –l

When running this command, the important outcome should be that theoutput is listed without any prompt to enter a PIN.

Note: If no PIN prompted, then the credentials have been passedbetween SAP and BOE successfully.

Tips and common mistakes:• 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 thesapgenpse seclogin command, you can always delete this file and try againcopying the certificates from the SAP system and BOE system and link themtogether again for troubleshooting, without having to start completely over again.



Configuring SNC options in the Central ManagementConsole (CMC)UseAfter configuring all the above relevant steps, you can enable SNC for theentitlement system in the Central Management Console.

To configure SNC for the entitlement system:

Procedure1. 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 207: SNC

6. Check the option Enable Secure Network Communication (SNC) in thecategory 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 authenticationsettings with a prefix “p:”.

Note: Enter the Distinguished Name (DN) that you get from thecommand line sapgenpse maintain_pk –l, with a p:prefix..

10. Enter the SNC name of the BusinessObjects Enterprise system for the Trustsettings with a prefix “p:”.

Note: Enter the Distinguished Name (DN) that you getfrom the command line sapgenpse get_my_name –pTWDFXXXX.pse, with a p:prefix.

Figure 208: SNC

11. Click Update.

Objective 2 Summary: Configure BusinessObjectsEnterprise servicesIn order to leverage SNC in the BusinessObjects Enterprise services, we coveredthe three procedures needed to create an additional Server Intelligence Agentconfigured only for specific BusinessObjects processing tier services runningunder a credential that has access to the PSE file and how to enable SNC in theCrystal Management Console.

1. Adding a Server Intelligence Agent.2. Granting access to the PSE File to the appropriate user accounts.3. Configuring SNC options in the Central Management Console (CMC)



Exercise 25: Establishing trust betweenBusinessObjects Enterprise and SAP

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

Business ExampleYou are an administrator and need to configure server side trust betweenBusinessObjects Enterprise and the SAP system.

Task 1: Create a PSE File for the BusinessObjectsEnterprise system[Enter a high level description of the task the learner will perform in this exercise.]

Note: In the exercise, replace XX with your staff or training number

1. Install the SAP Cryptographic Library on the BusinessObjects Enterpriseserver.

2. Create a PSE file for the BusinessObjects Enterprise server calledTRAINXX.pse.

Enter your staff or training number as the PIN

Enter the distinguished name:CN=TRAINXX,OU=EDUC,O=SAP,C=DE

3. Export a public certificate of the owner's user certificate from PSETRAINXX.pse and call it myTRAINXX.crt

4. NOTE: Another useful command:

To display the distinguished name (DN) of the user certificate inside a PSE:

sapgenpse.exe get_my_name –p <pse file>




Task 2: Import a BusinessObjects Enterprise publiccertificateImporting theBusinessObjects Enterprise certificate into the SAP server PSE

1. Use transaction STRUST to import the public certificate of yourBusinessObjects Enterprise system: myTRAINXX.crt

Task 3: Export an SAP public certificateExporting a public certificate from the SAP server.

1. Use transaction STRUST to export a public certificate of the SAP serverand name it: SAP_TRAINXX.crt .

Task 4: Configure the SNC Access list1. 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=DE

Enable SNC options: Entry for RFC Activated and Entry for ext. IDActivated

Task 5: Import the SAP public certificateImporting the SAP server's public certificate into the BusinessObjects EnterprisePSE

1. Copy the exported SAP pubic certificate SAP_TRAINXX.crt from theprevious exercise to the Cryptographic Library's root directory.

2. Import the SAP public certificate or key SAP_TRAINXX.crt into theBusinessObjects Enterprise TRAINXX.pse store.

Task 6: Add a new Server Intelligence Agent1. Create an additional Server Intelligence Agent (SIA).

2. Assign a new Crystal Reports Job Server, Crystal Reports ProcessingServer, Crystal Reports Cache Server, Web Intelligence Server andMultiDimensionalAnalysisServicesServer to the new SIA.

3. Remove the Crystal Reports Job Server from the original Server IntelligenceAgent.

4. Ensure that the new Server Intelligence Agent and the Tomcat server servicesare running under the (OS) user account which has passwordless access tothe TRAINXX.pse PSE File.




Task 7: Grant access to the BusinessObjectsEnterprise PSE file1. 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 bythe SIA and Tomcat services.

2. From the command line prompt, navigate to the root folder of the SAPCryptographic library.

3. Add this OS user account credentials as a user that has SSO or passwordlessaccess to the BusinessObjects Enterprise PSE, TRAINXX.pse.

4. 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 thiscommand (i.e. that the OS user credential now has passwordless access tothe BusinessObjects Enterprise PSE)

Task 8: Configure SNC in the Central ManagementConsoleEnabling 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<SID>CLNT<CLIENT_ID>

3. Enter the full path to the SAP Cryptographic Library

4. Enter the SNC name (i.e. Distinguished Name) of the SAP system with aprefixed by “p:” under Mutual authentication settings as configured on theSAP server in STRUST.

5. Enter the Distinguished Name of your BusinessObjects Enterprise systemprefixed by “p:” under Trust settings.



Solution 25: Establishing trust betweenBusinessObjects Enterprise and SAPTask 1: Create a PSE File for the BusinessObjectsEnterprise system[Enter a high level description of the task the learner will perform in this exercise.]

Note: In the exercise, replace XX with your staff or training number

1. Install the SAP Cryptographic Library on the BusinessObjects Enterpriseserver.

2. Create a PSE file for the BusinessObjects Enterprise server calledTRAINXX.pse.

Enter your staff or training number as the PIN

Enter the distinguished name:CN=TRAINXX,OU=EDUC,O=SAP,C=DE

a) sapgenpse.exe gen_pse –v –p TRAINXX.pse

3. Export a public certificate of the owner's user certificate from PSETRAINXX.pse and call it myTRAINXX.crt

a) sapgenpse.exe export_own_cert –v –p TRAINXX.pse –omyTRAINXX.crt

4. NOTE: Another useful command:

To display the distinguished name (DN) of the user certificate inside a PSE:

sapgenpse.exe get_my_name –p <pse file>

Task 2: Import a BusinessObjects Enterprise publiccertificateImporting theBusinessObjects Enterprise certificate into the SAP server PSE

1. Use transaction STRUST to import the public certificate of yourBusinessObjects Enterprise system: myTRAINXX.crt

Task 3: Export an SAP public certificateExporting a public certificate from the SAP server.

1. Use transaction STRUST to export a public certificate of the SAP serverand name it: SAP_TRAINXX.crt .




Task 4: Configure the SNC Access list1. 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=DE

Enable SNC options: Entry for RFC Activated and Entry for ext. IDActivated

Task 5: Import the SAP public certificateImporting the SAP server's public certificate into the BusinessObjects EnterprisePSE

1. Copy the exported SAP pubic certificate SAP_TRAINXX.crt from theprevious exercise to the Cryptographic Library's root directory.

a) Copy SAP_TRAINXX.crt to the directory where sapcrypto.dll islocated. This is directory path is part of the environment variableSNCLIB.

2. Import the SAP public certificate or key SAP_TRAINXX.crt into theBusinessObjects Enterprise TRAINXX.pse store.

a) sapgenpse.exe maintain_pk –v –a SAP_TRAINXX.cert -pTRAINXX.pse

Task 6: Add a new Server Intelligence Agent1. Create an additional Server Intelligence Agent (SIA).

2. Assign a new Crystal Reports Job Server, Crystal Reports ProcessingServer, Crystal Reports Cache Server, Web Intelligence Server andMultiDimensionalAnalysisServicesServer to the new SIA.

3. Remove the Crystal Reports Job Server from the original Server IntelligenceAgent.

4. Ensure that the new Server Intelligence Agent and the Tomcat server servicesare running under the (OS) user account which has passwordless access tothe TRAINXX.pse PSE File.

Task 7: Grant access to the BusinessObjectsEnterprise PSE file1. 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 bythe SIA and Tomcat services.




2. From the command line prompt, navigate to the root folder of the SAPCryptographic library.

3. Add this OS user account credentials as a user that has SSO or passwordlessaccess to the BusinessObjects Enterprise PSE, TRAINXX.pse.

a) sapgenpse.exe seclogin –p TRAINXX.pse

4. 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 thiscommand (i.e. that the OS user credential now has passwordless access tothe BusinessObjects Enterprise PSE)

a) sapgenpse.exe maintain_pk –l

Task 8: Configure SNC in the Central ManagementConsoleEnabling 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<SID>CLNT<CLIENT_ID>

3. Enter the full path to the SAP Cryptographic Library

a) e.g C:\Program Files \SAP\Crypto\sapcrypto.dll , i,e, as referenced inthe SNC_LIB environment variable.

4. Enter the SNC name (i.e. Distinguished Name) of the SAP system with aprefixed by “p:” under Mutual authentication settings as configured on theSAP server in STRUST.

a) i.e. As configured in transaction STRUST instance profile, underextended maintenance parameter snc/identity/as

5. Enter the Distinguished Name of your BusinessObjects Enterprise systemprefixed by “p:” under Trust settings.

a) p:CN=TRAINXX, OU=EDUC, O=SAP, C=DE



Lesson Summary

You should now be able to:• Configure the BusinessObjects Enterprise system as a trusted system with

SAP• Configure BusinessObjects Enterprise services



Lesson: Creating a publication

Lesson OverviewIn this lesson you will learn the necessary steps in the BusinessObjects Enterprisesystem in order to create a publication for a Crystal Reports object.


• Create a publication for Crystal Reports• Describe the workflow for a publication with server side trust

Business ExampleYou need to implement a scheduling process for distributing reports to a largeset of users and users groups


BO100 Lesson: Creating a publication

Creating a publication for Crystal ReportsUseA publication allows the administrator to configure a scheduling process for alarge set of users and user groups and define how the outcome of the schedulingprocess is distributed to the users.

To create a publication in BusinessObjects Enterprise:

Procedure1. Log onto the Central Management Console.

Figure 209: CMC

2. Click Folders.

Figure 210: Click Folders




3. Navigate to the folder of your report

4. Select the menu Manage →New → Publication .

Figure 211: Select the Menu

5. Enter the Title and Description for the publication.

6. Click Source Documents.

Figure 212: Click Source Documents

7. Click Add.




Figure 213: Click Add

8. Navigate to the folder for the report object.

Figure 214: Navigate to the folder for the report object

9. Select the report.

10. Click OK.




Figure 215: Click OK

11. Click Enterprise Recipients.

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




Figure 217: 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 withinUniverses or Business Views).

19. Click Save & Close.

Figure 218: Click OK

20. Select the newly created publication.

21. Select the menu Actions → Schedule .




Figure 219: Select

22. Click Enterprise Recipients to verify the settings from thepublication.

23. Click Schedule.

Note: After a successful scheduling process you should be able tosee the result in InfoView for the users that have been configured asrecipients.

Workflow for publication with server side trustThis image briefly outlines the workflow of publication and the scheduling processresulting out of the publication leveraging the granted server side trust to achieveimpersonation.



Figure 220: Publication and Scheduling Workflow with SNC andImpersonation



Lesson Summary

You should now be able to:• Create a publication for Crystal Reports• Describe the workflow for a publication with server side trust


BO100 Unit Summary

Unit SummaryYou 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 BusinessObjects Enterprise system as a trusted system with

SAP• Configure BusinessObjects Enterprise services• Create a publication for Crystal Reports• Describe the workflow for a publication with server side trust


Unit Summary BO100



Test Your Knowledge

1. With server side SNC trust is configured and user impersonation grantedbetween SAP server (entity A) and a trusted entity B, entity B can onlyimpersonate exactly one and only one specified SAP user credential withoutthe need of any password.Determine whether this statement is true or false.□ True□ False

2. The SAP Cryptographic Library is the only External Security Product thatcan be used to configure server side SNC trust between BusinessObjectsEnterprise system and an SAP System.Determine whether this statement is true or false.□ True□ False

3. In Secure Network Connection (SNC) terminology, the acronym PSE standsfor Page Storage Extension.Determine whether this statement is true or false.□ True□ False



Answers

1. With server side SNC trust is configured and user impersonation grantedbetween SAP server (entity A) and a trusted entity B, entity B can onlyimpersonate exactly one and only one specified SAP user credential withoutthe need of any password.

Answer: False

False. Entity A can impersonate one or more SAP user credentials that existon on Entity B without the need of any password.

2. The SAP Cryptographic Library is the only External Security Product thatcan be used to configure server side SNC trust between BusinessObjectsEnterprise system and an SAP System.

Answer: False

False. Any External Security Product that supports the followingrequirements and is certified by SAP can be used.See SAP SNC help:Requirements: To use a security product with SAP systems, the product mustmeet the following requirements:·

• The product must provide the entire range of functions defined in theGSS-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.

3. In Secure Network Connection (SNC) terminology, the acronym PSE standsfor Page Storage Extension.

Answer: False

False. PSE stands for Personal Security Environment - secure store or filecontaining amongst other items, a private-key certificate identifying the useror owner entity; and a list of imported public-key certificates that identifyother parties or entities.


Unit 14Integrating with SAP Enterprise Portal

Unit OverviewThis unit provides you with the steps to integrate BusinessObjects Enterprisewith the SAP Enterprise Portal.


• Import the BusinessObjects Enterprise iView template to the EnterprisePortal

• 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 ContentsLesson: Integrating BusinessObjects Enterprise content into SAPEnterprise Portal using iViews ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525

Procedure: To upload the iView template .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .527Lesson: Portal System landscape for BusinessObjects Enterprise ... . . .530

Procedure: To create the portal system landscape ... . . . . . . . . . . . . . . . . .531Exercise 26: Creating a new report portal system entry forBusinessObjects Enterprise... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .537


Unit 14: Integrating with SAP Enterprise Portal BO100

Lesson: Creating BusinessObjects Enterprise content iViews... . . . . . . . . .543Procedure: To create a new iView ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .544Exercise 27: Creating iViews for BusinessObjects content .. . . . . . . . . .549

Lesson: Creating portal pages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .553Procedure: To create a new portal Page ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .554Exercise 28: Creating a portal Page and adding an iView to thePage... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .559

Lesson: Creating portal worksets.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .563Procedure: To create a new portal workset .. . . . . . . . . . . . . . . . . . . . . . . . . . . .564Exercise 29: Creating a portal Workset .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .567

Lesson: Creating portal roles.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .571Procedure: To create a new portal Role .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .572Procedure: To assign the portal Role to a portal User.. . . . . . . . . . . . . . . .575Exercise 30: Creating a portal Role.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .577Exercise 31: Assigning the portal user to the portal Role .. . . . . . . . . . . .581

Lesson: BusinessObjects Enterprise Repository Manager.. . . . . . . . . . . . . . .584Procedure: To install the Knowledge Management integration... . . . .585Procedure: To verify the installation... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .587Procedure: To create a new repository manager integration with yourBusinessObjects Enterprise system ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .589Procedure: To use the Repository Manager .. . . . . . . . . . . . . . . . . . . . . . . . . . .594Procedure: To use the collaboration features... . . . . . . . . . . . . . . . . . . . . . . . .597Procedure: To create a new iView ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599Exercise 32: Create a new BusinessObjects Repository Manager ..601Exercise 33: Creating a Knowledge Management iView ... . . . . . . . . . .605


BO100 Lesson: Integrating BusinessObjects Enterprise content into SAPEnterprise Portal using iViews

Lesson: Integrating BusinessObjects Enterprise contentinto SAP Enterprise Portal using iViews

Lesson OverviewSAP Enterprise Portal uses iViews as the fundamental building blocks to createportal content. Enterprise Portal comes with many predefined iViews (templates)so portal content administrators can easily create content. BusinessObjectsIntegration Kit for SAP delivers an iView template for integration of CrystalReports into the Enterprise Portal. In this lesson you will find how to import theBusinessObjects Enterprise iView template to the SAP Enterprise Portal.


• Import the BusinessObjects Enterprise iView template to the EnterprisePortal

Business ExampleYou need to describe the process and steps for displaying BusinessObjects contentin the SAP Enterprise Portal.

BusinessObjects Enterprise iView templateThe iView template as part of the BusinessObjects XI Integration for SAPSolutions is delivered as a portal archive file and needs to be uploaded to the portalserver before it is available to the users.

The BusinessObjects portal iView template allows BusinessObjects content tobe displayed in the SAP Enterprise portal. The template contains the propertiesrequired to configure and display a BusinessObjects Enterprise based report ordocument, 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 CrystalReport reports. This is specific to CR reports that aredesigned with alerts.

ThumbnailiView

This is a sample a iview that displays reports fromBusinessObjects Enterprise as thumbnail.

iView Template This iView template allows EP content administrators createnew iViews of the type BusinessObjects Enterprise Report.This is the iView template you use to integrate Crystal



iView DescriptionReports into EP. You should not use it to integrate WebIntelligence Reports as this iView template was createdspecifically for Crystal Reports

There are 2 configuration steps you have to perform before you can create iviewsfrom the BOE iView template:

1. Import BOE iView template into Enterprise Portal2. Create a System Landscape in Enterprise Portal



To upload the iView templateUseThe iView template that comes with BOE Integration Kit for SAP is a portalarchive file that needs to be uploaded to EP before it is available.

Procedure1. Log onto the SAP Enterprise Portal.

URL: http://portal-<SID>-800.wdf.sap.corp:50000/irj/portal

2. Navigate to System Administration > Support.

Figure 221: Support

3. Click Portal Runtime.

Figure 222: Portal Runtime

4. Click Administration Console.




Figure 223: Administration Console

5. Click Browse next to the Archive Uploader.

Note: Themaster iView is installed by default in the following folder://<INSTALLDIR>/Program Files/Business Objects/BusinessObjectsEnterprise 12.0/Web Content/Enterprise12/sap/iviews/import/ep

The filename is com.businessobjects.pct.masteriview.par.

6. Select the file.

7. Click Upload.

ResultUploading the BOE iView template adds the "BusinessObjects Integration Kit-iView template" into the list of templates available when you are creating a newiView from a template.



Lesson Summary

You should now be able to:• Import the BusinessObjects Enterprise iView template to the Enterprise

Portal



Lesson: Portal System landscape for BusinessObjectsEnterprise

Lesson OverviewIn this lesson, you will learn how to create a new system as part of the EnterprisePortal landscape.


• Create a new system for the BusinessObjects Enterprise system


Create a new portal system landscape forBusinessObjects EnterpriseWhen creating a new iView for BusinessObjects Enterprise, one of the requiredparameters is a defined system inside the Enterprise Portal. This system definitionincludes the details of the BusinessObjects Enterprise system that will be used tohost the content displayed inside the an iView.


BO100 Lesson: Portal System landscape for BusinessObjects Enterprise

To create the portal system landscape


2. Navigate to System Administration > System Configuration.

Figure 224: System Administration>System Configuration

3. Click System Landscape.

4. Navigate to the Portal Content.

5. Right-click the Portal Content folder.

Figure 225: Portal Content

6. Select New > Folder.




Figure 226: New>Folder

7. Enter Folder Name, Folder ID and Folder ID Prefix.

Note: The folder name is the display name that appears in the PortalContent, the Folder ID is a unique identifier for the folder.

8. Click Finish.

Figure 227: Finish

9. Click OK to close the wizard.

10. Navigate to the new folder.

11. Right-click the folder.

Figure 228: Folder

12. Select New > System (from template).




Figure 229: New>System

13. Select the option SAP system using dedicated application server.

14. Click Next.

Figure 230: Next

15. Enter the System Name, System ID, and System ID Prefix.

16. Click Next.

Figure 231: Next

17. Click Finish.




Figure 232: 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 regardingthe BOE system that hosts the report and the Web App Server thatshould be used to redirect the BOE iview requests.

Figure 233: Crystal Enterprise Server

21. Enter the host name for the Crystal Enterprise server with the port.

Note: Enter the fully qualified domain name of the BOEWeb Application Server including the port. For example<hostname>:8080.

Hint: If you don't specify fully qualified name for BOE App Server,it may happen that Enterprise Portal determines that not all themachines are on the same DSN domain, causing the following errorwhen trying to view the report through the BOE iview:: "SessionManager will not work Check DSM log for details"

22. Enter the path to the SAP specific applications on the BusinessObjectsEnterprise server.

Note: This is the virtual directory on the Web Application Server thathosts the BOE applications. By default this virtual directory is /SAP.




23. Select http to be the protocol that is used for the BusinessObjects Enterpriseserver.

Figure 234: Select Protocol

24. Click Save.

25. Select the Property Category User Management. Here you will configurethe authentication method to use.

Figure 235: User Management

26. Set the Logon Method property to SAPLOGONTICKET.

Note: This is assuming that SAP logon tickets are being leveragedfor authentication purposes.

27. Set the Authentication Ticket Type to SAP Logon Ticket.

28. Select the Property Category Connector. Here you will be entering theinformation of the SAP ABAP system that will be validating the users. Thisis the system that you have defined previously as an entitlement system inCMC.




Figure 236: Connector

29. Configure the values for Application Host, Gateway Host, Gateway Serviceand Logical System Name according to the SAP system.

Note: If you don't know how to get the Gateway Service, you justneed to connect on the SAP NetWeaver BW server using SAP GUIand run the transaction SMGW. You then should see a column likeTP NAME and the value is the Gateway Service.

30. Configure the values for SAP Client, SAP System ID (SID), and SAP SystemNumber according to the SAP system.

Note: The entries entered here are the values derived from the usedSAP system.

31. Click Save.

32. Select System Aliases in the Display list box. This is the name you willreference to, when creating the iviews.

33. Enter the Alias Name SAP_BW.

34. Click Add.

Figure 237: Add

35. Click Save.

36. Click Close.



Exercise 26: Creating a new reportportal system entry for BusinessObjectsEnterprise

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new report portal entry.

Business ExampleYou are a portal administrator and need to create a new system entry and configureit for your BusinessObjects Enterprise system.

Task:Instructions

1. Log onto the Enterprise Portal.

2. Create a new System entry given by the instructor.

3. Use the following properties:

Category : Crystal EnterpriseSever

Host Name of Crystal EnterpriseServer

<Your CMS name and port> (Forexample: TWDFXXXX:8080)

Path of Crystal Enterprise Server /SAP

Protocol of Crystal EnterpriseServer

http

Category : User Management

Authentication Ticket Type SAP Logon Ticket

Logon Method SAPLOGONTICKET

Category : Connector

Application Host SAP application server (For exam-ple: <SID>tdc00.wdf.sap.corp)

Gateway Host SAP application server (For exam-ple: <SID>tdc00.wdf.sap.corp)

Gateway Service sapgwXX

Logical System Name <SID>CLNT800




SAP Client 800

SAP System ID <SID>

SAP System Number <System Number of the SAPserver>

System Type SAP_BW

4. Create a new alias called TRAINING_SYSTEM_XX where XX is replacedwith your user number.

5. Save your changes.



Solution 26: Creating a new reportportal system entry for BusinessObjectsEnterpriseTask:Instructions


2. Create a new System entry given by the instructor.

a) Navigate to System Administration > System Configuration.

b) Click System Landscape.

c) Navigate to the Portal Content.

d) Right-click the Portal Content folder.

e) Select New > Folder.

f) Enter Folder Name, Folder ID and Folder ID Prefix.

g) Click Finish.

h) Click OK.

i) Navigate to the new folder.

j) Right-click the folder.

k) Select New > System (from template).

l) Select the option SAP system using dedicated application server.

m) Click Next.

n) Enter the System Name, System ID, and System ID Prefix.

o) Click Next.

p) Click Finish.

q) Ensure the default selection Open the object for editing is selected.

r) Click OK.

s) Select Crystal Enterprise Server as Property Category.

t) Enter the host name for the Crystal Enterprise server with the port.

u) Enter the path to the SAP specific applications on the BusinessObjectsEnterprise server.




v) Select the protocol that is used for the BusinessObjects Enterpriseserver.

w) Click Save.

x) Select the Property Category User Management.

y) Set the Logon Method property to SAPLOGONTICKET.

z) Set the Authentication Ticket Type to SAP Logon Ticket.

aa) Select the Property Category Connector.

ab) Configure the values for Application Host, Gateway Host, GatewayService and Logical System Name according to the SAP system.

ac) Configure the values for SAP Client, SAP System ID (SID), and SAPSystem Number according to the SAP system.

ad) Click Save.

3. Use the following properties:

Category : Crystal EnterpriseSever

Host Name of Crystal EnterpriseServer

<Your CMS name and port> (Forexample: TWDFXXXX:8080)

Path of Crystal Enterprise Server /SAP

Protocol of Crystal EnterpriseServer

http

Category : User Management

Authentication Ticket Type SAP Logon Ticket

Logon Method SAPLOGONTICKET

Category : Connector

Application Host SAP application server (For exam-ple: <SID>tdc00.wdf.sap.corp)

Gateway Host SAP application server (For exam-ple: <SID>tdc00.wdf.sap.corp)

Gateway Service sapgwXX

Logical System Name <SID>CLNT800

SAP Client 800




SAP System ID <SID>

SAP System Number <System Number of the SAPserver>

System Type SAP_BW

4. Create a new alias called TRAINING_SYSTEM_XX where XX is replacedwith your user number.

a) Select System Aliases in the Display list box.

b) Enter the Alias Name TRAINING_SYSTEM_XX.

c) Click Add.

5. Save your changes.

a) Click Save.

b) Click Close.



Lesson Summary

You should now be able to:• Create a new system for the BusinessObjects Enterprise system


BO100 Lesson: Creating BusinessObjects Enterprise content iViews

Lesson: Creating BusinessObjects Enterprise contentiViews

Lesson OverviewIn this lesson, you will learn how to create iViews displaying BusinessObjectsEnterprise content.


• Create new iViews for BusinessObjects Enterprise content


Create a new iView for BusinessObjects EnterprisecontentBusinessObjects Enterprise content can be hosted by providing the content specificparameters when creating a new iView based on the imported BusinessObjectsEnterprise iView template.



To create a new iView


2. Navigate to Content Administration > Portal Content.

3. Open the folder Portal Content.

4. Navigate to the folder you created previously when creating the SystemLandscape.


Figure 238: Folder

6. Select the menu New > iView.

Figure 239: New>iView

7. Ensure the option iView template is selected.

8. Click Next.

9. Select BusinessObjects XI Integration for SAP Solutions– iView templateoption.

10. Click Next.




Figure 240: Next

11. Enter the following details:

iView NameThis is a display name that appears in the Portal Catalog, Dialog Box andWindow that displays a list of iViews.

The iView name may contain up to 40 characters of any type, includingspaces, but not apostrophes and quotation marks.

iView IDThis is the unique identifier registered in the Portal Content Directory. ThisID appears within the portal administrator environment.

The iView ID may contain 40 characters and include alphanumericcharacters, underscores (_), dashes (-), dots (.) exclamation point (!), tilde(~) and parentheses. Other special characters and spaces are not permitted.

iView ID PrefixIf you want all your iViews to follow a specific naming convention, makingthem easier to locate, you can add a uniform prefix to each system you create.

12. Click Next.

Figure 241: Next




13. Select the option Standard BusinessObjects Enterprise Report.

Note: This step allows you to choose between a standard reportstored to BusinessObjects Enterprise or a report that has beenpublished via the publishing integration between SAP BW andCrystal Reports.

14. Click Next.

Figure 242: Click Next

15. Enter the SAP system alias that was created earlier.

16. Enter the report number into the field BusinessObjects Enterprise ReportID.

Note: The report ID is shown as part of the object properties inInfoView and the Central Management Console (CMC).

If you specify an ID that does not exist, later when viewing the iviewyou will just get a blank page without any errors.

17. Enter the following into the Application Parameters:

cms_name=<CMS>:<CMS_PORT>

where

<CMS>

is replaced with your name of the Central Management Server and

<CMS_PORT>

is replaced with the port configured for the Central Management Server. Forexample: cms_name = TWDFXXXX:6400

18. In Viewer Application Page, specify reportView.do

19. Select the BusinessObjects Enterprise Viewer and a BusinessObjectsviewing type.

20. Click Next.




Figure 243: Next

21. Select the option Open for editing when wizard completes.

22. Click Finish.

Figure 244: Finish

23. Click Preview.

You can now add this iView to any page in the portal. Open the page whereyou want to add this iView (If you don't have a page, right-click on a folderand select New Page), right click on the iView you want to add and selectAdd iView to Page > Delta link.





Exercise 27: Creating iViews forBusinessObjects content

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create iViews for content from BusinessObjects Enterprise

Business ExampleYou are a portal administrator and need to create a new iView to show contentfrom your BusinessObjects Enterprise system.



2. Create a new iView for a Crystal Report object displaying data from theSAP BW system.Use the following details:

- iView Name: Crystal Reports iView.

- iView ID: IVIEW_01_XX (XX is replaced with your user number).

- iView ID Prefix: com.sap.



Solution 27: Creating iViews forBusinessObjects contentTask:[Enter a high level description of the task the learner will perform in this exercise.]


2. Create a new iView for a Crystal Report object displaying data from theSAP BW system.Use the following details:

- iView Name: Crystal Reports iView.






a) Navigate to Content Administration > Portal Content.

b) Open the folder Portal Content.

c) Navigate to the previously created folder.

d) Right-click the folder.

e) Select the menu New > iView.

f) Ensure the option iView template is selected.

g) Click Next.

h) Select BusinessObjects XI Integration for SAP Solutions– iViewtemplate option.

i) Click Next.

j) Enter iView ID

k) Enter iView ID Prefix

l) Click Next.

m) Select the option Standard BusinessObjects Enterprise Report.

n) Click Next.

o) Enter the SAP system alias that was created earlier.

p) Enter the report number into the field BusinessObjects EnterpriseReport ID.

Note: The report ID is shown as part of the object properties inInfoView and the Central Management Console (CMC).

q) Enter the following into the Application Parameters:

cms_name=<CMS>:<CMS_PORT>

where <CMS> is replaced with your name of the Central ManagementServer and <CMS_PORT> is replaced with the port configured for theCentral Management Server. For example TWDFXXXX:6400.

r) Select a BusinessObjects Enterprise Viewer and a viewing type.

s) Click Next.

t) Select the option Open for editing when wizard completes.

u) Click Finish.

v) Click Preview.



Lesson Summary

You should now be able to:• Create new iViews for BusinessObjects Enterprise content


BO100 Lesson: Creating portal pages

Lesson: Creating portal pages

Lesson OverviewIn this lesson, you will learn about SAP portal pages. You will learn how to createnew 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 PagesA portal Page can organize and display the content that is presented to the enduser. The content can be organized according to topics, Roles, and various othercategories.

A portal Page can contain iViews and other Pages containing iViews.



To create a new portal Page


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 245: Right-click

5. Select New > Page.

Figure 246: New>Page




6. Complete the following fields:

• Page NameThe Page name is a display name that appears in the portal contentcatalog.

• Page IDEnter a unique identifier up to 100 characters for the page. The PageID may include alphanumeric characters, underscores (_), dashes (-),percent signs (%), tildes (~) and parentheses. Other special charactersand spaces are not permitted.

• Page ID PrefixEnter a prefix for the Page name. This option is useful if you want allyour portal Pages to follow a specific naming convention, thus makingthem easier to locate since they contain a uniform prefix.

• Master LanguageChoose the master language for metadata defined in the new portalPage.

• DescriptionEnter a brief description of the portal Page.

7. Click Next.

Figure 247: Next

Note: The Default Page Template creates a Page based on theregular portal Page template. The Web Dynpro Proxy Page creates aPage based on Web Dynpro technology.

8. Select Default Page Template.

9. Click Next.




Figure 248: Next

10. Select the page layout and add it to the Selected Layouts list.

11. Click Next.

12. Click Finish.

Figure 249: Finish

13. Ensure the option Open the object for editing is selected.

14. Click OK.

15. Right-click the iView.

Figure 250: iView

16. Select Add iView to Page > Delta Link.




Figure 251: Add iView to Page>Delta Link

17. Click Page Layout for the portal Page.

Figure 252: Page Layout

18. Click the iView placeholder appearing in the layout.

19. Select Appearance – size in the Property Category of the Property Editor.

Figure 253: Appearance-Size

20. Set the Height Type option to FULL_PAGE.

21. Click Save.

22. Click Page Content for the portal Page.




Figure 254: Page Content

23. Select the iView and click Properties.

Note: The Property Editor now displayes the properties of theselected 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.



Exercise 28: Creating a portal Page andadding an iView to the Page

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new portal Page• Add a portal iView to the portal Page

Business ExampleYou are a portal content administrator and need to create a new portal Pagecontaining a portal iView that will display the content to your end users.



2. Navigate to the Portal Content Administration tab.

3. Create a new portal Page with the following details:

• Portal Page Name: SAP Training Page XX

• Page ID: TRAINXX_PAGE

• Page ID Prefix com.sap

4. Add the previously created iView to the portal Page.

5. Change the Page Layout to have a full height.



Solution 28: Creating a portal Page andadding an iView to the PageTask:[Enter a high level description of the task the learner will perform in this exercise.]



3. Create a new portal Page with the following details:

• Portal Page Name: SAP Training Page XX

• Page ID: TRAINXX_PAGE

• Page ID Prefix com.sap

a) Navigate to the required folder in the Portal Content directory.

b) Right-click on the folder.

c) Select New > Page.

d) Complete the following fields:

• Page Name• Page ID• Page ID Prefix• Master Language• Description

e) Click Next.

f) Select Default Page Template.

g) Click Next.

h) Select the page layout 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.




4. Add the previously created iView to the portal Page.

a) Right-click the iView.

b) Select Add iView to Page > Delta Link.

c) Click Page Layout for the portal Page.

d) Click the iView placeholder appearing in the layout.

5. Change the Page Layout to have a full height.

a) Select Appearance – size in the Property Category of the PropertyEditor.

b) Set the Height Type option to FULL_PAGE.

c) Click Save.

d) Click Page Content for the portal Page.

e) Select the iView and click Properties.

f) Select Appearance – size in the Property Category of the PropertyEditor.

g) Set the Height Type option to FULL_PAGE.

h) Click Save.

i) Click Preview.



Lesson Summary

You should now be able to:• Create a portal page• Define the content and layout of portal pages

Related Information

• [Enter an optional reference using the URL or CrossReference tag toadditional information that learner may find useful. Examples includewebsites or whitepapers. Delete if not used.]


BO100 Lesson: Creating portal worksets

Lesson: Creating portal worksets

Lesson OverviewIn this lesson, you will learn about SAP portal Worksets. You will learn how tocreate new portal Workset and how to assign portal Pages and portal iViews toWorkset.


• Create portal Worksets• Assign content to portal Worksets


Portal WorksetsWorksets allow the content administrator to combine iViews and Pages. Worksetsare reusable structures that are added to a portal Role. A Workset cannot beassigned to users directly.



To create a new portal workset



3. Navigate to the required folder in the Portal Content directory.


5. Select New > Workset.


• Workset NameThe Workset name is a display name that appears in the Portal ContentCatalog.

• Workset IDEnter a unique identifier for the Workset here. The Page ID may includealphanumeric characters, underscores (_), dashes (-), percent signs(%), tilde (~) and parentheses. Other special characters or spaces arenot permitted.

• Workset ID PrefixEnter a prefix for the Workset name. This option is useful if you wantall your portal content objects to follow a specific naming convention,thus making them easier to locate since they contain a uniform prefix.

• Master LanguageChoose the master language for metadata defined in the new Workset.

• DescriptionEnter a brief description of the Workset.

7. Click Next.

8. Click Finish.


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.

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 appearancein 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 apreview mode.





Exercise 29: Creating a portal Workset

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new portal Workset• Add a portal Page to the Workset

Business ExampleYou are a portal content administrator and need to create a new portal Worksetcontaining a portal Page that will display the content to your end users.




3. Create a new portal Workset:

• Workset Name: SAP Training Workset XX

• Workset ID: TRAINXX_WKS

• Workset ID Prefix: com.sap

4. Create a folder as part of the Workset.

5. Add the previously created portal Page to the top level of the Workset.

6. Add the previously created portal Page to the folder of the Workset.



Solution 29: Creating a portal WorksetTask:[Enter a high level description of the task the learner will perform in this exercise.]



3. Create a new portal Workset:

• Workset Name: SAP Training Workset XX

• Workset ID: TRAINXX_WKS

• Workset ID Prefix: com.sap

a) Navigate to the required folder in the Portal Content directory.

b) Right-click the folder.

c) Select New > Workset.

d) Complete the following fields:• Workset Name• Workset ID• Workset ID Prefix• Master Language• Description

e) Click Next.

f) Click Finish.

g) Ensure the option Open the object for editing is selected.

h) Click OK.

i) Click New Folder.

j) Enter the Folder Name and Folder ID.

4. Create a folder as part of the Workset.

a) Click Create New Folder.

5. Add the previously created portal Page to the top level of the Workset.

a) Right-click the Page to be added to the Workset.

b) Select Add Page to Workset > Delta Link.




6. Add the previously created portal Page to the folder of the Workset.

a) Click the folder in the Workset.

b) Right-click the portal Page.

c) Select Add Page to Workset > Delta Link.

d) Click Close.



Lesson Summary

You should now be able to:• Create portal Worksets• Assign content to portal Worksets


BO100 Lesson: Creating portal roles

Lesson: Creating portal roles

Lesson OverviewIn this lesson, you will learn about SAP portal Roles. You will learn how to createnew 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 RolesA portal Role can organize and display the content that is being displayed to theend user.



To create a new portal Role



3. Navigate to Portal Content tab.


Figure 255: folder

5. Select New > Role.

Figure 256: New>Role





• Role NameThe Role name is a display name that appears in the Portal ContentCatalog.

• Role IDEnter a unique identifier for the Role here. The Role ID may includealphanumeric characters, underscores (_), dashes (-), percent signs(%), tilde (~) and parentheses. Other special characters or spaces arenot permitted.

• Role ID PrefixEnter a prefix for the Role ID. This option is useful if you want all yourportal content objects to follow a specific naming convention, thusmaking them easier to locate since they contain a uniform prefix.

• Master LanguageChoose the master language for metadata defined in the new Role.

• DescriptionEnter a brief description of the Workset.

7. Click Next.

8. Click Finish.

Figure 257: Finish


10. Click OK.

11. Right-click the Workset.




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

Figure 259: 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 portalcontent. As a next step, you need to assign the Role to the relevantport users.

Assign a portal Role to a portal UserPortal User AdministrationBy assigning a user to a portal Role, the user is granted access to the contentand rights assigned to the Role.



To assign the portal Role to a portal User


2. Navigate to User Administration tab.

Figure 260: User Administration

3. Search for the portal user.

Figure 261: portal user

4. Click the Logon ID.

Figure 262: Logon ID

5. Click the Assigned Roles tab.

6. Click Modify.




7. Search for the portal Role in the left screen.

Figure 263: 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 portalRole is an entry point, the created portal Role should now appear inthe top-level navigation.



Exercise 30: Creating a portal Role

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new portal Role• Add a Page to the portal Role

Business ExampleYou are a portal content administrator and need to create a new portal Rolecontaining a portal Workset that will display the content to your end users.




3. Create a new portal Role with the following details:

- Role Name TRAINXX_ROLE

- Role ID TRAINXX_ROLE

- Role ID Prefix com.sap

Note: Replace XX with your user number.

4. Add the previously created Workset to the portal Role.

5. Set the portal Role to become an entry point.

6. Save the changes.



Solution 30: Creating a portal RoleTask:[Enter a high level description of the task the learner will perform in this exercise.]



3. Create a new portal Role with the following details:

- Role Name TRAINXX_ROLE

- Role ID TRAINXX_ROLE

- Role ID Prefix com.sap

Note: Replace XX with your user number.

a) Navigate to Portal Content tab.

b) Right-click the folder.

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) Ensure the option Open the object for editing is selected.

h) Click OK.

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




5. Set the portal Role to become an entry point.

a) Right-click Properties.

b) Select Navigation in the Property Category list box of the PropertyEditor.

c) Set the Entry Point property to Yes.

6. Save the changes.

a) Click Save.

b) Click Close.





Exercise 31: Assigning the portal user tothe portal Role

Exercise ObjectivesAfter completing this exercise, you will be able to:• Assign a portal User to a portal Role

Business ExampleYou are a portal content administrator and need to assign a portal Role to a portalUser.



2. Assign the Portal User from the previous activity to the portal Role youcreated.

3. Refresh your browser window to view the Role and the iView.



Solution 31: Assigning the portal user tothe portal RoleTask:[Enter a high level description of the task the learner will perform in this exercise.]


2. Assign the Portal User from the previous activity to the portal Role youcreated.

a) Navigate to User Administration tab.

b) Search for the portal user.

c) Click the Logon ID.

d) Click the Assigned Roles tab.

e) Click Modify.

f) Search for the portal Role in the left screen.

g) Select the available Role by clicking the table grid (left-hand side).

h) Click Add.

i) Click Save.

3. Refresh your browser window to view the Role and the iView.



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



Lesson: BusinessObjects Enterprise RepositoryManager

Lesson OverviewIn this lesson, you will learn how to configure the BusinessObjects EnterpriseRepository Manager to integrate your system with the Knowledge Managementpart 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 ExampleBusinessObjects XI Integration for SAP Solutions delivers integration with theKnowledge Management part of SAP Enterprise Portal where the administratorcan create repository integration with the Knowledge Management and leveragefunctionality like subscriptions, discussion and feedback to enhance theinformation provided by the BusinessObjects Enterprise repository.

Configuring the BusinessObjects Repository ManagerThe Knowledge Management integration is delivered as a portal archive (PAR)file. The administrator needs to configure the BusinessObjects Enterprise specificvalues for each BusinessObjects Enterprise server after the portal archive hasbeen uploaded.


BO100 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 264: System Administration>Support

3. Click Portal Runtime.

Figure 265: Portal Runtime

4. Select Administration Console.

Figure 266: 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 Enterprise12.0\java\applications. The filename is BusinessObjectsKM.par

7. Click Upload.




After a successful deployment of the portal archive file you will find aninstance of the BusinessObjects Enterprise repository manager.



To verify the installation



Figure 267: System Administration>System Configuration

3. Open the folder Knowledge Management.

Figure 268: Knowledge Management

4. Click Content Management.

Figure 269: Content Management




5. Click Repository Managers.

6. Select the BusinessObjects Repository Manager (com.businessob-jects.kmc.manager.).

7. Select the entry and view the definition.

Figure 270: View the Definition

Note: The Enterprise Portal system is now configured to create newBusinessObjects Enterprise based repositories.



To create a new repository manager integration withyour BusinessObjects Enterprise system



3. Open the folder Knowledge Management.

4. Click Content Management.

Figure 271: Content Management

5. Click Repository Managers.

6. Click Business Objects Repository.

7. Click New.

Figure 272: New




8. Enter a name and description for the repository.

Note: Enter the name of your BOE repository as you want it to bedisplayed 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 beused to show the repository in the Knowledge Management content,

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: <server name>:8080

12. Replace the placeholder %WEB_SERVER_AND_PORT% for the fieldDispatch URL with values from your BusinessObjects Enterprise system.

Note: For example: http://<server name>:8080/SAP/jsp/Ac-tion_Dispatch/dispatch.jsp

13. Replace the placeholder %WEB_SERVER_AND_PORT% for the fieldOpenDoc URL with values from your BusinessObjects Enterprise system.

Note: For example: http://<server name>:8080/OpenDocu-ment/opendoc/openDocument.jsp

14. Replace the placeholder %SAP_CLIENT% for the field SAP Client withthe value of the SAP system that will be used in combination with yourBusinessObjects Enterprise system.




15. Replace the placeholder %SAP_SYSID% for the field SAP System ID withthe value of the SAP system that will be used in combination with yourBusinessObjects Enterprise system.

16. Replace the placeholder %WEB_SERVER_AND_PORT% for the field URLto Logoff BOE with values from your BusinessObjects Enterprise system.

Note: For example: http://<server name>:8080/PartnerPlatformSer-vice/service/app/logoff.do

17. Replace the placeholder %WEB_SERVER_AND_PORT% for the field WebService URL with values from your BusinessObjects Enterprise system.

Note: For example: http://<server name>:8080/dswsbobje/services/

18. Click OK.

Note: The newly created repository manager should appear in thelist of available repository managers after this step.

In order to make BusinessObjects-specific properties and commandsavailable, the layout set of your configured BusinessObjects Enterpriserepository needs to be changed into the BusinessObjects specific layout,which is named BOBJELayout.

19. Navigate to Content Administration > KM Content > KM Content.

Figure 273: KM Content

Note: The newly created repository should appear in the list.

20. Click on the context menu symbol of the repository.




Figure 274: Content menu symbol

21. Select Details.

Figure 275: Details

22. Select the menu Settings > Presentation.

Figure 276: Settings>Presentation

23. Click Select Profile.




Figure 277: 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 ManagerAfter configuration of the Repository Manager you can use the newly createdentry for viewing and creating reports, providing feedback and ranking of reportsand several other collaboration features.

After the successful configuration of the Repository Manager you can leverage thefull functionality of BusinessObjects Enterprise inside the SAP Enterprise Portal.



To use the Repository Manager





3. Click on the repository.

Figure 279: Repository

Menu ViewThe menu item View allows you to switch between a view by Folders orby Category.




Figure 280: Menu item view

Menu FolderThe menu Folder > New allows you to create new documents in the sameway you can create new content in InfoView.

Figure 281: Menu folder

The other options in the menu Folder are to view the detailed properties ofthe selected object and to fresh the folder structure manually.

Menu SelectionThe menu Selection allows you to copy, move, and delete objects insidethe repository.

Figure 282: Menu selection

Menu Go ToWith the menu Go To you can navigate to InfoView and the recently usedobjects.




Figure 283: Menu Go To

Menu BusinessObjectsThe menu item BusinessObjects allows you to navigate to InfoView.

Figure 284: Menu BusinessObjects

Context menusEach object part of the repository offers a context menu that, depending onthe object type, allows you to use certain functions.

In the image below, the context menu of a Crystal Report object is shown.

Figure 285: Context menu

Using collaboration featuresThe Repository Manager as part of Knowledge Management also allows the userto use some collaboration features.



To use the collaboration features





3. Click on the repository.

Figure 287: Repository

4. Navigate to a report object following your folder structure.

Figure 288: Report objectContinued on next page



5. Open the context menu of the object.

Figure 289: Context menu

6. Select Details.

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

Figure 291: Close

Note: The changes made will appear as part of the display.

Creating an iView for the Repository ManagerSAP Enterprise Portal delivers several iView templates for the KnowledgeManagement area. For this purposes, use the standard Knowledge ManagementNavigation iView.



To create a new iView


2. Navigate to Content Administration > Portal Content.

3. Open the folder Portal Content.

4. Navigate to the previously created folder.


Figure 292: Folder

6. Select the menu New > iView.

Figure 293: iView

7. Ensure the option iView template is selected.

8. Click Next.

9. Select the KM Navigation iView.

10. Click Next.




Figure 294: Next

11. Enter the following details:

iView NameThis is a display name that appears in the Portal Catalog, Dialog Box andWindow that displays a list of iViews.

The iView name may contain up to 40 characters of any type, includingspaces, but not apostrophes and quotation marks.

iView IDThis is the unique identifier registered in the Portal Content Directory. ThisID appears within the portal administrator environment.

The iView ID may contain 40 characters and include alphanumericcharacters, underscores (_), dashes (-), dots (.) exclamation point (!), tilde(~) and parentheses. Other special characters and spaces are not permitted.

iView ID PrefixIf you want all your iViews to follow a specific naming convention, makingthem 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 RootFolder for Navigation to the prefix of your Repository Manager.

18. Click Save.

19. Click Preview.

20. Click Close.



Exercise 32: Create a newBusinessObjects Repository Manager

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a new BusinessObjects Repository Manager

Business ExampleYou are a portal content administrator and need to create a new RepositoryManager for your BusinessObjects Enterprise system.



2. Navigate to System Administration > System Configuration > KnowledgeManagement.

3. Create a new Repository Manager for your BusinessObjects Enterprisesystem.

Use the following details:

- Name: TRAINXX (replace XX with your user number).- Prefix: /TRAINXX (replace XX with your user number).

4. Replace the required parameters with values for your BusinessObjectsEnterprise system.

5. Configure the Layout of the new repository to the AdminExplorerBOElayout.



Solution 32: Create a newBusinessObjects Repository ManagerTask:[Enter a high level description of the task the learner will perform in this exercise.]


2. Navigate to System Administration > System Configuration > KnowledgeManagement.

a) Navigate to System Administration > System Configuration.

b) Open the folder Knowledge Management.

3. Create a new Repository Manager for your BusinessObjects Enterprisesystem.


- Name: TRAINXX (replace XX with your user number).- Prefix: /TRAINXX (replace XX with your user number).

a) Click Content Management.

b) Click Repository Managers.

c) Click Business Objects Repository.

d) Click New.

e) Enter a name and description for the repository.

f) Enter a Prefix for the repository.

g) Select the required Repository Services.

h) Enter the name of your CMS with port into CMS Host and Port.




4. Replace the required parameters with values for your BusinessObjectsEnterprise system.

a) Replace the placeholder %WEB_SERVER_AND_PORT% for thefield Dispatch URL with values from your BusinessObjects Enterprisesystem.

b) Replace the placeholder %WEB_SERVER_AND_PORT% for the fieldOpenDoc URL with values from your BusinessObjects Enterprisesystem.

c) Replace the placeholder %SAP_CLIENT% for the field SAP Clientwith the value of the SAP system that will be used in combination withyour BusinessObjects Enterprise system.

d) Replace the placeholder %SAP_SYSID% for the field SAP System IDwith the value of the SAP system that will be used in combination withyour BusinessObjects Enterprise system.

e) Replace the placeholder %WEB_SERVER_AND_PORT% for the fieldURL to Logoff BOE with values from your BusinessObjects Enterprisesystem.

f) Replace the placeholder %WEB_SERVER_AND_PORT% for the fieldWeb Service URL with values from your BusinessObjects Enterprisesystem.

g) Click OK.

5. Configure the Layout of the new repository to the AdminExplorerBOElayout.

a) Navigate to Content Administration > KM Content > KM Content.

b) Click on the context menu symbol of the repository.

c) Select Details.

d) Select the menu Settings > Presentation.

e) Click Select Profile.

f) Select the option Layout Set.

g) Select AdminExplorerBOE from the list box.

h) Click OK.

i) Select the option Apply settings to all subfolders.

j) Click Save.

k) Click Close.





Exercise 33: Creating a KnowledgeManagement iView

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create an iView for the BusinessObjects Repository Manager

Business ExampleYou are a portal administrator and need to create a new iView to show the contentfrom the BusinessObjects Repository Manager.



2. Create a new iView using the Knowledge Management Navigation iViewtemplate.


- iView Name: Repository Manager iView.



3. Add the iView to your existing portal Page.



Solution 33: Creating a KnowledgeManagement iViewTask:[Enter a high level description of the task the learner will perform in this exercise.]


2. Create a new iView using the Knowledge Management Navigation iViewtemplate.


- iView Name: Repository Manager iView.



a) Navigate to Content Administration > Portal Content.

b) Open the folder Portal Content.

c) Navigate to the previously created folder.

d) Right-click the folder.

e) Select the menu New > iView.

f) Ensure the option iView template is selected.

g) Click Next.

h) Select the KM Navigation iView.

i) Click Next.

j) Enter the following details:

iView NameiView IDiView ID Prefix

k) Click Next.

l) Click Finish.




3. Add the iView to your existing portal Page.

a) Select the option Open the object for editing.

b) Click OK.

c) Select the Property Category Show All.

d) Set the property Path to Initially Displayed Folder and Path to RootFolder for Navigation to the prefix of your Repository Manager.

e) Click Save.

f) Click Preview.

g) Click Close.



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


BO100 Unit Summary

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


Unit Summary BO100



Test Your Knowledge

1. How many Crystal Reports can be displayed in a BusinessObjects iViewtemplate?Choose the correct answer(s).□ A 1□ B 2□ C 1 or more□ D None

2. An iView can be added to a Page and Workset?Determine whether this statement is true or false.□ True□ False

3. An iView can be added to a Page and Workset?Determine whether this statement is true or false.□ True□ False



Answers

1. How many Crystal Reports can be displayed in a BusinessObjects iViewtemplate?

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?


Unit 15Troubleshooting the SAP Connectivity

Unit Overview[Enter a brief overview of the unit.]hugo


• Describe the best practices which may be taken to maximize the performanceof Web Intelligence reports against BW.

• Trace and troubleshoot the SAP connectivity for Web Intelligence or Voyager• Describe the process flow for creating an OLAP Universe• Describe the process flow for viewing a Web Intelligence report• Trace and troubleshoot the SAP connectivity for Crystal Reports• Use OLAP BAPI functions• Use the OLAP trace tool RSRTRACE• Use the MDX Testeditor (transaction MDXTEST)

Unit ContentsLesson: Troubleshooting Web Intelligence connectivity .. . . . . . . . . . . . . . . . . .614

Procedure: To activate the connectivity trace for Web Intelligence ..619Lesson: Troubleshooting Crystal Reports connectivity .. . . . . . . . . . . . . . . . . . .622

Procedure: To activate the connectivity trace for Crystal Reports .. .624Lesson: Additional troubleshooting tools .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .627

Procedure: To call the BAPI function BAPI_MD-PROVIDER_GET_CUBES ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .628Procedure: To call the BAPI function BAPI_MDPROVIDER_GET_MEM-BERS... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .630Procedure: To activate the OLAP trace... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635Procedure: To view the results of an OLAP trace ... . . . . . . . . . . . . . . . . . . .636Procedure: To start the MDX Testeditor .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .638


Unit 15: Troubleshooting the SAP Connectivity BO100

Lesson: Troubleshooting Web Intelligence connectivity

Lesson OverviewThis lesson aims to provide guidance for a successful deployment of WebIntelligence as a front-end to SAP NetWeaver Business Warehouse (BW). It isintended to guide you through the high-level troubleshooting concepts relevantto such an implementation, and to highlight the best practices to consider in thecourse of such a deployment.


• Describe the best practices which may be taken to maximize the performanceof Web Intelligence reports against BW.

• Trace and troubleshoot the SAP connectivity for Web Intelligence or Voyager• Describe the process flow for creating an OLAP Universe• Describe the process flow for viewing a Web Intelligence report

Business ExampleYou have multiple Infocubes, DSO, Infosets, and hundreds BEx querie. Most ofthe BEx queries take long time to run; therefore you are trying to determine thebest performance strategy for building reports that run over SAP BW data. Youdecide to use Web Intelligence and build universes around the Infocubes for thesehundreds of queries and you need to know the best practices in deploying thissolution so that these universes built would serve the purpose for future reportingrequirements.

Overall RecommendationA primary focus of this document is a set of practices and steps which may betaken to maximize the performance of Web Intelligence reports against BW. Inthis context, maximizing performance refers to a balance of minimizing:

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


BO100 Lesson: Troubleshooting Web Intelligence connectivity

BEx Queries as recommended data sourcesBEx Queries are recommended as data sources for generating universes for thefollowing reasons:

1. BEx Queries offer a flexible extension to the data modeling environment.InfoCubes require more effort to change.

2. BEx Queries offer significant functionality to create customized data sourcesthat meet end-user requirements, such as Calculated Key Figures, RestrictedKey Figures, Structures and SAP Variables.

3. In the OLAP BAPI interface, not all BW metadata features can be retrievedon 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 BExQuery for every report, nor do you need a universe for every existing BEx Query.To minimize maintenance costs, focus the implementation strategy on limitingthe final number of BEx Queries and universes required to meet all the ad-hocquery and reporting needs.



Keep in mind the following points to reduce the number of universes needed:

• When Web Intelligence is the front-end tool, you are not restricted by theoutput format in the BEx Query.

• There is no direct impact on performance when working with OLAPuniverses created from large BEx Queries. OLAP universe objects notincluded in the Web Intelligence query have no direct impact on the queryperformance.

Note:

• It is recommended to have a few BEx Queries from a single one to ahandful of them for every InfoCube or MultiCube that is in scopefor ad-hoc query and reporting. Then build a universe on top ofeach of these BEx Queries.

• Do not build one query per InfoProvider because elements canadd processing time even though you not using them into the WebIntelligence report.

• Set the property Use Selection of Structure Members in transactionRSRT for the query to ensure structure elements are sent to thedatabase for processing.

Common scenarios and decisionsWhile every implementation and individual reporting requirement is unique, mosthave common elements. The following section details several common scenariosyou will come across and gives guidance on optimizing universe, Web Intelligencequery, and BEx Query design for each scenario.

Customizing BW universe defniitionWhile the default universe generated for a BW query or cube is usable, it containsa lot of elements which might not be required for most reporting needs, and otherelements which may require some tuning based on the detailed requirements. Forexample, when a characteristic has no active hierarchy, the L00 node will be Allmembers, and will not provide any reporting value. In this case, it is best to deleteall L00 objects in order to simplify the report design experience.

Scheduling VS on-demand reportingOne of the factors to consider when designing a report is whether it is necessary tohave the report run on-demand or if the reporting need can be met by having usersaccess scheduled instances of the report. In general, if is possible to minimize the



number of times a report is run against the BW system, it is desirable to do so.So, it is recommended to use scheduling when practical. The primary benefits ofscheduling 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.

FilteringIn all but the most basic cases, it is necessary to filter the data exposed by anInfoCube or BEx Query in order to get the desired result. There are severalmethods which may be employed to filter the results. The method applied mayhave an impact on the overall performance of the reports. Generally, filteringrequirements can be separated into 2 categories: static filtering, which will applythe same values each time the report is run, and dynamic filtering, which willfilter results based on user or other input.

Reports with high data volumeThe OLAP BAPI interface is not designed to run queries which return a highvolume of data in a single request. This is due both to internal design within theOLAP processor and to the flattening process which occurs before the data can beconsumed by WebI. The volume of data returned can be measured by the numberof cells returned. In general, it is desirable to reduce this number to the minimumrequired for the reporting requirement. This can be done by reducing the numberof columns or rows returned in the request.

Tracing and troubleshooting the Web Intelligence orVoyager connectivityTo be able to trace the SAP connectivity for Web Intelligence or Voyager thenecessary registry entries need to be configured. The entries can be found in thefollowing part of the registry:

Note: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite12.0\MDA\Log.



Figure 295: Registry Editor

The image shows that underneath the Log entry, each module of the OLAPconnectivity can be configured for tracing. For the SAP connectivity, the relevantregistry values are:

Note: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite12.0\MDA\Log\Modules\SAPMODULE

Verbosity (highest value is 10 decimal).

MDX Query Log (full path to the logfile).

Note: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite12.0\MDA\Log

LogFile (full path to the logfile).

These settings will generate two logfiles:

• A MDA logfile that includes all steps that have been performed on the SAPserver side.

• A MDX logfile that includes all executed MDX statements.

Note: After setting the registry value the corresponding services fromBusinessObjects Enterprise need to be restarted (Web Intelligenceservices, Connection Server, Multi Dimensional Analysis Server).



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

Process flow for creating an OLAP UniverseThis image shows the process flow for creating an OLAP Universe on top ofan SAP BW query or cube. The process flow also mentions the OLAP BAPIfunctions that are being used.

Figure 296: Creating an OLAP Universe



Process flow for viewing a Web Intelligence reportThis image shows the process flow for viewing a Web Intelligence report using anOLAP Universe as data source. The process flow also mentions the OLAP BAPIfunctions that are being used.

Figure 297: Viewing a Web Intelligence report



Lesson Summary

You should now be able to:• Describe the best practices which may be taken to maximize the performance

of Web Intelligence reports against BW.• Trace and troubleshoot the SAP connectivity for Web Intelligence or Voyager• Describe the process flow for creating an OLAP Universe• Describe the process flow for viewing a Web Intelligence report



Lesson: Troubleshooting Crystal Reports connectivity



• Trace and troubleshoot the SAP connectivity for Crystal Reports

Business ExampleYou need to describe the process for troubleshooting the Crystal Reportsconnectivity.

Tracing and troubleshooting the Crystal ReportsconnectivityTo be able to trace the SAP connectivity for Crystal Reports the necessary registryentries 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 of the connectivities has its own folder.For example, the BW MDX Driver entry:

Figure 298: BW MDX Driver entry

Each of the connectivity registry keys has a value called Trace which accepts aYes or No as a value.

In addition to the Trace value, the user needs to configure the trace directory. Thevalue for this setting is under the registry key SAP.


BO100 Lesson: Troubleshooting Crystal Reports connectivity

Figure 299: Registry key SAP

Note: The registry entry TraceDir is not created during the installationand needs to be created manually.



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

SAP BW connectivityFor the SAP BW connectivity you can also look at the following items as part ofthe troubleshooting process:

• Use transaction MDXTEST to verify the MDX statement used by CrystalReports and to verify the data.

• Use transaction SE37 to call the OLAP BAPI function manually so that youcan verify the metadata retrieved by Crystal Reports.

• Use transaction RSRTRACE to create an OLAP trace on the SAP BW server.

SAP InfoSet and InfoSet query connectivityFor the SAP InfoSet and InfoSet query connectivity, you can also look at thefollowing items as part of the troubleshooting process:

• Use transaction ST01 to trace the authorizations and to avoid any missingauthorizations.

• Validate the settings in transactions SQ01, SQ02, and SQ03 and ensure theInfoSet (or InfoSet query) is assigned to the correct environment variableand user group.

• You can use the QuickViewer to create a view on top of tables or logicaldatabase in case the issue might be in a layer further down.


BO100 Lesson: Troubleshooting Crystal Reports connectivity

Tables, cluster, and function connectivityFor the SAP table, cluster, and function connectivity you can also look at thefollowing items as part of the troubleshooting process:

• Use transaction SE11 and SE16 to validate the data from the tables.• Use transaction STMS to ensure the transports have been imported.• Use transaction SE37 to validate the underlying functions.



Lesson Summary

You should now be able to:• Trace and troubleshoot the SAP connectivity for Crystal Reports


BO100 Lesson: Additional troubleshooting tools

Lesson: Additional troubleshooting tools



• Use OLAP BAPI functions• Use the OLAP trace tool RSRTRACE• Use the MDX Testeditor (transaction MDXTEST)

Business Example[Enter a business example that helps the learner understand the practical businessuse of this lesson.]

Using OLAP BAPI functionsThe connectivity for SAP BW is based on OLAP BAPI functions from SAP. TheseBAPI functions can be executed using transaction SE37 (Function builder).

Each of the BAPI functions is different and accepts a different set of inputparameters and will provide a different resultset.

The following are two outlines showing how to use the OLAP BAPI functions.



To call the BAPI function BAPI_MD-PROVIDER_GET_CUBES

1. Start the SAP Logon pad.

2. Log onto the SAP system.

3. Start transaction SE37 (Function Builder).

Figure 300: Initial Screen

4. Enter the function name into the field Function module.

5. Select the menu Function Module > Test > Single Test (an alternative ispressing F8).

Figure 301: Test Function Module: Initial Screen

Note: In the given scenario the BAPI function allows you to specifyinput values.

6. Enter the input parameters.

7. Select the menu Function modules → Execute (F8).




Figure 302: Test Function Module: Result Screen

8. Click on the icon next to the number of entries for your resultset.

Figure 303: Structure Editor

Note: You can export the resultset via the menu System > List >Save > Local file.



To call the BAPI function BAPI_MD-PROVIDER_GET_MEMBERS



3. Start transaction SE37 (Function Builder).

Figure 304: Function Builder: Initial Screen

4. Enter the function name into the field Function module.

5. Select the menu Function Module > Test > Single Test (an alternative ispressing F8).







Figure 305: Test Function Module: Initial Screen

Note: In the given scenario the BAPI function allows you to specifyinput values.

• CAT_NAM

The technical name of the Catalog, which is the technical name of thecube. For example: Z_BOBJ

• CUBE_NAM

The technical name of the query in the syntax CUBE/QUERY. ForExample: Z_BOBJ/UBI_TRAIN_QUERY_SIMPLE

• DIM_UNAM

The member unique name of the dimension. For example:[Z_COUNTRY]

• HRY_UNAM

The unique name of the hierarchy.

• LVL_UNAM

The unique name of the level.

• LVL_NUMBER

The numeric level number.

• START_ROW

The numeric value for a starting row.

• END_ROW

The numeric value for a row.

6. Enter the input parameters.




Figure 306: Input parameters

7. Select the menu Function modules > Execute (F8).

Figure 307: Structure Editor: Display MEMBERS from Entry

8. Click on the icon next to the number of entries for your resultset.

Note: You can click Single Entry to view all values for one row.



Using the OLAP trace tool (RSRTRACE)The OLAP trace tool allows you to trace all OLAP related functions on the SAPBW server. The benefit of the tool is that the actual trace is stored on the BWserver and in this way the steps can be recalled.



To activate the OLAP trace



3. Start transaction RSRTRACE.

Figure 308: Configure trace tool

4. Enter the user name into the field User.

5. Click Activate User.

6. Perform the tasks that have to be traced.



To view the results of an OLAP trace



3. Start transaction RSRTRACE.

4. Click All Logs.

Note: The option User logs shows the logs that belong to the currentuser.

Figure 309: Logs

Note: A list of logs is displayed and the administrator is able toview them.

5. Double-click the log entry.




Figure 310: Processing of logged callups

Note: All used functions are listed and can now be entered via theABAP debugger.

MDX TesteditorBy using the MDX Testeditor the user can test BW queries with a sample MDXstatement.



To start the MDX Testeditor


2. Start transaction MDXTEST (MDX Testeditor).

Figure 311: MDX testeditor

Note: In the MDX Testeditor the phrase CATALOG refers to theBW cube and the phrase CUBE refers to the BW query.

3. Select the BW cube from the list box CATALOG.

Note: The entry InfoProvider refers to the option to connect directlyto cubes without the usage of a BW query.

4. Select the BW query from the list box CUBE.




Figure 312: MDX Testeditor

Note: The screen shows all available elements of the select BWquery.

5. Click Generated Test Sequence.


Note: The MDX Testeditor generates a MDX test sequence. The testsequence includes all measures (keyfigures) and one characteristic(dimension).

6. Click Run Query Multidim. to execute the MDX Statement.







Lesson Summary

You should now be able to:• Use OLAP BAPI functions• Use the OLAP trace tool RSRTRACE• Use the MDX Testeditor (transaction MDXTEST)


Unit Summary BO100

Unit SummaryYou should now be able to:• Describe the best practices which may be taken to maximize the performance

of Web Intelligence reports against BW.• Trace and troubleshoot the SAP connectivity for Web Intelligence or Voyager• Describe the process flow for creating an OLAP Universe• Describe the process flow for viewing a Web Intelligence report• Trace and troubleshoot the SAP connectivity for Crystal Reports• Use OLAP BAPI functions• Use the OLAP trace tool RSRTRACE• Use the MDX Testeditor (transaction MDXTEST)


BO100 Course Summary

Course SummaryYou should now be able to:

• Describe the integration of SAP BusinessObjects software with SAPNetWeaver 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


Course Summary BO100


FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.
