Transcript Click edit Master title slide - Lenoir

Access the easy, quality and
performance of your SAP BW
based reporting activities
Dr. Bjarne Berg
Lenoir-Rhyne College
© 2005 Wellesley Information Services. All rights reserved.
2
What We’ll Cover
•
Overview – BEx, Query designer, WAD, APD, Crystal, Broadcaster & Visual composer
•
How to fix some issues in BW reporting
•
Picking the right methodology for your next BW project
•
Report dispositioning – BW Vs. R/3 and what tool to use
•
Use of standard content
•
Skills needed on your project
•
Wrap up
3
The BW Toolset
BW is an enterprise-wide
comprehensive decision
support (DSS) system for
analytical needs of an
enterprise.
BW can also support some
degree of operational
reporting
Therefore it has many
presentation tools and
options for companies to
leverage.
This Conference Focus on
the Presentation tools
4
BEx what is it?
BEx is the 'umbrella name' for many of the presentation tools in BW.
Therefore you will notice the tool names are often pre-fixed with
names such as BEx Broadcaster, BEx Query Designer and BEx
workbooks etc.
5
The BEx Query Designer
The BEx query designer
is a simple tool that you
use to develop queries
for users.
While the Query
Designer defined the
query, you have many
options on how you
deploy the queries
You can deploy the
queries through web
templates, broadcasted
emails, portals, Excel
and more.
6
The BEx Ad-Hoc Query Designer
A simplified version of the BEx query designer is the "ad-hoc query
designer".
This is a powerful tool that can be used by power users to define their
own queries. It can be made available through a BW web template as well
as directly in the SAP Enterprise Portal
7
BEx - Workbooks
1. BEx Workbooks is Excel 'on steroids'.
2. BW queries can be opened in Excel
3. Queries can be refreshed
and standard Excel functions can
be used
This is a great tool for financial
analysts and power users.
To use this tool you need BEx/GUI
installed on each client machine
8
BEx web reports
•
•
The most common way of deploying BW queries are through a standard, or
customized web template with built-in navigational features.
BW provides a global web template that can be enhanced with logos, colors,
fonts and additional features at a low cost of development and ownership.
9
BEx Web Application Designer (WAD)
BEx Analyzer/
Query Designer
Web Browser
BEx Web Application Designer
WAD is an intuitive
tool to build powerful
web applications and
to interact with portals
and custom templates.
OLAP Processor
Web Service
Charting Engine
HTLM Templates
InfoProvider
Source: SAP AG
BW queries can be
manipulated in WAD
for better display
10
Web Application Designer for custom applications
You do not have to use the SAP
Enterprise Portal to use WAD.
WAD can also incorporate other nonSAP web items into powerful cockpits
and custom report centers.
While WAD can be used by developers
without extensive HTML and Java
scripting knowledge, these skills will be
useful on most projects.
11
Analysis Process Designer
•
Using the BW analytics toolkit, it is possible to build association data sets that can be
fed back into the OLTP engine. The way to approach this by using a new functionality
within SAP BW called APD (analysis process designer). This is a visual data
processing composition engine that enables organization of data flows and updates
into the OLTP database
Images: Bhanu Gupta, ASUG 2005 Illinois chapter
More on APD on day two at the 3:00 – 4:30 pm session
12
Crystal Report
•
With BW you get access to Crystal reports. In fact you have 100+ pre-developed
reports that comes with SAP-BW. Currently, you can modify, or develop and deploy 10
crystal reports without any additional licensing cost.
•
Crystal is a great tool for batch reporting of "pixel controlled' formatted reports.
13
Different Needs and Broadcaster Tools
Reporting needs
Reporting tools
KPI & Scorecard
Formatted
• Simple
• Easy to view
• Limited nav
• Aggregates
Flat Reporting
• Formatted
• Print
• Form based
• Static
• Predictable access
OLAP Reporting
• Drill Down
• Slice and Dice
• Analyse
• Data Mining
• Search and discover
“Casual” users, non-BW users, traveling users, and executives
are all prime candidates for broadcasted reports!
14
BEx Information Broadcasting
•
•
•
It’s a standard part of SAP BW 3.5 and higher
It lets you send “reports”, i.e.,
 BEx Queries
 Workbooks
 Web Applications
To...
 Email addresses, BW users, BW roles
 SAP Enterprise Portal Knowledge Management folders
 SAP Enterprise Portal Collaboration Rooms
