Try to get the list of Fact (and dim) tables excluding common dims and set the refresh dates to NULL and start the load that would take care of EAM as full load and all other modules as Incr.
if helps mark
Thanks for the quick reply,
but was wondering how to figure out which one are common dimensions.
Any method by which i can get a list of Fact and Dim tables and as well common dimensions.
Also when we right click a execution plan in DAC 11g, there is an option of Reset Source(s).
Also we have an option of Add Refresh dates, when we right click an execution plan.
Any idea about its usability would be appreciated.
1 person found this helpful
You should know that since you are working with those modules. If you look at the fact in rpd you may get the related dim tables. Try to do as said. no worry about common dims
I can get a list of all the Facts and dimensions for a particular module from BI Apps Content guide... and then i can go and make refresh dates as Null for those Tables.
Now should i run the execution plan for one particular module or an Execution plan containing all the modules?
Cause i got this from someone..
"The Data models for the different modules have many common dimensions, so a reload of one module could leave the facts in another in an invalid state as the dimension keys would be moved.
Therefore it should not be expected that you can reload a module in isolation.
However, you can selectively do a reload of any table by resetting it's refresh date in the DAC console.
Then the DAC will determine the dependent objects that will also need a full load in order to maintain data consistency."
1 person found this helpful
Since you got all modules in 1 EP and all these are based on 1 container you can go as I said. Leaving common dims aside setting refresh dates to null works but you need to do a test it to make sure all is well.
Its all depends on how you are maintaining with containers..
Since you got SIL mappings those take care of Insert and Updates you never have any issues as someone said to you.
Just do it you come to know what is right
just in case if you are flexible with going for multiple containers let me know.
sveerava at gmail or cool-bi.com
hope this helps
Thanks for the info.. i ll try out what you suggested.
Meanwhile, do let me about the multiple containers route as well ( in case of multiple containers, can we use the same single OBIEE RPD for all the modules?)
In this case assume that each module is from each container and all set in 1 EP.
for any module refresh can do any time that might followed with common dims but dac will take care of it.
do not pull rpd into this, no relation at all at this context
let me know what you see after the load
Moreover, when you create the execution plan, just select the subject area which you want to run and generate it.
Finally build your execution plan and run it..
dint get this line of yours "for any module refresh can do any time that might followed with common dims but dac will take care of it."
Help me understand it.