Increase BW success by 70 percent

Download
Share  Add to  Flag Embed
Uploaded from authorPOINTLite
Views:
 
Category: Entertainment
     
 
License:   All Rights Reserved

Presentation Description

No description available.

Comments

 

By: manojreddy (44 month(s) ago)

hello authorSTREAM, this is manoj presently doing MBA, i would be very much greatful if you send me this ppt. thank you

 

By: gvlkiran (54 month(s) ago)

please send me this PPT kiranind3@gmail.com

 

By: skmailhere (54 month(s) ago)

please sent SAP BW ppt.

Presentation Transcript

Increase BW success by 70%: 

Increase BW success by 70% Hari Guleria icm AMERICA

Brief on icm: 

Brief on icm 19 offices in Europe and US with over 500 employees 100% senior SAP resources BW TRACK RECORD Ranked # 5 globally for BW implementations 21 BW Projects completed 16 BW projects underway FPS partner in 3.0x (have 3.0A since Oct 2001, 3.0B since June 2002) 2 icm employees on SAP AG BW Development board COMPANY TRACK RECORD Area Projects Completed Upgrades 100 Data Archiving 68 BW 21 RBE/CBI 36 System Mergers 07 Area Projects Completed APO 03 SEM 02 eBusiness 10 CRM 02 SAP Implementations 176

Slide3: 

SAP Reporting Options Plan your work & work your plan

Where we are: 

Where we are Start: PLAN Reporting & Analytics The Business Reason The success factors in BW implementations Data Modeling Data design selections End: REPORTING - Queries and Analytics

Primary Reason : 

Primary Reason Every DW is initiated for reports, analytics and/or as a data repository. With reports as the end, only a planned beginning can assure success To ensure successful Reports and Analytics from the BW we must: Collect and document all Reports/ Analytic requirements Model all requirements by source and computations The modeling phase must isolate 90% of issues and gaps Then deliver the required reports and analytics Reporting v/s M I S Queries and Analytics

Sample Business Reasons: 

Sample Business Reasons Supply chain informatics Accurate PO and Vendor information (info) Accurate Production capacity, output, rejections and shipment info Customer and material reporting Consolidated customer and material info across companies and regions Margin analytics by selection Margin by total company, partner companies, regions, sales offices, materials, customer and material groups, etc Accurate up to date and online stock information Material and valuation from every partner storage location Tactical and Strategic information Competitive analytics by market segments and regions Service offering trends and projections and their impact on Operations

BW 3.0x options and ROI: 

BW 3.0x options and ROI BW 3.0x Pure WEB Query Designer SAP Non SAP Legacy APO SEM CRM BW DW CAPTURE Downward Integration Upward Integration

Where we are: 

Where we are Start: PLAN Reporting & Analytics The Business Reason The success factors in BW implementations Data Modeling Data design selections End: REPORTING - Queries and Analytics

The 7 Steps of success (SF*): 

5 reasons contribute to 70% of the success of all data warehouse projects. 2 the balance 30% Define Business Reasons Proven Methodology Implement POC / CRP From a Workshops to a Pilot ‘Proof of Concept’ Conduct detailed Multi-dimensional data-modeling Plan your Reports and Analytics Experienced Partner selection Planned procedures, documentation and knowledge transfer The 7 Steps of success (SF*) * SF = Success Factor

SF 1 – Methodology: 

SF 1 – Methodology * SF = Success Factor

SF 1 – Methodology II: 

SF 1 – Methodology II Collect Reports and document Current reports from production systems with ID Reports being generated off-line with ID Wish List reports not yet generated Code and track Report requirements Define and plan Dimensions, Characteristics, Attributes, and ‘Key Performance Indicators’ Map Data-Flow Reports Track KPI’s 40B > 46C1 * SF = Success Factor

SF 1.2 – Proof of Concept: 

SF 1.2 – Proof of Concept Must be followed after a overview understanding of BW functionalities, i.e. in workshops Also known as CRP ‘Conference Room Pilot’ demonstration – WHY is this important Essential for end-users to understand the functionalities and limitations of BW Imperative for answering data-modeling questions for designing the BW Imperative for defining KPI’s, Calculations, formulae, change data management, etc * SF = Success Factor

Where we are: 

Where we are Start: PLAN Reporting & Analytics The Business Reason The success factors in BW implementations Data Modeling Data design selections End: REPORTING - Queries and Analytics

Data modeling: 

Data modeling ..without a clear goal at the end of design beginning the design phase becomes Totally redundant.. The BW is just a repository between your source and requirements * DM = Data Modeling

Work Plan: 

Work Plan Company 1 70:30 1 week gathering all reports 2 weeks coding the reports 1 week defining business drivers 1 week defining KPI’s 2 weeks data modeling 5 weeks constructing 1 week debugging 4 weeks reporting Company 2 10:90 2 weeks gathering reports Little coding Assumed business drivers Assumed KPI’s ½ day data modeling 5 weeks constructing 1 week debugging 2 week reconstructing 3 days debugging 2 week reconstructing 3 days debugging 2 week reconstructing 2 days debugging 4 weeks reconstructing …… * DM – Data Modeling

