Transcript IP Powerpoint Template | Three Verticals Montage

Enhancing Your User
Community’s
Reporting Experience
Joe Subits David Cole
Dr. Bjarne Berg
November 11, 2004
Who We Are - General Facts
More than 100 years of paper and forest products industry experience
World’s largest paper and forest products company with $25 billion in sales in 2002
More than 90,000 employees worldwide
Ranked 64th in Fortune 500
Number one in our industry in Fortune’s Most Admired Companies survey
Founding member of the global business-to-business electronic marketplace for the
forest products industry –forestexpress.com
Wealth of experience developing products and finding innovative solutions for our
customers
Slide 2
Our Sales Around the Globe
N. America 78%
L. America 3%
Europe 11%
Asia Pacific 8%
IP facilities
Slide 3
International Paper and SAP
Reporting
SAP History (LIS, SIS, CO-PA, ABAP Reporting)
1995 -- First Go Live on R3 with Financials and limited Logistics
1997 – Implementation of R3 Logistics for Masonite division
1999 – Implementation of R3 Logistics for Arizona Chemical division
2001 – Implementation of R3 Logistics for Beverage Packaging division
2003 – HCM (Human Resources) implemented in North America
2004 -- Financials implemented globally at 375 + locations
-- Enterprise supply chain improvement initiative
Experienced all of the traditional limitations and
frustrations with traditional SAP reporting tools
Who We Are
Leveraging BW
Business Driver
BW Report Center
Q&A
Slide 4
International Paper and SAP
Reporting
 A company as large as
International Paper has to consider
data as a corporate asset…
 The data must be uniformly
accessed and have the same
meaning…
 SAP R/3 is our core system and the
tight coupling to BW is hard to
ignore..
Who We Are
Leveraging BW
Business Driver
BW Report Center
Q&A
 We want to leverage our solution
