You are on page 1of 20

_________________________________

_________________________________
_________________________________
_________________________________
Unlock the Secrets of _________________________________
Query Management
_________________________________
Using SAP NetWeaver BI
_________________________________
_________________________________
Gary Nolan _________________________________
TekLink International
_________________________________
© 2007 Wellesley Information Services. All rights reserved.

In This Session
_________________________________
• Learn your options for creating and managing queries in _________________________________
SAP NetWeaver® BI _________________________________
• Gain insights into important query development and
_________________________________
performance standards
• Get recommendations for establishing and enforcing _________________________________
query design standards _________________________________
• Learn the best ways to manage and roll out queries _________________________________
• Get guidelines to match complex query requirements _________________________________
with the right solutions in SAP NetWeaver BI
_________________________________
_________________________________

What We’ll Cover …


_________________________________
• Development strategy _________________________________
• Publishing strategy _________________________________
• Performance management strategy
_________________________________
• Security strategy
_________________________________
• Wrap-up
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

2
Develop a Data Management Strategy
_________________________________
• Most of query management is about gathering the _________________________________
proper requirements
_________________________________
• Develop a sound methodology to gather and track the
_________________________________
requirements from both:
Œ Top down — from the query, to the data sources _________________________________
Œ Bottom up — from the data sources, to the query _________________________________
• Developing a good methodology to gather the query _________________________________
requirements allows for a sound data model
_________________________________
_________________________________
_________________________________

What Should Be in Your Functional Model Document?


_________________________________
• Business questions asked and answered by the data _________________________________
model _________________________________
• History requirements of information
_________________________________
• Data sources required to complete model
_________________________________
ΠVolume/system/frequency
• Dependencies/constraints/assumptions _________________________________
• Transformation of data required _________________________________
• Frequency and timing _________________________________
• Functional model diagram to show flow and data model _________________________________
_________________________________

What Should Be in Your Functional Model Document? (cont.)


_________________________________
• Presentation requirements _________________________________
• Audience and distribution of presentation _________________________________
• Security
_________________________________
• Sign-off
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

5
Enforce Strong Query Governance to Ensure Consistency
_________________________________
• Providing a coherent strategy for query development _________________________________
means keeping queries consistent on the following
_________________________________
elements:
ΠNaming _________________________________
ΠLook and feel _________________________________
ΠSecurity _________________________________
ΠTools
ΠEase of use
_________________________________
ΠPerformance _________________________________
ΠTemplates _________________________________
• Keep the queries consistent _________________________________
ΠDevelop a standards document to spell out the query strategy
and development, security, and naming standards 6

How Can You Ensure Standards Are Followed?


_________________________________
• Establish a design steward for each functional area _________________________________
ΠThe steward
_________________________________
f Is a member of the SAP NetWeaver BI development team
f Is not a consultant _________________________________
f Is responsible for current and future design in one
_________________________________
functional area
f Can spot conflicts and scope creep into his/her area _________________________________
ΠEstablishes some ownership in the development team _________________________________
ΠAllows team members to focus on one functional area
f SAP is much too big to understand many areas
_________________________________
ΠThe design steward works with the business, project _________________________________
manager, and overall SAP NetWeaver BI data architect
_________________________________
• Have some redundancy in case team members leave or
are reassigned
7

Tool Strategy
_________________________________
• Determine the right tool for the job _________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

8
SAP NetWeaver BI Front-End Tool Tips
_________________________________
• BEx Analyzer _________________________________
ΠExcel-based and typically requires a desktop GUI to be set up
for all users _________________________________
ΠCan be cumbersome when rolling out front-end patches _________________________________
ΠNice for users that are used to BEx Analyzer from 3.x or those
that prefer the data in Excel _________________________________
• BEx Web Analyzer _________________________________
ΠRuns on Java and does not require GUI on the user machine
_________________________________
ΠMuch faster to roll out new users
ΠMemory intensive _________________________________
f Because it uses Java, it is typically much more memory
_________________________________
intensive than BEx Analyzer
ΠNice for users who want integration of Java with limited _________________________________
footprint
9

More SAP NetWeaver BI Front-End Tool Tips


