1813 Lessons Learned in Leveraging SAP BI

7/29/2019 1813 Lessons Learned in Leveraging SAP BI

1/23

]

Orange County Convention CenterOrlando, Florida | May 15-18, 2011

Lessons learned: Leveraging SAP BI to meet needs of both Finance and HR users groups

Rakesh TripathiThe Capital Group Companies


2/23

Real Experience. Real Advantage.

[

2

Agenda

Learning Points The Capital Group Companies, Inc. (CG) Reporting Requirements of HR and Finance users BW Solution Approach and Challenges

Best Practice

Feedback and Contact


3/23


[

3

Learning Points

Different business groups have different perspective whileleveraging same data. Flexibility of SAP BW in meeting different set ofrequirements of same data. Importance of data governance. Challenges in meeting analytical requirements withsensitive data.


4/23


[

4

Agenda

Learning Points The Capital Group Companies, Inc. (CG) Reporting Requirements of HR and Finance users BW Solution Approach and Challenges

Best Practice

Feedback and Contact


5/23


[

5

The Capital Group Companies, Inc. (CG)

Who We Are

Founded nearly 80 years ago

Privately held Home of American FundsOur customers Individual mutual fund shareholders Companies that offer 401(k) retirement plans Institutional clients High-net-worth individuals


6/23Real Experience. Real Advantage.

[

6

The Capital Group Companies, Inc. (CG) Contd..

SAP History at CG

1998 2003 SAP ECC implementation

Finance modules (GL, CO, FI, Fixed Assets)

2004 2007 SAP BW Implementation

Finance modules (including custom) and HCM (PA) data

2006 2007 SAP ECC extended to CG Central Services

Learning Management System (LMS)Portal and Human Capital Management (HCM)

2010 SAP BW ImplementationEnterprise Compensation Management (ECM)

Salary, Bonus, Appraisal, Compensation PlanningPersonnel Administration (PA) extended to HR users

Actions, Headcount, Personal Data



[

7

Agenda

Learning Points The Capital Group Companies, Inc. (CG)

Reporting Requirements of HR and Finance users

BW Solution Approach and Challenges Best Practice Feedback and Contact



[

8

Reporting Requirement (HR vs. Finance)

Headcount/ Actions Compensation Data

Finance

Numbers frozen (Snapshot)

monthly

Board reporting for headcount

Headcount drives costallocation for Company Code& Cost Centers

HR

Location and Org. hierarchybased analytical reporting

Demographic, attrition rateinfo.

Finance

Analytical reporting based on

company code and cost center

Account for % split acrosscompany code and cost centers

HR

Summarized compensationplanning

Performance reporting



[

9

Agenda






[

10

BW Solution Approach : Historical Perspective

Finance HR

Custom database for monthlyheadcount reporting

No link between headcountand actions

No analytical reporting

capability

Manual compensationreporting (allocations andsplits)

Inconsistency with HR reports

PeopleSoft

Operational reporting

Inconsistency with Financereports



[

11

BW Solution Approach : BW Maturity

Earlier BW initiatives Developer created reports

Business dependent on IT

Recent BW initiatives Focus on data set

Business less dependent on IT

Important to include use case scenarios in design



[

12

BW Solution Approach: Employee data

Important to carefully plan and implement employee master data

How many attributes need to be time dependent?

Analyze whether source is sending time delimited records

Data load performance (volume of load and technical reorganization)

Which attributes need to be navigational?

Analyze usage and query performance

Which attributes need to be flagged sensitive?

Analyze usability and performance

Are there back dated corrections?

Analyze impact on data accuracy of employee attributes stored in thecube



[

13

BW Solution Approach: Employee Data Cont..

3)Custom DB

4)ECC 2

1)ECC 1

2)BI

ECCPA008

Extractors

1. ECC (SAP Std. Enhanced)2. BI Internal3. Custom database4. ECC2 (Custom extractor)

Key Facts

1. Plan and review Impact of back datedchanges on accuracy of data.2. Plan and review impact due to sensitivedata



[

14

BW Solution Approach: Employee Data Cont..

Employee Data Reorganization

This BW feature is used to review and mergetime delimited records wherever possible.

Employee data in BW may have data load from

various sources.

The attributes are usually a mix of timedependent and non time dependent attributes.

A new entry is created in the employee master

data in case of a change in one of the timedependent attributes.



[

15

BW Solution Approach: Headcount & Actions

Key Facts1. Current cube is daily drop / reload2. Previous months are frozen2. Separate multi providers for HR and Finance3. Monthly review of data and correction requests

Reporting Challenge

1. Historical reporting due to not assigned nodes

of Org Unit Hierarchy2. Understanding of Data Definition3. International Assignment and Transfers

CurrentCube

Prior MonthCube

Actions Headcount Custom DB

HR Reports Finance Reports



[

16

BW Solution Approach: Compensation Mgmt.

Key Facts

1. Separate multi providers for HR and Finance2. Employee attributes are read and storedwhile loading data into the cube3. Employee attributes are in sync between PAsolution and comp. solution

Reporting challenge

1. Conflict in analytical reporting due to change

in structural authorization2. International Assignment and Transfers3. Understanding of data definition



[

17

BW Solution Approach: Data Correction Requests

Sample Requests Employee Delete requests Future hires need to be manually deleted from thesystem if they decide not to join Headcount/ Action correction requests

This may be necessary for prior month based on monthlyreview between F&A and HR group

Process

Business initiates the request by populating necessaryinformation in a form

IT processes the request and requests validation



[

18

BW Solution Approach: Key Issues Encountered

Legacy data quality Review, prioritize and fix Back dated changes resulting in data correction requests. Aggressive monitoring and process modification to reduceoccurrence BW Accelerator out of Sync Instituted better monitoring and alert mechanism



[

19

BW Solution Approach: Authorizations

Multiple level of authorization implemented. Line of Business, Manager etc. ECC vs. BW authorization Business would like to have consistent end result Security implementation in the two systems will defer due todifferent features Conventional and structural authorization Daily drop and reload of structural authorization



[

20

BW Solution Approach: Sensitive data Impact

Non production system refresh Scrub of sensitive data

Review of BI Team access (for production support)

Select few to have sensitive data access Review of access for System Admin group.

Probably need full access



[

21

Agenda






[

22

Best Practice

Identify use scenarios and incorporate those into thedesign. Socialize the proposed solution early on and establishexpectations. Establish a review group to look into concerns and jointapprove change requests. Review the impact due to sensitive data early andallocate resources. Plan for performance test. There may be impact due tosecurity implementation.


23/23

[

Thank you for participating.

SESSION CODE: 1813

Please remember to complete and return your

evaluation form following this session.

For ongoing education in this area of focus, visitwww.asug.com.

1813 Lessons Learned in Leveraging SAP BI

Documents

Transcript of 1813 Lessons Learned in Leveraging SAP BI