The right method & tools for building SAP BI web cockpits at International Paper. Dr. Bjarne Berg Joe McFerrin Comerit Inc International Paper. What We’ll Cover …. Company Background & Basic Terminology Our Tool options SEM CPM Web AD and SAP NetWeaver 2004s
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
The right method & tools for building SAP BI web cockpits at International Paper
Dr. Bjarne Berg Joe McFerrin
Comerit Inc International Paper
N. America 78%
Asia Pacific 8%
L. America 3%
frustrations with traditional SAP reporting tools
Who We Are
BW Report Center
1999 - Received first SAP overview of BW 1.2 - Perceived as too immature for IP requirements
2000 - BW 2.0b released GA - Still could not justify separate purchase w/o APO as driver
2001 - BW 2.1c released GA, we implemented on NT platform
- Justified pilot implementation along with APO as “futures” prototype
- By year-end, adopted BW as part of enterprise information delivery strategy
- Financials pilot for Capital Management (FI-AM, FI-GL)
2002 - Upgraded to BW 3.0B on Solaris- Beverage Packaging Sales Excellence live by year-end
- Crystal Reports/BW integration utilized extensively for report delivery to the field
2003 - Upgraded to BW 3.1 with 3.2 content - Completed S&A expenditure tracking project
- Began enterprise supply chain reporting project with a foundation strategy
- Started design of a BW based Enterprise Data Warehouse (EDW)
- Completed supply chain “early deployment” BW projects
2004 - Completed first release of enterprise supply chain reporting project
- Laid foundation (master data, ODS layer) for a BW based EDW
- 48 Process Chains and 71 Data Targets (ODS Objects/Infocubes)
2006 - Enabled BW Broadcaster and PDF functionality. Went live with IPG Containerboard Lead Team Cockpit
These are typical parameters, and some may be slightly different (i.e., some metrics in a cockpit may only be updated monthly). However, such deviations should be exceptions.
Logical grouping of similar information
The presentation layer in SAP
Management cockpits has
These presentation layer object are already web enabled and integrate with the Portal. They also provide built-in drill downs and navigation based on how you constructed your measures.
The management cockpits and web rendering closely integrate with the pre-delivered measures in SAP Measure Catalog. You also can add new measures through SAP Measure Builder.
By linking the higher-level measures, using Measure Trees, you can create true performance measures that are consistent throughout your cockpit and which also take care of most of the web navigation and drill downs in the cockpit. Navigation is built in to the management cockpit and you do not have to build customized links.
Consider SAP CPM when you have limited in-house web skills, or when measure consistency and rollups are very important.
Drawback: Users often complain that there are too many steps that they have to follow when drilling up and down within the measures (rigid navigation that is hard to customize).
Integrate queries and Web applications into the portal through publishing, broadcasting, or Web calls
The portal can either receive designed pages passively or actively create communities, Web pages, collaboration rooms, or cockpits
Central navigation can change multiple views
Link more documentation
Make multiple measures available
Source: SAP AG, 2005
Java programmers will recognize the standard development kit's (SDK) main libraries such as the abstract windowing toolkit (AWT) and the GUI-oriented Swing object library as well
Source: SAP AG, 2005
IPG Containerboard Lead Team Cockpit
A jump-to is hyperlink that allow users to navigate to more detailed reports associated with that Key Figure.
Most of our key figures have jump-to links attached to them allowing the user to see more detailed information with out having to search for other reports.
Pre-calculation Options We Used
KIWI Cockpit Report
A Good Cockpit Is Simple
Majority of usage of cockpits are in user segments 1 and 5. You should use BI queries and OLAP for the other segments.
Segment 4: Info Gatherers - 4%
Concentrated in information areas. Rarely reach transaction areas.
Segment 5: Single-clickers - 32%
Visit homepage only.
Segment 6: Wanderers - 15%
Very few, very random pages.
Few hits, but long duration per page view.
Segment 1: Trackers - 37%
Tracking -Characterized by low duration overall.
Segment 2: Reservers - 3%
Low duration per page view.
Segment 3: Uncommitted - 10%
Characterized by long duration.
Example source: Dr. Paul Strupp, Sun Microsystems
The average manager navigate in no more than 7 dimensions and only 2 levels deep (49 views). Therefore, the majority of users of cockpits need few, simple, but highly informative views. The other user community is best served by OLAP queries.
Colors share a powerful connection with emotions, so you want to be conservative
Colors on opposite sides are complimentary and looks good together in a cockpit
Sir Isaac Newton developed the first circular diagram of colors in 1666 and identified 12 basic colors
Shade: base color mixed with black
Tint: base color hue mixed with white
Tone: base color + gray or another base color +
a complementary color
Source: Bob Marteal, Cornell Univ. 2005, Susan M. Raymond, WHS
This uses a single pure color with a number of tints and shades to provide variety
Pros: Extremely unified and harmonious; effective for establishing an overall mood
Cons: Can be dull because of the lack of variation and therefore can lose the interest of the viewer
Any three colors which are side by side on a color wheel,
Pros: Great selection of possible combinations makes this scheme versatile. The similarity makes the schemes harmonious with great results because it is soothing and restful.
Cons: The use of more than three colors can dilute the overall effect of this scheme.
Pick any three colors on a triangle. This scheme is very appealing and well balanced.
Pros: Extremely stable, each color perfectly balances with the other. It is useful for presenting information in bold, decisive patterns.
Cons: The vibrancy may be too much and detract from the message.
Any two colors that are side by side on a color wheel
Pros: This scheme has more variety than a simple complementary color scheme
Cons: It is less vibrant and eye-catching; it is difficult to harmonize the colors
Colors that are so similar that not everyone will be able to distinguish them (blends information)
Split scheme background colors that are unattractive
Distracting color that breaks the color scheme and attracts attention for no apparent reason
Consistent use of graphs is visually pleasing. Here are three types of graphs and a map.
Background colors are monochromatic scheme in blue
Bars and lines are limited to same color scheme with few additional colors
Symmetry is visually pleasing and makes the cockpit easy to read. Here we have 3 walls, 4 frames in the outer walls, and a central section.
Filling the white space by either enlarging the map, or adding a message board would improve this cockpit
IMPORTANT: Old Reporting Agent scenarios still run in SAP NetWeaver 2004s. However, Reporting Agent will not be developed any further and is removed from SAP NetWeaver 2004s Workbench. In BI 7.0 you can only reach it by transaction code REPORTING_AGENT
There are many options and sometimes, the choice is based on what you are familiar with and whether you enjoy using new tools
Always consider pre-calculating the result set
Use SAP functionality where possible
Break up development into multiple phases