Logical table source error

I am having a union report.
I have a strange problem. The report executes successfully normally but when I am ordering the columns as per the customer requirement its throwing an error "
A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact - tablename does not contain mapping for [case when Dim - Account. Number in (some values)]
none of the report is using any column from the fact table so I don't think that join should exist between fact-dim in this case.
Any other solution one can suggest?

Try to redo the same report with requested order. that would be the simplest way to handle it unless you have hidden hills in your development.
If helps mark
Thanks,
http://cool-bi.com

Similar Messages

NQSError 15018 Incorrectly defined logical table source error

Hi,
I am getting the following error when I am building one of my reports.
I have 3 dimensions - Time, customer and Product and two facts F1 and F2. Both F1 and F2 are joined to all three dimensions
The part I dont understand is that when I built a report with columns from all 3 dimensions and 2 facts it worked fine. But as soon as I added a new column from the customer dimension I am getting the below error. When I remove this specific column the report works fine.
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 F1) does not contain mapping for [Time.Mth_name, Time.Year]. (HY000)
Please help me figure out the issue.

Hello All,
I am also getting the same error.
I have one dim table d1 and 2 fact tables f1 and f2.
f1 contains 5 columns and f2 contains 2 columns. I created a logical table source between f1 and f2. Column mapping is done between f1.agency_no and f2.agency_no.
Columns in f1 : agency_no, agency_name,source, proj#, proj_phase
Columns in f2: agency_no, manager
Columns in d1: agency_no, agency_shortname, agency_name
Now, when i select f1.agency_no and f2.agency_no in the report. It is working fine, because the column mapping is defined between these 2 columns.
When i drag f2.manager into the report (report contains f1.agency_no, f2.agency_no, f2.manager) i am getting the following error.
[nQSError: 15018] Incorrectly defined logical table source (for fact table f2) does not contain mapping for [f1.agency_no]. (HY000)
Please help me out with this issue.
Thanks in advance.

Incorrectly defined logical table source error

Hey ,I am very new to obiee and getting an error
A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact - D) does not contain mapping for [case when Dim - Account. Account Number in ([ 11500, 11501, 11502, 11503, 11504] ) then 'ABC'
Can you tell me how to resolve this issue and what things should I look for

In that case you are not the one to handle the issue.
No point to respond to this post
Check this
ANNOUNCEMENT:Forums Etiquette/Reward Points
~ http://cool-bi.com

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

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

No Fact table Exists and [nQSError: 14070] Cannot find logical table source

Hi,
I have 3 tables A(fact),B(dim) and C(dim). there are some other dims. i am getting Errors here.
A is joined with B and B is joined with C .
1) In report if i pull columns from A and B its giving data. If i include C table Columns in the report i am getting Error like
No Fact table Exists.
2) If i pull the C table columns only in the Criteria i am getting error [nQSError: 14070] Cannot find logical table source
How can i resolve this.
Thanks

In Logical table B source properties general tab ->Click on Add button and add table C and pull required columns from Physical layer table C.
If helps mark for any issues let me know.
Edited by: Srini VEERAVALLI on Feb 13, 2013 6:42 AM

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

Handling Outer Join for hard coded values in the Logical Table Source

