Modeling SAP NetWeaver BW and SAP HANA Mixed Scenarios · Modeling SAP NetWeaver BW and SAP HANA Mixed Scenarios ... the consumption of BW data by BO Explorer via HANA interfaces

Modeling SAP NetWeaver BW andSAP HANA Mixed ScenariosGabor KovacsCustomer Solution Adoption (CSA) - TIPNovember 14, 2012

© 2012 SAP AG. All rights reserved. 2Public

Agenda

SAP NetWeaver BW (on HANA) – SAP HANA Mixed ScenariosOverview

Consuming HANA Models in BW– TransientProvider on HANA Model– VirtualProvider on HANA Model– CompositeProvider– Virtual Master data InfoObject on HANA Attribute view

BW InfoProvider consumption in SAP HANA– Generate HANA Models from BW InfoProviders


Agenda





SAP HANA - Platform for different DataMarts

SAP BW SchemaSAP HANA Schema(s)

SAP HANA

SAP NetWeaver BW on HANA

EDW -Architected

DataMart

SAP HANA Studio

AgileDataMarts

SAP HANA as platform to deploy multipleapplications on top

See SAP Notes 1666670 & 1661202 formore information

Storing BW data and non-BW DataMart inthe same SAP HANA database

Multiple database schemas in one SAPHANA database

SAP HANA DataMart data can beintegrated in BW and vice versa

Access of BW managed data via own definedHANA views is not allowedInstead use generated HANA views(see SAP note: 1764251)

https://service.sap.com/sap/support/notes/1666670




SAP NetWeaver BW – SAP HANA Mixed ScenariosProviding additional flexibility

BW InfoProvider consumption in SAP HANA

SAP HANA model consumption in BW

Mixed scenarios include support of Open Hub to enable data loading from BW to HANA. Also the consumption of AnalyticViews generated in BW via HANA interfaces, the consumption of BW data by BO Explorer via HANA interfaces and data loadoptimizations from HANA to BW. SP 8 for SAP NetWeaver BW on SAP HANA - Overview

https://scn.sap.com/docs/DOC-32264


Agenda





Consumption of SAP HANA models in BW

SAP NetWeaver BW – SAP HANA Mixed Scenarios

SAP BW onHANA

InfoProvider TransientProvider

CompositeProvider

VirtualProvider

Query

MultiProvider

SAP BW Schema SAP HANA Schema(s)

SAP HANA

QueryQuery

HANA Analytic / Calc View


Consumption of SAP HANA Models in BW on HANATransientProvider vs. VirtualProvider

TransientProvider VirtualProviderInfoObjects optional InfoObjects mandatory

Limited integration with BWmaster data with assignedInfoObjects (No Nav.Attributes)

Full Integration with BWmaster data

BW Authorizations forassigned InfoObjects

All BW Authorizations

Combining HANA data withBW data viaCompositeProvider

Combining HANA data withBW data via MultiProvideror CompositeProvider

TransientProvider based on HANA ModelFor ad hoc scenariosGenerated not modeled, no InfoObjects requiredFull BEx Query supportCan be included in a CompositeProvider to combine withother BW InfoProviders

VirtualProvider based on HANA ModelFor a flexible integration of HANA data with BW managedmetadata (e.g. lifecycle)Security handled by BWFull BEx Query supportCan be included to Composite- and MultiProvider tocombine with other BW InfoProviders

Reporting on HANA models in BW-on-HANA (www.saphana.com)

http://www.saphana.com/servlet/JiveServlet/download/1463-2-4312/SDN_HANA_Models_in_BW+FINAL.pdf

http://www.saphana.com/


Agenda





SAP BW on HANASAP HANA Model

TransientProvider based on HANA Model

TransientProvider

RSDD_HM_PUBLISH

Execute Transaction RSDD_HM_PUBLISH in BW

InfoProvider:@3Z_COPA

Analytic Index:z_copa


TransientProvider based on HANA Model

DEMOSee next 5 slides for the screens


Publish HANA Model to BWTransaction RSDD_HM_PUBLISH

Execute Transaction RSDD_HM_PUBLISH

Select Package and Model from HANA

no need to maintain connection parameters

lower case Fields are excludedfrom the HANA Model


Publish HANA Model to BWAssign InfoArea


Publish HANA Model to BWCharacteristics and Key Figures

Transient InfoObjects are generated


Publish HANA Model to BWMaintain TransientProvider

Execute Transaction RSDD_LTIP


Publish HANA Model to BWMap InfoObject


TransientProvider based on HANA ModelConsiderations – HANA

HANA Model propertiesOnly HANA Models without mandatory variablesOnly Analytic views and Calculation views(for Attributes views see Virtual Master Data on HANA Model)

