Business Intelligence111

SAP Business Intelligence
Delta Training BW 3.5 to SAP NW2004s Training Material Version 1.1

Created on: Feb 2007 Last updated on: Feb 22, 2007
Copyright 2004 Accenture All Rights Reserved.
Agenda
Name of the section
Delta Training from BW 3.5 to NetWeaver 2004s BI
Objective
To understand what are the new offerings and changes in NetWeaver 2004s BI and its various applications.
Pre-requisites
Knowledge of SAP BW 3.X.
Contents
SAP NetWeaver 2004s - Day 1 New Features in NW 2004S (BI 7.0) - Day 1 Data Modeling EDW: - Day 1 Data Modeling (new DSO types, remodeling) Data acquisition (new Data source concept, remote access capability) Transformation Data flow (Data transfer process, RDA) Administration & monitoring (Process chain, administrator cockpit) BI Accelerators. Enterprise query, Reporting and Analysis Query Designer BEx Analyzer Excel Integration Information Broadcasting Document Browser Information Lifecycle Management Near Line Storage Offline Storage BI Integrated Planning - Day 2 - Day 2
- Day 2
- Day 2
SAP NetWeaver 2004s
SAP NetWeaver 2004s

With Business Intelligence (BI), SAP NetWeaver provides data warehousing functionality, a business intelligence platform, and a suite of business intelligence tools. Business information from productive SAP applications (R/3) and all external data sources can be integrated, transformed, and consolidated in BI with the toolset provided. Flexible reporting, analysis, and planning tools to support evaluating and interpreting data, as well as facilitating its distribution.
New Features in NW 2004S (BI 7.0)

Old Term
Reporting authorization
New Term
Analysis authorization
New terms definition

An improved type of reporting authorization that gives you control over authorization of navigation attributes
Transfer Rules/Update Rules
Transformations
Rules for data transfer. Consists of start Routine, End Routine and express routines. (Transfer Rule + Update Rule = Transformations) An improved version of the ODS object A DataStore object that queries the write-optimized DataStore object with BEx tools An SAP NetWeaver BI object to facilitate the load from a source system to PSA only An SAP NetWeaver BI object to aid with follow-on loads and transformations in SAP NetWeaver BI. DTPs are used for loading data from PSA to data targets.
ODS object Transactional ODS
DataStore object Direct update DataStore object InfoPackage
InfoPackage
Data transfer process
Data transfer process (DTP)
New Features in NW 2004S (BI 7.0)

Old Term
SAP Enterprise Portal 6.0 VirtualProvider RemoteCube --
New Term
SAP NetWeaver Portal VirtualProvider HPA

Provides a roles-based GUI and single sign-on BW does not manage the transaction data for this type of InfoCube A feature that improves query performance by combining hardware technology improvements with the existing SAP NetWeaver TREX search engine features Allows you to redesign SAP NetWeaver BI data targets A DataStore object that allows you to transform large sets of data more efficiently. Built in NLS (Near Line Storage) available. Performance optimizers. Separate box with 64 bit processor. Combination of hardware and software. Caching for multiproviders. Define number of parallel processes.
7
-----
Remodeling toolbox Write-optimized DataStore object NLS BI Accelerators
--
Delta caching
Data Modeling EDW

SAP NetWeaver 2004s provides additional flexibility for implementing new data models and changing the existing ones
Data Warehousing Workbench as successor of Administrator Workbench

Improved Usability
Split into modeling and administration aspects New InfoCube maintenance UI Display complete dataflow from source to target Integrated Object Editor New navigation possibilities
Data Warehousing Workbench
EDW Main process overview

Data Modeling
Data modeling supports and facilitates highly flexible and comprehensive information models. In particular, it enables an EDW layering that also supports future information requirements.
Meta Data & Document Management