Has anyone tried to apply an outer join in the Logical Table Source Content Tab?
I have to add this APPLSYS.FND_LOOKUP_VALUES.LANGUAGE (+)= 'US' but the outer join is not allowed. I get this message.... [nQSError: 27002] Near <(>: Syntax error [nQSError: 26012] .
Could you tell me please how this should be handled? I have a lot of this cases in my project and without this being set-up affects the expected output of my report.
Thank you in advance.

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

[nQSError: 15018] Incorrectly defined logical table source

Hi,
I have two fact tables and a type dimension.
business model / physical
fact1 /fact1
fact2 /fact2
type /type
now I have them joined up on the physical layer with foreign keys AND on the business model layer.
Nevertheless I still get this error whenever I mix and match the columns.
[nQSError: 10058] A general error has occurred. (for fact table WABFact) does not contain mapping for [Dates.FLIGHTDATE [ ] ]. (HY000)

Hi,
The error "Incorrectly defined logical table source (for fact table XXX) does not contain mapping for YYY" means that the BI Server cannot reach from table XXX to table YYY. It can happen because of two reasons: The first one is that there are no relationships defined in the logical or the physical layers (or maybe both). Note that the connections can be indirect. The second one is that the relationships doesn't makes sense. For example, going from a fact table to a dimension table through many-to-many table cannot happen. You'll see this error many times as a beginner and it can be quite frustrating at first. You need to understand that the BI Server can only understand simple and classic star schemas. More complex ERDs need to be split by using alias tables.
Thanks to-Miki
Regards
MuRam

NQSError: 10058 Incorrectly defined logical table source

Hi All,
i am trying to join two facts using a dimension. If i run report having one column from dimension & one from fact it works. But when i run a report having 1 column from first fact & 2nd column from second fact i get the below error.
I am sure this has something to do with the content tab under sources in BMM later.
But can anyone me what exactly i need to do.
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 DWH_PA_MBR_PA_TMP_NEW) does not contain mapping for [DWH_PA_MBR_PA_TMPT_NEW.PERIOD_CODE]. (HY000)
SQL Issued: SELECT DWH_PA_MBR_PA_TMPT_NEW.PERIOD_CODE saw_0, DWH_PA_MBR_PA_TMP_NEW.CURRENCY_ID saw_1 FROM DWH ORDER BY saw_0, saw_1
Thanks,
Pankaj

yes i have the following
Facts
1) DWH_PA_MBR_PA_TMP_NEW
2) DWH_PA_MBR_PA_TMPT_NEW
Dim
1) PA_PERIODS_ALL
Join 1) PA_PERIODS_ALL.PERIOD_NAME = DWH_PA_MBR_PA_TMPT_NEW.PERIOD_NAME
Join 2) PA_PERIODS_ALL.PERIOD_NAME = DWH_PA_MBR_PA_TMP_NEW.PERIOD_NAME
When i run report with columns from Fact 1 & Fact 2 i get the error.
else if i run report with column from Fact 1 & Dim it works fine.
Note: here Period Name is the key.
I guess we need to define the LTS, colmn mappings.
Thanks,
Pankaj

Incorrectly defined logical table source (for fact table X

Hi!
Imagine the following Physical Diagram:
- Dim A
- Dim B
- Fact A
- Fact B
Joins:
- Dim A is parent of Dim B
- Fact B has a FK to Dim B
- Fact A has a FK to Dim A
Business Layer:
- Logical Table Dim A
- Logical Table Dim B
- Logical Table Fact A
- Logical Table Fact B
Joins:
- same joins (not FK Joins) that Physical Layer
When we build a report that only has one column of Dim A and one column of Dim B (A is parent of B), the following error appears:
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 "Fact A") does not contain mapping for [Dim A.col1, Dim B.col1]. (HY000)
What is wrong?
Help!
Thanks.

Hi,
The joins of dimensions go via a fact table. In your case there is no common fact table.
You can solve this by drag/drop a field from the physical table Dim B on the displayed logical table source of the logical table Dim A.
Now the BI Server knows that Dim A and B have a physical relationship.
Regards

Incorrectly defined logical table source in rpd

Hi
I'm very new to rpd building and started with the below model
F1 >----D1------<F2
Fact 1 is joined to Dim 1 and the same Dim 1 is joined to Fact 2. With this model in physical & BMM Layer I built rpd and deployed.
In answers I picked 1 column from each of these three tables and getting the below error.
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 FACT_SALES) does not contain mapping for [DIM_LOCATION.LOC_NAME]. (HY000)
Seems, I'm missing some basic rule in building rpd, any help will be great.

Hi,
Just check the mapping between the fact_sales and Dimension table.
the error explaining about the mapping error only.
Just check the datatype compability too.
Regards
VG

Incorrectly defined logical table source (for fact table Facts) does not

Hi,
I have two Dimensions A and B. A is joined to B by a foreign Key.
The report works if I pull B. Column1, A.Column2.
The report is throwing an error if i try to change the order of the columns like this. A.Column2, B. Column1.
error : Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
File: odbcstatementimpl.cpp, Line: 186
State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Facts) does not contain mapping for B.Column1
I am not sure where it is going wrong.
Thanks
jagadeesh
Edited by: Jagadeesh Kasu on Jun 16, 2009 4:22 PM

did you make joins in LTS or on the physical table.
try to make join in LTS if they are not there.

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.

Logical table source error

Similar Messages

Maybe you are looking for