Reports and Analytics: 

Reports and Analytics 2 primary reason’s for every BW (1) Reports and Analytics, (2) End User Do not ever forget the End User, they are the key to the success of every BW. Involve them No single OLAP tool will ever meet all end-user requirements. Start with BEx as the beginning tool Analyze vendors on differentiating factors (Requirement v/s how each product compliments BEx) * DM – Data Modeling

Delivered v/s Customization: 

Delivered v/s Customization Data Modeling requirement The higher the customization higher is the Data modeling requirement DM = Data Modeling

BW Information Architecture: 

BW Information Architecture DM = Data Modeling

BW Snowflake Star-Schema: 

BW Snowflake Star-Schema Big Leap = 13 Dimensions = x Dimensions Each DIM can take 248 Characteristics = Dimensions Total Dimensions possible in BW = 13 x 248 = 3,224 DM = Data Modeling

ERM : 

ERM DM = Data Modeling

ERM > Star Schema: 

ERM > Star Schema Plan Granularity DM = Data Modeling

DM-2 __ Star Schema > InfoCube: 

DM-2 __ Star Schema > InfoCube DM = Data Modeling

Plan & Strategize: 

Plan & Strategize DM = Data Modeling Change of data management, I.e. Customer in Region 1 goes to region 2 in the future Dimensions, Characteristics, and attribute relationships – and their multi-dimensional relationships SID table functionalities and plans, I.e. time dependant or not Other Hierarchies, Partitioning & Compression, Navigation Attributes, Variables, Reporting alternatives, etc

Trade offs: 

Trade offs Granularity (detail) v/s space, access speed Navigation Attributes (ease) v/s speed Aggregation (speed/ease) v/s no detail Partitioning (segregation) v/s single point of access Design (planned) v/s random growth and confusion Archiving (space) v/s historical access Compounding objects (identity) v/s loss of uniqueness Performance (easy of use) v/s all above Roll-up Planning (planned) v/s fire-fighting DM = Data Modeling

Where we are: 

Where we are Start: PLAN Reporting & Analytics The Business Reason The success factors in BW implementations Importance of Data Modeling Data Modeling Data design selections End: REPORTING - Queries and Analytics

Design Criterion – 1 Rules of changes: 

Design Criterion – 1 Rules of changes DM = Data Modeling

Where we are: 

Where we are Start: PLAN Reporting & Analytics The Business Reason The success factors in BW implementations Importance of Data Modeling Data Modeling Data design selections End: REPORTING - Queries and Analytics

Reporting Options: 

Reporting Options Standard BEx (modified MS Excel) Approved BW OLAP vendors Integrating reports in the SAP Portal system: mySAP Workplace (now SAP Portal): Drag & Relate, MiniApps Running reports against the SAP Business Information Warehouse (BW): SAP BW: ODBO/BAPI* Running reports against SAP, and non SAP sources: SAP R/3: RFC/BAPI**/ conversions

OLAP Vendors: 

OLAP Vendors VENDOR Product SAP R/3 BW Other SAP BEx  arcplan dynaSight    Brio Brio Report, Query   Business Objects Bus Query, WebIntell  Cognos Power Play, Visualizer   Comshare Decision  Crystal Decisions Enterprise, analysis    ESRI Connect  IBI WebFOCUS  MIS Alea, OnVision   SAS Enterprise Guide  Viador E-Portal Suite 

OLAP Vendors – S&W: 

OLAP Vendors – S&W

OLAP Vendors – Analysis: 

OLAP Vendors – Analysis

InfoCube to Query Relationship – 1: 

InfoCube to Query Relationship – 1 End-User Doc

What a BEx Report contains: 

What a BEx Report contains

REPORT 1 – BEx Query A: 

REPORT 1 – BEx Query A

REPORT 2 – BEx Query B: 

REPORT 2 – BEx Query B

REPORT 3 – Enhanced MIS: 

REPORT 3 – Enhanced MIS

Takeaways : 

Takeaways PLAN YOUR WORK AND THEN ONLY WORK YOUR PLAN Follow tried methodologies, and proven templates (do not try and reinvent the wheel) Define Business Content Gather Reports and Analytics requirements Implement Proof of Concept 20% Commence Data Modeling 40-50% Partner with an experience Get Steering committee approval on reports and models Get USER commitment on reports and expectations Construct and Configure the BW Select OLAP tools and options GO Live Post go Live plan and work }

1 slide to tell it all: 

1 slide to tell it all plan it, understand it, schedule it, manage it

Your Turn: 

Your Turn Hari Guleria icm AMERICA hguleria@icm.de Mobile:(408) 835-9552 Off: (610) 647-9000 ext 4835 www.icmamerica.com

Questionnaire format: 

Questionnaire format Email: hguleria@icm.de Fax: 610.647.9177