SAP First Guidance SAP BW 7.5 powered by SAP HANA. SAP HANA Appliance

Transcription

1 SAP First Guidance SAP BW 7.5 pwered by SAP HANA SAP HANA Appliance First Guidance... LSA++ and SAP Business Warehuse pwered by SAP HANA Dynamic Dimensinal Mdeling thrugh Dynamic Star Schemas and Partitined Dimensins Applicable Releases: SAP Business Warehuse 7.5 pwered by SAP HANA Versin 1.1 March 2016

2 Cpyright 2016 SAP SE. All rights reserved. N part f this publicatin may be reprduced r transmitted in any frm r fr any purpse withut the express permissin f SAP AG. The infrmatin cntained herein may be changed withut prir ntice. Sme sftware prducts marketed by SAP AG and its distributrs cntain prprietary sftware cmpnents f ther sftware vendrs. Micrsft, Windws, Excel, Outlk, and PwerPint are registered trademarks f Micrsft Crpratin. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PwerVM, Pwer Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPwer, PwerPC, BatchPipes, BladeCenter, System Strage, GPFS, HACMP, RETAIN, DB2 Cnnect, RACF, Redbks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivli and Infrmix are trademarks r registered trademarks f IBM Crpratin. Linux is the registered trademark f Linus Trvalds in the U.S. and ther cuntries. Adbe, the Adbe lg, Acrbat, PstScript, and Reader are either trademarks r registered trademarks f Adbe Systems Incrprated in the United States and/r ther cuntries. Oracle is a registered trademark f Oracle Crpratin. UNIX, X/Open, OSF/1, and Mtif are registered trademarks f the Open Grup. Citrix, ICA, Prgram Neighbrhd, MetaFrame, WinFrame, VideFrame, and MultiWin are trademarks r registered trademarks f Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks r registered trademarks f W3C, Wrld Wide Web Cnsrtium, Massachusetts Institute f Technlgy. Java is a registered trademark f Sun Micrsystems, Inc. JavaScript is a registered trademark f Sun Micrsystems, Inc., used under license fr technlgy invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explrer, StreamWrk, and ther SAP prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f SAP AG in Germany and ther cuntries. Business Objects and the Business Objects lg, BusinessObjects, Crystal Reprts, Crystal Decisins, Web Intelligence, Xcelsius, and ther Business Objects prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f Business Objects Sftware Ltd. Business Objects is an SAP cmpany. Sybase and Adaptive Server, Anywhere, Sybase 365, SQL Anywhere, and All ther prduct and service names mentined are the trademarks f their respective cmpanies. Data cntained in this dcument serves infrmatinal purpses nly. Natinal prduct specificatins may vary. The infrmatin in this dcument is prprietary t SAP. N part f this dcument may be reprduced, cpied, r transmitted in any frm r fr any purpse withut the express prir written permissin f SAP AG. This dcument is a preliminary versin and nt subject t yur license agreement r any ther agreement with SAP. This dcument cntains nly intended strategies, develpments, and functinalities f the SAP prduct and is nt intended t be binding upn SAP t any particular curse f business, prduct strategy, and/r develpment. Please nte that this dcument is subject t change and may be changed by SAP at any time withut ntice. SAP assumes n respnsibility fr errrs r missins in this dcument. SAP des nt warrant the accuracy r cmpleteness f the infrmatin, text, graphics, links, r ther items cntained within this material. This dcument is prvided withut a warranty f any kind, either express r implied, including but nt limited t the implied warranties f merchantability, fitness fr a particular purpse, r nn-infringement. SAP shall have n liability fr damages f any kind including withut limitatin direct, special, indirect, r cnsequential damages that may result frm the use f these materials. This limitatin shall nt apply in cases f intent r grss negligence. The statutry liability fr persnal injury and defective prducts is nt affected. SAP has n cntrl ver the infrmatin that yu may access thrugh the use f ht links cntained in these materials and des nt endrse yur use f third-party Web pages nr prvide any warranty whatsever relating t third-party Web pages. SAP Hw-t Guides are intended t simplify the prduct implementatin. While specific prduct features and prcedures typically are explained in a practical business cntext, it is nt implied that thse features and prcedures are the nly apprach in slving a specific business prblem using SAP NetWeaver. Shuld yu wish t receive additinal infrmatin, clarificatin r supprt, please refer t SAP cnsulting. Any sftware cding and/r cde lines / strings ( Cde ) included in this dcumentatin are nly examples and are nt intended t be used in a prductive system envirnment. The Cde is nly intended better explain and visualize the syntax and phrasing rules f certain cding. SAP des nt warrant the crrectness and cmpleteness f the Cde given herein, and SAP shall nt be liable fr errrs r damages caused by the usage f the Cde, except if such damages were caused by SAP intentinally r grssly negligent. Disclaimer Sme cmpnents f this prduct are based n Java. Any cde change in these cmpnents may cause unpredictable and severe malfunctins and is therefre expressively prhibited, as is any de-cmpilatin f these cmpnents. Any Java Surce Cde delivered with this prduct is nly t be used by SAP s Supprt Services and may nt be mdified r altered in any way. ther Sybase prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f Sybase, Inc. Sybase is an SAP cmpany.