Meta data and documents must be managed, searchable and open with respect to exchanging them with other systems. Documentation on meta data should be generated.
Data Acquisition
Data acquisition plugs your SAP BI to various (heterogeneous) source systems either via direct BI connections or via SAP Exchange Infrastructure. It also includes remote connectivity to source systems
Transformation
Transformation is the main process for data consolidation, cleansing and integration. Data from possibly heterogeneous sources can be semantically synchronized here.
Data Distribution
In addition to querying on the data residing in the Data Warehouse, data can also be distributed to other warehouse in case your EDW landscape consists of several warehouses.
10
Data Modeling EDWDSO types

Three different types of DSO objects Standard type with known tables (Active, Change Log and Activation table). Direct update with only the active table usable for analysis processes Write optimized with only the active table usable for large amount of records.
Versions of data BEx access Usage EDW layer ODS layer Delta determina tion X Fast access (no activtn) Other Structure Active data Chan ge log Activtnq ueue Integration
DSO object type
Standard
Active, modified, delta Active
Via data transfer process Via data transfer process Via API Functions
Writeoptimized
Especially for large sets of data Also for use by the Analysis Processes Designer (APD)
Direct update
Active
Active
11

Enhanced DataStore objects (formerly: ODS objects)
Improved performance and flexibility Performance optimization of activation process New DataStore Type: Write-optimized DataStore (without change log, no activation, Partitioned on request ID)
Example for Write-optimized DataStore Object

Staging of large volumes of document data with unique key into fast inbound layer Data can be directly written into the DataStore without activation The request information enables further processing/update of the data Missing change log does not allow delta determination of multiple records with the same key
12
13
Data Modeling EDWEnhanced InfoSets

Enhanced InfoSets
Improved flexibility Integrate InfoCubes into join condition
Example for new InfoSet features:

Slow-sellers analysis Define outer join condition between article master data and sales InfoCube Result: all articles even those, which have not been sold Transitive Attributes Join InfoCube containing material to InfoObject material and join material to InfoObject material group Now you can also use the (transitive) attributes from material group
14
15

New transaction available: RSISET The capability to join InfoCubes as part of InfoSets results in much more flexible objects. For example, can easily create a report of slow or no sales customers via an outer join between master data 0CUSTOMER and InfoCube 0SD_C01. Result: all articles even those, which have not been sold. In addition, ability to link an InfoCube to an InfoObject, and this InfoObject to another InfoObject, which gives you access to an attributes attribute, known as a transitive attribute. Join InfoCube containing material to InfoObject material and join material InfoObject material group. Now you can also use the (transitive) attributes from material group. With improvements to temporal joins and the ability to link to an InfoCube, you could create a pseudo-historical truth report. Example by linking the day of the sales transaction in the InfoCube and timedependent master data attributes without including these in the star schema.
16
Data Modeling EDWRe-Modeling Toolbox

Re-Modeling Toolbox:
Changing InfoCubes without rebuilding them from scratch improved flexibility Remove, exchange, replace, add and fill dimension characteristics and key figures Information: during (dictionary - based) conversion process, queries are not possible; aggregates will be automatically deactivated and must be rebuilt afterwards
17
18

Impact
During the conversion process, reading (querying) and changing the InfoCube is locked. All depending objects (queries, transformations, MultiProviders etc.) will be deactivated and have to be adjusted manually. Aggregates and HPA must be rebuilt after the conversion.
Authorization
Same authorization objects apply as for the InfoCube maintenance.
OSS Component
BW-WHM-DBA-RMT
19
Data Modeling EDWBusiness content

Content Analyzer
New Tool which is delivered with SAP NW2004s Content Add-On 2: Analysis of BI content objects with respect to errors and inconsistencies Easy access and determination of the results of analysis Extensive reporting possibilities based on the results of analysis Role-specific deployment: analysis (administration) and reporting (governance)
20
Data Modeling EDWBusiness content

