Logical Join

I would like to know how to create a logical join between fact table and dimension table which exist already in the Business Model and Mapping. I mean that I know how to show the Business Model Diagram of a fact table, but I don't know how to add a dimension table to this diagram to create a logical join. if someone can help me I will be really pleased for it.
Thank you in advance

Check this
http://www.oracle.com/technology/obe/obe_bi/bi_ee_1013/bi_admin/biadmin.html#t2s4
Cheers
Nawneet

Similar Messages

Adding a single table without a logical join to another table (OBIEE 10g)

Sometimes I want to just display a single table without a logical join to another table in the repository. However, everytime I move it to the Business Model and Mapping layer and perform a Global Consistency Check, it tells me that it needs a logical join and I am forced to create another table to join to it. Thus creating a dimension-fact relationship. There are times I don't need this relationship and just want to display some data. Is there anyway to get around this?
Thanks in advance!

Yes,You have to create a join.You cannot take single table to BMM layer.You can create an alias of the table.Join this alias and base table through any common column and take both tables to BMM and desired table to presentation layer.
Another way is to create a view in physcial layer.Write a select statement like
Select primary_key from Table
Where primary_key is primary key of base table.Join this view ith base table and repeat the steps defined for Alias.
Regards,
Sandeep

Multiple 'logical joins' between a fact table and one dimension table

It appears that one cannot create multiple ‘logical joins’ between a fact table and one dimension table in OBIEE using the Oracle BI Administration Tool. For example, considering a Business Model with a dimension table TIMES and a fact table FACT containing START_TIME and END_TIME, we would like to create separate logical joins from FACT to TIMES for the START_TIMEs and END_TIMEs? Obviously, the underlying foreign keys can be created, but as far as I can tell the Oracle BI Administration Tool doesn’t support this. The workaround would be to replicate the TIMES table, but that’s ugly.
I seek an alternative approach.

Try this. Create an two aliases for the TIMES dimension (Start & End) in the Physical Layer and then remove foreign key to the "Parent" Times dimension. Create the Foreign Key in the Physical Layer to the new aliases and then create the complex joins in the BMM Layer to the new aliases as well. This will allow you to present both dates within the same table in the Presentation Layer. Not the most elegant solution but it works.

Unable to create logical joins

Oracle BI version 10.1.3.3
After transferring the tables from the physical layer to the business modeling layer, I am trying to create logical joins among the tables in the logical layer using the Logical Diagram. At the logical join dialog box, I am unable to select the table columns on either side and the join operator is grayed out. The join is created, but with an empty expression.
I am, however, able to create foreign keys in this layer.
What could be the reason for this, and how do I create logical joins? The documentation recommends to create logical joins rather than foreign keys.
I have the same problem if I use the Join Manager.
Thanks.

Hi,
What you´re doing is creating "Complex joins" at logical level, that´s why the boxes are grey, you can't insert a join operator in this type of joins. It is recommended that you use complex joins at logical level that follow's the physical joins at physical level.
Regards.

Logical joins vs Physical joins

Hello,
Can anyone tell me what is the difference between physical joins and logical joins. And how OBI Server treats the joins in relation to the Logical and Physical Layer.
I'm a little confused also with the place to configure the joins, since there is more than one option.
Thanks in advance,
Sofiane

Well actually no. The actual sql fired would depend on both the logical and physical joins. Logical join would be the entry point. Think of it this way. Business Model layer helps you designing a star schema(like a data warehouse) out of your source data. So logical joins are joins that you define on your star schema. But the star schema in itself derives its data from physical layer. So the Physical layer joins would be necessary as well. But if you have a star schema already in your physical layer the physical joins alone would suffice and logical joins are redundant but necessary.
Thanks,
Venkat
http://oraclebizint.wordpress.com

Logical joins differ from Physical layer joins

Can please answer to my Question?
1.How does Logical joins differ from Physical layer joins?
2.What is NQSConfig.INI file and what does it contain?
Thanks
Chi
[email protected]

2) The NQSConfig.INI file contains configuration and tuning parameters for the Oracle BI Server. There are parameters to configure disk space for temporary storage, set sort memory buffer sizes, set cache memory buffers, set virtual table page sizes, and a number of other configuration settings that allow you to take full advantage of your hardware's capabilities.
For more information about the NQSConfig.INI file parameters, refer to Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
1) Logical joins are used in Business Model, Physical joins are used in physical layer. A key property of a logical join is cardinality. Cardinality expresses how rows in one table are related to rows in the table to which it is joined. Logical joins supports outer joins. so many else to mention... just go through RPD help file.
- Madan

Difference between physical join and logical join

Hi Gurus,
Can anyone tell me what is the difference between physical join and logical join
Thanks,
Chandra

Hi,
A physical join is at the physical layer and defines the join between two physical tables. Logical joins live at the BMM (logical) layer and define a join between two logical tables.
The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join, you just tell it that there is a relationship between these two logical entities. When the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
In BMM you use complex joins to establish which logical tables are joined which another, the OBI EE server will go to the physical level to search the physical join to make the query. You can also use physical joins in the BMM to override the join in the physical layer but only in very specific conditions.
If you also set complex join in the physical layer OBI EE won't be able to construct the physical query.
Hope this answers your question.
Award points if helpful.
Thanks,
-Amith.

