Skip to Content
avatar image
Former Member

office 365 compatibility with EPM 10.0 and EPM addin with AO

Hi All,

I am looking for help if some one using the Office 365 2016 with EPM Add-in Analysis 2.3 Base version. We are using this point and facing lot of issue in Reports of BPC which were created in version of 2007 and 2010 MS Office but now Reports are not working properly after upgrade to MS Office 365 2016

Please help me to let me know the best compatibility to reduce the issues.

Thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • Dec 11, 2016 at 04:10 PM

    What BPC model are you using? Standard or embedded?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 12, 2016 at 08:05 AM

    Hi Mirza,

    What kind of problems are you facing with the reports? Is VBA used?

    For EPM 10.0 compatibility check the note given in this discusion...https://archive.sap.com/discussions/message/15959491

    For EPM Plug in in AO check these... https://blogs.sap.com/2016/05/10/what-is-new-in-analysis-office-23-asug-webcast-summary/

    https://support.sap.com/content/dam/library/ssp/infopages/pam-essentials/SBOP_Analysis_MS_22.pdf - PG.No 10 check the notes given.

    Regards,

    JP

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 07, 2017 at 01:28 PM

    Hi Vadim, sorry for late reply I was on vacation. we are using Standard BPC Model, the mean issue we are facing is my client have almost 3 thousand Reports saved in Share folder so Non- BPC user can able to open it and prior to 365 2016 with EPM Add-in Analysis 2.3 Base version with MS Office 2010 Non-BPC user were able to open the Reports with out any issue but after upgrade to 65 2016 with EPM Add-in Analysis 2.3 Base version when Non-BPC user tried to open up the Reports they are getting #NAME error in their Reports.

    Please help

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 08, 2017 at 03:07 PM
    Hi Vadim,
    
    Please below find the step by step details with screen shot 
    
    Prior to Upgrade
    1.My Client was using BPC 10.0 Standard Office 2010 SP Level 11
    2.When BPC user sent out the Reports to Non SAP BPC user the Non BPC user was able to open up the Reports without any 
    Error
    After Upgrade to Analysis 2.3 bounded with EPM Add-in with Office 365 2016
    
    1. After upgrade whenever Non BPC user tried to open up the Reports getting #NAME Error in Row, Column, Page Key Axis
    and and EPM function used
    
    Please find attached screenshot 
    
    Thanks,
    Mirza
    
    name-error.png
    
    
    Add comment
    10|10000 characters needed characters exceeded

    • Also not clear: "1.My Client was using BPC 10.0 Standard Office 2010 SP Level 11"

      SP Level 11 - what application?

      What client was used? EPM??

      What was used for non BPC users?

      Why you decided to use AO 2.3 for standard model? Why not EPM add-in?

  • avatar image
    Former Member
    Jan 09, 2017 at 03:59 PM

    Hi Vadim,

    Please below find the details of your question

    For SAP Level I mean when we check in BW side it's shows

    a. Component: CPMBPC

    b. Release: 800

    c: SP Level: 0011

    2. As I mentioned that we are using AO 2.3 analysis bundled with EPM Add-in and EPM Add-in is SP 25

    3. The Non BPC users which don't have BPC install their machine and BPC users need to send the Reports

    4. Our Basis team decided to go for Analysis AO 2.3 because they wanted to install Analysis AO 2.3 and EPM Add-in in single shot

    I hope this will

    Thanks,

    Mirza

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 10, 2017 at 03:59 PM

    Prior to Analysis AO 2.3 we were using EPM Add-in SP 19

    And the reason behind is that SAP recommended to use Unified AO 2.3 bundled with EPM Add-in

    Thanks,

    Mirza

    Add comment
    10|10000 characters needed characters exceeded