3 Dcument Histry Dcument Versin Descriptin 1.10 Adjustments with respect t terminlgy 1.00 First fficial release f this guide

4 Typgraphic Cnventins Type Style Example Text Descriptin Wrds r characters quted frm the screen. These include field names, screen titles, pushbuttns labels, menu names, menu paths, and menu ptins. Crss-references t ther dcumentatin Icns Icn Descriptin Cautin Nte r Imprtant Example Recmmendatin r Tip Example text Example text Example text <Example text> EXAMPLE TEXT Emphasized wrds r phrases in bdy text, graphic titles, and table titles File and directry names and their paths, messages, names f variables and parameters, surce text, and names f installatin, upgrade and database tls. User entry texts. These are wrds r characters that yu enter in the system exactly as they appear in the dcumentatin. Variable user entry. Angle brackets indicate that yu replace these wrds and characters with apprpriate entries t make entries in the system. Keys n the keybard, fr example, F2 r ENTER.

5 Table f Cntents 1. Intrductin SAP BW Classic Dimensinal Mdeling SAP BW extended Star Schema, SAP BW pwered by SAP HANA Flat Star Schemas Limitatins f SAP BW Classic Dimensinal Mdeling Dynamic Dimensinal Mdeling in SAP BW pwered by SAP HANA SAP BW Dynamic Star Schema - Separating Star Schema Mdeling frm Fact-Table Mdeling Scenari 1: SAP BW Dynamic Star Schema CmpsitePrvider n InfPrvider w. InfObjects Scenari 2: SAP BW Dynamic Star Schema - Virtual Remdeling f InfPrvider Scenari 3: SAP BW Dynamic Star Schema - Partitined Dimensins using InfObjects Scenari 4: SAP BW Dynamic Star Schema - Partitined Dimensins acrss LSA++ Layers Scenari 5: SAP BW Dynamic Star Schema Partitined, Federated Dimensins Scenari 6: SAP BW Dynamic Star Schema - Fact Table w. Fields and Partitined Dimensins SAP BW Dynamic Dimensinal Mdeling and Fields as Characteristics Scenari 7: SAP BW Dynamic Star Schema - Fact Table Federatin and Partitined Dimensins SAP BW Dynamic Dimensinal Mdeling and Perfrmance Summary...20 April

6 1. Intrductin SAP Business Warehuse pwered by SAP HANA ffers a multitude f new features that enable mre permeable, mre pen, mre flexible, in shrt dynamic, dimensinal data mdels vercming traditinal data warehusing brders. Remving brders between the Data Warehuse Layers will result in less persisted data stres - the LSA++ (Layered Scalable Architecture) fr simplified Data Warehusing. Remving brders between landscape cmpnents e.g. between SAP S/4HANA and SAP BW thrugh virtualizatin instead f data mvement will result in mre respnsiveness t business requirements - the LSA++ fr Lgical Data Warehusing. This paper describes the SAP BW pwered by SAP HANA Dynamic Star Schema, which is a new mdeling pattern partitining Dimensins (master data) f fact-table InfPrvider using Cmpsite Prviders r Open ODS Views f type fact. Partitining is a well-knwn technique when we have t manage cmplex situatins in the bradest sense. We knw it frm DB-partitining r frm lgical/ semantical partitining in SAP BW. Bth are bund t April

