Ouch !! that hurt
When I tried creating a flat file extract of my Planning application's Account heirarchy, I sort of hit a roadblock. There is no LKM which pulls metadata information of Planning into a staging area.
Unless somebody gives me access to the Planning application's relational database tables and unless I have the courage to meddle with the tables, it seems difficult to get it right. I wanted to automate a process which pulled metadata from Planning application and then populate the same in ASO cube
But how do I proceed now ??
The only solution I could think of was using OutlineLoad utility's extract outline method to extract metadata. But wait, why do I need to use Planning metadata extract at all when I can use its corresponding Essbase cube's metadata?, plus there is a LKM for the same. So as far as practical uses are concerned, Planning LKM, though it would be great to have one, is not necessary.
And the bug :
For once, I was frustrated to find that IKM planning is not getting reflected in the interface I was creating.
Thanks to my colleague, he said the IKM is 'bugged'.
The procedure to correct it, he told me is, as follows:
1.Open the Knowledge Module in Edit mode
2. On the 'Source Technology', which says 'Generic SQL', change it to 'Undefined' (dont worry, it is fine)
3. Open the interface again, you will see what you want to see ;)
Just as I was typing this, I thought of searching it on John Goodwin's blog and I got it as expected
http://john-goodwin.blogspot.in/2012/08/odi-11116-planning-km-bug-fix.html
Looks like there is a opatch !!!