Content Browser
New standard business content objects. The content browser helps customer getting a clear overview about business content which is applied in the customers SAP NetWeaver BI and provides an easy way to find out the appropriate standard business content:
Overview about business content in a given area (e.g. CRM, SRM etc) Usage of customer-defined content and SAP standard content Relationship between different content objects
21
Data Modeling EDWData Acquisition

SAP NetWeaver 2004s improves and streamlines the data source definition. In addition, it enhances remote access capabilities
New DataSource Concept

Unified and improved maintenance E.g. Web Service (XML), UD Connect Additional DataSources enabled for remote access (including flat files and DB Connect)
Enhanced remote capabilities

Remote master data access no data replication, low TCO Remote access of master data from source systems
22
Data Modeling EDWDataSource
23
24
25

DB Connect Data Sources
Powerful native SQL connection to all DB platforms of SAP NetWeaver AS Enable via multi connect feature of the SAP NetWeaver AS DB Interface Enhanced with preview features now Direct Access to the external DB in a remote scenario now also possible even for master data during query processing
26
Data Modeling EDW- 3.x DataSources in NW2004s
27
Data Modeling EDWFile Adapter Extraction
28
Data Modeling EDWFile Adapter Proposal
29
Data Modeling EDWFile Adapter Fields list
30
Data Modeling EDWFile Adapter Preview
31
DM EDW-Emulated view on Classic Data Source
32
DM EDW-Delta Process Types-Emulated 3.x DS
33
DM EDW-Delta Process Types - Emulated 3.x DS
34
DM EDW-DataSource Lifecycle Examples
35
DM EDW-Generic Data Source Replicated from R/3
36
DM EDW-Migrated 3.x Generic DataSource
37
Data Modeling EDWTransformation

SAP NetWeaver 2004s significantly improves transformation capabilities. The improved graphical UI contributes to decrease TCO
Transformation
Improved performance, flexibility and usability, simplification by unifying transfer and update rules Unification of transfer and update rules New rule type: end routine New rule type: expert routine (pure coding of transformation)
Unit Conversion
Capabilities for unit conversion during data load (and reporting)
38

Transformation Types
Move, aggregate, constant, master data lookup. Business rules, unit / currency conversions. Formula builder with rich predefined functional library. ABAP Routines including regular expressions.
SAP NetWeaver 2004s Enhancements:

Intuitive UI Unit conversions Unified transfer rules + update rules
39
Transformation Update Rules
40
DM EDW-Transformation Graphical UI
Source Fields
Target
Fields
Note: Key figures, characteristics and date fields are shown on the same level (transformation group)
Rules per group

41
Data Modeling EDWTransformation Rules
42
DM EDW-Transformation Rule Routine

Routine
Interface: ABAP OO Class Only ABAP OO statements allowed (e.g. type declaration via LIKE not allowed) Global Area Global tables, variables, structures for all routines of a transformation Forms and routines are not allowed in this area Reuse of SAP BW 3,x coding Function modules or methods The call via external PERFORM can be included in the local part of the routine Transport Make sure that external classes, function modules and external performs are transported together with or earlier than the transformation routine.
43
DM EDW-Transformation Rule Start Routine

Start Routine
A Start Routine is required in the following scenarios:
Preparation of data before transformation. Package based, semantic Packaging possible.

Example: Deletion of records that are not required for updating.
44
DM EDW-Transformation Rule End Routine

End Routine
Post preparation of data before transformation. Package based, semantic Packaging possible. Example: Deletion of records that are not required for updating. Validation checks of records after transformation (eg. KF sales value must be greater than the purchase value).
45
DM EDW-Transformation Rule Expert Routine

Expert Routine
An End Routine is required in the transformation that can not be expressed declaratively for functional or performance reasons. Example: Performance: reading several database tables can be implemented faster when knowing the application logic (rather than using the generic transformation framework). Pivoting: transpose of vide data records into several smaller records.
46
DM EDW-Transformation comparison
47
Data Modeling EDWTransformation Groups

