BPC 7.5 NW upgrade to SP18: Add-in crashes when using Excel 2013

[former_member230099]

Hi all,

We are in the process of upgrading SAP BPC 7.5 NW from SP14 to SP18 level. At the same time we are moving from Excel 2010 to Excel 2013. So we are upgrading BPC 7.5 from Excel 2010 / SP14 to Excel 2013 / SP18.

We recently found out on our upgraded test environment that, when using Excel 2013, the BPC add-in crashes. This only happens with certain schedules. Finding the trigger has proven to be impossible so far.

When the BPC add-in crashes in Excel 2013 I notice the following behavior:

• Parts of the schedule are not displayed anymore (similar to Excel having a memory issue in the old days)
  This behavior seems to be related in particular to objects like header bars and buttons)
  
  
• Drop-down menus (eTools, eAnalyze, etc.) do not work anymore
• Typically, when refreshing or expanding the schedule, Excel freezes completely and a restart is required.

In general this "feels" like an Excel memory issue, but I'm certainly not sure about this!

Can you please let me know if I've stumbled upon a known issue with Excel 2013 and point to existing documentation? So far I haven't been able to find anything.

Regards,

Erwin

[former_member230099]

Issue is solved. Cause of the Excel 2013 crashes was the user having a corrupt user profile on his laptop. Seems like Excel 2013 is more sensitive to this issue than Excel 2010.

Rg. Erwin

[JohnL]

Hi Erwin,

Have you looked at these articles already?

How to clean up an Excel 2013 workbook so that it uses less memory

https://support.microsoft.com/en-us/kb/3070372

Memory usage in the 32-bit edition of Excel 2013

https://support.microsoft.com/en-us/kb/3066990

Thanks,

[former_member230099]

Hi John,

Good point. We seem to be guilty of most of the formatting points that MS mentions. At the same time we use these formatting options because they are needed for the BPC schedule to work.

I've also created a SAP incident because this is a showstopper in our upgrade project. I'll be sure to mention your suggestions to SAP.

Rg. Erwin