Skip to end of metadata
Go to start of metadata

1 - General Information

  • Please find the PAM details for Product Version SBOP ANALYSIS MS OFFICE 2.7 here, also in PDF version.
  • Please find the PAM details for Product Version SBOP ANALYSIS MS OFFICE 2.8 here, also in PDF version.
  • Hardware & Software requirements for Analysis, edition for MS Office see note 1466118.

    For MS Office 2016 installations, refer to the SAP note below, which describes a known issue introduced by MS Office update:
    2670331 - Analysis Office Compatibility issues after Excel 2016 update

2 - Analysis for Office client tool

Analysis Office Client versions


Product VersionStatus
2.8 SP6-Planned (CW 48, 2020). See note 2927196
2.8 SP5-Planned (CW 41, 2020). See note 2924400
2.8 SP4 patch 12.8.401.94659Released (CW 35, 2020). See note 2959437 - latest 2.8 version
2.8 SP42.8.400.94350Released (CW 31, 2020). See note 2924387
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
2.8 SP2 patch
Released (CW 18, 2020). See note 2919308
2.8 SP22.8.200.93367Released (CW 14, 2020). See note 2679436
2.8 SP12.8.100.92864Released (CW 05, 2020). See note 2679485
2.8 SP02.8.000.92058Released (CW 48, 2019). See note 2679473


Product VersionStatus
2.7 SP10 patch 12.7.1001.93285Released (CW 12, 2020). See note 2904706 - latest 2.7 version and the last planned support package
2.7 SP102.7.1000.93083

Released (CW 09, 2020). See note 2874414

2.7 SP92.7.900.92200released (CW 50, 2019). See note 2772754
2.7 SP8 patch 12.7.801.91780released (CW 45, 2019). See note 2851131
2.7 SP82.7.800.91299released (CW 39, 2019). See note 2772753
2.7 SP7 patch 12.7.701.91262released (CW 39, 2019). See note 2841165
2.7 SP72.7.700.90338released (CW 31, 2019). See note 2772706
2.7 SP6 patch 12.7.601.90251released (CW 29, 2019). See note 2814781
2.7 SP62.7.600.89395released (CW 21, 2019). See note 2768353
2.7 SP5 patch 22.7.502.89393released (CW 21, 2019). See note 2791706
2.7 SP5 patch 12.7.501.89013released (CW 18, 2019). See note 2785097
2.7 SP52.7.500.88128released (CW 12, 2019). See note 2738666
2.7 SP4 patch 12.7.401.87606released (CW 8, 2019). See note 2753563 
2.7 SP42.7.400.87314released (CW 5, 2019). See note 2733028
2.7 SP32.7.300.86673released (CW 51, 2018). See note 2609916 (Contains EPM Add-in SP34. See SAP Note 2678610)
2.7 SP2 patch (CW 44, 2018). See note 2709385
2.7 SP22.7.200.84890released (CW 40, 2018). See note 2609982 (Contains EPM Add-in SP33 PL01. See SAP Note 2667731)
2.7 SP1 patch 1

released (CW 35, 2018). See note 2678400

2.7 SP1

released (CW 31, 2018). See note 2609829 (Contains EPM Add-in SP32 Patch2. See SAP Note 2651143)

2.7 SP0 patch 1

released (CW 26, 2018). See note 2656890

2.7 SP02.7.000.82311

released (CW 24, 2018). See note 2609974 (Contains EPM Add-in SP32. See SAP Note 2608302)

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:


  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:

      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

      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. 


      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!


        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,

          1. Former Member

            Thank you, Felipe.