Best Practices with SAP BusinessObjects BI for SAP landscapes

Ingo Hilgefort Director, Solution Management Customer Insight & Action

Disclaimer

The information in this document is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information on this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP 2009 / Page 2 AG 2009. All rights reserved. / Page 2

SAP NetWeaver Release

The first integration improvements between SAP and SAP BusinessObjects products are realized with the release of NetWeaver 7.0 EhP1. NetWeaver 7.0 EhP1 is the prerequisite for the following SAP BI Solutions:

    

Business Planning and Consolidation (BPC) based on NetWeaver 7.0 EhP1,
SAP BusinessObjects Explorer version 1.0 and 2.0, Native access of SAP BusinessObjects Xcelsius via BICS, Better Support for Web Intelligence via OLAP Universes, Improved MDX Interface, Direct Access to BW 7.01 via SAP BusinessObjects Data Federator.

© SAP AG 2009. All rights reserved. / Page 3

Best Practices for Xcelsius 4.Agenda 1. Best Practices for SAP BusinessObjects Explorer 5. / Page 4 . Summary 7. Best Practices for Crystal Reports 2. All rights reserved. Further Material © SAP AG 2009. Best Practices for Web Intelligence 3. Best Practices for BW Query Design 6.

layout. All rights reserved. / Page 5 . pagination  High fidelity rendering in all clients and in print  Access to both SAP NetWeaver BW and SAP ERP data  Access to virtually any data source or back-end system Open Connectivity End User Empowerment Enterprise Deployment  Sort and filter without querying the database  Embed Flash for powerful visualization and what-if scenarios  Interoperability with other clients like Pioneer  Multiple broadcasting and file format options for enterprise-wide deployments  Consume reports offline with the Crystal Reports viewer © SAP AG 2009.BI Solution : Enterprise Reporting Product : Crystal Reports Is the market leading standard in enterprise reporting that provides connectivity to any type of data and empowers all end users with a simple and scalable deployment model  The SAP standard enterprise reporting tool for all applications from SAP Business All-in-One to the SAP Business Suite The Standard in Reporting Report Formatting  Easy access to Crystal Reports skills in the market  Precise object layout and positioning  Complete control over font.

print-optimized reports It enables the creation and modification of formatted reports:  Report off of all sources of information in your organization © SAP 2008 / Page 6 AG 2009. / Page 6 . All rights reserved. mass-distribution Operational and tactical applications with low interaction rate (view static and parameterized reports)     Professional report layout (one-to-many approach) Form-based.BI Solution : Enterprise Reporting Product : Crystal Reports Crystal Reports is the market leading tool for highly formatted. compliance. pixel-perfect enterprise reporting Customer Requirements  Highly formatted reports for forms.

All rights reserved.Crystal Reports and SAP NetWeaver BW SAP InfoSet SAP Table. Cluster and Function BW MDX ODS SAP ERP SAP NetWeaver BW BEx Query BI Client BEx Query Table and Cluster Transient Provider Classic InfoSets SAP Queries ABAP Functions Multi Provider InfoSet InfoCube DSO © SAP AG 2009. / Page 7 .

All rights reserved.1  SAP BusinessObjects Integration for SAP Solutions XI 3. / Page 8 . and Cluster Tables  ABAP Data Cluster © SAP AG 2009.1 or SAP BusinessObjects Edge XI 3.1  SAP ERP available data sources   Classic InfoSets & InfoSet Queries ABAP Dictionary – – ABAP Functions Transparent.Crystal Reports & SAP ERP Data Connectivity Overview  Required Software Components   Crystal Reports 2008 Designer SAP BusinessObjects Enterprise XI 3. Pool.

All rights reserved. / Page 9 .Crystal Reports & SAP ERP Data Connectivity – SAP ERP InfoSets © SAP AG 2009.

All rights reserved. the creation of a new InfoSet providing all data should be considered (client side join vs. / Page 10 . server side join) © SAP AG 2009.Crystal Reports & SAP ERP Data Connectivity – SAP ERP InfoSets  Crystal Reports provides access to InfoSets and InfoSet queries  Allows for re-use of logical database and custom logic Crystal Reports provides the view of Global and Local InfoSet / InfoSet Queries  Crystal Reports honors the User Group assignment in transaction SQ02   In fact it is a mandatory step  Performance Considerations  In cases where you plan to leverage two InfoSets in a single Crystal Reports object.

