Skip to Content

SAP BusinessObjects Analysis, edition for Microsoft Office has just been released in its 1.1 version and is available for ramp-up customers. The MS Office edition of Analysis is a premium alternative to BEx analyzer. Version 1.0 was mainly targeted to introduce a new usability paradigm: simple, intuitive, tightly integrated into the Microsoft Office framework. This story is continued in release 1.1, which can be titled “planning release”. It leverages the BW-IP framework of SAP NetWeaver BW 7.x (also note the new features in BW 7.3 such as the new ABAP-based planning modeler) and extends it to an intuitive ad-hoc planning client. You may start your planning workflow within the design panel of Analysis – similar to how you analyze. You can enter new values, write them back to BW, add new lines or use planning functions or planning sequences. Adding new lines is easy – and supported by a value help for the dimension values as well as a validation of new entries with BW master data tables.

In addition to ad-hoc planning, you would certainly build powerful workbooks for planning (or, of course, for analyses). Release 1.1 extends the existing API (application programming interface) substantially. You can use a rich set of functions in your macros and your VBA code that affect the filters or prompts, execute drilldowns, execute planning functions or simply get contextual information on where the cursor is located. This enables you to build sophisticated workbooks targeted to your end users.

Analysis 1.1 runs on top of SAP NetWeaver BW – like the 1.0 release -, but can also connect to SAP In-Memory Appliance (HANA). You can use it stand-alone or you can run via SAP BusinessObjects BI platform. Together with BI 4.0, you can leverage single sign-on offered by the platform and you can interoperate with other clients such as Web Intelligencr, Crystal Reports or the web client of Analysis.

In addition, several continuous improvements features have made it into release 1.1, such as default workbook handling, remove data before saving (enforces refreshing upon opening a workbook), storing and using analysis views (when using BI platform), changing conditional formatting rules/filter by measure, and some more.

You can find detailed information in the “what’s new” guide.

To report this post you need to login first.


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

      1. Alexander Peter Post author
        Hey Mikhail,

        thanks for asking.
        I am proud to announce Anaylsis 1.1, edition for MS Office will generally available as of tomorrow, July 11 !!!
        Have fun using it !!


        1. Former Member
          Hi Alexander.
          Just in time… Thats great news!
          This news is worthy for a new blog ๐Ÿ™‚

          I am sure it isn’t easy to create software with tigher integration with MS products, but is challenge
          for you and your command.

          My ñongratulation for you and all the people who’s involved in this proccess.
          Please keep innovation temp for AAO.

          Count of users who use AAO in everyday work must be extremly grow – be ready for this.:)   

          I was gave my users AAO (for evaluation purposes) and collected feedback from them.
          Maybe this informations be usefull.


          Feedback from my users, who’s worked both with Bex and little bit with AAO:

          1. Default theme is grey, please add theme(-s) with more softly colors (comments mostly from womens :))

          2. Remove DrillDown by double click on column headers. (like in Bex)

          3. If you close AAO worbook, the aao ribbon is not active
              and you must close AAO and launch again. Strange AAO behavior. 

          4. On filter screens we caN search only by key or text – but often needed filtered by attributes.
             (for example materilal -> material group – you want to filter materails by only one matl. group)

          5. AAO behavior for a huge (long) query –

          6. On designe panel somehow highlight characteristics thats drilled now. 

          And last but least – Logon screen – must be like in all BO products – with combobox – connection types.

          1. Tammy Powlas
            Hello Mikhail,
            1) Re: default theme:
            you can create your own default theme; I will to try to find a recording to show you.  Do you mean style sheet?

            3) “3. If you close AAO worbook, the aao ribbon is not active
            and you must close AAO and launch again. Strange AAO behavior. ”
            You can simply create a new Workbook and the Analysis ribbon is active again

            The number of Analysis users where I work is growing too – although we are a small shop.

            I am going to go check out your idea now.


            1. Former Member
              Hi Tammy,
              Very glade to you.

              3) You can simply create a new Workbook and the Analysis ribbon is active again.

              I know that, but users warry on that (Oh my God, i was closed AAO Worksheet and AAO his dead :)).
              And if you want make AAO ribbon alive, you need to do additional steps (File->Create->Create WB) 

              More intuitive (imho) next logic:
              a) insert button always active.
              b) when push on insert and choose system and query – AOO checks is there any opened wb.
              c) If none – AAO created new WB and executed query on it.

              This logic it similar like in Bex 7.0.

              > The number of Analysis users where I work is growing too – although we are a small shop.
              Users loves to clients based on MS Office products, isn’t it ๐Ÿ™‚

  1. Former Member
    I hope with new Analysis, we’l forget about 750.00 cells limitation, like in Bex.
    (Note 1040454 – Front-end memory requirement of the BEx Analyzer).

    Sometimes end-user want to work with “heavy” query.

  2. Former Member
    Alex, thanks for your post.

    I hope with new in Analysis 1.1, we may forget about 750.000 cell limitation (like in Bex). – Note 1040454 – Front-end memory requirement of the BEx Analyzer.

    Sometimes user want to work with huge datasets.

  3. Tammy Powlas
    being able to edit Conditional Formatting in 1.1, changing the filtering by measure, and having the Analysis Add-In always available in the Ribbon.

    Thank you for the link!



Leave a Reply