7 manage cmplex vlume scenaris. We will explain that partitining r splitting f Dimensins has a different target managing master data f cmplex entities hsting its attributes in different lcatins. With the Dynamic Star Schema and partitined Dimensins we achieve a new degree f dynamics and flexibility withut lsing the business rientatin f SAP BW. The scenaris discussed in this paper were verified n SAP BW 7.5 SP02 pwered by SAP HANA. 2. SAP BW Classic Dimensinal Mdeling SAP BW extended Star Schema, SAP BW pwered by SAP HANA Flat Star Schemas Classic Dimensinal Mdels in SAP BW has experienced an ptimizatin in terms f perfrmance frm the riginal Extended Star Schema n rw-stre RDBMS t Flat Star Schemas n SAP HANA (and BWA) clumn-stre. BW Flat Star Schemas n SAP HANA are knwn as HANA Optimized InfCubes and as the pssibility defining Star Schemas n DSOs fr direct querying. Despite the drastic perfrmance gains f SAP BW Flat Star Schemas n SAP HANA, the mdeling prperties f a flat Star Schema d nt differ frm the extended Star Schema Why? April

8 The InfObjects f type Characteristic play traditinally a central rle setting up a classic dimensinal mdel in SAP BW. InfObjects define the dimensins f the SAP BW Star Schema. Having the InfObjects defined in advance setting up a Star Schema in SAP BW is straight frward: The InfObjects that describe the fact table (DSO, InfCube) autmatically define the assciatins t the dimensins described by the navigatinal attributes and hierarchies f an InfObject. Thus the InfObjects f a DSO r an InfCube describe already the cmplete star schema. This is a rbust way f defining a star schema. If dne prperly it guarantees cnsistent, shared dimensins acrss the star schemas in an SAP BW Data Warehuse. 2.1 Limitatins f SAP BW Classic Dimensinal Mdeling Nevertheless this autmated, nt changeable assciatin f dimensins via InfObjects means limitatins with respect t Flexibility and adaptability Maintenance and stability Supprt f mdern federated DWH architectures This becmes bvius if we lk at cmplex DWH-entities like Material, Business-Partner, etc. The cmplexity derives frm the fact that different rganizatinal units have different views n an entity r even have different semantics fr it. Frm DWH perspective this means Different attributes Different wnership f attributes Different surces f attributes April

9 Different stability f attributes Different quality and latency Different change frequency requirements. Resulting in vlatility f a dimensin, which is challenging if a dimensin is mdeled by a single InfObject. Intrducing additinal attributes later n means always maintenance and changes f the prductive InfObject and ELT (extractin, lad, transfrmatin) path This impacts the verall stability and availability. We can bserve anther issue f autmated, nt changeable assciatin f dimensins if InfObjects are errneusly used in an InfPrvider. E.g. the InfObject that shuld be used is 0MATERIAL but in an InfPrvider ccurs ZMATERIAL. This causes a mdel incnsistency and redundant master data lads that can nly reslved via a cstly remdeling. April

10 3. Dynamic Dimensinal Mdeling in SAP BW pwered by SAP HANA SAP BW 7.5 pwered by SAP HANA cmes with several new features and functins that enable a pwerful, yet simple and dynamic way defining and maintaining the dimensinal mdel: Separatin f persistency mdeling frm semantics and assciatins mdeling Field-based mdeling in additin t InfObjects Federatin with external data Each feature by itself and in cmbinatin with each ther enables a new level f dynamics defining a dimensinal mdel in SAP BW. Prbably the mst interesting pattern we call the SAP BW Dynamic Star Schema. The fllwing chapter will elabrate this pattern step by step. 4. SAP BW Dynamic Star Schema - Separating Star Schema Mdeling frm Fact-Table Mdeling The SAP BW pwered by SAP HANA Dynamic Star Schema gets its dynamics separating the fact table mdeling frm star schema mdeling. As an SAP BW pwered by SAP HANA Dynamic Star Schema fact table may serve SAP BW InfPrvider whereby it is recmmended t use the new DataStre Object (advanced) - in shrt DSO (advanced), Still pssible are DSOs (classic) and InfCubes Any table r DB-view (lcal r remte) The SAP BW Dynamic Star Schema is mdeled using as a rule f thumb CmpsitePrvider n SAP BW fact-table InfPrvider f Integrated DWH/ Prpagatin Layer Unin-CmpsitePrvider n InfPrvider if yu nly want t define the Star Schema Open ODS view f type fact n DB-table/ -view and field-based DSO (advanced) f the Raw DWH / Open ODS Layer that serve as fact tables CmpsitePrviders and Open ODS views f type fact define Assciatins f master data (dimensins) Semantics fr fields April

