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

Similar Messages

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.

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.

Tables icon displaying yellow in BMM layer.

Hi all,
When i was tring to drag drop tables from physical layer to BMM layer it's showing yellow icons.....
Scenario is as follows:
tables: EMP, DEPT, BONUS, SALGRADE.
I have created complex join in Physical layer between EMP and SALGRADE (condition is "EMP$".SAL BETWEEN "SALGRADE$".LOSAL AND "SALGRADE$".HISAL). Samething i have taken into BMM layer. 4 table icons showing yellow and checked for consistency..giving errors like there is no join of logical tables.
i have created join Physical layer will it not carry to BMM layer? Do i need to create same complex join in BMM layer? After creating the complex in BMM layer will those errors come again??
Please aswer to my questions..asap.
regards
ck

Chandra kanth wrote:
Gurus,
The other two tables (DEPT, BONUS) are not required to join but i just kept it like that in BMM layer.
1. I have created complex join between EMP and SALGRADE in physical layer and i also manually created complex join in BMM layer....it did not come when i drag drop the schema from physical to BMM layer. Do we require to create manually again the complex join in BMM layer?Yes.
>
2. After creating complex join in BMM layer EMP table icon shows white others are yellow. Will complex join not suffice to make error free (Consistent) in BMM layer?
Is it require to join all tables (to maintain a star schema)?
You need to create complex joins to create a star schema in BMM layer. This is needed to create an error free BMM layer.
3. As per the requirement i dont require to join other two tables (DEPT, BONUS).
What is the purpose of these tables?
>
Please advice if i am wrong in the above cases....and also please answer to all my questions.
Thanks in advance
chandra kanth.

Changing the LTS mapping in BMM layer to new Physical Alias table

Experts
I need to change the source table mapping in my BMM layer to new physical tables aliases.
I have finished BMM layer design (column name changes, business friendly names etc.) before actually creating the alias tables in the Physical layer and I know I hv to run for hiding now. I expected changing the logical source mapping to the new aliases will work but it's not the case though it works partially. Since the Column names are changed in the bmm, I have to manually change the Expression, Physical Table in the LTS column mapping tab for each non-matching name logical columns.
Column mapping is intact where both the BMM columns and the new Physical alias names match.
eg: CALENDER_YEAR(BMM) ---> CALENDAR_YEAR(Physical alias) mapping is intact but
Week Day(BMM) ---> WEEK_DAY(Physical alias) need to be changed manually.
Any tips/suggestions will be appreciated.
Regards,
Tom

Hi Tom,
I too do not see any other options here other than manually modifying the individual logical columns. When there is a new logical column, we have to map it manually to the physical column explicitly because the Admin tool will not know which physical column to pick up.
Hope this helps.
Thank you,
Dhar

Display of yellow colour icon to a table in BMM layer

Hello all,
Please ignore my previous thread. By mistake it went without any description of problem. Sorry for that.
I have two tables org details, emp details
org details having columns like orgname, year, quarter1 results, quarter 2,quarter 3, quarter 4
emp details having columns like org, year, emp in quarter1, quarter2,quarter 3, quarter 4.
Spread sheet as datasource and imported to physical layer....when i drag drop to BMM layer...emp details table icon showing yellow.
But it's not a fact table...those two are normal tables....why is it showing yellow colour icon?
please let me know the concept of how OBI administrator tool decides that the table is fact table or dimension table.
regards
chandra kanth.

By default OBIEE will show yellow colour.Once you create joins in BMM layer then it will show colours accordingly.Table on n side in 1:n join will be shown as yellow(Fact).So create joins in BMM layer.
Regards,
Sandeep

Case statement problem for a column in BMM layer

Hi friends.
In physical layer I've a "cardio" column whose data type is INT, and two values comes here either 0 or 1.
I need to replace 1 by 'YES' and 0 by "NO'.
For that I changed the datatype of "Cardio" column to CHAR. and in BMM layer I'm using this formula
CASE WHEN "A Analysis"."C Report"."CARDIO" = '1' THEN 'Yes' ELSE 'No' END
But this is giving me "Invalid Expression" error.
Please help me correct this error.
Help appreciated.

