Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Warning 38100: Tables joined logically, not physically
Here is an example of a warning from my consistency check: Warning: [38100] The logical tables "Core"."Inventory" and "Core"."Dept Budgets" connected by logical join '"Relationship_2004:6243231247724664"' have no corresponding physical connections.
Analysis: There are 74 of these warnings in the consistency check. Most of them are as clear-cut as the example above. It is obvious that there would be no business reason to link departmental budgets with product inventory. If an author should build an analysis with columns from these two unrelated tables, that analysis would return an error, and rightly so.
As far as I can tell, nothing will be harmed by removing this logical join, because it doesn't make any sense to begin with, and OBIEE can't create an analysis containing columns from these two tables because they aren't connected in the physical layer.
But why does this logical join exist at all? This RPD originally was delivered with EBS. I am pretty sure that my client didn't go to the trouble of joining unrelated logical tables. Why would the EBS RPD contain logical joins between unrelated tables?
Answers
-
Mark.Thompson wrote:Analysis: There are 74 of these warnings in the consistency check. Most of them are as clear-cut as the example above. It is obvious that there would be no business reason to link departmental budgets with product inventory. If an author should build an analysis with columns from these two unrelated tables, that analysis would return an error, and rightly so.
Errr no? That's the whole point of cross-fact analytics using non-conformed dimensions.
Mark.Thompson wrote:But why does this logical join exist at all? This RPD originally was delivered with EBS. I am pretty sure that my client didn't go to the trouble of joining unrelated logical tables. Why would the EBS RPD contain logical joins between unrelated tables?
There's your answer. the pre-built stuff is many times of questionable quality/precision and random things are left over in there "because they don't actually hurt" just like in your case.
Mark.Thompson wrote:As far as I can tell, nothing will be harmed by removing this logical join, because it doesn't make any sense to begin with, and OBIEE can't create an analysis containing columns from these two tables because they aren't connected in the physical layer.
Well check the LTSs and the hierarchy. If there are measures tied to the grand total in non-conformed dimensions and / or grand total levels for LTSs set then you have your answer.
0 -
Thank you, Christian.
0 -
Any time
0