BPC Macros not working after upgrading EPM addin to SP18

[Former Member]

Dear all

we have recently upgraded EPM addin from SP13 to SP18.

While performing regression tests  for the reports which use macors the reports are crashing

and closing automatically.

But the same reports when tested with SP13 addin, we were able to execute without any issues

please suggest if its bug in SP18 and anything needs to be fixed.

Attached screenshot of the error.

EPM Addin : 10.0 SP18 patch .Net 3.5

MS Office version: 2010

Visual Basic : Microsoft visual basic for applications 7.0

VBA retail: 7.0.1637

thanks

[former_member186338 · Accepted solution]

I have no issues with VBA on any EPM SP version...

You have to find the minimum lines of code that will generate the error!

Vadim

P.S. EPM SP18 is also extremely old! Better to upgrade to the latest! SP23...

[Former Member · Accepted solution]

hi Vadim

thanks for the reply.

When I access the same input template with EPM addin SP13, its working fine.

but when ran this input templates in Epmadding sp18, we are getting this error.

"Automation error : object invoked has disconnected its clients"

BPC version -> 10.0 with SP16

Epm adding -> SP18

we have also upgrade bpc sp from sp09 to SP16.

Does any of these upgrades causing issue.

please advise..

its preventing our golive

[former_member186338 · Accepted solution]

Theoretically some code may be affected by EPM SP! You have to investigate all VBA code and try to find the minimum piece of code generating the error! Show it!

Try SP23 - SP18 is already very old!

Vadim

[Former Member · Accepted solution]

hi Vadim

thanks for the reply.

Yes , but its client decision to upgrade sp18 and already deployed and testing in progress.

i was wondering the same piece of vba code working for sp13 but not for sp18.

i tried to check code, but its protected to edit..here is where I am stuck with.

[former_member186338 · Accepted solution]

"its protected to edit" - ???? What do you mean? Who created this code? How do you want to support it???

[Former Member · Accepted solution]

yeah, i thought i could run un-protection macro, even that is protected which is unknown as prior consultants created this has left organization.

[former_member186338 · Accepted solution]

Ups, macro protection is the reason for the issue you describe.

If you are unable to unprotect - then you will have to recreate template from zero! No other way!

Vadim

P.S. You are talking about this?

[Former Member · Accepted solution]

no macro protection may not be issue as i didnt face in sp13 version.

as you said earlier, there could be piece of code which is causing sp18 upgradation, so i wanted to check the vba code. But unfortunatelly no password for this vba code.

unable to come to conclusion whether this sp18 causing issue or something else.

as per your first mail, vba couldnt cause issue to sp18 and this password issue couldnt be the case as it worked for sp13..

raised high oss note as well, but not sure if they could help as its customised code SAP may not help.

so searching options

[former_member186338 · Accepted solution]

Incorrect! Macro code protection itself can be a reason for EPM SP incompatibility! And anyway you can't work with some protected code without password. The legal people may ask you interesting questions.... what exactly this code is doing... etc!

[Former Member · Accepted solution]

hi Vadim,

read some blog

one of the user also reported the protection sheet causing issues in SP18,but for the same i have searched here in scn.spa.com but it got removed.

any inputs?

SCN : All Content - SAP Planning and Consolidation, version for SAP NetWeaver

http://netweaver57.rssing.com/browser.php?indx=19493930&item=1964

[former_member186338 · Accepted solution]

We are talking about code protection, not sheet protection!

[Former Member · Accepted solution]

i think its vba project itself protected. no involvment of legal people here, the code max involves validation and on fly calcuation and posting in another sheet and some epmsave data formulas, epm retreive  data, multiple sheets in that workbooks. nothing more to legal people involve..

[former_member186338 · Accepted solution]

This message was moderated.

[Former Member · Accepted solution]

Dear Vadim

we have un protected vba and workbook as well.

Even after which we excel getting crashed.

I tried to comment all protection /unprotection code. still excel crashing out.

Any incompatibilties with office and EPM addin or VBA?

Please advise

[former_member186338 · Accepted solution]

Sorry but links are pointing to nothing...

[Former Member · Accepted solution]

hi Vadim

Our excel getting crashed after epm addin upgrade to sp18, we are getting crash with SP24 patch1 which is latest in market place.

the first piece of code that runs in macro is below. When i run these few lines alone the excel crashing

any help please.

Dim EPM As New FPMXLClient.EPMAddInAutomation

    Dim api As Object

    Set api = Application.COMAddIns("FPMXLClient.Connect").Object

    api.SetSheetOption "Blend_Actual", 301, False, "Test1"

    api.SetSheetOption "Blend_Actual", 300, False, "Test1"

    api.SetSheetOption "Blend_Plan", 300, False, "Test1"

the Unprotect alone when i ran, its causing crash.

Any help please ,

the API which invokes EPM ribbon, hence setting sheetoptions password.

when I try to run Dim EPM As New FPMXLClient.EPMAddInAutomation this alone, also excel crashed. please advise

[former_member186338 · Accepted solution]

Hi Vijay,

Test the following sequence on the new workbook:

1. In VBA editor create new module

2. Add reference to FPMXClient:

3. Add the code to the module:

Option Explicit

Dim epm As New FPMXLClient.EPMAddInAutomation

Public Sub Unprot()

    epm.SetSheetOption ThisWorkbook.Worksheets("Blend_Actual"), 300, False, "Test1"

    epm.SetSheetOption ThisWorkbook.Worksheets("Blend_Plan"), 300, False, "Test1"

End Sub

4. Protect using Sheet Options both worksheets: Blend_Actual and Blend_Plan with password Test1

5. Run Unpot macro and ensure that both sheets are not protected.

Vadim

P.S. You can't combine 300 and 301, because 301 is simply protect of all worksheets with the same password (not a real workbook protection).

[Former Member · Accepted solution]

hi Vadim

yes unprotection worked when i followed your steps.

But our template is getting crashed.

[former_member186338 · Accepted solution]

It simply means that you have incorrect VBA code in your template. Correct it based on my sample and it will work without issues.

Vadim

[Former Member]

Hi Vijay,

I am currently using VBA in SP18. I do not find any bugs or issues in that SP related to using VBA.

Hope it helps!