N o te
You can define and deploy iViews based on the resulting KM /
Collaboration documents, if you wish!
15
Scheduling the Broadcast
We can schedule the job
to run every time the
infocube is changed (the
process chain has run)
We can limit the users to
when they can schedule
jobs to avoid stress on the
system. We can provide
multiple pre-defined times
when they can schedule the
reports.
We can also allow the
users to create their own
scheduling times (Only
authorized users see this)
More on SAP BEx
Broadcasting later today!
16
Visual Composer
Visual Composer is a tool to visualize the data. It is a browser-based intuitive modeling
and design tool for rapid application development and prototyping in a code-free
development environment.
Today Visual Composer supports both JSP and HTMLB; and has plans to also support
Web Dynpro metadata as well.
SAP NetWeaver
Visual Composer
You will see a demo of Visual Composer
on day three at the 10:15 – 11:45 session
17
Modelling of BI Applications using Visual Composer
Modelling of BI Applications using the BI Kit of the Visual
Composer
 Allows Business
Users to create analytical content for SAP Enterprise Portal
 Offers the integration with BI InfoProviders (e.g. InfoCubes, BEx Queries and Query
Views, BEx Web Applications) via WEB API as well as with heterogeneous data sources
(including OLAP and relational data sources) via Java Connectors
18
What We’ll Cover
•
Overview – BEx, Query designer, WAD, APD, Crystal, Broadcaster & Visual composer
•
How to fix some issues in BW reporting
•
Picking the right methodology for your next BW project
•
Report dispositioning – BW Vs. R/3 and what tool to use
•
Use of standard content
•
Skills needed on your project
•
Wrap up
19
Fundamental issues with BW reporting
Issue #1 – Query Performance Degradation Over Time
Issue #2 – The Pain Associated with Changing Data Models
Issue #3 – Remote Capabilities are very slow
Issue #4 – Pre-Modeled Data Relationships Required
Issue #5 - Managing Authorizations
Issue #6 - Dealing with User Expectations
Issue #7 – Data Reconciliation
Issue #8 - Dealing with Data Integrity
Issue #9 – Integrating Data Together in BW
Issue #10 – Upgrades get really complicated
Tomorrow we will examine each of these issues in a
focused session and see how you can solve each of them
20
General Issues with Business Warehouse Web Reporting
The pre-delivered BW’s web template does not always provide the
functionality required.
Currently lacking functionality includes:
• Creating favorites/bookmarks that can be accessed from any machine
• Printing fit to page, report info, data status, basic formatting
• Ability to search for reports within the end user roles
• Definitions of characteristics and key figures are not available
• Current web reports can not show repeat values of characteristics
• Online user help is not available in the web template
• No standard tool to target specific users about system status/changes
• On-line training is missing
As a result, most customers enhanced the functionality of the web template
using development tools such as HTML and Java Script, ABAP, WAD.
21
Portal Integration - Issues
The portal takes “control” of the pages hosted by BW. This prohibits interaction between
pages contained within the frameset by changing the document.domain property of the
launched page
The Solution
Understanding Try/Catch :
Must be addressed on the
frameset page
http://www.devguru.com/Technologies/ecmascript/quickref/try...catch.html
More on Cross Frame Scripting With IE :
http://msdn.microsoft.com/workshop/author/om/xframe_scripting_security.asp
Place this function in the
frameset ONLOAD event 22
Navigation
Users often complain that they can
not see all of the query names
Creating a scroll
feature allows users to
increase the size of the
role menu, or hide it.
23
Searching for a report
Users are often frustrated when they have to search for a
report they are unfamiliar with. The report may be hard to
locate in a hierarchy of roles on the launch pad.
Adding a search feature so that users can locate a set of
similar reports, significantly reduces this frustration.
The search feature can be added as a simple extension
within a web template.
Let's take a look….
24
Searching for BW queries
A regular windows
icon is intuitive and
easy to locate.
This searches within any string of the report
name, and all the folders you have access to.
No TREX engine required, only a simple
javascript that searches the SAP delivered
role menu.
25
The Web Template and Toolbar
•
Rule: After the BW query has been launched users
should interact with a standard interface that does not
change depending on the query executed.
•
This standardization is accomplished through the global
BW web template. Hint: Use WAD to customize and enhance yours
•
The web template should always include a toolbar that is
customized for your company.
•
In the next sections we will take a look at some standard
BW toolbar functionality and how you can extend the
web template to add more user features on the toolbar.
26
Web Print format
•
The web printing feature of a web browser is very limited
and users are normally very unhappy with it.
•
In the early days of BW, companies frequently employed
Crystal as their formatted reporting tool, even when the
formatting was very basic.
•
SAP now provides several ways to format the web
reports. Many of these delivered objects can be
extended to basic and advanced print formatting using
standard web technologies and scripting languages.
•
The next section demonstrates two ways incorporate
formatted web printing in a BW web template.
27
Print format basic
Users are generally
very unhappy with
browser based web
printing…
Again a simple JavaScript can leverage
SAP objects so that basic formatted BW
reports can be printed on the web.
28
Create your own “fit to page”...
Prompt the user for some
basic choices
Using these choices,
construct a new table while
inserting page breaks after N
number of rows
This process requires looping
thru the query results, row by
row, and copying the
contents of that row to a new
table. The # of rows generated
before a new page is needed
is determined by page layout
and paper size.
Loop with different font sizes
until the result set fits the
output format
29
Print format basics – how to get started
Copy of current data provider
launched in template containing Data
Table, Filter and Text Element web
items
Customized style sheet for printing
Page Break between report and
report details accomplished with
PAGE-BREAK-BEFORE (CSS2)
Page break text hidden with @media
print { } (CSS2)
NOTE: If your query uses a modified
table API class, add the following to
your url : &MODIFY_CLASS=THE
_NAME_OF_YOUR_CLASS
More on CSS for Printing :
More on CSS Media Types :
http://www.w3schools.com/css/css_ref_print.asp
http://www.w3schools.com/css/css_mediatypes.asp
30
Create advanced print formatting
We will spend more time of
fixed format reporting on day 2!
A more experienced web programmer can also add advanced web print
features that reduces the need for other formatted reporting tools. It also gives
user's flexibility and increases the likelihood that the go-live is a success!! 31
Control the number of rows in the output
The default number of rows from SAP is 100,
and this is often not enough for end users.
This is not a standard BW feature, but the object you
will need to call in a javascript is provided by SAP.
NOTE: Train the users appropriately!! If they ask for
32
100,000 records it will take some time on any system…
Get Access to On-line Definitions
Users often ask what a certain field means or what how
it was calculated. Adding on the context menu a link to
a dictionary makes many users really happy!!!
1. Characteristic, Key Figure and Query
definitions stored on SQL Server table.
2. Aliases used to extend match probability
3. Context menu item added to basic menu
33
4. Search results open in new window
Create your own BW Alerts Center
BW system messages reach entire
user community. We needed to narrow
that down to certain users via custom
Query/InfoProvider messages
ZB W _M S G _C E N TE R
m e ss a g e _ id
num ber
in fo _ p ro vid e r c h a ra c te r
in fo _ q u e ry
c h a ra cte r
m e ss a g e
c h a ra cte r
va lid _ fro m
d a te
va lid _ to
d a te
c re a te d _ b y
c h a ra cte r
c re a te d _ o n
d a te
34r
re q u e ste d _ b y c h a ra c te
On-line help
•The
user help is a musthave feature.
•The
development of the
company specific help
system can be done in
tools such as front-page,
MS-word, SAP-web
application designer etc..
•The
trick to a good user
help system is to present
the information so that it is
easy to locate. Therefore,
you should add indexes,
content trees and search
35
features in the help system
A place holder
CSV format
A "place holder" allows users to create a separate
window to "hold" a view of the information while
exploring the data (standard BW feature). You can
add these features to your toolbar.
Workbooks (Excel)
New Window
36
What We’ll Cover
•
Overview – BEx, Query designer, WAD, APD, Crystal, Broadcaster & Visual composer
•
How to fix some issues in BW reporting
•
Picking the right methodology for your next BW project
•
Report dispositioning – BW Vs. R/3
•
Use of standard content
•
Skills needed on your project
•
Wrap up
37
Business requirements
One of the first steps is to gather the right requirements. This is done
in a variety of ways based on the methodology that the company
employs. It is a complex process and involves a period:
1.
2.
3.
4.
Discovery and Education,
Formal communication,
Reviews
Final approvals.
What user wanted
How customer described it
A BW implementation does not simply
involve a series of black-and-white technical
decisions; just because something is
technically feasible does not mean it is wise
or desirable from a business perspective.
How analyst specified it
How designer implemented it38
What is ASAP?
Most traditional methodologies such as ASAP are based on the System
development Life Cycle (SDLC) approach. Under this approach, the two
key strategic tasks are to:
 Completely
 Select