Hi,
Your are probably using the column Cardio as a 'source' and as a 'target'.
So you have to duplicate the cardio column (right mouse click and Duplicate option) in the business model and then apply the formula CASE WHEN "A Analysis"."C Report"."CARDIO" = '1' THEN 'Yes' ELSE 'No' END
That should work. It is not even necessary to change datatype of Cardio, OBI will handle this for you.
Regards
Edited by: wobiee1 on Nov 12, 2008 1:07 PM

Optimizing data grouping on BMM Layer

Hi.
I'm faced with the next task.
*(1)* Business goal
Display number of customers registered and activated by periods. The request in Answers should contain:
*{Period, NumberOfContacts_Registered, NumberOfContacts_Activated}*
*(2)* At Physical Layer I can provide data in two ways:
*2.1.* In single table like {customer_id, registration_date, activation_date..}
*2.2.* In two tables like {customer_id, registration_date..} and {customer_id, activation_date..}
*(3)* The question is about the most effective way of organizing data on BMM Layer.
I'm interested in whether I can organize single logical table to represent desired data in Answers. For example, logical table with columns {customer_id, registration_date, activation_date..} and then define complex join with logical table "Periods".
For now, I had an occasion to define two logical tables - with columns like in Paragraph 2.2. But it seems to be more effective way to do this.
Could anyone give me a piece of advise how to resolve this task more effectively (in preference, with single logical table).
Regards,
Alex.

hi Jeremy,
Use this '01-JAN-08' format in answers filter
Let me know if you have issues
OBIEE will replace with time stamp adds if its a timestamp/datetime data type
Thanks,
Saichand.v

Facts and dimension tables in BMM layer

HI Experts,
i have one doubts that is.... i have 7 Fact and 20 dimension tables in my current project ( this is mine first project ) how can i join these tables in BMM layer...
Regard's
Harish

Harish,
Just explicitly mentioning # of facts and dimensions won't fetch you any help. Extract a simple business scenario containing a fact and dimension tables.
e.g.
1. firstly, how many of the fact tables built are associated with different subject areas?
2. of the fact tables belonging to each subject areas, how many of them are aggregate tables?
3. if step 1 is not true, do they have conformed dimensions to access? <-- a caveat exists which your user MUST definitely know.
4. are there any partitions?
5. are they aggregate or summarized tables?
etc,....
based on which your modelling will start.
-bifacts :-)
http://www.obinotes.com

Circular Join in BMM Layer

Hi,
There are few dimension tables in my BMM Layer which is joined to every other table. I get circular joins error at this point. I tried duplicating the logical tables and avoided the circular schema. It always showed my an error.
Please guide me.
Thanks in Advance
Edited by: 914981 on Feb 16, 2012 5:43 AM

Hi,
Eliminate all circular joins (intra-dimensional circular joins) in a logical table source in the Physical Model by creating physical table aliases.
For example, say you have a Customer table that can be used to look up
ship-to addresses, and using a different join, to look up bill-to addresses.
Avoid the circular joins by aliasing the table in the Physical layer so that there is one instance for each purpose, with separate joins.
If its the same dimension table, make an alias on the dim for each different join you want to use and model them as seperate logical tables in the BMM.
Also refer thread for good understanding:
Re: Obiee - physical layer
Regards,
MuRam

Design of BMM layer

Hi,
Please explain in detail of design of BMM layer which includes the following
1. What are the things the we perform in BMM layer?
2. Hierachies and fact dimenstion table design?
i have gone thru the pdf but i am not clear...i want an explanation of above things clearly. Please help me.
regards
chandra kanth.