/ Page 11 .Crystal Reports & SAP ERP Data Connectivity – ABAP Functions FUNCTION BAPI_SFLIGHT_GETLIST IMPORTING VALUE(FROMCOUNTRYKEY) LIKE BAPISFDETA-COUNTRYFR VALUE(FROMCITY) LIKE BAPISFDETA-CITYFROM VALUE(TOCOUNTRYKEY) LIKE BAPISFDETA-COUNTRYTO VALUE(TOCITY) LIKE BAPISFDETA-CITYTO VALUE(AIRLINECARRIER) LIKE BAPISFDETA-CARRID DEFAULT SPACE VALUE(AFTERNOON) LIKE BAPI_AUX-AFTERNOON DEFAULT SPACE VALUE(MAXREAD) LIKE BAPI_AUX-MAXREAD DEFAULT 0 EXPORTING VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2 TABLES FLIGHTLIST STRUCTURE BAPISFLIST © SAP AG 2009. All rights reserved.

 ABAP Functions can be joined with tables from the ABAP Dictionary © SAP AG 2009.Crystal Reports & SAP ERP Data Connectivity – ABAP Functions    The ABAP functions needs to have defined return types for each of the outputs The ABAP function cannot use complete tables as input parameters You cannot call entire programs. / Page 12 .CARRID). All rights reserved. You can only leverage individual functions  All input parameters will result in fields with a prefix “I_” in the technical name  These fields can be used in the record selection  The output fields are available in Crystal Reports and the technical name depends on the type of output.  In our case the output is a table with the name FLIGHTLIST and therefore the fields are name with the prefix combining “T_” (for table) and the name of table (for example: T_FLIGHTLIST.

fitness for a particular purpose. All rights reserved.Crystal Reports and SAP ERP Data Connectivity – ABAP List Viewer  Crystal Reports Viewer and Crystal Reports Designer are able to leverage ABAP List Viewer (ALV) as a data source for reporting  This integration becomes available with SAP Business Suite Innovation 2010 (ERP 6. or non-infringement. T his document is provided without a warranty of any kind either express or implied.02) You will be able to use Crystal Reports objects as layout option for Web Dynpro ALV and SAP GUI ALV layouts  You will be able to create Crystal Reports objects as templates for all users   Crystal Reports objects become part of the software logistics of the ALV This presentation and SAP‟s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. / Page 13 .0 EHP 05 / NW 7. © SAP AG 2009. including but not limited to the implied warranties of merchantability.

All rights reserved. / Page 14 . table and row-level security  Batch  Processing BusinessObjects Enterprise processing tier can be configured to leverage SAP‟s batch processing © SAP AG 2009.Crystal Reports & SAP ERP Additional considerations  Security  Definition Editor Allows for definition of user.

1 or SAP BusinessObjects Edge XI 3.Crystal Reports & SAP NetWeaver BW Data Connectivity Overview  Required Software Components   Crystal Reports 2008 Designer SAP BusinessObjects Enterprise XI 3. All rights reserved. / Page 15 .1  SAP BusinessObjects Integration for SAP Solutions XI 3.1  SAP NetWeaver BW available data sources    SAP NetWeaver BW Queries SAP NetWeaver BW InfoProvider SAP NetWeaver ODS / DSO Objects © SAP AG 2009.

Fields representing a parent-child relationship. Filter Navigational attribute Display attribute SAP variables Structure Conditions Exceptions Keydates Display Settings © SAP AG 2009.Crystal Reports & SAP NetWeaver BW Meta-Data Mapping SAP NetWeaver BW Query element Characteristic Hierarchy Keyfigure Calculated Keyfigure Restricted Keyfigure Crystal Reports Designer Element Separate fields for key and description per characteristic. Each Keyfigure can have up to three elements: numeric value. Parameters. The display attributes are grouped together with the actual characteristic. Measure element in the folder Keyfigure. Measure element in a grouping called Keyfigure. (Information about the details of the calculated keyfigure is not available in Crystal Reports.) Filters will be applied to the underlying query but are not visible in the Crystal Reports designer.) Measure element in the folder Keyfigure (Information about the details of the restricted keyfigure is not available in Crystal Reports. unit. All rights reserved. Each display attribute becomes one field in the field explorer. Separate fields for key and description per navigational attribute. / Page 16 A structure is being returned as a single field with several rows Not supported > means Crystal Reports is receiving all rows Not transferred to Crystal Reports A single keydate variable per Query is supported Not supported (example: number of decimals) . and formatted value.

/ Page 17 . All rights reserved.Crystal Reports & Xcelsius   Live Office allows you to leverage Crystal Reports as “source data” for Xcelsius Live Office allows you to leverage reports on-demand and instances (pre-scheduled reports) © SAP AG 2009.

Crystal Reports and SAP NetWeaver BW

SAP Toolbar
 

Menu File > New

When reporting from BEx queries Uses SAP BW Query or SAP BW MDX driver

When reporting from InfoSet, Table, Cluster, Function, ODS or InfoCube.

You can select the specific driver to use

If you don’t use the SAP Toolbar when reporting off BEx queries you miss list of values from variables

© SAP AG 2009. All rights reserved. / Page 18

Crystal Reports and SAP NetWeaver BW

Crystal Reports and Publishing to SAP NW BW

When you save your Crystal Reports you can choose to save it to BusinessObjects Enterprise or you can save it to SAP NetWeaver BW and publish to BusinessObjects Enterprise

It is not mandatory to save to SAP NetWeaver BW and publish to BusinessObjects Enterprise but some functionality is missed if you just save to BusinessObjects Enterprise:  Online list of values for prompts
  

Hierarchical display for hierarchical node prompts SAP variable personalization Life cycle management of Crystal Reports (from DEV to QA to PROD) with SAP transports

© SAP AG 2009. All rights reserved. / Page 19

Crystal Reports and SAP NetWeaver BW

Hierarchical Reporting
 

Leveraging parent-child relationship from SAP NW BW Hierarchical Group has to be created to navigate trough the hierarchy

© SAP AG 2009. All rights reserved. / Page 20

Crystal Reports and SAP NetWeaver BW  SAP Variables  List of Values for Variables are always static in Crystal Reports Designer (please don‟t change to dynamic). / Page 21 . they are dynamic/online in InfoView  Hierarchy node variables always flat in Crystal Reports. hierarchical display in InfoView © SAP AG 2009. All rights reserved.

Best Practices for SAP BusinessObjects Explorer 5. Best Practices for Xcelsius 4. Best Practices for Web Intelligence 3. Further Material © SAP AG 2009. Best Practices for BW Query Design 6. / Page 22 . Summary 7.Agenda 1. All rights reserved. Best Practices for Crystal Reports 2.

make decisions. including but not limited to. in MS Office. including Excel. / Page 23 . either express or implied. and share information with others across the organization Ad-Hoc Reporting & Analysis Combine SAP & Non-SAP Data Intuitive. Easy to Use  Self service reporting designed with the casual user in min  Users can analyze data and answer their questions in a single environment  Combine data from SAP NetWeaver BW and non-SAP data. in a single report  Easy to use BI tool empowering end-users to access and analyze the information they need  Free-form layout with light formatting and printing capabilities Accessible Anywhere  Web Intelligence reports can be viewed online. This document is provided without a warranty of any kind. or non-infringement. © SAP AG 2009. on mobile devices. offline. in dashboards. reporting & analysis Product : Web Intelligence Self-service ad hoc analysis and reporting enabling casual users to ask questions on any data. and on the desktop This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.BI Solution : Ad-Hoc query. the implied warranties of m erchantability. All rights reserved. fitness for a particular purpose.

/ Page 24 .Web Intelligence – Input Controls Filter possibilities exposed as simple widgets © SAP AG 2009. All rights reserved.

breaks facilitate identifying most salient details to unfold Enables consumers to progressively explore details most relevant to their analytical needs online & offline © SAP AG 2009.Web Intelligence – Fold / Unfold Folds automatically adhere to report structure (sections. breaks. tables Turn on feature as needed. no predefinition by author required Summary measures for sections. / Page 25 . All rights reserved.

All rights reserved. / Page 26 .Web Intelligence and SAP NetWeaver BW OLAP universe (MDX) Relational Universe (SQL) Data Federator SAP ERP SAP NetWeaver BW BEx Query BI Client BEx Query Classic InfoSets Transient Provider Multi Provider InfoSet InfoCube DSO © SAP AG 2009.

/ Page 27 . numeric value and formatted value (based on User preferences) Measure and dimension objects (same as Key Figure) Measure and dimension objects (same as Key Figure) Structure based on Characteristics (BEx Queries only) Navigational attribute Display Attribute Key Figure Calculated Key Figure (BEx Queries only) Restricted Key Figure (BEx Queries only) © SAP AG 2009. All rights reserved.Web Intelligence & SAP NetWeaver BW Meta-Data Mapping SAP BI element Dimension Universe object Class Subclass with dimension and detail objects BI Query: Subclass containing dimension and detail objects for each hierarchy level in the currently defined hierarchy Characteristic Characteristic with hierarchy BI InfoProvider: Subclasses containing dimension and detail objects for each hierarchy level for all hierarchies defined for the characteristic Class with single dimension object for the structure Subclass with dimension and detail objects (identical to characteristic) Detail object for the dimension Measure object in the class for the Key Figure structure with dimension objects for units/currency.

All rights reserved. two dimension objects supporting the list of values. Not supported > means Crystal Reports is receiving all rows Not transferred to Crystal Reports Display Settings Not supported (example: number of decimals) © SAP AG 2009. one for description. one for caption.Web Intelligence & SAP NetWeaver BW Meta-Data Mapping SAP BI element Universe object Pre-defined Filter in the Universe Variables (BEx Queries only) Key date variable (BEx Queries only) Filter Conditions Exceptions In the class for the dimension to which the variable applies. Universe parameters defining key date variable in the universe Filters will be applied to the underlying query but are not visible in the Crystal Reports designer. / Page 28 .

All rights reserved.  For large sets of key figures. / Page 29 . use option .“Use Selection of Structure Members” Restricted and Calculated Key Figures  Navigational Attributes and Key Dates  Restricted and Calculated Key figures should be built as part of the underlying BEx query to use the BW back-end processing for better performance  Queries with a larger set of such Key Figures should use the “Use Selection of Structure Members” option in the Query Monitor (transaction RSRT) to leverage the OLAP engine A large number of navigational attributes defined in the underlying InfoProvider negatively impacts overall performance  A single universe can only support a single Key Date variable © SAP AG 2009.Web Intelligence and SAP NetWeaver BW Hierarchies  Key Figures  Hierarchy support in Web Intelligence for SAP NetWeaver BW is limited  Use of hierarchy variable is recommended  The Use Query Drill option in Web Intelligence significantly improves drill down performance A large number of Key Figures in the BEx query will incur a significant performance penalty when running queries. regardless of whether the Key Figures are included in the Universe or used in the Webi query.

the entire Microcube is refreshed © SAP AG 2009.Web Intelligence and SAP NetWeaver BW  The Query Panel Definition is what defines the “Microcube” and thus the MDX Query which is executed on SAP BW  When refreshing the data in the Web Intelligence report. / Page 30 . All rights reserved.

those who continuously add/remove objects from report will require execution of query – can turn feature off and retrieve all objects in query Currently planned for SP3 of XI 3. removes objects – to match those required for the user‟s report content  All Web Intelligence interactive features are available inside report‟s structure Query stripping should not be used for all user workflows:   Users can add content (objects) that are additive to report content… however. / Page 31 .Web Intelligence and SAP NetWeaver BW  Query stripping will streamline report consumption and interactivity:  Each refresh automatically reduces queries – i.e. All rights reserved.1 © SAP AG 2009.

Web Intelligence and SAP NetWeaver BW  SAP Variables in Web Intelligence  Mandatory variables will always load a list of values (try to leverage more optional variables)  Leverage the Delegated Search feature for List of values  Web Intelligence filters  Prefer the inclusive filter over the exclusive member to increase the performance   Ensure the reference objects are indexed to avoid unnecessary steps to resolve the value to the member unique name Ensure the user can only select values from the actual LOV (List of values) © SAP AG 2009. / Page 32 . All rights reserved.

[TECH_NAME]. / Page 33 .[TECH_NAME] © SAP AG 2009. All rights reserved.Web Intelligence and SAP NetWeaver BW  Index Awareness   Navigate to the tab “Keys” in the Universe Designer Add a primary key Type Character Key Type Primary Key Syntax [<characteristic>].[LEVEL<xx>]. or [<characteristic>].

Web Intelligence and SAP NetWeaver BW  Delegated search for List of Values (LOV)   Navigate to the tab “Properties” in the Universe Designer of the LOV items Activate the “Delegate Search”  No values will be loaded automatically  User is “forced” to leverage search to receive members  Search is being delegated to the SAP BI system © SAP AG 2009. / Page 34 . All rights reserved.

SUM. All rights reserved. MIN. MAX Aggregations       Navigational Attributes Mass Data Enabled Ad-hoc Reporting      Federation (e. / Page 35 .Data Federator and SAP NetWeaver BW BW Server Feature BW Hierarchies Restricted and Calculated Key Figures BEx Queries BW Variables Currency and Unit Conversion MDX SQL  (calculated)        Exceptions. Conditions Security AVG.g. BW – RDBMS)   = fully supported  = limited support / workaround © SAP 2009 / Page 35 AG 2009. COUNT.

/ Page 36 . COUNT DISTINCT) available via Data Federator processing Define joins (in DF) from InfoProvider to master data InfoProvider tables Use filters on measures No workaround Non-Cumulative Key Figures No workaround © SAP 2009 / Page 36 AG 2009. All rights reserved. does not work for exit variables or variables filled through authorizations Simulate via joins in Data Federator SQL standard aggregations (AVG. Formulas Workaround Define calculated measures in Universes / WebI BW Variables Currency and Unit Conversion Exception Aggregations Display Attributes Conditions BW Hierarchies Define @prompt in Universes or WebI Query Panel.Data Federator and SAP NetWeaver BW BW Server Feature Calculated Key Figures.

MDX query and object definition) Want to combine SAP BW with other sources (SAP or non SAP)  Want to access DSO (fined grained reporting)  Can wait for Single-Sign On (SSO). … Defined a lot of BEX Queries  Requires advanced analytics   Requires Single-Sign On (SSO)  Relational universes for customers who:   Are not familiar with OLAP concepts (cube design. Planed for 2H 2010 © SAP AG 2009. / Page 37 . All rights reserved. calculated/restricted keyfigures.Web Intelligence and SAP NetWeaver BW  OLAP universes for customers who:  Invested in cube design and elements such as hierarchies. variables.

Agenda 1. Further Material © SAP AG 2009. Best Practices for Xcelsius 4. Best Practices for Web Intelligence 3. Best Practices for Crystal Reports 2. Summary 7. Best Practices for SAP BusinessObjects Explorer 5. Best Practices for BW Query Design 6. All rights reserved. / Page 38 .

/ Page 39 . All rights reserved.BI Solution : Dashboarding / Visualization Product : Xcelsius Enterprise Provides rapid development of highly interactive dashboards and data visualization through a flexible and easy to use interface Easy-to-Use  Highly customizable visualizations and dashboards through easy-to-use. drag and drop interface  Build Dashboards within weeks not months.  Leverage Flex to develop custom components and controls  Free-form layering of visual controls  Deploy to a variety of formats including Portals. Business User desktop applications and development IDE frameworks  Dashboards and Visualizations are compiled into flash format which is highly portable and widely supported Flexible Rapid Development  Deploy within minutes  Leverage investment in SAP BusinessObjects and SAP NetWeaver with specific data connectivity options  Open connectivity options through web service and XML connectors  Enable real-time dashboard updates through leveraging of Adobe Live cycle Data Services connectivity  Extensible connectors SAP & Non-SAP Data Sources © SAP AG 2009.

personalization) No limitations in queries features used BW authorization enforced Free characteristics list of values for filtering Dashboard authorization Xcelsius Enterprise  NetWeaver platform integration      Favorites and Roles Transport capability (integrated into DW workbench) Translation of texts Access through NW Portal using BEx iView BEx Queries & Views  Prerequisite   Xcelsius Designer 2008 SP2 BEx Frontend Patch 901   SAP NetWeaver BW 7. All rights reserved.Xcelsius 2008 and SAP NetWeaver BW  Direct connector to SAP NetWeaver BEx queries      Consume BEx Queries and Views Support of all variable type (incl.01 SP Stack 5 SAP NetWeaver BI ABAP & BI Java © SAP AG 2009. / Page 40 .

/ Page 41 . Cluster and Function ODS BW MDX Data Federator OLAP Universe SAP ERP SAP NetWeaver BW BEx Query BI Client BEx Query InfoProvider InfoSet Classic InfoSets SAP Queries ABAP Functions Table and Cluster Transient Provider Multi Provider InfoCube DSO © SAP AG 2009. All rights reserved.Xcelsius 2008 and SAP NetWeaver BW Xcelsius Live Office Crystal Reports Web Intelligence Query as a Web Service SAP InfoSet SAP Table.

medium text. and long text are being leveraged from the BW query.Xcelsius 2008 and SAP NetWeaver BW BW Query Element Characteristic Xcelsius Designer Element Each characteristic in the actual dataset is being retrieved based on the settings in the BW query. The user does not have access to the underlying definition in the Xcelsius designer. Variables from the BW query are transferred to Xcelsius as part of the connection and will be shown as variables in the Input Values area of the SAP NetWeaver BI connection settings. Display Attribute Display attributes can be used for a list of values and can become part of the overall dataset. Keyfigures Each keyfigure can be shown as plain numeric value or as formatted value based on the user preferences. Settings in regards to elements like key. The depth of the hierarchy depends on the configured number of levels in the BW query designer. Navigational Attributes Navigational Attributes are being treated identical to a characteristic. short text. All rights reserved. This choice can be made for each SAP NetWeaver BW connection configured in the Xcelsius Designer Data Manager. A single item with several rows Fully Supported Fully supported Variables Structure Conditions Display Settings © SAP AG 2009. Calculated / Restricted Keyfigure Each calculated / restricted keyfigure is treated like a keyfigure. In the actual dataset a display attribute can only be shown in combination with the actual characteristic. Filter Filters will be applied to the underlying query and the user has access to the configured filter values and can use those values for display purposes. In addition the user can set additional filter values for characteristics from the underlying BW query during the runtime of the Xcelsius object. In addition each characteristic is also available with a list of members which can be used for filtering or provide a list of values for variables. / Page 42 . Hierarchies Each level of the hierarchy will be presented as a column in the data set.

/ Page 43 .Xcelsius 2008 and SAP NetWeaver BW  Data Preview allows you to specify which data set the connection will return © SAP AG 2009. All rights reserved.

Xcelsius 2008 and SAP NetWeaver BW  Datasets includes information about lables. All rights reserved. currency. … © SAP AG 2009. / Page 44 .

All rights reserved.Xcelsius 2008 and SAP NetWeaver BW Design considerations  Xcelcius Direct Connectivity  Start from the business needs. What decision should this support? What KPIs should it display?   What visual components best represent the data? Consider if all data reside in SAP NetWeaver BW  Business needs highly visual and interactive dashboard interface  How will the user interact with the data?  Keep it simple! Other reporting tools are used . aggregate in BW © SAP AG 2009.000 rows maximum  Highly aggregated data  Execute cascaded prompts and queries  Reduce number of key figures in the universe  Avoid aggregating in flash. but integration with other SAP BusinessObjects products is not needed Performances and Interactivity  Use Live Office based on scheduled Crystal Reports where live data is not needed  Limit result sets to 2. / Page 45 .

continue to host Xcelsius within Business Objects Enterprise and connect Xcelsius to data via Live Office or Query as a Web Service  © SAP AG 2009. if business requires to access dashboard from BusinessObjects Infoview or Dashboard Builder  In that case.Xcelsius 2008 and SAP NetWeaver BW  When to use the new direct SAP NW BI Connectivity ?   When data resides in SAP NetWeaver Business Warehouse When the business requirements are about – Highly visual and interactive dashboard interface – Intuitive guided navigation for casual business users  When NOT to use the new direct SAP NW BI Connectivity ? Do not consider. All rights reserved. / Page 46 .

All rights reserved. Further Material © SAP AG 2009. / Page 47 . Best Practices for BW Query Design 6. Best Practices for Crystal Reports 2.Agenda 1. Summary 7. Best Practices for Xcelsius 4. Best Practices for SAP BusinessObjects Explorer 5. Best Practices for Web Intelligence 3.

    Designed for high data volumes (retail. All rights reserved. utilities.) Leveraging SAP NetWeaver BW Accelerator Scalable blade server platform Highly consistent and predictable response time Performance SAP & Non-SAP Environments  Combined with SAP BusinessObjects Open Accelerator allows exploration of SAP and non-SAP datasources  Enables cross data source search of all corporate data  Users are able to upload Excel spreadsheets to SAP BusinessObjects Explorer in the cloud or on premise to start the data exploration Time for Development  SAP BusinessObjects Explorer leverages existing infrastructure from SAP BusinessObjects Enterprise and SAP NetWeaver BWA  Bring BI to more business users with SAP BusinessObjects Explorer  Get new insight into your business  Instant answers to “on-the-fly” questions without annoying time delays  Intuitive interfaces with familiar „common language‟ workflows  Users can search and explore large volumes of enterprise data to discover relationships and uncover root cause New Business Scenarios © SAP AG 2009.BI Solution: Data Search and Exploration Product : SAP BusinessObjects Explorer SAP BusinessObjects Explorer brings together the high performance in-memory capabilities of SAP NetWeaver BW Accelerator with an intuitive front-end interface for search and exploration. banking etc. / Page 48 .

/ Page 49 .What Is Explorer? It’s Search Against BI… Use familiar key-word search to find business information  Answers “on-the-fly” and investigative questions Searches directly on pre-indexed data  No previous reports or metrics need exist  Provides fast search and exploration Searches across all data sources  Any universe accessible source  Any Accelerator accessible source © SAP AG 2009. All rights reserved.

All rights reserved.…and Then It’s Exploration Of the Results Intuitively explore on data  No data model or data knowledge required Web or Mobile Automated relevancy of results  Most relevant information is displayed first Best chart type auto generated Share insights with others  Export to CSV or image Save it locally as a browser bookmark  One-click send to email  © SAP AG 2009. / Page 50 .

All rights reserved.BI Solution: Data Search and Exploration Product : SAP BusinessObjects Explorer Search Explore Visualize Share © SAP AG 2009. / Page 51 .

All rights reserved.SAP BusinessObjects Explorer and SAP NetWeaver BW SAP BusinessObjects Explorer OLAP Universe Relational Universe (SQL) Data Federator SAP ERP BI Client SAP NetWeaver BW BEx Query InfoProvider BEx Query SAP NetWeaver BWA Classic InfoSets Transient Provider Multi Provider InfoCube DSO InfoSet BW Accelerator © SAP AG 2009. / Page 52 .

All rights reserved. security  An SAP BusinessObjects Explorer-enabled index can also be used to accelerate BW queries  Converting a standard index to an SAP BusinessObjects Explorer-enabled index requires re-indexing (due to new layout and additional fields) © SAP AG 2009. conversion factors.SAP BusinessObjects Explorer and SAP NetWeaver BW  SAP NetWeaver BW Accelerator Index for SAP BusinessObjects Explorer   Contains “standard” SAP NetWeaver BW Accelerator index Provides additional information: texts. / Page 53 .

SAP BusinessObjects Explorer and SAP NetWeaver BW  Multi-provider indexing and exploration:   Natively index common MultiProviders Index once for SAP BusinessObjects Explorer and SAP NetWeaver BW use cases – Delta-loading capability  Snapshot indexing of complex MultiProviders   Such as those that refer to DataStore Objects and InfoObjects Support for MultiProviders with compounded characteristics across InfoCubes  Query indexing and exploration  SAP BusinessObjects Explorer can now be used to explore existing (or new) queries  Quickly index your existing queries for SAP BusinessObjects Explorer and have your users exploring them almost immediately   Snapshot indexing of queries Ability to leverage query features such as complex unit conversions © SAP AG 2009. All rights reserved. / Page 54 .

/ Page 55 .. g > kg)  Support of one key date for currency conversion  © SAP AG 2009. we assume the current time of initial(!) indexing time is chosen for all time-dependent texts   Re-indexing is required after new text loads into SAP NetWeaver BW  Unit/Currency Conversion  Conversion factor is defined before indexing Support for simple unit conversions (e.g. All rights reserved. short text.g. according to InfoObject/RSD1 setting)  For time-dependent texts.SAP BusinessObjects Explorer and SAP NetWeaver BW  Texts  Text support in one language (one language for all SAP BusinessObjects Explorer-enabled BWA indexes) One text type per InfoObject (e.

user-specific date formats) are not supported © SAP AG 2009. date format) Complex conversions (e. standard conversions (e.SAP BusinessObjects Explorer and SAP NetWeaver BW  Security  Support of one single SAP NetWeaver BI analysis authorization per user (user does not need to be an SAP NetWeaver BW user) Indexing of authorizations must be scheduled  SAP BusinessObjects Explorer authorizations automatically filter to the authorized values   Characteristics/Dimensions   Time-dependent master data is always displayed for the current date (query keydate = current day) Display attributes are not supported  Support for simple conversion/format routines for external keys at design time – – E. / Page 56 . All rights reserved.g.g.g.

transformation logic. transformation. and loading (ETL)  SAP BusinessObjects Rapid Marts  Add-on content to SAP BusinessObjects Data Services Ready to use packaged data integration for SAP ERP with support of SAP. PeopleSoft. and Siebel will accelerate your data warehouse / datamart projects  Combine application knowledge with data integration best practices to deliver prebuilt data models. from databases to Web forums  Integrate and deliver data in real-time or batch using flexible approaches through extraction. and data extraction  © SAP AG 2009. All rights reserved.SAP BusinessObjects Explorer and SAP NetWeaver BW Accelerate ANY data now:   SAP BusinessObjects Data Services XI Access all types of structured and unstructured data from virtually any source. / Page 57 . Oracle.

SAP BusinessObjects Explorer and SAP NetWeaver BW Use SAP BusinessObjects Data Services to bring data from a wide variety of sources into SAP NetWeaver BW Accelerator Data Services Databases Data Services Applications Legacy   Use the index designer to model accelerated indexes Index designer ships with SAP BusinessObjects Data Services and can be launched from within SAP BusinessObjects Data Services Designer Index designer generates the XML spec needed to create the accelerated indexes. cleanse and load it into SAP NetWeaver BW Accelerator SAP BusinessObjects Data Services uses SAP NetWeaver BW Accelerator‟s bulk-load library (TREX thinclient) to load the data Index designer can also be used to create the initial SAP BusinessObjects Data Services data flows needed to populate the accelerated indexes © SAP AG 2009. transform. / Page 58 . SAP BusinessObjects Data Services executes this and the indexes are created during run-time  index designer    Use SAP BusinessObjects Data Services to extract data from multiple sources. All rights reserved.

All rights reserved.SAP BusinessObjects Explorer and SAP NetWeaver BW SAP BusinessObjects Explorer SAP NetWeaver BW SAP NetWeaver 7.2 SP1 SAP BusinessObjects index designer plug-in Any corporate data © SAP AG 2009.2 SBOP Enterprise XI 3.20 SAP NetWeaver BW Accelerator 7.01 SP05 SBOP Explorer (blade) 2.1 SP2 SBOP Integration XI 3.1 SP2 SAP NetWeaver BW Accelerator 7. / Page 59 .20 SAP BusinessObjects Data Services SAP BusinessObjects Data Services XI 3.1 SP2 for SAP SBOP Client Tools XI 3.0 SBOP Explorer XI 3.

Best Practices for BW Query Design 6. Best Practices for Crystal Reports 2. / Page 60 . Best Practices for Xcelsius 4. Further Material © SAP AG 2009. Summary 7. Best Practices for SAP BusinessObjects Explorer 5. Best Practices for Web Intelligence 3.Agenda 1. All rights reserved.

Characteristic Measure vs. All rights reserved. / Page 61 .Business Intelligence Green Fields Common Risks No common terminology. lack of product knowledge • • Clarification of key business intelligence concepts are likely to be necessary Tendency to put the data source central. “dashboards” Dimension vs. Key Figure Hard to get beyond operational/regulatory reporting Lots of customer education required. will only know SAP terms    No prior experience with BI tools • • What is the meaning of “report”. “BI”. and potentially aggregation added Web Intelligence is not an OLAP interface • Confusion of intended audience © SAP AG 2009. rather than the end user report Expectation that Web Intelligence should replace BEx Analyzer • • Assumption we just connect up to existing BEx Queries • • • Lack of product knowledge Misunderstanding of product portfolio and roadmap • SAP doesn‟t dictate moving all your analysts off BEx Analyzer at all • Product may not support all elements of the existing BEx queries well Violates the BI principle of working backwards from report requirements BEx queries need to be purpose-built. tuned.

Only difference with relational RDBMS is BEx/InfoCube instead of database structure Reports Dashboards • Universes • BEx Queries • InfoCube • BEx Queries Universes • • • • Reports Dashboards • requirements gathering • end User interviews • vision. change the cube to support the required query. universe and reports Consider whether going directly against an InfoCube or MultiProvider is desirable • Develop the BEx query Test the BEx query Generate the OLAP universe Hide inappropriate objects Test universe Develop required reports • Develop required dashboards • Test reports • Test dashboards © SAP AG 2009. bearing in mind BOE supported product features • Consider adding aggregation • Tune the query • If data for a query is not yet in the cube. / Page 62 . strategy and purpose • visual layout • mockups • navigation • folder structure • Access rights identify subject areas • define required data elements • evaluate adhoc requirements • Prioritize easeof-use/ maintenance or performance Identify data elements needed for universe in BEx • Purpose-build the BEx query. but the practice is equivalent for other tools.The “Business Intelligence” Approach The concrete example is for OLAP Universes. All rights reserved.

such as Calculated Key figures. All rights reserved.  You do NOT need a BI Query for every report and you do NOT need a universe for every BI Query  Focus the implementation strategy on limiting the number of BI Queries and universes that share common elements Build a small set of BEx queries focusing on sharing common elements in a small number of Universes  The Web Intelligence Query Panel definition is the primary influence factor on how much data is being retrieve from SAP NetWeaver BW   In some situations extremely large queries and universes can adversely affect performance © SAP AG 2009. / Page 63 .SAP NetWeaver BW Query Design  Overall recommendation   BI Queries are recommended as data sources for generating universes BI Queries offer a flexible extension to the data modeling environment and require less effort to change than InfoCubes  BI Queries offer significant functionality to create customized data sources that meet enduser requirements. Restricted Key figures and SAP Variables.

/ Page 64 . All rights reserved.SAP NetWeaver BW Query Design  Consider splitting up the large Queries & Universes into smaller ones  Depending on # of objects (Dimensions & Measures) utilized per report. it might make sense to find common groupings of objects to service particular Web Intelligence Reports Grouped by Commonality Group A Group B = WebI Report Measures Group C Group D Dimensions © SAP AG 2009.

no direct impact on generation of OLAP Universe or other reports “Allow External Access” option should be set in the properties of the BEx query  Items not supported via InfoCube data access:     Variables Restricted or Calculated Key Figures Filters Custom Structures  Restricted Key and Calculated Key Figures For large sets of key figures. All rights reserved. minimizing development downstream Use BW authorizations for data level security  Data Level Security & BW  © SAP AG 2009.SAP NetWeaver BW Query Design   Placement of Characteristics / Key Figures .“Use Selection of Structure Members”  Leverage the capabilities of the Restricted Key and Calculated Key Figures where possible    As part of the underlying BI query. use option . / Page 65 . they will be processed by the BW back end Can be shared across queries.

minimizing development downstream List of Values are being generated automatically  Time based structures / calculations  Leverage EXIT Variables as part of the BW query © SAP AG 2009.SAP NetWeaver BW Query Design  Leverage Restricted and Calculated Key Figures as part of the BW Query   Can be shared across queries. / Page 66 . minimizing development downstream As part of the underlying BI query. they will be processed by the BW back end  Leverage SAP Variables as part of the BW Query   Can be shared across queries. All rights reserved.

/ Page 67 SAP OLAP BAPI support level InfoCube/BI Query InfoCube/BI Query InfoCube/BI Query BI Query only InfoCube/BI Query BI Query only BI Query only BI Query only BI Query only .SAP NetWeaver BW Query Design BI metadata feature Characteristics (incl. All rights reserved. Time and Unit) Hierarchies Basic Key Figures Navigational Attributes Display Attributes Calculated Key Figures / Formulas Restricted Key Figures Custom Structures Variables © SAP AG 2009.

SAP NetWeaver BW Query Design This simple property change helps improve performance in situations where there are a lot of Restricted Key Figures and other calculations in the Query Definition (>>Transaction RSRT)  This ensures that structure elements are sent to the database for processing © SAP AG 2009. All rights reserved. / Page 68 .

Best Practices for BW Query Design 6.Agenda 1. Best Practices for Crystal Reports 2. / Page 69 . Best Practices for SAP BusinessObjects Explorer 5. All rights reserved. Best Practices for Web Intelligence 3. Summary 7. Best Practices for Xcelsius 4. Further Material © SAP AG 2009.

sap.com/irj/boc/bi-solution-architecture © SAP AG 2009.sdn.Further Material  SAP BusinessObjects Community SAP BusinessObjects BI Solution Architecture http://www. All rights reserved. / Page 70 .