11 It is imprtant t nte that als existing DSOs (classic) and InfCubes may serve as fact table surce fr a Dynamic Star Schema using a CmpsitePrvider! (Nte: Open ODS Views d nt wrk n DSO (classic) r InfCubes.) The definitin f a CmpsitePrvider n tp f DSOs (classic) and InfCubes is always recmmended yet nt enfrced. 4.1 Scenari 1: SAP BW Dynamic Star Schema CmpsitePrvider n InfPrvider w. InfObjects First let s investigate hw a star schema definitin using a CmpsitePrvider wrks n an InfPrvider (fact-table) that is built nly with InfObjects Scenari 1: SAP BW defines all persisted parts f the Dynamic Star Schema Fact Table: a DSO (advanced) (r existing DSO (classic) / InfCube) InfPrvider with nly InfObjects Dimensins: InfObjects Dynamic Star Schema: a CmpsitePrvider n tp f the InfPrvider. The CmpsitePrvider defines the dimensins - assciatins t InfObjects and Navigatinal Attributes April

12 SAP BW Dynamic Star Schema bservatins: The CmpsitePrvider prpses the InfObjects f the InfPrvider as standard assciated master data (dimensins) Navigatinal Attributes f assciated InfObjects are defined at CmpsitePrvider level fr a DSO (advanced) at DSO (classic) / InfCube: at CmpsitePrvider level and at DSOs (classic)/infcubes level Multiple CmpsitePrviders n the same fact-infprvider define multiple Star Schemas SAP BW Dynamic Star Schema and InfObject defining standard Dimensin Assciatin: 1. A CmpsitePrvider with standard assciatin fr InfObjects ffers the same functinality like the autmated InfObject assciatin in a DSO (classic)/infcube. 2. A CmpsitePrvider ffers the same abstractin t the InfPrvider persistency like the MultiPrvider in the Extended/ Flat Star Schema. April

13 4.2 Scenari 2: SAP BW Dynamic Star Schema - Virtual Remdeling f InfPrvider Nw we intrduce the new pssibility actively designing an SAP BW star schema. I.e. we can mdel the assciatins f master-data (dimensins)! Firstly let s stick t Dimensins defined by InfObjects. Scenari 2: Like Scenari 1 in additin The standard assciatin f an InfPrvider InfObject is exchanged with anther InfObject SAP BW Dynamic Star Schema bservatins: The assciatin f an InfObject is maintainable. Yu can replace the standard assciatin f the surce InfObject with anther InfObject that fits (frmat, length and f curse cntent) SAP Buisness Warehuse Dynamic Star Schema and Remdeling f InfObjects f an InfPrvider InfObject: 3. The SAP BW Dynamic Star Schema allws exchanging the standard assciatin derived frm the fact table InfPrvider InfObject with anther InfObject. That means a remdeling f errneusly mdeled InfPrviders (als DSOs (classic) and InfCubes) using an imprper InfObject can be dne n virtual CmpsitePrvider level April

14 4.3 Scenari 3: SAP BW Dynamic Star Schema - Partitined Dimensins using InfObjects Nw as we knw that we can mdel/ influence the assciatin f an InfObject f an InfPrvider facttable i.e. that we can influence the dimensin assignment, we want t g a step further assigning tw different InfObjects t the same InfObject f a fact-infprvider: Scenari 3: Like Scenari 1 in additin New attributes f an existing entity arrive. The new attributes have a different wner/surce than the attributes f the existing InfObject. Thus we have a situatin like described in chapter 2.1: We mdel the new attributes in a new InfObject In a CmpsitePrvider we want t assciate t the InfPrvider (Fact-table) InfObject the new InfObject in additin t the existing InfObject assciatin SAP BW Dynamic Star Schema bservatins: Yu can map a surce InfObject multiple times t CmpsitePrvider target-fields (target area). Edit the target-field name and change the name (which is as standard the name f the InfObject) t a different name the assignment frm surce t target persists Drag the surce InfObject again t the new target field. Nw we have the surce InfObject assigned t tw CmpsitePrvider target-fields April

15 In the CmpsitePrvider utput area yu can nw assciate different InfObjects (dimensins) t the CmpsitePrvider fields Define Navigatinal Attributes fr each assciated InfObject All this applies als t DSOs (classic) and InfCubes InfPrviders as surce bject f a CmpsitePrvider. SAP BW Dynamic Star Schema and Partitined Dimensins via InfObjects: 4. Yu may partitin the attributes f an entity acrss multiple InfObjects. Different wnership and prperties drive the partitining f the attributes int different InfObjects. The CmpsitePrvider allws assigning a surce InfObject t multiple CmpsitePrvider fields. The CmpsitePrvider fields can then be assciated with different InfObjects. April

