Where clause in BMM (logical table Source) is not working

Hello Folks ,
I felt I ask here before I ask Siebel(oops Oracle!) support, by which I could save significant time NOT restart box multiple times , change log level , upload RPD , making multiple screen shots etc.. etc..
Here is an example the scenario
I have a custom field in the activity called the Activity source with two digit abbreviation
TX – Text message
LT – Letter
EM – Email so forth
The LOV table W_LOV_D has the type as CUST_SRC_ACT
Whoever implemented analytics they did an alias table for W_LOV_D and did a physical join between W_ACTICITY_F to W_LOV_D through field VAL
W_ACTICITY_F.X_ACT_SRC--> W_LOV_D.VAL and they did not do a where clause in BMM to retrieve only W_LOV_D.TYPE =’CUST_SRC_ACT’
So in fact the query pulls TX for CUST_SRC_ACT as well as TX for State abbreviation
I went ahead and added the where clause filter
"Siebel Data Warehouse".Catalog.dbo."Dim_W_LOV_D_Acty_Src".TYPE = 'CUST_SRC_ACT'
I saved the repository and started the server (I was doing offline) spooled the SQL and the results are the same. Looks like the filter is not being applied.
I did reload the server meta data etc..
Would anyone knows what is going on with the filter (or what I am doing wrong)?
Thanks in advance,
AP

hi Ap,
Pull only Dim_W_LOV_D_Acty_Src column into answers and check whether u r able to see CUST_SRC_ACT or not .Of course, you need to check sql query too
Thanks,
Saichand.v

Similar Messages

Repos - logical table source does not contain mapping

Hi,
I have a repository question?
I do not have a fact table in my physical layer. Do I have to have one? I thought the fact table got created in the BM.
I do have a date table in the physical layer, but it isn't joined to any other table.
I added the PK from the date_dimention to my logical fact table.
when I open the properities of my logical date table it is mapped to the physical date table.
Now in answers, I can query the date_dimension without error.
But, when I query the fact table using the date key, I get this error.
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table CRTK_FACTS) does not contain mapping for [CRTK_FACTS.MASTER_AI_ID, CRTK_FACTS.INT_DOC_ID, CRTK_FACTS.DATE_KEY]. (HY000)
SQL Issued: SELECT CRTK_FACTS.MASTER_AI_ID saw_0, CRTK_FACTS.INT_DOC_ID saw_1, CRTK_FACTS.DATE_KEY saw_2 FROM CRTK ORDER BY saw_0, saw_1, saw_2
Anyone have any suggestions on what I am missing?
thanks,
Kathy

I don't have a fact table in the physical layer. Do you mean join between the date table and other dimension tables?
or do I have to build the fact table in the physical layer?
I have not built any hierarchies yet, working on it.

Variable in where clause of the logical table

Hi,
is it possible to define a variable in "where" clause of rpd's physical table (table type - select)? If yes, pls elaborate the steps including how to refresh it with every end user's request?
Thanks and Regards,
Igor
P.S.
If not, is there any workaround?

Nico
thanks, but I am afraid that is not my case. I need to refresh variable value interactively with every query by a dashboard prompt. To illustrate my need just imagine a recursive SQL (defined as a view/logical table in rpd):
SELECT ....
FROM ...
WHERE ...
START WITH .... columnA=variable1
CONNECT BY PRIOR .... and columnB=varariable2;
or
SELECT c1,c2,c3,c4 from tabA where c1='A' and c2=variable1
union
SELECT c1,c2,c3,c4 from tabA where c1='A" and c2='D' and c1 NOT IN ( SELECT c1 FROM tabA where c1='A' and c2=variable1 );
So, what I want to do is to pass value(s) to my variable(s) every time when respective select (view) is executed. I see above selects are not typical ones the OBI EE is intended for but nevertheless I wonder if such kind of reports are possible to do in OBI EE.
Thanks and Regards,
Igor

Time series functions are not working for fragmented logical table sources?

If i remove that fragmented logical table sources, then its working fine.
if any body know the reason, please let me know.
thanks and regards,
krishna

Hi,
is because the time series function are not supported for the framentation content, see the content of the oracle support:
The error occurs due to the fact the fragmented data sources are used on some Time series measures. Time series measures (i.e. AGO) are not supported on fragmented data sources.
Confirmation is documented in the following guide - Creating and Administering the Business Model and Mapping Layer in an Oracle BI Repository > Process of Creating and Administering Dimensions
Ago or ToDate functionality is not supported on fragmented logical table sources. For more information, refer to “About Time Series Conversion Functions” on page 197.
Regards,
Gianluca

Where Clause in Logical Table Source

I have a dimension table joined to a fact table in BMM Layter. I would like to apply a filter in the where clause of the dimension table. Does the fact table also require the same exact filter to be applied in the where clause.

It would be nice if you add that filter on Fact's where clause part, that would be for entire fact level(start schema) instead of only on table level
You might need to map the dim to fact to do so.
mark if helps

Union of more than 2 fragments/Logical Table Sources in BMM Layer

Hi,
I have come across many blogs which explain how to union two fragments/physical tables in a logical table source.
Currently, i have a requirement where i have to combine/union 4 fragments/physical tables in a logical table source, say T1, T2, T3, T4 dimension tables.
All have the same table structure, but differ in data.
The requirement is to define dashboard prompt on the union of these tables and populate the values from all the tables.
I am able to union two of the tables using a '>' and a '<' condition on a key column.
But, am not able to union the other two tables.
If i try to put more than 2 LTS, then the union fails.
Please share your thoughts.
thanks,
Varun

Hi Varun,
What do you mean by the Union fails?
You can have a logical table source in your business layer with 4 different tables as a source.
Import the tables in the physical layer and create your joins.
Then create a logical table in the Business layer and go in the table properties you will see that you can add as much tables as you want into the source (Map to these tables).there you can add all of your 4 tables and specify what type of join you want to have between them (inner, outer...)
Regards
Adil

Logical table source in BMM

Hello,
I am using obiee 11g.
I have few doubts In RPD with respect to logical table Source.
Consider i have tableA,tableB,tableC in PL.
Now in my BMM i dragged tableA now i want one column from the tableB.
So which method is correct?
1>
Go to the logical table source properties of tableA->then there + sign click and then add tableB left outer join with tableA.
Here in the logical table source we see only one table tableA.
2> Drag the tableB column so that we have 2 logical table source.
Now what i am more interested is which method is selected on what basis?
Any help?
Thanks

Thanks a lot for the reply
Second case can u just elaborate more.
First case i think i understood.
My main confusion is ok ill explain my situation.
I have tableA,TableB,TableC all are connected.
Now i have one fact table.In that fact table i would like to create 10 measures.5 From tableA,3 from tableB and 2 from tableC.
So
First i created 5 measures from tableA.
Second i created 3 measures from tableB.
Third i created 2 measures from tableC.
Till now i have 3 logical table source sources in one LTS.
Now in my report when i combine columns from tableA and tableB , tableB column shows no data.
When i see in the sql i see tableB col is not taken itself.
Then i need to go to tableB,then go to General tab and then click + sign add tableA and then go to column mapping and map atleast one col of tableA here.
So on what basis here i should do mapping.
Since i have 3 logical table source sources in one LTS.Each time i click on sources->tableB->i could see even the
tableA columns but not mapped?
Is that every column from tableA should be mapped to tableB and tableB to tableC and tableC to tableA?I mean in the column mapping
This is something which i am feeling very difficult to understand?
Pls help me out?
Thanks

Multiple Logical Table Sources In BMM Under 1 Logical Table In OBIEE 11g

I have a question and even after doing a lot of search on google i could not find any article so through to ask you :-
I want to create a Logical Dimension table
This logical dimension has columns coming from 2 different physical tables, TableA and TableB. The relationship between TableA to TableB is 1 to zero.
There are 2 ways to create the logical dimension :-
1) Go to the logical table source properties of TableA-->then there + sign click and then add TableB right outer join with tableA.
Here in the logical table source we see only one table tableA.
2) Drag the tableB column so that we have 2 logical table source.
Please try this to explain without using the concept of fragmentation and without considering the fact tables. I have this question for simple logical dimension tables only.
I wanted to know which is the right way and what requirement/factor decides what to do ?

Check this post
Business Model - Logical Table Source
Let me know for Qs.
If helps mark as correct :)

Filter on the same logical table source on two logical tables is not working properly

Hi,
In the RPD, assume that I have a physical table named Employee_fact, created an Alias called D0 Employee Fact
In the BMM I've two logical tables called Employee_fact_Type1 and Employee_fact_Type2
Each of these logical tables has the same Logical table source - D0 Employee
But in each logical table source, I've a filter in where clause
such as, for Employee_fact_Type1 employee_type = 'XXX'
for Employee_fact_Type2 employee_type='YYY'
These two facts are present in the same BMM and each of them are connected to two dimensions
such as
Dept_type1 <- Employee_fact_type_1 -> Tenure_type1
Dept_type2 <- Employee_fact_type_2 -> Tenure_type2
In analysis, When I query the columns from Dept_type1 and Tenure_type1, the database query generated shows the condition employee_type='YYY' instead of employee_type='XXX' .
But, adding the columns from Dept_Type1, Employee_fact_type_1, Tenure_type1 it shows proper filter.
I checked the relationships, presentation layer for the sources of presentation tables and everything looks good.
Can anybody tell me what goes wrong here?

did you set the content level as well?

"create columns with a where clause" in BMM

Hi All,
I have a question about OBI EE Meta data layer.
We have OBIEE sitting on a Data Warehouse with a star schema.
Our Fact table holds the following fields...
EmployeeID
CompanyID
Measure ID
Measure Name
MEASURE
This is what we have in the physical layer, BMM layer and the presentation layer but I want to be able to "create columns with a where clause"
So my fact table in the presentation layer would look like this
Amount Sold
Unit Cost
Company Amount
I thought I could just create a logical column with
Amount Sold = Measure
where Measure Name = "Amount Sold"
But I can't seem to find any to do that.
Any ideas?
Thanks

Or you simply map your measure in the Logical Table source as something like :
CASE WHEN MEASURE_NAME = 'Amount Sold' THEN MEASURE ELSE 0 END.
You need to decide if you want the where clause adding in the Logical table source (be careful you will need a seperate LTS for each measure, this will mean more than one SQL being fired when you have more than one measure in the report).
Or you go with this case method on each measure, be able to have all the measures mapped in 1 LTS, include all those in the report and they will be retrieved by one SQL block.

Dynamically change the Priority Group of Logical Table Sources in OBIEE 11g

Hi All,
I have 2 Logical Table Sources(LTS 1 and LTS 2 for a Logical Table in BMM Layer).
Example: Logical Table : Sample
LTS Source 1 : Sample 1(Priority Group Set to 1)
LTS Source 2 : Sample 2(Priority Group Set to 0)
I have set the Priority Group of Sample 1 LTS Source to 1 and Priority Group of Sample 2 LTS Source to 0.
I need to dynamically change the Priority Group of Sample 1 LTS Source to 0 if my role is DEVELOPER where role is a column in database.
If my role is not equal to DEVELOPER then the Priority Group of Sample 1 LTS Source will remain same(1).
Please suggest how can i achieve this.
Thanks,
Soukath Ali

hello Soukath Ali,
didi you find a way to dinamically changing Priority Group?
thanks,
Maria Teresa Marchetti

Problem: 1 physical table -- multiple logical table sources

Hi,
I'm quite new to BIEE and setting up my repository.
So I have a question, if the following scenario is possible:
Physical Layer: TABLE_A: COL_A, COL_B, COL_C
TABLE_B: COL_D, COL_E, COL_F
Join TABLE_A.COL_A = TABLE_B.COL_D
In Business Model I have a Dimension Table with TABLE_A as datasource with fields DIM1 (COL_B).
The Fact Table (MEASURE) would have twice TABLE_B as data source with different where-clauses on COL_F and logical table columns (ATT1 and ATT2) of value COL_E.
So far I have created everything and the consistency check shows no errors or warnings, but I get an error in Answer: Incorrectly defined logical table source (for fact table MEASURE) does not contain mapping for [MEASURE.ATT1, MEASURE.ATT2], when I creating an report showing DIM1, ATT1, ATT2.
Isn't it possible to have one physical column used as multiple data source?
I know it 's working, when I create the physical table twice ... but maybe there's a solution for business model.
Thanks
chrissy

Hi mengesh,
that's what I also tried, but it's always returning me the same error.
I know it would work, when I import the physical table twice or more, but that's not what I want to do, because at the end I have 10 or more fields based on this one physical table. There's one field indicating what value is contained in the record, this means:
COL_F | COL_E
1 | customer name
2 | customer number
3 | customer branche
4 | salesman
5 | date
6 | report number
etc.
I don't think it's usefull to import the physical table as often as I need this field. So I want to divide it in business model.
thanks
chrissy

Invalid data from serveral fact logical table sources after upgrade to 11g

Hi,
We have a situation after upgrade from 10g to 11g. Answers' querys works fine in 10g environment, but in 11g, generated SQL is not correct.
Our example is something like that: we have orders fact table, customers and time dimensions. Customer have an hierarchy like: Customer Total -> Customer Country -> Customer Region -> Customer Detail (each level in one different physical table).
Order's logical table source has two table sources. One sets to Customer Country level, second one Customer Region level, both with different WHERE clauses in Content tab inside LTS configuration. Both at same level of Time dimension.
The issue is that, at dimension level, SQL is getting correct table to resolve Customer data (Customer Region level), but then, is getting the WHERE clause sets in LTS set to Customer Country level, so we are getting error data. Priority is the same to both LTS at fact table, sets to 0 (default).
How to know the way Oracle BI Server takes one LTS instead of another one? It's supposed to take the LTS defined at the same granularity level... but is not correct this case.
Thanks.

Can you try one of these options:
Try to set the priority group of lowest granular dimension to 1
or disable the LTS that is getting the where clause and check if it works fine and then enable again.

Question related to Logical table source

Hi All,
I have very basic questions -
(1) When do we create multiple logical table sources within a dimension?
(2) If a dimension has more than one logical table sources , when do we need to map the underlying table to other underlying table of logical table sources.
For exp consider these tables XLE_Entity_Profile, XLE_REgistration , AP_Invoice_ALL
AP_Invoice_All is a fact table. relationship between XLE_Entity_Profile & XLE_REgistration is (1:M).
Join info is as below -
(a) XLE_Entity_Profile.Legal_entity_id = AP_Invoice_ALL.Legal_entity_id
to get the registration of LE the where clause is as below-
(b) XLE_Entity_Profile..Legal_entity_id = XLE_REgistration.Source_id and XLE_REgistration.Source_table = 'XLE_Entity_Profile'
I have created the alias of XLE_REgistration as XLE_REgistration_LE.
With in a dimension , i have 2 logical table source - XLE_Entity_Profile & XLE_REgistration_LE.
logical table source 'XLE_REgistration_LE' has where clause 'XLE_REgistration.Source_table = 'XLE_Entity_Profile'
When i query , LE name , LE Registration Name, i get error like -
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14070] Cannot find logical table source coverage for logical columns: [LE_NAME]. Please check more detailed level keys are mapped correctly. (HY000)
Le Name is from XLE_Entity_Profile and LE Registration Name is from XLE_REgistration_LE.
But when using the properties of logical table source ' XLE_REgistration_LE' , i map it to 'XLE_Entity_Profile' ,i get the correct result.
I am not able to understand why am i getting error in first way of modeling.
Thanks , Ashish

Hi Ashish,
first about logical table sources (lts): you can create different lts for aggregation and/or fragmentation. Aggregation means that data is aggregated on another level among different physical tables. Fragmentation means that the content is different over different tables (other rows).
In your case, I think the problem is that your dimension is not denormalized, which results in a snowflake.
What I understand is that you have the following (physical diagram):
Invoice (fact table) >----- Entity (Dim) >----- Registration (Dim)
You have the following joins:
invoice.entity_id = entity.entity_id
and entity.entity_id = registration.source_id and registration.source = 'something'
First idea:
I would create the following join (in physical diagram):
Invoice (fact table) >---- Registration (Dim)
Where:
invoice.entity_id = registration.source_id and registration.source = 'something'.
Then in your Entity dimension you should create a hierarchy:
Grand Total Level
Entity
Registration.
In your dimension you should create the first lts: Entity
Set the aggregation content of this lts to Entity.
This lts contains only one physical table.
Map only the entity columns to the Entity physical table.
Then create the second lts:
Entity and Registration.
Set the aggregation content of this lts to Registration.
This lts must contain two physical tables, Entity and Registration.
Map the entity columns to the Entity physical table and the registration columns to the registration physical table.
Let me know if it works or not.
Regards,
Stijn

Logical table source

Hello!
Can someone please explain difference between dragging and dropping a physical column from a table in Physical Layer to a Logical Table in BMM layer and ragging and dropping a physical column from a table in Physical Layer to a Logical Table Source? When to use these two options?
Thanks,
-D

Hi,
First you have to read the OBIEE Administrator concept and will clear you doubt,
OBIEE Administrator, Windows based client tool to develop and manage Metadata repository. Repository changes can be done in either online or offline mode.
Online mode is when BI Server is actively reading the repository file (when a user is logged in).
Offline is when BI Server is idle. Best practice is to develop in Offline mode.
Minor changes can be made when in online mode. Administrator uses ODBC connectivity to connect to physical data sources, uses Native Drivers for Oracle and DB2.
OBIEE defines three layers of abstraction.
Physical Layer – connections to physical data sources (OLTP, OLAP, Flat Files, Oracle, SQL*Server, Teradata, etc.).
Business Model Layer – Brings together data elements from Physical sources into a logical Star-Schema representation. This is where business rules and definitions are setup.
Presentation Layer – An abstraction from the Business Model, defines exactly how users will see tables and fields.
Connection Pool is a connection to a Physical data source. Multiple connection pools can be created to the same source to improve end-user query performance.
All tables in the Physical layer must have a Primary Key column. Column properties can be edited to set the Primary Key. Physical joins need to be established between tables, using Foreign Keys and Primary Keys. Right-click on Connection pool to create the Physical diagram joins.
A Business Model can be created by drag and drop of objects from the Physical Layer. It’s a logical Star-Schema representation of the Physical objects. Tables from different sources can be merged to form one Logical table. These sources are called Logical Table Sources.
Logical Fact tables hold Metrics; every Metric must have an aggregation rule. Hierarchies can be setup on dimensions for drilldown functionality.
It is important to join logical Facts and Dimensions together, much like the Physical Diagram. Right-click on Model, click Business Model Diagram to create joins. Use Complex joins in the Business Model.
Presentation Layer is exactly what End-Users will see in BI Answers, contains multiple Subject Areas that answer specific Business questions.
Thanks,
Balaa...

Where clause in BMM (logical table Source) is not working

Similar Messages

Maybe you are looking for