17
Lessons Learned from the Vodafone HANA Project Vodafone, Accenture and SAP KHNC - 20 th February 2013

Lessons Learned From Vodafone HANA Project.pdf

Embed Size (px)

DESCRIPTION

Best Practices and Lessons Learned from Vodafone’s SAP HANA Implementation - Presentati

Citation preview

Page 1: Lessons Learned From Vodafone HANA Project.pdf

Lessons Learned from the

Vodafone HANA Project

Vodafone, Accenture and SAP

KHNC - 20th February 2013

Page 2: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 2

Agenda - KHNC

• Project Scope and Benefits

• Detailed Requirements

• Detailed Modeling examples

• Next steps for Vodafone

• Q&A

Page 3: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 3

Vodafone Overview

Company: Vodafone Group Plc

Headquarters: Newbury, United Kingdom

Industry: Telecommunications

Products and Services: Network, mobile, and data communications

Employees: 86,000

Revenue: £46 billion (€57 billion)

Web Site: www.vodafone.com

Implementation Project Team: Accenture, SAP Field Services, TIP CSA

Page 4: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 4

• Implementation of HANA as a Data Mart (ERP side car) to speed up Vodafone

MEC (Month End Close) process

• Real Time Data Provisioning via SLT (PRD: >30 Tables and 1Bn rows of data)

• Use of the Analysis for Office reporting client, to deliver reports directly in Excel.

• Administration and End User Training for 35 users distributed globally

• “Live” Proof Of Concept – 2 months in June/July 2012

• Implementation into Production – 3 months (much of that time spent testing) with

a Business Go-Live mid-November 2012.

Project Scope

Page 5: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 5

Project Scope: SAP side architecture

SAP BO BI 4.0

SAP HANA SPS4, Rev 36

SAP ECC 6.0, EhP7

ERP RDBMS (Oracle) In-Memory DB

Analysis for Office

1.2 SP8

CSKS

Attribute Views

Analytic Views

Calculation Views

Analytic Privileges

HANA

Operational

reporting for

Month End

Close

BKPF

In-Memory

Modeling Studio

CE4XXXX_ACCT

SLT Server

DMIS SP07

BSEG

DMIS

SP07

Page 6: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 6

AS IS Process – Reporting Financials Data to Group

ECC (GL & COPA

Data)

Automatic

Manual

User manually

launches trx

ZFINHFM001 in

BI

Flat Files(one

per entity +

VGS) are

extracted and

saved on

shared drive

Manual

2 M

HFM

M1

3

Files are

transferred

automatically to

HFM

If results of HFM reports are not satisfactory from a reporting point of view, the changes

