Cognos OLEDB Interface for SAP BW
May 30, 2016 | Author: manikandanu1 | Category: N/A
Short Description
Cognos Interface for SAP...
Description
Integrating OLAP Frontends with OLE DB for OLAP Guido Schröder OLAP technology group Inc.Kralsruhe; SAP™TechEd ‘98 Aug. 31-Sept. 3, 1998 sessioncode.ppt / 1 SAP America, AG; TechEd Integration of OLAP Frontends
Talk Contents
~ ~ ~
BW architecture What is OLE DB for OLAP? OLE DB for OLAP Foundations
MD Schema Dataset Object
~ ~
MDX grammar BW’s use of ODBO
Mapping of BW Objects to ODBO Building QueryCubes Demonstrations
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 1
Architecture Overview 3rd party OLAP clients 3rdparty party OLAP OLAPclient clients 3rd 3rd party OLAP client 3rd party OLAP client 3rd party OLAP client ODBO
OLE-DB OLE-DB for for OLAP OLAP Provider Provider
Administrator Workbench
Business Explorer Analyzer Analyzer (hosted (hosted by by MS MS Excel) Excel)
OLAP OLAP Processor Processor Meta Data Repository
Administration Administration Scheduling Scheduling
Meta Meta Data Data Manager Manager
Business Information Warehouse Server
Monitor Monitor
Data Data Manager Manager
Staging Staging Engine Engine
Browser Browser
InfoCatalog
InfoCubes Operational Data Store
BAPI
Non Non R/3 R/3 Production Production Data Data Extractor Extractor Non Non R/3 R/3 OLTP OLTP Applications Applications
Production Production Data Data Extractor Extractor
OLTP OLTP Reporting Reporting
R/3 R/3 OLTP OLTP Applications Applications
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
BW ODBO driver architecture Desktop with SAP ODBO driver ( mdrmsap.dll; mdxpars.dll; scerrlkp.dll; saprfc.ini; librfc32.dll)
Dataset Object
3rdADO Party Client Tool
ODBO-Objects
Consumer
OLE DB-Objects
RFC OLAP API OLAP OLAP Processor Processor Meta Data Repository
Staging Staging Engine Engine
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 2
Data Base
Business Information Warehouse Server
OLE DB: Universal Data Access
Applications
ADO MD
ActiveX Data Objects (ADO)
OLE DB
E-mail
OLE DB
Spreadsheets
OLE DB
OLE DB
RDBMS
HTML
OLE DB for OLAP
Multidimensional data
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
OLE DB for OLAP
~ ~ ~
Set of COM objects and interfaces ODBO extends OLE DB for multidimensional data Reuse of OLE DB
Common Connection Model Rowset plays as an abstraction of tabular data plays a central role
~
Command Interface for builing queries ODBO adds
1 new object: Dataset 1 mandatory interface 5 mandatory methods SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 3
BW ODBO interface: Customer Benefits
~ ~ ~
Protect previous investment in reporting tools
connect BW server to a broad spectrum of Applications ADO/MD simplifies the task of custom application development Extensibility
Provider can add specific interfaces
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
ODBO industry support ISVs developing consumers
~ ~ ~ ~ ~ ~ ~ ~ ~
Arcplan, Inc. Andyne Computing Limited AppSource Corporation Arbor AutoDesk AVOCA Systems Limited
Brio Technology Business Objects Comshare
~ ~ ~ ~ ~ ~ ~ ~ ~ ~
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 4
Cognos Hyperion Software International Software Group IQ Software Panorama Software Systems Sagent Technologies SAS
Seagate Simba Technologies X-Tension
Terminology: BW vs ODBO
ODBO terms
BW terms
• Dimensions
• Characteristics
• Measures
• Key Figures
• Members
• Characteristic values
• Dimension Properties
• InfoObject Attributes
• Dataset
• Query
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
ODBO Schema Objects Meta- and Masterdata Catalogs
Schema Rowsets Schema
CUBES
Cubes
Dimensions (Measures)
DIMENSIONS MEASURES
Hierarchies
HIERARCHIES LEVELS
Levels
Members
Properties
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 5
MEMBERS
PROPERTIES
Schema Rowset example: DIMENSIONS Rowset column name
Description/Comment
CATALOG_NAME SCHEMA_NAME CUBE_NAME
Name of catalog, schema and cube CATALOG and SCHEMA not supported in BW
DIMENSION_NAME DIMENSION_UNIQUE_NAME DIMENSION_GUID DIMENSION_CAPTION
UNIQUE_NAMEs are unambigous. BW provider follows two strategies : qualification and opaque tokens Use Unique Names for MDX Query SCHEMA for UNAMs!!!
DIMENSION_ORDINAL DIMENSION_TYPE
Time, Measure, Unknown, Other
DEFAULT_HIERARCHY DIMENSION_CARDINALITY
Number of members
DESCRIPTION
Human readable description
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Sample Dataset Slicer Axis 2 dimensions Actual
Actual data
DE
Germany
Berlin
Qtr1
17.793.920,00 DM 3.561.920,000 ST
35.583.920,00 DM
Qtr2
12.504.000,00 DM 2.504.000,000 ST
25.004.000,00 DM
Qtr3
12.503.000,00 DM 2.503.000,000 ST
25.003.000,00 DM
Qtr4
18.083.940,00 DM 3.619.940,000 ST
36.163.940,00 DM
Qtr1
12.502.500,00 DM 2.502.500,000 ST
25.002.500,00 DM
Qtr2
12.503.500,00 DM 2.503.500,000 ST
25.003.500,00 DM
Qtr3
12.502.000,00 DM 2.502.000,000 ST
25.002.000,00 DM
Qtr4
18.213.900,00 DM 3.645.900,000 ST
36.423.900,00 DM
Cost
Rows Axis 2 dimensions
Columns Axis 1 dimension
Value type Country
Stuttgart
SoldPcs
Cell data
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 6
Revenue
Structure of a dataset
Cubes
~
Datasets
~
have dimensions
Dimensions have members
~
At the intersection of members are data cells
have dimensions on axes
Sets on Axes have members
At the intersection of Axes coordinates are data cells
Datasets (in BW terminology Queries) have the same structure as Cubes
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
MDX I
~ ~ ~
MDX stands for MultiDimensional EXpression Expression syntax for querying Datasets Parts of MDX statements
FROM clause -> selects a cube SELECT clause -> defines the axes WHERE clause -> defines a slicer SELECT , ,… FROM WHERE
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 7
MDX II: Example
SELECT CROSSJOIN({City.Berlin,City.Stuttgart}, {Quarters.MEMBERS}) ON COLUMNS, {COST,SoldPieces,Revenue} ON ROWS FROM CUSTOMER_ANALYSIS WHERE (Country.Germany,ValueType.Actual)
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
MDX III: Basic Entities and Functions
~
Basic Entities
Numeric Values
Members
Strings
Tuples: Collections of Members of different dimensions (Berlin,Qtr1)
Sets
~
Functions
numeric value functions: return numbers set value expressions: manipulate/generate sets member value expressions: return member ......
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 8
MDX IV: Set Value Expressions, Numeric Value Functions
~ ~ ~ ~
Controlling the order of tuples ORDER(,,[ASC|DESC|BASC|BDE SC])
ORDER(customer.MEMBERS,Revenue,DESC) Ranking functions TOPCOUNT|BOTTOMCOUNT(,,)
TOPCOUNT(customer.MEMBERS,5,Revenue) Filtering FILTER(,)
FILTER(customer.MEMBERS,Revenue>1.000.000) Numeric Value Functions: AVG,MAX,MIN,MEDIAN...
AVG(customer.MEMBERS,Revenue) SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
MDX V: Dimension Properties
~ ~ ~
Members may carry additional information e.g. a material has properties colour, weight, packaging information.... ODBO supports dimension properties on a per dimension, per level and per member basis Dimension properties are selected using the DIMENSION PROPERTIES clause
SELECT material.MEMBERS DIMENSION PROPERTIES material.colour, material.weight ON ROWS
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 9
Fetching cell data IMDDataset::GetCellData Columns Axis 3 coordinates 0..2
0
Rows Axis 8 coordinates 0..7
1 0
1
2
1
3
4
5
2
6
7
8
3
9
10
11
4
12
13
14
5
15
16
17
6
18
19
20
7
21
22
23
Selection of cells
~ ~ ~
2
0
24 cells cell ordinals 0..23
by cell ordinal axis coordinates member unique names
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
What are the properties of a cell?
~ ~ ~ ~ ~ ~ ~
CELL_ORDINAL VALUE - this is a variant since cell data is not only numeric (date/time/string- Key Figures) FORMATTED_VALUE - string representation of the value optional cell properties defined by ODBO FORMAT_STRING, FORE_COLOR,FONT_SIZE... Optional provider specific cell properties Mechanism for the selection of cell properties is the same as for dimension properties - use CELL PROPERTIES clause list of supported cell properties comes with the properties schema rowset
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 10
Fetching Axis “Masterdata” IMDDataset::GetAxisRowset
~
Rowset column name
Description/Comment
TUPLE_ORDINAL
Axis coordinate
MEMBER_UNIQUE_NAME MEMBER_CAPTION LEVEL_UNIQUE_NAME LEVEL_NUMBER DISPLAY_INFO
For each dimension on the axis
MEMBER_NAME MEMBER_TYPE::::
Additional mandatory and user defined member properties
Axis Rowsets have at least 5n+1 columns (n is the number of dimensions projected along the axis)
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Axis Rowset and Cell Data Example CELL_ORDINAL
VALUE
0
17793...
1 2 ....
3561930.. 35583...
Value type Country
Actual
Actual data
DE
Germany
Berlin
Qtr1
17.793.920,00 DM 3.561.920,000 ST
35.583.920,00 DM
Qtr2
12.504.000,00 DM 2.504.000,000 ST
25.004.000,00 DM
Qtr3
12.503.000,00 DM 2.503.000,000 ST
25.003.000,00 DM
Qtr4
18.083.940,00 DM 3.619.940,000 ST
36.163.940,00 DM
Qtr1
12.502.500,00 DM 2.502.500,000 ST
25.002.500,00 DM
Qtr2
12.503.500,00 DM 2.503.500,000 ST
25.003.500,00 DM
Qtr3
12.502.000,00 DM 2.502.000,000 ST
25.002.000,00 DM
Qtr4
18.213.900,00 DM 3.645.900,000 ST
36.423.900,00 DM
Cost
Stuttgart
SoldPcs
Revenue
TUPLE [city].[MEMBER_ [city].[MEMBER [city].[LEVEL [city].[LEVEL [city].[DI [Quaters].[ [Quarters _ORDI UNIQUE_NAME] _CAPTION] _UNIQUE_NA _NUMBER] SPLAY_I MEMBER_U ].[MEMBE NAL ME] NFO] NIQUE_NA R_CAPTI ME] ON] 0 [city].[berlin] Berlin [city].[citylevel] 1 0 [Quarters].[qt Qtr1 1 [city].[berlin] Berlin [city].[citylevel] 1 0 [Quarters].[qt Qtr2 1 0 [Quarters].[qt Qtr3 2 [city].[berlin] Berlin [city].[citylevel]
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 11
FORMATTED_VALUE 3.645.900,00 DM 18.213.900,000 ST 35.583.920,00 DM
Dataset Flattening Value type Country
Actual
Actual data
DE
Germany
Berlin
Qtr1
17.793.920,00 DM 3.561.920,000 ST
35.583.920,00 DM
Qtr2
12.504.000,00 DM 2.504.000,000 ST
25.004.000,00 DM
Qtr3
12.503.000,00 DM 2.503.000,000 ST
25.003.000,00 DM
Qtr4
18.083.940,00 DM 3.619.940,000 ST
36.163.940,00 DM
Qtr1
12.502.500,00 DM 2.502.500,000 ST
25.002.500,00 DM
Qtr2
12.503.500,00 DM 2.503.500,000 ST
25.003.500,00 DM
Qtr3
12.502.000,00 DM 2.502.000,000 ST
25.002.000,00 DM
Qtr4
18.213.900,00 DM 3.645.900,000 ST
36.423.900,00 DM
Cost
Stuttgart
SoldPcs
[city].[M EMBER [Qua rters].[M EMB [m e asures].[cost] _CAPTION] ER_CAPTION]
Berlin Berlin Berlin Berlin
Q tr1 Q tr2 Q tr3 Q tr4
Revenue
[m e asures].[SoldPc [m e asures].[Re venue ] s]
17793920 12504000 12503000 18083940
3561920 2504000 2503000 3619940
35583920 25004000 25003000 36163940
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Mapping of BW Objects to ODBO Schema Objects ODBO
BW
Catalogs
InfoCubes
Schema
Not supported
Cubes
Queries
Dimensions (Measures)
Characteristics(Keyfgs)
Hierarchies
Hierarchies (external) Numbered Levels or Dummy level names
Levels
Members
Characteristic Values
Properties
Display Attributes
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 12
OLAP dataflow Presentation Server;ODBO client application
Datasets
mdx$
ODBO BW Application Server
answer
OLAP Processor operates on ...
„QUERY_CUBE (BEx: Query)“ Database Server Stored in
Star Schema
„INFOCUBE“ SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Mapping of Query Objects BW Query
QUERY_CUBE structure
Charact.1:Region
Dimension1:Region
Charact.2:FiscalYear
Dimension2:FiscalYear
Charact.3:Customer
Dimension3:Customer
Structure for Key Figs.
Measures Dimension
Member1: Cost Member2: SoldPieces
Measures
Member1: Revenue Cost SoldPieces Revenue
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 13
Creating a QUERY_CUBE
~ ~ ~
Select from an InfoCube characteristics - these will be mapped to dimensions of the ODBO QUERY_CUBE Create one structure and drag Key-Figures from the InfoCube to this structure - this structure will be mapped to the measures dimension of the ODBO cube, the members of the structure are the members of the measures dimension Enable the query for ODBO by setting in the Query properties dialogue ODBO support checkmark
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Benefits of QUERY_CUBES
~ ~ ~ ~
Leverage of existing BW OLAP Processor Consistent definition of derived key figures on the BW server - no calculated members via MDX but on the BW server Smaller entities for reporting purposes - BW InfoCubes may contain large number of InfoObjects Centralized Authorization concept!!!
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 14
Application of Leveling Rules
~ ~ ~ ~ ~ ~
Section “Elements” - no object qualification by catalog, schema...; numbered levels (dummy level names) Section “Expressions” - #1,#2,#3; .VALUE, case expressions not supported Section “Set Value Expressions” - #3 (YTD, MTD, WTD..), #4 (nonmeasure dimensions in value expressions) Section “Member Value Expressions” - COUSIN , PARALLEL/OPENING/CLOSINGPERIOD Section “Numeric Value Functions” - RANK, AGGREGATE, COVARIANCE, LINREG*s Section “MDX Statement” - #1 (formulas), #2 (slicer is single tuple), #3 (no joincubes), #4,5 (supported axes 0..2), #6 (create formula), #7
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Rollout Status
BW ODBO Pilot customer shipment (rel. rel. 1.2 GA)
9/98
General availability with 1.2B
Pilot certicertifications with Arcplan & Business Objects
12/98
2/99
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 15
Where to find more information
~ ~
Final OLE DB for OLAP Programmers Reference at: www.microsoft.com/data/oledb/olap Microsoft Data Access SDK 2.0
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Summary
~
BW provides access to its data via OLE DB for OLAP compliant driver
leverage investment in front end tools via industry standard interface
~ ~
extensibility Queries are mapped to QUERY_CUBEs via the ODBO layer MDX is the command language for querying MD data
powerful syntax for manipulation of sets, tuples,members and numeric values
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 16
Demonstrations and Q&A
~ ~ ~
Definition of a QUERY_CUBE Applications :Arcplan inSight; Business Objects ADO MD sample
SAP AG; TechEd Kralsruhe; Integration of OLAP Frontends
Page 17
View more...
Comments
