jason w. jones

software from the trenches

Delete that stubborn Essbase application in EAS!

Sometimes you need to delete an Application but you can’t.  You still see it in Essbase Administration Services or even Application Manager (hey, there’s nothing wrong with still being on 6.5.x, if it ain’t broke…), but the app is broken or doesn’t exist.  The simplest cause of this is that someone [probably you] deleted the folder that contained the app, but you didn’t delete it through EAS.  And now, paradoxically enough, when you go in to EAS to delete the app, you can’t, because it can’t be started, because it doesn’t exist.  So essentially, the Essbase server tracks databases based not just on the existences of their folder, but also via some other means.

The easiest and most consistent method that I’ve come up with to kill the unruly app is this (assuming you have an extra Essbase server laying around):

Continue reading Delete that stubborn Essbase application in EAS! →

How to copy an Essbase application from one server to another

I got a question from a reader about how to do this.  Specifically, they were copying an application from one server to another and everything seemed to be going fine, except that there was no data in the resultant database on the target server.  The reason for this is that when you copy Essbase apps between servers, the data does not get copied.  If you copy the app on the server, it will copy the data.  So, how do we accomplish this?

For BSO cubes, the easiest option to do a cross server data copy is to copy the application by right-clicking on it, selecting Copy, then choosing the target server.  Then right-click on the database and select Export…. The export file will show up in your App folder were all of the Essbase applications are.  On your new (but empty) database that you just created from a copy, you can load this data.  If you have access to the File System locations, you can load the file across the servers, otherwise, you may have to copy/move the newly created export text file to a location that you can get to through the EAS Load file dialog box.  You don’t need any load rules since the data is already formatted in a way that is native to the application (just don’t make any changes to the outline before you import the data).

Continue reading How to copy an Essbase application from one server to another →

An Introduction Essbase Integration Services (EIS)

So, just what is this EIS thing?  You’ve heard about it, you know it has something to do with outlines, but you haven’t used it and you just don’t know where to start.  I understand.  I’ve been there.  I couldn’t really see an immediate payoff to using it, which kind of made getting all setup a little more daunting.  Please note that this article is written referring mostly to version 7 of EIS — I’m not sure what changes may have occurred since then.

Interestingly, my motivation for using EIS was a bit odd.  I was building some new cubes for the enterprise and they were in ASO for the first time.  The cubes were the evolution of a set of cubes that had been around in the company for a number of years, and the goal was to take what worked (and avoid what didn’t), and apply it for the entire organization.  Which is huge.  Hence the reason for ASO.  Along with learning all of the quirks that ASO brings to the table versus BSO, I also ran into another issue.  The original cubes, as part of their calculation method, would FIX on all of the accounts related to Gross Profit, flip the sign, and then roll up the whole cube.  The reason for this is that the GP accounts come in their “natural” accounting sign, so something like a sales account would be negative in the source database.  But since there are no calc scripts in ASO, I had to come up with another solution.  Well, it turns out that there’s this neat little feature on load rules that lets you flip the sign on a particular UDA.

Continue reading An Introduction Essbase Integration Services (EIS) →

Essbase, the economy and thoughts from the last ODTUG

I was going through some papers today and I happened to come across a sheet of my notes that I jotted down while I was at ODTUG in New Orleans last year (the best Hyperion conference around, seriously).  Coincidentally, earlier in the day I also had a conversation with a colleague of mine who works at a sizable company that does not significantly utilize BI/EPM.  She said they had looked at some options, including Essbase, but at the end of the day that just couldn’t justify the cost to get up and running — especially in “this economy” where everything else is being cut back, scaled down, or eliminated.

My question to her was this: how can you afford not to?  I noticed that many of the points I had taken away from various presenters and people I talked to at the conference wove in perfectly with this company’s predicament.  In the next paragraph I’ve italicized my original notes and added some context .  So, is investing in Essbase worth the money, especially in this economy where each dollar is even more critical than before?  Yes.

Continue reading Essbase, the economy and thoughts from the last ODTUG →

MaxL Essbase automation patterns: moving data from one cube to another

A very common task for Essbase automation is to move data from one cube to another.  There are a number of reasons you may want or need to do this.  One, you may have a cube that has detailed data and another cube with higher level data, and you want to move the sums or other calculations from one to the other.  You may accept budget inputs in one cube but need to push them over to another cube.  You may need to move data from a “current year” cube to a “prior year” cube (a data export or cube copy may be more appropriate, but that’s another topic).  In any case, there are many reasons.

For the purposes of our discussion, the Source cube is the cube with the data already in it, and the Target cube is the cube that is to be loaded with data from the source cube.  There is a simple automation strategy at the heart of all these tasks:

Continue reading MaxL Essbase automation patterns: moving data from one cube to another →

The new year, looking back and looking forward with a little Hyperion thrown in

2008 is finally at an end, and a lot happened. In the Hyperion sense of things, 2008 was busy in terms of new versions of software coming out, more name changes (I’ve almost given up trying to stay current with the terminology), and a very successful ODTUG in New Orleans.  The current latest version of things is 11.1.1.1.0.  Now, in my book, for all intents and purposes, System 9 was really version 8 of Essbase, and with no disrespect to the Oracle/Hyperion developers, I think from a development, stability, and feature standpoint, 11.1.1.1.0 is really like version 8.5 of things.  This lines up with the internal under-the-hood versioning scheme of Essbase as well, since internally it is referred to as 9.5 (and keeping in mind that version 8 was totally skipped).

Continue reading The new year, looking back and looking forward with a little Hyperion thrown in →

A quick and dirty substitution variable updater

There are a lot of different ways to update your substitution variables.  You can tweak them with EAS by hand, or use one of several different methods to automate it.  Here is one method that I have been using that seems to hit a relative sweet spot in terms of flexibility, reuse-ability, and effectiveness.

First of all, why substitution variables?  They come in handy because you can leave your Calc and Report scripts alone, and just change the substitution variable to the current day/week/month/year and fire off the job.  You can also use them in load rules.  You would do this if you only want to load in data for a particular year or period, or records that are newer than a certain date, or something similar.

Continue reading A quick and dirty substitution variable updater →

Getting everything done with just Essbase and Dodeca

Many people I talk to are amazed that a company can get by with just Essbase and Dodeca.  No Planning deployment, no HFM, none of that other stuff.  The core Essbase analytic engine brings a lot to the table, which is this: multi-dimensional analysis and all of the associated functionality for building, automating, and managing cubes (EAS, EDS, EIS, and such, in Essbase 7.x terminology).

So, out of the box with a typical Essbase setup, you can unlock the benefits of multi-dimensional analysis just by virtue of using using the Excel add-in.  We all know the Excel add-in has some issues (it’s not exactly aging gracefully), but it’s simple, fast, and many users absolutely love it.  The financial types tend to “get it” right away and go on their merry way.  They also seem pretty sad when they are “forced” to go to Business Objects for some data that isn’t in Essbase.

Continue reading Getting everything done with just Essbase and Dodeca →