If you have been working with 11.1.2 then you may have encountered an issue with the amount of time it takes to authenticate through workspace. You will more than likely have experienced the issue if you have a number of products installed but not active so maybe in a development/test environment.
If you do have products installed and not started then you will also see problems with menu items not displaying icons as they should.
I was planning to post this a lot sooner but I am finding it increasingly difficult to find any spare time lately, in the last blog I went through the final instalment of deleting essbase members and I thought that it would be worthwhile just finishing off with a post closely linked to the last blog but this time going through how to rename essbase members.
Today I am going to look at another method of deleting essbase members using ODI; in the previous blogs the methods used standard interfaces and required no customisation, they required an essbase load rule using the “Remove Unspecified” option.
In ODI 11g there are number of different methods to manage agents, one of these is through the use of Oracle Process Manager and Notification server (OPMN). Unfortunately with the current release of ODI 11g the components that make up OPMN have not been included in the installation, I am sure this will be rectified in future releases of ODI.
In the last blog I went over a simple method of deleting essbase members, today I want to expand on that method and provide a different solution to accomplish the same task.
There are situations where you may not have the full dimension hierarchy to hand so the last method does not work for you, it can be painful going through a full dimension looking for the members to remove.
Recently I have had a few emails and have seen a few posts about deleting essbase members using ODI, unlike the planning adaptor there is no operation setting to define how to delete members.
Much much later than planned I am going to go through the final method of managing planning hierarchies using ODI.
If you don’t use ODI within your company then I wouldn’t start to promote using it just for the sole purpose of loading planning unit hierarchies, one of the other methods I have been through would suite you more.
Today I am going to give a simple example scenario to hopefully make it more interesting and take you through the steps of achieving it.
In the last blog I went over loading a planning unit hierarchy directly through planning, today I am going to through the next method and that is the outline line utility.
The outline line utility appeared in the first release of version 11, even though a couple of versions late in my opinion it has turned out to be the most useful utility for classic planning, if you need to quickly load metadata and you can generate a fixed format file then it can save a lot of time, especially if you are prototyping.
In the last blog I went through the basics of planning unit hierarchies and creating a source file template to load, today I am going to go very quickly through one of the methods of loading and that is directly through Planning
This is the easiest method; create your planning unit template (look back at the previous blog if you have no idea on what to do) and make sure you save it with .exp extension.
Here is the same source file template I am going to use.
With the release of 11.1.2 comes an overhaul of the workflow process, there has been much criticism in the past of how rigid the process had to be and it was severely lacking in anything but basic functionality.
Oracle have taken onboard this outcry and started to invest development into enhancing workflow, now the aim of this post is not to explain the how workflow operates but to look at the different options for managing planning unit hierarchies.