case study: lessons from newell rubbermaid's sap hana proof of concept

Produced by Wellesley Information Services, LLC, publisher of SAPinsider. © 2014 Wellesley

Information Services. All rights reserved.

Case Study: Lessons from Newell Rubbermaid’s SAP HANA Proof of Concept

Rajeev Kapur and Roger Sauvageau Newell Rubbermaid

1

In This Session

• Newell Rubbermaid will guide you through the key elements that

comprised its SAP HANA business case and proof of concept.

Learn firsthand how Newell Rubbermaid:

Identified which business processes were most likely to realize

significant improvement as a result of utilizing SAP HANA and

our approach for our POC

Determined which SAP BI tools to use based on specific

reporting scenarios and end-user requirements

Built an interactive Dashboard

2

What We’ll Cover

• Introduction

• HANA – Proof of Concept

• Opportunities

• Tool Set Discussion

• Demo

• Wrap-up

3

Introduction

• About Newell Rubbermaid

We are a global marketer of consumer and commercial

products with a strong portfolio of leading brands known for

delivering superior performance, design, and innovation

Headquartered in Atlanta, Georgia, USA

Approximately 19,000 employees worldwide

Sales in more than 100 countries

NYSE: NWL

4

Home Solutions

Baby & Parenting

Writing

Commercial Products

Tools

Introduction (cont.)

• Our Five Business Segments:

5


• Tools Segment

6


• Commercial Products Segment

7


• Writing Segment

8


• Baby & Parenting

9


• Home Solutions

10

What We’ll Cover

• Introduction


• Opportunities


• Demo

• Wrap-up

11

SALES 360 at Newell Rubbermaid

• Objective

Provide daily sales KPIs to senior leadership and managers

• Target Audiences

Executive Team

Sales Team

Supply Chain/Customer Service

Plant/DC

Sales 360

ANALYTICS H

12

Business Questions

• Are we going to make the month?

Invoiced Sales and Open Orders vs. Last Year, vs. Latest

Estimate, vs. Financial Estimate (QTR Call)

• How are we doing for the Year as a Whole?

Same breakdown as above with out open orders, but compared

by management structures

• What areas of the business are contributing or failing to

contribute to making the month or the year?

Geographies, Product/Segment, etc.

• Ad hoc access mode for unforeseen questions?

13

What Is Sales 360?

• Combination of COPA (Invoiced Sales) and OTC (Open Orders)

coming from SAP

• Legacy Data from APAC (100%) for Invoiced Orders and Open

Orders

• 3 BEx Reports

• 50+ Reports published daily to an audience of several hundreds of

people (and growing daily) including a Briefing Book which goes

to the XLT

• Most used reporting environment

14

Develop Sales Environment 1

• Make it Agile, Expect Frequent Requirement Changes

• Area less likely to change given that we just went through standardization

effort

Simplify Security Model 2

• Business-friendly for reporting

• Profit Center-Based for Segments vs. SKU-based (Aligned to Finance)

Increase Frequency of Data Loads 3

• Provide Data Refresh Every 4 hours

• Increase Reliability of Data Refresh

Tailor for Executive Reporting 4

• Build Standard Hierarchy Definitions

• Guided Analytics for Executives versus ad hoc Reporting – Prove out newer

toolsets from SAP

• Increase and Continue to provide Push Reporting

• Upgrade BEx

Enhance Reporting Toolset 5

Sales 360 – Our Approach on HANA

15

• Current Security model by Sales Org, Company Code, Plant, and

Profit Center, which is more Transaction System-Based

• New Model for Sales Reporting (Align to Corporate Structure)

Easy to Comprehend for User/Their Geographical location

US, CA, APAC, LATAM, EMEA

Simplified Security Model

Region

Profit

Center

Sales Team

Invoicing

Entity

Financial Hierarchy-Based, 15 High-Level Values

Matches the Organizational structure of Sales Teams

Ensures EPC Compliance (Company Code)

16

Frequency of Data Loads

• Increase Frequency of Data Loads

Data Refresh (Every 4 hours vs.

Nightly)

Ability to toggle between the

