SAP First Guidance– SAP BW 7.4 On SAP HANA - SAP HANA

Transcription

SAP First GuidanceSAP HANA ApplianceSAP BW 7.4SAP First Guidance – SAP BW 7.4 on SAP HANA SAP HANA View GenerationApplicable Releases:SAP BW 7.4 powered by SAP HANA, or higherThe first guidance guides are not intended to be exhaustive. The purpose of these documents is to deliveradditional information besides SAP Help and Blogs to get a better understanding of the concepts of SAPBW on HANA.For more information or feedback please contact: SAPBWProductManagement@sap.comAuthor: Silvia BratzVersion 1.1February 2015

Copyright 2015 SAP AG. All rights reserved.No par t of this p ubli cati on may be r epr o du ced or tr ansmi tte d in a ny f or m or for any pur p ose wi th out th e expr es s per missio n of S AP AG. Th e inf or matio n co nt aine d her ei n may b e ch ang ed wi th out pr ior no tice.Some sof twar e pr o duc ts mar ke ted by SAP AG and i ts dis tr ibu tor s co nt ain pr opr iet ar y sof twar e c ompo ne nts of o th er soft war e ve ndor s.Micr oso ft, Wi nd ows, Ex cel, Ou tlo ok, a nd P ow er P oint ar e regist er ed tr a demar ks of Mi cr oso ft Cor p or ati on.IBM, DB2, DB2 U niver sal Da tab ase, Sys tem i, Syst em i5, Syst em p, Syst em p5, Sys tem x, Sys tem z, Syst em z10, System z9, z10, z 9, iSer ies, pSer ies, xSer ies , zSer ies, eSer ver , z/VM , z/OS, i5 /OS, S/390, OS/ 390, OS/ 400, AS/400, S/390 P ar allel E nter pr ise Ser ver , P ower VM, P ower Ar chit ect ur e, P OWER6 , P OWER6 , P OWER5 , P OWER5, P OWER, O penP ow er , P ower P C, Batc hP ipes, Bla deCe nter , Sys tem Stor a ge, GP FS, HACMP , RE TAIN, DB2 Co nne ct, RACF, Re db ooks, OS/ 2, P ar allel Sys plex, MVS/ESA, AIX,Intelli gen t Miner , We bS pher e, N et fini ty, Ti voli a nd I nfor mix ar e tr ademar ks or r egister e d tr a demar ks o f IBM Cor por ati on.Linux is th e r egist er ed tr ademar k o f Li nus Tor val ds in t he U.S. a nd o th er cou ntr ies.Adobe , th e Ado be lo go, Acr o ba t, P ostScr ip t, a nd Rea der ar e ei ther tr a demar ks or r egister e d tr a demar ks o f Ado be Syst ems Inc or por a ted i n t he Uni te d Sta tes a nd/ or ot her co untr ie s.Or acle is a r egis ter ed tr ademar k of Or acl e Cor por a tio n.UNIX, X/Open, OS F/1, an d M oti f ar e r egis ter ed tr adem ar ks of the O pe n Gr ou p.Citr ix, ICA, P r ogr am Neigh bor ho od, Me taFr ame , WinFr ame, Vid eoFr ame , an d M ultiWin ar e tr ad emar ks or r egis ter ed tr ademar ks of Ci tr ix S ystems, I nc.HTM L, XML, XH TM L an d W3C ar e tr ademar ks or r egister e d tr a demar ks o f W3C , Wor ld Wi de Web C ons or tium, Massa chu set ts In sti tu te o f Te chn olo gy.Java is a r egis ter e d tr ad emar k of Su n Mi cr osys tems, In c.JavaScr ipt is a r egist er ed tr ademar k o f S un Micr osy stems, Inc., use d un der lice nse f or tec hn olog y inve nte d a nd impl emen ted by Ne tsca pe.SAP , R/3, SAP NetWeaver , Due t, P ar tner Edg e, ByDesig n, SAP BusinessO bjec ts E xpl or er , Str eamWor k, an d o ther SAP pr odu cts a nd s er vices men tio ne d her ei n as well a s th eir r espec tive lo gos ar e tr ad emar ks or r egis ter ed tr ademar ks of SAP AG in Ger many a nd o th er cou ntr ies.All other pr o du ct a nd s er vice nam es men tion ed ar e the tr ad emar ks of their r es pec tive c ompa nies. Da ta c ont aine d in this doc umen t ser ves i nfor ma tion al p ur pose s onl y. Nati on al pr o duc t spe cific atio ns may v ar y.The i nfor ma tion i n t his d ocume nt is pr opr ie tar y t o SAP . No par t of t his d ocum ent ma y be r e pr od uce d, co pied , or tr ansmi tt ed in any for m or for an y pur pose wi th ou t t he ex pr ess pr ior wr it ten per missio n of SAP AG.This doc umen t is a pr elimin ar y ver sion an d no t su bjec t t o yo ur license agr eeme nt or any o th er agr eeme nt wi th SAP . This doc umen t co nt ains o nly in te nde d str a te gies, d evel opmen ts, a nd fu ncti onali ties of t he SAP pr odu ct a nd is no t in ten ded to be bi ndi ng u po n SAP to an y par ti cular c our se o f b usines s, pr o duc t str a teg y, an d/ or devel opme nt. P lea se n ote th at this d ocum en t is su bjec t to cha nge a nd ma y be c ha nge d by SAP at a ny tim e wit hou t n otic e.SAP assumes no r esp onsi bilit y for er r or s or omissio ns in this doc umen t. SAP does not w ar r ant the accur a cy or com plet ene ss of th e inf or matio n, t ext, gr aphi cs, link s, or o ther it ems co ntai ned withi n t his mat er ial. T his d ocume nt is pr ovid ed wi th out a war r an ty of any ki nd, eit her expr ess or implied , incl udin g b ut n ot limi ted to the im plied w ar r anti es of mer c han ta bility, fit ness for a par ticul ar pur p ose, or n on -in fr ingeme nt.S AP shall have n o liabili ty f or dama ges o f an y kin d incl udi ng wit ho ut limit ati on dir ect, s peci al, in dir ect, or cons eq uen tial d amage s th at may r es ult fr om th e use of thes e mater ial s. T his limita tio n shall no t ap ply in c ases of in te nt or gr o ss ne glige nce.The s ta tu tor y lia bility for per so nal i njur y an d d efec tive pr od uct s is no t af fec te d. SAP has no con tr ol ov er the i nf or matio n t hat y ou ma y acce ss t hr oug h t he us e of ho t links con tai ned i n t hese ma ter ials a nd does no t en dor se y our us e of third -p ar ty Web pag es n or pr ovid e any w ar r anty wha tso ever r elati ng t o t hird- par ty W eb p ages .SAP “How-to” Guides are intended to simplify the product implementtation. While specific product features and procedures typically areBusiness Objects and the Business Objects logo, BusinessObjects,explained in a practical business context, it is not implied that thoseCrystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and otherfeatures and procedures are the only approach in solving a specificBusiness Objects products and services mentioned herein as well as theirbusiness problem using SAP NetWeaver. Should you wish to receiverespective logos are trademarks or registered trademarks of Businessadditional information, clarification or support, please refer to SAPObjects Software Ltd. Business Objects is an SAP company.Consulting.S ybase a nd Ad ap tive S er ver , iAnyw her e, Syb ase 3 65, SQL A nywh er e, an d o ther S yb ase pr o du cts a nd s er vices men tio ne d her ein as well as th eir r espec tive lo gos ar e tr ad emar ks or r egist er ed tr ademar ks of S yb ase, I nc. S yb ase is a n S AP company .Any software coding and/or code lines / strings (“Code”) included in thisdocumentation are only examples and are not intended to be used in aproductive system environment. The Code is only intended better explainand visualize the syntax and phrasing rules of certain coding. SAP doesnot warrant the correctness and completeness of the Code given herein,and SAP shall not be liable for errors or damages caused by the usage ofthe Code, except if such damages were caused by SAP intentionally orgrossly negligent.DisclaimerSome components of this product are based on Java . Any code changein these components may cause unpredictable and severe malfunctionsand is therefore expressively prohibited, as is any decompilation of thesecomponents.Any Java Source Code delivered with this product is only to be used bySAP’s Support Services and may not be modified or altered in any way.