_________________________________
• BEx Report Designer _________________________________
ΠFormatted report development tool _________________________________
ΠCan be used for a subset of reporting requirements
ΠAccommodates users that require a preformatted report
_________________________________
ΠRobust in SAP NetWeaver BI 7.0, but is not a complete _________________________________
replacement for Crystal Reports
_________________________________
f Crystal has much more functionality — but for many
implementations, Report Designer is enough _________________________________
ΠOverall nice toolset but should be limited to those reports that _________________________________
are flat and without drilldowns
_________________________________
_________________________________

10

More SAP NetWeaver BI Front-End Tool Tips (cont.)


_________________________________
• Web Applications Designer _________________________________
ΠWeb development tool
_________________________________
ΠCan be used to create Web applications to be used with SAP
NetWeaver BI _________________________________
ΠMost commonly used to develop Web templates to be used _________________________________
with existing SAP NetWeaver BI reports
ΠRobust tool set, but not very intuitive for a new developer _________________________________
• SAP NetWeaver Visual Composer _________________________________
ΠRobust tool to allow integrated reporting from multiple areas _________________________________
ΠVery promising tool
_________________________________
_________________________________

11
More SAP NetWeaver BI Front-End Tool Tips (cont.)
_________________________________
• Third-party front-end tools such as Crystal, Cognos, etc. _________________________________
Œ A “Why not SAP?” approach should be followed
_________________________________
f Any benefit should be heavily weighted against the cost of
integration of the third-party tool _________________________________
f No third-party tool is integrated as tightly as they tell you _________________________________
fMany times it’s difficult to determine where an issue
_________________________________
resides – with SAP or with the third-party vendor
_________________________________
_________________________________
_________________________________
Note
_________________________________

12

What Is a Key Figure Matrix?


_________________________________
• A universal document used to track and document the _________________________________
most common key figures and KPIs _________________________________
ΠEstablishes one place for all key figures and KPIs
ΠEnforces one vision and view of these values
_________________________________
ΠAllows agreement on one formula and method for calculating _________________________________
a KPI
_________________________________
ΠEstablishes one central repository for naming and change
management _________________________________
ΠSets common abbreviations, categories, granularity, etc. _________________________________
_________________________________
_________________________________

13

What Is a Key Figure Matrix? (cont.)


_________________________________
• A universal document used to track and document the _________________________________
most common key figures and KPIs (cont.)
_________________________________
ΠAssigns one owner to a KPI
f It is quite common for one KPI to be measured quite _________________________________
differently by different audiences _________________________________
ƒ One customer I worked with had three different
definitions of a commonly used measure — who _________________________________
decides which measure is “right”? _________________________________
f This document keeps the Business Intelligence (BI) team
out of these decisions _________________________________
_________________________________
_________________________________

14
How Do I Complete the KPI Matrix?
_________________________________
• Most projects use a spreadsheet as their KPI matrix _________________________________
• The document must be a “living” document and owned _________________________________
by the business and process teams
_________________________________
ΠThis should not be seen as a BI team deliverable
• Before any work can be done in SAP NetWeaver BI, _________________________________
insist that all key figures that are calculated be _________________________________
documented in the KPI matrix _________________________________
ΠThere should be no query formulas or InfoProvider
transformation calculations without the measure first _________________________________
documented in the KPI matrix _________________________________
_________________________________

15

How Do I Complete the KPI Matrix? (cont.)


_________________________________
• Some projects take short cuts and allow measures to be _________________________________
slipped in without documenting these on the KPI matrix _________________________________
ΠEventually this will come back to haunt them
ΠIf the KPI conflicts with other KPIs or the calculation is not
_________________________________
clear, the BI team often has to go back and redo their work _________________________________
• This document helps get the calculations right the _________________________________
first time
_________________________________
• Insist on sign-off of the KPI matrix once complete
_________________________________
_________________________________
_________________________________

16

Query Development Strategy Tips


_________________________________
• It is typically better to have fewer queries with many _________________________________
different free characteristics and key figure values in
_________________________________
one query than many queries with very narrow scope
ΠThis strategy allows existing queries to answer many more _________________________________
business questions by simply using new filter criteria or _________________________________
drilling down differently in the report
ΠAlso allows for easier testing, documentation, and rollout _________________________________
• You can add many key figure values to one query by _________________________________
putting it in the query and hiding it with the ability to _________________________________
view when necessary
_________________________________
_________________________________

17
Hide (Can Be Shown)
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
• Allows you to
have key figures _________________________________
that are in the _________________________________
query but not
_________________________________
initially shown
_________________________________

18

Utilize Key Figure Grouping in the InfoProvider


_________________________________
• Key figure grouping can now be used … _________________________________
ΠFolders
_________________________________
also appear
in BEx Query _________________________________
Designer
_________________________________
ΠThese are like
dimensions _________________________________
for key
_________________________________
figures
_________________________________
_________________________________
_________________________________

19

Query Development Strategy Tips


_________________________________
• Do not develop queries to match to existing legacy _________________________________
reports
_________________________________
ΠThey reflect existing measurement criteria
ΠAs SAP ECC becomes more mature and users become more _________________________________
aware, there will be new measurements _________________________________
ΠFocus instead on the KPI or key figures that need to be
measured and build to them _________________________________
• Be careful of query requirements with many different _________________________________
levels of granularity _________________________________
ΠSome metrics only make sense at one level and cannot be
aggregated
_________________________________
ΠMake sure you understand the metric _________________________________

20
Query Development Strategy Tips (cont.)
_________________________________
• Always develop queries using a MultiProvider, even if _________________________________
there is only data being read from one InfoProvider
_________________________________
ΠAllows for growth, if needed, without moving or changing the
query drastically _________________________________
ΠAllows for logical partitioning to be added later to the data _________________________________
model without disrupting the query
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

21

Develop Queries in Production?


_________________________________
• Many customers develop queries directly in production _________________________________
ΠThis is a big debate among customers
_________________________________
• Pros
ΠQuick deployment _________________________________
ΠReal production data can be used to test queries
_________________________________
• Cons
ΠHard to enforce governance _________________________________
ΠPerformance issues may arise
ΠLack of understanding of the data leads to incorrect
_________________________________
assumptions _________________________________
• The best way to achieve optimal performance and
standardize queries is to not allow query development in _________________________________
production _________________________________
ΠDevelop all queries in the development environment and
transport through the landscape (DEV ΠQA ΠPROD)
22

If You’re Developing Queries in Production


_________________________________
• Keep query development in the hands of a few well- _________________________________
trained power users
_________________________________
• Have a certification/training process for the power users
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

23
If You’re Developing Queries in Production (cont.)
_________________________________
• Make sure power users are _________________________________
ΠStrategic
_________________________________
f They will steer the strategic vision of BI to the user
community; they need to understand the overall reporting _________________________________
strategy _________________________________
ΠDetail-oriented
_________________________________
ΠNot renegades
f They need to adhere to standards and documentation _________________________________
rigorously
_________________________________
ΠBusiness-oriented, yet technical
f This allows them to understand both sides: the
_________________________________
development and the user community _________________________________

24

Production Query Development Tips


_________________________________
• Have strict naming and development criteria _________________________________
Œ This is where many SAP NetWeaver BI projects fail — the _________________________________
query development becomes the “Wild West”
ΠThere is no common naming (i.e., Net Sales in two queries _________________________________
mean two different things) _________________________________
ΠProliferation of queries makes the solution difficult to manage
_________________________________
ΠFilter criteria is not administered consistently
ΠBe mindful of data integrity _________________________________
ΠTry to keep queries with the same look and feel _________________________________
• Keep power users informed of the changing data model _________________________________
ΠFilters or selection criteria may not be clear
_________________________________

25

Production Query Development Tips (cont.)


_________________________________
• Make sure the query developers understand _________________________________
performance strategy and adhere to this strategy
_________________________________
• Consider the security implications of development
ΠSometimes segmenting the data can make security
_________________________________
implementation easier _________________________________
• Develop a publishing strategy to segregate different _________________________________
types of queries
_________________________________
_________________________________
_________________________________
_________________________________

26
What We’ll Cover …
_________________________________
• Development strategy _________________________________
• Publishing strategy _________________________________
• Performance management strategy _________________________________
• Security strategy
_________________________________
• Wrap-up
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

27

Query Publishing Strategy


_________________________________
• Publishing refers to rolling out new queries to end users _________________________________
• Group new queries into three categories: _________________________________
ΠSanctioned Queries
_________________________________
f These have been built by the development team, validated,
and published to the user base _________________________________
ΠPower User Queries _________________________________
f These have been created by a select group of the user
community _________________________________
ΠFavorites _________________________________
f Queries that have been created as a result of other queries
_________________________________
and saved to be reused
_________________________________

28

Sanctioned Queries
_________________________________
• Published by the BI team _________________________________
• Follows strict standards _________________________________
• Transported from one environment to another
_________________________________
ΠUse a naming standard Z_* prefix and set security so no user
can add new Z_* or change these queries at all _________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

29
Power User Queries
_________________________________
• Published by the BI power users _________________________________
• Typically developed in production _________________________________
ΠUse a naming standard Y_* prefix and set security so only
power users can change _________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

30

Favorites
_________________________________
• Created from another query in production _________________________________
• Filtered result set _________________________________
• Characteristic/key figure view _________________________________
ΠUse a naming standard X_* prefix and set security so only the
user that created it can change it _________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

31

Build an Effective Query Change Control Strategy


_________________________________
• Understanding and communicating change control _________________________________
helps to eliminate many issues with end users
_________________________________
• Determine how your changes to the data model will
affect existing queries or the existing user base _________________________________
ΠSome query changes will break existing favorites built from _________________________________
that query
_________________________________
ΠKnow what these changes are in order to prevent frustrated
users _________________________________
• Develop a methodology for communicating change _________________________________
• Link changes back to the original functional _________________________________
requirements document and KPI matrix
_________________________________
• Periodically purge non-used queries
ΠPublish a list of these, wait for a few weeks, then delete 32
Query Publishing Strategy Segmentation
_________________________________
• It may make sense to allow the power user queries to _________________________________
exist in production for a limited time
_________________________________
• If these power user queries are useful, they could be
_________________________________
copied and transported by the BI team
Œ This would make them “Sanctioned” _________________________________
• Before sanctioning, queries can be reviewed to make _________________________________
sure they adhere to: _________________________________
ΠDevelopment standards
_________________________________
ΠNaming standards
ΠPerformance standards _________________________________
ΠSecurity standards _________________________________

33

Segment Queries on the Portal


_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

34

SAP NetWeaver BI 7.0 and SAP Enterprise Portal


_________________________________
• SAP NetWeaver BI 7.0 is much more integrated with the _________________________________
SAP Enterprise Portal than SAP BW 3.x
_________________________________
• A portal strategy needs to be developed in conjunction
with the BI team _________________________________
ΠTo federate or not to federate _________________________________
ΠNon-BI content _________________________________
ΠCustom Java
_________________________________
• Organization of the SAP Enterprise Portal
ΠFunctional areas _________________________________
• Security _________________________________
_________________________________

35
What We’ll Cover …
_________________________________
• Development strategy _________________________________
• Publishing strategy _________________________________
• Performance management strategy _________________________________
• Security strategy
_________________________________
• Wrap-up
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

36

Query Performance Tips


_________________________________
• Make sure the query developers understand the data _________________________________
model _________________________________
• Limit the initial query result set
_________________________________
ΠMany queries try to show too much data on the initial view and
the users then “un-drill” the report to match what they need _________________________________
f This degrades performance _________________________________
ΠLimit the level of hierarchies on initial view
_________________________________
f This can slow performance if showing multiple levels of
hierarchies _________________________________
_________________________________
_________________________________

37

Query Performance Tips (cont.)


_________________________________
• Always use mandatory variables _________________________________
ΠTypically this is, at minimum, created for the date criteria
_________________________________
ΠUse variable settings to default values into mandatory
variables _________________________________
ΠHave mandatory variables appear as the first selection _________________________________
ΠMake sure mandatory variables are turned on for all large
queries _________________________________
• Utilize filters based on InfoProviders _________________________________
ΠIf a query is using data from only one InfoProvider, filter the _________________________________
query on that InfoProvider to speed performance
_________________________________
• Suppress results rows if they’re not needed
_________________________________

38
Query Performance Tips (cont.)
_________________________________
• Eliminate or reduce “Not” logic in queries _________________________________
ΠWhen possible
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

39

SAP NetWeaver BI 7.0 Performance Tips


_________________________________
• There is significant performance work being done in _________________________________
SAP NetWeaver BI 7.0 in each Java support package _________________________________
ΠDo your best to stay current with support packages
_________________________________
• This is difficult because the Java is now tied to stacks
ΠThis means that the ABAP and SAP Basis sides need to be _________________________________
upgraded to the new patch at the same time as Java _________________________________
ΠThis typically requires some regression testing
_________________________________
_________________________________
_________________________________
_________________________________

40

SAP NetWeaver BI 7.0 Performance Tips (cont.)


_________________________________
• New features are even being added to support packages _________________________________
ΠYou can find the list of features on the SAP Service
Marketplace
_________________________________

• Many new features in Support Stack 12 _________________________________


ΠSAP did a lot of work to improve Java performance in this _________________________________
support stack
_________________________________
ΠYou should be on this if you are using BI Java
• Plan for a great deal more memory in SAP NetWeaver BI _________________________________
7.0 if using Java _________________________________
• A good Basis resource is a must _________________________________
ΠGetting SAP NetWeaver BI 7.0 tuned properly from an SAP
_________________________________
Basis standpoint is quite challenging
41
What We’ll Cover …
_________________________________
• Development strategy _________________________________
• Publishing strategy _________________________________
• Performance management strategy _________________________________
• Security strategy
_________________________________
• Wrap-up
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

42

Security Options
_________________________________
• SAP NetWeaver BI 7.0 analysis authorizations _________________________________
ΠSAP highly recommends moving to this new method of
_________________________________
security after upgrade
• Analysis authorization security can be set at almost _________________________________
any level _________________________________
ΠCharacteristic/key figure
_________________________________
ΠCharacteristic value
ΠHierarchy node _________________________________
ΠInfoProvider _________________________________
ΠQuery
_________________________________
• Plan a security strategy that will effectively secure
reports with the minimum amount of maintenance and _________________________________
ongoing support
43

SAP Enterprise Portal Security


_________________________________
• Adds another dimension of security _________________________________
ΠMake sure that this is coordinated and reconciled with SAP
NetWeaver BI security
_________________________________
ΠCan be used in place of or in conjunction with the SAP _________________________________
NetWeaver BI security
_________________________________
f This can cause conflicts
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

44
Security Strategy
_________________________________
• Group the users into logical groups _________________________________
ΠUse these roles to help develop the security roles
_________________________________
• Do not forget how ad-hoc or power user development of
_________________________________
queries in production affects security
ΠThis is a big hole in most security strategies _________________________________
ΠThere is often no check to make sure that a newly developed _________________________________
query follows security standards
_________________________________
_________________________________
_________________________________
_________________________________

45

Security Strategy (cont.)


_________________________________
• Plan for security during the requirement gathering _________________________________
process _________________________________
ΠDo not attempt to retrofit the security into the model after
development is complete _________________________________
ΠSome security can be handled or made easier with data _________________________________
modeling decisions
_________________________________
• Plan adequate testing time
_________________________________
• Test from end-to-end
ΠIncluding portal _________________________________
_________________________________
_________________________________

46

What We’ll Cover …


_________________________________
• Development strategy _________________________________
• Publishing strategy _________________________________
• Performance management strategy
_________________________________
• Security strategy
_________________________________
• Wrap-up
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

47
Resources
_________________________________
• Gary Nolan, “Maximize Your Query Optimization Options _________________________________
in BW” (BW Expert, July and August 2007).
_________________________________
• Catherine Roze “Best Practices for Allowing Power
_________________________________
Users to Develop Queries in BW” (BW Expert, March
2004). _________________________________
• Gary Nolan, “Effectively Gather BW Functional _________________________________
Requirements” (BW Expert, May 2007). _________________________________
• Gary Nolan, Efficient SAP NetWeaver BI Implementation
_________________________________
and Project Management (SAP PRESS, 2007).
_________________________________
_________________________________

48

7 Key Points to Take Home


_________________________________
• Develop a strong requirements gathering methodology _________________________________
• Establish and enforce query design standards to ensure _________________________________
consistency
_________________________________
• Understand the advantages and disadvantages to
developing queries directly in production _________________________________

• Develop a publishing strategy to segregate different _________________________________


types of queries _________________________________
• Be cognizant of performance during query development _________________________________
• Have an end-to-end security strategy including the _________________________________
portal
_________________________________
• Create a change control strategy to manage new and
changed queries and roll these out to the end user 49

Your Turn!
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
How to contact me: _________________________________
Gary Nolan
_________________________________
Gary.nolan@tli-usa.com
50
Notes:
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
Notes:
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
Wellesley Information Services, 990 Washington Street, Suite 308, Dedham, MA 02026
Copyright © 2007 Wellesley Information Services. All rights reserved.