A Holistic BI Architecture with SAP NetWeaver Business Warehouse

October 2013

RDP301 A Holistic BI Architecture with SAP NetWeaver Business Warehouse and SAP HANA

©  2013 SAP AG or an SAP affiliate company. All rights reserved. 2

SAP NetWeaver BW on SAP HANA Get your own system today

�  Follow this link to go to SAP HANA Marketplace

http://www.saphana.com/docs/DOC-3954

�  SAP NetWeaver BW on SAP HANA Trial - First Steps Overview �  SAP NetWeaver BW on SAP HANA – Tutorials �  SAP Cloud Appliance Library

Get your very own SAP NetWeaver BW on SAP HANA with SAP BI 4.x system today !

You will receive a SAP NetWeaver BW 7.3 on SAP HANA SP06 and SAP BusinessObjects BI 4.0 SP07 system as 30 day trial.


Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.


Agenda

Warm up – LSA++ (Layered Scalable Architecture) and BW on SAP HANA – TechEd 2012 review

Modeling BI functions and integration – context

BW on HANA Open ODS field-based modeling – open functions and scalable integration

�  Function modeling on any field data with new Open ODS Views

�  Crossing the border – Open ODS function modeling on remote data (HANA Smart Data Access)

�  Open ODS View generated staging services for field data - BW field-based DSOs*

�  Integration of field data into EDW context - association of InfoObjects to Open ODS Views

�  Field-based DSOs* and Open ODS Views – scalable EDW integration of non-SAP data

BW on HANA and incremental LSA++ as common DWH & BI platform

* Pilot only



LSA++ holistic framework for BW on HANA Flexible consistent data framework virtually wrapped BI on Streamlined EDW - Operational BI – Agile BI – Virtualization - Open BW Services

BW

Ope

n Se

rvic

es: D

ata

Mod

el,

OLA

P, A

utho

rizat

ion,

Dat

a A

ging

BW Virtual Data Mart Layer

Architected Data Mart Layer

Business Transformations

EDW Propagation Layer

EDW Transformation Layer

Externally managed BW managed

Open Operational Data Store Layer

Agile DMs/ BW

Work space

Cen

tral

BI-

Prom

ote

To P

rodu

ctio

n

Agi

le B

I - c

entr

al/ d

epar

tmen

tal LSA

++ for BW

on HA

NA

BI on S

treamlined E

DW

, O

perational BI, A

gile BI

Cor

pora

te

Mem

ory

refe

renc

e

BW Queries EPM , BO BI, Apps

TechEd 2012


LSA++ holistic framework for BW on HANA Open Operational Data Store layer - targets

BI on Streamlined EDW - Operational BI – Agile BI – Virtualization - Open BW Services B

W O

pen

Serv

ices

: Dat

a M

odel

, O

LAP,

Aut

horiz

atio

n, D

ata

Agi

ng

BW Virtual Data Mart Layer

Architected Data Marts

Business Transformations

EDW Propagation Layer

EDW Transformations

Externally managed BW managed


Agile DMs/ BW

Work space

Cen

tral

BI-

Prom

ote

To P

rodu

ctio

n

Agi

le B

I - c

entr

al/ d

epar

tmen

tal LSA

++ for BW

on HA

NA

BI on S

treamlined E

DW

, O

perational BI, A

gile BI

Cor

pora

te

Mem

ory

refe

renc

e

BW Queries EPM , BO BI, Apps

Immediate Querying – no staging to EDW

On any data

Incremental integration with EDW

TechEd 2012


LSA++ Open Operational Data Store layer as parenthesis

The target of the Open ODS Layer is to provide the services and technology gaining a holistic picture on data

BW HANA instance HANA

Application instance BW

accelerator

SAP Application

Custom Model

HANA sidecar instance

SAP Application

ERP2 ERP1


TechEd 2012


Demo 1: first impression on Open ODS modeling Open ODS Multidimensional Modeling – BEx Query (OLAP) on any data

Dimension / master data

Dimension / master data Fact data

on data in any HANA db-schema

Demo


Demo 1: first impression on Open ODS modeling BEx Query (OLAP) on any data – on data in any HANA db-schema

