Question:
Hi,
I know how to create InfoSet.
Can somebody please tell me that when should I go for creating InfoSet. What is a businnes implication.
Thanks in advance.
Answer:
Hi,
Infoset is necessary when you use transactionnal ODS, because they are not infoprovider, only datatarget. You put this kind of ODS into Infoset, usually not alone because associated with an ODS non transactionnal.
It is helpful for SEM, if you want to use ODS with SEM : transactionnal ODS !
It is also necessary to get the right value of master data attributes if they are time dependant. If you create a query directly on master data, you don't have an option of time determinition, instead of query properties itself. So, if you want to relate facts from a cube, to a value of attributes with time dependance, you have to put the master data into an infoset, then create a multiprovider wich will use infoset and cube. Infoset will bring you a valid time interval for the time union.
And, to conclude, Infoset allows you to create a left outer join, I mean to get an information from an infoprovider, even if that information does not exist in the second infoprovider inside the infoset. With multiprovider, it is not possible, it is an union.
Regards
_________________
Laurent THIBERT
Business Connection Amerique
Answer:
You generally want to create an InfoSet when you need to combine (join) InfoObjects to analyze master data, or to join InfoObjects to an ODS to perform lower level data anaylsis or reporting.
Ex: Join 0MATERIAL and 0MAT_PLANT by the material number in order to more fully query information about materials by plant.
Often times you can have attributes in one InfoObject which you would like to see in relation to attributes in another InfoObject.
InfoSets allow you to look at information differently then just transactional data in a InfoCube or ODS by iteslf.
Answer:
Other possible reason: you want to report on a single ODS but you don't want to set it available fro BEx reporting to avoid SID-creation.
(because this will slow down loading)