Document HistoryDocument VersionDescription1.00First version of this guide1.10Updates version

Typographic ConventionsIconsType StyleDescriptionIconExample TextWords or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.Cross-references to otherdocumentationExample textEmphasized words orphrases in body text, graphictitles, and table titlesExample textFile and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.Example textUser entry texts. These arewords or characters that youenter in the system exactlyas they appear in thedocumentation. Exampletext Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.EXAMPLE TEXTKeys on the keyboard, forexample, F2 or ENTER.DescriptionCautionNote or ImportantExampleRecommendation or Tip

First Guidance SAP BW 7.4 on HANA – HANA View GenerationTable of Contents1.Introduction . 22.BW Model Import versus HANA View Generation . 33.HANA Model Generation Process . 43.13.23.33.43.53.6Settings . 4Access Rights . 4View Generation . 5Administration . 6Consumption . 7Check . 74.Integrated Scenario with Lumira . 85.Appendix . 165.15.2Online Documentation . 16Further Information and Blogs . 16August 20151

First Guidance SAP BW 7.4 on HANA – HANA View Generation1. IntroductionAn important part of the whole BW-on-HANA story is the option to create scenarios where dataowned and modeled within BW and data owned and modeled within native HANA tools interact.This is what we call mixed scenarios. The interaction can happen in both directions, from HANA toBW and vice-versa, and there are options to physically move the data or to virtually expose the data.The focus of this document is the exposure of BW data natively in HANA as HANA views that pointdirectly to the data and tables managed by BW. This enables HANA-native consumption of BW data.The goal is to provide a clean interface between the BW-managed schema and an area that ismanaged outside BW, e.g. by other tools or by a project team taking over management andsemantics that are built on top. The interface intends to make it very clear where BW's services endand where manual or 3rd party enhancements start. In that way, it gives room and provides freedomfor arbitrary designs and scenarios which goes along with the respective responsibility for thoseenhancements. It is clear that the generated HANA views are limited and cannot expose allsemantics defined and available in BW. However, they provide a well-defined and fantasticopportunity for arbitrary and externally managed scenarios. In general the generation of HANAviews in BW on BW data has been introduced as interface for stand-alone data marts. This meansthat HANA views are released (generated) for dedicated scenarios only, which have to be selectedexplicitly. It is not possible to handle the impact of changes in case views for all kinds of objects in aBW system would be generated and even further consumers (e.g. Calculation Views on top of theseAnalytic views) would use these.Supported BW objects are (see also sap help):- SAP HANA-optimized InfoCubes- (classic and advanced) DataStore objects- InfoObjects- Queries as InfoProviders- BEx Queries (with BW 7.4 SP08)- New CompositeProviders (created with the ABAP in Eclipse Modeler) and localCompositeProviders in the BW Workspace.SPOs, MultiProviders and Open ODS Views have to be consumed via the new CompositeProvider,i.e. a corresponding calculation view can be generated.Not all BW object properties can be added to the generated SAP HANA view. The followingproperties e.g. are not supported (see also online documentation [constraints]):Navigation attributes of InfoObjects, which do not have “standard” as their master dataaccess type, are not supported. If the navigation attribute is also authorization-relevant, it isnot possible to generate an SAP HANA view.Texts for InfoObjects, which do not have standard as their master data access type, are notvisible.SAP Note 2073820 describes in detail how to determine the text fields in the solutionsection.Non-cumulative numbers are only supported in the SAP HANA view for queries (key figureswith exception aggregation LAST [closing balance]).Key figures, for which the aggregation is set to “No Aggregation”, are not supported.Compounding is not supported: There is no attribute in the SAP HANA view, whichrepresents the chained value of an InfoObject with compounding.Date conversion and alpha conversion are not supported.BW hierarchies are not available in an SAP HANA view.Key figures of data type date or time are not supported with aggregation SUM.Characteristics with property “attribute only” are not supported.For more information on data from near-line storage, see SAP Note 2032797.Non-cumulative range key figures are not available in an SAP HANA view.The technical key figure 1ROWCOUNT is only supported for DataStore object (advanced),CompositeProvider and BW queries, which are based on a DataStore object (advanced) oron a CompositeProvider.August 20152

First Guidance SAP BW 7.4 on HANA – HANA View Generation2. BW Model Import versus HANA View GenerationSince HANA SP05 and BW7.3 SP8, it is possible

SAP does not w arrant the accura cy or com pletene ss of the information, text, graphi cs, link s, or other items contai ned withi n this material. This docume nt is provided wi thout a warranty of any ki nd, either express or implied, incl uding but not limi ted to the im plied w arranti es of merc hanta bility, fitness for a par ticul ar purpose, or non-infringeme nt. SAP shall have no .