Nightly View and the Refreshed

View

• Faster Data Loading and

Provisioning

HANA-Optimized Data

Providers

System Navigation

DB Space Improvement

17

Improved Query Performance

• Processing Pushed Down to SAP HANA

18

Standardized Hierarchies

• With the move to highly standardized reporting, a key

consideration in our technology roadmap is a view of how the

business operates using Standard Hierarchies

Sales Orders

Segments/ Product View

Geography

Customer (Top 75

Corporate; Top Segment)

Sales Team

Warehouse

Brand

Channel

19

Sales 360

20

What We’ll Cover

• Introduction


• Opportunities


• Demo

• Wrap-up

21

Current State HANA

Sales Order Analysis/

Service-level metrics

PO Tracker (Document

Flow)

• 7 Cubes

• 0.78 TB of data

• 82 BEx Queries

• 2 Calculation Views

on Design Studio

• 0.22 TB of data

Area

• 15 Cubes

• 1.58 TB of data

• 26 BEx Queries

• 1 Calculation View

on Design Studio

• 0.46 TB of data

HANA Opportunities

22

What We’ll Cover

• Introduction


• Opportunities


• Demo

• Wrap-up

23 Source:

Ingo Hilgefort, “Selecting the Right SAP BusinessObjects BI Client Product based on your business requirements for SAP BW Customers” (SAP 2012).

Tool Set Discussion

24

Tool Set Discussion (cont.)

Source:

Ingo Hilgefort, “Selecting the Right SAP BusinessObjects BI Client Product based on your business requirements for SAP BW Customers” (SAP 2012).

25


26

Lots of Tools to

choose from.

Which one is the

right one?


27


28

Lots of Tools for

our targeted

audience

Can we simplify?


29

Push Reporting Monitoring Analyze Discover

WebI One Application That Delivers

All 3 capabilities

Excel

Workbooks

SAP BusinessObjects –

Analysis Toolset

Data Discovery –

Limited Group

(Tool: Explorer, Lumira, etc.?)

Business Users

Groups use

same tool


30

Sales 360 Dashboard

31

What We’ll Cover

• Introduction


• Opportunities


• Demo

• Wrap-up

32

Demo

33

What We’ll Cover

• Introduction


• Opportunities


• Demo

• Wrap-up

34

Where to Find More Information

• www.saphana.com/welcome

SAP HANA website

• www.youtube.com/playlist?list=PLkzo92owKnVzPESNUVm87QTYrkbiUtKDN

How to use various SAP BusinessObjects solutions as well as SAP Predictive Analysis and SAP Lumira to interact with SAP HANA data sources

• www.sap.com/pc/analytics/business-intelligence/software/design-studio/index.html

SAP BusinessObjects Design Studio

• www.saphanatutorial.com

FREE website which has been created to provide quality online education to the people who are enthusiastic to study different technical and non-technical aspects about SAP HANA

35

7 Key Points to Take Home

Start Small – Simple calculation view and data model.

Don’t build for a wide community. Try something simple.

Keep the end goal in mind

Minimize the number of layers

Merge data in DSO and build HANA models on it.

Will eliminate need for cubes.

Use either HANA models or traditional BW, but don’t use both

Be careful with data loads. Consider going to the source system when it

makes sense. Master Data should be taken into account.

Security! Understand upfront the implications of applying security in

Native HANA vs Traditional BW.

36

Special Thanks!

• Ado Ajanovic: Dashboard/BOBJ Developer – Newell Rubbermaid

[email protected]

• Ketan Doshi: BW/HANA Architect – Newell Rubbermaid

[email protected]

• Girdhar Shingala: BW/HANA Development Manager – Newell

Rubbermaid

[email protected]

• Entire BI and Basis team for all the help and support

mailto:[email protected]



37

Your Turn!

How to contact us:

Rajeev Kapur:

[email protected]

Roger Sauvageau:

[email protected]

Please remember to complete your session evaluation

38

Disclaimer

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or

an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective

companies. Wellesley Information Services is neither owned nor controlled by SAP SE.

case study: lessons from newell rubbermaid's sap hana proof of concept

Technology