Transformation Groups
This replaces the former concept of key-figure specific updates for the characteristics. All Transformation Groups are referencing the standard group. If the standard group is changed, all the groups might change in the same way. Every rule is executed once even if is used in the several transformation groups. Example: Source has two date fields: order date, delivery date. KF order quantity is updated for order date, delivered quantity is updated for delivery date. Two transformation groups are generated: order date and delivery date.
48
Data Modeling EDWTransformation Groups

Summarize key figures with the same characteristics assignments All key figures of one transformation are updated based on the same characteristic values If other characteristic updates are necessary for particular key figures, a new transformation is created
49
Data Modeling EDWSimplified Data flow
50
Data Modeling EDWComplex Data flow
51
Data Modeling EDWBenefits of new DTP

Data Transfer Process (DTP)
Data Distribution within SAP BI (from PSA or InfoProviders to InfoProviders) Loading data from one layer to others except InfoSources Separation of delta mechanism for different data targets: delta capability is controlled by the DTP Enhanced filtering in dataflow Improved transparency of staging processes across data warehouse layers (PSA, ODS layers, DWH layer) Improved performance and high scalability Enables real-time data acquisition (RDA)
52
Data Modeling EDWCreating DTP
53
Data Modeling EDWData Transfer Process
54
Data Modeling EDWDTP Error Handling
55
Data Modeling EDWDTP Monitor

DTP Monitor
Integrated in InfoProvider management screen Integrated in DTP maintenance Additional information: duration of each step Temporary storage access if activated Error Stack is displayed in DTP Monitor
56
Data Modeling EDWDTP Error Stack
57
Data Modeling EDWDTP Error Stack
58
Data Modeling EDWRDA

Enhanced Real-time data acquisition capabilities
XML Web service Direct push into PSA (instead of Service API/Delta Queue) InfoPackage & DTP for real-time data acquisition Daemon-based update from delta queue (Service API) Daemon-based update of DataStore objects (ODS layer) including lean staging (with minimized logging)
59
Data Modeling EDWRDA

Daemon
System process fulfills a specific task at regular intervals The SAT NetWeaver BI Daemon performs three steps (depending on the scenario chosen) : Initiate service-API (SAPI) data pull via infopackage for real-time data acquisition into PSA Track status of data transfer from source system Initiate update of DataStore object (DSO) via DTP Successful execution of each step is tracked in a control table Allows restarting if necessary Restart can be initiated so it starts at the next step after the last successfully executed step.
Daemon Monitor
60
Data Modeling EDWInfoPackage for RDA
Real-time flag must be selected for the infopackage which the daemon will monitor. This option is only available for one infopackage attached to the datasource
61
Real-time extraction must be selected in the Adapter section of the infopackage settings
62
Periodicity is determined by update periods setting via real time monitor (RSRDA) Data package size : No of rows Allows control of number of records per datapackage (multiple datapackages per request possible) The deamon uploads at least one datapackage (even if number of actual records is smaller than setting) Request size : Number of rows Allows control of packets for downstream processing based on time Automatic closure of request by number of records ( 1,000,000 shown here) Max number of failed attempts Max number of times Daemon attempts to request/commit data before throwing error condition .
63

Only delta processing is available for Real-time updates( because the delta queue is leveraged for data staging)
On the schedule tab you can jump via Assign to the RDA monitor. There you can assign the infopackage to a daemon.
64
Data Modeling EDWProcess chain

Process chain Enhancements
New Features
Copying process chains Display-only mode Parsing system command return codes Choosing background user for execution of process chain Accessibility
New Process Types

Decision: depending on conditions, a particular path will be entered.
65
Data Modeling EDWAdministration Cockpit
66
Data Modeling EDWAdministration Cockpit

