Writing a series of blog posts covering a complex functionality can be challenging, however it also leads to other posts (that’s why you saw the post about Hierarchy driven Smart lists and this one) 😉
I was researching and writing my follow up post on Groovy in PBCS and noticed some differences in Vision App on PBCS. I’m not sure when those changes made it into PBCS. There were lot of kick outs when I tried to load the data in PBCS from an on-prem Vision app.
Many accounts were removed, Start Year changed from FY09 to FY10.
As you know when metadata changes and you try to load a level 0 data file, it aborts the load when it hits and error and becomes bit frustrating without using a load rule, now this is PBCS data and there is no load rule!!!
What can we do? What can we do?
I did write about a change that was introduced in 16.09 here and if you read the comments Glenn Schwartzberg pointed out that you need to edit the .esm file. ESM file is the Essbase kernel file that manages pointers to data blocks and contains control information used for database recovery,so this file has the Essbase install root directory information and you’ll have to edit that file and update it to your on-premises Essbase install directory. Mine is C drive and here is how it looks like.
You need to repeat this for all the databases.
Once that is done, you can create the following Applications
Oh yeah, those are ASO plan types.
Once the applications are created, please stop the apps, so that you can copy the files from Essbase Data LCM folder.
Now that I got my PBCS Vision app as an on-premises Essbase application, I can use my old text file, create a load rule and load them all at once (and ignore the errors).
Now that’s done, how are we going to get this back to PBCS?
Get a level 0 export and import it back, yes this works now. Earlier PBCS versions really didn’t like Essbase level 0 format, however that changed (not sure which release that happened)
P.S you can also do this if you really want to get a level 0 extract of PBCS cube.
P.P.S Long live on-premises 🙂