accelerated access to bw al weedman idea integration
Post on 21-Dec-2015
217 views
TRANSCRIPT
BW Overview
Building a data warehouse will give your organization the ability to analyze information that is currently hidden within SAP R/3 (or other transactional systems).
BW Overview
Data Provision• ETL (Extraction, Transformation, Loading)• Operational Data Store (ODS)• Multi-dimensional data storage• Metadata support
Service Provider• Ad-hoc querying and data distribution to downstream systems• Aggregate data generation and aggregate aware reporting
Warehouse Management• Scheduling• Data flow management
Functionality Supported by Data WarehousingFunctionality Supported by Data Warehousing
BW Overview
In Order to Build an Effective Data Warehouse You Would Need:In Order to Build an Effective Data Warehouse You Would Need:
ETL Tool with SAP Extractors (Like Data Stage or Informatica)
Scheduling/Monitoring Package Tool (Like Maestro)
Metadata Management Tool (Like Meta Stage)
DW Database Engine (Like Oracle)
Robust Reporting Tool (Like Business Objects, Crystal, or Cognos)
Data Modeling Tool (Like Erwin or Silverrun)
Integrate all of those tools and developed pieces so that they can work together
BW Overview
SAP’s data warehouse solution All components of a traditional data warehouse in one package
A multi-dimensional database
Integrated with the mySAP suite of products
Business Intelligence (BI)
What is BW?What is BW?
BW Overview
Advanced functionality to manipulate data (OLAP)
Quickly retrieve values using any combination of characteristics
Data from R/3 and external systems can by cleansed and merged together
Business Content!!
Some BW FunctionalitySome BW Functionality
BW Overview
Map reporting (GIS)
Publish to the internet / WAP
SAP Portals integration via iViews
Drill through to R/3
3rd Party reporting software can be used (Business Object, Cognos, Brio, etc.) through the ODBO interface (Microsoft standard).
Some BW Functionality ContinuedSome BW Functionality Continued
Steps to Bring BW Live in 30 Days!
Project plan
Number of stakeholders
If falling behind, the decision must be made as to whether solving the individual problem is worth missing the deadline.
PlanPlan
Steps to Bring BW Live in 30 Days!
Size the system and find a server• How many users?
• How much data?
• Verson 3.0b / 3.1c runs on the 6.20 BASIS kernel. WAS built in!
• Operating system / Database / BW version matrix on SAP.com
Install BW software
Install plug-in on R/3 if needed
Install patches
1 - 2 weeks
Pre-Project InstallationPre-Project Installation
Steps to Bring BW Live in 30 Days!
6.20 GUI with BW content checked
Front-end patches. Now self-extracting .exe files
If web front-end desired, a huge advantage is that no client based software is required
Change management / training may be required depending on user base and scope of the project
Roll-out GUI to the User Base throughout the ProjectRoll-out GUI to the User Base throughout the Project
Steps to Bring BW Live in 30 Days!
What information would give your project and your business the most value in the time allotted?
Is there BW business content available? BW, R/3 extractors are very powerful. Use them if at all possible.
User exit on the R/3 side allows non-business content data to be merged with business content.
Follow good BW design practices
1 week
BlueprintBlueprint
Steps to Bring BW Live in 30 Days!
Configure system-wide settings in BW (currency conversion, fiscal calendars, etc.)
Configure extractor(s) in R/3 if required
Develop and/or install master data in BW
Develop and/or install InfoCubes, ODSes, Transfer Rules, Process Chains, etc., in BW
Load test data
Write queries
RealizationRealization
Steps to Bring BW Live in 30 Days!
Publish to web if in scope
Develop process chains - new 3.0 functionality
Security / role based
Apply OSS notes as required
Unit test
QA - system / integration test if in scope for your project
2 weeks
RealizationRealization
Steps to Bring BW Live in 30 Days!
Initialization for deltas or full loads?
The more historical data you load into BW during initialization, the longer your go-live will take.
Do users need to be out of R/3 during initialization?
Parallel out loads whenever possible
OSS notes as required
1 week
Go-liveGo-live
Production Support
Think about a production support processes ahead of time
If jobs are critical and are monitored 24/7, your operations department must be trained on how to use the monitor functionality in BW
Otherwise custom developed processes can be used to externally monitor BW jobs
If jobs are not critical, get in the habit of checking the monitor every morning
Next Steps
Add more standard business content
More complex custom content
Perform a requirements analysis throughout your organization for appropriate KPIs to deliver
Incoming RFI requests
SEM
Publish queries to the internet / SAP Portals
Add more robust security to existing content
Merge legacy system(s) data