This was a webcast today with SAP’s David Stocker.

The usual SAP legal disclaimer applies that things in the future are subject to change

New roadmaps are coming at Las Vegas SAP TechEd

/wp-content/uploads/2014/09/1aroadmap_541361.png

Figure 1: Source: SAP

BW supports of all BEx queries, calculated/restricted measures, structures, all types of variables, special OLAP functions, runtime currency conversion, variable merge and unmerge, full hierarchy support, and compact axes as of Q3 2014

In Q4 SAP plans to release in November Analysis Office 2.0

Convergence with Live Office is not in immediate timeline; SAP is working on EPM client

A future direction for Analysis Office to store and run on HANA and where HANA is acting as BIP/BW

/wp-content/uploads/2014/09/2unifiedplanning_541362.png

Figure 2: Source: SAP

Figure 2 covers the EPM for BPC server

There is a convergence strategy with Analysis Office & EPM the speaker said they are not there yet

There is a NetWeaver Planning model in BW 740.  The next step comes in Analysis Office 2.0 to implement a core framework with both apps installed together.

/wp-content/uploads/2014/09/3hanamodelsaoffice_541363.png

Figure 3: Source: SAP

Native means connecting to the HANA backend up until 1.4 using the ODBC connection.  Customers for security reasons can’t use ODBC.

With Analysis 2.0 you can do http or https connection to backend to be used for Cloud with the BICS on client on backend

/wp-content/uploads/2014/09/4figaoffice20_541364.png

Figure 4: Source: SAP

Figure 4 shows how to define a local connection in Analysis Office 2.0: Use context menu and insert host name, port

/wp-content/uploads/2014/09/5aofficehanasupportedfeatures_541365.png

Figure 5: Source: SAP

Figure 5 shows HANA /Analysis Office supported features, including scaling factor support

/wp-content/uploads/2014/09/6featuresnotsupported_541366.png

Figure 6: Source: SAP

Level based hierarchies can’t have multiple parents; this also applies to Design Studio

SAP note 2038663 is a general BICS on Hana limitation which also applies to Design Studio

The speaker said “any limitation here also applies to Design Studio”

/wp-content/uploads/2014/09/7platformrecom_541367.png

Figure 7: Source: SAP

BIP is the recommended platform

/wp-content/uploads/2014/09/8figurea20sso_541368.png

Figure 8: Source: SAP

SAML ticket is the same mechanism that Design Studio uses in the BI Platform to Hana scenario

/wp-content/uploads/2014/09/9aofficehanabest_541369.png

Figure 9: Source: SAP

The best practices are also the same for Design Studio

Build smaller, more dedicated calc views, easier for when user comes in contact with query

Part 2 is coming, focusing on Design Studio with Question & Answer

Related:

Consider attending SAP TechEd && d-code .  Join ASUG for the ASUG SAP TechEd Pre-conference HANDS-ON: SAP BusinessObjects BI 4.1, SAP BW and SAP BW on SAP HANA – All in One Day, October 20th.  This includes exercises for Analysis Office and SAP BusinessObjects Design Studio. Register today

Also see:

Stay Ahead : Attend TechEd && d-code – Win Big SAP BI BusinessObjects HANA Hands-on Sessions

Next week David Stocker is presenting BI on Excel Update and Roadmap at the ASUG SAP Analytics BusinessObjects Conference. See Predictive Analysis and Analysis Sessions a ASUG SAP Analytics BusinessObjects Conference

Join SAP at the end of October for Reporting & Analytics 2014 INTERACTIVE conference – register here

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Muthu Sethuraman

    Tammy,

    Thanks for the information. We are having challenges with single sign-on (SAML ticket from BI 4.1 to HANA). As mentioned in your webcast, it’s planned for future release. I’m interested to get more details on the workaround solution. How to get it done, in which system and the complexity of getting it done. It would be great if you can share the details.

    Best regards,

    Muthu S

    (0) 
  2. Tim Korba

    Tammy,

    i am a little confused on the above slides when it comes to hierarchies and I must just miss the difference.  It states hiearchies based on Analytic and Calculation Views are supported in Analysis for Office on Native HANA are supported and then it states display hierarchies are not.  Can you provide further explanation for me?

    Tim

    (0) 
  3. Tim Korba

    Tammy,

    in addition, you talk about best practices with Analysis views.  Are you referring to Analytic Views within SAP HANA should be the main source for end users within Analysis for Office?  Or is it stating that you should have Analytic Views within the Calculation View and that is ok.

    Tim

    (0) 

Leave a Reply