We have been working for a couple of months with documents that VBA macro’s and VBA procedures, and everything works fine. Now we want to use the BCA …
I understood from a BO consultant it’s not possible to use VBA macro’s that pop the user for additional selection criteria in the BCA (these screens aren’t shown when scheduling the report), so we now have to change the logic of a couple of documents. No problem with that, but when we were testing the BCA we encountered problems with the use of VBA procedures. The processing always failed with the error message stating that the dataprovider containing the VBA procedure hasn’t been refreshed successfully “(109) The following data providers have not been successfully refreshed: (DMA0007)”.
The document refreshes online without any problem on the client and on the BCA server.
The add-in containing the VBA procedures has been registered for all users both on the clients and the server.
The SAPGUI has also been installed on the BCA server.
The documentation indicates this message is returned when “you select Cancel in the Enter or Select Values dialog
box and stop the data provider from being refreshed.”. I assume that BCA is performing the Cancel on your behalf!
Make sure your document doesn’t have any prompts or @variable functions in any of the data provider queries.
If they do, then you will have to set the values for the prompts using a VBA macro.
Create a macro that creates a document or application BOVariable with exactly the same name as your prompt or @variable function - right down to case and punctuation, then set the value of the variable to the value you need prompted.
Eg. if you have a prompt such as: “Invoices Date(s)”
You will need to submit the document with the VBA macro - but do not select the Refresh option when you submit the document, the script will do the refresh.
Make sure your document doesn’t have any prompts or @variable functions in
any of the data provider queries.
Tests with other documents - not containing any VBA macro’s or procedures - went well, and most of these documents had prompts/@variable functions. So I don’t thinks that’s the actual cause.