Chandra kanth wrote:
Hi,
Please explain in detail of design of BMM layer which includes the following
1. What are the things the we perform in BMM layer?
2. Hierachies and fact dimenstion table design?
i have gone thru the pdf but i am not clear...i want an explanation of above things clearly. Please help me.
regards
chandra kanth.Hi Chandra Kanth,
Please refer to the following links that provides you the entire details on building BMM Layer in a repository:
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10540/busmodlayer.htm#i1045226
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10540/dimensions.htm#BABHIDCC
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10540/lts.htm#CIHFGDIB
Thanks,
-Amith.

Diffence between physical layer and BMM layer

Hi all,
Please let me know the difference between Physical layer design and BMM layer design. Please write your views in your reply instead of links.
regards
chandra kanth.

chandra kanth.,
Use in the layers
The physical layer is the layer of the Logical Business Model where you define the physical data model of your data source. It contains information about the physical data sources.
The most common way to create the schema in the Physical layer is by importing metadata (table, view, …) from databases and other data sources. If you import metadata, many of the properties are configured automatically based on the information gathered during the import process. You can also define other attributes of the physical data source, such as join relationships, that might not exist in the data source metadata.
In the Business Model
In the business model, OBI recommends using complex logical joins instead of foreign key logical joins.
When Complex joins are used in the business layer then they are really acting as placeholders. They allow the OBI Server to decide on which are the best joins define in the Physical Layer to satisfy the request.
In a Dimension, you may have multiple Logical Table sources that all join to one fact table. The OBI Server will then decide the best joins to use to meet the requirements.

Sum Aggregation Error in Physical & BMM Layer in OBIEE 11g with Essbase 11

Hi everyone,
I'm using OBIEE 11g with Essbase 11 as the data source. I'm using Sample Basic database from the Essbase as my data source. If I'm using the hierarchy for the measures (so I don't flatten the measures), and when I changed the aggregation in both physical and BMM layer from Aggregate_External to Sum, I can't create a report at all from the Answers.
Does anyone encounter the same thing? Any ideas/solution about this? Please help.
Thanks a lot!

Hi Deepak,
When I picked the "Basic - measure" alone, I got this error.
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: 96002] Essbase Error: Unknown Member Basic - measure used in query (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Basic"."Basic - measure" s_1 FROM "Sample Basic".
When I picked the "Gen1,Measures" alone from the measure dimension, I got this error:
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: 46008] Internal error: File server\Query\Optimizer\ServiceInterfaceMgr\SIMDB\Src\SQOIMDXGeneratorGeneric.cpp, line 2610. (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Measures"."Gen1,Measures" s_1, SORTKEY("Sample Basic"."Measures"."Gen1,Measures") s_2 FROM "Sample Basic"
But when I queried the dimensions one by one (only single dimension each), no error was shown.
This only happens if I use Sum in the physical and BMM layer. If I use External_Aggregation, these errors do not happen. And if I flatten the measures, these errors also do not happen.

How to determine the logical Keys of logical fact table in BMM layer?

Hello guys
I'd like to know more about how to know what columns of the logical fact table should be used as key in BMM layer. How OBIEE behaving differently when different keys are selected?
In my situation, I have 1 fact table that physically joins to 20 dimensions in physical layer. Therefore, in physical layer, this fact table has about 20 foreign keys but no primary keys..
In the logical layer, this fact table is logically joined to the same group of dimension tables. So in this case, how do I know what columns in logical fact table I should use as keys?
Please advice
Thanks

thanks for the reply...
The interesting thing I notice is that, when I start using fragmentation with the fact tables in its LTS, if not primary key is defined in the logical fact table, then I will be getting errors:
[nQSError: 10058] A general error has occurred. [nQSError: 14023] None of the fact sources for columns are compatible with the detail filter []. (HY000)
When I create the key by choosing random columns from the fact table as the logical key columns, this error goes way and the correct SQL is generated according to the frag..
Because of such behavior, I'd really like to know how logical key really works in BMM layer.

Unable to create logical dimension in bmm layer

Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!

Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful

Regarding BMM Layer MultiLTS

Similar Messages

Maybe you are looking for