for future DSS development and do
not want stand-alone custom solution
that is non-scalable.
Slide 5
Where are we headed ?
(Crawl, Walk, Run)
SAP History (BW Reporting)
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.0a on Sun Solaris platform
- Began Beverage Packaging Sales Excellence project
- Upgraded to BW 3.0B
- Beverage Packaging Sales Excellence live by year-end
- Crystal Reports/BW integration utilized extensively for report delivery to the
field
Slide 6
Where are we headed ?
(Crawl, Walk, Run)
SAP History (BW Reporting) – continued
2003 - Upgraded to BW 3.1 with 3.2 content added
- Completed S&A expenditure tracking and analysis project
- Began enterprise supply chain reporting project
- Created foundation strategy and design for 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
- 356 Master Data loads
- 152 Data Packages (extracts)
- 48 Process Chains
- 71 Data Targets (ODS Objects/Infocubes)
2005 – Tentative plan to upgrade to BW 3.5 and companion SEM release 4.0
Slide 7
BW / EDW Scope compared to the scope of
most Legacy Data Warehouse(s) at IP today
Demand Planning
Supply Network Planning
Transportation Planning / Vehicle Scheduling
Customer
Relationship
Management
Orders
Shipments
Deliveries
Invoices
A/R-CC
Supply Chain
Event Manager
Production Planning
Greycon Trim
Material Movements
Production Orders
Supplier
Relationship
Management
E-Procurement
T&E, P-Card, Freight
Purchase Orders
Production Performance
Cost-Profitability
MRO/RM
Inventory
A/P
General Ledger / Hyperion
Most Legacy DW
Slide 8
BW / Enterprise Data Warehouse Status
Demand Planning
Supply Network Planning
Transportation Planning / Vehicle Scheduling
Supply Chain
Event Manager
Customer
Relationship
Management
Production Planning
Greycon Trim
Material Movements
Orders
Shipments
Deliveries
Invoices
A/R-CC
Production Orders
Supplier
Relationship
Management
E-Procurement
T&E, P-Card, Freight
Purchase Orders
Production Performance
Cost-Profitability
MRO/RM
Inventory
A/P
General Ledger / Hyperion
2003
2004
Slide 9
BW Organization Strategy
Reorganize – Highly integrated and centralized team around BW
architecture
–
–
–
–
BW Back-end Development team (Data structure design/build & ETL)
BW Front-end Development team (OLAP, presentation layer, Portal apps)
Project Management team (application development, technical landscape)
BW Architecture/Data Model/Development Standards team (develop and enforce)
Retool – Three SAP classes (13 days total), follow up tutoring by
consultants
Q1 2003
Q1 2004
Q1 2005
5 BW developers
15 Legacy developers
3 BW contractors
18 BW developers
2 Legacy developers (break/fix)
14 BW contractors
24 BW Developers
0 Legacy Developers
8 BW Contractors
Refocus
– Have ended investment in legacy ( software, hardware, & people)
– Legacy EDW transitioned by the end of 2004
– All new development in BW ( = our strategy )
Slide 10
BW / Enterprise Data Warehouse Status
Functional Reqmts Complete – 10/8/03
Build/Unit Test Complete –Demand
12/5/03 Planning
Delivered SAP Content (structure) with
Supply Network Planning
moderate customization
2.6 Effort Months
Transportation Planning / Vehicle Scheduling
Consultant – 4 Years BW Experience
IP Employee – 9 Months BW Supply
Experience
Supplier
Chain
Customer
Relationship
Management
Event Manager
Relationship
Management
Production Planning
E-Procurement
Reqmts Complete – 9/29/03
Greycon Functional
Trim
T&E,
P-Card,
Freight
Build/Unit Test
Complete
– 12/5/04
Material Movements
Delivered SAP Content (structure) with
Purchase Orders
Production Ordersmoderate customization
Orders
Shipments
Deliveries
Invoices
A/R-CC
MRO/RM
3.0 Effort Months
Production Performance
Consultant – 4 Years BW
Experience
Inventory
IP Employee – 9 Months BW Experience
Cost-Profitability
A/P
General Ledger / Hyperion
2003
2004
Slide 11
BW / Enterprise Data Warehouse Status
Demand Planning
Supply Network Planning
Transportation Planning / Vehicle Scheduling
Complete – 10/8/03
Functional
Reqmts Complete – 10/29/03
Supply ChainFunctional ReqmtsSupplier
Customer
Complete – 1/13/04
Build and Unit Test Complete – 12/3/03
Event Manager Build/Unit TestRelationship
Relationship
4.3 Effort Months
Delivered SAP Content (structure)
Management
100% Custom Built
Content (structure)
1.5 Effort Months Production Planning
Management
Consultant – E
3 -Years
BW Experience
Consultant – 3 Years BW Experience
Procurement
Greycon TrimIP Employee – 1 Month BW Experience
Orders
IP Employee
– 1 Month BW Experience
Material Movements
Shipments
Deliveries
Invoices
A/R-CC
Production Orders
T&E, P-Card, Freight
Purchase Orders
Production Performance
Cost-Profitability
MRO/RM
Inventory
A/P
General Ledger / Hyperion
2003
2004
Slide 12
Agenda
Business Driver
Enhancing our Supply Chain With BW
Who We Are
Leveraging BW
Business Driver
BW Report Center
Q&A
Slide 13
Business Driver
As a result of the company's tremendous growth through mergers and
acquisitions ($4 billion in the mid 1980s to more than $25 billion today). That
is why we are establishing consistent processes, improving our visibility
and access to better serve our customers and provide solutions.
In short; our supply chain initiative is to continue to improve our processes
to make IP easier to do business with.
While R/3 is how we will execute our supply chain, BW is how we will
manage the supply chain.
Who We Are
Leveraging BW
Business Driver
BW Report Center
Q&A
Slide 14
We leverage Standard Content…
As a guiding principle we map
requirements to standard
content before we start
customizing.
Mostly standard storage objects
Some customization
Highly customized storage objects
31%
However, we also have external
data sources that require
custom ODSs and InfoCubes.
36%
33%
BW Content available:
Some observations on higher
level objects…….
•InfoObjects 11.772
•ODS objects
349
•InfoCube
605
•MultiCubes
121
•Roles
861
•Queries
3.299
•Workbooks
1.979
Slide 15
Agenda
Business Warehouse Report Center
David Cole
Who We Are
Leveraging BW
Business Driver
BW Report Center
Q&A
Slide 16
Key Points
Our Toolset
 Standard Web Scripting ( HTML, JavaScript, Cascading Style Sheets)
 BW Specific Solutions ( Web Application Designer, Business Server Pages)
 Editors ( Web Application Designer, HTML Text Editor, Web Application
Builder (SE80) )
 All Solutions Require IE 5.5 or Later
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Slide 17
Report Center – At A Glance
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Not a replacement for the Portal
Slide 18
Report Center – At A Glance
Code
Snippet
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Slide 19
Portal Integration
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Slide 20
Portal Integration - Issues
The Issue
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
Code
Snippet
The Solution
 Must be addressed on
the frameset page
Place the following
function in the frameset
ONLOAD event
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Understanding Try/Catch :
http://www.devguru.com/Technologies/ecmascript/quickref/try...catch.html
More on Cross Frame Scripting With IE :
Slide 21
http://msdn.microsoft.com/workshop/author/om/xframe_scripting_security.asp
Global Template
Our Approach
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
 Ensure positive experience with
front end
 Consistent look and feel for all our
customers
 Centralization and standardization
of template
 Custom templates must use same
“Feel” and adhere to naming
standards. Colors may vary.
 Toolbar functionality controlled in
one location, referenced via
JavaScript include file and is built on
the fly.
Slide 22
Our Toolbar – High Level
Use of standard BW/Microsoft icons
Code
Snippet
Slide 23
Toolbar Highlights – Save To
Favorites
Code
Snippet
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Microsoft Outlook Users : Use similar logic to create an icon to email
bookmarks. For more information on mailto, see
http://msdn.microsoft.com/workshop/networking/predefined/mailto.asp?f
rame=true
Slide 24
Toolbar Highlights – Online Help
Application
Our Approach
 Generic navigation tips and