define applications in the context of business requirements
technology based on compatibility and organizational know-how.
Under the ASAP, defining an enterprise's requirements as completely as
possible is extremely important, because even modest changes in the
applications' functions is assumed to cause dramatically changes to the
resulting tactical choices.
For ASAP, the longer the project duration, the more important the
methodology is to keep the project on-track.
39
The SAP NetWeaver Workflow - ASAP
Integration
Testing
Create Technical
Query specs
No
Create Functional
Query specs
System Testing
Complete?
No
Yes
Unit Testing
Complete?
Yes
Develop
queries
Yes
Peer Review
No
Approved?
Peer Review
Yes
No
Complete?
Yes
Approved?
Structured
walkthrough
No
No
Complete?
Yes
Structured
walkthrough
40
Getting Functional Query and Reporting Specifications
Avoid creating a total inventory of all reports in the organization. The "top-5" (most
used) sales, distribution, inventory etc. reports from each department will cover the
vast majority of the reporting needs. Create structured interviews with individuals that
have a stake in the outcome
Avoid attempting to replicate each report based on what you might have in place today.
Accept new ways of accessing data.
41
How can we do this Faster, Better and Simpler?
There are times when other methodologies should be used.
What determines the best methodology to use, is the impact of failure
and the time to delivery.
W h e n to S e le c t D iffe r e n t M e th o d o lo g ie s
H ig h
Jo in t Ap p lica tio n D e sig n
(J AD )
S ys tem d ev elo p m en t Life - C yc le
b ase d m eth o d o log ie s
(S D L C )
T im e to
D elivery
E xtrem e P ro g ra m m in g
(E P)
R ap id Ap p lic a tio n D e ve lo p m en t
(R A D )
ASAP and SDLC
Methodologies are not
the only choices. RAD
is very popular as well.
This framework
illustrates the benefits
of each methodology.
Low
Low
H ig h
Im p act o f F ailu re
42
Using RAD to deliver your next BI effort faster & better
The RAD core idea: Traditional
methodologies are too slow and
rigid to meet the business
demands of today’s economy.
Your RAD teams should consist
of about 6 people, including both
developers and full-time users of
the system plus anyone else who
has a stake in the requirements.
Prototypes
Source: Dr T.H. Tse
& Dr. Bjarne Berg
Developers chosen for RAD
teams should be multi-talented
"renaissance" people who are
analysts, designers and
programmers all rolled into one
(Walter Maner)
Small integrated teams - focus on small parts of BW i.e.
a set of infocubes, web reports or functional area.
43
How do you start your next BI effort using RAD?
Remember, RAD has an abbreviated blueprinting phase where meetings
are executed in short succession to get the requirements. Most of the
blueprinting and realization phase of the project are combined.
The first meeting: a one or two
days meeting with uninterrupted time
Who: Power users, casual users, people who today interact with the
current system and managers who have a stake in the outcome of the
information system development.
How many: A rapid pace is kept in these meetings and the number of
attendees is kept at a manageable level, with typically no more than
twenty people in attendance.
Different Needs: The coordinators and business analysts will focus on
shared information needs and conduct multiple sessions if needed.
44
WAD, APD and Visual Composer as RAD tools
The key idea of RAD with NetWeaver is the creation quick reports/queries that users
are asked to jointly develop. In the beginning these are simply "mock-ups" with data
that can be loaded from spreadsheet in a sandbox environment.
As the sessions progresses, tools such as the SAP Query designer and the Web
Application Designer is introduced and prototyping is done in each session with the
users.
Each RAD session is a working session, NOT a presentation session. Therefore,
each session should therefore be at least 3-4 hours long (not at someone's cubicle).
There should be at least 2-3 sessions each week to keep the work going forward….
Many critics of the ASAP have started to use tool
such as the SAP query designer and the SAP web
application designer as tools to do interactive
prototyping with the users.
45
What We’ll Cover
•
Overview – BEx, Query designer, WAD, APD, Crystal, Broadcaster & Visual composer
•
Some issues in BW reporting
•
Picking the right methodology for your next BW project
•
Report dispositioning – BW Vs. R/3 and what tool to use
•
Use of standard content
•
Skills needed on your project
•
Wrap up
46
Report Dispositioning BW Vs. R/3
Not all reports belong in BW. Avoid using BW as a "dumping group". Just because
the report is not in BW does not mean it can not be in a portal or on the web.
You need to make conscious decisions on what reporting needs you are going to
need and how you want to accomplish this.
Key questions for report dispositioning
1.
2.
3.
4.
5.
6.
7.
8.
9.
Is this really a reporting need or a "want"?
Is the data going to be in BW at a frequency that solves the user's request (intraday)?
Is the data needed for this report already in our BW scope?
Are there already a report available in R/3 ?
Does standard BW content exist?
Is it less expensive to create in R/3?
Are there a significant number of users?
Is the reporting need resource intensive?
Is BW cost effective in the long-run (ownership)?
Hom e
O verview
C o r p o rate S ervic es
P ers o n n el
B u s in ess A re a
S u p p l y C h ain
B I An alyst
S ales
A bo ut
M y B udget
C o n tro llin g
C o ntac t U s
P e rs on alize
Lo g O ff
F in an cials
Source: K eith Linn em ann
47
Team starts by reviewing documentation tool for
documentation completeness
An example on how to decide
which reports should be in R/3
or the legacy system )
Review requirements and identify
corresponding Data Model (InfoCube/ODS)
D1
Is report
documentation
complete?
Yes
D1a
Is this a true
reporting
need
No
Communicate to
bus. leader
Yes
No
D2
Is this
an Intraday
report?
Request additional
input from Business
Team member
No
D2.5
Does data exist
in "in-scope" models
Infocube/ODS
Yes
Yes
Yes
D6
Does
Standard BW
content
exist?
Yes
BW is selected as
Reporting Tool and
documented in doc.
tool
Communicate final
disposition
No
No
D7
Is it less
expensive to
create in
R/3?
BW is selected as
Reporting Tool
and documented
in the documentation tool
Communicate final
disposition
D8
Is BW cost
effective?
No
R/3 is selected as
Reporting Tool
and documented
in doc. tool
Communicate final
disposition
Yes
D9
R/3 Tool
Selection
Process
BW is selected as
reporting tool and Change
Request is submitted if
the scope changed
No
Standard
R/3
Yes
R/3 is selected as
Reporting Tool
and documented
in doc. tool
No
R/3 is selected as
Reporting Tool
and documented
in doc. tool
Yes
A2
Total Cost of
Ownership
Analysis
Communicate final
disposition
D5
Does
Standard R/3
content
exist?
D4
Is the report
system
resource
intensive?
No
Yes
R/3 is selected as
Reporting Tool
and documented
Responsible
Team member
acquires/documents
additional information
No
D3
Significant
number
of users?
BW is selected as
Reporting Tool and
documented in doc.
tool
Communicate final
disposition
Communicate final
disposition
Communicate final
disposition
ABAP/
Custom
Report
Writer
Query
Other
A3
Sub-Process Report Consolidation &
eliminate if appropriate (winnowing)
R/3 team make final disposition
BW Team to forward completed detailed report specifications
based on selected Reporting Tool - BW or R/3
A4
Baseline reports
48
Web Tools
Query tools
Deciding which reporting tool is right for you
Workbooks
Web
reports
Fixed
format
Web
Applications