Administration Cockpit
Centralized Monitoring
Pro-active support of SAP NetWeaver BI administrator in status tracking and performance optimization (Data load, Reporting & Planning) Focused on critical issues Time-lines and comparisons (with deviations) Drill-down from overviews to details Direct jump to facilitate solving problems Based on new technical content InfoCubes Based on BEx and Portal technology -> Enhancements easily possible.
67
BI Accelerator Architecture
68
BI Accelerator
SAP NetWeaver 2004s provides various tools to increase the data load and query performance significantly among them the innovative BI accelerator. Thus, the implementation of large enterprise data warehouses is facilitated.
Performance optimizers. Separate box with 64 bit processor. Combination of hardware and software. New paradigm for high performance data access. Requires additional data push from InfoCube to Performance optimizers.
69
BI Accelerator Scenarios
Ready for high data volumes
Queries that routinely involve access to many millions of records and may involve up to billions of records Examples: retail, utilities, telephone companies
Challenging response time SLAs

Example: service level agreements for call center operators demand short response times for good closure rates
Unpredictable types of queries

Far more different data sets and aggregations than traditional optimization and caching strategies can handle Excellent response times for any drill-down, slice & dice, . Examples: on-demand reporting for different user groups, ad hoc analyses
70
BI - Re-partitioning
Re-partitioning
Re-partitioning enables the change management of partitioned InfoCubes
Attaching, combining partitions or complete re-partitioning
Example of Re-partitioning:
The InfoCube is partitioned on week, this partitioning has proven as too granular too many partitions have been created during the past year The new partitioning should be on monthly basis
71
Enterprise Query, Reporting and Analysis
72
Business Explorer Strategic Focus (NW04s)

Business Explorer will facilitate to extend the reach of BI by providing:
An Integrated and state-of-the art modeling environment

For all types of queries, reports, and analytics For business users and IT BI data and external data High Visual Appeal & Usability High performance use of BI Actionable BI Portal Knowledge Management Collaboration Visual Composer
73
BI for the masses:

Seamless integration into

Business Explorer Suite
74
Query, Reporting & Analysis

Designing a Query
(1) Choose Info Provider
Designing a Report
Designing a Web Application
BI User Interaction
Usage Type: BI JAVA
(2) Design Query (3) Save query (4) Open Query (5)Design Report (6) Save Report (7) Create new Web template (13) Access BI data
Tools:
(8) Insert new Web item
Usage
(14) Analyze data (if applicable)
Business Explorer
(9) Assign Data provide (10) Configure interaction (11) Save Web Application (12) Deploy
Type:
(15) Personalize data (if applicable) (16) Integrate documents (if applicable) (17) Use KM services (if applicable) (18) Use export/printing Services (if applicable) (19) Use Information Broadcasting (if applicable)
BI JAVA
75
Designing a Query
Designing a Query
State-of-the art UI concept, Providing for example:
Available tasks for a selected object presented via a task pane Message panel shows warnings and error messages in context -> helps to avoid or correct errors Enhanced application menus, toolbars and context menus Extended visualization of status and user actions
Support of multi-selected objects drag&drop, properties Options for BI-integrated planning
Query design takes place in the Business Explorer (BEx) Query Designer, a Visual Basic .NET-based Unicode-compliant tool.
76
Screen- Query Designer
77
Designing a Report
Designing a Report
Standard formatting: Font styles (e.g. bold, italic) and colors, etc. Group level changes with individual formatting Layout options, for example Height of rows, width of columns Multiline column headers Flexible positioning of fields Merger of cells Support of hierarchies Rules for the presentation of special characteristic values. Integration of text, pictures, and charts Header and footer for reports and pages
Report design takes place in the Business Explorer (BEx) Report Designer a new, VB .Net-based tool that allows to create formatted, print-optimized reports.
78
Designing a Web Application

