Wow - this is a thread necro!December 22 2016 at 5:50 AM
No score for this post
from IP address 126.96.36.199
Response to Were you able to achieve this? How?
You'll be glad to know that it's fairly well documented (and been available since 9.3.1)
That being said, most of the 'new' school methods for writing back to relational from essbase are for a specific reason - and therefore use something like FDMEE writeback facility to write budget data back to an ERP for reporting purposes - whereas a lot of the newer tools in the oracle stack (OBIEE, DV etc) have direct connectivity back to essbase without needing to write back to a relational layer.
Anyways I'd be interested to see what your use case is to push back to SQL - there are probably other options you could look at.
With regard to your second question - if essbase can see the relational then it's simply the matter of writing a dataexport statement to write to it. No additional licensing required from the essbase side.
- Thanks and more queries - PM on Dec 27, 2016, 5:32 AM
- Essbase licenses - John A. Booth on Dec 28, 2016, 4:05 PM