-
-
-
-/
-/
*
-/


-
-
-

-/

-
-
-/
-



-
-


-/
-
-
-
-

Bex Broadcaster
-
-
-
-
-
-

Crystal Reports
-
-/

-

-
Query Designer
Ad-hoc query designer
Web Application
Designer
Visual Composer
Analysis Process
Designer
Other tools
Broadcaster -wizard
Models
-
Vizualization
Distribution
* Through embedded Bex Broadcaster
49
What We’ll Cover
•
Overview – BEx, Query designer, WAD, APD, Crystal, Broadcaster & Visual composer
•
How to fix some issues in BW reporting
•
Picking the right methodology for your next BW project
•
Report dispositioning – BW Vs. R/3 and what tool to use
•
Use of standard content
•
Skills needed on your project
•
Wrap up
50
The Blueprinting Phase: Leveraging Standard Content
M os tly s tandard s torage objec ts
• As
a guiding principle we
map requirements to
standard content before
we start customizing.
S om e c us tom iz ation
H ighly c us tom iz ed s torage objec ts
31%
• However,
we may also
have external data sources
that require custom ODSs
and InfoCubes.
• Some
observations on
higher level objects…….
36%
33%
An example from a large
manufacturing company
BW Content available:
Z
•
•
•
•
•
•
•
InfoObjects 11,772
ODS objects 349
InfoCube
605
MultiCubes
121
Roles
861
Queries
3,299
Workbooks 1,979
51
The Blueprinting Phase: Modeling Your Solution
Storage
B W fu n ctio n al req u irem en t:
W h en :
W ho:
P u rp o se:
Q u an tity:
Storage
Requirements
F all-03 to Jan -12, 2004.
In fo rm atio n d elivery te am
S to rage o b ject req u irem en ts
25
Un it
M a teria l
Lo g is t ic s
Cu rren c y K e y
M a terial nu m be r
M a terial en te red
P la nt
M a terial grou p
S a les u nit o f m ea s u re
Item c ate g ory
V o lum e un it of m ea s u re
W e ig ht un it o f m e as ure
P rod uc t h ie rarc h y
E A N/UP C
B W lo g ical m o d el:
Un it o f M e as ure
B a s e un it of m e a s u re
S hipp in g/rec eivin g p oint
B illin g
B illin g d oc um e nt
B illin g item
B illin g ty p e
B illin g c at eg ory
B illin g d at e
C rea tio n da te
C an c e l ind ic ato r
Num be r o f b illin g do c u m en ts
Cu s to m er
W h en :
W ho:
P u rp o se:
Q u an tity:
B illin g inform a tio n
+
F all-03 to Jan -12, 2004.
In fo rm atio n d elivery te am
S to rage o b ject req u irem en ts
25
B illed it em q ua ntity
Net weigh t
O u tp u t m e d iu m
~ Ba tch b illi n g i n d ic a to r
D e b it/cre d it re a so n co d e
B iling c a te go ry
S ub tot al 1
R efe re nc e do c u m e n t
S ub tot al 2
P a ym e n t te rm s
C a n c e lle d b illin g d o cu m e n t
D ivis on fo r th e ord e r he a de r
Num be r b ilin g lin e item s
S old-to
S hip-to
B ill-to
P ay e r
S ub tot al 3
S ub tot al 4
Cu sto m e r c la ss
Cus to m e r g ro up
S ub tot al 5
~ Cu sto m e r c o u n try
~ Cu sto m e r re g io n
~ Cu sto m e r p o sta l c o d e
~ Cu sto m e r in d u stry co d e 1
En d u se r
P ri cin g p ro ce d u re
S ub tot al 6
S u b to ta l A
Net va lu e
Doc um e nt de tails
Cos t
Ta x a m ou nt
V olum e
S a le s o rd e r d o c u m e n t typ e
S a le s de al
S a le s do c u em e nt
O rga niz a tio n
Co m pa ny c o d e
P ers on n el
A c c o un tin g
Tim e
Divis ion
Dis tribu tion c h an n el
S a le s o rg an iz ation
S a le s g ro up
S a le s rep n um be r
Cos t c en te r
P ro fit ce n te r
Con tro lling a rea
Acc o u n t a ssig n m e n t g ro u p
Ca le nd ar y e ar
Ca le nd ar m o nt h
Ca le nd ar wee k
Ca le nd ar da y
LE GE ND
Standard content
Z
D elivered in s tanda rd extractors
D elive red in L O e xtra cto r
N o t in d elivered C o n ten t -b u t in R -3
Map functional requirements to the standard
content before you make enhancements
BW InfoCubes
52
Modeling Your Solution
U n it
Lo g is t ic s
M a teria l
C u rren c y K e y
1. Create a model
based on predelivered BW
content
M a teri al nu m be r
M a teri al en te red
P la nt
S hi pp in g/rec ei vin g p oi nt
M a teri al grou p
S a les u ni t o f m ea s u re
Item c ate g ory
V o lum e un it of m ea s u re
P rod uc t h ie rarc h y
E A N /U P C
W e ig ht un it o f m e as ure
B il lin g
B il lin g inform a tio n
B ill in g d oc um e nt
B ill in g i tem
B ill in g ty p e
B ill in g c at eg ory
B ill in g d at e
C rea tio n da te
C an c e l i nd ic ato r
N um be r o f b il lin g do c u m en ts
C u s to m er
S hi p-to
B il l-to
P ay e r
C u sto m e r c la ss
C us to m e r g ro up
~ C u sto m e r
~ C u sto m e r
~ C u sto m e r
~ C u sto m e r
En d u se r
B ill ed it em q ua nti ty
N et w ei gh t
O u tp u t m e d iu m
~ B a tch b illi n g i n d ic a to r
D e b it/cre d it re a so n co d e
B ili ng c a te go ry
S ub tot al 1
R efe re nc e do c u m e n t
S ub tot al 2
S ub tot al 3
S ub tot al 4
P a ym e n t te rm s
C a n c e lle d b illin g d o cu m e n t
D ivis on fo r th e ord e r he a de r
S ub tot al 5
P ri cin g p ro ce d u re
N um be r b il in g l in e i tem s
S ol d-to
2. Map your data
requirements to
the delivered
content and
identify gaps.
U n it o f M e as ure
B a s e un it of m e a s u re
c o u n try
re g io n
p o sta l c o d e
in d u stry co d e 1
S ub tot al 6
S u b to ta l A
N et va lu e
D oc um e nt de tai ls
C os t
Ta x a m ou nt
V ol um e
S a le s o rd e r d o c u m e n t typ e
S a le s de al
S a le s do c u em e nt
O rga ni z a tio n
C o m pa ny c o d e
P ers on n el
A c c o un tin g
Tim e
D i vis ion
D i s tribu ti on c h an n el
S a le s o rg an iz ati on
S a le s g ro up
3. Identify where the
data gaps are
going to be
sourced from.
S a le s rep n um be r
C os t c en te r
P ro fit ce n te r
C on tro lli ng a rea
A cc o u n t a ssig n m e n t g ro u p
C a le nd ar y e ar
C a le nd ar m o nt h
C a le nd ar w ee k
C a le nd ar da y
LE GE ND
D e li ve re d in s ta nd a rd e xtra cto rs
D e liv e re d in L O e x tra c to r
N o t in d e liv e re d C o n te n t -b u t in R -3
53
What We’ll Cover
•
Overview – BEx, Query designer, WAD, APD, Crystal, Broadcaster & Visual composer
•
How to fix some issues in BW reporting
•
Picking the right methodology for your next BW project
•
Report dispositioning – BW Vs. R/3 and what tool to use
•
Use of standard content
•
Skills needed on your project
•
Wrap up
54
Example: small BW project for single subject area (i.e. billing, orders, deliveries)
These are roles not positions. (sometimes one
team member can fill more than one role)
P rojec t s pons or
P rojec t M anager.
B us ines s team
B us ines s analy s t
P res entation dev eloper
T ec hnic al team
B W A rc hitec t
E T L dev eloper
Basis and functional R/3 support
4-5 team members and normally
3-6 months duration depending on scope
55
Example: mid-sized BW project for single complex subject area (i.e. cost and
profitability, internal billing).
These are roles not positions. (sometimes one
team member can fill more than one role)
P ro je c t s p o n s o r/
S te e rin g C o m itte e
P ro je c t M a n a g e r
BW
A rc h ite c t
B u s in e s s
E x tra c t, T ra n s fo rm s
D a ta M a n a g e m e n t
P re s e n ta tio n
A n a ly s t(s )
and Loads
(In fo C u b e s & O D S )
D e v e lo p e r(s )
S r. B u s in e s s a n a y s t
S r. E T L d e v e lo p e r
S r. B W d e v e lo p e r
S r. P re s e n ta tio n d e v lo p e r
B u s in e s s a n a ly s t
E T L d e v e lo p e r
B W d e v e lo p e r
P re s e n ta tio n d e v e lo p e r
Basis and functional R/3 support
8-10 team members and normally
2-4 months duration depending on scope
56
Example: large BW project, multiple subject areas (i.e. sales, finance and MM)
These are roles not positions. (sometimes one
team member can fill more than one role)
P rojec t s pons or/
S teering C om ittee
P rojec t M anager
B W A rc hitec t
P ortal dev eloper(s )
S ales T eam
F inanc e T eam
M aterial M gm t. T eam
B us ines s analy s t/(s ub-team lead)
B us ines s analy s t/(s ub-team lead)
B us ines s analy s t/(s ub-team lead)
B W dev eloper
P res entation dev eloper(s )
E T L dev eloper
B W dev eloper
P res entation dev eloper(s )
E T L dev eloper
B W dev eloper
P res entation dev eloper(s )
E T L dev eloper
Basis and functional R/3 support
15-25 team members and normally
6-18 months duration depending on scope
57
On-Boarding and Training
Id e a l Y rs
T ra in in g d a ys
In -h o u s e
E x p e rie n c e
(if n e w in th e
tra in in g
(m in im u m )
ro le )
d a ys
B W D eveloper
2+
15
3 -5
E TL D eveloper
3+
1 5 -2 0
3 -5
P resentation D eveloper
1+
5 -1 0
3 -5
P roject M anager
5+
1 0 -1 5
3 -5
B usiness A nalysts
5+
5 -1 0
3 -5
N o te
Don’t underestimate the value of in-house, hands-on
training in addition to formal SAP training classes.
58
Tool Access – Who should do what…..
Other tools
Web Tools
Query tools
There are many options and decisions to be made on who
should be able to access all the different tools.
Query Designer
Ad-hoc query designer
Web Application
Designer
Visual Composer
Regular
users
Power
users
Authors
Developers
BW
Admins
-/
-/
-/
-
-/





