Documente Academic
Documente Profesional
Documente Cultură
Applies to:
Supporting the Business Objects Explorer + BW Accelerator
Summary
This article helps in understanding the Support components of the SAP BW Accelerator as the underlying
layer and then the BO Explorer
Author Bio
Hari Guleria is a ’BI Business Value Strategist & Architect’ at erada Inc, and BI DataBridge llc, launching SAP BI software
products like SmartCube (automated InfoCube modeling), BWA Workbench (tool for BWA administration) and RapidPro (ABAP
optimization tool). The team is currently working on ‘Datentech’ a 100% BI Data Profiling, Scoring and Management tool. Hari
has completed 3 FLC BWA projects and participated in two BWA implementations.
Hari routinely works with customers as their business value Architect, i.e. building sustainable BI methodology by working with
business owners and vendor partners, assuring SAP and SAP BI Business Value enablement. Hari is highly business need
focused. His strength is in BI Strategy, Architecture and Business Value assurance, and assisting BI customers realize their
business goals. He is the author of the book ‘BI Valuenomics 1’ due for release in April 2010 and 2 in June 2010.
Prior to this Hari worked at SAP America with their Value Realization group focusing on SAP BI strategy and value audits. Before
that Hari held national BI & EP practice director roles with major SAP premier partner companies. Hari started SAP with Andersen consulting (now
Accenture) in Saudi Arabia in 1995.
Prior to SAP Hari comes with over 9 years of Sr. sales, marketing and strategic planning experience with European multinationals. He has been
assisting customers meet their SAP R/3 business goals since 1995 and BI goals since 1997. He has been a regular speaker at ASUG, and BITI national
SAP conferences. Hari has over 14 full life‐cycle SAP projects under his belt.
Hari may be contacted at hguleria@erada.com
Table of Contents
BW ACCELERATOR ......................................................................................................................................... 3
BO EXPLORER ................................................................................................................................ 3
BO Explorer background ................................................................................................................................. 3
BOEx Technical Profile ................................................................................................................................... 3
BOEx Service components ............................................................................................................................. 3
Support options ............................................................................................................................................... 3
BOEx Implementation Checklist ......................................................................................................................... 4
Check 0: What all will I not have to do with a BOEx ....................................................................................... 4
Check 1: Why do customers buy BO Explorer ............................................................................................... 4
Step 2: Align User Expectations ..................................................................................................................... 4
Check 3: Aligning user expectations ............................................................................................................... 4
Aligning user expectations is the most critical aspect of the BO Explorer deployment. ..................................... 4
Check 4: Enhance your BW before planning for BOEX.................................................................................. 4
Check 5: What can I do with BOEx ................................................................................................................. 5
Check 6: What is the best and worst thing about BO Explorer ....................................................................... 5
Check 7: How can I use BO Explorer best of all ............................................................................................. 5
As an executive tool for ................................................................................................................................... 5
Sept 8: Preparing BW DSO’s and InfoCubes for BO Explorer ....................................................................... 6
Step 9: Review your standards ....................................................................................................................... 6
Step 10: Check BW for Redundancy .............................................................................................................. 6
Step 11: If BOEx is so great how can it go wrong? ........................................................................................ 6
SELECTION 1 .................................................................................................................................................... 6
• By not setting the user expectations correctly............................................................................................. 6
Check 12: Why do I need to remodel my InfoCube for BOEx? ...................................................................... 7
Step 12: Understand the BOEX Implementation ............................................................................................ 7
Check 13: Who should support a BOEx Implementation................................................................................ 7
Check 14: What support does BW team need to do of BOEx is through BWA .............................................. 8
BASIC Rule Plan your work and only then work your plan ......................................................................... 8
BOEx Miscellaneous ....................................................................................................................................... 9
Other questions .................................................................................................................................................. 9
High level – BO Explorer Architecture & Data Flow ......................................................................................... 10
Copyright........................................................................................................................................................... 11
BW ACCELERATOR
See document: https://cw.sdn.sap.com/cw/docs/DOC-119971
BO EXPLORER
BO Explorer background
It used to be called Polestar and is now BO Explorer.
BO Explorer (BOEx) is an appliance provided jointly by SAP/BOBJ that can be a stand alone or an add-on to
the BW Accelerator.
The role of the BO Explorer is to provide ‘blistering speed’ analytics by leveraging [1] Columnar based
structures for [2] text based analytics (contextual informatics)
Currently the BO Explorer can source data from BW, Business Objects and other source systems.
Support options
Layer 1 support must come only from SAP (BOEx Software in each blade)
Layer 2 support comes from your BO Explorer HW vendor (everything other than the BOEx SW)
Layer 3.1 support needed to be defined in a RACI with the Data Center support administration
Layer 3.2 support comes from the BI Basis and BO Explorer BI Support team
Aligning user expectations is the most critical aspect of the BO Explorer deployment.
The value offer of BOEx is ‘Enable exceptional performance for Executive Informatics Mining’
The reason for this is that
• BOEx is not designed to provide complex cross function reporting for operational management.
BOEx is designed for executive level informatics browsing to view trends and process distribution so
as to enable them to ask further questions.
• BOEX does not need data base access or OLAP time. It creates queries in the fly with daa and
graphs
• If ‘Executive Self Service Informatics is your goal’ BOEx is your appliance
• If replacing your DW, BI or BW is your goal BOEx is not your solution.
• However if you have a 200 million records and you need to summarize that into a one single
question BOEx can show the answer without any query in the background.
• Executive friendly analytical mining tool, i.e. running self-service queries that are totally never
developed or existing in any system
• Asking questions that have never been asked before
• Analytics at the speed of thought
• Going where no query has ever gone before
SELECTION 1
• Getting too many answers and not knowing which one to choose
• Not getting the details one thought users could get
• Not being able to ask complex questions
• Assuming BOEx will answer all the BW Queries
• Assuming executives can sit in a room and ask any question and get the answer in under 1 second
The most important component of a BOEx project is to set user expectations straight from the start.
Check 14: What support does BW team need to do of BOEx is through BWA
BW Checks
1. Cubes are cleaned for BOEx
2. Cubes are remodeled for BWA and BOEx
3. Redundant data is identified and cleansed or planned for cleansing
BW Accelerator Checks
The BW team support will consist of (but not limited to)
1. Indexing and re-indexing of Cubes
2. Daily Process chain Check up
3. Daily Roll up comparison of indexed cubes
4. Daily Data Reconciliation between BW and BOEX data
5. ** Ability to forecast BOEX data growth (Tool based)
6. ** Ability to compare BOEX and BW Indexed cubes (Tool based)
7. ** Ability to physically view Indexed data in BOEX (Tool based)
BW Basis Team
1. Monitor Space usage and Alerts
BO Explorer Checks
The BW team needs to support
BASIC Rule Plan your work and only then work your plan
This will eliminate surprises 2 to 4 weeks after go-live
BOEx Miscellaneous
Other questions
1. What do we need to train BW and Basis on?
2. How do I know if the BOEx data is right or worng?
3. What is the best method to manage BOEx loading process?
4. How does one determine if an InfoCube needs to be re-indexed for BOEx or not?
5. What the new BOEx features that we can plan for from now?
6. What are the new BOEx features we should know?
7. How does one model for BOEx?
8. Where can I get the 2009 Hasso Plattner presentation & speech on BO Explorer? (author)
9. Should I put the entire BW into BOEx, or select InfoCubes?
10. Can I put all of my R/3 into the BOEx?
11. Can I put my Business Objects universe into BOEx? (yes)
12. How do I optimize what cubes go into BOEx?
13. What is the BOEx Go-live Strategy?
14. Can BOEx data get out of sync with BW data (Data Reconciliation)?
15. What do we need to know about BOEx Monitoring?
16. How does BOEx answer question of Calculated Key Figures and Aggregates?
17. How does BOEx react to Custom BW developments?
Copyright
© 2009 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,
zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,
Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All
other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
These materials are provided “as is” 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.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors
or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.