Regarding logical joining of two table by using ODI interface

I have a two table in database.i have to logically add them, with the help of ODI interface.which should reflect in target.
there is a smple cinario regarding ,convertion of relational table to flat file.
but how to reflect mutiple table through joining in target from source.

Hi
Please correct my understan on your query
You want to say that, you have two tables at source side and want to store data to target table, later from target to flat file
or
You have two target table want to store data into flat file
Thanks
Phani

Logical And Physical Joins Of SH_PartTwo.rpd provided by oracle OBIEE

Hi,
I am new the OBIEE tool.After downloading SH_PartTwo.rpd .Planned to recreate the physical and logical joins.
If any one has already tried this, kindly explain why we are creating Alias tables of (SALES,TIMES)and joining COSTS to them instead of directly joining to Sales fact table. Below is the table structure.My question again,previously in SH.rpd we were joining Sales fact with other dimensions.If I need cost data then why should'nt I join cost with sales.
Thanks for your cooperation in advance.
Regards,
Sreekanth
Costs Sales Times Customers Countries Products Promotions Channels
Timeid Timeid Timeid
Productid Productid Productid
Promotionid Promotionid Promotionid
Channelid Channelid Channelid
Custid Custid
Countryid Countryid
Unitcost Amount_sold

Well don't know the example anymore ;)
But you normally will make aliasses to reuse the object.
So if you have a time dimension, and you have all kind of fields, like date_sold, date_bought, date_paid...
Now if you connect those dates directly to the time dimension, then you can get very odd reports... if you use aliasses, then the times have nothing to do with each other...
So it is always better to use aliasses... you never know if you need a table only once..

[38133] The Logical Table [...] is not joined to any other logical table.

Hi all!
I'm very new to Oracle BI EE. My need is to create my first report in BI. I've opened Oracle BI Administration Tool, created new repository, added physical tables, created new item named "reports" in "Business Model and Mapping" section, made "drug-n-drop" my physical tables into new item. Now when I run "check consistency" on "reports" item it returns errors:
Business Model reports:
[38133] The Logical Table '"reports"."table1"' is not joined to any other logical table.
[38133] The Logical Table '"reports"."table2"' is not joined to any other logical table.
[38133] The Logical Table '"reports"."table3"' is not joined to any other logical table.Could you please help me with these errors?
Oracle Business Intelligence 11.1.1.6.0

Looks like you drag-n-drop each table, try to all at once with that all physical layer joins are come and treated as logical joins. Other wise try to create them manually.
drag-n-drop always is not possible so we have to go for manually.
If this is not in your case let me know else pls mark as correct/helpful

Error [38133] : does not join to any other logical table

Hi,
Is there a way to avoid this error. We dont have the requirement to join the table with any other table. The client wants to use
the OBI Answers functionality on a single table. No joins needed or wanted. Some hidden checkbox to avoid the OBI join-requirement?
Thanks

Hi,
Refer the below link.
Adding a single table without a logical join to another table (OBIEE 10g)
or,
To report on a single table: just drag/drop the table twice from the physical layer to the busines model layer. Then define a complex join (just drag/drop a line) between tablex and tablex#1. Define a key on the dimension table (the white colored folder).
You can then put one of the tables in a presentation folder and report.
Hope this help's
Thanks,
Satya ranki reddy
http://satyaobieesolutions.blogspot.in/

Z report logic- Customer open item analysis

Dear Experts
Our client is using S_ALR_87012178 report for customer open items due analysis.
Now,here they also need sales group wise & division wise split up. Sales group from SO, not CMR, since a single/same customer may have different sales groups for different SOs.
I tried.. but no other report..satisfying this..
So, decided to go ahead with a new Z Development , wherein I plan to call in the program to our customized prgram/report & then to code it, so that sales group & divison are reflected to the corresponding customers.
Now, the challenge is, most (infact all) of the std credit management reports are customer master based, but this requirement (sales group & division) is transaction 9from SO) based.
Now, how do we write the logic/join the tables for me to write FSpec, so as to develop a Z Report.
Anticipating your guidance/suggestions/help.
Good day...
Rgds
Sumanth.Gururaj

hi,
this is to inform you that,
take the program with RFDOPR10 copy the same program under the name of Z report.
add these fields in selection screen and keep them mandatory on the selection screen & take logic from these tables and fields
1. Sales Group - VBAK-VKGRP
2. Division - VBAK-SPART
take the program with RFDOPR10 copy the same program under the name of Z report.
i think so you cannot capture the total functionality of RFDOPR10 which is the extract of plenty of tables.
finally if it is exectued then entire effort goes invain.
so my suggestion is catch hold of ABAPER and follow the above.
note : if sales group wise and division analysis is coming in the same report then it is very to populate the data from the Z report.
first confirm that.
if it is coming then go ahead with Z reprot itself
balajia

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

Fact table is joining with Other table having values for measures

I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
How should be the physical join between them and the logical join.
Earlier we had those VALUES in Fact1 only
Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
How we have to proceed now..!! Please help us!!?

I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
How should be the physical join between them and the logical join.
Earlier we had those VALUES in Fact1 only
Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
How we have to proceed now..!! Please help us!!?

Logical Join

Similar Messages

Maybe you are looking for