Hierarchies in BMM

Hi All,
I have a query reg hierarchies..
I have a Dim A which will be made in to two alias tables in physical layer as Dim Alias1 and Dim Alias2 , these both are connected to fact table separately...
I mean in STAR form..
When i pull these tables to BMM and try creating hiearchies...Both need same hierarchy as Country-State-City, but based on Fact keys they get the different values..
the issue is when I create same hierarchy for both the tables it gives me error "There is no uniquely identified "ABC" " ABC is the first level in the hierarchy..
But I would need hierarchy for both the tables in BMM..
Wat is the problem here?? If there is a problem is there any workaround??
Please share any info as pointers...
Thanks in advance..

I have a Dim A which will be made in to two alias tables in physical layer as Dim Alias1 and Dim Alias2 , these both are connected to fact table separately...Dim Alias1 and Dim Alias2 are joined within the same fact table? They have same table source (which is the original table source -> in the physical layer what is the source table for aliases?).
If you mean that Dim A is the physical table on the physical layer and you made two alliases for it (Dim Alias 1 and Dim Alias 2) then you make two logical dimension tables in the BMM, each has its own dimension object with Country-State-City hierarchy.
But if you mean that Dim A is the dimension table in the BMM and has two logical table sources (Dim Alias 1 and Dim Alias 2) then explain what kind of information you have in both logical table sources (Dim Alias 1 and Dim Alias 2) and how do they join to the fact table (they join the same fact table (original), fact table aliases, aggregates, etc).
Regards
Goran
http://108obiee.blogspot.com

Similar Messages

What is the use of logical key in logical tabls in bmm

hi
can any one tell me why we have to create logical key for logical table in bmm
Thanks
sreedhar

See the links below
why we have to create logical key at levels in Hierarchies
Re: Business Model - Logical Primary key
Regards,
Sandeep
Edited by: Sandeep Saini on 15-Sep-2010 05:17

Problem with BMM layer warning messages.

Hi,
I have modelled with the following tables in BMM layer.
Dimension tables: Regions,Countries,Departments, locations, Employees, jobs, job history
Fact table: HR Facts (measured columns like salary, max salary, min salary, commission)
The model is consistent with the following warnings:
Logical dimension table REGIONS has a source REGIONS that does not join to any fact source.
Logical dimension table DEPARTMENTS has a source DEPARTMENTS that does not join to any fact source.
Logical dimension table COUNTRIES has a source COUNTRIES that does not join to any fact source.
Logical dimension table LOCATIONS has a source LOCATIONS that does not join to any fact source.
and also in the answers section (Presentation services) i could not able to view data, it's giving the following error (when i am trying to display REGION NAME field values)
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: REGIONS.REGION_NAME. Please fix the metadata consistency warnings. (HY000).
I could not able to trace the problem where exactly is to be fixed.
regards
chandra kanth.

Hi,
Thanks for the information. Ideally that works out without any hierarchies. But the problem with which i was facing is somewhat different.
Let me explain the problem scenario exactly:
I have an employee, region tables in physical layer. Employee table has SALARY Column. Region table dont have any
join with Employee table. In BMM layer i have created a fact table "HR Facts" and crated a logical fact column SALARY.
The logical fact table source is Employee table. I have drag dropped Region table into BMM layer and joined with HR
Facts table. While consistency check its given a warining message: Logical dimension table REGIONS has a source
REGIONS that does not join to any fact source.
What is the problem exaclty?
regards
chandra kanth.

OBIEE 11.1.1.6 different layer hierarchies

Hi experts,
I want to know whether the following layout is implemented. How to create different layer hierarchy in BMM in OBIEE 11.1.1.6?
If it does work , I want to drag this hierarchy into presentation. Please help me as soon as possible. Thanks.
For example:
Presentation Hierarchy
Total
---Region
-----District
---------Brand
-------------Product Type
-----------------Product Detail

Hi SPowell42,
I am using OBIEE 11.1.1.6 to design and develop anything.
I have searched some related help information in RPD, and found 'modeling dimensions with multiple hierarchies in the presentation layer ' title which introduced some simple hierarchy information,such as
Country
--Region
-----City
-------Supplies
-------------Product
-------------------Product detail.
I am not sure whether it can do different layer hieiarchy in hieiarchy persenation. Maybe the sample column data stored in one table, however, it is my assumption.

BMM Logical Table - Create Multiple dimension

Hi All,
In BMM , I want to create more than one Dimension for a Logical Table. Is it possible to create multiple dimensional hierarchies on a single logical table. Can one share the thoughts or provide inputs. Thanks is Advance
S

If I understood your requirements, you are basically trying to do the "Role Playing" dimensions. Is that correct? Ifso, You can create alias for the associated physical table, and then use those aliases as logical tables and then create dimensions of this.
HTH
Mahesh

BMM issue for multiple fact tables