-


-
-/



-
-


Broadcaster -wizard





Bex Broadcaster
-
-/
-/


Crystal Reports
-
-/



Analysis Process
Designer
59
What We’ll Cover
•
Overview – BEx, Query designer, WAD, APD, Crystal, Broadcaster & Visual composer
•
Some issues in BW reporting
•
Picking the right methodology for your next BW project
•
Report dispositioning – BW Vs. R/3 and what tool to use
•
Use of standard content
•
Skills needed on your project
•
Wrap up
60
7 points to take home
1. Pick the right tools based on what you want to accomplish.
“everything in the world is a nail, when you only have a hammer”…
2. The basic web print features are not sufficient
3. The BW tool set has evolved substantially over the last 2 years
–have you?
4. There are more than one way to continue BW development – take a
serious look at RAD.
5. On-line definitions on the context menu are very popular, but you will
have to add this as an enhancement (not SAP standard)
6. Today’s presentation developer is much more than a query developer.
More than one skill set is needed.
7. Leveraging standard content will give you access to higher level
objects as well.
61
Resources
•SAP
Project Management 2005
Pick
Your Poison – a look at methodologies for SAP NetWeaver” Bjarne Berg
•TechEd
/ ASUG- 2005 - Boston
Session
ID: IM100 – “Creating a Web Reporting Center at International Paper using SAP
Business Information Warehouse” George Brothers and Bjarne Berg
•SAP.com
“How To…Reconcile
Data Between SAP Source Systems and SAP NetWeaver BI”, SAP
June 2005
•Web
Template Enhancements:
•IFRAMES
: http://www.oreillynet.com/pub/a/javascript/2002/02/08/iframe.html
•Expressions: http://www.regular-expressions.info/javascript.html
•Getting Started with BSP Applications: http://tinyurl.com/642c4
•CSS for Printing : http://www.w3schools.com/css/css_ref_print.asp
•CSS Media Types: http://www.w3schools.com/css/css_mediatypes.asp
62
Your Turn!
Questions?
Dr. Bjarne Berg
Director of Business Intelligence
MyITgroup Ltd.
[email protected]
63
Front-end Team Members – Role descriptions
Reference
only
PRESENTATION DEVELOPERS The presentation developer is responsible for designing core reports for the functional
area that they support. This includes reviewing business requirements, existing reports, and working with the BW developers
to assure that the business requirements are supported in the cube and/or the ODS design, and creating template reports for
user acceptance based on requirements.
The presentation developer is also an individual who has a specific tool background. The developer may work on 3rd party
presentation tools, WAD, Broadcaster and BEx Query designer. The developers must assure data security, user friendly
reports, "drill-down" features, as well as a flexible design of data hierarchies and a logical and easy to use Graphical Unit
Interface (GUI) for end-users. Finally, the developer must assure that the front-end tool provides all functionalities supported
by the logical data model(s) and that the tool takes advantage of the physical database design features.
The design work also includes a detailed description of each access point, the navigation of access points, as well as a
detailed role description with association to the pertinent reports. The presentation developers also work with the portal
developer to integrate roles with the existing roles in the web portal.
PORTAL DEVELOPERS The developer in this position is responsible for the design and development of user roles for
accessing the SAP BW environment. This includes the creation of security requirements for the user interface, BW role
reconciliation, as well and integration of reporting help features, collection of external data for reporting purposes and the
integration between BW reports and jump-points to the transactional system. The individual in this role is also responsible
for the design and development of standard templates for reports delivered by the development teams, as well as the user
acceptance process for these templates. In a SAP Portals environment, the individual is also responsible for the content
management section of the portal and the configuration on the navigation bars and initial launch pad.
The individual staffed in this technical position should have a strong reporting and design background from SAP BW as well
as development knowledge of portals and the integration of standardized reporting environments. Prior industry experience
would also be helpful. The individual must also have solid programming experience in HTML, Java and XML.
64