16 All this applies als t DSO/ InfCubes InfPrviders as surce bject f a CmpsitePrvider A CmpsitePrvider defining a Dynamic Star Schema brings the partitined dimensins tgether again 4.4 Scenari 4: SAP BW Dynamic Star Schema - Partitined Dimensins acrss LSA++ Layers Ok, what s next? The DWH wrld has changed and we find the new paradigm f virtualizatin instead f persisting data. The answer f the LSA++ is prpagating permeability and emancipatin f the layers LSA++ layer permeability means transferring nly thse data t a subsequent layer if they experience a significant transfrmatin r significant increase f service ffering LSA++ layer emancipatin means that any layer within the DWH and utside f the DWH prvides wn value being a ptential target fr querying and analytics Scenari 4: Like Scenari 3 - in additin New attributes f an existing entity arrive. The new attributes have a different wner/surce than the attributes f the existing InfObject. We mdel a DSO (advanced) with the new attributes defined as fields and stre the new,master data in the DSO (advanced) The ADSO is a member f the Raw DWH/ ODS Layer We define an Open ODS view f type master n the (master data) ADSO defining semantics, text handling etc. In a CmpsitePrvider we want t assciate the new Open ODS view type master in additin t the InfPrvider (Fact-table) InfObject SAP BW Dynamic Star Schema bservatins: In a CmpsitePrvider yu can assign a surce InfObject t multiple CmpsitePrvider targetfields. The CmpsitePrvider target-fields can then be assciated with different InfObjects r Open ODS views f type master. April

17 All this applies als t DSOs (advanced) and InfCubes InfPrviders as surce bject f a CmpsitePrvider SAP BW Dynamic Star Schema and Partitined Dimensins acrss LSA++ Layers: 5. Yu can partitin the attributes f an entity int varius InfObjects and/ r DSOs (advanced). The chice depends n the layer- and service requirements Using Fields defining a DSO (advanced) means an additinal level f dynamics in dimensinal mdeling (bttm up). An Open ODS view f type master defines semantics, authrizatins, text handling etc. n fields f the master data stred in a DSO (advanced) A CmpsitePrvider may assciate Open ODS views f type master like InfObjects. SAP BW Dimensin Partitining using Open ODS views f type master facilitates dimensins acrss LSA++ Layers within SAP BW. Again a CmpsitePrvider n tp f a fact-infprvider brings the partitined dimensins tgether. 4.5 Scenari 5: SAP BW Dynamic Star Schema Partitined, Federated Dimensins LSA++ layer permeability and emancipatin is nt restricted t the SAP BW-DWH itself. The layer regardless where they reside (in- r utside f the SAP BW DWH) may verlap and the brders are n lnger strict. Any system in the landscape is a ptential surce f infrmatin valid integrating with the SAP BW DWH cre cntent. Scenari 5: Like Scenari 4 it differs in New attributes f an existing DWH-entity frm a remte surce shall firstly be virtually integrated Mdeling a persistency in SAP BW (InfObject, DSO (advanced)) is fr nw nt an ptin A SAP HANA remte surce cnnectin exists (SAP HANA smart data access/ Integratin) We define an Open ODS view f type master n a table/ view ffered by the remte surce SAP BW generates a HANA virtual table fr the Open ODS View In the Open ODS view type master we assign semantics, defining text handling etc. In a CmpsitePrvider we assciate t fact-data the new Open ODS view type master n remte master data in additin t an existing assciatin t an InfObject April