Model-driven BI application building
Wizards for charts, maps, command editing Wizard for layout elements (e.g. buttons) ,,Intellisense support for Web API developers Easy integration of native HTML commands New layout elements (Tab strips etc.) New Web items New chart types, e.g. GANTT chart, MTA chart Design of planning aware business applications Web application design takes place in the Business Explorer (BEx) Web Application Designer, a Visual Basic .NET-based, Unicode-compliant tool.
79
BEx Web Printing Overview
80
BEx Web Printing

Using the Print Dialog, you can generate PDF files from BEx Reports, Web Applications, and ad hoc analyses created with the BEx Web Analyzer.
81
BEx Web Analyzer

Web Analyzer, a Web-based tool for analysts, was introduced in SAP BW 3.5. In SAP NetWeaver 2004s, Web Analyzer works with KM features to create and save complex analyses more easily using only a Web browser. Average user can use this tool as the primary way to obtain Ad Hoc Query analysis. Analysts without formal query design authority can create quick custom queries without needing to consult a power user.
82
Excel Integration
83
Query Embedding: BEx Analyzer

Embedding Queries, Views & InfoProviders
Direct Access to InfoProviders as well as queries & query views New workbook default layout Intuitive User Interaction via Drag & Drop and redesigned property dialogues Personalizable Filter value lists (Favorites & History) Full accessibility and Unicode support Excel based data entry and planning. Manual data entry into Planning Aggregation Levels and usage of planning functions Taking advantage of many new information broadcasting features
84
Workbook Design: BEx Analyzer

Workbook Design
Application-building in Excel (similar to Web Application Designer) New Options for Queries with 2 Structures Excel Formulas allow access to any cell of the result set Excel Formatting options can be fully leveraged for BEx Workbooks (e.g. blank lines, fonts etc.) Combining Excel Formulas and Excel Formatting allows the design of HighEnd Formatted solution workbooks Integration of Business Planning
85
Example: End User interaction via drag & drop
86
Information Broadcasting
87
Information Broadcasting allows you to make objects with Business Intelligence content available to a wide variety of users according to their needs
Information Sources:
based on BEx Queries, Views, Workbooks, Web Applications & Enterprise Reports
Information formats:
HTML, MHTML, PDF, ZIP, Printer Formats, Online Links, SAP alerts
Receiving media:
e.g. single users, groups, distribution lists, user-specific or Role-specific (incl. Non-SAP Users)
Channels:
e-Mail, Portal, BEx Portfolio (Unified access based on Knowledge Management Folders), Collaboration Rooms, Universal Work List
Event Driven:
- exception driven, Ad-Hoc, scheduled
88
Additional new broadcasting features include:
New Object Types Query Views Formatted Reports New Distribution Types Data Bursting Broadcast to recipients derived from BW master data and optionally adapt the output format for each recipient. With bursting in BEx, you filter once for each sales manager and email a Web link or completed output (Web or Excel workbook) to him or her Exception broadcasting - Create Alert settings based on defined exceptions Integration into SAP Alert Framework &UWL New Output Options Printers PDF Files
89
Information Access and Collaboration

KM Services enabled on top of any broadcasted BI data
Use KM Services for: Subscription Feedback Discussion Collaboration Rating TREX search Notes Download
90
Data Bursting
This capability allows you to broadcast user-specific data based on master data in BI. Example: burst a cost center report according to each cost Center manager and retrieve the e-mail addresses from a master data attribute
91
Data Bursting
Make sure the e-mail addresses of your receivers are retrievable via BI master data
92
Exception Broadcasting
93
BI NW04s Document Integration
Document Browser
Intuitive Access to KM Services for each document attached to BI data Rich Set of customizable Services for End-Users
Unified Information Access

Repository Manager allow access to documents residing in BI or KM
Copyright 2004 Accenture All Rights Reserved. 94
Assignment of Documents
Assignment & Upload of documents via BEx Web
95
Document Browser-KM & Collaboration Services

Use of all available KM & Collaboration Services
96
Document Browser: E.g. Feedback service