Hi All,
I have three facts F1,F2, F2 and two confirmed dimension D1,D2 in my sample rpd.
In BBM layer , I tried to do the modeling as follows instead of creating one logical fact table. There are many fact tables to come
in future.
F1<----D1--->F2<----D2--->F3
When I deploy this sample rpd and run the report from F1 andF2, I get an error No fact Table exists at requested level of detail.
I have not created any hierarchical dimension to set up the content in the fact table.
I am very much thanksful for any advices.
Thanks,
Vishal

Hi,
Please refer the below link.
http://satyaobieesolutions.blogspot.in/2012/07/implementing-multiple-fact-tables-in.html
My suggestion would be bring both the facts to the same logical table sources and have a single fact table in the BMM layer joined with multiple dimensions.
Build a dimension hierarchy for the dimensions and then in the content logical layer mapping, map the dimensions to the fact tables with detailed level/Total
Refer the below link-
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
Hope this help's
Thanks,
Satya
Edited by: Satya Ranki Reddy on Jul 26, 2012 7:34 AM

Why we have to create logical key at levels in Hierarchies

hi
i have one doubt that what is the use of logical key at levels in hierarchies directly we can create logical primary key and we can enable for drill down option
what is the use of creating logical key at levels (what i known is that is for unique column in the logical level)
i need small example for this
apart from that why we have to create logical key in logical tables in bmm layer so what is the need of it
Thanks
Sreedhar

hi Sreedhar,
I suggest you to go through
http://download.oracle.com/docs/cd/E12103_01/books/admintool/admintool_BusModSetup20.html#wp1005703
will clarify your doubts :-)
Thanks,
Saichand.v

Regarding BMM Layer MultiLTS

I have
D1 and F2 which is no join between them.
But I have D2 which is joined with F1 and F2.
so, I made an logical fact table and add F1 and F2, then join with both D1 and D2
Create the Hierarchies for both D1 and D2 and set the content as detail for both dimensions and both F1 and F2
And I set the fact column logica levels as Detaiil for the dimension which as confirmed (D2), as I am not able to see other dimension at fact column.
I created a report from D1 and fact column from f2 and getting the below error.
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail: [,,,,,RSM Service,,[FACT_CUST.CHEQU],,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,]. (HY000)
SQL Issued: SELECT 0 s_0, "Customer_Summary"."Dim_RSM_PRODUCT"."RSM_SERVICE" s_1, "Customer_Summary"."FACT_CUST"."CHEQU" s_2 FROM "Customer_Summary" FETCH FIRST 65001 ROWS ONLY
We have so many other facts as well in BMM layer. is it required to set detail level for all fact tables?
Could you please let me know the steps i created are correct or not. If not please suggest me how to do it. It seems problem with content level? It is urgent.
Regards,
Shaik.
Edited by: user5388961 on May 22, 2013 3:19 PM

Hi,
I have created the Logical fact table as mentioned and added 2 Facts to LTS and also brought some measures.
But I have non confirmed dimension PRODUCT with F2.
I didn't set any thing at dimension LTS content and I set content for F2 as Total for Product
For the fact table measures, set the levels with the non-conforming dimensions at the Grand Total logical level for each measure
I am getting consistency error, Fact Table functionally dependent upon Total level, but detailed child level has associated columns from that same table or a more detailed table.
If i remove the level at measure column in Fact table then no error but while running the report, i am still
getting nQSError: 14020] None of the fact tables are compatible with the query request ., if i include the column from Non confirmed dimension.
If i include measure and Non confirmed dimension then i am not getting error but the value of measure is 0. If i include one flag column which is at Fact table, then getting the above error.
I am not sure what to do. if any body wants the screenshot I would send it out.
Regards,
Shaik

Dimension Design - Single Dimension with Multiple Hierarchies

Morning,
the purpose of this discussion is to understand how we should design a specific dimension with 3 levels and multiple hierarchies for optimal performance.
We have an institution dimension with the following characteristics:
Characteristics
Dimension: Institution
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
Hierarchies:
1. Some of the hierarchies have 3 levels and others have only 2 levels (Skip Level)
2. ALL the hierarchies have a TB level and an Institution level
3. None of the hierarchies have the same leafs
4. Some of the hierarchies leafs can overlap
Design:
We are considering two approaches for the institution dimension levels:
a)
Levels:
Hierarchy 1 TB Level
Hierarchy 1 PG Level
Hierarchy 1 Inst Level
Hierarchy 2 TB Level
Hierarchy 2 Inst Level
Hierarchy 3 TB Level
Hierarchy 3 Inst Level
Note:
This approach is working and the resulting dimension and cubes are used by OBIEE, but some of the OBIEE analysis takes a long time (more than a minute) to return the results.
At this point, we are not sure whether this approach will result in an optimal design from a performance perspective and are looking at restructuring the dimension to represent only the three conceptual levels as indicated below.
b)
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
The rest of the dimension i.e. hierarchies, attributes and mappings are defined in the same way.
The cube associated with this dimension have approximately 80 million records.
Please advise on any best practices or design considerations that we need to take into account.
Thanks

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

Financial Analytics - segment and FSG hierarchies