18 SAP BW Dynamic Star Schema bservatins: The CmpsitePrvider facilitates assciatins t Open ODS views f type master regardless f the lcatin f master data surce This applies als t DSOs (classic) and InfCubes InfPrviders as surce bject f a CmpsitePrvider. SAP BW Dynamic Star Schema and Partitined, Federated Dimensins: 6. SAP BW Dimensin Partitining enables slutins Where certain attributes f a DWH-entity reside inside SAP BW (InfObject r DSO (advanced) hsted) and thers utside f SAP BW ffered as DB-table/-view Where SAP BW ffers cleansed, cnsistent valued attributes f an entity and the nn-sap BW surce ffers e.g. real-time valued attributes 7. Open ODS views f type master Define thse parts f a dimensin (r an entire dimensin) that reside utside f SAP BW regardless whether the attributes reside n the lcal HANA-DB r n a remte DB. Address nn-sap BW master data and defining semantics n nn-sap BW master data. Generate an SAP HANA virtual table n a remte table/ view. Offer strng frmat transfrmatin capabilities fr surce fields Offer a service-level rientatin enabling transitin f virtualizatin t SAP BW persisted strage (DSO (advanced)) 8. Again a CmpsitePrvider n tp f a fact-infprvider brings a partitined, federated dimensin tgether again. 9. The partitined dimensin pattern enables federatin f master data. It is an essential part f a mdern SAP BW LSA++ fr Lgical Data Warehusing integrating with lw effrt/ n shrt ntice additinal master data int ur existing SAP BW dimensinal mdel April

19 4.6 Scenari 6: SAP BW Dynamic Star Schema - Fact Table w. Fields and Partitined Dimensins The dynamics f dimensinal mdeling in SAP BW pwered by SAP HANA is nt restricted t master data. Als mdeling fact data with DSOs (advanced) prvides additinal flexibility and dynamics using fields instead r in additin f InfObjects. Scenari 6: Like Scenari 4/5 but differs in The fact-table InfPrvider is a DSO (advanced) f the Raw DWH/ ODS Layer The DSO (advanced) cntains fields, InfObjects are pssible The fields have SAP BW-cmpatible frmats (e.g. n INTEGER frmats s. belw) April

20 In a CmpsitePrvider we assciate t fields f a fact-data DSO (advanced) multiple InfObjects and/ r an Open ODS views f type master SAP BW Dynamic Star Schema bservatins: The CmpsitePrvider handles frm mdeling perspective InfObjects and SAP BW-cmpatible fields in the same fashin i.e. Fields and InfObjects f a fact-table DSO (advanced) can assciate (partitined) master data / dimensins SAP BW Dynamic Star Schema and Partitined Dimensins n Fields f fact-table InfPrvider: 10. Using fields mdeling a fact-table DSO (advanced) f the LSA++ ODS/ Raw DWH Layer brings additinal dynamics ffering slutins in SAP BW n SAP HANA. Using fields is a cre pattern f LSA++ fr Simplified Data Warehusing. If the Fact- DSO (advanced) cntains nly fields with SAP BW-cmpliant frmats (s. belw) yu can define directly a CmpsitePrvider n this ADSO. In the CmpsitePrvider yu define Semantics f the fields (like aggregatin behavir fr key-figures) Assciatins f master data (InfObject/ Open ODS view type master) t fact-fields, which wrks in the same way like fr InfObjects. Assciatins f partitined master data (dimensins) t a fact-fields 4.7 SAP BW Dynamic Dimensinal Mdeling and Fields as Characteristics Cmmn fr all the Dynamic Star Schema scenaris we discussed s far is that They are defined by a CmpsitePrviders The fact-data are hsted by SAP BW InfPrviders The InfPrviders are defined by InfObjects (DSO (advanced), DSO (classic), InfCube) r SAP BW-cmpatible Fields (DSO (advanced)) April

21 The emphasis is n Fields that are SAP BW-cmpatible. S it s time talking abut Fields. In general using Fields defining fact- and master-data in SAP BW DSOs (advanced) r wrking with remte data means Mre dynamic, cheaper bttm-up mdeling, mre ptins Wrking and integrating data that are clser t the surce i.e. data f the Raw DWH/ ODS Layer r a remte surce It means n the ther hand that the mre we want t integrate r stre raw data the mre increases the need t handle a variety f data frmats: SAP BW-frmats / ABAP-frmats / DB-Frmats. This is the reasn that SAP BW pwered by SAP HANA cmes with tw kind f views defining a Dynamic Star Schema allwing efficient mdels n either SAP BW related InfPrvider r raw/ field data related InfPrvider/ surces: The CmpsitePrvider The Open ODS view f type Fact The fllwing picture shws, which ABAP-Field-frmats used in a DSO (advanced) can be handled by which SAP BW-view SAP BW Dynamic Star Schema and Fields in Fact-Tables: 11. A CmpsitePrvider n a fact-table InfPrvider defines a Dynamic Star Schema if the InfPrvider cntains nly InfObjects and/r SAP BW-cmpatible fields (n INTEGER fields) 12. An Open ODS views transfrms surce frmats int SAP BW cmpatible frmats n the fly as far as pssible. (Fr example INTEGER frmats t CHAR frmats). 13. If an Open ODS view cannt transfrm surce-field frmats n the fly yu can define an InfSurce n the surce ffering all the SAP BW transfrmatin capabilities. The Open ODS views is then defined n the InfSurce April