are done either in ECC (long waiting time 90-150 min before seen them reflected in BI, or in

FDM/HFM directly and then posted back in ECC (this brings the risk of potential point of

misaligned in the systems).

5

Ei

FDM

E1

Files are manually uploaded into FDM.

Manual changes should not performed but

the actual process allows it. (Doing in ECC

requires waiting time to see changes

reflected in BI).

2a

C1

HFM report

is generated

4

BI

ECC extraction every: 90 min

BI refresh time: 60 min 1

Page 7: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 7

HANA Phase 1 -

HANA

Real Time

Replication

1

ECC (GL & COPA

DATA)

BI

ECC extraction every: 90 min

BI refresh time: 60 min

If results of HFM report are not satisfactory form a reporting point of view, the

changes are done in ECC and will be immediately available in HANA for a subsequent

submission to HFM.

5

2

User extract

flat Files with

real time data

using Analysis

for Office.

Manual

Ei

FDM

E1

Files are manually uploaded into FDM.

2a

M

HFM

M1

Files are

transferred

automatically to

HFM

3

HFM report

is generated

C1 4

Automatic

Manual

Page 8: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 8 Copyright © 2012 Accenture All rights reserved. 8

Business Process Improvements

Max Total

time:

155min

Max Total

time:

5min

30 times faster! / 97 % reduction!

Business

Process

AS IS

HANA

BW Data Loads

and Aggregation ECC Postings Extraction for HFM

BW Data Loads

60 min

ECC Postings

BI Extraction every 90 minutes

5 min

After the BI Refresh

ECC Postings (anytime when required by the business)

HANA with SLT Replication (real time)

Extraction for HFM – 5 min

(anytime when required by the business)

End-user Posting

End-user Posting

HFM Update

HFM Update

Page 9: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 9

Currently live in production globally with HANA

By generating key financial reports in real time that used to take hours every time

they were run, SAP HANA saved a day out of the seven-business-day process

Helped the company gain labor efficiency benefits over the next 4 years

96% Reduction in data extract, processing, and load times

“Month-end closing is a highly visible and critical application at Vodafone. Speeding it up was

very valuable in its own right, as well as a great first application of SAP HANA to demonstrate

its power to the company.”

Valentina Del Frate, Project Manager, Vodafone Group Plc

“For the first time ever I can post an entry and see its impact on HFM after minutes. Thanks

for everyone contributed in HANA.”

End User, Vodafone.

Project Benefits

Page 10: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 10

34 tables required to be loaded to HANA via SLT and joined together in a

model to produce csv output for HFM (Vodafone’s 3rd party consolidation

tool at present).

To generate the Output file, the user was allowed to choose a Fiscal

Year, a Fiscal Period and one or many HFM Entities. (An HFM Entity was

a group of one or more SAP Company Codes)

There were 20+ COPA tables of the form CE4XXXX_ACCT where XXXX

was a different Operating Concern (DE01, GB01 etc).

The output format for HFM was 20 columns and expected to be only

thousands of rows long, however HANA had to sift through billions of

rows to arrive at that final output list during each user query

Detailed Requirements (1)

Page 11: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 11

The population of the Output was defined differently for different groups

of GL Accounts. (For example GL Accounts with a number starting between 10… and 49… had

one set of rules on how to populate each of the columns of the output file (sometimes some fields were

required to be set to initial values for example) whereas GL Accounts with a number starting between

50… and 69… had another set of rules on how to populate each of the columns of the output file)

An iterative lookup of the Movement Type over prior fiscal years (typically

handled by ERP itself in Application logic above the BSEG Cluster table)

was also required to be modeled

Numerous instances of Bad Data from ECC that had to be covered up

with some creative modeling in HANA

User interaction was required with the final output from HANA as well as

a reconciliation report

Detailed Requirements (2)

Page 12: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 12

BKPF as Attribute View (keeping

BSEG as only table in Analytic

View Data Foundation)

Filters on BSTAT in BKPF

Use of TKA02 as KOKRS not

always reliable from BSEG

HFM Mapping table inclusion

Detailed Modeling Examples – First Steps. Attribute Views.

CSKS static filter for time

dependent data

Calc View as

workaround for

unexpected ECC data

Page 13: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 13

BSEG as only table in Analytic

View Data Foundation

Filters on HKONT for relevant GL

account number ranges

Detailed Modeling Examples – First Steps. Analytic Views.

Intentionally a very

simple Analytic View. No

Calc

Attributes/Measures.

The Final Live POC

Analytic View only for

Spanish Operating

Concern

Page 14: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 14

Detailed Modeling Examples – First Steps. Calculation

Views.

Projection Node above

each of 4 „Vanilla“

Analytic Views for

uniformity and filter

expressions functionality

Filter Expressions

passed down to lowest

level Analytic Views

(confirmed with PIRT

trace)

("GJAHR" ='$$FYEAR$$' and "MONAT" <='$$FPERIOD$$') OR "GJAHR" <'$$FYEAR$$'

"GJAHR" ='$$FYEAR$$' and "MONAT" <='$$FPERIOD$$'

Page 15: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 15

Detailed Modeling Examples – Final Calculation View

Additional complexity of many

Operating Concerns.

Single Calculation View desired

Design is for majority of nodes to

bring back zero values very very

quickly

Deployment of Analytical Views to

Join Engine helped in this case

Other Thoughts: Table partitioning,

CE4 Mega table idea to be

revisited

Page 16: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 16

HANA MEC Phase 2 – Planned

Go Live in March 2013.

A set of 5 BO WebI reports

enabling the business to analyse

financial data before the HFM

submission.

Non-SAP data (complex

mappings) upload in HANA using

BO Data Services.

Complex „on the fly“ mapping

modeled with HANA Calculation

Views.

Next Step – Real Time Reporting with Business Objects

HFM Files:

Mapping,

Text,

Hierarchy

Da

ta S

erv

ice

s

In-Memory

HANA

Real-time

Replication

FDM

Mapping

Input P&L Balance Sheet CAPEX Data Analysis

Cash Flow

EVO

EVO Tables

General

Ledger

COPA

Mater

Data

Business Objects

Page 17: Lessons Learned From Vodafone HANA Project.pdf

© 2011 SAP AG. All rights reserved. 17

Further HANA Opportunities

Acceleration of ECC reports:

GL and Asset Accounting

BW on HANA (partial

migration) for Finance data

flows.

Mobile reporting for executives

In-Memory

HANA

Real-time

Replication

ECC

BW VIP

(OHP)

Non

SAP

HFM