how-to’s
Complements our training
program
Help file created with Microsoft
Word and saved as HTML.
 Anchors placed in help topic
headings
 Javascript/HTML used to link
to anchors
 Camtasia Studio used to
author How To lessons
Slide 25
Toolbar Highlights – Simple Print
Our Approach
Code
Snippet
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 :
http://www.w3schools.com/css/css_ref_print.asp
More on CSS Media Types :
http://www.w3schools.com/css/css_mediatypes.asp
 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 PAGEBREAK-BEFORE (CSS2)
 Page break text hidden with
@media print { } (CSS2)
Slide 26
Toolbar Highlights – Advanced
Printing
Our Driver
 IE print function not
very robust
 Provide user
community with
increased flexibility while
printing from the web
 Target is to reduce the
need for static,
predefined, formatted
reports.
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Slide 27
Toolbar Highlights – Advanced
Printing
Our Solution
 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.
Slide 28
Toolbar Highlights – Advanced
Printing
1
1. Launch copy of current
DataProvider into a new template.
Template contains DataTable to
store query results, text elements
and filter/variables used on the
query.
2. Get handle on DataTable web item
and hide.
3. Analyze DataTable to set
recommended page layout and
paper size.
4. Capture user header/footer
choices (report title, company
logo, print date/time, page
number) and report details to be
printed (standard Text Elements
and report filters/variables)
2,3
4
Slide 29
Toolbar Highlights – Advanced
Printing
5. Build new html string representing the formatted output of the query.
Slide 30
Toolbar Highlights – Advanced
Printing Shortcomings
Shortcomings
 No fit to page function
 Num rows per page calculation not consistent
 User must change IE print settings to match selected print settings
Possible Solutions
 Some printers offer fit to page function, as do some browsers
 Some non IE browsers support TBODY,THEAD,TFOOT and put in page
breaks in the appropriate places when printing
 Active X Component will set users print settings, must be trusted by
browser
Slide 31
BSP Applications
Current BSP Applications
 BW Definitions – Links the user to an external ASP/SQL Server application which
contains definitions of queries, characteristics and key figures.
 BW Alerts Center – Allows business analyst/system administrators to broadcast
alerts to specific queries and/or cubes.
Planned BSP Applications
 Centralized Favorites – Allow users to manage their bookmarks on a server based
application ( much like Cognos Upfront © or Business Objects ePortfolio © )
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Getting Started with BSP Applications
http://tinyurl.com/642c4
Slide 32
BW Definitions
Our Approach
 Characteristic, Key Figure and
Query definitions stored on SQL
Server table.
 Aliases used to extend match
probability
Context menu item added to basic
menu
Search results open in new
window
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Slide 33
BW Definitions
Our Solution
 Definitions stored in SQL Server
 SQL Server data accessed via
ASP/XML
Context Menu entry added with
SAPBWAddToMenu ()
Characteristic/Dimension Text value
retrieved using
SAPBWGetDataProviderDimensions ()
For Key Figures, BSP page retrieves
text for a given key figure id (l_UID) from
RSZELTTXT
 Retrieved string is ESCAPED via
Method ESCAPE_URL of Class
CL_HTTP_UTILITY
 Key Figure text is massaged with
JavaScript regular expressions to
remove various hexadecimal values
before page is redirected to ASP search
page.
OnInitialization Event
Code
Snippet
Page Layout
Code
Snippet
More on Regular Expressions :
http://www.regular-expressions.info/javascript.html
Slide 34
BW Alerts Center
Our Driver
 BW system messages
reach entire user
community…We needed
to narrow that down to
certain users via custom
Query/InfoProvider
messages
Slide 35
BW Alerts Center
Our Solution
 Created custom BW table
(ZBW_MSG_CENTER)
ZBW_MSG_CENTER
message_id
info_provider
info_query
message
valid_from
valid_to
created_by
created_on
requested_by
 Built admin interface with
BSP/HTMLB pages
number
character
character
character
date
date
character
date
character
Slide 36
BW Alerts Center
Our Solution
If BSP finds a message, it calls the
alertBwMessage() function located on the
template
 InfoProvider/Query id captured on
web template using text elements
REPTNAME and INFOCUBE
 This information is passed to a
BSP lookup page via remote
scripting
Javascript function loads hidden iframe with
z_get_message.bsp?query=x&infoP=y
 BSP Page : z_get_message
retrieves message(s) from
zbw_message_center
 Messages passed back to
template via remote scripting
 If given message_id has not been
seen by user, a pop up window is
created and the message is
displayed
For more information on remote scripting with IFRAMES, see 
Used cookies to determine if the
user has seen a message_id before
http://www.oreillynet.com/pub/a/javascript/2002/02/08/iframe.html
Slide 37
Looking Ahead
Enterprise Portals go-live
Management Cockpits
SAP BW
Broadcaster
Key Points
Portal Integration
“Global” Template
BSP Applications
Looking Ahead
Slide 38
Agenda
Questions and Answers
Who We Are
Leveraging BW
Business Driver
BW Report Center
Q&A
Slide 39