Feedback service of the New Document Browser
97
Visual Composer
Modeling of BI Applications using the BI Kit of the Visual Composer
Allows Business Users to create analytical content for SAP Enterprise Portal Offers the integration with BI InfoProviders (e.g. InfoCubes,BEx Queries and Query Views,BEx Web Applications) via WEB API as well as with heterogeneous data sources (including OLAP and relational data sources) via Java Connectors.
98
Business Explorer Suite
99
VC Dashboard Examples
100
VC & BEx Design Tools in a BI Context
101
Information Lifecycle Management (ILM)

Data warehousing is a very powerful concept for creating a unified and consistent view of the business In data warehousing environment it is typical that: Data is amassed and analyzed at an increasing rate. As time progresses, companies face the dilemma of storing more and more historical data. Over time, data tends to lose its day-to-day relevance and is therefore accessed less frequently. The costs associated with maintaining historical data are high. Data aging is a strategy for managing data over time.
Each data aging strategy is uniquely determined by the customers data and the business value of accessing the data.
ILM is a storage management concept that actively manages all information objects during their lifecycle. ILM is a combination of processes and technologies whose goal is to provide the right information at the right time in the right place with the lowest possible cost.
102
Information Lifecycle Management at SAP

Analyze business objects, determine data categories and layers, define attributes, identify parameters
Analyze Categorize
Define Policy
Automation, archiving, migration, deletion, accessibility
Realize
ILM
Determine policies and categories such as retention period, data extracts.
Apply Policy
Apply policies to business objects and data categories

103
Information Lifecycle Management in SAP BI

1. Online
Data persistent in the database Data modeling aspects important Use multiple layers to control data growth Frequent cleanup necessary
2. Near-line
Near-line Storage (NLS) ADK (Archiving Development Kit) and non-ADK-based Set up proper archiving policy Transparent access for reporting
3. Offline
Classic archiving as known in SAP BW 3.x Very cheap storage medium can be used ADK-based No access for reporting
104
ILM : Online strategy

PSA deletion:
Temporary inbound data load layer, exists for recovery or reload purposes. Retain daily loads one week, monthly retain 60 days Customer example: DB growing at 450 GB/month without PSA deletion, 150 GB/month with deletion
ODS object data deletion

Change log deletion: Its like a PSA Optimize ODS Object activation performance When data consolidated in subsequent data target When no delta at all is provided by this ODS Active table. When data is consolidated in active table
Data consolidation: Eliminate redundant data

Merge data from similar data marts Optimize aggregates Aggressively archive and delete from InfoCube and ODS object layers Summarize at the InfoCube and aggregate level (RRI)
Remote access:
Use RRI, Virtual InfoProviders, UDI, etc. Operational processing possibly might remain in OLTP system
105
ILM : NLS strategy (Near Line Storage)

Near-line storage is the on-site storage of data on removable media. NLS allows to read NLS data via the query without reloading it to the database. MultiProviders are build upon the Info Cubes and the NLS source, to access data using BEx queries.
106
ILM : Offline strategy

Logical partitioning of data into different basic Info Cubes and use MultiProviders at the top. Criteria for partitioning: Year, Plan/Actual, Regions, Business Area.
Bex / Web Report
Multi Provider
2002 2003
2004
2005
2006
107
ILM : NLS Solution in SAP NetWeaver BI
Archieiving (SAP BW 3.x) ADK-based archiving solution for InfoCubes and ODS objects Cost reduction due to storing data on alternative storage media ADK indexes for BI Query access ineffective, index structures too inflexible Archived data must be reloaded
108
ILM : Classic Archive in SAP BI
Near-line Storage (SAP NetWeaver 2004s BI) SAP NetWeaver BI analyses have direct access to archived data in various storage media Availability of historic data while reducing costs Physical decoupling of frequently, less frequently, or rarely used data Reloading of data into the InfoCube or DataStore object only necessary in exceptional cases
Copyright 2004 Accenture All Rights Reserved. 109
Information Lifecycle Management: Benefits

Increase Volume Manage and use even larger amounts of information more effectively Information available for any time frame for ad-hoc analyses and rebuilds Reduce Resource Consumption Main memory and CPU as well as costs for system administration Reduction of hardware costs for hard drive on the BI side Increase Availability Quicker, simpler software and release management in BI Reduced backup and recovery times Intelligent data access
Optimize Performance Speed up loading processes in SAP NetWeaver BI SAP NetWeaver BI Query answer times in the dialog
110
BI Integrated Planning
Old Term
Transactional InfoCube Planning package
New Term
Real-time InfoProvider Filter

InfoCube designed for direct plan data loading The data a planner plans in one planning session The entry screen for planning
Manual planning layout
Input-enabled BEx Queries
Planning level
Aggregation level
A high-level slice of an InfoCubes data to support SAP-delivered planning tools
111
BI Planning Architecture
112
BI Integrated Planning
BW BPS
Transactional Info Cube
BPS Integrated Planning
Real Time InfoProvider A new virtual InfoProvider for input (planning) Ready queries Aggregated Level
Planning Area
Planning level Planning package Planning package
Filter Filter Input ready query

BPS Specific output via:Excel/Excel in place/planning folders/Web
Bex Analyzer Workbook
Manual Planning
Planning layout Planning function Parameter group
Bex Web Designer and a browser Planning function Parameter group
113
Business Planning and Analytical Services

Benefits
Brings together analysis & planning on the same database (single version of the truth) Improved strategy implementation through flexible top-down distribution capacities and target setting Fast reaction to market changes using analytical methods which allow to turn data into action Find cross-selling opportunities through market basket analysis Great usability and flexibility through graphical design, most sought-after transformations and 3rd party interfaces to yet more specialized data mining tools Companies can easily enhance their existing SAP BI implementation through data transformation, data entry and planning functionality.
114
SAP NetWeaver 2004s BI
Questions?
115
SAP NetWeaver 2004s BI
Thank You
116

Business Intelligence111

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Business Intelligence111

Загружено:

Авторское право:

Доступные форматы

SAP Business Intelligence

Delta Training BW 3.5 to SAP NW2004s Training Material Version 1.1

Knowledge of SAP BW 3.X.

Copyright 2004 Accenture All Rights Reserved.

Copyright 2004 Accenture All Rights Reserved.

SAP NetWeaver 2004s

Copyright 2004 Accenture All Rights Reserved.

SAP NetWeaver 2004s

Copyright 2004 Accenture All Rights Reserved.

New Features in NW 2004S (BI 7.0)

New terms definition

Transfer Rules/Update Rules

ODS object Transactional ODS

DataStore object Direct update DataStore object InfoPackage

Data transfer process

Data transfer process (DTP)

Copyright 2004 Accenture All Rights Reserved.

New Features in NW 2004S (BI 7.0)

New terms definition

Remodeling toolbox Write-optimized DataStore object NLS BI Accelerators

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDW

Data Warehousing Workbench as successor of Administrator Workbench

Copyright 2004 Accenture All Rights Reserved.

Data Warehousing Workbench

Copyright 2004 Accenture All Rights Reserved.

EDW Main process overview

Meta Data & Document Management

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWDSO types

DSO object type

Active, modified, delta Active

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWDSO types

Example for Write-optimized DataStore Object

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWDSO types

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWEnhanced InfoSets

Example for new InfoSet features:

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWEnhanced InfoSets

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWEnhanced InfoSets

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWRe-Modeling Toolbox

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWRe-Modeling Toolbox

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWRe-Modeling Toolbox

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWBusiness content

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWBusiness content

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWData Acquisition

New DataSource Concept

Enhanced remote capabilities

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWDataSource

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWDataSource

Copyright 2004 Accenture All Rights Reserved.

Data Modeling EDWDataSource