Is it possible to define 6 segments and then additionally define FSG hierarchies in the same implementation of financial analytics ?
We have 6 segments defined in our Oracle EBS application so I have set the gl_account_segment_config to include those segments.
I have also modified the BMM to use the correct segment_lov_id for all 6 segments. This all works correctly no problems.
I am now setting up the FSG hierarchies required by the business.
I have modified file_gl_hierarchy_assignment_ora.csv to include 4 of my FSG hierarchies...
Unfortunately I do not see these coming into the database tables. I have the following set in the DAC -
Oracle - Extract FSG hierarchies -
Oracle - Extract Value Set Hierarchies - inactive.
Any help greatly appreciated....

See My Oracle Support note 1050724.1. Engineering have stated that using the two hierarchy methods is not supported.

Regarding BMM layer

HI All,
I am working on designing BMM layer. I have many facts and dimensions, few of the dimensions are confirmed.
1. could you please let me know how the BMM layer. Can i create Fact and related dim joins for each fact or can i create one logical fact table with all facts as LTS and join with all dimensions.
2. Do I really need to create Hierarchies for all Dims or necessary one.
Hope your reply soon.
Regards,
Shaik

create each LTS for each fact. If they are agg Facts they have to be in same logical table.( for optimised query path)
Physically join facts with required dimensions.
If there are facts which have some dimensions not conformed, better to have them as new logical Fact table.
It is a best practice to have dimension hierarchy. If you dont have detailed hierarchy just keep it total->detail -> key.
do also mentions number of elements in dimension that also optimizes the query path.

OBIEE hierarchies

Hi,
Can we create multiple hierarchies for a dimension in obiee rpd. Any links please.
Thanks

Hi,
It is a basic rule that you cannot create more than one hierarchy on a single dimension table, so what you do is create three alias tables and drag into BMM layer as 3 different dimensions and on top these tables create 3 different dimension hierarchies.
Please refer this link.....
Multiple Hierarchies from Single Dimension Table in OBIEE-11g?
Please mark if it correct/helpful.......
Thanks..

OBIEE Parent-Child Dimension with multiple hierarchies

Is it possible to have in a parent-child dimension multiple hierarchies? I want to have the same botom childs to aggregate to different parrents. example.
Account Dimension
HR1-total
HR1-parrent1
CHILD1
HR1-parrent2
CHILD2
HR2-total
HR2-parrent1
CHILD1
CHILD2
Thanks in advance.

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

Values not getting displayed in the selection screen for Hierarchies?

Hi All,
Our system was upgraded from BW 3.1 to 2004s. The quality system displayes values when query result is filtered for a hierarchy infoobject but the production system does not display any values and sometimes throws an error 'The operation failed because of a server error. See system logs.' There is no changes done for hierarchies in both the systems.
Please let me know if anyone has had similar problems.
Thanks,
Krishna

Hi All,
Our system was upgraded from BW 3.1 to 2004s. The quality system displayes values when query result is filtered for a hierarchy infoobject but the production system does not display any values and sometimes throws an error 'The operation failed because of a server error. See system logs.' There is no changes done for hierarchies in both the systems.
Please let me know if anyone has had similar problems.
Thanks,
Krishna

Report performance with Hierarchies

Hi
How to improve query performance with hierarchies. We have to do lot of navigation's in the query and the volume of data size very big.
Thanks
P G

HI,
chk this:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c
Query Performance Is "Aggregates" the way out for me?
/people/vikash.agrawal/blog/2006/04/17/query-performance-150-is-aggregates-the-way-out-for-me
° the OLAP cache is architected to store query result sets and to give all users access to those result sets.
If a user executes a query, the result set for that querys request can be stored in the OLAP cache; if that same query (or a derivative) is then executed by another user, the subsequent query request can be filled by accessing the result set already stored in the OLAP cache.
In this way, a query request filled from the OLAP cache is significantly faster than queries that receive their result set from database access
° The indexes that are created in the fact table for each dimension allow you to easily find and select the data
see http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6473e07211d2acb80000e829fbfe/content.htm
° when you load data into the InfoCube, each request has its own request ID, which is included in the fact table in the packet dimension.
This (besides giving the possibility to manage/delete single request) increases the volume of data, and reduces performance in reporting, as the system has to aggregate with the request ID every time you execute a query. Using compressing, you can eliminate these disadvantages, and bring data from different requests together into one single request (request ID 0).
This function is critical, as the compressed data can no longer be deleted from the InfoCube using its request IDs and, logically, you must be absolutely certain that the data loaded into the InfoCube is correct.
see http://help.sap.com/saphelp_nw04/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/content.htm
° by using partitioning you can split up the whole dataset for an InfoCube into several, smaller, physically independent and redundancy-free units. Thanks to this separation, performance is increased when reporting, or also when deleting data from the InfoCube.
see http://help.sap.com/saphelp_nw04/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
Hope it helps!
tHAK YOU,
dst

Hierarchies in BMM

Similar Messages

Maybe you are looking for