1. Create SQL-view to transform format SMALLINT -> INTEGER CREATE VIEW "AW"."TE1_PROD_SQL_VIEW" ( "PROD_ID", "PROD_NAME", "PROD_NUMBER", ….. AS select cast(T0."ProductID" as integer) as "PROD_ID", T0."Name" as "PROD_NAME", …. from "AW"."Product" T0

2. Create new BW Open ODS Views on SalesOrderDetail table and TE1_PROD_SQL_VIEW SQL view

Tell BW about

• semantics of tables/ SQL-views and fields and

• associations between tables/ SQL-views

3. Run a BEx Query on Open ODS fact table view

Finally you define a multidimensional model

Open ODS View Type: master

Open ODS View Type: fact

BEx Query

……..


LSA++ and BW on HANA - BW just for modeling a SAP EDW ? BW Open ODS field-based modeling directions

Virtual Data Mart Layer

BEx Query Access

Externally managed

Open ODS BW managed

Sources

LSA++ for B

W on H

AN

A

Architected Data Mart Business Transformation

EDW Propagation

EDW Transformation

Cor

pora

te

Mem

ory

ED

W P

erspective

1.  Function modeling on any data

2.  Transform data for function modeling only if it shows up value

3.  Consume data instead of moving data

4.  Data staging – in case consumption of data is not appropriate


Traditional BI architecture landscape components Perceived as dispersed, expensive, sluggish

Centrally defined BI Analytics & Reporting

BW EDW

SAP Enterprise Applications

Non-SAP Enterprise Applications

Local DWHs

local Applications

Locally defined BI Analytics & Reporting

Traditional BI Provisioning

Architected Data Marts Independent Data Marts

The BW EDW is just a part of the BI landscape. Apart of the EDW we observe a dispersed landscape of BI systems with a high degree of data redundancy

Such a landscape means low responsiveness and high costs

BI architecture components –

different weight of (data) integration Integration before Function Function before Integration

Modeling BI functions and integration - context


Two different perspectives on BI provisioning Central & local BI

BI Provisioning

Integration before Function Function before Integration

Function modeling § Queries § Schemas § Staging

Function modeling § Queries § Schemas § Staging

Integration modeling



Function and integration modeling in BW up to version 7.3

BW ≤ V. 7.3

Common function modeling �  Queries and Cell-based OLAP �  Schemas / InfoProvider �  Staging / data flows �  Authorizations �  Operations �  Data aging management (NLS) �  Promote to production management (transports)

§ Function modeling § Queries § Schemas § Staging

§ Integration modeling § Map fields to InfoObjects

Data integration modeling with InfoObjects �  InfoObjects define the integrated EDW data model (common semantics,

common values)

Integration before Function

on InfoObjects

based on InfoObjects

�  No InfoObjects – no functions : up to BW 7.30 the existence of actively modeled InfoObjects is a prerequisite modeling functions in BW


Modeling of functions and integration with BW 7.40 ≥ SP5 on HANA

Integration modeling § Map fields to InfoObjects

Function modeling § Queries § Schemas

§ Persistencies, Staging


InfoObjects Fields

Modeling Options Integration before Function Function before Integration


BW on HANA Open Service Framework

BEx Query Designer

BW Analytic Manager (OLAP)

BW Operations § Loading, staging, transformation and persistency management

InfoObject-based modeling • Applies to

• EDW, Architected Data Marts • SAP sources, Non-SAP sources

• persisted objects • DSO, InfoObject, InfoCube

• Virtual objects •  VirtualProvider, CompositeProvider

Field-based modeling • Applies to

•  Data Marts, DWHs; EDW • Non-SAP sources, SAP sources

• persisted objects • DSO*, Tables

• Virtual objects •  SQL-View, BW Open ODS View, CompositeProvider

Combine Move

* pilot ðDSO roadmap


BW on HANA open functions and scalable integration Field-based modeling

Source - 3NF Model

Remote access 3NF model - field

BEx Query/ Composite Provider

Open ODS View

sql-view DSO – Field *

Local replicate

transform transform - denormalize data

generate

persisted data Non persisted data

BW DataSource

load

virtual access

InfoObject integrate DSO - InfoObject

denormalized model - field SAP Application Extract - ∆ Queue

Non-SAP Application Extract – BO-DS

Integrate

transform

BW DataSource

Integrate

* Pilot only


Agenda


Modeling BI functions and integration – context


�  Function modeling on any field data with new Open ODS Views

�  Crossing the border – Open ODS function modeling on remote data (HANA Smart Data Access)

�  Open ODS View generated staging services for field data - BW field-based DSOs*

�  Integration of field data into EDW context - association of InfoObjects to Open ODS Views

�  Field-based DSOs* and Open ODS Views – scalable EDW integration of non-SAP data


* Pilot only


�  Function modeling on any field data with new Open ODS Views �  Crossing the border – Open ODS function modeling on remote data (HANA Smart Data Access) �  Open ODS View generated staging services for field data - BW field-based DSOs* �  Integration of field data into EDW context - association of InfoObjects to Open ODS Views �  Field-based DSOs* and Open ODS Views – scalable EDW integration of non-SAP data

* Pilot only


BW Operations Modeling

BEx Query & BW Analytic Manager

Table

SQL View

HA

NA

DB

Table Table /Table Field DSO

/Table Field DSO

BW on HANA field-based function modeling Open ODS View as central meta object


Open ODS View

Master data

InfoObject Tables

Open O

DS

EDW


Open ODS View

Master data

Open ODS View Fact data

InfoObject Master data

Virtual Data Mart – Virtual Star Schema

* Pilot only


BW on HANA Open ODS View (short: ODS View) BW Field-based Modeling on any Data - Overview

Facts ODS View

Master ODS View

Master ODS View

Master ODS View

Master ODS View

Field DSO

Field DSO

Table

Table

SQL View

Field DSO/ Table

�  The BW metadata model for field data consists of entities – the Open ODS Views – defining – Semantics of sources (fact, master.. data) – Semantics of source-fields (characteristic, key figure,…) – Associations to other Open ODS Views –  (optional) associations to InfoObjects (EDW model)

�  ODS Views are view constructs that can be defined on various types of source objects – BW Field-based DSOs*/ DataSources – DB tables & SQL views

�  The source object of an ODS view can be exchanged with a different source object of identical structure

�  From a BW-OLAP perspective, ODS Views can be consumed like InfoProviders (facts) or InfoObjects (master data, text)

Table

Open ODS Views of type fact define a multi-dimensional Star Schema * Pilot only


Demo 2 – multidimensional modeling using Open ODS Views 1st analyze data: understand the source model (Powerdesigner)

Product Dimension/ master data

Customer Dimension/ master data

1. Understand the model – analyze tables – what do you want to achieve - at a first glance

text data

Offers facts that we want to analyze -> fact table

Observation: CustomerID is not foreign key in fact table but in SalesOrderHeader table

Fact table


Demo 2 – multidimensional modeling using Open ODS Views 2nd create star schema: define sql views (HANA Studio, Powerdesigner)

sql-view - Customer Dimension/

master data sql-view - facts

……….

……….

……….

………. ………

………

sql-view - Product Dimension/

master data


Demo 2 – multidimensional modeling using Open ODS Views 3rd define Open ODS Views: model semantics & associations (BW Studio, RSA1)

sql-view - facts

……….

Open ODS View - facts

Open ODS View - Product master data

……..


master data


master data

Open ODS View - Customer master data


Demo 2 – multidimensional modeling using Open ODS Views 4th query: check Open ODS Views, build query functions

Demo


Demo 2 – multidimensional modeling using Open ODS Views Summing up

SalesOrderHeader

SalesOrderID PK

CustomerID FK

TaxAmt

SalesOrderDetail

SalesOrderID PK,FK

SalesOrderDetailID PK

ProductID FK

OrderQty

Customer

CustomerID PK

Product

ProductID PK

Product Dimension ≙ sql-‐view

Customer Dimension ≙ sql-‐view

1.  Define fact Open ODS View for supposed fact table SalesOrderDetail and run query

Fact table

2.  Associate product master data/ dimension to fact Open ODS

Multidimensional Model (Star Schema) ≙ sql-‐view

a.  Define sql-view on product tables

3.  Association of customer master data/ dimension to fact Open ODS is not possible – no CustomerID in fact table

4.  Associate customer master data/ dimension to fact Open ODS based on new sql-view source (s.2)

Fact

Ope

n O

DS

Vie

w

Master Open ODS View

Master Open ODS View

b.  Define master Open ODS View on product master sql-view

c.  Run query on fact Open ODS

ð we exchange the source (table SalesOrderDetail) of fact Open ODS against an sql view that joins tables SalesOrderDetail and SalesOrderheader and thus offers CustomerID


BW on HANA field-based function modeling with Open ODS Views Iterative multidimensional modeling process – modeling tools

Analyze, qualify Tables/ Fields •  determine facts and dimensions

(master data)

Model SQL-Views •  fact and dimension views •  transform, denormalize data

Model Open ODS Views •  semantics of sql-views, tables •  semantics of fields •  associations •  authorizations

Model BEx Queries •  all functions

BW on HANA field-based multidimensional model

on Star Schema

Model Star Schema Components

BW Studio

HANA Studio

SAPGUI RSA1

Eclipse

BEx Query

Designer

Mod

elin

g

Powerdesigner


One common modeling environment Planned with BW 7.4, SP5/SP6 on HANA

Common user experience via a central, unified modeling environment �  Attractive, flexible and simplified BW modeling

environment �  Harmonization BW and HANA modeling environments �  Integration of BW and HANA models in one modeling

approach �  Integrated development & modeling environment across

–  SAP HANA Modeler, –  BW Modeling

o  New developed native Eclipse based modeling tools for Query Designer, Open ODS View and New Composite provider

o  Other editors as in place SAPGUI based editors –  ABAP Development Tools –  …


BW on HANA field-based function modeling with Open ODS Views semantics & associations modeling at a glance – source semantics (RSA1) Tac: RSODSVIEW

Source semantic

Source type

Physical location of source for tables/ sql views: �  Connection to remote DB (for virtual table) �  DB schema name �  DB-Connect source system (generated, if not exist for DB schema �  Table/ sql-view name

External sources connected via DB-Connect:

New DB-Connect connection types


BW on HANA field-based function modeling with Open ODS Views semantics & associations modeling at a glance – field semantics for fact data

mapping/ propose �  Assign/ maintain basic semantics to fact data

�  assign/ maintain basic properties to fact data

•  Key figures

Source – ODS-view mapping

Internal name – local or inherited Aggregation behaviour

–  characteristics Source – ODS-view mapping Internal name – local or inherited from

association Associations – ODS View , InfoObject Authorizations (-> internal name) �  Not relevant �  Relevant and local authorization �  Relevant and inherited from

associated Object


BW on HANA field-based function modeling with Open ODS Views semantics & associations modeling at a glance – field semantics for master data

mapping/ propose

�  Assign/ maintain basic semantics to master data

�  assign/ maintain basic properties to master data –  characteristics

Source – ODS-view mapping Internal name – local or inherited from

association Associations – ODS View , InfoObject Authorizations (-> internal name)

Note: Associated objects to Open ODS views of type master are only relevant for navigation if the query is executed on the master ODS view – if the master ODS view is associated to an ODS view type fact then only texts (if exist) are offered – no snowflake support


BW on HANA field-based function modeling with Open ODS Views semantics & associations modeling at a glance – fact Open ODS view & associations

Open ODS View type fact



* Pilot only


BW on HANA field-based modeling Incremental modeling process – multidimensional model, data delivery, integration

Model BW on HANA field-based functions

on Star Schema

Model Star Schema Components

Model Data Delivery (sources)

Model Integration, Standards

(EDW/ LSA++)

Multidimensional modeling with Open ODS Views happens normally in a broader context described by guidelines on EDW/ LSA++/ integration and on data delivery We have already a feeling that new BW on HANA will have a big influence on future solution delivery but how does it fit in such a broader BI architecture context? This section illustrates how BW on HANA field-based modeling can be embedded into a more factory like BI architecture context

Incremental modeling of data delivery �  Independency of Open ODS Views from source location (data delivery)

Incremental integration of field data with EDW �  Integration of Open ODS Views into an EDW context (InfoObjects)

�  Field-based DSOs* – BW persistency & staging service for all

* Pilot only


BW on HANA field-based modeling Incremental modeling of data delivery – remote data access

Incremental modeling of data delivery •  Independency of Open ODS Views from source location

Model Data Delivery (location of sources)

Open ODS – BW managed data ð Field-based DSOs*

Open ODS – Externally managed data ð local HANA DB schema

Open ODS – Externally managed data ð remote DB via HANA Smart Data Access

Source - 3NF Model


BEx Query

Open ODS View

sql-view DSO - Field

Local replicate


generate

BW DataSource

* Pilot only


BW on HANA incremental modeling of data delivery Demo 3 - flexible, transparent exchange of Open ODS View source – remote source

Local HANA DB: ‘KT1’

Sch

ema

“AW

”

Sch

ema

“AW

”

Remote DB (e.g. HANA DB: ‘KD1’ )

product

customer

Salesorder sql-view

Fact Open ODS View SalesOrder

Master Open ODS View Product

Master Open ODS View Customer

HANA Smart Data Access

Salesorder sql-view


BW on HANA incremental modeling of data delivery Demo 3 Open ODS View and remote sources




master data

remote local local

local

Demo


Open ODS View and remote sources Demo 3 – HANA Studio and two HANA instances

Local HANA DB Remote HANA DB


Open ODS View and remote sources Demo 3 – HANA Studio & remote sources

Remote DBs

Local HANA DB

Virtual table is sql-view

Local HANA DB

the remote source KIW


Open ODS View and remote sources Demo 3 – Assign new source based on a virtual table to Open ODS View

The necessary virtual table in the local HANA DB is generated by BW! –> source exchange fully transparent



* Pilot only


BW on HANA function & integration modeling Incremental modeling of data delivery – staging & Field-based DSOs

Incremental modeling of data delivery �  Independency of Open ODS Views from source location

Source - 3NF Model


BEx Query

Open ODS View

DSO - Field

Local replicate


generate

BW DataSource

sql-view

Model Data Delivery (location of sources)

Open ODS – BW managed data ð Field-based DSOs*

Open ODS – Externally managed data ð local HANA DB schema

Open ODS – Externally managed data ð remote DB via HANA Smart Data Access

* Pilot only


Open ODS Layer – field-based DataStore Objects (DSOs)* architecture aspects

Provide BW operational services (loading, staging, persistency management) to any data – data become part of the BW-managed part of Open ODS

Open Operational Data Store Layer Externally managed BW managed

Field-based DSOs * Database Tables LSA++ Open ODS and persisted data

- Field-based DSOs and Database Tables - Staging is necessary in case certain SLAs cannot be guaranteed �  Availability – unreliable source �  Reproducibility – source is not our control, no historical data, … �  Balance between performance and costs �  Maintainability �  As part of a central governance roadmap the data shall become part of an EDW �  …..

* Pilot only


Open ODS Layer – field-based Data Store Objects (DSOs)* basic properties

Easy Modeling •  All fundamental functions (delta, staging,..) as

InfoObject-based DSOs – but no SPO, NLS •  Easy integration of non-BW data types. Support

for all DDIC data types •  Easy integration of Non-SAP data models •  Pilot – functional completeness with new DSO++ Reporting •  Field-based DataStore Objects are reporting

enabled (via Open ODS Views) w/o the need to model InfoObjects

* Pilot only


BW on HANA incremental modeling of data delivery Demo 4: Open ODS View & staging of any data to Field-based DSOs*

Local HANA DB: ‘KT1’

BW

Sch

ema

“SA

PK

IT”

Sch

ema

“AW

”

Sch

ema

“AW

”

Remote DB (e.g. HANA DB: ‘KD1’ )

product

customer

Fact Open ODS View SalesOrder

Master Open ODS View Product

Master Open ODS View Customer

Field-based DSO* on

salesorder

HANA Smart Data Access

Salesorder sql-view

Salesorder sql-view

* Pilot only


BW on HANA incremental modeling of data delivery Demo 4: Open ODS View & staging of any data to Field-based DSOs*




master data

local local

Field-based DSO

local remote

* pilot ðDSO roadmap Demo


BW on HANA incremental modeling of data delivery Demo 4: Open ODS View & staging of any data to Field-based DSOs* - DataSource

Open ODS View ð Generate DataSource

It is planned to automate the generation of an entire data flow �  DataSource based on Open ODS view �  Field- based DSO* based on DataSource

* Pilot only


BW on HANA incremental modeling of data delivery Demo 4: Open ODS View & staging of any data to Field-based DSOs* - DSO

* Pilot only


BW on HANA incremental modeling of data delivery Demo 4: Open ODS View & staging of any data to Field-based DSOs* - DTP

No PSA

Direct load data via DTP

* Pilot only


BW on HANA incremental modeling of data delivery Demo 4: Open ODS View & Field-based DSOs* – DSO as source

* Pilot only


BW on HANA function & integration modeling Incremental modeling thru flexibility of Open ODS Views

Source - 3NF Model

Remote access

BEx Query

Open ODS View

DSO - Field

Local replicate

transform

BW DataSource

sql-view

Analyze, qualify Tables/ Fields •  determine facts and dimensions

(master data)

Model SQL-Views •  fact and dimension views •  transform, denormalize data

Model Open ODS Views •  semantics of sql-views, tables •  semantics of fields •  associations •  authorizations

Model BEx Queries •  all functions

Model Field-based DSO*

* Pilot only


Open ODS Views & BI architecture Consequences so far

Open ODS views propagate �  an iterative flexible multi-dimensional approach

–  Extending, enhancing the underlying source sql-view changing sql-view definitions –  Exchanging the sql-view by another one –  Changing of the source-type (view/ table, DSO) – from externally to BW-managed –  Changing the location of non-BW sources (local- , remote-view) without making investments in multidimensional function modeling (Open ODS View semantics & associations modeling) and querying obsolete - as long as the new source offer comparable fields

�  That allows starting with the ‘cheapest’ solution design in a kind of prototyping mode –  Preventing/ reducing early investments in moving data (ETL, SLT) –  Focusing on business requirements first

With the option to grow subsequently into an integrated, managed EDW or EDW-like solution (industrialize) - partly or entirely -> incremental EDW modeling



* Pilot only


BW on HANA open functions and scalable integration Incremental modeling process - integration

Model BW on HANA field-based functions

on Star Schema

Model Star Schema

Model Data Delivery (sources)

Model Integration, Standards

(EDW/ LSA++) Multidimensional modeling with Open ODS Views happens normally in a broader context described by guidelines on EDW/ LSA++/ integration and on data delivery We have already a feeling that new BW on HANA will have a big influence on future solution delivery but how does it fit in such a broader BI architecture context? This section illustrates how BW on HANA field-based modeling can be embedded into a more factory like BI architecture context

Incremental modeling of data delivery �  Independency of Open ODS Views from source location (data delivery)

Incremental integration of field data with EDW �  Integration of Open ODS Views into an EDW context (InfoObjects)

�  Field-based DSOs* – BW persistency & staging service for all

* Pilot only


BW on HANA open functions and scalable integration Field-based modeling and integration with EDW content

Source - 3NF Model



Open ODS View

sql-view DSO – Field*

Local replicate


generate

BW DataSource

DSO - InfoObject integrate InfoObject

Integrate

transform

Integrate

EDW

Open ODS View integration with EDW �  Combining Open ODS Views with EDW InfoProviders in a

Composite Provider �  Associating (partly) InfoObjects to Open ODS View fields �  Open ODS View as DataSource template for EDW provisioning

* Pilot only


BW on HANA open functions and scalable integration Open ODS View integration with EDW content – associating InfoObjects

Table

SQL View

Open ODS View

Master data


Virtual Data Mart – Virtual Star Schema

InfoObject Tables

Open O

DS H

AN

A D

B

EDW


Table Table /Table Field DSO

/Table Field DSO

Open ODS View

Master data

Open ODS View Fact data

InfoObject Master data

InfoObjects can be assigned to any field of any Open ODS View

�  InfoObjects behave like dimensions (navigation attributes)

�  Snow flaking is not supported except for texts

�  InfoObject authorizations may be inherited

�  Hierarchy support

�  Open ODS View master data and InfoObject master data are supported for the same source-field (local and EDW dimension)


Demo 5 – Associating InfoObjects to Open ODS View fields

Open ODS View - facts Open ODS View - Customer master data

Open ODS View - Product master data

Demo


BW on HANA open functions and scalable integration Demo 5: Associating InfoObjects to fact data – local keys & EDW keys

Different fact ODS View fields to assign product master data:

�  PRODUCT_ID – ODS view ‘TT-Product’ (local)

�  PRODUCTNUMBER – InfoObject ‘ZEDWPROD’

Solved via sql-view joining Product table to fact sql-view


BW on HANA field-based modeling & integration Demo 5: Associating InfoObjects to fact data – multiple dimensions for field

Same fact source-field CUSTOMERID shall :

�  ODS view ‘TT-CUSTOMER’ (local) and

�  InfoObject ‘ZEDWCUST’ (as EDW master)

Solved via duplicating field in Open ODS view ( as CUSTOMER1)



* Pilot only


BW on HANA field-based modeling & integration Open ODS Views & Field-based DSOs* for non-SAP data extraction

Source - 3NF Model

DSO - InfoObject

denormalized model - field SAP Application Extract - ∆ Queue

Non-SAP Application Extract – BO-DS

InfoObject

Integrate

transform

BW DataSource

Integrate

persisted data

No persisted data

load

virtual access

Open ODS View integrate

DSO - Field


Loading non-sap data provided e.g. by BO-DS to Field-based DSOs has the advantages

�  Partial, incremental InfoObject creation, assignment in Open ODS View

�  Reduced source data formatting issues

* Pilot only


BW on HANA field-based modeling & integration The value for non-SAP data integration in an BW EDW

Field-based modeling in an EDW Context will open the door for integrating and function modeling on non-sap data in a BW EDW faster and cheaper without losing services – on the contrary – no more meaningless InfoObjects - the EDW data model will stay clean

Not with Field-based DSO* staging & Open ODS Views If you do not know the meaning of a field or in case you

are not sure about it – don’t create an InfoObject

L – I will have to create/ assign 85 InfoObjects to load, stage and query this data

* Pilot only



BW on HANA open functions and scalable integration LSA++ for EDW-centric and open functions BW

LSA++ for EDW centric BW LSA++ for open functions BW

* Pilot only


BW on HANA open functions and scalable integration Consequences on architecture and BI process

BW on HANA & LSA++

•  Propagate an iterative incremental multi-dimensional & EDW modeling approach

�  Offer stability thru an EDW framework defined by LSA++ Layers and common EDW dimensions defined by core InfoObjects

�  Offer openness and responsiveness thru field-based function and scalable integration modeling, which will especially be valuable with non-sap data regardless of data provisioning

�  Enable a responsive BI Process - starting with the ‘cheapest’ solution design (consume instead move) in a kind of prototyping mode

–  Focusing on business requirements first �  Subsequently optionally growing into an integrated , managed EDW or EDW-like

solution (industrialize) - partly or entirely


BW on HANA & LSA++ Towards a streamlined, responsive BI architecture

BW EDW

SAP Enterprise Applications

Non-SAP Enterprise Applications

Local DWHs

local Applications

Architected Data Marts Independent Data Marts

EDW

Open ODS

�  Open ODS field-based modeling

�  Streamlined data provisioning

–  On remote data o  HANA Smart Data Access

–  Open functions modeling on any data o  Open ODS Views o  Field-based DSOs*

–  Scalable integration modeling Open ODS

BI Architecture Components & BW on HANA �  Open functions and scalable integration

BW on HANA & LSA++:

BW on HANA & LSA++ open functions and scalable integration

* Pilot only


Further Information

SAP Education and Certification Opportunities www.sap.com/education

Watch SAP TechEd Online www.sapteched.com/online RDP270 - REAL-TIME DATA WAREHOUSING WITH SAP NETWEAVER BUSINESS WAREHOUSE 7.40

SAP Public Web BW on HANA FAQ - http://spr.ly/bwonhanafaq scn.sap.com


© 2013 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Documents

A Holistic BI Architecture with SAP NetWeaver Business Warehouse