Skip to end of metadata
Go to start of metadata


1 - General Information

2 - Analysis for Office client tool

Analysis Office Client versions

Future Release:

Currently there is no plan for a AO 2.9 release.  Instead there will be frequent SPs for AO 2.8. 
This will not have any impact on the support, which has been announced in the Product Availability Matrix until 2027.

Release

Product VersionStatus
2.8 SP12-Planned (CW 47, 2021). See note 3051730
2.8 SP11-Planned (CW 39, 2021). See note 3051741
2.8 SP10-Planned (CW 30, 2021). See note 3051755
2.8 SP92.8.900.96586Released (CW 23, 2021). See note 2993498 (Contains EPM Add-in SP38 patch 5. See SAP Note 3043664latest 2.8 version
2.8 SP82.8.800.96347Released (CW 14, 2021). See note 2993475 (Contains EPM Add-in SP38 patch 4. See SAP Note 3011303)
2.8 SP72.8.700.95947Released (CW 06, 2021). See note 2993485 (Contains EPM Add-in SP38 patch 3. See SAP Note 3001963)
2.8 SP62.8.600.95340Released (CW 48, 2020). See note 2927196 (Contains EPM Add-in SP38 patch 2. See SAP Note 2954008)
2.8 SP52.8.500.94986Released (CW 41, 2020). See note 2924400 (Contains EPM Add-in SP38 patch 1. See SAP Note 2951215)
2.8 SP4 patch 12.8.401.94659Released (CW 35, 2020). See note 2959437 
2.8 SP42.8.400.94350Released (CW 31, 2020). See note 2924387 (Contains EPM Add-in SP38. See SAP Note 2920897)
2.8 SP3 patch 12.8.301.94265Released (CW 29, 2020). See note 2948273 
2.8 SP32.8.300.93887Released (CW 22, 2020). See note 2917177 (Contains EPM Add-in SP37 patch 1. See SAP Note 2902111)
2.8 SP2 patch 12.8.201.93748
Released (CW 18, 2020). See note 2919308 
2.8 SP22.8.200.93367Released (CW 14, 2020). See note 2679436 (Contains EPM Add-in SP37. See SAP Note 2825503)
2.8 SP12.8.100.92864Released (CW 05, 2020). See note 2679485 (Contains EPM Add-in SP36 patch 1. See SAP Note 2854019)
2.8 SP02.8.000.92058Released (CW 48, 2019). See note 2679473 (Contains EPM Add-in SP36. See SAP Note 2778197)


Note that there is a component included in Analysis for Office tool, which is responsible for the communication with the backend. This component is called BI Consumer Service (BICS).

  • BICS 2.0 is used in Analysis Office until 2.4
  • BICS 3.0 is used in Analysis Office from 2.5 onwards

Whenever opening in AO 2.4 version (or lower), a workbook that was saved using AO 2.5 or higher version, the warning message below will occur:
"XML stored with a newer BICS version (XML version 3.0, client version 2.0)"

It means that some issues might occur, since new versions can contain improvements and new functionalities.
Opening workbooks saved with 2.4 or lower version using AO 2.5 or higher version should never be a problem. This is why the recommendation is to always use new and higher versions to open workbooks saved in old versions. See SAP note 2546926.

3 - Analysis Office Add-On for SAP BI Platform

Currently the AO BIP ADD-ON is only available for Windows. There is no version available for others operating systems (e.g. Linux).

4 - Why test with latest AO patch?

  • Investing the time to locate the error which is already solved with current patch is not very useful. Thus testing with latest patch is very important.
  • We understand that AO patch cannot be rolled out to thousands of users every quarter/month. But it is recommended to install the latest AO patch on one test PC to test the issue.
  • Installing a new AO patch on a test PC is neither time consuming nor complicated. It takes less than 10 minutes.
  • If confirmed that the issue is solved with latest AO patch, then this will save a lot of time that is needed with incident creation (by customer) and analyzing the issue (by customer & SAP Product Support).
  • It is only possible to provide a correction based in the latest patch. Therefore, even if an error is occurring in lower patch, the solution cannot be provided for that lower patch.
  • In contradiction to ABAP correction, AO correction cannot be provided as code-snippets, thus the complete AO patch needs to be installed. Even if emergency hotfix patch is released, the solution will be a complete update of the AO patch.
  • Generally, multiple errors are corrected in each AO patch. Important errors are documented in SAPNOTE, but NOT ALL. This means that the issue might be already solved in the latest AO version but no SAPNOTE is available.

5 - SAP Ramp-Up

Ramp-Up is SAP's early adoption program for customers who want to go live with SAP's software innovations as soon as possible. For more information about it click here. Any issue accessing Ramp-Up version of software on the SMP, please log a message under Component: XX-SER-SAPSMP-SWC.



Link to this page: http://wiki.scn.sap.com/wiki/x/j41IGQ

15 Comments

  1. Former Member

    Very good summary!

    One question, since I could not find the answer to it anywhere: Is it (and how) possible to "lock" old AO versions. E.g. how can we prevent users to continue using 1.4.x versions? For Bex Query Designer there are settings with which you can exit, and you need to use EQD instead. Is there a registry or conf.-file parameter with which to force a 2.x version?

    The "MinorVersion" parameter seems only optional: "You use this setting to specify the minor version that should be used."

    Thanks, Martin

    1. Hi Martin,

      Thank you for the feedback.

      Regarding your question, currently there is no option to prevent users to use old AO versions, but this is a very good/interesting feature to have. Thus, I strongly recommend that you request this feature in our Customer Influence site: https://influence.sap.com/SAPBusinessObjectsAnalysiseditionforMSOffice.

      The MinorVersion setting will not help in this case.

      Kind Regards,
      Filipe Zeuch
      SAP Product Support

  2. Former Member

    Thanks Filipe for your answer.

     No, I will not request this. If you think this is a valuable feature, then just implement it! The world is not improving by talking about it, but by acting.

    Btw. why do we always have to request "new features" if this kind of functionality has been known long before, like in BEx Query Designer or BEx Analyzer etc.

    Actually it is a "forgotten feature" ... Maybe our expectation is just too high, to get a tool, which is worth its title "premium alternative"? No answer needed, just think about it.

    Regards, Martin

    1. Hi Martin,

      Thank you for the feedback. From Product Support team I am not able to implement the feature, but we have the development team which is responsible for that.

      This is why we have the official platform that I sent to you. The developers check that platform regularly and move the requests to the backlog for implementation, depending on the rating and feasibility.

      Therefore, I have created this request there. You can follow it in the link https://influence.sap.com/sap/ino/#/idea/201525.

      I appreciate your comment and I encourage you to continue help us to improve the tool. Many functionalities that exist in the tool were suggestions that came from users and customers.

      Regards, Filipe

  3. Former Member

    Which document does describe compatibility of Analysis for Office client tool and Analysis for Office Add-On for SAP BI Platform?

    For example: An Analysis workbook is created in Analysis 2.5. Are there any restrictions to create a schedule on BI Platform with Analysis for Office server Add-On 2.3?

    Thank you,

    1. Hi Vlad, 

      It's listed in the last section of each of the "Essential Information" documents attached to the corresponding A4O release in PAM. 




      Glen 

      1. Former Member

        Hi Glen -

        The last section only talks about the Add-on for SAP BI platform. What version of AO Add-on is supported with BI platform version but not the AO client version. Like Vlad asked are there any restrictions to schedule a AO work book created on 2.5 version to run on a 2.3 Add-on? Thanks in advance!

        Praveen

        1. Hi Praveen, Hi Vlad,

          SAP always recommend to use the latest version of both: AO client and AO BIP ADD-ON. This is because some corrections and improvemens may be included in both versions.

          However, I am not aware of a document describing the restrictions when using AO client and AO BIP ADD-ON in different versions. In general, this should not be a problem, as there is no direct relation between them.

          Kind Regards,
          Filipe

          1. Former Member

            Thank you, Felipe.

  4. Hi folks.  We're testing Analysis 2.8 with our latest Office 365 update. 

    We're upgrading via "click-to-run" from Office 365 Release 1808 to Release 2002
    But after we've updated Office, we are getting the following error when we try to launch SAP Analysis for Office 2.8. 

    Could not start (or attach to) Excel Application.

    Even tried a de-install/re-install, but no dice.  Not finding any useful KBAs in SAP Support.

    I'm going to log a ticket with SAP Support about the issue.  But was wondering if anyone else has run into these types of issues with Office 365 upgrades, and what you had to do get the SAP Analysis add-in working again.

    Thanks!

  5. Hi Corey,

    Was AO working before the upgrade of MS Office?

    Have you checked SAP note below?
    >> 2409901 - Launcher could not attach to Excel Application

    I think that if the note does not help or is not applicable, open the ticket to SAP providing the traces by following the instructions of SAP note 2129389.

    Regards,
    Filipe

    1. Hi Felipe.  Yes, it was working before the upgrade of Office from build 1808 to 2002. 

      I've also tried downloading the 2.8.500.4986 (2.8 SP5 Patch 0 - June 2020 version) and installing it after the 2002 upgrade.  Same error.

      I'll take a look at the note and will update here with my results.  I've already logged a ticket with SAP Support on the issue. 

      1. As per the note 249901 - doing a REPAIR on MS Office 365 fixed my issue.  YAY!

        I had another tester try the O365 upgrade as well, and on his machine, after upgrading from Office 365 build 1808 to 2002, his SAP Analysis Add-In worked fine first try with no issues.  So this was a PC-specific issue in our case.  But good to know that an O365 repair does the trick. 

        From reading through the details of note 249901, it sounds like old Office-related registry entries cause this issue and the O365-repair feature cleans them up.  My PC is old and has had multiple upgrades over the year, but my other tester's machine is quite a bit newer, and probably doesn't have all that "registry dust" hanging around.  (smile) 

        Thanks again for the assist Felipe!  Greatly appreciated.

        1. Hi Corey,

          Great news! I'm glad to hear that the issue has been fixed after a repair in MS Office! (smile)
          I have also found and replied the ticket that you logged with SAP. 

          1. Aha!  I didn't know the two were connected.  (smile)  Sorry for the ticket noise!  But I gotta say, I really appreciate the super-fast response Felipe!    Ask for a raise!  (smile)  Thanks again!