Provider name, Column namesThe complete name of the HANA model must not be longer than 63 characters(DB schema + package name + model name)Full model name <= 55 (ABAP API is _SYS_BIC:<package>/<name>)The column names of the HANA model must be UPPER CASE, <= 64 (attributes, with description max. 52),<= 57 (measures, with currency conversion max. 55)

Publish in BWHANA Model can be published only onceAll fields from the HANA model (no individual field selection)The technical name of the Transient Provider: ‘@3’ + HANA model name/alias (analytic index)The transient InfoObject technical alias: Providername + ‘@’ + column name/Alias


TransientProvider based on HANA ModelConsiderations - BW

No Transport -> Re-create TransientProvider in all systems (QA, PRDO)

Ad-hoc, frequent changing scenariosTransientProvider and BEx Query* is adapted automatically to changes in HANA Model (* complex query may not be able toadopt)

BW ModelingCan be only used as PartProvider in a CompositeProvider, No MultiProviderNot in RSA1 (even if InfoArea assigned) but in Query designer or when building CompositeProvider

InfoObject MappingNo navigational attributes (available as display attributes only): e.g. 0ACCNT_GRP is NAV of 0CUSTOMER 0ACCNT_GRP

Authorization relevant InfoObject – consider Analysis Authorizations and Analytic PrivilegesUse Master data text, hierarchy in BExAll Master Data values are available in BWConversion routines, Leading zeros – data in HANA ‘1000’ vs ‘0000001000’ in BWFiscal year/period mapping (GJARH – 0FISCYEAR)


TransientProvider based on HANA ModelAuthorization handling

Both Analysis Authorization (BW) and AnalyticPrivilege (HANA) are checked against the BW nameduser during query execution

Filter conditions are combined via UNIONBW named user and HANA user are identical(<userID> in BW same as <userID> in HANA)! No integration yet !

Design time – generic R/3 userYou only see those HANA models that are visible for thegeneric R/3 user in HANA. The access to the HANA databaseand metadata happens via the R/3 user, not the named user.the Analytic Privileges in HANA have to be granted to the R/3user.


SAP HANASAP BW on HANA

TransientProvider based on HANA ModelAuthorization handling

user ID: XYZ

Authorization

0SALESORG = ‘3000’

user ID: XYZ

Analytic Privilege

VKORG = ‘1000’UNION


TransientProvider based on HANA ModelQuery Designer








TransientProvider based on HANA ModelBex Query

RSRTuser restriction via Analysis Authorization (0SALESORG = ‘3000’)as well as Analytic Privilege (VKORG = ‘1000’)



RSRTuser with no restriction



RSRT


Agenda





VirtualProvider based on HANA Model


VirtualProvider based on HANA ModelAssign HANA Model Fields


VirtualProvider based on HANA ModelAssign HANA Model Fields

Use matching data types from HANA

_SYS_BI.M_FISCAL_CALENDAR


VirtualProvider based on HANA ModelConsiderations

Transport and Activation – Long Term ScenariosPossible to activate a VirtualProvider based on a HANA-model even if the HANA-model does not exist on HANA-DBYou can also transport this new VirtualProvider-type into another BW-system, even if in the target-system the HANA-modeldoes not exist on HANA-DBFully integrated in BW (InfoObjects, MultiProvider, CompositeProvider)

Assign HANA Model fieldsCharacteristics, Key figures, Navigation Attributes (optional)– Map to HANA field (data consistency!!, JOIN inside the HANA model)– BW InfoObject (Left outer JOIN between the X/Y tables, or P/Q-table if needed – read HANA and Attribute data in one step)Mapping recommendations (search strategy based on DDIC and TEXT)

Referential Integrity – performance optimizationInner JOIN to the x/y table if Navigational attributes are used, all HANA master data values available in BW)

AuthorizationOnly Analysis Authorization for BW user during query execution (HANA privileges are checked for the technical R/3/DB Useronly)


Agenda





CompositeProviderIntroduction

The CompositeProvider is a new InfoProvider type introduced with BW7.30It offers the possibility to combine InfoProviders via UNION, INNER JOIN and LEFT OUTER JOIN.

One “initial” Provider has to be taken over to the CompositeProvider with a UNION connection as abasis.

CompositeProviders can only be used in combination with BW powered by SAP HANA (andpartially with BWA, which is not covered in this presentation).

UNION and JOIN operations are executed in HANA and not the application server – if possiblefrom a data consistency point of view – without join column information.Consider Non-unique JOIN conditions (1:N, N:M)

BEx Queries can be created on CompositeProviders as on any other BW InfoProvider.

Fully integrated in RSA1 (SP8), transportable when all part-providers are transportable


CompositeProviderLimitations

Temporal JOIN: If a temporal JOIN between the Providers is needed, a CompositeProvider cannotbe used (currently only possible with InfoSet).

Non-cumulative key figures: Non-cumulative key figures currently cannot be used in aCompositeProvider.

Queries with Exception Aggregation: Exception Aggregation in Queries based on aCompositeProvider can only be executed on HANA (query option ‘6’) when standard, transportableBW InfoProviders are contained exclusively. Additionally, it is only possible to use ExceptionAggregation on InfoObjects for which SID-based processing is possible (Display Attributes e.g. areprocessed key-based).

Planning scenarios: Currently it is not possible to use a CompositeProvider as Provider forplanning scenarios.

SAP NetWeaver BW Workspaces (SCN)

http://scn.sap.com/docs/DOC-24093


CompositeProviderCreate New CompositeProvider – RSA1

1

2

Or Transaction:RSLIMOBW


CompositeProviderAssign fields


CompositeProviderMaintain field assignments, properties


CompositeProviderAdd JOIN composition


CompositeProvider


Consumption of SAP HANA Models in BW on HANAGeneral Recommendation

Know your HANA ModelComplexityCalculated/Restricted Attributes, MeasuresFilters, JOIN types

Consider OLAP vs. HANA modelingKeep HANA model simpleLeverage RKF, CKF, Exception aggregation, etc. in BW


Agenda





SAP NetWeaver BW Virtual Master DataHANA attribute view exposed as master data in BWNo data staging of SAP HANA master data requiredPrior to SP 8 information in master data tables stored inSAP HANA schema could only be consumed in BW queryvia staging into BW

SAP BWon HANA


SAP HANA AttributeView

VirtualInfo

Object

Master Data ReadClass

Query

InfoProvider

VirtualInfo

Object

VirtualInfo

Object

SAP HANA

Virtual Master Data on SAP HANA Attribute view

Easy consumption of HANA master data in BW queries


Virtual Master Data on SAP HANA Attribute view


Agenda





Generate Analytic View for BWInfoProvider via HANA Modeler

Generated Analytic View contains basic BWMetadataGenerated Analytic View can be consumed viaSAP HANA interfaces and used in further SAPHANA modelsThis enables SAP BO Explorer on BW dataOnly HANA-Optimized InfoCube and DSOQuery Snapshot (SAP Note 1769374)

SAP BWon HANA

SAP HANA Studio

SAP HANA

Explorerconsumes

BW Schema

SAP HANA


SAP HANA

HANA Analytic/CalcViews

generatesInfo

CubeDSO

Master

Data

BW Models to SAP HANA

Easy BW InfoProvider Consumption



Importing BW Models in SAP HANA

Only HANA-Optimized InfoCube and DSO

HANA-Optimized InfoCube-> Analytic View: <InfoCube>_INTERNAL-> Calculation view: <InfoCube>

HANA-Optimized DSO

-> Analytic View: <DSO>


Importing BW Models in SAP HANAAnalytic view from InfoCube

Referential join (N:1) betweenF table and SID table

Referential join (1:1) betweenSID and P tables

Text join (1:1) betweenP and T tables


Importing BW Models in SAP HANACalculation view and Analytic Privilege from InfoCube

Simple graphicalCalculation view


Importing BW Models in SAP HANAConsiderations

Prerequisites, limitationsSAP Note 1764251 - Documentation: Importing BW Models in SAP HANA Modelerimplemented SAP Notes 1703061, 1759172, 1752384 and 1733519SAP HANA 1.0 SP04 Rev 37SQL Privileges (BW schema to import)CKF, RKF need to be re-created in Calculation viewReporting: InfoCube generated Calculation view, DSO generated Analytic view

Analysis AuthorizationIf 0TCAIPROV included the authorization moved to HANA -> Analytic PrivilegeOther BW authorizations are not considered

Consistency of ModelsChanges in BW not automatically reflected in HANARe-import BW Models -> Overwrite changes in HANA



Importing BW Models in SAP HANAAdditional information

Modeler Unplugged: Episode 1.1 - Importing BW Models as Native HANA Models

Modeler Unplugged: Episode 1.2 - Understanding HANA Models imported from BW

Modeler Unplugged: Episode 1.3 - Exploring Data for HANA Models Imported from BW

http://www.saphana.com/community/blogs/blog/2012/09/27/modeler-unplugged-episode-11--importing-bw-models-as-native-hana-models

http://www.saphana.com/community/blogs/blog/2012/10/04/modeler-unplugged-episode-12--understanding-hana-models-imported-from-bw

http://www.saphana.com/community/blogs/blog/2012/10/11/modeler-unplugged-episode-13--exploring-data-for-hana-models-imported-from-bw

Thank youContact information:

Gabor [email protected]

mailto:[email protected]

Documents

Modeling SAP NetWeaver BW and SAP HANA Mixed Scenarios · Modeling SAP NetWeaver BW and SAP HANA Mixed Scenarios ... the consumption of BW data by BO Explorer via HANA interfaces