22 SAP BW Dynamic Star Schema and Open ODS Views f type Fact: 14. Like a CmpsitePrvider defines an Open ODS view f type fact a SAP BW Dynamic Star Schema n a fact-surce, i.e. Semantics fr fields (characteristic, key-figure, ) Assciatins f master data (dimensins) Assciatins f partitined master data (partitined dimensins) 15. An Open ODS view f type fact is necessary integrating field-level fact-data fr Remte fact data (DB-table/ view) DSOs (advanced) with Change-lg and Activatin-Queue if nt SAP BW-cmpatible fieldfrmats exist 16. There are sme restrictins t be bserved with respect t Open ODS views n DSOs (advanced) An Open ODS view defined n a DSO (advanced) always accesses the active-table. It fllws that an Open ODS view f type fact des nt supprt Near Line-Strage hsted data Cube-like DSOs (advanced) That des nt mean any restrictin with respect t remte fact-data 4.8 Scenari 7: SAP BW Dynamic Star Schema - Fact Table Federatin and Partitined Dimensins We cannt discuss here all the pwerful functinality f Open ODS views f type fact. We nly fcus n the pssibilities defining a Dynamic Star Schema. With SAP BW pwered by SAP HANA als remte fact data can be integrated n the fly using Open ODS views type fact. Scenari 7: The fact-table resides utside and are ffered as DB-table r DB-view (SQL- r HANA-View) The table r view may reside lcally n the same HANA-DB r n a remte data base accessible via SAP HANA smart data access We define an Open ODS view f type fact n such a surce In the Open ODS view f type fact we assciate t fact-fields multiple Open ODS views f type master and InfObjects April

23 SAP BW Dynamic Star Schema bservatins: Assciating master data (dimensins) and even partitined master data in an Open ODS views f type fact wrks like we knw it frm a CmpsitePrvider SAP BW Dynamic Star Schema and Open ODS Views f type Fact: 17. Any Open ODS views allw exchanging the surce against anther surce keeping the semantics and assciatins Open ODS views are an imprtant feature establishing the LSA++ Lgical Data Warehuse Open ODS views allw generatin f a DataSurce and a DSO (advanced) based n the Open ODS view definitin 18. Open ODS views f type fact can be used in a CmpsitePrvider as part f a fact-table Unin r Jin 5. SAP BW Dynamic Dimensinal Mdeling and Perfrmance Elabrating the seven scenaris I hpe that yu gt an impressin hw dynamic and flexible the dimensinal mdeling in SAP BW pwered by SAP HANA can be. But as always in life there is n free lunch. Gaining flexibility and dynamics in ur mdel means n the ther hand that we have t pay fr it. The flexibility gains are achieved splitting the dimensins in smaller, mre stable persisted pieces resulting in partitined dimensins. The partitined dimensins have t be cmbined (jined) again and query time that may mean a perfrmance penalty depending n the jin-cmplexity and partitin sizes. A secnd perfrmance aspect cmes with the usage f Fields. Using Fields instead f InfObjects means csts interpreting the data at query time. Csts that yu have frmerly spent mdeling and lading InfObjects. April

24 At the end virtualizatin must always pay back in business value at reasnable csts. 6. Summary SAP BW pwered by SAP HANA ffers a pwerful new way mdeling a star schema: the SAP BW Dynamic Star Schema. The SAP BW Dynamic Star Schema is mdeled either by A CmpsitePrvider r by An Open ODS view f type fact Depending n the fact-table surce. It is pwerful mdeling pattern as the Dynamic Star Schema allws cmbining fact data and master data (dimensins) acrss the layer brders within SAP BW and utside SAP BW (federatin) cmbining partitined master data (dimensins) Spanning the SAP BW Dimensinal Mdeling acrss the DWH-layers and beynd is a fundament defining a mdern SAP BW pwered by SAP HANA LSA++. Partitining f master data f cmplex entities and bringing them virtually tgether again in a SAP BW Dynamic Star Schema ffers a new degree f mdeling flexibility and respnsiveness t business requirements April

25 SAP First Guidance Cllectin: