Business Intelligence With SAP BI Edge

espresso
tutorialS
•
•
lnstallation and setup tips for Query and repor1ing tools

SAP 81 Edge with SAP ERP best practices
How to build your own Step-by-step instructions on

dynamic SAP ERP data model how to create a SAP BI universe
Thank you for purchasing this book from Espresso Tutoriais!
Like a cup of espresso coffee, Espresso Tutoriais SAP books are concise
and effective. We know that your time is valuable and we deliver infor
mation in a succinct and straightforward manner. lt only takes our read
ers a short amount of time to consume SAP concepts. Our books are
well recognized in the industry for leveraging tutorial-style instruction and
videos to show you step by step how to successfully work with SAP.
Check out our YouTube channel to watch our videos at

https:llwww.youtube.com/user/Espresso Tutoriais.
lf you are interested in SAP Finance and Controlling, join us at

http://www.fico-forum.com/forum2/
to get your SAP questions answered and contribute to discussions.
Related titles from Espresso Tutoriais:

► Anurag Barua: First Steps in SAP® Crystal Reports
http:/15017.espresso-tutorials.com
► Kermit Bravo & Scott Cairncross: SAP® Enterprise Performance
Management (EPM) Add-ln
► Gerardo di Giuseppe: First Steps in SAP® Business Warehouse (BW)
► Jõrg Bõke: SAP® 81 Analysis Office - a Practical Guide
► Shreekant Shiralkar & Deepak Sawant: SAP® BW Performance
Optimization
http:/15102.espresso-tutoria/s.com
► Rob Frye, Joe Darlak, Dr. Bjarne Berg: The SAP® BW to HANA
Migration Handbook
► Dominique Alfermann, Stefan Hartmann, Benedikt Engel: SAP® HANA
Advanced Modeling
http:/1411O.espresso-tutorials.com
Ali you can read:
The SAP
eBook Library
http://free.espresso-tutorials.com
Ili e.sores.s0
.. tu1or1a1s
► Annual online subscription

► SAP information at your fingertips
► Free 30-day triai
Wolfgang Niefert
Business lntelligence with SAP® 81 Edge
ISBN: 978-1-5191-6894-8
Editor: Alice Adams
Proofreading: Christine Parizo
Cover Design: Philip Esch, Martin Munzel
Cover Photo: Fotolia #60596613 © Maxim Kazmin
Interior Design: Johann-Christian Hanke
AII rights reserved.
1st Edition 2015, Gleichen
© 2015 by Espresso Tutoriais GmbH
URL: www.espresso-tutorials.com
AII rights reserved. Neither this publication nor any part of it may be copied or
reproduced in any form or by any means or translated into another language
without the prior consent of Espresso Tutoriais GmbH, Zum Gelenberg 11, 37130
Gleichen, Germany.
Espresso Tutoriais makes no warranties or representations with respects to the

content hereof and specifically disclaims any implied warranties of merchantabil
ity or fitness for any particular purpose. Espresso Tutoriais assumes no responsi
bility for any errors that may appear in this publication.
Feedback
We greatly appreciate any kind of feedback you have concern1ng this book.
Please mail us at info@espresso-tutorials.com.
Table of Contents
Preface 9
1 lntroduction to SAP 8usiness0bjects 8usiness

lntelligence (81), Edge edition 11
1.1 BI business placebo and the SAP shadow theme 12
1.2 Problems with BI projects 13
1.3 The BI consulting method 15
1.4 Chapters overview 17
2 lntroduction to 81 Edge 4.1 19

2.1 BI Edge products and technologies 19
2.2 SAP ECC 6.0 reporting 21
2.3 SAP BI Edge editions 23
2.4 SAP BI Edge installation tips 25
2.5 Custam parameter files for Contrai Configuration
Manager 26
2.6 SAP ECC and BI Edge transport files 28
2.7 SAP system not found when connecting 30
2.8 BI Edge product history 32
2.9 BI Edge positioning of included applications 33
2.10 BI Edge roadmap 33
2.11 Types of reports within the enterprise 34
2.12 Enterprise perspective versus end user problems 35
3 The 81 case study and the top two SAP transaction codes 37
3.1 SAP BI consulting method and system auditing 37
3.2 Different ways to conduct system audits 38
3.3 Transaction code analysis concept 40
3.4 How to use ST03n, SM 19, and SM20 40
3.5 Using BAPls to extract utilization data 46
5
TABLE OF CONTENTS
3.6 Automating BAPls without programming 49

3.7 The most important SAP transaction codes revealed 51
3.8 From SAP data to report 53
4 Connecting to SAP ECC 6.0 57

4.1 The repository concept and KPls 58
4.2 The SAP lnfoSet concept 59
4.3 SAP lnfoSets explained 61
4.4 SQO1 /SQ02/SQ03 61
4.5 SQL tracing in SAP 74
4.6 Your company's dynamic data model and transaction
code portfolio 78
4.7 Summary and next steps 78
5 lnfoSets in BI Edge 4.1 81

5.1 The lnfoSet strategy 82
5.2 Reporting with lnfoSets using BI Edge 84
5.3 lnfoSet and Crystal Reports integration 86
5.4 Create your company repository 89
5.5 lnfoSet limitations 91
5.6 Overcoming limitations 92
5.7 Company repository download 93
5.8 Summary 93
6 Creating a universe in BI Edge 95

6.1 BI Edge versions and patches 96
6.2 Universe versions 97
6.3 Crystal reports versions 98
6.4 Repository and KPls 99
6.5 The present state of BI technology - A criticai
perspective 100
6.6 Connecting to BW, SAP HANA, and others 103
6.7 Creating your first universe 104
6.8 How to create a universe step-by-step 106
6
TABLE OF CONTENTS
6.9 Planning your company's universe strategy 112

6.10 SAP tables and data model repository on GitHub 113
6.11 Summary and next steps 115
7 Publishing reports and dashboards 117

7.1 SAP dashboard evolution 118
7.2 Key aspects of a successful reporting and dashboard
strategy 119
7.3 The smallest unit of reporting in SAP BW 120
7.4 The SAP BW platform evolved -AGILE 122
7.5 Publish the universe for a dashboard 123
7.6 Publish as web service 134
7.7 The BI Edge CMS Repository 137
7.8 API standards evolving 140
7.9 Dashboard design considerations 140
A About the Author 144
B lndex 145
C Disclaimer 149
7
Preface
Visual data representation is a hot topic in the age of big data. 1 would
like to take a step back and ask (with apologies to the German philoso
pher Schopenhauer), do visual representation concepts follow sufficient
reason? Honestly, has it ever occurred to well-informed SAP consultants
why so many reporting-related tools seem to surface and then disap
pear? 1 am sure you have come across more than one ingenious SAP
demo where you see nice screens for reporting tools, only to realize not
too long after that a new tool is already in the works. ln this sense, Scho
penhauer, who is notorious for his complex but appealing theories about
will and representation, has some commonalities with SAP- things are
complicated. ln this book, 1 will review the reporting from a higher level
and use an investigative style that puts the reader in "discovery mode."
This is designed to help cross-functional consultants survive the jungle of
tools and utilize core SAP functionality, which is close to the transactional
level. Hence, you will not find the traditional walk-through demos in this
book but rather a concept that will help you understand the data and cre
ate a framework that you can use in your own projects. This small library
of skills can be leveraged better than dozens of tools that fail if just one
connection is not in order.
The target demographic for this book includes informed cross-functional

consultants who need to understand technology beyond the marketing
demo.
1 will focus on the source of data and its path to the visual representation
in a report or dashboard. How can you find the data in SAP? How can
you train yourself to create a repetitious concept to analyze transactions
in SAP for reporting? With this focus, 1 will expand the scope to connect
with common BI tools and also relate to SAP HANA. 1 will walk you from
SAP ECC transactions to BI tools and transaction codes to Business
Object Universes. Finally, 1 will show you how all of these connect in SAP
HANA without losing track of the core concepts. 1 will also share a BI
Consulting method that focuses on a data audit versus solely focusing on
BI Edge and the tools currently included with this product.
9
PREFACE
Personal Dedication
1 believe real knowledge can be found beneath the surface where it ena
bles us to form new ideas instead of following the old ones. 1 dedicate
this book to my wife and kids who lead me down new paths every day.
We have added an icon to highlight important information:
Tips
Tips highlight information concerning more details about
the subject being described and/or additional back
ground information.
Finally, a note concerning the copyright: all screenshots printed in this

book are the copyright of SAP SE. AII rights are reserved by SAP SE.
Copyright pertains to all SAP images in this publication. For simplifica
tion, we will not mention this specifically underneath every screenshot.
10
1 lntroduction to SAP BusinessObjects
Business lntelligence (81), Edge
edition
"We have the answer, but the relevant question has not been asked
yet." While this sounds a bit funny, it highlights a core element of
modern analytics. Vou have to know what questions to ask before
you can select the right data sources and dig into the data to get the
answers in the form of information that you need. ln SAP 8usi
ness0bjects 8usiness lntelligence (81), Edge edition (81 Edge) terms,
this would mean first defining the semantic layer, then configuring
the data, and finally utilizing the business layer. These are the ele
ments of the so-called "universe" (more about that later).
ldentifying the right questions to ask is an essential part of this book. A

good question to start with is: When do you qualify someone's statement
as brilliant? Are you doing so because your own sentiments are mirrored,
or is it because they are offering a completely new perspective that en
lightens you? 1 hope that you are like me and are drawn to the power of
enlightenment that comes with new ideas.
So what does this have to do with SAP 81 Edge? For starters, 81 is trying
to capture information based on the questions that I asked. Is it possible
to extract new information from the "universe" of data that can enlighten
us even on the questions that I did not ask?
Don't worry, 1 will not drift off into a metaphysical discussion. However, 1
do believe there is power that can be unleashed once the problems are
identified by asking the right questions and then delivering a process that
employs the tools that are part of the SAP 81 Edge suite.
ln the following sections of this book, 1 will identify the key problems
faced with SAP 81 projects. Then, 1 will explore an accelerated implemen
tation process to leverage the value in SAP 81 Edge tools.
11
lN'T'RODUCfION TO SAP BUSINESSÜBJECT'S BUSINESS lNTELLIGENCE (BI), EDGE EDITION
ln this book, you will learn how to use BI Edge tools and gain an under
standing of the key problems that are common to BI projects within the
context of SAP ECC implementations.
1.1 81 business placebo and the SAP shadow theme
Modern ERP systems evolved from the idea that a centralized system
can manage processes better than disparate "islands of data." However,
a centralized approach often comes at a cost for the end user. The rea
son is that an integrated ERP system can only provide value if all of the
departments and users continuously enter and update the data they pro
duce. Users often perceive this requirement as a constraint that limits the
freedom and creativity previously found with Excel, for example.
From a C-Level perspective, though, this looks a bit different. The unified
infrastructure allows for strategic management of the enterprise where
data is effectively summarized, grouped, and analyzed to drive decision
making.
Consequently, the adoption of SAP and related ERP systems is not a

question at the C-Level. lt is interesting, though, that the problems found
at the micro level where users interact with SAP are still very much the
sarne as they were many years ago. The main reason for this is that, at
the micro level, the user has to deal with daily uncertainties and needs
practical ad hoc tools for support. On the marketing front, this problem is
well known, and new products promise to address challenges with self
service BI and similar marketing-style buzzwords.
There is another problem. SAP end users are conditioned to praise SAP,
driven by the tear that they will be labeled as incompetent if they do oth
erwise. This unofficially establishes a shadow theme, which means that
users officially support and are happy with the system. Unofficially, h o w
ever, users feel paralyzed by data entry tasks and the inability to get in
formation out of the system for analysis. When users only utilize the tools
provided and stop creating their own methods to improve business pro
cesses and efficiency, then the shadow theme is at work. lt means that
the organizational structures are not optimized to leverage the creative
input from employees, and consequently, productivity may be sacrificed.
Essentially, the SAP process standardization leverages the integrated

flow of information but may not address the day-to-day operative tasks
12
lNTRODUCT'ION TO SAP BUSINESSÜBJECrs BUSINESS lNTELLIGENCE (BI), EDGE EDITION
that need to be accomplished by users. The religious embrace of the

system leaves users with an inability to deal with the unknown because
they are trapped within an integrated standard process. As time goes by,
the user base may even unlearn the valuable skill of dealing with the
unknown. For example, a user may say "I cannot do x, because SAP
cannot do x."
To further dive into this topic, review the theory of complex responsive
processes. 1 This theory attempts to explain the dynamics, or inclusion
exclusion, used by human agents. The theory states that there is an in
herent level of uncertainty within the organizational life of companies.
The standards imposed by systems such as SAP ECC, SAP CRM, etc.
can inhibit this essential dynamic process and lead to unwanted results.
Consequently, the key challenge with modern ERP business solutions
and 81 projects is to include a process that allows for dynamic change
and integrates the requirements that are yet unknown in the form of a
flexible process.
1.2 Problems with BI projects
What are the core problems with 81 implementations? The project phas
es to implement 81 tools include the traditional phases from requirements
definition to implementation and live operation with maintenance. The
project plan aligns the budget with the milestones that achieve the busi
ness value. So far, this looks good. The reality, however, paints a differ
ent picture. Due to massive infrastructure requirements, as well as the
very dynamic structure of 81, projects are delayed. Numerous tools and
platforms accumulate in a jumble of technologies and tools, which in
stead of providing a clearer image of the data, does the opposite
creating an additional layer of obscurity.
The 81 Project break-even analysis in Figure 1.1 shows the ideal project
investment in red and the value of the project in green. Please note that 1
indicated the maximum value line. This is meant to highlight that only a
certain level of value is reached with the 81 tools. Due to the problems
related to the shadow theme, the value gained from the 81 implementa
tion is limited.
1
Complexity and Group Processes: A radically social understanding of
individuais. Brunner-Routledge, London 2003.
13
User Value /
lnvestment
j
Max,mum Value
Trad it ional BIIBW ---------------- ---------- - ----------------- - -
Target Break Even

� - - --------------------------
--+ Time
GoLrve Competftlve Edge
Figure 1. 1: 8/ project break-even ana/ysis
A closer look reveals that the SAP BI Edge suite includes a full set of B1-
related tools. The high-level schema graph (see Figure 1.2) shows the BI
tools included with BI Edge. Note that the BI tools are independent of
SAP ECC.
NetWeaver Server End-User Analytics
N20NE Portal Business Objects Client Tools
SAP ECC 6.0 System Business Objects Edge
Figure 1.2: SAP 81 Edge technology schema
14
The following key problems can therefore be summarized for 81 projects:
► Time to value: 81 projects take too long.

► 81 projects have a value maximum.
► The shadow theme traps knowledge and expertise.
ln order to address these issues, 1 will introduce a method that targets

the following aspects:
► Improve time-to-value with 81.

► lncrease the maximum value of 81.
► Unleash the potential of the shadow theme and translate it into
usable information with reporting apps designed by agile teams.
1.3 The BI consulting method
The 81 consulting method I introduce in this book utilizes the tools in
cluded with SAP ECC, including SQVI, lnfoSets, etc. and aligns their use
with a strategic deployment of the 81 Edge suite. The priority is to get
immediate production use out of each tool while unleashing the trapped
potential within the organization and translating it into usable reporting
apps.
As shown in Figure 1.3, the 81 consulting method begins a 81 project by

analyzing the SAP module utilization. This will document the current
transaction code use across departments and the transactional volume
associated with them. With the information collected, 1 can conclude ob
vious value potentials that are left unused. For example, 1 can identify if
the features within SAP ECC are utilized or are left unused. ln practice,
MRP often is not fully configured. The most comment explanation for this
is that the implementation team wanted to implement this in a subse
quent phase after the go-live. However, then MRP was never impleme n t
ed.
This information is used as a starting point for 81-related requirements

with a focus on identifying the long-term key competitive advantages that
the organization wants to achieve and maintain.
15
The reporting requirements can then be divided into strategic and opera
tive (daily) reports. While the strategic reports are commonly run from
within SAP B1/BW, there are a significant number of reports that need to
be run on a daily basis. Predominantly, the shadow themed requirements
may surface in the form of operative daily reporting requirements.
The strategic reports will be implemented using the BI Edge tools and
may use the BW infrastructure where data is summari zed, grouped, and
ready for analysis. The operative reports may require real-time analysis
and may also need to mix and merge with information available outside
SAP and within SAP. 1 will establish agile project groups that are ready to
identify those requirements and translate them into reporting apps with
immediate results.
BI Consulting Method
Utilization Shadow N Application

Live Operation
Analysis Theming Design
We are doing this wi th SAP SAP can·t do ... Let's do ...
Business Area • Profit Center
-----------,11 '1·-----------
1
1
'
1
Value Potential
•':-----------
1 1
Utilizat ion Analysis Agile Teams uncover 1
1 1 Reporting Apps Design Cycle
Key Data Sou rces 1 Shadow Themes
1 1
1
61 Success Factors : lmplementat1on 1 Live Operat1on
1
lclentify core requ irements
1 1
1 Start using reports as early a s Manage Production and Re lease
Define umque requirements to possillle 1 Upgrades
1 1
manage competitive advantages 1 Start integrating wilh real data ASAP 1 Encourage Reporting App
lclentify GAPS using SAP usage 1 Establ ish Change Management and 1 devel opment
repolts 1 slralegic d irection 1
1 1
1 1
Utilization - Data Modais - F orecasting

Business lntegration and Transformation Models - BITS
Figure 1.3: Business integration and transformation suite models {BITS)
With this BI project implementation method, 1 am targeting the

established project problems and improving the time to value. 1 can also
raise the maximum value limit because the flexible organization allows it
to adapt and integrate new requirements.
16
Therefore, the 81 consulting method achieves a better project break-even

point and also increases the maximum 81 value (see Figure 1.4).
User Value / f
lnvestment
- -
----- -
,::r
Maximum Value
Acceterated 81 ------------------------ Accelerated ,,
81
''
:' Traditional
Max, mum Value :' 81/BW
Trad1l1onal 81/BW
euai Break Even

Target Break Even
- Time
GoL,ve Reporting Apps
Competitivo Edge
Figure 1.4: Accelerated 81 method ROi improvement
1.4 Chapters overview
During the course of this book, 1 will review the available tools that come
with SAP 81 Edge and position them within the portfolio with regard to the
current task, as well as the user skills required. ln addition, 1 will take a
criticai approach to analyzing the use and implementation of the 81 Edge
Suite, which differs from the commonly found marketing information you
may find on the Internet. The point is that I will add a new and practical
angle to using these tools. ln summary, the book will shine light on info r
mation blurred by marketing information that does nothing more than
feed a business placebo with new products and technologies.
ln Chapter 2, 1 will review all of the products and tools available in the 81
Edge toolset. This includes the positioning of the most criticai products in
a diagram. 1 will also briefly discuss the published roadmap with rele
vance to the existing product versions and new releases. Furthermore, 1
17
will review some important installation and setup tips for 81 Edge with
SAP ECC.
ln Chapter 3, 1 will introduce a case study. This case study forms the core
of the 81 consulting method, which I introduced in Chapter 1. ln essence,
1 will establish a practical approach that guarantees fast results and re
solves the delayed break-even point on larger 81 projects. ln this chapter,
1 will further position the 81 Edge tools and try out them out as part of the
case study. 1 will also define the core elements of a strategic reporting
framework.
ln Chapter 4, 1 will explore the query and reporting tools that are built-in
to SAP ECC 6.0. These tools form the platform for efficiently using 81
Edge tools.
ln Chapter 5, 1 will discuss how to leverage reporting functionality, such

as running Crystal Reports using lnfoSets created in SAP ECC. 1 will also
explore the limitations of this concept.
ln Chapter 6, a universe will be created by expanding upon the

knowledge gleaned from the concepts reviewed in previous chapters.
You will learn the operative and strategic perspectives for these con
cepts.
Finally, in Chapter 7, 1 will walk through a sample solution that publishes

SAP reporting data in a web-friendly format.
18
2 lntroduction to BI Edge 4.1
ln this chapter, 1 will review the BI Edge Suite tools available from
SAP. These tools are updated regularly. That is the primary reason
why focusing on tools is not as effective as focusing the process.
2.1 81 Edge products and technologies
The 81 Edge suite includes a full set of reporting tools that can be orga
nized by function and complexity. For example, there are end user tools
with lower levels of complexity, such as 81 Launchpad and Xcelsius. The
value of these tools is highly based on the infrastructure available to the
project team. This infrastructure is designed with server-based tools that
may be more complex, but are primarily designed for use by technical
admins. For example, the Universe Design Tool creates the semantic
layer and data connections in a hierarchy to publish relevant information
in a business layer. The business layer data can then be consumed by 81
Launchpad and Xcelsius applications. ln the case study, 1 will configure a
full information workflow example. Figure 2.1 highlights that there may be
many tools and layers involved in generating a report that is embedded
within a corporate reporting strategy. For some, this graphic may also
highlight the jumble of tools and interface technologies within the solution
architecture.
Figure 2.2 shows a partial view of the technologies and highlights the
process from semantic to data and the business layer in red. You need to
keep in mind that these three layers are at the core of the 81 Edge con
cept; they are essentially the building blocks of the universe concept.
Therefore, if you want to create a report in 81 Edge, you very rarely just
create a query and use the reporting tool to create a list and/or graphical
visualization. The idea is that you can utilize a complex network of data
sources, which you would connect on the lowest level called the seman
tic layer. 8y semantic, 1 mean the logical language established for re
ports, which will be represented by the data sources selected for the re
porting infrastructure.
19
lN'T'RODUCfION TO BI EDGE 4.1
.._, __
·---
81 l,1unch Pad
..
Bfx\Veb Appllcadons
)--�-IIC.o
'
1
t • • . ' •
--·-·
____ ,,,,
-
·
·-·-
lNllnftCObt«U
R..-po-., to1y Unlof9'no�I�'°" CMC P,ofl�
Profll�s
Figure 2. 1: 81 toais jungle
This selection will define the scope of data to deal with in reports. How
ever, these data sources may have different representations of data and
multiple areas of business focus. For example, there could be manufac
turing and CRM data from various sources that may have unique column
names for data. On the data foundation layer, this data is organized and
prepared for business use. Then, in the third layer, the data is logically
aligned with a business focus so that it can be easily understood by func
tional consultants for reporting.
While at first glance this may sound like a lot of overhead, the concept
makes sense when you have complex data sources with multiple layers
of privileges for user groups and departments. However, you are right
that, for a simple report and ad hoc reporting, this concept may be p e r
ceived as a headache for a user who just needs to create a quick report
in Excel. However, in the long run, the problems you face creating a
mess of quick and dirty reports will be resolved with the organizational
structure of the layered concept introduced with the universe.
20
lNTRODUCnON TO BI EDGE 4.1
Objects
6uslness Layer: blx
Ovtafo4Jndat10n: .df>c
Rd1bonal Conn«tion: .cnx
Publish •
Figure 2.2: 81 universe /ayers
ln the following section, we will look at the 81 Edge tools. ln addition, we

will review the tools that are already built in with SAP ECC. You will also
learn how to connect them.
2.2 SAP ECC 6.0 reporting
81 Edge tools include the following applications:
► CMC Licensing
► lnformation Designer
► Universe Designer
► Crystal Reports
21
► WE81
► Query as a Service
► 81 LaunchPad
► Xcelsius
The CMC - Central Management Console is designed to manage the

administrative overhead not covered by other toais. Essentially, the CMC
must be used to manage the license for 81 Edge, which will then deter
mine the toais available to users. ln 81 Edge 4, a certain number of data
services are included. However, the full feature set of data services is not
included by default. The data services are a separate product that allow
you to further integrate various data sources via service connectors and
present the information by means of the semantic or data layer in the
un1verse.
The information designer is the new version of the universe designer in

81 Edge 4.x. lt will replace the universe designer in future releases.
Please note that, due to compatibility issues, you may have to use the
universe designer for some older production systems. However, if you
are deploying a new project, you can use the information designer.
One of the core reporting products in 81 Edge is Crystal Reports. Crystal

Reports can connect to data sources directly or also use 81 Edge uni
verses.
A WEB/ is a Web lntelligence document that can be run in a browser. lt

usually integrates graphical representations of the data which are com
bined with a grid.
The Query as a Service toai is of particular interest, as using this tech

nology efficiently is very powerful. Essentially, you can create a web s e r
vice based on a query and then consume the web service in Xcelsius. 1
will look at this functionality further as part of the case study.
Xcelsius is an Excel-based add-on that includes various widgets to pre

sent data as a dashboard. For example, you can connect relevant data
based on web services and drive graphics.
22
Figure 2.3 shows the BI Edge toais and also lists the lnfoSet as part of
the SAP ECC 6.0 built-in toais. As part of an accelerated BI implementa
tion, a core aspect of the reporting strategy includes built-in reporting
toais to help drive the BI Edge reports. The lnfoSets will also be used
during the case study. ln fact, the first report created will use the lnfoSet
concept in SAP ECC 6.0.
1. lnfoSet ECC 6.0
2. CMC Licensi ng
3. lnformation Designer
4. Universe Designer 81Edge
5. Crystal Reports (Filter)
6. WE81
7. Query as a Service
8. 81 Launch Pad
9. XCelslus
81 Edge Server Crystal Reports XCelsius

lnformation Designer WEBI 81 Studio
Universe Designer Query as a Service
CMC XCelslus
Figure 2.3: 81 Edge toais
2.3 SAP BI Edge editions

The license code will determine the specific BI Edge product edition
available to you. The license code is noted in the license management
section of the CMC (see the details in Figure 2.4).
23
Central Management Console
• OJrrent held lice.nse ke s seJect a ke to see its lice.n.s· inforrmtion
�
Add Key Addl
DT!OH-NT'MVOOG-JXJSA9M·2ACT86T-O (Product code) Deletel
3 OCOOZ·WCYMIOG-TNVHH9N-5ASOOWC·70 (Product code)
f DP104·VUP3B38·2P2HN9Y·MACT861 ·PR Product code
:!'.. (Olanges take effect irr mediately on clickof Add or Oelete)
-iô" Ucense Key tnformatlon
•
Selected Key Total Ucenses
J
ltimed Users: ll'llimited O
concurrent Users: lrlimited [ O
Processors: o
Elq>ires: 201+03·1 3
,.. Publicatlon Reclplenls: t o
Figure 2.4: CMC license screen
The following 81 Edge editions are available. Please note that these
packages may change as SAP makes updates.
SAP 8usiness Objects 81, Edge Edition, Standard Package:
► This package includes the 81 platform for scheduling and

publishing reports, including the information designer for
semantic layer design.
► Crystal Reports with semantic layer integration. This lets users
design and aggregate data sources using the information design
toai in Crystal Reports.
► SAP WE81 - Web intelligence.
► Advanced Analysis.
► 8usiness Objects Explorer.
► Dashboard design.
SAP 8usiness Objects 81, Edge Edition with data integration:
► ln addition to the standard package, this version also includes

the ETL (Extract Transform and Load) data services. ETL is a
data services environment that allows the user to automatically
24
collect data from vanous sources 1n the form of automated

workflow style services.
► lmpact analysis and data lineage for data services.
SAP 8usiness Objects 81, Edge Edition with data management:
► This edition adds more data quality management for larger

enterprise environments - in particular, the global address
cleansing feature. However, this product is not within the scope
of book.
2.4 SAP BI Edge installation tips
When you install 81 Edge, you will run through the standard installation
wizards. However, there are a number of things that you should be aware
of. Keep in mind that this information may change as SAP updates its
products. Therefore, 1 have chosen to focus on the core aspects that may
apply across versions.
When you install 81 Edge, a separate SQL instance is created by default.

This instance is called <Your Ser v er>\ BCE1 40, as in the example
shown in Figure 2.5. This instance holds information about your 81 Edge
configuration. For example, any adjustments you made using the Central
Management Console (CMC) will be saved in this 81 Edge Content Man
agement System (CMS).
Microsoft SQL Server Management studio
Fê Edit Viow Debug Tools Window Community Holp
Object Explorer Detail• �---------

Comect • ti �2 .;f T @ ,;s Search
l,l NIEFERT-03H90RO\N2010(SQL Ser,er 10.50.1600 • sa)
NIEFERT·03H90RO\BOE140 (SQL Sorver 10.0.1600 •sa)
B NIEFE>.T-03H90>.0\BOE140 (SQL Ser,er 10.0.1óOO • sa)
B eJ Databases Nome Poli Healh state
l±J � System Databases Databases
l±l IJBOE 140 1D Securit y
l±l t;j BOE 140_Audit Server Objects
C!I Security Repl iUltion
l±J � Server Objects Management
1±1 I::!) Repl ication
l±l D Management
Figure 2.5: SQL instance for 81
25
When you log on to the BI Edge installation using the CMC), you have a
drop-down menu to select the type of authentication. lf you do not have a
specific enterprise setup, you may want to log in to the installed instance.
lf the CMS option is not available, you may proceed to create a custem
parameter file.
User Identifícation EJ
Univ erse
�
Design Tool
SAP BusinessObjects·
Enter your name and password to log in.
,��-
MI System 1BISAP:6400 .:]
b its.exe
Shortcut
User Name: 1Administrator
Password:
1 Authentication jEnterprise
OK ! Cancel j Help 1
Figure 2.6: Login window
The problem you may encounter is that the drop-down does not offer the
CMS option. This problem may occur with various BI Edge tools when
trying to log in. ln that case, you may also consult the parameter files.
2.5 Custom parameter files for Control Configuration

Manager
The CONTROL CONFIGURATION MANAGER as shown in Figure 2.7 displays

the criticai services related to your BI Edge system installation. lf you
want to connect to the CMS or run a report publishing function, then you
have to make sure these services are running.
26
f1, Central Conílgurahon Manager l!!!I�EJ

1 s � l ci' 11!i l ► • 11 •• 1� .i x 1 � l li � (1) .:l
DI� Narne Version st«us
1 l, Rlrnn<I
f:l
2.0.6.0
aw""1>11,he, Se<va_BOE1•- 1•.o.•.738 i6 st_..i � •poc1 ofc,y,u1 Rtpo,t put,1,1,er,
0 S.,ver lntelligerc• Agoot (NIEFERT_03H90RO) 2.0.6.0 Ô R.....-.i � � EnterpriSe s«vt<S
O World Wde WebPIJ>ll$Nng Service 6. 1. 7600. 16385 Ô R.....-.i P><>•tdos - QlMOCll,ty..tedmr,lstutlon throogh the lntemot lnlo,m,
◄ �
Reody ú.
Figure 2. 7: Central Configuration Manager
ln order to set the defaults for each application, you can consult the
parameter files in this directory:
C:\ Pr ogram Fi I es ( x86) \ SAP Busi nessCl>j ect s\

Torrcat 6\ v.ebapps\ BCE\ \/éB- 1 NF\ conf i g\ def aul t .
ln order to make a change, create a text file in the directory
C:\ Pr ogram Fi I es ( x86) \ SAP Busi nessCl>j ect s\

Torrcat 6\ v.ebapps\ BCE\ \/éB- 1 NF\ conf i g\ cust om
For example, you could create the file "Bllaunchpad.properties" that can
include custem configuration parameters to allow you to connect with the
CMS.
crrs.default=servernarre:portnurrber
crrs. vi si ble=t r ue
Note that, once you create a parameter file, you need to restart the
Apache Tomcat Services.
You can parametrize the user experience for each 81 Edge tool using this
type of parameter file. T his includes custem products names in the login
window, etc.
27
2.6 SAP ECC and BI Edge transport files

lf you want to use SAP 81 Edge alongside an existing SAP ECC 6.0 sys
tem, you need to install the transport files. You can find the transport files
in the folder shown in Figure 2.8.
/ Cat a_Uni t s/ Transpor t s/ Uni code_corrpat i bl e/data
DATA_UNITS • Transports • unicode compatible

_ • data ..- m ISearch data
--
§--
1 Date modified 1 Type 1 Size
1
Name •
tJ R900047.R72 6/12/2012 1 :51 PM R72 File 201 KB

Q R900688.R21 6/12/2012 l :51 PM R21 File 50 KB
O R900689,R21 6/12/2012 l :51 PM R21 File 159 KB

LJ R900690.R21 6/12/2012 l :51 PM R21 File 199 KB
O R90069I.R21 6/12/2012 l :51 PM R21 File 7 KB
LJ R900695.R21 6/12/2012 l :51 PM R21 File 16 KB
0 R900722.R21 6/12/2012 1 :51 PM R21 File 307 KB

D R900732.R21 6/12/2012 1 :51 PM R21 File 98 KB
LJ R900744.R21 6/12/2012 1 :51 PM R21 File 125 KB
LJ R900748.R21 6/12/2012 1 :51 PM R21 File 21 KB
Figure 2.8: Transports
The transport files will install the necessary drivers and files that will
allow the SAP ECC system to connect with the SAP 81 Edge tools. lf you
do not install these transports, then you may experience connectivity
issues or other related problems.
The transport installation in the SAP ECC system 1s done us1ng the
transaction code STMS (see Figure 2.9).
28
Transport Management System
��!!) !e.$ 4)� �
System System EYP

Transp. Domain Transport domain EYD
········�.. rf "1iVS
••••••••••••► A 1,... -.:it:1r1t:.;1; � "li .'I ,, ..
-:11- :il 7"'
►••···• )ºSTE.111
....
Figure 2.9: SAP Transport Management System
You can consult the file transpor t s_EN. t xt , which explains which type
you must instai!: ANSI or Unicode. The ANSI version is for SAP Basis
systems earlier than 6.20. The Unicode version is for SAP Basis 6.20
and later. You then copy the folder cofiles in usr \ sap\ t rans\ cof i I es
and data in usr\ sap\ t rans\ data. To import the transport, you must
use the STMS transaction ( see Figure 2.1 O).
@ Q..eue Edit Goto fteq.,est [Ex11,is Eni,orment � l:!eb
e . <J Leoerd Ctrl+Shift+F4 lil!I 1iãJ (j/J !ii

� Setú,gs Ctrl+Shift+Fl2
Import Queue: Sy•tem • àdd
1----
A<Uv•te � RS(IUQSIS
Delete in-tedRS(IUQS tS --- -- Fr,d h Other Gto.Jps
�Reque:st.s for
==-- 1211112013 oe,11,21
NUJ&ber Reque:st Clt Ovou Sbort Text St
e,
- - e,
- e,
e,
.- e,
-
· - o
o
- - e,
- e,
e,
.- e,
-
· - e,
e,
e,
Figure 2. 10: Transport status
29
From the menu in Figure 2.10, select OVERVIEW and then IMPORTS.
Double-click on QUEUE. Then, in the top menu, select EXTRAS • ÜTHER
REQUEST • ADD. From the drop-down menu, select the request. Now you
will find the request in the queue. Repeat for all transports as necessary
(see Figure 2.11 ).
�1�1 � � �
Import Queue: System EYP
Q1 8 w � ®. � 'j 61:, �� ÍIB �
- - - - - - - - - - - - - - -- - - - - - --
@Import Transport Request )(
1
Transport Request Freight
Target System System EYP
•
Target Cl ient 1001 Cl ent
i for BP Activation
/Date Execution �, Options 1

Start Date
®Immediate
�,
0At Start Time
1
Planned Start � [04/14/20141 0 13: 12: 321
No Start After 1 0[ 1
0After Event
Event 1 j
Parameters J_ j
� ��
Figure 2. 11: Transport scheduling
You can run the transports immediately to make sure that your SAP ECC
system is prepared. These transport integration steps are commonly ran
1
by your SAP admin. However, want to mention the steps here so that
you are aware of them.
2.7 SAP system not found when connecting
Once you have the parameter files and the transport in place, you can
still run into a situation where you want to select and connect to an exist
ing SAP system. Some 81 Edge tools use the SAPLogon.ini file. You may
30
have to adjust the environment variable and modify the saplogin.ini file
on your system where the BI Edge tools are running.
You can also create the environment variable SAPLm N_I NI FI LE. This
environment variable points to the .ini file, which is commonly placed 1n
the following path (see Figure 2.12):
C: \ User s\ Adni ni st r ator\ Appl:at a\ Poani ng\ SAP\ Olmmn\

sapl ogon. i ni
Systen1 Properties 131

· Computer Name I Hardware Advanced I R emote l
Environn1ent Yariables 13
-user variables for Administrator
1 ,._. ·-
TEMP ¾USERPROFILE¾\AppData\Local\ Temp
TMP ¾USERPROFILE%\AppData\Local\ Temp
New ... Ed it ... Delete

1 1 1
System variables --------------,
Variable Value
PROCESSOR_LE... 6
PROCESSOR_R.•. la05
C:\W indows\system32\WindowsPowerS...
.
, . ....J
SAPLOGON_INI. .. C:\Users\Administrator\AppData\Roami...
..:..1
New ... Ed it. .. Delete
1
OK Cancel j
Edit System Yariable 13

Variable name: �SAPLOGON INI FILE
1
Variable value:
,__o__
K _.,I Cancel
Figure 2. 12: Variables to review
Make sure the saplogon.ini file 1s saved ,n UTF-8 format (see Figure
2.13).
31
(=x::) 1 • Adnwlistrator • AppOata • Roal'JS'IQ • SAP • Corrmon
Organize • Newfolder :: .. fJ
• Name • l Date mo<iied
11
No lems match Y<JU" sear<h.
Downloads
'I:I Recent Pl,.,es
A Ubraries
Ê:) Dorument<
.J, Music
� Picrures
8 Vídeos
; Ccmpute,
t. Local O.Sk(C:)
� O.:.�A OrivP-{í)•) ..:J
Fi le narne: sapbgon.ini •
Save as type: lrext Documents (•.txt) ..:J
• lide Folders1 Encod,ng: IUTF-8 � Cancel
..,..,.,,
,o,Ng
::-
----=�=, ,.._ ___,
_ - --' Ú,
- - - - - - - - - - - --+-
-- --<unicode
-
Unicode bi endian
Figure 2. 13: Update saplogin.ini
8y using this setting, you can be sure that your 81 Edge tools can identify
existing SAP systems and connect properly.
2.8 BI Edge product history
The 81 Edge product versions deserve a special note. lf you are starting
a new project, you may opt to implement version 4.x within the 81 Edge
suite. This will enable you to utilize the new information designer func
tionality. However, keep in mind that a previous version may be more
suited for production use based on the overall requirements and system
complexity you have to cover.
One reason for this is the fact that a major release upgrade from version
3.x to 4.x also includes new concepts and technologies that may have to
be established before they are ready to be used within the enterprise
solution landscape.
32
2.9 BI Edge positioning of included applications
You can picture the BI Edge tools in a graph based on the analytical skills
required and the level of end-user friendliness. While this portfolio seems
complete, it also uncovers a big gap for end user tools. The most com
mon platform for end-user analytics and reporting today is Excel. How
ever, Excel is basically not covered, or only indirectly covered, using the
available tools. 1 am sure many SAP enthusiasts will disagree and claim
that there are many ways to leverage Excel. However, none of the avail
able options can stand its on their own, as Excel requires some other
infrastructure to be in place to be usable.
We will revisit the chart in Figure 2.14 a few times during the course of
this book with additional information.
Analytic Skills
BI LaunchPad BI Studio
XCelsius
Crystal
Cube
lnformation Designer
BI Workbench
lnfoSet
Backend Setup
End User
Frlendly
Figure 2. 14: Positioning the toais
2.10 BI Edge roadmap
The relevance of any roadmap for SAP products must be considered with
SAP HANA in mind. 1 am suggesting this because SAP HANA may be
the most groundbreaking SAP platform since the introduction of R/3.
Therefore, you can expect that many of the tools discussed in this book
33
will eventually somehow be integrated or replaced by SAP HANA tools

and data services.
The 81 Edge technologies will evolve into the open Eclipse platform and
be merged with the SAP HANA (Design) Studio.
You can find details about 81 Edge products on the official roadmap
page: http://service.sap.com/roadmap.
2.11 Types of reports within the enterprise
8efore I move any further with reporting tools, let me quickly clarify the
types of reports commonly looked at in an enterprise. The reports can
largely be organized into strategic reports, which will often be covered by
8W; ad hoc reports; and operational reports, which need to be run by
users without further consulting 8W.
Reporting types include:
► Strategic reports: 8W, cubes, analysis.

► Operational reports: Real-time information.
► Ad hoc reports: User interactive reports.
The main characteristic of strategic 8W reporting is that the data is ex

tracted using predefined extractors to organize relevant data for analysis.
However, this means that the data is often not real time because it must
be synced from the ERP system with 8W.
An example of a typical 8W report is a sales analysis report with a year

to-year comparison. Here, data is collected and grouped in 8W prior to
running the report. Examples of operational reports are: sales orders in
the past hour, web orders placed within the last two hours, and ship
ments made within the last hour.
With the information provided thus far, you may conclude that the strate
gic reports are mostly the ones that utilize 8W and require that the infor
mation be treated and massaged accordingly to be ready for analysis by
subject matter experts.
34
The operational reports may require more direct access to data to short
en the journey from data source to analysis. Therefore, 8W may not nec
essarily be consulted as a data source but rather connect with the SAP
ECC system directly. lt depends on how much delay you can afford when
evaluating the value of the information presented.
ln addition, there is a set of requirements that are not part of the defined
requirements. These are the day-to d - ay requirements that need to be
covered. The users need new reports quickly and every day to analyze.
ln order to avoid feeding into the shadow theme, a strategy is needed to
address these. ln particular, 1 will utilize the 81 consulting method intro
duced in Chapter 1 in the case study to arm users with the necessary
tools to achieve their ongoing reporting requirements.
Finally, it is important to note that more data and better analytics does not
equal better information. lt is important to define a 81 strategy that en
sures that you ask the right questions.
2.12 Enterprise perspective versus end user problems
81 Edge products can effectively cover your reporting and analytical re
porting needs. However, 1 want to ensure that the end user perspective is
not neglected in this book. ln particular, how the 81 Edge tools can help
the common SAP user resolve their daily reporting needs must be de
termined, without having to undergo a large reporting and 81 project to
establish the relevant infrastructure. As mentioned previously, this is
largely an organizational aspect. During the initial scoping of the 81 pro
ject, it must be ensured that a platform is established that allows users to
define and implement their reporting requirements on a daily basis.
Those reporting solutions will evolve as reporting mini-apps, which will
then be used as part of the ongoing refinements to optimize the enter
prise reporting architecture. For example, a new departmental report that
was created as part of a reporting mini-app will be used as a requirement
to define new universe structures that can then be leveraged across the
enterprise outside the limits of the department where the reporting mini
app was designed.
35
3 The BI case study and the top two
SAP transaction codes
ln this chapter, 1 will introduce the tools needed by power users to
translate their requirements into manageable mini-reporting apps. ln
order to gain a solid understanding of this process, 1 will share a
detailed case study.
The case study in this book has two components. The first part focuses
on the BI consulting method and the idea that system utilization is an
indicator for how users navigate and accomplish their tasks. lt forms the
basis to identify utilization exceptions, which surface either in the form of
unused features and/or missing features.
1 will review basic auditing methods to obtain this information. Once this
is done, 1 will continue in Chapter 4 to create actual reports for the
ecommerce example, which forms the second component of the case
study.
First, 1 will walk through the toais you need to structure reporting re
quirements for your SAP system using the concept of system utilization
analysis.
You can then follow the sarne steps when it comes to your own require
ments. During the course of the case study, 1 will also introduce the most
two most important transaction codes in SAP. You may wonder-what
are the most criticai transaction codes in SAP? l'11 share more about the
top two candidates later in this chapter.
3.1 SAP BI consulting method and system auditing
The BI consulting method discussed in Section 1.3 is designed to in

crease the value you can obtain from your SAP BI platform. lt engages
users to enter their knowledge and expertise via the BI mini apps. The BI
mini apps are comprised of specialized user knowledge packaged in the
form of an analytical BI mini app. However, how can the need for a BI
mini app be captured? How can it be determined that there is a gap be
tween the expertise that users have and the way the system functionality
37
THE BICASE STUDY AND 'T'HE TOP T'\XIO SAP TRANSACT'JON CODES
is leveraged? A significant part of this process is analyzing the existing

SAP ECC system.
The utilization analysis is based on common system audit procedures.

This portion of the analysis can drive more productivity in the system.
What is utilization analysis?
Utilization analysis uses audit features that are built into

the functions and tables used with a given instance of
SAP. Within constraints given by the SAP system size
and deployment, this approach can assist with the defi-
nition of an adequate reporting layer.
The SAP audit features track the use of the system. The technique al
lows you to reference the tables used by the transactions and then ap
propriate this information to determine how the system is used versus its
intended use. ln addition, the information collected forms one of the
building blocks to dynamically generate a reporting system.
Let's briefly review the different ways to audit SAP system usage. 1 will
cover the different system usage types via transaction code, function
module, table access, and BAPls. This way, you as the reader will under
stand the options you have available to interact with SAP. lt will clarify the
scope and limitations in later chapters where I will utilize direct table ac
cess for reporting. How does it clarify and limit the scope? Based on the
system utilization audit, it can be determined what transaction codes the
users are employing. This determines and limits the data model that is
relevant for the reporting strategy.
3.2 Different ways to conduct system audits
System audit concepts are used to prove compliance based on industry

requirements. However, in this scenario, 1 am using it to document how
the system is used and to drive relevant improvements. The key factors
to analyze are:
38
THE BICASE STUDY ANO THE ·rop T\X10 SAP 'T'RANSACf!ON CODES
► What transaction codes are employed by users during their work

days?
► What transaction codes are available to users based on the roles
assigned to them?
8ased on this information, conclusions can be drawn that are relevant for
81 reporting, user training, and system customization.
3.2.1 SAP BI reporting conclusions

Once the transaction codes and reports employed by a user are deter
mined, it is possible to evaluate if the way the system is used adequately
supports the business processes that are handled by the user. lf, for e x
ample, the user group does not utilize implemented reports and instead
continues to employ custem reports in Excel, then there is a high likeli
hood that additional system training is required alongside the need for
translating the custem report into a 81 mini app with the relevant report
ing information included.
Furthermore, the transaction code utilization also determines the relevant

data model for the particular SAP ECC system.
3.2.2 User training conclusions
ln addition, the transaction code and report usage can provide insights
into discrepancies between the system features and how the system is
used. Relevant user groups may require re-training in cases where fea
tures are available but remain unused.
3.2.3 System customization conclusions
Often, powerful features in SAP ECC remain unused because, during the
initial implementation phase, a go-live date had to be achieved, and the
infamous Phase 2 tasks were never implemented. For example, Material
Requirements Planning (MRP) is a candidate for this. MRP functionality
is included with SAP ECC, but remains unused in many systems. These
types of areas can be identified with the transaction code analysis.
Therefore, the transaction code analysis can also lead to new blueprint
39
definition requirements. With regards to MRP, this may consequently lead

to a corporate MRP Production Planning blueprint.
3.3 Transaction code analysis concept
The transaction code utilization audit can be done using various ap
proaches in SAP ECC. This is not uncommon with SAP ECC, as there
are various angles you can approach the system from. For example,
while in some instances you may want to use a transaction code to get
the relevant information, you may find that you want to collect data over
time to drive detailed analytics against the data, which is sometimes not
initially possible using a transaction code. ln this instance, you may opt
for a BAPI interface that uses a set of BAPls from within the SAP system
against selected instances. ln addition, the available tools in SAP are
constantly changing and being improved, and there is a good chance
that you may find a different tool in SAP Solution Manager that may
promise to resolve the task. However, keep in mind that the true value
from the SAP ECC system comes from the very core of it. Consequently,
you can always count on the ability to get the job done using transaction
codes and BAPls, which is exactly what those other tools available in
Solution Manager are doing. ln addition, the more you learn about the
SAP ECC system, the more you will find out that many features that are
available via new SAP products were already built into the core SAP
ECC system. For example, BI, MRP, and forecasting and web services to
connect with externai systems are part of SAP ECC.
3.4 How to use ST03n, SM19, and SM20
There are various methods available for auditing the system. However,
the best option to identify what transaction codes a user has employed is
to run the SAP transaction ST03n. This will open the Workload Monitor.
You will have to activate EXPERT MODE.
As shown in Figure 3.1, once you have ST03n open, select TOTAL and
then USER AND SETTLEMENT STATISTICS. ln the submenu, select USER
PROFILES. Within this transaction, there is also an alternate method you
can reach via choosing TOTAL and then selecting BUSINESS TRANSACTION
ANALYSIS. This will then show the sarne result that you would get via the
STAD transaction code.
40
$ 1ST03rJ
L
Workload in Systa11 Svstem 10

�� S'.l mlFIJ screen onfo'ff fcs.r,e YieW
� �pert mode ,
• � Wcrkload
•W Sv,stem 10
Total
•
· Is Business Transaaíoo Analygs
Last Mil'"lJte's Load
1
• B Load Hstory and Distrh.rtion

-�
• li! Load Histoy

• 6'à rns:tance Col"l'(l.;nson
• � U9ers per lnstarx:e
► � BI Workload
• � Collector and Performance DB
• i,, Analysis Views

· � workbad over>Mw
• ['.) Transacbon f:\'otre
· ® Time Profile
• cJ R<11ki"içi Lists
· O Memory Use Statísti:s
• ['.) RFC Profile�
• C5l U9er .:ind Settlement Statlsocs
·!O&lher Profilel
· tf) Settlement Statisti;;s
• � Frontend StatJstJCs
· g Spod Stattst1cs
· lfJ Response lima Distrib.Jti)n
• � Lo.m frO"ll Ei<temsil S't'rtems
· � 0B Connec:tft:11 statisbcs
• � V(I.\C Statlstlcs
Figure 3. 1: Transaction code ST03n
Figure 3.2 shows the transaction codes used in this system in the TRANS
ACTION column. ln arder to activate the system log file to continuously
capture required log information, 1 will utilize transaction SM19 (see Fig
ure 3.3), which allows me to configure the type of data that will be col
lected.
41
SAP Worltlo•d: Single Sútistic•I Records - Overview

Dowrilad @ '8 � .o. • � !ii]o,sp, rrocle §!!Sei. tields 3( Senler 1D �
Systea:
===-- Ntmber ot RFC:s which cesi,onded (vithout error:,):
Analysed tiu: 04/21/2014 / 16:22:00 - 04/21/2014 / 16:32:00
1 ( 1)
Display ID04e: Ãll St.aUSUC tecotds, sort.ed by time
St.erted Serve.e Tr�sa-ction Progrea T Ser. liJp User Response

c.1111e (•.s>
• • • • o
16:22:01 ST03U SAPIJL_ST03N D 1000 2 3
16:22:08 ST1)3U S.lPWL ST03N O 1000 2 138
16:ZZ:18 nAJ> RSSTAT26 D 0010 2 7
16:22:21 ST03U SAPIJL_n03N D 1000 2 4
16:22:30 <btLAYEb PUNCTION CALL> z 1 o
16:22:30 (BATCH) B 2 35
16:22:30 RSPOWPOO s 15 2
16:22:32 ST03U SA.PWL ST03N O 1000 2 467
16:22:58 ST03U SA.PwL_
ST03N D 1000 2 361
16:23:01 ST1)3U SAPIJL_ST03N D 1000 2 432
16:23:0S ST03U SA.PüL Si03N O 1000 2 44
16:23:07 ST03H SAPU-L_ST03N D 1000 Z 339
16:23:27 ..,..,.._.,..:L But. Svnc y o l
Figure 3.2: STAD or ST03N via business transaction analysis
Security Audit: Administer Audit Profi/e
D 't? mi 'lí'
_/Static Confi,;iuratio"j;"OynamicConfigurati
Actlve profile [BITS Activated By 104;16/20141
Displayed profile p>J Changed By 104/18/20141
,./Filter 1 V Filter 2
0Filter act1ve R_e_se_t_�]

� _ I Detailed D i splay
Selection criteria Audi t classes Events

Clent 100 0D,alog logon Ali
User • J @RFC/CPIC iogon
R)RFC call
0Traosaction start
0Report start
0User master change
@System
00ther events
Figure 3.3: Transaction code SM19-create audit profile
42
The audit profile has options for filtering out only those events that you
want to track in the auditing process.
ln this example, 1 have activated all of the criteria. ln Figure 3.4, you see
the area REREAD AUDIT LOG. This allows you to read the current audit log
and view the results. This is identical to the area described in ST03n,
which shows the sarne result as STAD.
An•/ysls ofSecurlty Audlt Lo11
Reiead Audt LOQ Reclsplay ONy Read Al.dt LOQ FIie Statlstlcs
Audt LOQ Entries Read 831
Time Period Restnction

From Date/Time 041211201◄ iMIIMHI:,
1 �
To Date(Tine 04/21/2014 /
Events Extras Format Statis1íc
k_ Reset___,I k 0eta1 Sei.

-
selection C(rteria Aulll Classes Everits
Clent • [lOl;bJLogon AI
User • ✓RFC/CPIC Logon
RjRFCcal
Ri Transaction Start
,/ Report start
,/ User master ch;;rlge
R Other events
"System Events
Figure 3.4: Configure audit profile options
lf you want to identify the location of the audit files, use the top menu
path GOTO• FILE LIST as shown in Figure 3.5.
@ Security Audit -
Log -E dit I Goto ] Environment S'l_sten
... DigJlay Statistics
Fi le Stªtistics
Analysis of Securi/Jj Eile List Shift+F7
Reread Audit Log
Figure 3.5: Find file location of audit log files
43
Once you click on RE-READ AUDIT LOG or call the STAD transaction,
then you will see a result similar to the one shown in Figure 3.6. The
TRANSACTION column shows the transaction codes used by users. Note
that this analysis also shows the PROGRAM, which is an essential part of
our later effort to develop the custem data model for this particular SAP
ECC implementation.
@-f;dl l""'!iOCO--�
e • <1 g e0e Qlle& oa�� lãllll ci>•
SAP WorldoMl:Sln{lle Stlti,t/u/ll«ord, --
- \lJJcS" • • � �-- !iiS&- x,..,.,., <11
_•
$pto,: n1 ....._, of JUt. �di rot...-,6td l'ntbout. ,aGU): 1 ( 1)
,.•
..
An&lJMd �,: 04/18/:01$ / 15:)4:00 • Wlt/2015 / lS:44�N
,u.u,ue
..., ....
OUplqo IJOOI: 111 CteO 't4'� Mtt.44 b7 UM
T>M>o C',U e.,

U H [N) W, -s [NI Cu> IU
• • • •
"'""' .. ..
• • o
•
lS:)4 :1 7 llld:.t,De T O U.PST S l l
u,m
•' •'
lS:)4: 11 4()1.0C Ctu.arf> i: 1
• o u,m
••
o
.. ..
lS:)4: to
<teum rmcncs a u,m
••
15:)4: l:O c.u.t> __ t
1S:l4: l:O ltS.... - -S 1$ !.I.PS'T'S
1$:)4: 2 S SESSIOl_uDQ:fl S.UUl'!ll_JI.Ylc..LTIC9' o ou,e o
" •o
........
15:)4 :)1 fl'AD ltSSTAT2' O •1• O 18
1$:)5:02: fl'� ftSff.l.Tt:6 D IOlt O
,,.,.
"'
4
"''
'·º"
4
•o
-
lS:'5:14 A UOI O
. •' "• "• •o

15:)5:14 � .UVA fflOa:SSIK> ' 1
•'
..
lS:)S:to SESSIOI_UJM.D. S.Utsr!a_Jl'Yt'4TICS D GlOI O 10
,umo
--- --
" "'
1$:)5:20
- . ......
U:35:?0 <tCUlUI na:rtor CAU>
15:)5:20 ibSICRít
•s •" ' ••
o
......
U:)S:to "
.."'••, ,
<amo
--- ......
18
•o
1$:)5:U
o
.. .,..".
--
.,.
U:SS:21 tt&\Tal_lal'ft'._fNI'_11_,u,1.ioç
15:,S:U
.......,. • • •o
- ·-·
......
..........
lS:)S:tt
...... ,,",
1$:)$:,0 <».>ISPU.C:C,, l l
......,.
...• ,,.•
U:)5:)6 D 1-SOI O
15:)5:,t
......,. o
•o
o
-
15:)5:SO
---
lS:)5:St
-
U:H:1 1 a.r.,,. T O l l
•' •' "• "• o
-
•o
1$:)6 :1 1 4CLOC CL&Ut!t> • l
!Umo o
- - -··-·-·
...... ... ... ..
U:H:U
...' ,'
1$:)6:21 4CU1D rmcnor au.-,.
15:H: U s "
1$:)6:'1 o
15:)6:'1 - m: • 1
.,,
... ,'" .. o
o
•
1$:)6:)4
'• •
U:H: )4
1$:'7:U
- - m:
<teu.rc ,menor CAU> ? l • o
o
• •,
.
t; EYP (l) 1 CO • CS<8AP CMl
Figure 3.6: SM20 shows the transaction code when you read the log files
Transaction code SM20 reads the log file content and allows you to view
the content. Now that the relevant information is available, the process
needs to be automated.
There is a program in SAP that can be executed and return the results
seen when running the transaction code STAD. lt is called RSAU SELECT
EVENTS and is a report built into SAP ECC. lt allows you to obtain the
information I discussed above via a report. For these purposes, the re
port needs to be automated so that it runs every day and exports the
data to a database automatically. lt is possible to do this, but it is not a
very straightforward process.
44
You can run reports and programs manually using transaction code
SE38. Once you run the report, you can schedule it via SM36.
[ ABAP Editor: Initia/ Screen
ifc. D� fs.. li 1íJJ [õ � ©,oebugçjng ©,with Variant �Variants
1
Program :RsAu_SELECT_EVENTs
l
!QJ [D Create
Subobjects
@Source Code
ovariants
0Attributes
0Documentat ion
QText elements
�
[
Display J li:? Change
Figure 3. 7: Transaction code SE38-Run ABAP report
ln order to automate this process using the ABAP report

RSAU_SELECT_EVENTS, the report can be scheduled via transaction code
SM36.The process involves writing the file to a spooler and then grab
bing the spooler file via BAPI RSPO_DOWNLOAD_SPOOLJOB. ln addi
tion, 1 have to add a variant input variable when I schedule the report
because I need to run the report with dynamic data ranges.
To summarize the method outlined above, the following steps need to be

completed to get the SAP utilization information:
SM19 • SM20 • SM36 • VARIANT • SPOOLER • BAPI "RSPO

DOWNLOAD SPOOLJOB
This process seems rather convoluted and is not efficient. ln addition,

data obtained this way must also be collected in a database. This is re
quired to analyze trends, etc. Let's take a look at two alternate methods.
While I was able to produce the required results with the previous meth
od, it is very complex to automate the process and utilize the information
in an externai database for reporting. Therefore, 1 suggest alternate ap
proaches to better run and automate the process.
45
3.5 Using BAPls to extract utilization data
lt is one thing to run a transaction code with a transaction. lt is another

story to automate the process to retrieve data that is ready for analysis.
As shown in Section 3.4, a series of transaction codes can only be used

for ad hoc analysis. ln order to automate the process, there is a simpler,
more straightforward approach.
What is a BAPI?
The SAP ECC system offers BAPIS. BAPIS are Busi
ness APls (BAPI). The acronym BAPI stands for Busi
ness Application Programming Interface.
ln fact, it is notable that a large part of the functionality in SAP can be

utilized without the SAP GUI, but rather using BAPls. 1 will utilize a BAPI
to extract the required utilization data and write it into an externai data
base where the data can be used to analyze trends.
There is a transaction code in SAP that allows you to test and run a B A
PI. This way, you can identify what input data is required, and you can
determine if the result meets your goal. ln this case, we will utilize trans
action code SE37 (see Figure 3.8). This allows you to run BAPls and
provide the sarne input that you would later provide in your own applica
tion. SAP provides various BAPls focused on system utilization and sta
tistical data analysis. Once you have SE37 open, you can enter the
name of the BAPI SW-,.C_CXl..LECTCA_CET_AG:REGA.TES.
When you run this BAPI with the correct parameters, you will see the
result tables. ln Figure 3.9, see the highlighted area USERTCODE. lt
shows 36 records. lf you click on the icon next to 36 ENTRIES, you can
see the details for each entry.
46
Function Builder: Initi•I Screen
��oet,,ggng � Test data drectOIY
fe$t for funct.1on group SCSM_

COLLECTOR
f'unct.ion nodule
Functlon Modlle Jsi. 1 1 ccoLL!:CTOR_
_ Gt T AGGRZ:GATES
_ ] Jppetcase/Loveccase o - - -
SWC COLLICTOR G�T AGGREGATES
t:F:::::::=o;=·•=pl•r=::::'..llil t? Olarq, l�ID'-- _ c_,ea_re-'--_,

Iapott paruetets Value -
COHPONEIIT TOTAL 1
ASSICJIDSYS
Function Bui/der: Displ•y SWNC_ COLLECTOR_ e
� � 'P tõ 18 @ 6õ n 1@la;- ...., J:lo � li/i
c:1
PERIODTYPE
PERIODSTRT
D
05/01/2015
SUM!!ARY_ODLY
Ftnctlal rrodule Slll<C_COLLECTOR_GET_AGGREGAn:SJ Aclive FACTOR 1,000
A llit>utes 1
....
...__ ;..;==-.;;..a __
°'....;;..
EXl)Cl'=--1 ..... Tal:ies 7 Exce .- - --------
--r- - - - - - - - -
Tablu 1Value
;._
...
•"•"Lokele Schn1tt.stelle:
,.. IMPORTI«G
Figure 3.8: BAPI runner SE37
es TestFunction Module: Result Screen

e
Test Function Hodule: llesult Screen
PERIODSTRT OS/18/2014
1 SUJOClRY ONtY I
P'ACTOR 1,000
1
Tablu ValW!:
TASKTYPE o tntne.s
Til!t:S
R.esu.l t:
Re5Ult-: 1 8 Lntc1e�
fll O tntdu
16 Enales
0 Entr.1e:S
DBPROCS
EXTSYSTlll
Rc�t:
Result-: 1
B
40 Entdcs
o tnt.nu
o tnu:ie-s
o tntue.s
TCOET
FRO!ffl:ID
P.uult:
1 2 tntxiH
1111 O tnu1e:s
o Entne.s
o tnuie.s
l!EBORY
SPOOLACT
P.uv..Lt:
Rea:ult:
1 1 tn;,ry
lill O i:n,.n..
36 ?ntL1é.S
O tnu-1e.s
2 Ent.uea
TABLlRl:C Ili o tnuie:s
tlSERTCODE
RFCCLNT
R.esul t:
R.esul t:
1 36 Enta:iea
o tntne.s
13 ?nuic:.s
o rnuu.s
6 thtrus
RP'tCLNTDE ST ■ O tnt.r.le:s
Figure 3.9: BAPI SWNC_COLLECTOR_GET_AGGREGATES
47
The BAPI S\.l'IIJC_CXl.LECfffi_GET_AaREG\TES uses the table MONI on

the database table level. You may think that you can just query this table
directly. However, in SAP, there are various types of tables that cannot be
used the sarne way as regular SQL database tables. The MONI table is a
table with cluster columns. This means that metadata is stored here,
which is used by the application server to get the actual data dynamically.
Therefore, you cannot get data via direct table access. You have to use
the BAPI to extract the data.
You can evaluate the structure of the MONI table using transaction code
SE11 (see Figure 3.10).
@ ABAP Dictionary: Initial Screen
e ISEll
ABAP Diction;,ry: Initi;,J Screen
6"0 D $�IH Ili CD
@Database table
0View
0Data type
0Type Group l ]
0Domain
Osearch help
0Lock object
I¾> Display 1 I# Change 1 ID Create
Figure 3. 10: SE11 for MON/ table
Click on DISPLAY to view the structure of the MONI table, which will reveal
that it is a cluster table (actually cluster column) as shown in Figure 3.11.
Tables in the SAP database may have cluster columns. ln this case, you
cannot directly use SQL queries to extract the information.
48
Dictionary: Displ•y Table

� � � t, iâ' ,,;l, '. � áa ,Êi
0
l:J O 11:ll 1111 Technieal 5etthCIS Inde xes... Append Strucu.re...
1!0111
L.
Attrb.ltes Delve,y a-d 1-\ahtenanca Fiekls Entry he\0/chedc Currency/Quantlty Flelds

6
Srth Hefp Prooefnecl T ,pe 1 /6

Field Key Iri... Data e&
11B1,t Data T... Length Doei... Shcr t Cleicriltiln
"""\Êu» PI 7' SYCHAR02 CIIAR 2 OCHAR02 data elemen t for SYST
, SRTJ1> 0 :z SYOW<22 CIIAR 22 oCharacter 22
SRTT2 @ :Z SYBDl4 INT4 10 081N4 data el ement for SYST
� o - SYCB.lRD2 CIIAR 2 OCHAR02 data elem ent for SYST

CLUSTR INT2 s
-
Q --, SYBIN2 OBIN2 data element for SYST
CLUSTI> G � llOHI L RAU LRAV 2886 OOata d.Jstg MOOI: Lang raw
Figure 3. 11: MONI table structure
ln the meantime, 1 have gathered the required information to run and test
BAPls. With this information, you can now use SAP GUI to test the pa
rameters needed to produce the required output for your application. ln
this case, 1 used the S\,1'11\C_CX]_LECTCR_C:ET_Acnl:GA.TES function mod
ule to get the required statistical information based on transaction code
use.
3.6 Automating BAPls without programming
ln order to run BAPls, you need to define the interface and programmati
cally provide the data via C++ or ABAP programs. However, 1 am using a
solution that enables the user to first find a BAPI, then identify the inter
face elements and finally, provide the required input data via a graphical
user interface. The solution is called BITS and leverages BAPls.
The BITS interface shows a graphical interface where you can organize
your tasks and design the workflow. The green boxes represent direct
table access. The yellow boxes are BAPls that take input and produce
output (see Figure 3.12).
49
º�""',,._
,,._
---��,,e,,.,to.,;
llll'P�
111TP<OUe
e- e.--
• J
---
SAPlll'Cwt
.m.... Síne
i,00 .,1 1-l 'l , ... ...
;-��.....
i:- ······· · · ··· ········�············ ·- · · · · ········
.C:.- Moa-llf. «I
.,, f!í,....,,.,.c;r»io.. 'I
.
.,,
·--
...,
,,
�--
::;-,:-_
•Cl1.,__==-
fte
;. »t. €:ii:iiiiiiZtt:1
.,,
fl!__
-CI,.�
'"'e1lblt
ª
11
B 1
o...,_,
,, B ICCltCI'
.,...... "I
.., '"':rz1
ei.,._
......
��
..... .. . . ...
sg--
,__
,o-tt
W•• .., .
n··--·••f...................
-g��w..
IF'tdw.1._W
,.." .......
i:-"s,,Ndlr-.cllk
»-.fit
·
Figure 3.12: BITS interface to run BAPls
The BAPI explorer interface allows the user to search a BAPI by keyword
and then view the interface elements. This essentially provides the func
tionality available via SE37. You can search, find, and test BAPls using
this interface. l n Figure 3.13, you can see the BAPI I searched for and
the required input fields, just like you see in SAP SE37. However, now
you can work without the SAP GUI to automate the task.
""""'"'" - .
.....
,\l'IC.IIIOnI\Ofllt
W,M\Átlltllt
HMdl,t.U.:
r
ib-COl l.t(lCft_ Cifl..,lG(iR(<i,All;S
::J r o.IM•OOl'tCll'U(11'1 y1 \1'1

"'i;:;."'v,.,,,,--� (loctlt.o1e«-'lttrq-..-, tc0rdf>
""=
,...l r;,- Wl Ccwl\lN
....... ,........
,........ •
• ((ff()t,ENJ
HNde.-b,y li.li f1u:f_lO � (41oc<llt4'Kl!Mtlri>t0il) """.......
'
Red �: (-dtheWred:v�) ...IOO,,,.
�ehe4derfie4d; � (i'lhMdeltlblt) PfRKlOSTflT
r ,-«flsrri'(IOOl'tdll'IJ:
5l.tt'NAAV.Ot-l.V
Jl'ACTOR
r ônfflorft!Uv-: � - - - lASf:.TVPf (IA81L]
TASKTIHES f!A8lf]
""""'
TI "5
""""'"
[T-"")
[T-"")
""""'""'
.""_...
P•.wnat•
TC OET
[TABlE]
(TABI.E]
l'tRIOOTYP!:
FRONTE>D
POUOOSTU '""º'" [l""I
[l""I
!POOIACT f!A81L]
�Y.ôNLY
FA<:TOA: TA8lfll;C C [TA8lf]

'""""' (TA&.f)
VSERTCOOf f!A8lf]
.:J
TASKTI�S (TABl.f)
'""'
....oc,
(l-"")
(l-"")
""''""'
""'' (tASLE)
(1""1
.:J
v� S'-'l __________________ -=�v=�=��,==� �• �I
Figure 3.13: BITS BAPI explorer
50
Using this concept in BITS, you can easily automate data extraction from
SAP ECC using BAPls and function modules. Later in this book, 1 will
further expand on this approach and will use BITS to drive the SAP data
model to build the platform for SAP 81 Edge.
3. 7 The most important SAP transaction codes revealed
Using system utilization analysis has provided us with information about

the relevant transaction codes, BAPls, and tables such as MONI. How
ever, how can you connect all of this information without prior knowledge
of the inner workings of your SAP system?
With the following concept, you can understand the SAP system and
structure the relations of tables, procedures, etc. ln the SAP GUI, enter
SE93. This transaction code allows you to maintain transactions. For
example, you can enter the transaction VA02 and click on DISPLAY (see
Figure 3.14). The result will show the transaction name CHANGE SALES
ORDER. You can also just enter a * in the transaction code form field.
Then you can press ( F4) to see the full list of transaction codes by de
scription and transaction code. Note that because there are a lot of
transaction codes, this list will only show a filtered preview. However, for
now, you may understand the key value of SE93. The subsequent screen
also shows the PROGRAM NAME that is used internally by SAP to run
VA02.
@ Maintain Transaction
SE93
0 1
jMaintain Transaction
6Ó � � ê].. li M Cõ �
Transaction Code jvA02 l

tôQn==== _iº __ps __al v-:...-:... I] [__
�___c_ha_n_g_
e __,] [D
� ::. - -:...� _____c_re_a _t_
e __,]
Figure 3.14: SE93 to find program name
51
The program name is displayed in the OISPLAY DIALOG TRANSACTION

screen. We can use this program name to find the relevant dictionary
objects and tables using SE80, which is the ABAP Workbench.
DlsplilyD/iJ/011 TrilnSiJCtlon
+-* �i:8' ó'ô@� AS.COO
7 -
� ......1
Transactlon code
Package
Transaction text Khange Sales Order 1

Program SAPMV45A
Screen number 102
Authorization object [llfl Values
Figure 3.15: SE93 showing the program name
ln essence, this is a way to identify all of the tables involved 1n certain

SAP transactions (see Figure 3.16).
e [SEBO
ABAP Editor: Display Include VBAPDATA
[
jgMIME Repository
1
�Repository Browser
[
� Repository Information System ,1
l!EJT ag Browser 1
!�Transport Organizar 1
[
� T est Repository 1
IProgram B
lsAPMV45A 1...1�1
[ç:, 1 ,l[�l,jl@)�l�[�,I� �
Object Name
• [J SAPMV45A
• l'él Dictionary Structures
1lleso1:ltion
Sales Order Processilg 1 1�,
•
• *CCDATA
• *COBL
• *FPLA
• *FPLAD
• *FPL T
• *FPLTD
• *MTCOM
• *T691K
• *TGSBT
• *TVAK
• *TVAP
• *VBADR •
• *VBAK �
◄► ◄ ►
Figure 3.16: Use transaction SEBO to see dictionary object and tables
52
3.7.1 System Audit Concept Overview

► Use the SAP BAPI that collects auditing information to automati
cally obtain transaction codes used by users.
► When reviewing the transaction codes, also make note of the
program names associated with the transactions.
► Use SE80 to list the data dictionary tables used by program
names.
► Use this information to define the data model that is relevant for
your ECC system. You can do this by tracking the transaction
code and the related program names, which you then can review
in the data dictionary.
► Use BITS to generate the data model and automate the process.
This way, you do not have to go through the process noted
above manually.
► Use BITS to write data back using BAPls. This allows you to in
teract with SAP and write data back instead of just reading it for
reporting. This can be important if you interface with an e
commerce platform, for example. You would read the relevant
product information and use it to update your ecommerce. Then
you would return and write the sales orders back into SAP.
ln order to better utilize this concept, keep in mind that SAP transaction
codes have a common structure. The suffix "1" usually indicates that this
transaction code is used to create transaction data. The suffix "2" is used
to indicate that the relevant transaction code is used to change already
existing transactional data. 1 have noted a rough categorization of this
concept below. You can use this information to better identify the relevant
tables. You can also group the tables involved using this filter.
SAP transaction code structure:
► XX01 e:::, Create

► XX02 e:::, Change
► XX03 e:::, Display
3.8 From SAP data to report

ln order to efficiently create reports using BI Edge tools, it is important to
understand the inner structure of your SAP ECC system. Due to the
53
complexity of the SAP ERP system, there can be very different structures
in place with regard to tables and data, depending on your SAP configu
ration. Therefore, the SAP system audit method has been established to
analyze the system and determine how it is used by users.
Furthermore, users can uncover untapped potential by identifying SAP

functionalities that are available but remain unused. With this concept,
reports can now be created against SAP ECC.
To summarize these efforts, see Figure 3.17 for an overview chart of the
tools I used in this chapter. You can use it as a guide for your own pro
ject.
SAP Utilization Analysis
What Tcodes are used by users?

Audit Report:
What Tcodes are available to users?
-----
STAO Aud,I Report: RSAU_SELECT_EVENTS
SE38- Run Report I Create Report Variants
SM36-Schedule report
Tabtes willt Audit lnfo·

SAP GUI AUCII! Tcocles: SQL Trace Toots CDHDR
SM18/19/20 STAD/ ST03n STOS- Trace User Activity AGR1 _251
SM04- Currenlly connected users SE16- Table Browser AGRH _ IER
SUIM- Roles SE11 -View Table structure SWNCMONI
Essential Admin Tcodes: Run and evaluate BAPIS

SE80- Object Navigator . SE37 (Run BAPI)
SE93- Maintain Transaclions . SWNC_COLLECTOR_GET_AGGREGATES
BAPIS / Function Modules

Direct Table Reporting:
Business Eng ineering SAP GUI Oueries and lnfosets Transparent Table content
ABAP Source Ob ect Types utilizing Apptication Server User can read transparent tab les
j
Methods Uses logical database Application Server is bypassed
Appl icat ion

Server Program Logic dynamically uses Cluster
Table/Column content
User cannot read cluster table/columns
1Business TablesJ Tabtes with Master Data and Transactions
,
"- 1 Metadata table
1
DD02L. SAP Tables
0005S- Foreign Key Fields
..
DD09L-Technical Setlings oftat>les
0026S- Ba.se tables and FKs
Structure Tables • Cluster Tables - Transparent Tables
Figure 3. 17: SAP audit overview
Figure 3.17 shows the path your data takes from the lower database lev
ei where data is stored in tables. The tables can be used in direct que
ries, and in that case, are called transparent tables. Cluster tables have
content that will be prepared by the application server once read. There
fore, the user cannot query this data directly. ln order to find tables with
54
information, you can use transaction code analy sis and auditing. Using
transaction codes will allow you to determine the tables used in SAP. You
will use SE93 and SE80 to do this. The relevant dictionary information is
the basis for your custem SAP data model, which we will further explore
in the Chapter 4.
55
4 Connecting to SAP ECC 6.0
When writing reports against SAP ECC, it is criticai to identify the
relevant information objects. ln order to accomplish this task, a data
model is most commonly used. However, with SAP ECC, the underly
ing data model is so complex that it is not available in a simple for
mat. The data models you can obtain are usually oversimplified, too
complex, or not accurate. The reason for this is that SAP ECC has
thousands of tables, and based on the configuration, there may be
different table structures.
ln addition, not all tables are meant to be read by the user directly. To
recap, SAP uses different table types to store data. The different table
types are:
► Structure tables.
► Cluster tables.
► Transparent tables.
When I say that SAP has a lot of tables, it is really true. There are more
than 50,000 tables in a standard SAP ECC system. However, users can
only employ the transparent tables for queries. The structure and cluster
tables are used by the SAP application server to assemble data dynami
cally as the user works with SAP via the GUI or another interface.
Keep in mind, though, that all the tables are rarely needed to obtain
meaningful transaction data. Most SAP systems use a common set of
functionalities. The common areas are grouped by the modules that are
configured for that particular SAP system. The subtle variances in con
figuration make all the difference when trying to get your queries to run
with SAP ECC. Those will be captured with transaction code utilization.
These subtle differences can have a significant impact. Some examples

of configuration-specific settings that vary from system to system are:
► Specific pricing conditions to configure how pricing is applied in

sales orders.
57
CONNECfING TO SAP ECC 6.0
► Localized tax settings can have a big impact on how tax calcula
tions are dane. They may be different from country to country
and can sometimes also be undocumented. 1 mention this be
cause, in some smaller countries in Eastern Europe, the tax re
quirements are unique and are often adapted by local experts.
Depending on how fast the relevant laws and regulations
change, the relevant tables, programs, etc. may be undocu
mented.
Therefore, 1 dynamically develop the data model on a per-system basis.

The steps taken to develop the data model are the following:
► Determine transaction codes used in SAP system based on SAP

utilization analysis.
► Determine the programs associated with transaction codes.
► Determine the tables used by these programs using the ABAP
Workbench.
► Use this information to create a dynamic repository.
► Develop data models based on the repository.
Please note that this concept can be entirely automated up to the point
that you generate the repository. ln this book, 1 am using N20NE Bits to
accomplish these tasks. But, what if this approach does not get you to
the information you need? ln this case, you can use the concept of SQL
tracing.
4.1 The repository concept and KPls
As part of BI Edge, you get the toais to connect with SAP ECC. Whatever
toais you use to collect the data, it is important to keep in mind the desti
nation and the potential user group. Hence, the data sources you create
have multiple layers. ln SAP BI Edge, these layers are represented in the
universe concept via the data layer, the semantic layer, and the business
layer.
58
CoNNEC'nNG TO SAP ECC 6.0
However, the 81 Edge toais provide no direct support to simplify query

generation with direct table access. ln addition, we cannot write data
back to SAP ECC, which could be required in some instances. ln arder to
achieve this task, you need additional SAP products. An alternative solu
tion for this is, once again, N20NE Bits, which I will continue to use to
generate the externai data model.
ln the meantime, 1 will further focus on the toais provided by SAP in SAP
ECC. As I mentioned before, the SAP ECC system already includes
many toais. ln fact, the more you learn about SAP, the more you will real
ize that many products that evolved from SAP to address certain market
needs already existed in SAP R/3 and SAP ECC. This fact also leads to
the conclusion that a bare banes SAP ECC system is often a better
choice than having additional products in the solution architecture.
Therefore, 1 will focus on the query toais that are built in with SAP ECC.
You can use these query toais to create direct table queries, create que
ries against the logical database, etc. These toais are important because
you can use them as a data source in SAP 81 Edge.
The concepts explained in this chapter are essential when it comes to

designing the 81 Edge universes. The 81 Edge universes hold the infor
mation architecture from the data source to report in a file. With this in
mind, you can better understand why lnfoSets in SAP can be used as a
data source in SAP 81 Edge in the universe concept.
1 will discuss the benefits and limitations of these toais in this chapter. ln
addition, 1 will add more information to the case study, which will continue
to describe the steps required to develop and fine-tune your own data
base model with SAP ECC access.
4.2 The SAP lnfoSet concept
To get started with SAP queries in SAP ECC, use the transaction code
SQVI to open the QuickViewer. lt is, in essence, it is a landing page for
all of your SAP queries.
59
0> Qúd(Vl6w fdt t;ioto �tem �
e!• -�-0 Q1C©'-' Qilll!I coce llill!!I �Ili

,,
Q icltV,.wer:n
I.
/ti.
� IS&lfl#Jn
e� �t
-..._,
COG:>0 cP Q)1n bael,:ao.n:i �savedl.lSU
-
\\'ck:omc (O 1hc
"'-·ickV,ewc,-
1. Eocet ammt ardchoose

.l 1 � O>r,ge-1 !D o.... 1
I:«•" D t]rê � ((1) Execute 1 14-· 1 p: oe.o,xon 1

. Cboose a 1ile and
""'"b.
-
. Eisttlht' mrnrofa Data
QutâVicw, tor wcc:
1
_,,........ -.
...,
•11tt• . This can be a
�ble. a bgical� . a ...,., T«le Tatlef{ew/j;Jn ....., ,._...,
�n, or anhli>Ste iom lrtst TSTCT ...
.
,AP QU<t)' .
. Use 0)'0Ul mxk-(it0
13.)'0.,_ )'OlX QUICk:VICW
�ap""411y.ChooS< bus
�§wb:o:,tt)OO
ti',.w:to drcctlyc:q:,ontbe
epon ficlds sc:kclcd.
Cbc.k onthc h-1pcrlnc to to

to rhe com:,poncmgtops: .,
�onlne doclffll'ff..'lt1on .•
� ' • ' •
'1 .� Eielp toptel : 0.11 IOIIU'CC H � , t..t fidSH � , SoftHs-c.,dt.Sn.«100 ,ln 100Ckfsoo�
.OKM:uclde<'l>OII�,Qu d:1.--, $eed.. .:.
.=J
Figure 4. 1: SQVI QuickViewer initial screen
ln Figure 4.1, you can see that there are two main sections of the screen.
On the left side, there is a brief explanation of the features available in
this section. As discussed previously, most SAP transaction codes are
categorized by a suffix, which identifies the purpose of the transaction
code with regards to create, change, and view functionality. ln this case,
the relevant transaction codes are available via the links on the main
SQVI page. For example, if you click on SAP OUERY, you will go to a new
screen, which you can also reach directly using transaction code S001
(create). The other relevant transaction codes are S002 and S003.
The suffixes 01- 03 in the context of queries mean:
► S001: Create SAP Query.

► S002: lnfoSet based on SAP Query.
► S003: Assign user groups who can use an lnfoSet.
You can see that the increasing suffix identifier structures the expected
workflow. 1 designed the query, then I assigned a query to an lnfoSet.
Finally, 1 assigned a security context for the lnfoSet.
60
4.3 SAP lnfoSets explained
8ased on the description above, you can see that an lnfoSet uses a que
ry, which then can be employed by users who have access to the securi
ty context assigned to the lnfoSet. ln other words, you can only run an
lnfoSet if you have the proper privileges. This is a crucial detail because 1
will utilize lnfoSets as data sources for 81 Edge later in this book. There
fore, you can see that the data we use in 81 Edge can be defined in SAP
ECC using query toais that are already built in to your core SAP ECC
system. The execution of lnfoSets outside of SAP require that the user
executing them have the relevant privileges assigned. The new 81 Edge
version includes a new option that allows the user to connect with SAP
ECC using lnfoSets. For this reason, you can utilize this concept to cre
ate Crystal Reports in 81 Edge. lf you already have preexisting queries
and lnfoSets, you can also leverage this fact and use them in Crystal
Reports as a data source. However, as mentioned previously, you need
to make sure that the relevant user has the required privileges.
4.4 SQ01/SQ02/SQ03
To design a basic query in SAP ECC, start by using transaction code

S001. ln the example in Figure 4.2, you can see that I will be creating a
query called N20\JE_SQ;. ln essence, 1 will be creating a query that
shows all the sales orders and delivery information.
� Qua,y � Goto Extr.i Setu-os Eni,01""",t 5-Dtem t;!Qb
e [SQOll -�<I IQ e0e QINll6 Ct'.!�O li;illll ©�

Query from User Group /ISDFPS/OH:Initil1/ Screen
t:8 ltJ � O ái,) lã Q, Q,Wlth v.inant Q,1n � �Saved Usts
Qt.,e,y area Global Area (Ctoss-dent)
Qt.,e,y N20NE SOS
fit:i Qt.,ick Viewer J fit:i InfoSet Q:,ery J !4:-,� J [& Oesaiption
��[00)[00,� .J �8ª9 �
Quenes of user grc,.p /ISUPS/a-1 : /� Organizational Manage
Name Title lnfoSet Logal Database T;lJefVrew/- !nfoSet Tltle
Figure 4.2: Transaction SQ01-create query
61
Before I continue to create a query, 1 will briefly review the other transac
tion codes involved in this process. Transaction S002 transaction allows
you to create an lnfoSet, which you can do by assigning a query and the
security context (see Figure 4.3).
� l,\foSet Eót (iOCO El!Uts �- en,,,cn,,ent SIS- �
eISQ01l •:<IA e0e w1&1e enol) mn� ��

InfoSet: Inlti•I Screen
ltJ � I} 60 $ � T1a!h AddltJcnalU1ru>ns
lnfoSel Í [□ er..,.
Data scuce Aulhor
Figure 4.3: Transaction SQ02-lnfoSet initial screen
Transaction code S003 is the interface for the user to create and assign
security limitations and groups for the lnfoSet (see Figure 4.4).
With this in mind, 1 can continue with the query creation process by se
lecting the type of data source that I will utilize. ln SAP ECC, you have
the following options for selecting the data source:
► Table.
► Table join.
► Logical database.
► SAP Query lnfoSet.
62
@ User group �dit Goto !2ettings En�irorment S�stem !::!elp
UserGroups:Initia/Screen
1D � � � Additiona l funct ions
Query area _ _ Global Area (Cross-client)
l.9
User ,;iroup _[isAPQUERY10DI Chan,;ie 1 _
._ID cr _ea_te _,
_ _
1 1� 1
1�
Display Description
Assign users and InfoSets �j
User group assignment
l 1'1'
User Chan!JB
InfoSet 1 Change
Figure 4.4: Transaction SQO�query security context
4.4.1 Table data source

The table data source allows you to specify a single table, which can
then be used in the query. Naturally, this does not allow for a lot of flexi
bility because you are limited to a single table. This data source is geared
toward situations where users may have used transaction code SE16,
which allows you to view the content of a specified table. Use the trans
action code SQVI to create queries, create an lnfoSet based on the que
ry, and then make the sarne information that was available via SE16
available in Crystal Reports. ln this scenario, the user would have to use
the lnfoSet as a data source in Crystal Reports (see Figure 4.5).
63
QulckV/ewer:Inlti•I Screen
lô � fl <f>l (l,w«h v.nnt q,1n backg-o.rd *5aved Llsts
Vckome to the
ickViewer
1. Emer a name and choose
1 [im:s Jl LORDS
_ 1 1 I.? Change 1 �I íl =º==C=
re=
•t•==--J
reate D
J. Cboose a title and
lo& SAI' Q.Ery J (<l> Execute 1 '--'*l __o _s...
i ola'-y __,
emarks
. Emer lhe na.meofa Data
uru . 1bis can� a
ble, a logical databasc, a QJcl<Vlew II 2 lS_ A LO�
_
·oi,, or anllik>Sct íiom
Tltle Sales Orders
APQuery.
. Use la}-OU:mode @ to Conirnents 'This wil sh:Jw hJw to extract Sales Oder Information
)'OUI yourQu.:k View
pbically. Cboose basi,
li,node !ê wbc,..,..,-you 1. Data scuce:
,-.n1 t o dÍtcctlyCJ<pOrt tbe
,port fields sdected.
Tál:te
Tatle 8
Tatiepn
Click ontbe b)perlr,k to� Logi:.11 database
to me correspondmg ropic in SAP Q.Ery rnroset
tbe onlne docu-nerution
®§ 8asis mode O@Layout mode
Figure 4.5: SQVI data sources
4.4.2 Table join

The table join data source is where the real fun starts when it comes to
creating your own queries. Use this data source to add related tables and
connect their columns based on primary and foreign keys. ln the follo w
ing sections, 1 will briefly walk through this option. You will learn how to
add related tables, understand how they connect, and verify the connec
tions.
4.4.3 Logical database

The logical database data source hides the complexity of the underlying
table connections with primary keys and foreign keys from the user. 1 n
stead, you can choose the type of information you want to retrieve from a
functional point of view. For example, you can choose a logical database
that holds sales order information. You then do not have to worry about
the details. You can assume that you will find sales order information in
the logical database.
64
4.4.4 SAP Query lnfoSet

The lnfoSet data source can be viewed as a type of logical database
data source because it may incorporate the logic to obtain sales order
information or other information that is organized based on the type of
transactions. However, the lnfoSet also includes the authorization limits
that come with the lnfoSet privileges.
4.4.5 How to use a table join

lf you looked closely at the data source options, you may have noticed
that the table join option is the most powerful option, but also the most
challenging one. lt gives you the most control and therefore requires that
you also know what you are doing. 1 will take you through a closer look at
this option and go through an actual example.
Once you have selected the data source TABLE JOIN, you will see an
empty area with an icon-based menu system (see Figure 4.6). Select
INSERT TABLE. Select carefully because it is advisable to connect tables
from left to right. ln fact, if you do not follow this paradigm, the system
may give you an error when you check the validity of the connections.
@> ,!:>in !;dit !Pto Extr� �em !::[elp
Cre11te QuicltView N2:I._SAL_ORDS: Choose D11t11 Source
"'1 !•i.rnser
lo t �Alias �:a, concitlorlS m� El. (;a
tal:Ê (Snft_.Fl)
Navigation
Figure 4. 6: Transaction code SQV/-insert tables
65
ln this example, 1 have selected the tables in the following sequence:
► VBAK "Sales Document Header Data"

► VBAP "Sales Document Item Data"
► KNA 1 "General Data Customer Master"
► LIPS "SO Documents: Delivery: Item Data"
► LIKP "SO Documents: Delivery: Header"
► VBRP "Billing Document: Item Data"
► VBRK "Billing Document: Header Data"
These are transparent tables that hold business data. The tables are
connected with key fields called primary keys and foreign keys. For ex
ample, the VBAK table holds sales document header information. The
primary key in this table is the VBELN (evolved from the German word
Beleg Nummer) column. This table connects with the VBELN column in
the VBAP table, which holds the item data of the sales orders. Subse
quently, all the tables are connected by single key columns or a combina
tion of key columns. The relevant logic must be developed based on
business logic and required target result.
Please note that the core transaction tables are the sarne for all SAP
ECC systems. However, there may be subtle differences based on how
the system is configured. For example, when you create a query to get
sales orders and pricing for items, then you will have to consider that
different tables may contain the relevant data based on how the particu
lar pricing system was implemented. VK13 is the transaction code to
configure the pricing structure in SAP ECC. Depending how this pricing
structure is implemented, different types of tables hold the data.
When you add the tables in the right sequence, the primary and foreign
key connections are made for you automatically. You can also update the
join conditions by selecting the tables you want to join and then select
JOIN CONDITIONS in the icon based menu. An additional aspect makes
this method of creating your reports user friendly is that the table name is
accompanied by the table's long description. When I mention user friend
ly in this context, 1 mean that the intent of the design seems to have been
to be "user friendly." You decide for yourself if that is really the case or
not.
66
I �"" ....._1
Crem QukkViewNU_SAi.._ ORDS: Choo•e Dm Somee
60 C•, O ,.-
,._ l!l � � �
·- -- ... .
. - -----
- .....,.......,,_
-.....-·-- ---
'
_ ...
, .....ª.............
.,_, ,
........... ='----•
-
°"""'
--
.._
"°"'
•
A""� ,f'4(1N
-- --
....�
..., A-
'°°'
......,__,.,�--
,fPOSJ«
"""'
�I!- ...,,_
�.,_. .,w«-..w..
"""" """'
...
~·
'"''"
Mulh--1Q,w,lilr
--
,c...,10.,,,....,.0,,.;1,
....., o.o...... �-· ._,

....,. ........�
,,.,,.
""""' _,,,
.....
..... •
��twc:-...
s.-_,..,..�----
a-u,,,J-.-
��iiii"' """"'!
---· --...._
�r-�;;�� - = �--ti . . . . ..... . =----... .
�
� � �
................�
....,,_ L ,,.........fí..-í,- 3
-
-
""" • ._.,_, """'
tfvew.;
""'' .,.,.,,.
�o.o-
......�..... .c;.w.
'"'"' ... ......,
w-
-·
-
(
..
�I N-1
°"""•,..�-e
.............
SOdtc:VIWWu,....,.
,wcr u..,..i
......
i;oo.o.--o-,
""" ,.... ..:....-.. -""""'
OtlOI 0t.-
'1Slll
"""
KGI O
......
i.t •C. .
,.,..(P.-.P
....••..
•
• O... ......
�- ..,...,,,..
u.�-.i """'
........
U.N�1�CII-
fllM ,S ....__,.., .,.._ •

•
..,.., � �� .
IVflNftlN.__........
Figure 4. 7: Transaction code SQVI -table join conditions
As you add more tables and connect them, you may come across a situ
ation where there are multiple columns that have to combine to achieve a
proper link. ln this scenario, it can get complex quickly, and you may
have trouble managing the complexity. 1 recommend that you create a
group of manageable queries and table links and then combine those to
create a query hierarchy.
The SAP ECC table join manager also assists with this issue with the
CHECK TABLE JOIN CONDITIONS feature. lnterestingly, this feature checks
the join conditions from left to right. Therefore, the way the tables are
organized on the screen has an impact on how the logic is tested. For
example, in this scenario, there is a message that indicates TABLE LIKP
MUST BE THE RIGHT HAND TABLE IN A JOIN (see Figure 4.8). While this is ra
ther counterintuitive, it can actually be helpful at times.
67
Crt:•te QulckVlt:w N:li_SAL_ORDS: Choo,11 D•t• Sourc11

ó'â(:� o ':s"Alls
1 �);il"l('Qlir;ibollS m � & [la
1m.1
"""" ,._
-- i _,,......,.,..._,,....
-�-
-----
... --
tweAll'1 t..10.C-,1-•111•
(1.-ctllo,re:ti!:::1 '-
.
1 •._.,..,._'"t.:a=-.... 1::
UPl,IIINC
"'"'"'
---
.......
....,.......
[
�"'""" --
--
- ....
..._
-�-......... --
'
..... I
,.,..... !,
"'°"" !!
..... R"""WgC,. �Oo,c,wt-1 ,....
""'""" .........
_....,...,.,..t '""' o.1-,l 'lff
l l
"""'
wos ...;-...i11oa.,..f/_,,,.
_
"'= """"
""' .., ,_ ,.w..< """ ...,.._
"°"'a,,-..iq,.,,,.,
..,.,._
�li�•�
.,.,.,
.............
...""""
""'"'il•,Mt.cft .,....,,..._. Muri,I
,�.,
_..,.,_... ,.............. ......,
......
·--
o-,on..,,,... ___ .,..,,OI),____
...,., _,... CHAA<l
.....
�wt.�
,_,.....
/
,.,,.,
"'"" "'"" .....,_...., 0.-�-c-...
......
(D11119.-«i>H Mill..W�
'""' �-fw$lllil......_
"'"'
--
e...u.i.,..........
��._o,.
..,,,,, "'"j ..._f/_i.
-
S<•�h...
TIM)G
�E ' • _i • •
--·- ,. - .....
-- __
lPAI ,._....... e.-,.. __ "
.. /
--· _-· -
.
-·,....,
,.,,,..,
.......
.L..1te k1•111 1......,..........
TeclllllC:iilJ&we ......
,_
.....,
IT---!Nw I�•-
...... _,,.. .
-- --
I
. -,f-
....,.,,,�..-o.-
'-"A-.UI .H
..... """'
�t+
...... I
e.,,,,,.,
......,. ,, ...
""""
,,..
.,,.., lt"'°'"•C '""" ,.
,...,_..,.._
..... .,. ,._n(..°°"' ......
0-,.,(lft...
'""
()lltfOI
""" ��...,..,._. wo,o
"""" , ...... ,,,_.....,

.,....,_.._,."'
�.,,,,
••n ......"
UGIO S..°'1ff""-
'°""
�(51.i-, u...ic
..... .........
�-""" .._
W-r'n•
�,.;,1/,t,,""4-
f'I
l'J
1.
�
'
...,�,..
,f "
Figure 4.8: Transaction code SQVl-check table join conditions
Once the table is moved a bit to the right, the TABLE JOIN checking fea
ture approves (see Figure 4.9).
c,..te (}ulc.Vkw N2J_SAL._ OIIDS: Choa•• D•t•Source
_ ,
-.... -�--...............
-- ...
-·.......... --
....
,,..,, -
..........
··· -
°"' -
.. , ....._..._.,..._....
,fY. a.ak..í ,_.,......._._
---�
VW11J11
...
,...,_._..__
• Jt 1- A"'"'
.-
-
A"'"'
M
í
-........... ,__,___
-,
A,..., o... .,......,•..,....� A- • ·••c.-11- A....,.
.... __,"
"''"' ...........
.... .,_..�....
,,,_
,,,,.,_
.....
,,.,.. ,._,,,a...,_....
o-...,...........,
-·
""·,
"'
M/llt�
,snv � nl!l4 "6,;,I...._
..�,
..... ...
N_tl._.....0._,
�"'011"'-MllfM
c,..,,
�IIIMII/I.......li•.wlltol ,,,
_.. ..,..,--�
........ ,_,
N
..
, ll'Mo\m
..,., o.......,�---
...... �...,-.....·......... ""'"· """"""''�
...
Dto........�-"''
"""ui."•
0--•�lwc-..llt
�o ....ou-•-.-.
,_ ...... __
/rl\A l(L
so...,,_.;..,....., _,,..
..........
l
,.,..
""'°" ,,.,.t11t11
1 ....
' ..,ov � ""'n!I
• ,}
�·___,, ...-,,,
.............e..-...... " --
JllDtlO..
_....._...........
-
-·....., --
1m.1,._; , e_,_
_, ...
A Wllli o.a,. ..,
e..._
-o• ..
,.. ,..,_
,flO.tffl C-t�I EflMirl,\ "_,,,.._ .....
,.....,
__ ,.,.,
, ......... .•
o...... ��w.c
""' "' """ �...................

A_,.
"""
•
.....
<,ltl•I
11o1,o1e
.. s.o.,--
"""" ..,., �......., .......
t.,....((uo-.�o,Çw o,,a.-,'""
...... "' •
V..., g
,..n
HMo.........._ SI
' .
Figure 4.9: Transaction code SQVI -table joins positioning
68
Without consideration of the positional impact of a table, 1 have grouped

the tables in this example query by function. You can use this as a start
ing point for your own sales order queries. The functional groups of ta
bles are the essential order-to-cash (OTC) tables and are surrounded by
red boxes (see Figure 4.10).
Customer Table VBAK: Sales Header LIKP: SD D lvry Data VBRK: Billing Header
KNA1 VBAP: Sales ltems LIPS: SD D lvry ltems VBRP: Billing ltems
__.........-__ ·-�--- -"--� -�- --

_
_,..,.______
-- --
_,..._ ....._
_,_ -.
íL"'-:••_.....,.....__
-·.......... -...---�""-- -,._, ,- ....,_
--· --- - ---
_____,.,_...,_
i
,l'1Ml.N
�
...,. .....
U'
,Wf
.-·..,. _.,a.,;,.,_a.-.. .._....

1:
, ...
-
o...._._._o.
-· �..... W'fl,�....-.,.......�
oe-
...
�- ..._o_.
Qo-�--�"'- lJ.t».t
""" ..,.. .__

...,,,, s..o.-- .._,
.....�.._,-
�.,.........-.......11;-,,_ -
o.-o-.p.,
...�
......,,� ,.....
·-,_ ,______
-
....., _..,., - --
"41r•P
'
to-- .,_,,.,,,
. .. ·-• ....: . ._...,..._
-_
�-=· .. .. .:.
< ..................
,�
•·"-"'-·--·=. ,.
- -�
"'
.:,: ,
<• •-........l
... , _,..,_.,.._ .• ...... ... -
--- -
,i I.U'I"°
e,....,.. ...
' .,_ ...T
w�•
.._ ._
_ -....-· �- --- ---

""'" ,,�o.,,,-.....
-,_ ., -
T
...
�
,_, "
...
''"'., ._........ ,--.- i ., ..,,.
r - ,;-,.
_ ..
.-·....· ...............
�-
.......-...... .....:i.-
l'l,n;o:
........._.,..,..__.._ -
,i...:1151"'
""'''li: ..,,,,,
j-
-- ,i �
...,.___.,#___
---· ,..
-- --
....... �....---<,,,.,-.
.,....,. ---�--"·
""' ""'"" '-·"- _
�-... ----
....-,1--<-,,-
... s.,_-........._.'"""'._tb....,.
lllllO
"'"' ,�-
. -- ..,.._
a....... ....._,._c,
...,.. --J-
t.... . . ,.__. _ ._ l'\l.Hl
�..
....�·....··-�li!
- �,. .,. :--...........o--
mw
- "' •
.....-••-u--":/'--
�
�
'-�·• •o,
• -
Figure 4. 10: Direct table example /ogic
Once all the tables you require for your query are selected and connect
ed properly, you can proceed with the next step. Select the columns from
the selected tables that you want to display in the query result. Keep in
mind that, up until now, you only selected the tables, and the logical way
they are connected is by Primary Keys (PKs) and Foreign Keys (FKs).
Now you can select the relevant columns. This is achieved by reviewing
the DATA FIELDS section in the top left corner. Once you click on the arrow
next to the table name, all of the columns for this table will be displayed,
and you can select them. The selected columns will be displayed in the
right hand section FIELDS IN LIST (see Figure 4.11 ).
69
-
QulckV/ewer:InltlalScreen
rnla'yrut mxkl <:i>Exerute 60 00 00 fi
Dat afiefds USt •••
• T )Jl"l
• 8Sa1es0ocunent: HNCler 1
4
1
Title Sales°'"""
• B0mera1 Data ri Custuner 3 Conments TI-is M show how to ext,act Sales o-der lnformat ion
► BSM00a.ffll,rit: lttm OII o
• Dso dxunent: Oeherr : u o
o
• Bso ocw:t.ment: DeMry 1-11 'SAPUstVlow9< ·I
-'
._,.,
• Bea,g Doo.rnent: ltem CM o
Ust lld. selec t . Scrt seq,.ence Selectlcn felct o.ata Souce
Doo.rnent: 1-eader o
FIE!lds ti '5t Avatbiefieljs

No. Flel:IOescrlpt. llD Fd:tOesai:lt. llD
1 _s,;,,ooc,,,-.n, Oillt O'I Wt-ictl Record Wat •
• •
Fl '• CUSwm>r,....,,.,.,1 Ent,v twnt
N:wnt °' Pfl'fOn• c,.at,
Nlrnl 1
II)
8 Nlrnl2 Q.(KlllOn/ ll'Q.lr'y. v,lld (tt
D.IliU"IU wNctl l:llcS/Q,.,l)Ut
�
00Q.tr1lrlt Oilt {Oatt Rtct
�
---
so cfoct.mlint tittQ(lry
[ill \,a"ISaetJOn �o.e>
• • • • •• �
SaltsOOCl.ll"llt"lt Typo
uic1cV,ewer-Fie1d aelection Odet reason (reason for tt
Choose the f�lds you w:u1t to
· ,-pby in th,e list Cclectoe ourt>e< (SO)
o selec:1, dek on� �.,,the toble Dehertblxl<(doc.,,...,th •
oncrolonthe r;lt anel choose ◄ . Blro tlock hSO docunerr •
o destlcct. cOCk on thettltl)'illhe ◄ •
•
ble comoion tbe leli anel cOOOse
•
�l>woo ►
ou chlnge tbe tieli scquenc:e usir:ig lhe
◄ • ◄ •
IP'-it>uttom
• • a.d •.
on6dis and �lttti:m tields can�
aftd onW appropriatt �s
Figure 4. 11: Transaction code SQV/-manage co/umns for report
ln this example in Figure 4.11, 1 have CUSTOMER NUMBER 1, NAME 1, and

NAME 2 selected. lf you carefully review the other tab pages on the right,
you can conclude that the subsequent steps would involve sorting, etc.
Therefore, you can essentially create a customized query using the ta
ble-based tools available in SAP ECC.
ln other words, this is a visual query designer where the forms and fields
completed will determine the resulting query logic (see Figure 4.12).
70
QuickViewer: Initia/ Screen
� Layout mode @>Execute 6"b 00 00 00
Data fields
I
1 • ffflGenerai Data in Customer
1 List ...
3
Qui ckView jN2l_SAL_ORDS l
• Customer Number 1 b!J ... Tit le Sales Orders
o
E
• Country Key Comments This will show how to extract Sales Order Infc
• Name 1 ,/
.
• Name 2
o
�
• C ty
i
• Postal Code o Exportas JsAP List Viewer ...]
• Reg on (State, Prov nce,
i i o List fld. select. Sort sequence /Selection fields ½
Sort field o
• House number and stree
o
• First te ephone number
l
Fax Number
o
o lãl.l ds in list
• Ind cator: Is the account

i o i1 No. ow !Field Descr ipt. 1m
• Address o l . . Sales Document
...
o 8-
-
• Search term for matchco
... Customer Number 1
o
2
• Search Term for Matchco �
... Name 1
• Search term for matchco o "
••
• Title
o El 4 . . Name 2
1•
• Centrai arder b ock for cu
l o ='
• Express train stat on
• -· i o
n
o ...
. �
International location nun
• Internat onal location nun n
◄ ►
i
1 ◄ ►o ◄ ► �
-
>-- ·1
Figure 4. 12: Transaction code SQVl-selected co/umns
You can also test the query as you progress through the process. Once
you test it, you can save the query. To initiate the test, click on the EXE
CUTE button as shown in Figure 4.13.
71
QuickViewer NU_SAL_ ORDS list design

@Layout mode <i,Execute b" 00 !J8 fi
l••-••
Data fields list •.. QuidcView _jN2l_SAL_ORDi_J
• llfl General Dat a in Customer 3 •
Tiije
• Customer NUmber 1 � •
• Cruntry Key O ccmnents _Jrt-is will show how t o ext,act sael s Order Informati:ln
·Nanel liJ
• Name 2 liJ
• City 0
!SAP List Vlewer
• Postal Code 0 Exportas :]
• Region (State , Pl'ovince, e O
Us t fld . select. SOrt se(lJer v::e SelecticV1 fie l ds Data source
• Sort fteld 0
• House nunber and street O
• First te lephone number O Availabl e fiel:ls
• Fax Numbe, O Field Descript. Fiel d Oescript.
Eil. El}
• Indi cator: Is the account
Row �
O j
. . Sales Document l'mH:h Record wa,
•
• Ad:lress O ◄ :
��:� ��
J
• Search term fcr matchcoc . . Customer Nu mber 1
•
O : Y
• Search T erm for Matchco, O ... Name 1 ame of Person who Creab
• Search term fcr matchcoc O
3
4
[Ij -r._
... Name 2 uotation/lr-.:iuiry is va licl frc
-'
·Title O :
. 0
Cl _f
7 ---ioate unti wh ich bid/quotat
[◄◄J
OC!
f�:::.:�.;�;�/
• r,..,...+,..,1 ,..�,..,. 1-J.-..rl, 1.,-.,. .- , ..
◄ ► ◄ ► ◄ ► -
- �
- - ��-
QuickVie\ver-Field -
selection -
-. ri5I __;
� ,
Cboose tbe fields you want to
Tr ansacti on group
display w tbe list 1
_y;ales oocument Type
o select, click on tbe entty in tbe table
-,Order reason (reason for t�
ontrol on tbe right and cboose ◄ .
o deselect, click on tbe entry in tbe -t uarantee date
ble contrai on the left and choose Collective nurrber (SD)
ushbutton ► . Oelivery b lock (cbccment h •
ou change lhe field sequence usingthe 1smrg !:rock n SD documen ...
i
ushbuttons ,... and "". • ◄ ►
Sort fields and selection fields can b e •
naiatained o nthe appropriate pages ◄ ► ◄ ►
Figure 4. 13: Transaction code SQV/- test run
Figure 4.14 shows the additional options available to design the query
using table-based forms in SAP ECC.
The last step in the process will save the query with the name you as
sign. By doing so, you can call this query again later using the parame
ters you defined. With reference to SAP 81 Edge, this means that the
query will be available in Crystal Reports only if you create an lnfoSet
based on the query (see Figure 4.15).
72
QuickView J
T i tle
Comments This wil l show how to extract Sales Order Jnformation
Export as J SAP List Viewer •I

List fld. select. ;' Sort sequence /Selection fields Data Source
11. Data source:

1Table join
12. Data source table join

[ Change join
Figure 4.14: Transaction code SQVl-additional options
QulckV/ewer:Inltiilf Screen
(t:J� o <til <l,w.th va1.llt (t>Jn badq°""' .,.,...,,..uru
-
Wdcomc to thc OutckV,cwcr ..:.
1. Enter amme and cboosc Creatc Q
2. Choose
Qud<Vlew lâ1_SA.L_ORDS
1.:1
°"""" l (D o- 4
--. 1 _,,. : Oesooc:ion .,
a ta� am ter'tW'k:s.
3 . Eaerlhe m.me oh Oat:a Source
J'biscanbc a table, alogi:aldatabasc, líii � '1 §, ))
a joil, or anln&:&t iomSAP Q ucry .
ou1c1ev1ev:• toe uuc: BUTIR
4. Use layour rmde til t0 la)'OUI )'Our
6'< -
g..__. �.,
�u,::k \/,ew s,aphó:aly. Choose buis
1
1 WoSet
1
. ,@. wbcnc,'Cr you wam to d..cctly T�liOln t>loSettilte
the rep01t 6c:1b
: sclected. sã;êsQde's VSAK ...
test 19CT • . •
Clickonlh< b)pe,ld< togo
to tbc conespond.ilgtops: n
tbtonline doctrnemaUO!l
.
Figure 4.15: Save the query so that it appears in the query /ist
73
4.5 SQL tracing in SAP
Sometimes you do not know which tables are involved in a complex

transaction. For example, the previously shown method to identify the
program name for a transaction and then using SE80 to get the involved
tables via the dictionary view does not work. This sometimes happens
when the dictionary table list is large, and tables we need for the query
cannot easily be identified. ln this situation, 1 can use the SQL trace
method to trace the background SQL transactions that are performed
during a transaction.
The SQL tracing method requires that you activate the trace using trans
action code ST05 performance analysis. Select SQL TRACE and click on
ACTIVATE TRACE. Next, open another session with SAP GUI and perform
the transactions you want to later run reports on. For example, enter a
sales order while the SQL trace continues to run in the background.
Once the transaction is complete, click on DEACTIVATE TRACE and then
run DISPLAY TRACE. The trace collected contains all of the SQL transac
tions performed by the transaction (see Figure 4.16).
@- e_erformance Trace �dit �oto System t:Jelp
1
e lsTos
L 1
Performance Analysis
Se lect Trace Select Trace Ft.11ction
1
1 �SQL Trace Activate Trace
0Enqueue Trace Activate Trace with Filter
ORFC Trace 1 Oeactivate Trace 1

0Table Buffer Trace
11 Oisplay Trace
Enter SQL Statement

1 1
Trace Status
�ll Traces are Switched Off - Proqress Display On __]
Figure 4.16: Transaction code STOS - tracing SQL
74
ln the trace window, click on the line that relates to the transaction you
want to analyze. Then, in the top section, select EXPLAIN. ln SQL terms,
this means that the SQL transactions are explained in detailed SQL nota
tion. Essentially, you get all of the SQL commands that were performed
during the SAP transactions while the SQL trace was active. ln other
words, by analyzing the SQL commands, you can reverse-engineer the
SAP transactions and identify the tables that were used to write the data
during the transaction. Hence, you get the relevant tables and the prima
ry key and foreign key relationships most of the time. lf you utilize this
method, you will also understand that there are often many transactions
in SAP ECC that are not relevant for a specific SQL trace. Therefore, you
need to develop a good understanding of which record to select in the
trace window. ln addition, you have to adequately set the proper filters
when you start the trace (see Figure 4.17).
Tr•t:e u,t
� OO IC --1 1
�E,plan (3- Ili Q'\ 8 �
Ttanuc:uon 1 IVoc:1C Pc:�.. no ulrroc. 1'ypf: sc;olcuut. 1ool1Ju.r JQ.I.TUIneblWIP waouixAJe ru1eJsJoois$PU:J001 loe.tf: OS/23/l0141
Dutot1on Ob). noae

•• Rec•. RC St.t.c:ac:nt -
-
32,688 p(ECffl o o c:omur t cored)
Tl:atiuetion sov1I 1Ttan:sGU'll> BCBOlll lF68JPlOte383001S$Plt"lOO?loate
'
ptoeus no O Proc. Type ou cuent 1oo 1o.su 05/23/20141
l
=
lkl t
l
Dutttlon Ob) , nlM •· Rec1, RC lt.ett atnt 1•
,..,. [OU•IR Otl!N
;
S ILICT IIHtPZ " HUU:" • ' 1• P):SlPlSV.ut: 11f;; T:1'1U>IR '/ /º\ll"IC, cd, •t
'",. l'RMR
dTru •IR
r!TCH
OP!r.t
1
O !l!L!CT IMtRt ··1u.,v;·· • ' 1• P)i SU
. UVAP: l )4416 T :TPblP /ºune. rd. 0/
,..,,•• IR OP!N o
O
( l'Rl>IR oO CO IVU-T
/
.
Jl;TCH
IX!CIT.t.
'! EL!CT lii'XtRt . . NllCt" • /•une. td.
'º' ....,.
IR /º Pl151Pisv.ut:11��4 T:'nl>IR 0 0
1
/ /
�
Ll r!TCH
...... OPIUI O Sll.ltT lllitRE "ft.Ul)T'' • 1 UI) -,.Zl,IV • t AD •Sln'rv • 1 .uro '"SRrn" >• 1 Rll IY '"rwwr'' , "IU:UD" ,"SRTn>'" ,"Slttn"
...,., ...... "'"'" 1),,

300 l"ITCH 11 o
150 OPEN O IIL!CT WHEP,E ..-1WB>T" • , AID -.LIV • 1 AIID "'SRTW • t AW '"SRTT2" >• 1 ON!R IIY ..l'Wn)T"' , "RELID" ,NSRTrt>.. ,'"SRT12"
... AOU>B
iOlbl mtH o
AOU>II o
..
FITCH 1) o
521 AQlbl o
, AOWI "'"'"
mtH
""'"
1)
1) o
••• AOLTS
17 .\OU>B
10&l�OLTS
OP!N
1
SJ
o
O S!L!CT Wt:RE �JUJll>T"' • ;, � - c u., - • ;, r Jl3:5.\PlJ.OI! X::S:46.?.? T:lOLTS •t 1•unc. td,•/
o
---
rl:TCH
..
''· ·-· · . - - - •---• T• • . - ---·,· ·-· · .,
/•une. rd. •/ 1
- -
•� n -•.
108.356,�,
.. OP!lí O SlL!CT ffflERE T 00 •"ILIJ:lr" • 1 /' R3:/18CDW/SA,LIQ000000000027:449 T:VBAK •/
14 V84X mtH o o
Figure 4. 17: Trace Jist explain SQL details
When you identify the correct record and click EXPLAIN, then you will get
a full SQL statement (see Figure 4.18). ln summary, you can use the
information to:
► ldentify tables used during SAP transactions.

► ldentify the relationship between the tables.
► Review columns used by the tables.
► ldentify the possible use of non-transparent tables.
► Review the parameters used to filter the result set.
75
SQL stiltement with pilrill11eters from SAP SQL stiltistics

II,lfuJ Saeen On/Off '"f? �Explain u:!Table deta-1 � ABAP cocle ii
Connected to: ll:I
SQL Code Explain Tree Text Expla in
Parameters: From SAP/SQL tiace, used for executlon of already complled staternent
SELECT T_OO ."VBELN" AS e ,T_Ol ."KUIIllR" AS e ,T_Ol ."NAJ!El" AS e ,T_Ol

."NAm:2" AS e ,T_02 ."VBELN" AS e , T 03
_ ."POS)lR" AS e , T 0
_ 3 ."VBELM" A.Se ,T_04
,"VBILNN AS e ,T_OS ,"VBELN" AS e ,T_D6 ,"KNKLI" AS e ,T_06 ."VBELN" AS e
FROM "VBAK" T_OO INNIR
JOIN "KNA1" T Ol
_ ON T Ol_ . "IIANDT" = QPO AND T Ol_ . "KUNIJR" = T OO
_ . "!OIKLI"
IIINER
JOIN "VBAP" T 02 ON T 02 . "IIANDT" = RPl AND T 02 ."VBEL N" • T 00 ."VBELN"
..... í[u1,co1
Par name Param type Par vai
CPO nv;ychar(3) N'lOO'
CPl nvarchar(3) N'lCXJ'
CP2 nvarchar(3) N'lOO'
CP3 nv;ychar(3) N'lOO'
CP<! nvarchar(3) N'lCXJ'
(l'tlc,c:; nltYN"l�(':1\ l\l'lnrl'
Figure 4. 18: SQL explain details
Therefore, you can use the SAP GUI to run the transactions you want to
report on. Enable the trace and then analyze the trace result using the
method described above.
As this task may evolve into a tedious process to go through all of the
tables and identify their name, columns, and links to other tables, 1 rec
ommend an organized approach. For example, if you want to trace a
single transaction, you can easily use the method suggested here. How
ever, if you have a large set of transactions, it requires that you organize
and structure the project.
An example toai you can use to organize the queries and data in a way
so that you can easily maintain it and use it in 81 Edge is the N20NE Bits
SQL Designer for SAP ECC. This toai is built in with the core N20NE Bits
interface. You can easily find a table by its table name and then see the
table description and the links to other tables. lt makes the task of going
through many SAP transaction codes with multiple sessions much easier
and reduces it to a single interface where you can immediately test and
adjust your queries even without a SAP connection (see Figure 4.19).
76
ri-OHLtJ!;ii#t\1itl11Hi#Ml111rli
e, B /. e:,; ~• a, ·1 ► ■ l.i) s tt ti C\ !il
--
,,._
e El""""'
- ,....., - -
,,,.....,
ln� - Qut-ry bcJlld,rt (�)
--
·-
�-: l<t�d.:t4bsseq.,e,y>
... °"'
HTIP � «um,
�·
..,,__,
SAP�Cc.el
--
�□- ):::.SI _V6# A(;iOer,dtoZSI
-..............
°""""""""
COffllMscipor«ed -� Addtiotlalo.taaNSOOOC\
--
_ 3GZYBAP �Têlef'Of'CEM04t•í
heetêle
□-• bttlL't8AP -�('()fSale$
□--
º'°""
Tnl.)_V8J4> �'l!.Al>ffan Offllf'ie
!
'
º""""
► S.SDoo.ment: Jtem0ot4
--
--
[J,s-,,w_CN
º""-
Vef'SIIOn: 5-s�: ne
--
□-"'
º"""°
º""....
PmnJAetcfctte�
n ....
na.
--·- -· ,.
•
Figure 4. 19: BITS SAP ECC Query Designer
ln Figure 4.19, you can see the table VBAP selected on the right side. 1
can easily identify the table using a direct table search or by entering a
search key for the table description. This searches the SAP table reposi
tory and returns a list of matching candidates. You can drag the desired
table to the center and then continue with related tables. You can also
generate descriptive documentation that makes the resulting code easy
to read. This is especially important when you design complex queries
and need to update them or have third party team members who need to
make updates to existing queries. Please also note that you can further
add BAPI integrations to obtain data from SAP ECC based on transac
tions.
With this method, 1 can:
► Easily create SAP ECC queries.

► Document the results in the Query Tool.
► Structure queries hierarchically to keep them simple.
► Enable team members to modify queries.
77
► Use BAPls to obtain transaction code use information.

► Generate a transaction code cloud and landscape automatically.
► ldentify the tables used in the department or company automati
cally.
► lmplement customized data models for SAP ECC.
4.6 Your company's dynamic data model and transaction

code portfol io
You are now armed with the toais and techniques to conquer every SAP
reporting challenge using the existing SAP ECC toais. Combined with the
additional toai N20NE Bits, you can leverage these steps and automate
transaction code utilization. With the standard SAP business models,
which are organized by business function based on modules, you have
all of the required information needed for your specific project.
SAP has standard transaction tables that are used to collect business
transactions. Based on your specific configuration, collect the transaction
codes used by department. Using the concepts presented in this book,
you can identify the tables used for the transactions. Given the nature of
the tables involved, you can use direct queries for transparent tables. For
other business data, you have to leverage BAPls, which can be auto
mated using the N20ne Bits solution.
ln essence, you dynamically create your company-specific 81 model. The

81 model even allows you to integrate externai applications using BAPls,
which means that your SAP ECC system gains flexibility and usability
without the need for any other software.
4.7 Summary and next steps
ln this chapter, 1 reviewed the techniques and toais you find within SAP
ECC for query design. 1 utilized SQVI and related transaction codes to
design a business query. ln addition to the already described methods to
analyze SAP transaction code use, 1 also discussed the SQL trace meth
od to identify tables and columns used internally by SAP during the exe
cution of transactions.
78
Finally, 1 briefly explored an alternative tool, N20NE Bits for SAP ECC,
which makes the overall query design easier and more efficient to man
age.
ln the next chapter, 1 will expand on these concepts and will then define
the dynamic SAP ECC Data Model for your specific ECC configuration.
ln fact, you already have the tools and the knowledge at this point to
identify how this may work. You can review your own system to see how
to create your dynamic data model.
79
5 lnfoSets i n BI Edge 4.1
"Great minds think alike!" is a famous quote that is meant to be in
spiring. lt means that great minds think alike in the way they think
differently from others. Therefore, what it really means is that "Great
minds think differently! And inspire new thoughts."
So far, you may have realized that we are not following the mainstream
SAP marketing books. Regurgitating marketing brochure content that
would just follow the current marketing wave to advocate a new product
for each and every trendy demand is not the goal of this book. lnstead, 1
want to encourage what the new SAP CEO called the simplification of
SAP product line. 1 agree with this notion and find that the simplest way
is when you use the concepts and technology that is already built in with
SAP ECC. Therefore, 1 am not exploring products alone, but I am touch
ing on the concepts used to build products such as BOBJ BW and SAP
HANA and using those concepts to design my own reporting framework.
ln this book, you are learning some of the core concepts that are used by
BOBJ and SAP HANA to integrate with SAP. ln particular, this book is
discussing the SAP ECC meta database that comes with SAP ECC,
used to extract table logic. ln this chapter, 1 will expand on this concept
and use it to create our own meta database model. lf you combine this
with the transaction code analysis, it is possible to achieve a data model
that accurately represents your requirements based on actual system
usage.
The main question you may ask is "Why would you need BOBJ BW,
then?" You may find your own answer. However, there are some im
portant factors to consider. While you can create your own data ware
house database and run reports and analytics, you can indeed benefit
from BOBJ BW content. For example, if you have a multinational SAP
system rollout and require a full 81 infrastructure, the predefined BW con
tent in BOBJ BW can provide guidance and a starting point for a larger
corporate reporting strategy.
Nonetheless, you can utilize the concepts introduced in this book to im
plement a specialized data warehouse without the overhead of the larger
content that comes with BOBJ BW. ln this sense, you introduce different
81
lNFOSETS IN BI EDGE 4.1
thoughts and this can serve as an inspiration for your business intelli
gence.
ln this chapter, we will utilize the lnfoSet concept. This will add another
layer to our current set of toais. At this point, you are able to identify ta
bles in SAP and also know how to create lnfoSets in SAP ECC. With this
concept, you can essentially group your queries into functional groups.
The queries are assigned privileges and are hence integrated with the
SAP privilege concept.
First, 1 will discuss how to run lnfoSets outside of SAP ECC. For this ex
ample, 1 will utilize Crystal Reports. ln Crystal, you can use the lnfoSet
data source, which will allow you to connect to the lnfoSets in SAP. H o w
ever, the settings must be correct. You will learn how to make sure the
lnfoSets actually show up in the Crystal Reports data source. 1 will use a
set of screenshots to highlight the areas where you need to focus.
You can create many lnfoSets and organize them by functional module
area. You will see an example framework in the form of the company
repository. 1 will then use this example to touch on the limitations of this
concept. Finally, 1 will challenge the limitations and identify solutions to
overcome them.
5.1 The lnfoSet strategy
The lnfoSet concept allows you to group queries within SAP ECC, assign
a name, and then restrict access by allocating the lnfoSet to a user
group. The user group is employed to restrict access.
ln arder to create an lnfoSet strategy, 1 recommend that you carefully

plan the structure. ln this book, 1 recommend a dynamic model based on
transaction code use. Using this model, the core areas utilized in SAP
can be identified. Then, queries can be created and grouped by SAP
module.
82
lNFOSET'S IN BI EDGE 4.1
You can see how to structure this type of model. On the left side, you can
see the organizational chart. Here I employ the commonly used organi
zational information objects that are part of every SAP implementation.
lndeed, these information objects are very different from system to sys
tem. Of course, there are crucial differences in the way the system 1s
configured and operates.
For example, 1 have the following information objects:
► Countries
► Companies
► Subsidiaries
► Address locations
► Company codes
► Controlling areas
► Logistics: Werke and Fertigungshallen (factories and manufac-
turing sites)
► Sales and Distribution: sales offices, sales groups, sales district
► Material master: Material master records and storage locations
Based on the organizational aspects that determine how the system op
erates, the actual master data collects and manages data to enable the
administration of the company processes within this organizational con
figuration. The master data and transactional data is the basis for report
ing. The reporting data uses key figures to measure the business perfo r
mance.
ln order to limit the scope of our reporting, 1 use the business process
consulting based on the transaction code analysis. 1 identify the scope in
which the SAP system is used and identify how the future system utiliza
tion can be improved to better use the investment made in SAP ECC
(see Figure 5.1 ).
83
..! i o .lA..1 We are live.

■-
HllFlRT
Data Model Framework
CertHled Solutlons UC Are you? Buslness Process Consultlng
Organizational Chart Master

,� -�
: Transactions Logins
Data 1 ._____,
,� T Code
-per�
1
1
1
Countrles Key 1
1
11
Figures 1 Login Oepartments
Address
Companles Subsldlarles
location
1
Company TCode
Employees
Codes Trending
Controlling
Areas
01 Werke Fertigungshallen
1 Customers
01 11 1
Sales
Sales Offices Sales Group Sales District
:1
1
Sales Orders
Employees
01 11 1
1
Werke 1 lnventory
Lagerort 1 GAP Analysis
1 Master
1
--------------
Unused Features such as
----------------------------------► MRP
1 Key Figures
Figure 5. 1: SAP data model framework
ln summary, 1 recommend that you use a process-oriented approach to

identify your reporting needs and structure them based on the SAP mod
ule concept. ln conjunction with this, you can use a larger lnfoSet con
cept to cover your reporting needs. ln addition, your internai team can
collaborate on the model based on its departmental focus.
5.2 Reporting with lnfoSets using 81 Edge
lnfoSets can be used as a data source with SAP 81 Edge Crystal Re
ports. 1 will look at an example and review how you can make sure the
lnfoSets show up in Crystal Reports when you connect the lnfoSet data
source (see Figure 5.2).
84
-:') Oatabase Cxpel't
Oala
Browse the data source for the tables pou want lo add.
(Note: to edil the aias f0< a table . select lhe table in the 'Selected Tableo ' ltee and cicl< onl °'
p,ess lhe F2 key)
Ava i ab
l le Data S01.1cet: Selected Tables:
IE e:J My Connection, El ···6 10.10.30.58
EI EJ Oeate New Connec:t ion � SALESORDERS
í±I C)Acce,s/E,o::e l (DAO)
1±1 e:JADO NET �ML)
1,±1 O Database Fi les
ffi e)Java Beans Connect iv ily
!ti 0JOBCIJNOI)
1±1 CJ ODBC (ROO)
1±1 e:JDLAP
1E � OLE 08 (ADO)
� CJ 01acl e Seive,
D
1±1 Salesforce.com
1±1 SAP 8W MOXQuei
!E
l.!I SAP Operational Data Store
ltJ CJ SAP Tab le . C luster. or Funclion
eJ
1±1 Univ.,.es
1±1 C)XML andWeb Services
IE e:J Repository
@ CJ More Data S01.1ces
Figure 5.2: lnfoSet data source
When you create a new connection in Crystal Reports, you need to

choose the SAP INFOSET data source. This will prompt you with the rele
vant login screen where you will enter the username assigned to you for
your reporting project (see Figure 5.3).
85
-,Õ c;tandard RP.port ff'f"ahon Wuard EJ

º"'ª
Choose the data)101.1 want to rept,11 on_
Availbble Data SOl.l'ces:: SAP System lo,gon D

lll 8 S Q LC:ienl11_
_ 1 •
lll 8 S Q LCien
_ l 1 11_ 1_
Your SAP System here
8 OCieateNewConnecôon
t
lll E)AccewExcel[DAO)
lll E)AOO.NET [XML)
� EJDatabate Ae.s
lll E)Jova Bean, Conneclivi;y
1
lll e)JOBC IJNOI)
lll e)ODBC{ROO)
Usemame:
lll l::)OLAP
lll ElDLE 08 (ADO)
ffi E)Oracle Se,ve,
lll E)S• l-.com
lll SAP BVI MDX Quer
,e1,
8 OSAP lnfo
t, Make NewConneciion
. .
-/-�==;;,�= Click on "Make New Connectlon"
!ll l::)SAP Ope,aôonal Data Store

lll E)SAP Tab le . O..,te,. orfcr,côon
ffi E)Unr.,e,,es
lll E)XML ondWeb Semee.
� �Q.................. - - - �
-
<Bock I Ne,d> Hclp
Figure 5.3: lnfoSet /ogin
Once you log in, you get a list of lnfoSets that can be used as a data
source. However, if your required lnfoSet does not show up, you may
have to configure the security groups in SAP that your user is assigned
to. 1 will review this task in SAP briefly.
5.3 lnfoSet and Crystal Reports integration
ln the SAP GUI, use transaction codeSQ02 to access the initial lnfoSet
screen. First, select the name of the lnfoSet. ln this example, the name
of the lnfoSet is SALESORDERS. Then, select ROLE/USER GROUP As
SIGNMENT (see Figure 5.4).
86
@' tnfoSet �dlt �ato Extrjs §ettings Enylronment System t:!8':l
e JSQ021
e -
InfoSet: Initi11I Screen
[!) � ffi 61, $ i;b Trash Adt:ltonal
l functlJns
Que(y af'ea Global Area (cross-cllent)
InfoSet SALESOJU>ERS [.? Change 1D Create
'l 1
lf:c [�
Cillll•� Oesc(,Ptien
11 1
�
1 Role/us,,·G,oup Asslg"ment 1
��[l!lll� � ��l [@J
SI... lnfoSet Oescríptien Data SO..ce Aulhor
•
•
-
�
0 SALESOROO\S Sales Orders .loín usi"g VBAP ... MGOAANTlA •

. .
◄ ► ◄ ►
� 3/2 • CSASAP INS
Figure 5.4: Part 1-/nfoSet role/user group assignment
Once this assignment is complete, make sure that the user group has the
relevant user assigned. For this step, use transaction code SQ03, which
will take you to the USER GROUPS transaction (see Figure 5.5).
Once these settings are complete, your lnfoSet should be available in the
Crystal Reports lnfoSet data source if you choose the appropriate user.
87
@ User group !;_dit Goto âettings Enyironment S�stem Help
UserGroups:Initi8/Screen
Cõ � liil � Addit ional functions
1
Query area Global Area (Cross-client)
User group -1 -
..........
, ['9 Change
] [D (reate
* Display ] [ª'
[�------� Description
Assign users and InfoSets
User group assiç,-iment
User
1 -
F [
.:? Change
1
InfoSet 1 1 [# Change
Figure 5.5: Part 2-lnfoSet role/user group assignment
� Standard Report [r-eation Wtzard f3

Fieldt
Choo,e lhe inf"1Mlionto� a, lhe•-
Availabls Fi�s: Ftelds lo Oisplay.
E: SAI.ESOROERS = SAI.ESORDERS.VBAK-AUART
= VBAK-AUART = SAI.ESOROERS.VBAK·ERDAT
8
= SAI.ESORDERS.VBAK-ERNAM
= VBAK-ERNAM
ca VBAK-EROAT
= SAI.ESORDERS.VBAK•VBELN
= VBAK-vBELN = SAI.ESOROERS.TEXT_VBAK__AUAAT
= TEXT_VBAK AUART = SAI.ESORDERS.T E X TVBAP
= TEXT_VB A PABGRU = SAI.ESORDERS.VBAP·ABGRU
_ _ _MATNR
= T E X TVB.AP_MATNR = SAI.ESOROERS.VBAP-ARKTX
_
= T E X TVBAP
_
= SAI.ESORDERS.VBAP-l,1AHlR
= VBAP-ABGRU = SAI.ESOROERS.VBAP-POSNR
_ PSTYV
_
= VBAP-ARKTX = SAI.ESORDERS.VBAP.VBELN
= VBAP-MATNR = SAI.ESOROERS.VBAP·ZMENG
= VBAP.f'OSNR = SAI.ESOROERS.VBAP-ZMENG UNIT
= VBAP-PSTYV
= VBAP-vBELN
= VBAP�ENG U NIT
o:, VBAP�MENG
f"rdf"oeld...
< Back Frlish Cance l Help
Figure 5.6: Select the fields for Crystal Reports
88
ln Figure 5.6, you can see a set of fields selected for display in the Crys
tal Report. ln summary, you can see that the new lnfoSet data source
can be used to efficiently report against lnfoSets with SAP ECC.
5.4 Create your company repository
As outlined in the beginning of this chapter, 1 recommend that you care

fully plan your lnfoSet infrastructure. ln order to do so, take a process
oriented approach that has the operational structure of your SAP system
as the basis. This will tie your reporting requirements directly to your da
ta. ln Figure 5.7, you will see that we move from the business area,
which is based on SAP utilization analysis, toward reporting apps and the
key figure system.
SAP Utilization Now and future plans Reporting Apps Key Figure System
SAP Organizacional
System Layers
Sales Oistribution
Organization Channel
ompany Oistribution
Code Channels Purchasing Sales
Organi.zation Area SAP Sales SAP CRM
Oivi.sions
Warehouses Dashboard Forecastíng
MRP Alerts /Trending
Oemand Plants
Management ----
Execut111e SAP Log1st1cs SAP Pl•nning
Business Area Logistics Profit Center
P!ott_,_
===---
Cosi_.
---Componycodo
...
--- Con..a,,g .,..
Figure 5. 7: From business area to key figure system
The data in SAP is organized in a systematic structure (see Figure 5.7).

You can see that the order-to-cash (OTC) process uses a set of docu
ments as part of the overall process. Those documents are structured
based on the organizational configuration of the SAP system. Hence, the
OTC process includes the following process steps, which collect data via
89
the relevant transaction codes. The transaction codes determine the rel
evant tables, which reflect the organizational parameters configured for
your SAP system.
The OTC process includes:
► Sales order (VBAK, VBAP, KNA1, ...)

► Picking delivery
► Goods issue
► Tracking
► Delivery
► Shipping
► lnvoice
► AR status
► Payment
Each process uses backend tables and structures. The information is

collected based on the organizational structure, which was configured
during the SAP implementation (see Figure 5.8).
ales Organizalion
Organizational Distribution Channel '.·•
Divísíon
Data (Satea Offlcoa. 1ale1 groupa.
Sh ipplng Pointa, Loadlng Polnta)
Customer and Item Master OTC - Order to Cash Process
li
CustomersNendors
Material Master Conditions Goods
lssue
Tracking
Document Document Master KNAl Oelivery Shipping

Master VBAP
•••
VBAK
Currencies and system
Global Settings independent settings LIPS VBRP
LIKP VBRK
T-Codes
Programs
Tables
T-Code
Analysis
• lnventory Processes
Other Processes
Figure 5.8: Document data and processes
90
With this concept, you can create your own SAP data model. This can be
used to generate reports as well as a custom key figure system.
5.5 lnfoSet limitations
While the lnfoSet concept is very powerful, it also has some limitations.
Those limitations can impact your overall strategy. However, for most
limitations, 1 will recommend adjustments to the concept as a solution.
5.5.1 Only SAP data

The most obvious limitation is that you can only use SAP ECC data with
in basic lnfoSets. lf you run reports that require data from other sources,
you can extract this data separately and connect the different sources
using the universe concept, which I will discuss in the next chapter. ln
addition, if you need to extract and transform additional data sources,
then the data services may be required, which is not included with all
editions of the SAP 81 Edge suite. 1 will also discuss the 81 Edge v e r
sions in the next chapter.
5.5.2 SAP-centric
lt is an advantage to use the tools provided by SAP ECC for your report
ing strategy. However, sometimes you may not want to further expand on
the tools built in with SAP ECC. ln that case, you may opt for an externai
solution such as 81 Edge, 81/BW, or SAP HANA. ln addition, you can opt
for other third party tools and connect the 81 elements using the concepts
shown.
5.5.3 Performance hit
The lnfoSets utilize the SAP ECC database directly. Therefore, exten
sively using this concept can lead to performance hits, which will de
crease the response time of the relevant server. 1 will show you in the
next section how to create your own mini-SI database. Keep in mind that
the direct SAP access also has a major advantage-you always have
real-time data in your reports.
91
5.5.4 Not in web applications

There is also another crucial limitation. The lnfoSet data source cannot
be used if you are planning to deploy your Crystal Reports in an ASP.Net
application. Crystal Reports can be embedded within ASP.Net applica
tions. ln this setting, you can programmatically pass parameters based
on the type of user for example. However, in this scenario the Crystal
Reports cannot utilize the lnfoSet data source.
5.5.5 Cryptic usage
While there is an advantage to using buil t -in reporting toais in SAP ECC
to create lnfoSets, 1 must mention that the using SAP overall is very alien
to non-SAP users. Therefore, this approach can only be leveraged if your
organization has a user group that knows how to use the SAP GUI. On
the other hand, SAP queries can be used to create an interface for non
SAP experts, who are knowledgeable in basic SQL and 81 concepts.
They can then leverage the information without having to worry about
any specific 81 software.
5.6 Overcoming limitations
With every concept, there are advantages and disadvantages. The con
cept suggested shines here when it comes to creating a lightweight re
porting system. However, there are some issues we need to overcome:
► The query design is complex.

► Queries can be disorganized without proper planning.
► The integration of externai data sources is not built in with the
concept.
► Direct access to the database may require that we create an ad
ditional 81 database to prevent performance problems.
► Traditional queries cannot update data in SAP.
ln Chapter 6, 1 will address each of these issues in depth.
92
5.7 Company repository download
An essential aspect of this concept is to utilize SAP queries based on

system use. The concept addresses the issue that every SAP ECC sys
tem has a different configuration resulting in the use of different tables.
However, while the tables are different, there is also a common core of
tables that are always used. Therefore, 1 will introduce a collection of
queries that are built around the common core. The queries can be used
as a starting point to develop your customized set of queries and ln
foSets.
1 am planning to publish the query sets as open source projects on

GitHub. The queries will be organized by functional area. This will be a
collection of queries and key figures. The link is not available yet but will
be updated on my company website (www.niefert.com).
5.8 Summary
ln this chapter, we focused on SAP lnfoSets. Essentially, lnfoSets are the

connection to the SAP world. 1 utilized Crystal Reports to run a report
based on the lnfoSet data. You learned that there are some crucial steps
in regards to the privileges running Crystal Reports with an lnfoSet data
source. 1 mentioned that you can create an lnfoSet architecture as the
basis of your reporting. However, it is vital that you plan properly or risk
losing control of the multitude of queries and lnfoSets. Finally, 1 reviewed
the possible shortcomings of the concept but also highlighted that these
shortcomings can be overcome with proper planning. ln addition, you
learned about the upcoming GitHub project "SAP Query Bootstrapping."
ln the next chapter, 1 will explore a mini-BI system and the common core
queries you need to get started.
93
6 Creating a universe in BI Edge
Up until now, 1 have focused on the 81 tools from a SAP ERP-centric
perspective. This was done to help you understand the related trans
action codes in SAP that identify tables and transactions, as well as
how to create classic lnfoSets. Now you can basically run reports
without any additional tools, which is a nice skill to have. ln my opin
ion, it is the core skill you need to effectively design 81 reporting
strategies and also understand the 81 tools delivered with SAP as
part of the Edge and the 8l/8W suite. For example, once you have
designed your own queries and start to manage the issues from run
ning reports with millions of rows, you may better appreciate the
value you get from the tools that come with SAP 81 Edge/8W. How
ever, even with those advanced tools and platforms, you will still
benefit from the core skill of running queries against SAP tables di
rectly. As mentioned previously, SAP offers a large set of 81 tools,
and those tools are rapidly changing and being updated because the
81 field is a core business driver. Furthermore, the introduction of
SAP HANA as a platform is rapidly improving and will be the core
platform for all SAP products in the near future.
Nevertheless, in this chapter, 1 will focus on the most essential compo

nent of BI Edge, the information design too/ (/OT). Using this tool, you
can design data models and layer the data, which will then be saved as
universes. 1 will cover the core concepts of designing universes and also
relate the topic to newer products such as SAP HANA.
1 will also clarify that the IDT is of principal importance because this is
where data is structured and data sources are connected. l t is also here
where security is integrated. ln order to clarify regarding how to strate
gize with the IDT, 1 will further expand on a business model to create a
custom mini-BI system.
The mini-BI model will put the universe design process and the relevant
tools on a practical platform where you can apply the model design pro
cess and structure the tools needed for this process.
95
CREA'nNG A UNIVERSE IN BI EDGE
6.1 BI Edge versions and patches
When using SAP 81 and other software packages, it is extremely im

portant to be aware of the versions and patch levels you are using. Cer
tainly, as this is obvious with all software, you need to understand that,
with SAP 81 products, it can mean the difference between working and
non-working reports. ln this book, 1 used 81 Edge versions 4.0 and 4.1 to
create the screenshots.
The two main releases for 81 Edge in relation to SAP 8W that are in pro
duction use by companies today are versions 3.x and 4.x. The 3.x ver
sions are fully tested and mature within SAP landscapes. Version 4.x is a
major release upgrade with many new upgrades and versions that may
require extra work to establish functionality in a complex production envi
ronment. For example, you may want to review your specific requirement
for data services, which is a separate product and is fully tested with ver
sion 3.x. However, with version 4.0, there were initial limitations. With the
quick release of version 4.1 though the release 4 has reached a maturity
level that can be used in production.
lt is important to note that the entire SAP software architecture is going

through a major overhaul with the introduction of SAP HANA. Whereas
SAP HANA is technically an in-memory database, it is important to note
that the impact of this technology more or less touches all SAP products
including SAP 8usiness Suite, SAP 8W, and all 81 client toais. ln addi
tion, SAP HANA is the core technology for all cloud-related technologies.
ln essence, all SAP products will be related to SAP HANA at some point
as a main driver. You may want to consider this when choosing 81-related
technologies.
Therefore, instead of providing a list of versions that may be quickly ob

solete, 1 would like to further clarify the main strategic product direction,
which is relevant for the 81 suite. With respect to the above-mentioned
SAP HANA platform, there are many considerations.
96
CREATING A UNIVERSE IN BI EDGE
6.2 Universe versions
The core component of each 81 project is the connection and structure of

the underlying data sources. ln SAP 81 Edge, this is done via the uni
verses. ln essence, a universe structures the data connection from a
pure connection perspective toward a higher level that can be used by
business users within 81 client applications. 1 will go through an example
later in this chapter. With reference to versions, it is important to note
that, in version 4.x, 81 Edge introduced the lnformation Design Too/
(IDT). lt allows you to create a universe and save it either locally or on a
81 Edge Server. The IDT is a new tool that carne with version 4.x. lt
saves the universe with the .unx suffix. lt is not compatible with the older
universe format that had the suffix .unv (see Figure 6.1 ). Consequently,
when you come across the relevant tools, please make sure that you use
the newer IDT tool.
1 Define Business Model requirements
1 Connection .cnx
1 Data Foundation .dfx
1 Business Layer .blx
'-I _ n_i v_e_ r_

_Le_g_a_c_y_U _se ._u_n_ v_,
_ 1 Univ erse .unx
UDT IDT
Universe Designer Tool lnformation Design Tool
(Version 3.1) BOBJ 4.x and greater)
Figure 6. 1: Universe versions
97
6.3 Crystal reports versions
The most common tool for designing reports is Crystal Reports. Crystal
Reports has various versions, and it is criticai to clarify the relevant prod
uct versions so that you can identify the best fit for your project.
The classic Crystal Reports tool is Crystal Reports 2013, which is the
legacy upgrade from version CR2008. This version is intended for all
customers that have an existing investment with any Crystal Reports
related technology, such as vast amounts of existing reports or embed
ded reports with Crystal APls. This version is designed to use the classic
universe version from the universe design tool. lt is criticai to note that
the newer universe version is not specifically supported by Crystal Re
ports 2013.
The other Crystal Reports version is called Crystal Reports Enterprise

Edition. Here is where all the innovation and upgrades will take place.
This version is designed for enterprise-level integrations within the SAP
landscape, including SAP ERP tables, SAP HANA, BW integration, etc.
With regards to universe versions, the newer .unx format is supported.
However, it is important to note that this new Crystal Enterprise version
also supports direct table access against SAP ERP without having to use
a un1verse.
The Central Management Console allows you to configure the relevant

parameters for all versions, as it is the Central Management Console to
manage the relevant repositories.
One more comment about SAP HANA is needed in this context. There is
a dedicated version of Crystal Report with SAP HANA access. This is
designed to complement the traditional Crystal Reports 2013 version
(see Figure 6.2). lt is a separate version and requires that you implement
a Linux-based reports server to interact with the backend SAP HANA
system.
Now you should have a basic understanding of the relevant versions you
may want to consider. ln the next section, 1 will review the modeling as
pect and dive into some practical model design strategies.
98
1 Define Business Model requirements 1

1 1 Connection .cnx
1 1 Data Foundation .dfx
1
r------ ----- ----------- -,
[ Business Layer .blx
1 Legacy Universe 1 I
11
1
1 1 1 Universe 1
1 .unv .unx 1
1 1
1 1
1 UDT 1 1 IDT 1
Universe Designer Tool 1 1 lnformation Design Tool
1 (Version 3.1) 1 1 BOBJ 4.x and greater) 1
1 •1
1 •
1 BOBJ Server CMC (C ntral Management Console)
➔ Embedded security ➔ Co jiJure Common Services
1 ➔ WEf I rrocessing Server
➔
1 Legacy Universes � :1
Universe Repository
1
1
1 .unv Universes .unx
1 1 1
1 Crystal Reports 2013 1 1 Crystal Reports Enterprise 4.x
➔ Enterprise lntegration
1
1 ➔ Update for CR 2008 1
Crystal API support 1 1 ➔ HANA Connection
1 ➔ Legacy applications v�ith 1 (Ana lytical Views, Calculation Views)
1 ➔ Future 1
1 pre-existing CR integration CR Releases 1
1 ➔ Direct Access to SAP Tables
--
1
- -----------
1 1 1 _➔_ !! J!N � U�ve!;e �s� o�ID.!, 1
Figure 6.2: Crystal Reports versions
6.4 Repository and KPls
With the previous information provided about versions, you may start to
get an idea regarding the types of problems that are possible during
complex BI projects. What if the model design is suddenly running on an
obsolete platform? What if the data models and KPls need to span a
strategic timeframe and need to evolve as a collaborative work? ln order
to address these concerns, it is best practice to implement a KPI and
modeling architecture that is not as focused on the tools used but rather
on the KPls and models itself. ln order to achieve this, you can manage
the models in an independent platform agnostic framework that is not
99
tied to a single version or platform. ln this example, 1 will use BITS to

create this meta model (see Figure 6.3).
Define Business Model requirements
Lconnection Single Source SQL Connect ion ,---------------

BITS
- .� ➔ Preferred melhod Anatysis View ➔ Bootstrapping Query Modai s
lnfoSel
1Data Foundation .dóc l ➔ Sales Performance
➔ Logistics Performance
"'
Data Preparation
ror business usar Data Model ➔ Web lntegration Perfomiance
lsusi ness Layer
strate,gie
�
Tab leViews
.•
'- KPls
1 Universe
Direct Table Access
.unx 1 . Ol)&Iat!onal
Ad-Hoc Star Schema
➔ Facts (Transaction Data)
\ --------------
➔ Dimensions (Master Data)
IDT ➔ SQL Server, Oracle,...
lnformabon Design Tool ➔ SAP TableAccess
BOBJ 4 x and greater) ➔ SAP BAPI lntegrat,on
BOBJ Server CMC (Contrai Monoeomont Console)

➔ Embedded security ➔ Configure Common Services
➔ WEBI Processing Servtr
1 Direct Access
➔ Universe Repository
1
�
Universes .unx \
BI Client Toais
➔ Crystal Reports WEBI Office Anatytics
•
Figure 6.3: Data model considerations
6.5 The present state of BI technology - A criticai perspective
ln this section, 1 would like to comment on the SAP overall product portfo
lio as it relates to BI. A key problem with SAP products in the past has
been the notorious complexity of the SAP Business Suite and related
technologies. Users often complain that the products are counterintuitive
and require technical training to be usable. 1 mentioned the shadow
theme earlier in this book to showcase the hidden problems that live u n
der the surface but are nevertheless obvious to the informed consultant.
When I review the current state of BI as it relates to the SAP landscape, 1

see a similar trend. ln the previous chapters, you learned that many que
r y -related tools in SAP are already built in to the core system. Due to the
vast amount of data and previous industry trends, SAP BW was estab
lished. lt contains BW-specific lifecycle management services and re-
100
quires that data be loaded overnight in arder to be consumed by report

ing applications. The BW concept from SAP largely relied on lnfoSets.
The lnfoSets are designed to address the needs of analytical star sche
mas. BW also provided an easier way view to the master data and trans
actional data in SAP without the need to understand the underlying table
relations, which are highly complex.
However, for the average power user, these concepts often lead to frus
tration. lnstead of getting them to the data, it required that a new BW
landscape be implemented. Furthermore, the architecture and thought
concepts built into these solutions required a vast infrastructure.
lt is interesting to note that, with the latest BW releases, it is still required

to use ABAP in certain scenarios to simply join tables. ln addition, it is
only possible with the newest releases of BW to actually use common
SQL toais for reporting.
However, in arder to get there, you need to join the huge BW transition
towards SAP HANA. This transition simplifies the complex data loading
concepts and takes advantage of the extremely fast performance of SAP
HANA while keeping proven BW concepts in place. While this transition
is working towards a simpler BW concept, it must be said that it some
times appears complex for no reason. For example, the new composite
provider object allows users to connect to SAP HANA, which in return is
connected to a BW system, which generates the required schema in
SAP HANA, which is dri ven by BW based on the proven normalized SAP
data models. lt is a simple concept, but it gets complicated when you do
so much to keep the traditional BW alive.
lf you followed the concept in this book about transaction code analysis
and the automatic generation of table schemas, you may understand
how this may be handled in your own project.
ln the future, 81 architectures should be designed to address the needs

of the organization and only then use the technology to leverage the
concepts. For example, consider the following criteria:
► The data model is a company asset and should be designed to

achieve the target industry KPls and custam KPls to measure
business performance.
► The data load processes should be minimized because, with
more and more data being produced, it is not reliable to load da
ta into a BW system for analytics.
101
► Smart data streams should provide meta information about the

data. This would allow 8W systems to use analytics that are built
into the data stream prior to loading the data.
► lntelligent data models should consider the way the data is being
used. For example, build a version into the data model as well as
information about the target systems that can consume the data
presented by the data model.
Let's now take a closer look at the current SAP 81 architecture as it re
lates to 8W and SAP HANA. You can use this information to design your
own models. The core question you may have is: How do I get the data
from SAP, 8W, or SAP HANA within the current concepts provided by
SAP? See Figure 6.4 for an example.
Business Model Lifecycle with HANA and BW
➔ Sales Performance Meta Data Model

➔ SAP TcodeAudit r---------------
➔ Web lntegration Performance ➔ Custom Data Model
BITS Model Repository
➔ lndustry KPls Data Model ➔Platform agnostic

➔ Custom KPls ➔Analytic Semantic Layer
Company Model ➔Logical Data Warehouse
➔ Strategic, Operational,Ad-Hoc lntellectual Property ➔lntelligent Model concept
(SQL Access, Predictive ➔Model Versioning /Archiving
Llbrary Access)s ➔Strategic company assei
➔Analytic KPI Modelling
._ _______________
How to access SAP BW, HANA or 3rd Party Database?
SAPBW HANA SQL Data bases etc ...
Figure 6.4: Business model lifecycle with SAP HANA and BW
ln Chapter 7, 1 will review the details based on the current release levei
of SAP 81 8W and SAP HANA.
102
6.6 Connecting to BW, SAP HANA, and others
When you design reports and data models in the context of SAP, you
may have to consider SAP BW and SAP HANA. However, these technol
ogies are complex, and SAP HANA is being updated constantly. There
fore, 1 will provide a current status update about how these products work
together in a fully implemented SAP landscape where you find SAP ERP
with BW and SAP HANA.
There are many new objects in BW and SAP HANA. However, 1 would
like to focus on the core objects that are relevant to understanding the
essentials.
With the new BW release BW 7.4 SP8, you get the composite provider.
This object will supersede the previously used lnfoSet and MultiProvider
in BW. The composite provider allows for an inner join or left outer join
against lnfoSets. ln BW, the DataStore Object generates SAP HANA
views. Essentially, the data in BW is now transformed into SAP HANA to
take advantage of the built-in performance and analytics libraries that
come with SAP HANA. This means that you can run queries against mil
lions of rows and get your data almost instantly. lf you have ever created
a query against a table with millions of rows, you know that performance
is a key success factor in BI.
From an architecture perspective, the way the query is running on the

lower SAP HANA or BW levei is managed by the BW Analytic Manager.
The BW Analytic Manager orchestrates and prioritizes the order of SQL
execution down to the data levei. For example, if you have multiple KPls
and they must be executed in a particular order to address dependen
cies, Analytic Manager handles this automatically. See Figure 6.5.
ln summary, if you want to add your own queries, you may want to use
the composite provider object from now on.
103
Business Model Lifecycle with HANA and BW
Meta Data Model

➔ Sales Performance
➔ SAP TcodeAudi1 r---------------
➔ Web lntegration Performance ➔ Custem Data Model
B ITS Model Repository
➔ lndustry KPls Data Model -+Platform agnostic

➔ Custam KPls -+Analytic Semantic Layer
Company Model -+Logical Data Warehouse
➔ Strategic, Operational,Ad-Hoc lntellectual Property -+lntelligent Model concept
(SQL Access, Predictive -+Model Yersioning / Archiving
library Access)s .+Strategic company assei
�---------------
.+Analytic KPI Modelling
-
BW Analytic Manager Composite Provider
➔ Orchestrates data retrieval sequence ➔ Main Object for unions and joins �
➔ Eclipse based
Advanced D�aStore Object ➔ Supersedes MuhiProvi der and lnfoSet (i n BW concept)
Open ODS View ➔ Join of lnfoSets
lnfoCube ➔ Should be used from now on ➔ uses BW Schema within HANADatabase
Composle Provider
SPO ➔ High-Performance
SAP HANA V iew
SAP BW 7.4 SP8 ! !

➔ BW incorporates knowledge al>outlransactions and Master Data HANA
➔ LifeCycle Management Smart Data Access Layer
➔ BW OataStore Objectgenerates SAP HANA Views ODS Views (V irtual Views)
➔ Open ODS Views integrale BW and HANA as Virtual Layer Data Store Objects (Persistent Layer)
Figure 6.5: SAP HANA and BW integration and composite provider
6.7 Creating your first universe
The universe should be designed with the new information design tool
(IDT). You can use the cheat sheet in the IDT to guide you through the
steps to create a universe (see Figure 6.6).
The goal of the universe is ultimately to shield the query and data collec
tion complexity from the user who will use the data within an analytics
application. The universe also includes embedded corporate security
concepts.
104
Jnfot'matton Dr-.1gn Toni

f4e Edil Wlndow �
,e. ' 1 J " J t!.Íi' ]Íc@ él J �:ti

i1 Local Projcrts'i
X
J =o =o @wekome�
19 � � fi'l R\tit(lrt WdcO!!t
o 1ft 6t
Create Your First Relational U n iverse
► Introduc.tion
► l Cteate alocalpr()je(t
► 2 Cteate a,.elabonal ccn�t,oc1
► 3 úeate adata fosdation
► iúe4te obusnessla)'Cr
• SPublishthe-se�
► FormorerionnabQn...
-
c0 Repository Rcsouc:es t:3 =o
;), . ,, 11 , ) e,
Figure 6. 6: Universe cheat sheet in IDT 4.x
Using the steps outlined in the cheat sheet, you can start to create a pro
ject and then define the data connection. This will be a connection to a
SQL database, BW, or SAP HANA, for example. Following SAP best
practices, a single connection concept should be used against a prede
fined data model. Then, you continue to define the data foundation. This
means that you select the tables and columns within your data model to
define the data foundation layer. Finally, the business layer takes a sub
set of the data foundation layer and makes it available for the specific
user to prepare a report. Now all of the required layers are implemented,
and you can save the information as a universe. The universe can be
stored locally or within a BW server where other users can access it if
they have the appropriate privileges.
105
6.8 How to create a universe step-by-step
Following the cheat sheet, 1 will start to create our first universe with a
new project called Espresso Tutoriais. AII of the relevant layers will be
housed in this project. AII of the configuration in this project can then be
published as a universe.
Next, create a connection. ln this example, 1 will call it SAP ERP CONNEC
TION. See Figure 6.7.
lnformatM>n Oe-'"911 lool

E ldow heb
• ,
_,_;:.--=-----.----- =�==:-:;El=-X J ,.. J�ÍY Jfci à G 1fl
= El l�wekome 13I- - ------------
--,
Q
Create Your First Relational Un iverse
► Introduction
► 1 úeate o localpro;ect
• 2 Cre.Xe o rel.otioMI comedion
File> New > RelatK""'-' r""',.,_.+1,,., TI-.• ,.1 ,.......,_,..i ............,........., ........,►......, ..._ ;,.S,.,,....,p-......, �•,r,•n• h-. ...,.......,.
create a relatlonal e ff
New Reldhonal Connectlon l!I ■
Resource Nome
!rter a Nme for t;he resou,ce.
► 3 Create a dota f<
► ,. Create a busne:
' s.,._ thou,,1,,.
► For more irlormat !J Descl"()tlOn Connect to SAP System D i,ectly
c:fJ Reposiory Resou-ces t:!

0
O
◊ • / iíl � x e,
•
��
�
<Ba::k N e:xt > Anlsh Carxel
Figure 6. 7: Universe create data connection
You will then see a list of the various data connections supported by SAP
IDT (see Figure 6.8).
106
� New Relational Connection l!I� E!

D11t11b11se Middleware Driver Selection
Select the driver for your database middleware.
r. Hierarchical List r Flat List
IJ..$· C Hewlett Packard

$..,[J HSQLDB
1$..,[J IBM
1$-C Ingres
1$· C Microsoft
$·C Netezza
$.. C Oracle
$.., C PostgreSQL
$.., C Sa lesforce. com
S· C SAP
1±1 1) MaxDB 7.7
gl O mySAP ERP 2004
gi O 5APERP6
gi. . (l SAPHANA database 1.0
�... t] SAP R/3 Release 4
i+J... C ,vh�<P.
_
_
<Back _
�
_ _ _ _
�ex
r t_>_ J I
_ _
finish ! Cancel J
Figure 6.8: Universe data connection source selection
Once I have the essential data connection, 1 will define the data founda
tion. The data foundation is based on a data connection. This means 1
can select the objects I want to use at the data foundation level based on
the data connection. ln this example, 1 will use the predefined models in
the connection for extracting ecommerce products from SAP All-ln-One
(see Figure 6.9).
107
=- :._v--= ::=:tEl I
i1' Jnformation D�s,gn Tool
F e Edlt - lielp
:....• ' j N IL(i' j[dj à J '; iffl

X
-■-■--
�\■-....
-.. ,-
-__2-
ifll11
:-
- _=-
� :.. '4 SAI' ERPComection.cnx l::l !
O
':: .,_ ____________
___
___e1_,_
_ _,
e,
-t l
:J, Genet-al Inlonnat1on)-_q;__Show_v_al_ue__
s _ _ _ _ _ _ _ __
_ _ _
_,
& 1) Espresso Tutoriais _ ......,
-··!!. SA? ERP Comection.cnx
Resource Narne
Ent«a name for the resou-ce.
Gel Material Item lnformatl onl
s) • .I ct:I ft3 "'

d! Repository Rosourcos !3
<--
�
-
Next > lnlsh Cancel
Figure 6.9: Universe create data foundation
Per SAP's recommendation, select the single source option (see Figure
6.1 O). SAP recommends that I choose a single source connection based
on a predefined model.
i) l'lew Data foundation 11!!1� EJ
Select Data Foundation Type
Sele c ta data foundation type based on the features supported by each type.
(.' 5ingle 5ource

- Single connecti on
- Database-specific SQL syntax
- Universe to be publ ished locally or on secured server
r Multisource-Enabled
- Single or multiple connections
- Additional relat ional con nections: SAS, SAP NetWeaverBW
- Standard SQL-92 and SAP BusinessObjects SQL functions
- U niverseto be publ ished on secured server
< Back ! Next > !_ _

F_i ni_ s__
h _, _ c__ a n_ ce
_ _....
l_
Figure 6.10: Universe new data foundation se/ection
108
Choose the relevant tables (views from the predefined model) and save it
as the data foundation (see Figure 6.11 ). 1 have now successfully estab
lished the data hierarchy and can provide selective access for business
users to consume data foundations based on their needs. Therefore,
instead of offering the full data connection, 1 am offering a predefined
data foundation with preselected tables, views, etc. for the business user.
This makes it easier to work with complex data because the business
user can focus on the current task versus having to browse through the
complete data available in the data connection. This also provides the
essential foundation for security concepts.
;.umrmxm,w• mmm
Ne C:dt � Wrdow .-
1
X. ",f1.i1 ,a}
--<I
r"l - , .J � 01!1-=-
e v e> 0 .à.WDU'Comedl::n,ou;
"" ......
""
:-=-i
.�Ka!it�
"Í'l-«4'""-ieoeO f3 = ::-:-4'< .____________________
,_
o
.i. , {J C�ion
-1;>
·A
-
s.1. ...
li!� tAOIR
"i::: z..-....
-·
® :'i l
Jll.Ot«
. .. . .JR
.......
@ :. l.,Jl!<M...JJJ
�?-��"'""
.....
f!l
.....
81 � l.Jllr»<..00..6'U
(4;
� l.,Jll<M..JD,._dul..,._.JU!bl'
e:�o,. • I 'V'()l',I OJDot.........,uo.. 1 '"" ....,
""""
@ :;>z.JClO'E_O,t�
� � l._Hleli<._0,.�_,.. '""'
,.,,
""'"
.,,.,
l!l�
ai
;_! l,J0N...OIS
Z.jll(H,,.0.-.)014,.«JM ...,,.
"'°"' ...
vw
r- ' � l_NiZO<_O...O-llillt
•;ri l.,Jll<M.
..
_ eHet
�.,lâlJt..-p•..-,,.
""'°'
"'°"' .....
--"'i
IHCOI
...
--
[f ':" t.J®'C_�.>#"""-�
(t, l!I ..c.at.Allt..
l..J,IZU«:
�� j,('IM,-., • •
� °;tl:,.JCl'tNLOOAl:tteim.J)Mln(L
l'!i .;"'i ZJOOIC...�ftwl
• � l.,NZ(IIC,.GII.Mll .....,..._
• ._, �Glc.Alli....J,MMNN•
• !" lJQIC)l«,.c..tA&IWIMJ...
. ei l..)llOH(..Otótf.C.,,,. o ••ct-,,M•
. t: ,.,.,....___ .s f411JO,,,,,.. �---------
• � l.J«-C..CWIIJ.N l!MM
• � 1.)CO#I._Otéa� ..c,e.,..,
o
(<t.l� �-Orda,._-...ro
...._ ·_•_ __
- _ _ ___.f
6t,� l.Ji2'CIII<..��
Figure 6. 11: Universe data foundation e/ements
Finally, 1 created the business layer on top of the data foundation (see
Figure 6.12). The business layer is the leve! of access that the business
user will have. For example, a business user can utilize SAP Lumira or
Crystal Reports. Based on the connection credentials, the user would
have access to the business layer to consume the data within the securi
ty context of his or her profile. The business layer can be based on a
relational data foundation, which is the case in this example, or it can be
based on an OLAP connection.
109
� New Business layer l!I� Ef

Select lhe type of data source for lhe business layer.
Create a business layer from an existing data foundation.
1
R elat , ona l Data Foundat ,on

OLAP Connection
! < Back I Next > j Finish j __c_a_nc_e_l__,
Figure 6.12: Create the universe business layer (step 1)
Once the business layer is saved, 1 can assign specific properties to the
queries that will be used to present the business layer data (see Figure
6.13).
;J New Business layer l!I� Ef

Resource Name
Enter a name fo r the resource,
I
(i Resource Name eCommerce Products
3 Description We will choosethe MARA MARM Data Model l ...
__
<_B _a_ck _
_
_ N_ex_t_>_
�
j l Finish
! Cancel j
Figure 6.13: Create the universe business /ayer (step 2)
110
1 would like to point out a criticai setting. lt is called the ALLOW QUERY
STRIPPING checkbox (see Figure 6.14 ). lf you have complex queries, it
may be that you do not need to run all the subqueries to present the re
sult. For example, if you are using certain grouping levels, you do not
need to run all the queries to get the details.
r-=
1
=,..
i- Busincss Layer
.... =--===-
<> • � • J!I
e· ; cCommetce Prock.Kts
l@
� Busi ncss Lay� eCommer ce Produrts
�-,;;::-11.-'-_,,'--
.:.1
u3,,,_,.,J<N,,y0otionsl Corrmcrts CI.Gtom Propcrtics

_ _____ _ _ _ _ _ _ _ _ _)
!tifli ?N2oneGetAlltemsOist· -Queryi..Ms
f7 l>M.,..,<esUt setto j50CXl 3 "'"' r Wl./tn icost estmal:$eocceeds 1 ::J mR.tes
1'º ..:l
...J
P li'ntfOO!CIAiOf'Itn.e to _,, mh.Lts

Quo,y-
f7 A1owused subQueries p Alow�x operand5.-. QueryPorei
P A lowuse dU"IOO,,ntersec tanel fl'ftJSoperators P �SQlstat�fore«h�
r Alow qJCI')' str iwno

1
t -L� - •�
-
Jis Doto FoundM:k>n: /C.JptffJO 1!A.0t1Gls/MARA MARM.dftt
rf§'*'IMi4i lilin/ll@ll§j,
Figure 6. 14: Universe business layer option query stripping
When you select ALLOW QUERY STRIPPING, the system will automatically
use only those query elements required to present the result needed for
the report design.
Please note that, when you create a universe and utilize the universe in a
report, certain services are employed to execute the required processes
to present the report. You can configure these processes in the CMC. 1
will not go into detail on this topic but wanted to mention that these s e r
vices can b e configured with the CMC.
Once you have your universe elements configured, you can create a
query and run it to see the result. Create the query by dragging the re
quired columns to the right side as shown in Figure 6.15.
111
E!
1)�Tutonds
� eeor-e.-ce PtocMts.,bb:
1-�MAAAMAAM.«x
r 1� 9 - -....
fa. SllPOI PConnortlon.au "i' univcue: cCommc,cc Produtt., (J.l Rc,utt oti)ttb for C)ucry ••
�- e, .'Jí X ti
e-
,..,l�=��- - - - -
__j
r. lt«'M�h:t
, .11111.,,.,-
- �
,
Kr,...nt. t:i.nv ' �,
Quc,yFilttt for Quer-y#1
.'Jí >< 'JI �
- Rc:fu:-,hln9-(omln,o�)
1cíl-•-� !:![ o o
..) • /ál'éX �e ,
()O( 1 ao..
1
-
-
- i
'----= -----,l
Figure 6.15: Universe query
ln the next section, 1 will review some design principies you can follow to
make your universe design project a success.
6.9 Planning your company's universe strategy
Designing a customized universe strategy can be complex. However, it is

only complex if you do not plan properly. 1 may add that a model is more
useful if it is simple enough to be understood by the core users, and it
can only be expanded and improved if it is in a solid simple state. ln oth
er words, if your model is complex, you need to simplify it. The hier a r
chical concept of the universe design process can help you with that.
When you create a plan for your BI reporting project, you may take a
step back and define the requirements and goals independent of the
tools you are planning to deploy. As you can see with the SAP BI tool,
there are many changes and updates. Your BI strategy and models,
though, are of strategic importance to the extent that you can look at
them as a key company asset. Therefore, you may consider modeling
your required data models using standardized techniques prior to creat
ing your first universe.
112
lf you have SAP BW in your IT landscape, you can leverage existing ob
jects based on master and transactional data. However, especially in this
context, it is key that you do not get confused by the concepts offered by
SAP BW but rather establish your own data model and goals for KPls.
When modeling the data, it is a good idea to integrate metadata into the
model design. Therefore, instead of just modeling the plain data, you can
add information and version information about the data you will retrieve.
This can then be used to build a hierarchy of models that exchange meta
information.
This concept will be further explained on the GitHub site

(www.niefert.com) where the core set of SAP queries are collected for
transaction and master data management.
With this concept in mind, you can then follow SAP best practices in a r
der to best use the available toais.
1 will now summarize your project checklist.
Strategic reporting guidelines
► Design independent of the modeling toai.

► Design with an intelligent data model in mind.
Best practices for universe design
► Single source.
► Query stripping.
► Use the composite provider for new connections.
► Understand the architecture from model to connection and data
base (SAP ERP, BW, SAP HANA, etc.).
ln the next section, 1 will provide further information about the upcoming
SAP Data Model Project available in GitHub.
6.1 O SAP tables and data model repository on GitH ub
When you create queries against the SAP ERP system, you can use a
combination of transaction code analysis and related toais to identify
tables and ultimately create your own query collection. During many
113
years of work with SAP systems, 1 have defined a core collection of table
descriptions and queries that you can use as a starting point. Those que
ries are published and updated in a GitHub repository. The link to this
repository is available for ali readers of this book upon request during the
first publication phase.
Figure 6.16 shows the initial concept of the SAP GitHub query repository.
lt started as a collection of tables in Excel and evolved into a set of es
sential queries.
ln combination with BITS, 1 created an SAP query model collection that

will be hosted on the GitHub repository. The GitHub project information
will be updated on the website www.niefert.com.
Wl•blrUfH hctl
Otvt ope, INS[RT PAGELAVOUT FORMUlAS OATA RlVIEW WW V.tO!f,c.e AOO•INS POWCPJ'IVOT SAPl11111\n•8y0ti,,n TlAM
l
�J [ _./[
�, -,-,.- r: ir
G.,,.,. [ Nonnll 8•d
•
f},, iJ,W11plt'.(t
Ptstl
!l!e.., . a r u• + ConcM, oiwl fo,m,t fl GOlOd
• "fo,m,t P�ltr
+ ��9,&C,n1t1 • J • � , •J :g lMt11
Fo,mt111n9• 1.-1 ..
r. ''"'li r. r. r. Styln
L14 • ! )(. � ,
..
H K L M N o
2 Tra,u.port.11fon S.O Copy Control Table1 so n,m C;i1,cori.s Copy Controt Tab lu SOOocum.nt Schtdv ,lln• c..1,,ori.s Copy Contr ot TablH
l
3 VTTK TVAK TVAPT TVCPA
O VTTP TVCPA TVCPA
S TVRO TVCPf
6 TVTK TVASP TVCPl
••
7 VTRLI< TVCPf
lV(Pf
TVEPZ
TVLP
rvn
B llln gO O<um ents Copy Contro Tables
l
TVCPf
lVfSP
l
10
11
"
12 Oeli wr yooc.u:menh Copy Control Table1
Tl84t
1A
lS
1 • TVCPF
TVC:Pl
16 TVlSP
17
18
soUnk1 to fl
,.
19
KNVP
Zl KNVV
22 KNVO
23 KNAl
24 KN81
zs KN8S
Z6
21
ze WUnkstoMM
,.
Z9 t,'1ARC
MVKE
r, rSD MM fl MR PP PS W, lrthek1s e M ,l n.1gttne111 QM @
Figure 6.16: SAP table documentation
114
6.11 Summary and next steps
ln this chapter, 1 reviewed the importance of 81 product versions. You

learned about the IDT version for universe design. ln addition, you
should now understand the different roadmaps and versions of Crystal
Reports and Crystal Reports Enterprise.
1 also discussed the strategic importance of modeling as a tool

independent task. However, a reporting project is always embedded with
in a specific 81 infrastructure. Therefore, we took a closer look at the l a t
est integration scenarios for 81 with 8W and SAP HANA so that you un
derstand the importance of the composite provider. You can therefore
use the right tools when you run a new 81 project.
Finally, you learned about the new SAP GitHub project with information
about queries and tables in SAP. This will allow you to bootstrap your
query projects efficiently.
115
7 Publishing reports and dashboards
We have reached the final chapter of this book. During the course of
the book, a technological and conceptual platform for reporting in an
SAP environment has been built. 1 tried to keep the business user in
mind, the one who just needs to get a report done. lt is a traditional
problem in SAP that you need a team of experts to perform even
simple tasks. Today the challenge persists because it is a matter of
fact that you often find yourself needing a quick report that has not
yet been created in the SAP BW infrastructure. ln the beginning, 1
focused on the existing tools built in to SAP R/3. 1 also reviewed the
technical background to access tables directly. With these tools, you
can complete many reporting tasks.
ln this final chapter, 1 would like to conclude based on the infor

mation provided that there is a middle ground. The educated user
could leverage the SAP reporting infrastructure if it exists but can
also ramp up a quick report. lnterestingly, this is in line with the lat
est SAP B1/BW features. These features are focused on agile capabil
ities, which means the business user can leverage table and report
knowledge within a SAP B1/BW landscape.
The takeaway from this chapter will be a clear understanding of the rea
sons why the SAP architecture appears to be rather complex. As it turns
out, there is a reason for the tyranny of complexity imposed on users by
SAP. ln simple terms, when you report on millions of data records across
different geographic regions, things are different compared to ad hoc
queries and require a hierarchical solution architecture like SAP 8W and
SAP HANA. This architecture allows for integrated delta management of
data, integrated security with selective access, and embedded 8W ser
vices. ln essence, those topics are all key factors for modern dash
boards.
Refocusing all those aspects to the core topic of dashboards, in this

chapter I will establish the state of "81 Dashboards." This will be achieved
by clarifying the evolution from static graphic-oriented dashboards to the
81 Application. 1 will define the core characteristics of modern dash-
117
PUBL!SHING REPORTS ANO DASHBOARDS
boards. ln arder to understand how to connect this knowledge with the

SAP BI and BW platform, 1 will look once again at the smallest unit of
reporting in SAP B1/BW. 1 will review the latest updates available for SAP
B1/BW as they relate to agile reporting and dashboard design. Therefore,
instead of designing a demo dashboard, 1 will assess what is "under the
hood" of a successful dashboard, the smallest units that allow you to drill
down to a detailed level when a graphical representation triggers your
interest. You will then be able to design a strategic dashboard platform,
one that can sustain modern requirements from visual analysis to drill
down with detailed information down to the smallest unit of information.
7.1 SAP dashboard evolution
The demand for dashboards is increasing. The SAP portfolio includes

various products that can address this market need. 1 will briefly review
the most prominent candidates and will point you in the direction I believe
makes the most sense to utilize for your custam dashboard projects.
The top candidate for dashboards used to be Xcelsius. This tool allowed
users to work with an Excel-type sheet to organize data and then publish
it in a Flash format. This had pros and cons. On the pro side, it allowed
you to create flashy graphs, but with limited backend data integration.
Xcelsius also allowed you to utilize web services as a data source to
drive the graphs. This was a nice architecture because your data design
was driven in the right direction. This is true because, as you will see,
publishing data in a web service format is still the method that I recom
mend for your dashboard design. However, Xcelsius had many limita
tions due to Flash. ln fact, while Flash is available on many platforms, it
is not very well-accepted as a business technology.
The current evolution of visual representations in the form of graphics for

a dashboard is called Lumira. This solution fully supports HTML5 and
related technologies such as JavaScript. ln addition, Lumira has some
key design elements that make it a preferred application for your dash
board projects.
First, Lumira is highly integrated with SAP HANA. This allows you to not
only create dashboards that perform extremely fast but also enables you
to drill down to data with a high level of performance.
118
PUBLISHING REPORTS ANO DASHBOARDS
Second, Lumira has a built-in SDK that allows you to add your own
graphical representations using the D3 graphics library. For this, you can
use the Vizpackerr tool, which allows you to package your integration for
Lumira.
Furthermore, you can use JavaScript and CSS style sheets to format
your Lumira applications to your preferred style.
Lumira is available as a standalone application or as a server edition.

Then, you also can use the preconfigured Lumira cloud. As you will see
in this chapter, the true value of a dashboard is the tight integration with
the backend data. This means that all the participating layers of data pro
cessing and formatting have to be integrated properly. Since Lumira and
SAP HANA are two applications that are very rapid updated and patched,
it may be worth your while to choose the cloud-based offerings. This way
you do not have to worry about version difference.
Finally, you may want to review a product called Design Studio. This may
very well be the central application for business users to design reports
with dashboard character. For example, you can copy a Lumira graphic
into Design Studio using smart copy and paste. The pasted object will
maintain its ability to be edited.
With this quick product overview for dashboards, 1 would like to end this
section and will only summarize as follows: use Lumira alongside Design
Studio and design your data based on web services. lf you have a SAP
backend, then leverage the SAP HANA integration options. This is a brief
recommendation, which I think makes sense at this point.
7.2 Key aspects of a successful reporting and dashboard

strategy
One important thing to keep in mind as a consultant is that you should

not get carried away with new products and technologies. lt is of prime
importance to keep the user in mind. When you design a solution, you
must consider the specific user environment and business role that the
potential dashboard user faces.
The user needs to get the results quickly and easily within the current
work environment. ln addition, the user will not like constraints. For ex-
119
ample, if the user commonly works in Excel, then the dashboard may
require Excel integration.
ln order to achieve this, you may want to schedule user testing with
feedback during the early phases of the dashboard design.
The modern user expects to use a dashboard like an application. For

example, when a graph triggers a spike, the user wants to drill down to
see the detailed data that caused the spike. This allows the user to find
relevant data for their purposes. This may very well be the core feature
you are looking for. Data and graphics must be relevant. The new para
digm of analysis applications integrates the core features mentioned
above for dashboards. ln summary, consider the following key aspects
during dashboard design:
► Design for the user not based on technologies.

► Use technologies only to leverage the user requirements.
► Present relevant data and graphs.
► lntegrate with the user workflow.
► Allow for data drill down to enable the user to self-service.
7.3 The smallest unit of reporting in SAP BW
lnstead of creating a demo dashboard, which you can find elsewhere on

the SAP demo and tutoriais sites, we can benefit from looking at the oth
er end of dashboards, i.e. the smallest unit of data that drives the
graphics. How d o you best configure your data backend to work properly
for dashboards? Remember that I recommended that you allow for drill
down to enable a modern analytic application. The detailed data is driven
by the smallest unit of reporting. This smallest unit of reporting is called
the lnfoObject in SAP BI and BW terms. lf you thought that it was a table
column, then read on to understand the difference.
1 would say that the lnfoObject is the core design parameter that gives
the SAP BW reporting architecture its value, but also its burden. For ex
ample, when you need to add a simple column to a report, you may
wonder why you cannot do that by design in SAP BW. You have to add
an lnfoObject that will define the parameters for this column. Then, these
parameters will drive the way the data in this column is treated within a
cube. While this is good, it also creates a lot of overhead. lf you want to
add 100 columns, then you have to go through a lot of detailed work to
120
make it happen for the lnfoObject definitions that are required to accom
plish this. Let's look a bit further at what makes up an lnfoObject.
ln order to define an lnfoObject, you review a field and assign it a type

with certain properties. The type can be a key figure, for example. The
property in this case could be aggregation. lnfoObjects add this infor
mation to a field (column) and can then be used more intelligently by
subsequent data processing layers as compared to a simple column. ln a
modern BW architecture, the lnfoObject would be used in Open ODS
views (virtual views) and ADSOs (persistent data representations). Both
of these last objects, the Open ODS and the ADSO, are new objects in
troduced with SAP BW 7.4 SP08. That is why I will review those new
architectural changes introduced in BW at this point. Whatever the object
used to process the lnfoObject, on the top layer, you have your dash
board technology using Lumira, but you also have the BEx queries that
will query the data using the additional parameters available in lnfoOb
jects.
Since the lnfoObject is a key term, 1 will define it and provide an explana
tion.
What is an lnfoObject?
The lnfoObject is the smallest entity in BW.
How do you define it?
You define the data in an lnfoObject by means of types and properties.
What is a type?
Field-level semantics are types. For example, key figures and character
istics. They are used to drill down in reports. Types are also multi
dimensional semantics and include facts and master data. They are used
for aggregation.
121
How do you use lnfoObjects?
You can use non-persistent and persistent representations. An example

of non-persistent is ODS views. The ADSO objects are an example of
persistent representation.
7.4 The SAP BW platform evolved -AGILE
Traditional SAP BW architecture suffered somewhat from the overhead

required to accomplish simple tasks. The new BW version released with
7.4 SP08 introduced some key updates that address the needs of agile
users. Most importantly, the issue mentioned in the previous section that
required a user to go through heavy overhead to define lnfoObjects was
improved by giving the user the ability to add externai columns to preex
isting SAP BW reporting objects. Therefore, there is no longer a need to
define lnfoObjects. ln addition, when defining complex BW models, the
user had to define complex star schemas with aggregation tables and
dimension tables for lnfoCubes. This was required because the architec
ture was based heavily on extractors that would read the data from the
source and would then pre-format the result set into a specific BW data
base. This required a lengthy procedure. Virtual providers and MultiPro
viders are examples of this. They can connect to specific data sources
and then pre-extract the data to use in BW.
The new objects introduced with BW as of version 7.4 SP08 are simpler
and more powerful because they leverage SAP HANA. ln this context, it
is also important to mention the Open ODS view and the ADSO (Ad
vanced Data Store Object) along with the composite provider. They are
the core objects I recommend for your reporting. You may ask, why is
this better and more agile than before? The answer is in the SAP HANA
architecture and its speed. SAP HANA as a database platform runs the
data in memory and, therefore, does not require that vast amounts of
data be pre-extracted in tables for later analysis. SAP HANA allows you
to present the SAP extractor data in memory and enables the user to
combine this data with externai tables and columns using the Open ODS
view or composite provider. Furthermore, SAP HANA has built-in libraries
for analytics and forecasting. Hence, data processing is pushed down to
the SAP HANA technical level and enables high-speed performance (see
Figure 7.1)
122
My recommendation for your dashboard reporting project is as follows:
► Use the latest release 7 .4 SP08 for BW.

► Leverage the Open ODS view and composite provider.
► Use SAP HANA libraries for analytical data processing like fore
casting and complex analytics.
Traditional BW pre 7.4 SPOB release BW Hierarchy New BW 7.4 SPOB

Non-Agile Process Chain Agile
◄ Web Service APls ►
BEx WEBI Crystal Reports Xcelsius Office Analytics Lumira Lumira Cloud
BEx Query encapsulates OLAP
loglc built lnto lnfoObjects
Attributes
H i erarchies
lnfoObject
Currencies
SUM or MAX lnfoProvider
Non-Persistent
Virtual Provider (Non-Persistent) ➔ Open ODS View
➔ ODS (Access to externai sources)
➔ lnfoSet, Transient Provider, Virtual Prov ider, Multi-Provider ====== ➔ Composite provider
Persistent Persistent
➔ DataStore Object, Hybrid Provider, lnfoCube ➔ ADSO (Persistent and joins)
➔ Semantically Partitioned Object Traditional BW Model - ➔ Replaces DetaCubes and alows you to use HANA
Complex Star Schemas Predic1lve and OLAP IJbraries (Corrency recognmon)
➔ ADSO is l 1ke a matenalized •-
Aggregation Tables
Dimension Tables
' 'v' Push Down
� ---�
-
lnfoCube
HANA
➔ Predictive Libraries
➔ Logical Warehouse
➔ Converted Star Schema into nat data model
1
Figure 7. 1: SAP BW transition to agi/e
1 have now looked at the lnfoObject as the smallest unit of reporting and
how they connect with SAP HANA. ln the next section, 1 will review how
to best publish data so that it can be used in dashboards.
7.5 Publish the universe for a dashboard
You now understand how the smallest unit of reporting traveis via SAP
HANA and can be used alongside externai tables to enhance your report-
123
ing data. The universe can now be published using the Query as a Web
Service toai that comes with SAP BI.
When you open the Query as a Web Service toai, you can create a new
query and select a universe as a source to generate a web service from
the universe (see Figure 7 .2).
Web Servkr. Wlzard EJ
Defino tho Wob Sorvacos proporties: Web Service n4me, sorvioo nome in iho WSOL, and tho
descnptaon.
leComcc.._.........,
\Veb s-o-
PI......,• kl d-� lo! eComme,00 Sale •
..:J
c.nc.i 1 Hock 11 Nexl >
Figure 7.2: Query as a web service
When you follow and click through the wizard (see Figure 7 .3), you see
that the universe created does not appear on this list. But why? Please
note that this exercise is designed to highlight the core architecture of the
BI suite, which is BI services and the CMS repository.
124
,l,f:Publish Query as a Web Service Wízard EI

• 2. Select a universe r evi w
Select � universe on which to build your Query.
Fokler Unive1se name • Desc · lion

Universes efashion eFashion ,etai lData Wa,ehouse c1e,,ted 14 Oct 199...
webi unive1ses efashion eFashion 1etai lData Wa,ehouse daled 14 Ocl 2007....
Monitoring TrendOata U... Monitoring TrendOata Universe
Report Conversion Tool ... Report Conversion ToolAudít Universe
Universe description
eFashion ,etai Data Wa,ehouse c,eated 14 Oct 1998, updated 3Ap,i l2002. 89,000. 10w facl table Ve,s
. ion 6.0
i Selected universe: efashion
Cancel < Back j

l
, Next > !
Figure 7.3: Query as a service pub/ishing wizard
1 can open the information design tool (see Figure 7.4) and review the
universe that I created. lt is listed, and I can publish it to the repository.
Once the universe is in the repository, 1 can then hopefully use it in the
Query as a Web Service tool if there are not errors. 1 will show you a
common error and how to fix it.
125
Information Design Toól

File Ed it Window Help
-JI local Projects � lã � ,;;,

'--------------- = El
º ffi• Elt
,.B - (j) 1Espress o Tutor ais
i
�- - -(=;, retrieval-2014-12-29-10-28-31
�-
é' ---'=:, retri eval-2014-12-29-10-31-37
i----- 7"" eCommerce Products, b lx
[--e,\ MARA MARM.dfx
[--{R SAP ERP 2015.cns
[- fl. SAP ERP 2015.cnx
[----� SAP ERP Connection.cns
L-- f}. SAP ERP Connection. cnx
cíJ Repository Resources

� ],... =_EJ_
_ _ _ _ _ _ __ _ _
◊ • J cfl 1§ X
B---cíJ @WIN-EEVJB76EON6:6400 (Administrator - Enterprise)
�-lê] Connections
:----{cl CommonConnections
: ----(}. Conversion Audit Connect on
i
i- - !'Jb ef ashion
i ·---·Q. efashion-webi
i - -- !Jk Moni toring TrendDB Connection
'--Oi. SAP ERP Connection
Él--lii Universes
�-lc] EspressoTutorial s
: '-----i] eCommerce Products. unx
$"lê Monitoring TrendData Universes
$--ILI Report Conversion Too! Un iverses
1±1-� webi universes
'----· §1 eFashion
Figure 7.4: IDT pub/ish universe
Select the business layer and then right click to publish it to the reposito
ry (see Figure 7.5).
126
B··· (ili Espresso Tutorials

1 ±1-··f.õretrieval-201'1-12-29-10-28-31
l±l ···ló retrieval-201'1-12-29-10-31-37
1::
;:!
ll ;i:,:-liiilll&i& 1
· · ·{f; Sl�Copy Ctrl+C
· ·l'Jb 51 Paste Ctrl+\I
: ::� :: � Delete
: Move ..
Renam .. F2
t_JRefresh FS
Show R pository Dependencies...
Save A ...
�Print
Figure 7.5: IDT publish the business layer
However, when I do this, there is an errar message (see Figure 7.6). This
errar indicates that I cannot just publish the business layer. 1 need to first
publish the data connection and create a shortcut from it.
i� ' n,n;,,. �I 1B � 'v = El ,ff� MARA MARM.dfx ·
1(,&i SAP ERP Connectio ... ·
1 ;o.,"' eCommerce Product... 1(
o
B··· Oll Espresso Tutoriais
l±l• e, � General Information I Q; Show Values
$· ·!; retrieval-2014-12-29-10-28-31
Name 1
1r,.,.-. .-.-..-. r-----�'--
l!l·· r.,. retrieval-2014-12-29-10-31-37 �
IX
1\·····# eCommerce Products.blx 1
'
i··m°"m MARA MARM.dfx
j.... (&I SAP ERP Connection.cns t) Error while publishing 'eCommerce Products'.
L..°'= SAP ERP Connection.cnx The business layer references one or several missing secured connections.
Edit and update the business layer to reference only existing secured connections before publ ishing.
íl Close
1
Figure 7. 6: IDT publish universe errar
Figure 7.7 shows that I publish on the repository server. This is not a
local copy, but rather the universe logic is saved within the 81 CMS serv
er and can now be used within the 81 services. This is precisely the rea
son why I got the errar before. The connection needs to be reformatted
when published to work on the server versus just locally on the computer
where I designed the connection and universe.
127
·· ·fR SAPERP Connection.cns

· · -�•·
1
Open
'ª New Data Foundation
�Copy Ctrl+C
Paste Ctrl+V
� Delete
Move...
Rename... F2
=1!,Edit Connection
Repository R, � Test Connection
.. J c::€1 tJRefresh FS
·dJ @WIN-E
S·. ·íil. Conr � Save Print
As ...
: 1 · ·lo <
j !·····ll. ( �Check Integrity ...
i j ..... Q_ € +4j Show Local Dependencies
: !··· ll. € � Publish Connection to a Repository
j
j....Q_ r
L..q�
Open in Windows Explorer
� Properties Alt+Enter
e,e-:,, "'-'-'':.....- - -----------------
- -
-
Figure 7. 7: IDT pub/ish connection
iíilllL_____�E=....:�:::._ �
v
c Ô��3�MARA�;MAAM��:::'.:
- · ��
2� w�ERJ>��-��---_��-�� d=·- �
iillliMilll
0 -;:-
@+ 81 ,. 1 Generail Jnformatlon Showvaues
'"s.....,.()"'" �-.-, so-,--
ut ----------1
....,, 1
00 l,cj, retriev,>1•2014·12·29·10--28-31 i'S Publnh [onno,cbon -� El
(.3, retrieval•2014·12·29·l0·31•37 Publish Connedi on to o Repository
� eComm!1-ce Ptoducts,bbc
,.\ MARA MAAM,cfx
0pen •S-HPOl'I cntMr•l>O'ltory "'-•ywWHf'lttop,,t:ld\th9w,«to•
1:2SARERRConnec:tmcns
li, W ERJ> Comoctlon.cnx 1
.:.1
Password (••••••••••
cfJ Repos1to,y Resources i:il ºô

--------
-'1.1.
Figure 7.8: IDT pub/ish connection to repository
128
Finally, Figure 7.8 reveals the last step to publish the connection.
i) Publish Connection l!!I� Ei
Publish Connection to a Repository
Define the repository folder where you want to publ ish the connection.
�[ri Ir' � 8t
13..fiil Connections
L..&I CommonCon
li!)j l
/Connections
Name • 1Descr iotion

lu CommonConnections
Qi.Conversion Audit Conn .. .
• (A.efashion
(A.efashion-webi
fl.Monitoring TrendDB Co ...
c;A.sAP ERP Connection Connect to SAP System Di ...
◄ .!.J ◄1 1 .!.J
,,Qi <Back Mext > Finish

l_ _ c_ a _ n c_ e
� _l
Figure 7.9: IDT pub/ish connection to repository finish
Once the connection is published (see Figure 7.9), 1 can view it in the
repository (see Figure 7.10). However, keep in mind that this was only
the connection. 1 now also need to publish the business layer.
' Publ1sh Connect1on
Publish Connection to a Repository

Define the repository folder where you want to publ ish the connection.
Riíafi"!ô@ St
B··� Connections 6!I) J/Connections
'····iil CommonCon �- - - - - -
-�- - - - - -
-
Name • Descri tion
� CommonConnections
• (Ãconversion Audit Conn...
; � efashion
fl ---�..
,.1-,; ,.,... ",,.,1-,; 8
lnfo Ef
@ The connection was published successfully.

The connection was publ ished successfully.
Do you want to create a connection shortcut in the sarne local folder to reference this new secured connection?
Ves No
Figure 7. 10: /DT pub/ish universe success
129
�1 = El
El···cfl @WIN·EEVJB76EON6:6400 (Administrator • Enterprise)

S··a- Connections
\····{õ CommonConnections
[--···Q. Conversion Audit Connection
i·····ti efashion
i·····fl. efashion-webi
[.....(i Monitorinn TrendDB Connection
L... (l_ SAP ERP Connection
Figure 7. 11: IDT repository view
Figure 7.11 Figure 7.11: IDT repository view shows the repository view
with the connections. You have to consider where the connection infor
mation is stored. lf it is stored in the repository, then reports can use it in
the network. lt is criticai that you "Publish" the connection to the relevant
repository.
When you publish the business layer, you have to select the new con
nection shortcut that the business layer now should be using when it is
published (see Figure 7.12).
$···� retrieval-2014·12·29·10·31·37
i·--··:,�l &i•llfü@MMJ.r.:.sa;N
\· · � MARA M, Open
1 ······ t&, Unresolved reterence: /Esr
-
)....mi SAP ERP -�
-Copy
-------- ---•
; � � Ctrl+C
'··· �
· SAP ERP -
Paste Ctrl+V
�Delete
rvlc:,v-e•••
Rename... F2
Refresh FS
Show Repository Dependencies...

Save As ...
Print
�Check Integrity ...
••� Show Local Dependencies
Pubhsh ► �To a Repos tory.. ,
i
To a Local Folder..,
Properties Alt+Enter
Figure 7. 12: IDT publish business layer
130
Figure 7.12 shows how to adjust the connection for the business layer.
You can follow the steps highlighted in Figure 7.13.
i1 Local Proje:cts f;3 � - ----�--
f8 � "" - c::t EI -& SAP ERP Ccn,e<tk>.•. lA *SAP ERP Comectio1
e, 13 •
(@MMte,
E$presso Tutotials
1B � retrieVa 1· 2011·12·29 1· 0 2· 8·3 1 • .l(\ " e
' ◊ ltl<ett • 1Det«t • I o:S I FamUes
!
li)._ rietrieval-2.01 4 •12·2:9·10-31•37
.:(< eCarmorce F>oducts,blx -□ X
a
t MARA MARM. x
1 Q!l SAP ERP COnnert on.cns ·on
l
!. SAP ER.P Connectlon.mx Select a ,-«n>edll(l l« the dat a foundatk>n,
l!I retrisv.,l,,2014·12•29-10-31-37
� SAP ERP COft-1,u,, SO<u-ed [G>WIN-EEVl876EON6:6100)
l,à, SAPERP c...,...d.,,,a,x local
cf) Ropo,tto,y ResOU'COS !:! =e

) • ' dl < >' e, FroiSh cancel
13i:il@VIIN•EEVlB76tON6:6100 (Admlnlsbator • Enterpnso)
Figure 7. 13: /DT adjust the connection for the business /ayer
Finally, the business layer can be published to the repository (see Figure
7 .14 ).
$--lã retri eval-2014·12-29·10·31-37
� . �� ti·IM@M@ o:e�
D ------� Unresolved reterence: fEspre�
j.....Jk MARA MARM.d --------------

j--{&i SAP ERP Conne �Copy Ctrl+C
é.....Q_ SAP ERP Conne Paste Ctrl+V
� Del ete
Move ...
Rename .. , F2
�Refresh FS
Show Repository Dependencies.. ,
Save As , . ,
éjPrint
r;i Check lntegrity ...
+\ Show Local Dependencies
-------------------=-•� 1 • 1•
Publish ► �To a Repository...
11
Properties Alt+Enter
Figure 7. 14: IDT publish business /ayer
131
Prior to publishing the business layer, you can do an integrity check to

ensure that the logic used to query the data is available and can produce
a consistent result (see Figure 7.15).
i) Publish Universe l!I� 13

Publish 11 Universe to 11 Repository
Check Universe Integrity
1
Select rufes and click the Check lntegrity button to start the integrity check.
çl·· ·-
0. liil Connections ar • Description • 1ResourceI Obiect1
i ( ·0 CheckCon
.
j L...0 CheckDep
$ O llil Table s
�- Olii Joins - , ·•
•
: •
1'
$· 0 1i::i Bus iness Layer

! r·0 CheckBusi
i . .
�-0 CheckBusi
;�:;..:1
rho.-1,,R�
◄ li L... �
1
Check all J Uncheck all i!} Check lntegrity1
< Back
! Next >
!_ _
F_ln _lsh_� __ c_an _ce _l�
Figure 7.15: IDT universe integrity check
At this point, the universe with the connection and business layer are
published to the repository. You can verify this via the IDT by refreshing
the repository.
The repository resources 1n the IDT interface show the published uni-
verse (see Figure 7.16).
=
B·cíJ @WIN-EEVJB76EON6:6400 (Adm inistrator - Enterpr ise)

$· ta Connections
ÉHô Universes
l;l··lli EspressoTutorials
L ...� eCommerce Products.unx
$..lã Monitori ng TrendData Universes
$ · tiil Report Conversion Toai Universes
$··!ai webi universes
L.� eFashion
Figure 7.16: IDT check repository with universe
132
The universe is available in the repository. You can confirm this by log
ging into the Central Management Console where you can review the
universes that are published (see Figure 7.17). You can see the .unx
universe. lf you remember, the newer universe version is indicated by the
.unx suffix. This is the case when you use the new information design
tool to design and publish your universe.
Central Management Console
l
unlverses 3
Organize •
Type
Unlverse (lnf0rmatlon design 1001)
UJ40i4i•lií@H-II
Monito1 ing TrendData Univer:
UI Re!X)tt Conversia"I Tool lklivt
L:il webi unlverses
Figure 7. 17: Central Management Console showing .unx
When I once again enter the Query as a Web Service tool to check if the
universe is now available, 1 can see that the universe is still not visible
(see Figure 7.18). What could be the reason for this?
2. Setect a univcrse
Selec:t a uni verse on whic:h to bui ld your query.
Folde, o
ef-•etaillàaW-aeated li Dei13!i
wetii irive,s:es: astion
ef ef-•etaillàaW-d<ledllOd,fSR
Monitori-9TrendOata U... MriOIW'lg lierd)aia Universe
R--tConversi:ln Tool... R.........t Conveision ToolAutitUrivetse
UnYerse dc«:riplion
eFad'iion retail Data\1/aiehcuseaeoted14 Oct 1998. \.Cldated 3Ap,i 2002. 89.CXQ. IOl'flad latlle.Version&D
..:J
<B«I< 11 N
...>
Figure 7.18: Query as a Service does not show the universe
133
PUBL!SHING REPORT'S ANO DASHBOARDS
This is a good example of the type of issue you can run into when using
a solution like SAP BW/BI. There are many tools, and not all support the
sarne levei of products. The Query as a Web Service tool does not sup
port the new .unx universes. lt only supports the older revision of uni
verses. Does this mean I cannot create a web service from our query?
No. 1 just have to use the right tool, which I will explain in the next sec
tion.
7.6 Publish as web service
ln order to publish data as a web service, 1 can use the Web lntelligence
Rich Client (WEBI). When you open this application, select UNIVERSE
(see Figure 7.19). Now you can see the newly published universe be
cause this application supports the newer .unx universe.
-- • C' -' • 1 • 1 "" -.1 • •
1• ChOOse a dêlla source10 creaee adOcm'lenl
--
- ...
p...,,
,...
--
,.,• Wl!bSer.,cn Pt1t11e
�------
S.-ct•VMservietN•--to.,rc,e
Figure 7.19: Web intelligence rich c/ient
Select the correct universe and proceed (see Figure 7.20).
You can choose a sample query and add the columns you require. Then,
click on RuN QuERY as shown in Figure 7.21.
134
Umv .r
Select a unive..se for lhe query.
:Tvpe here to 111:er t&t4e
available Uriverses: � Refresh l.riverse ist

Slate
IName
(9 eCommetc:e ProdudS.ll"lX
� efa.shion 125 @\M'I-EEV.B76EOr.16_6400\
C) ef�ion 127 @'Nl>J-EEVJ376EON6_
64CIJM.<eti...niverses
C) eF&Sh iOl'\.Ul"IX 1 @\A.C'J-EEV..e76f0,16 _6400\weti .......,erses
C> Monll:orirg TrendDa1a U"lfverse 7 @Wl'I-EEV.B76EOl'6_64�,ig TrendO«a ll1
C) Rel)OO COnverSIYl TOOI Audt Unlvetse 12 @\M'l•EEV.676EOl<6 _6400Repon CcrwerSIOn T001
• Jlf
l
Help on selected urwverse:
We w cl'oosethe MAR.A. MARM Data Model
Figure 7.20: WEB/ shows . UNX
__
IUJ. Uuery P«iel �l:l
e ....-,.. -
- ..... ·-
t9 ::r ,. °"'.
.,
'.,...,_,, 1 ,,
- --;:
•
Ount.-..HMlirMI ,
-
..o
T X"'
.
1
• �Ptocadt
.i-,-.&,
. .c..m.,,......
,
..�
- [[]·--..,,.,
•
•Quet)' flllet• ��T,..

ot•the.-v •-av�lbrstJertor�ctwe<tllNrehn-�(Cet>f�orto�lnetu..,,flt.ers
...,.,...Pr......., � lteire,ti
.........,,,
Q. • Typen�·
, -�- -
. '.·1
LMsl re1tt$h dai� (TNis docuTlettr.tne-ve, bcorlreítwiod)
Figure 7.21: WEB/ choosing example co/umns
135
ln the next step, choose WEB SERVICE PUBLISHER in the left section of the
interface and connect to the repository server (see Figure 7.22).
f�Web lntellígence Rích Client - [ADMINISTRATOR - @WIN-EEVJB7
Fi el /Properties Report E lement I F
D !ii:> • 1In • 1 a I li\\ 1 ig •

º"'ª Providers Tools
(O New clata provicler •

.t [@i j I -, , X I tjl �
Web Service Pubhsher •
[Tu] ,___ _____._____.,
Host server
Manage servers...
/!!, V\J\N-EEVJB76EON6 •
� ITTI•lx 1 �l�•'IIO.·
e!. Web Services onWN-EEVJ876EON6:6400
Figure 7.22: WEB/ Web Service pub/isher
Once you see the query result set in the results window, you can select
the table that presents the result set. Be sure to select the entire table
and then right click to see the menu that has the PUBLISH AS WEB SER
VICE button (see Figure 7.23). lf it does not show up, then you did not
select the full table.
Report 1
-,.... Knumh IKunnr

-----
0000010865 00001039::i IQr Co,,y CtrK

0000012663 00001039:i • Ctrl+V
0000013249 000010455
':.;e,._
0000015037 00001045�
X Oele!e
0000015824 00001045�
T...-nlnlo •
0000035497 00001044S �
0000035500 000010445 .t.ssign Dolo
0000035564 000010445 •
0000035577 00001044 jj. P\A>IShOSWebS..w,e
�
.UlllllJlllé�l..,.O.WlAl.0,i•J
Figure 7.23: Pub/ish as Web Service
136
lf you get an error when you publish, then you have to make sure the
right versions are installed for all products involved in this scenario. This
includes the repository CMS server, the services, and the WEBI client.
How can you verify the relevant versions? The next section will dive into
this topic.
7.7 The BI Edge CMS Repository

The repository for BI Edge is based on SQL Anywhere. Hence, it is not
as it was when it was based on SQL Server, but rather in its own SQL
server based on SQL Anywhere. The standard installation of BI Edge
does not come with any tool to manage this SQL Anywhere server. You
can download the SQL Anywhere central management tool (see Figure
7.24Figure 7.24: SQL Anywhere CMS) and connect to the CMS database
using the ODBC settings that are implemented as part of the installation
for your BI Edge platform.
�
�
Connect EI
� Connect to a SQL Anywhere Database
Jdent if icati on ) Network Advanced Options)

I
� [!uthentication: loatabase .:.J
!:,!ser JD:
,---------------------
�assword:
LJ Aç,tion: lconnect w ith an ODBC Data Source .:.J

(.' ODBC Data Source name
_CMS_DSN
11614 .:.J �rowse...
1� 1
(" ODBC Data Source file
ª"owse ...
Adyanced << 11
Iools • Connect ) Cancel Help
Figure 7.24: SQL Anywhere CMS
137
You can also use Excel to connect to the CMS and run a simple query to
get the version (see Fi gure 7.25).
Data Connection Wizard lfJ EI
ti
Connect to ODBC Data Source
Choosethe ODBC data source you want to connect to.
ODBC data sources:

10.12.106.13 PPL MARE ...
B14 Audit DSN
B14 CMS DSN
CSABAP
EMI_BW2
EMI_DW
Excel Files
MS Access Database
orei
QAnywhere 12 Demo
Sales_Analysis
SQL Anywhere 12 CustDB
SQL Anywhere 12 Demo
S Q LClientll
_
Cancel < ªack

j
Next > !_ _
F_in_is_h_�
Figure 7.25: SQL Anywhere Repository Query example
You can use the Sybase Central Mana gement tool to visually manage
the CMS database. However, you can also run a query usin g the Trans
act SQL tool (see Fi gure 7.26).
jtools t,,__ Modo l:IOI P
l!Dl•� • W ·lêl ,l{f\ili>-J•

Ô f.l uglns
·
l4/Bl4_C,4S • clbo
gptlons•••
Ç,re-oto 04t-oboso,,.
$t!ol>b-,kl2 • !.a>Qrode Database...
� Q/>nywhere 12 • !!O<.... 0,,tabose..•
� fleloySetver 12 • Rostoro OAt-ob-aso,.,
Create Bactµp Images...
un[oad Dotabase..•
" E!,tract Dattibese ..•
ER diagram for tlis
�alidate Oatabase ...
Iranslate log File.,.
tenancc Ta:sk.s Cb,ange log File Settings...
rrase Oat:abase...
locenance plan
�igate Database...
:l<Up
�ompare �tob&ses ..•
..IP images
Gen,er.:,te DaWbase OocumentaOOn...
dat�se corte<ts
es � Open QDBC Administrator
et-eferenc:es
Figure 7.26: Sybase Central or SQL lnteractive
138
Figure 7.27 shows an ERD diagram that will help you understand the
architecture of the CMS database.
(J 8 1 4CMS
_ · dba
I I I I l
Contents Overview Connections Fragmentation Page Usage tocks ER Oia11am Oeadocks Au<iting I 1
C M SA�ases7
_ (dba) CMS IdNumbers7 ( dba)
Object!D lnteger integer • PARENTID
Al laslsTruncat ed integer ldName archar( 30) • CHILDID
Al ias nvarcha,(255) IN EEVJB76EON6_6i00 lnteger ISMEMBER
IN EEVJB76EON6 _6i!O integer nteger
• RElATIONSHIPID nteger
integer
integer
lnnn hin.-.rv ..:J
CMS Jnfo0bjects7(dba)
' Object!D integer •
P arent!D integer
Type!D integer CMS Rfl.ATIONS7 (dba) CMS Sessions7 (dba)
' PARENTID • • SESS 1D
OWnerlD integer lnteger lnteger
verslon lnteger
nteger SESS_STATE integer
LastModfyltne var blnary(32) STATE_TS v.,binary(32)
SCheduleStatus integea ORDINAL r'ltege, MAX_TOKEN irteger
rW!�tR,,nTin"t!'\ v.-.r hinArvr�,, ..:J ' RElATIONSHIPID integet
VERSIOII intcgcr
KEVID inte ger
OATA lnnn hinArv ..:J
CMS Yersionlnfo (db a) OUMMY(SYS)
SUbsystem(lljm ber integer dummy _ col teger
&.JildVerslo n varchar(M)
EXCLUDEOBJEC T (dbo)
ha,( 128)
gtt dbremote_ temp ( ...

ISYSHISTORY (SYS) archar( 1 28)
. operat on har(12B) • va\Je ng var-char
i
· objectjd nsigned irt
s u boperation
_ har(12B)
version har(12B)
· platform har(12B)
fi'st_ time imestamp ISYSMIRROROPTION (SYS) ISYSOPTSTAT(SYS)
la s t t_ime imestamp
�l'Mo:: nn vwrhA r ..:J · option_name har(1Z8)
option_value n9varchar
• st..:_id
• group _id
nsigned int
nsigned int
• fonnat_id
Figure 7.27: SQL Anywhere CMS Repository ERD
The point of showing the SQL Anywhere central interface is to enable

you to understand where to look for version information if you have is
sues with the publication of any of your reports or services. You can also
run separate reports against the CMS to get status information about
universes and scheduled tasks.
Of course, there is a next step. How can we use the published web s e r
vices?
139
7.8 API standards evolving
The web service is the preferred source for your dashboards. Web s e r
vices can be controlled using APls provided by the different products that
come with SAP BI Edge. For example, the Raylight API allows a user to
programmatically control how the BI applications behave. However, using
these APls is not for the business user, but rather for the technical pro
grammer who leverages what the business user can do.
A specific API I would like to mention at this point once again is the Lumi
ra API that allows you to integrate D3 visualizations with Lumira using the
Vizpacker tool.
Nevertheless, as you have seen in our example, the business user can
easily publish a WEBI report as a web service, which can then be con
sumed by Lumira, for example.
7.9 Dashboard design considerations
To conclude this chapter and also the book, 1 would like to reconnect with
a theme I presented at the beginning of the book. 1 highlighted the im
portance of increasing the user value and usage of BI applications. The
newer BI and BW releases of SAP seem to provide the right technologies
to achieve an organized workflow for different skill levels involved in a BI
project. You may see that this workflow sometimes does not appear to be
very simple. However, you may also understand the reason why it is
complex. ln addition, you are able to add your own queries and columns
and can now also connect with BW using the latest technologies availa
ble in 7.4 SP08.
1 would like to conclude with a list of recommendations for your dash

board design project.
Perfection is the enemy of solutions, and I encourage using custem que

ries to achieve results quickly. Follow up with new releases to understand
what the technology can do, but avoid a religious embrace of technology.
Keep you project accountable and focus on the process. However, don't
use the process concept as an excuse for complexity. lf all else fails, you
can use your own ad hoc query using the toeis built in to SAP ERP. To
get help with that, you can consult the evolving GitHub project with in
formation about queries and reports for SAP. Using these best practices,
140
you can minimize or even eliminate the SAP shadow theme from your
project and achieve an improved break-even point for your BI project as
shown in Figure 7.28Figure 7.28: 81 application break-even.
User Value /
lnvestment
__..,
,,
Ma�lmum va1ue ,,,,
Aece1eratee1 BI --------------------- Accelerated ,,
81
1
1
1
1 Trad1tonal
i
81/BW
1
axlmum va1ue 1
1
raClitional BIIBW
ctual Break Even
------- - - - -
-+Time
Gol.Jve ReportingApps
Compelitive Edge
Figure 7.28: 81 application break-even
141
espresso
tutorials
Vou have finished the book.
Sign up for our newsletter!

Want to learn more about new e-books?
Get exclusive free downloads and SAP tips.
Sign up for our newsletter!
Please visit us at newsletter.espresso-tutorials.com to find

out more.
143
ABOUT THE AUTHOR
A About the Author
Wolfgang Niefert studied "Wirtschafts-lnformatik" at the European Busi

ness School in Oestrich Winkel, Germany. The international manage
ment program included programs in London and San Diego with a focus
on Computer Science and Economics.
He has more than 15 years of experience with international SAP imple

mentations. A certification for SAP Production Planning allows him to
relate larger SAP solutions to SAP BusinessOne. Wolfgang also de
signed the N20NE Portal for SAP BusinessOne that allows the real-time
management of e-commerce functionality.
With more than 1O years of consulting experience in the SAP space,

Wolfgang has obtained the SAP PP Production Planning certification
from the London SAP Academy.
Wolfgang has worked with HP, Allen Bradley, Sabik, and ATT in Germa
ny, the USA, Saudi Arabia, and Russia.
Expanding your knowledge with new perspective sometimes requires

that you evaluate new fields and classic ways of thinking. Wolfgang a t
tended the "Philosophy of Mind" track at Oxford University.
144
lNDEX
B lndex
• BI,Edge Edition With Data

.unv 97 lntegration 24
.unx 97 BI,Edge Edition With Data
.unx Universes 134 Management 25
Big Data 9
7 BOBJ BW 81
7.4 SP08 122 BOE140 25
7.4 SP08. 140 Break-even Analysis 13
Business Driver 95
A Business Layer 19,58,11O,130
ABAP Report 45 Business Objects Explorer 24
ABAP Workbench 52 Business Processes 12
Ad-Hoc Reports 34 BW 101
Ad-Hoc Tools 12 BW Analytic Manager 103
ADSO 121,122
Advanced Data Store Object 122 e
Agile Project Groups 16 Central Management Console
ASP.Net 92 22,26,98
C-Level 12
B Cluster Table 48
BAPI Explorer 50 Cluster Tables 54,57
BAPls 46, 49 CMC 22
BI Consulting Method 15, 37 CMS Repository 124
BI Edge 11,19 Company Codes 83
BI Edge 4 22 Company Repository 89
BI Edge Content Management Complex Responsive Processes
System 25 13
BI Edge Suite 15 Composite Provider 103
BI Edge Universes 59 Control Configuration Manager
BI Launchpad 19 26
BI Mini App 37 Controlling Areas 83
BI Product Versions 114 Corporate Reporting Strategy 19
BI Tools 9 Corporate Security 104
CR2008 98
145
lNDEX
CRM 20 H
Cross-Functional 9 Hierarchy Of Models 113
Crystal Reports 22, 61, 63, 72,
84 1
Crystal Reports 2013 98 IDT 95
css 119 lnfoObject 120
Cubes 34 lnformation Designer 22
Custom Reports 39 lnfoSet 23, 62, 65, 72
lnfoSet Strategy 82
D 1 nfoSets 15, 6 1
Dashboard Design Project 140 IT Landscape 113
Dashboards 117
Data Hierarchy 109 J
Data Layer 58 JavaScript 119
Data Model 38 Join Conditions 66
Data Source 59
Design Studio 119 K
Dictionary 55 Key Figures 89
Drill Down 120 KNA1 66
KPI 99
E
eCommerce 37, 107 L
Edge Edition, Standard Package LIKP 66
24 Linux 98
ERD diagram 139 LIPS 66
ERP-Centric 95 Logical Database 62, 64
ETL 24 Lumira 118
Excel 12, 33 Lumira API 140
Explain 75
Extractors 34 M
Meta Model 100
F Mini-reporting apps 37
Field-Level Semantics 121 MONI 48
Forecasting 40 MRP 15
MRP PP Blueprint 40
G MultiProvider 103
GitHub 93 MultiProviders 122
GitHub Query Repository 114
146
lNDEX
N Role/User Group Assignment 86

N20NE Bits 58, 59, 78 RSPO-DOWNLOAD-SPOOLJO
N20NE BITS 49, 51, 53 B 45
N20NE Bits SQL Designer 76 Run Query 134
o s
ODS Views 121 Sales And Distribution 83
OLAP 109 SAP BAPI 53
Operational Reports 34 SAP 81 Edge 11, 51
Order-To-Cash 69 SAP 81 Platform 37
OTC 89 SAP Business ONE 144
SAP Business Suite 100
p SAP BW 7.4 SP08 121
Parameter Files 26 SAP Data Model 55
Performance 91 SAP ECC 9, 15, 18, 89
Persistent Representation 122 SAP ECC 6.0 23
Primary Keys 66 SAP ECC Data Model 79
Publish The Data Connection SAP ECC Meta Database 81
127 SAP GUI 49
Publish Your Universe 133 SAP HANA 9, 34, 81, 91, 96
Publishing The Business Layer SAP Lumira 109
132 SAP Query Bootstrapping 93
SAP R/3 59
Q SAP Utilization Analysis 89
Queries 59 SAPLogon.ini 30
Query As A Service 22 Scoping 35
Query As A Web Service 124, SE11 48
134 SE16 63
Query Hierarchy 67 SE37 46, 50
Query stripping 111 SE38 45
SE80 52
R SE93 51
Raylight API 140 Semantic Layer 19, 58
Reporting Apps 15 Shadow Theme 12
Reporting Mini-App 35 SM19 41
Repository 131 SM20 44
Repository Server 127 SM36 45
Roadmap 33 Solution Manager 40
ROi 17 SQ01 60, 61
147
lNDEX
SQ02 60, 86 Transport Files 28

SQ03 60, 63 Types 121
SQL Anywhere 137
SQL Database Tables 48 u
SQL Trace 74 Universe 22
SQL Tracing 58 Universe Strategy 112
SQVI 15, 59, 60, 63, 78 User Profiles 40
ST03n 40, 43 UTF-8 3 1
ST05 74
STAD 40, 43 V
STMS 28 VBAK 66, 90
Strategic Dashboard Platform VBAP 66
118 VBELN 66
Strategic Reports 34 VBRK 66
Structure Tables 57 VBRP 66
SWNC-COLLECTOR-GET-AG Version 3.x 96
GREGATES 48, 49 Version 4.0 96
Sybase 138 Version 4.1 96
System Utilization Analysis 37 Virtual Views 121
Vizpacker 119
T VK13 66
Table Join 64
Tables 54 w
TC- ode Structure 53 Web lntelligence Rich Client 134
Time To Value 16 Web Service Publisher 136
Transact SQL 138 WEBI 22, 134
Transaction Code 15 WEBI Client 137
Transaction Code Utilization 39
Transaction Codes 37 X
Transactional Levei 9 Xcelsius 19, 22, 118
Transparent Tables 57
148
DISCI..AJI\IER
C Disclaimer
This publication contains references to the products of SAP SE.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Busi

nessObjects Explorer, StreamWork, and other SAP products and s e r
vices mentioned herein as well as their respective logos are trademarks
or registered trademarks of SAP SE in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crys

tal Reports, Crystal Decisions, Web lntelligence, Xcelsius, and other
Business Objects products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of Busi
ness Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,

and other Sybase products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of
Sybase, lnc. Sybase is an SAP company.
SAP SE is neither the author nor the publisher of this publication and is
not responsible for its content. SAP Group shall not be liable for errors or
omissions with respect to the materiais. 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 warran
ty.
149
More Espresso Tutoriais Books
t,1=. Anurag Barua:

First Steps in SAP® Crystal Reports
► Basic end-user navigation
► Creating a basic report from scratch
► Formatting to meet individual presentation needs
---
--- ---
-... - ---
--
http:/15017. espresso-tutorials.com
--
•=- Kermit Bravo & Scott Cairncross:

SAP® Enterprise Performance Management
(EPM) Add-ln
► Learn about the Connection Concept
► Get familiar with the SAP EPM Add-ln for Excel
SAP Entorpr!H Per!orm1nc1 and BPC 10.1
--
---
M>nagtmtJ>t (EPMI Add-ln
► Create a Basic Report from Scratch
-------,., ---
_______ --· ► Walk through a Detailed Case Study
http://5042. espresso-tutorials.com
Gerardo di Giuseppe:
First Steps in SAP® Business Warehouse
(BW)
► lips for Loading Data to SAP BW with SAP ETL
► Using Business Content to Accelerate your BW
objects
-----·
-- -- -- ►
-- --
---- -- How to Automate ETL Tasks Using Process
Chains
► Leverage BEx Query Designer and BEx Analyzer
Jõrg Bõke:
SAP® BI Analysis Office - a Practical Guide
► lnstallation and prerequisites
► Analysis Excel Pivot, Ribbon and Context Menu
Explained
---
► Enhanced reporting with API and Visual Basic
---- ---
--·-
___......,. --
-----
(VBA)
► Comparison between Analysis Office AO and BEx
http://5096. espresso-tutorials. com
Shreekant Shiralkar & Deepak Sawant:

SAP® BW Performance Optimization
► Use BW statistics effectively
► Leverage tools for extraction, loading, modeling
and reporting
► Monitor performance using the Workload Monitor
--· - .... & database statistics
,,,._.._,.,_,...___ =-..�:=
f'I
_ __.,.
...__
► Use indexes to understand key elements of

performance
http:/15102. espresso-tutoria/s.com
Rob Frye, Joe Darlak, Dr. Bjarne Berg:

The SAP® BW to HANA Migration Handbook
► Proven Techniques for Planning and Executing a
Successful Migration
► SAP BW on SAP HANA Sizing and Optimization
- --
--
► Building a Solid Migration Business Case
--
-- ---
► Step-by-Step Runbook for the Migration Process
•= 1 Dominique Alfermann, Stefan Hartmann, Benedikt
Engel:
SAP® HANA Advanced Modeling
► Data modeling guidelines and common test
approaches
► Modular solutions to complex require ments
---
---
-
--
--
--
---
-
► lnformation view performance optimization
► Best practices and rec ommendations
http:/1411 O. espresso-tutoria/s.com

Business Intelligence With SAP BI Edge

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Business Intelligence With SAP BI Edge

Uploaded by

Copyright:

Available Formats

espresso

lnstallation and setup tips for Query and repor1ing tools

How to build your own Step-by-step instructions on

Check out our YouTube channel to watch our videos at

lf you are interested in SAP Finance and Controlling, join us at

Related titles from Espresso Tutoriais:

► Annual online subscription

Editor: Alice Adams

Proofreading: Christine Parizo

Cover Design: Philip Esch, Martin Munzel

Cover Photo: Fotolia #60596613 © Maxim Kazmin

Interior Design: Johann-Christian Hanke

AII rights reserved.

1st Edition 2015, Gleichen

© 2015 by Espresso Tutoriais GmbH

Espresso Tutoriais makes no warranties or representations with respects to the

1 lntroduction to SAP 8usiness0bjects 8usiness

2 lntroduction to 81 Edge 4.1 19

3.6 Automating BAPls without programming 49

4 Connecting to SAP ECC 6.0 57

5 lnfoSets in BI Edge 4.1 81

6 Creating a universe in BI Edge 95

6.9 Planning your company's universe strategy 112

7 Publishing reports and dashboards 117

A About the Author 144

The target demographic for this book includes informed cross-functional

We have added an icon to highlight important information:

Finally, a note concerning the copyright: all screenshots printed in this

ldentifying the right questions to ask is an essential part of this book. A

1.1 81 business placebo and the SAP shadow theme

Consequently, the adoption of SAP and related ERP systems is not a

Essentially, the SAP process standardization leverages the integrated

that need to be accomplished by users. The religious embrace of the

1.2 Problems with BI projects

Target Break Even

Figure 1. 1: 8/ project break-even ana/ysis

NetWeaver Server End-User Analytics

N20NE Portal Business Objects Client Tools

SAP ECC 6.0 System Business Objects Edge

Figure 1.2: SAP 81 Edge technology schema

The following key problems can therefore be summarized for 81 projects:

► Time to value: 81 projects take too long.

ln order to address these issues, 1 will introduce a method that targets

► Improve time-to-value with 81.

1.3 The BI consulting method

As shown in Figure 1.3, the 81 consulting method begins a 81 project by

This information is used as a starting point for 81-related requirements

Utilization Shadow N Application

We are doing this wi th SAP SAP can·t do ... Let's do ...

Business Area • Profit Center

Utilization - Data Modais - F orecasting

Figure 1.3: Business integration and transformation suite models {BITS)

With this BI project implementation method, 1 am targeting the

Therefore, the 81 consulting method achieves a better project break-even

euai Break Even

Figure 1.4: Accelerated 81 method ROi improvement

1.4 Chapters overview

ln Chapter 5, 1 will discuss how to leverage reporting functionality, such

ln Chapter 6, a universe will be created by expanding upon the

Finally, in Chapter 7, 1 will walk through a sample solution that publishes

2.1 81 Edge products and technologies

R..-po-., to1y Unlof9'no�I�'°" CMC P,ofl�

Figure 2. 1: 81 toais jungle

The Query as a Service toai is of particular interest, as using this tech

Xcelsius is an Excel-based add-on that includes various widgets to pre