One of the key features for the SAP BPC EPM Add-in for Excel has been the ability to write VBA to extend and customize the capabilities of the Add-in. The new EPM Plug-in for Analysis for Office (AO), which replaces the EPM Add-in, offers similar and in most cases compatible VBA support as the original EPM Add-in. However, there are some important distinctions between the two which this article covers.
The new EPM Plug-in for Analysis for Office (AO) requires a different method of declaring the specific API class used to access the library of VBA methods that SAP BPC supports. The latest version as of this writing, AO 2.4 SP1, made some but not all the old FPMXL Client methods compatible with the EPM Plug-in. To be safe, it’s recommended to start coding using the new standards for AO, as there’s no clear indication of whether all methods will be made compatible using the old object declaration standards.
To illustrate, here is a direct comparison of the differences between the two declaration methods.