This content has been marked as final. Show 4 replies
Basically, i have to convert the datas behind an EssBase Planning Cube into a structure of datas that allows me to build a model in OBIEE. I cannot use the direct connection to the EssBase Cube for a problem of performance. I need to know if i need to work on the tables and how should i convert them in a structure thet OBIEE accepts, because the dimensional tables are based on a parent-child hierarchy and the users wants to navigate through hierarchies in a similar way they do this in EssBase.
So what i would know is: what is the structure of the datas that i should give to OBIEE? I have the fact table, with measures and a foreign key linked to every dimension, and the dimensional tables, which are like this: cod_parent column, cod_child column, other attributes of the dimension. Plus, these is no flag indicating that a member is a leaf, and root member has as a parent the name of the hierarchy itself.
Do i need to build new physical tables starting from these ones?
I've found what i needed, for everyone else:
The parent-child relationship table must include four columns, as follows:
•A column that identifies the member
•A column that identifies an ancestor of the member. Note: The ancestor may be the parent of the member, or a higher-level ancestor.
•A "distance" column that specifies the number of parent-child hierarchical levels from the member to the ancestor
•A "leaf" column that indicates if the member is a leaf member (1=Yes, 0=No)
The column names can be user defined. The data types of the columns must satisfy the following conditions:
•The member and ancestor identifier columns have the same data type as the associated columns in the logical table that contains the hierarchy members. Note that the example shown in Table 9-1 uses text strings for readability, but you normally use integer surrogate keys for member_key and ancestor_key, if they exist in the source dimension table.
•The "distance" and "leaf" columns are INTEGER columns.
Note the following about the rows in a parent-child relationship table:
•Each member must have a row pointing at itself, with distance zero.
•Each member must have a row pointing at each of its ancestors. For a root member, this is a termination row with null for the parent and distance values.