URGENT!!! Incorrectly defined LTS

Gurus..please help
Physical Layer: I have the following tables
Dimensions: D1, D2, D3...D10
Facts: F1, F2
Both facts are joined to all the dimensions and also both facts are joined to each other as I would need to drill down.
BMM: same joins except a join between two facts as it would lead to circular join.
Presentation: Brought in all the tables.
Report level: I am using D1.C1 with F2.C1 and it throws me this error:
View Display Error
Odbc driver returned an error (SQLExecDirectW).
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 D2.C1) does not contain mapping for [F2.C1, D1.C1]. (HY000)*
SQL Issued: SELECT "F1"."C1" saw_0, "D1"."C1" saw_1 FROM "HOT Sales Queries" WHERE "F1".C1 = 'ABCDE' ORDER BY saw_0, saw_1
FYI: I tried to add the mappings in LTS but still didnt help.
Please help....its very urgent....have been struggling.

Hi,
Try to Create heirarchy for the dimension.
Then in LTS for both the fact tables, set the level to the lowest level of the dimension. (or other level as the case may be).
for more refer:
nQSError: 10058 Incorrectly defined logical table source
Thanks
Deva

Similar Messages

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 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.

Logical file name or logical path name incorrectly defined

Dear All,
We are doing archival in our IDES for test purpose before we do it to our Production.
Steps Performed
Copied AM_ASSET archive object to ZAM_ASSET
Logical Path
Logical path    ZAM_ASSET
Name            Asset
Syntax group    UNIX       Unix compatible
Physical path   /archive/test/<FILENAME>
Logical File Name
   Logical file    ZAMASSET
   Name            Asset
   Physical file   FI_<MONTH>_<DAY>.txt
   Data format     ASC
   Applicat.area   AM
   Logical path    ZAM_ASSET
But when we run the WRITE though SARA , in the job log we get the following
Logical file name or logical path name incorrectly defined
When generating a file name for an archive file that is to be created, the system determined that the logical file name FIAA_ARCHIVE_DATA_FILE or the logical path name ARCHIVE_GLOBAL_PATH was defined incorrectly.
But we have maintained a Logical name ZAMASSET , so we are unable to change the location of archived file and as well as the format.
So is there any setting we need to maintain apart from the logical file name and logical file path.
Suggestions are highly appreciated.
Thanks in anticipation

hi,
follow this steps :
- transaction SARA
- enter authorization objects, eg SD_VBAK
- hit button CUSTOMIZING
- Archiving Object-Specific Customizing: execute Technical Setting
- field Logical File Name enter or select ARCHIVE_DATA_FILE
- leave CONTENT REPOSITORY as blank if you are not using 3rd party for storing (eg. IBM Tivoli)
- back to customizing
- from Basis Customizing, execute : Cross-Client File Names/Paths
- on Logical FIle Path Definition, highlight (select) ARCHIVE_GLOBAL_PATH on the right pane
- double click on the Assignment of Physical Paths to Logical Path on the left pane
- double click on OS used, eg. UNIX, define Physical Path where archive file (on WRITE process) will be stored
- save changes made
- double click Logical File Definition, Cross Client on the left pane
- double click ARCHIVE_DATA_FILE on the right pane
- make sure that logical path is already set to ARCHIVE_GLOBAL_PATH
- save changes made
this setting also can be done using transaction FILE
we have experienced on this case using SAP standard archiving (SARA, SARI) and everything is fine with this setting above.
hope it help you.
rgds,
Alfonsus Guritno

[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

Code:10058. Incorrectly defined logical table source

Hi experts
I need to create Business model for which i have two fact tables in physical layer and both are connected to each other and one time dimension which is shared by both fact tables in physical layer and one dimension which is connected to fact2 that contain hierarchy. i want to create one fact table in BMM layer which should contain measures from both fact table......
How to achieve this, any help on this..
thanks & regards
Edited by: ObieeUser on 06-May-2010 02:58
Edited by: ObieeUser on 06-May-2010 03:00

hi
Go through this forum thread
OBIEE: Incorrectly defined logical table source doesn't contain mapping
try this steps
Goto Business Model and Mapping Layer. There Fact table is present expend that fact table. You will find Sources option expend that sources option. In that option you will find sone table name that is present in Physical layer.Get the property of first table and there you can see in General tab in downward ADD option is there. click on ADD option new window is open and there three part is . right down contains some table select table from that table which we are joining and then click on select option. Now that table will added. you can change join type also. By default it is inner join. now refresh you page.
i hope this will help you
thanks & regards

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

Hi all,
I have two facts(F1& F2) and two confirmed dimensions(D1,D2) for the facts F1 and F2.
F1
F2:LTS1,LTS2
D1
D2
When I query columns from D1,D2,F1,F2 LTS1 result is coming
But, when I query from D1,D2,F1,F2 LTS2 it is throwing incorrectly defined logical table sources.
Please help me in understanding this error

Here's what the OP wrote:
Hi all,
I have two facts(F1& F2) and two confirmed dimensions(D1,D2) for the facts F1 and F2.
Granted, people seem to insist on saying "confirmed" instead of "conformed" (ref. http://www.kimballgroup.com/data-warehouse-business-intelligence-resources/kimball-techniques/dimensional-modeling-techn…) but he's clearly asking for a perfectly normal and standard situation of two facts with two conformed dimensions.

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 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

OBIEE: Incorrectly defined logical table source doesn't contain mapping

In OBIEE 10.1.3.2 I have a very simple thing but cannot get it to work. Hopefully someone can point out the mistake. I have the same schema on two different database that I want to compare data.
The schema is simple. Table (dimension) A has two columns: id and name. Table (Fact) B has two columns: id and value. Table B.id is a foreign key to A. I imported two database schema into the physical layer and for each database, I built the foreign key relationship between table A and B. In the logical layer, I have two logic tables, one to represent A (Dimension) and the other B (Fact) with a logical join. Each logical table has two data sources. For the dimension tables, both id and name columns have two sources. For the fact table, the id has two sources and for the value, I created two separate columns, one called value1 and the other value2 with one from one database's B table's value column and the other from another database's B table's value. They then were made available at presentation layer.
Now in the Anwser, I can build a query with id from dimension and value1 from fact; it displayed fine. Same with a query with id from dimension and value2 from fact, it displayed fine. However, if the query is id, value1 and value2, I got the following 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 B) does not contain mapping for [B.value1 [ ] , B.value2 [ ] ]. (HY000)
Is there something I have to do additional to make both values appearing the same time.?
Thanks for your help
Ralph

Hi, Siddhartha P
I don't think I understand your information. I couldn't find connection pool at the business mapping layer. I only see it in the physical layer. Do you mean to do the mapping at the logical source table? That's only places I see any mappings and I don't see complex join there (only inner join, left outer, right outer and full outer) What mappings should I need to create between table B (fact table) of database 1 and table B (fact table) of database 2. I thought they don't have any relationship other than join through a dimension table which has columns that map to both table A (dimension table) of database 1 and 2. Then the logical fact table has 3 columns, one is id (to join to Dimension table) with two mappings (one to table B of database 1 and one to table B of database 2) and one column value1 which maps only to table B's value of database 1 and another column value2 maps to table B's value of database 2. That seems to be done correctly because I can pick column id and value1 or column id and value2 and have them displayed correctly but not all 3. I thought if it can display the two separately correctly, they should be able to display all 3. no?
I am not getting any inconsistency error.
There must be something I still don't understand. If you don't mind give me a little more direction, that would be great.
Thanks
Ralph

RE:[nQSError: 15018] Incorrectly defined logical table sourc

Hi Experts,
Actually we have a report by using X subject area and there are two users(Y,Z) accessing the report but for one user(Y) the report is looking fine for other user(Z) it is showing the below error
but for both users having same permission on the X subject area.
*[nQSError: 15018] Incorrectly defined logical table source (for fact table ABC) does not contain mapping for .ROW_ID)*
here in the report does not contain any column from the ABC fact table .
weather this is an security issues or any technical issue because one user is getting the report and other user is not getting the report.
Can any one guide me regarding the above issue...
Regards,

Since you have formatted the error message its not clear ROW_ID is from which table.
Here I'll give few hints to cross check.
1 There should be no key on fact tables in the Business Model.
2 Use Complex joins, not Foreign Key joins, in the Business Model.
3 All dimensions should have hierarchies defined
4 Content tab settings
Edited by: Srini VEERAVALLI on Mar 26, 2013 10:03 AM
It would be nice if you update your old post before you post new one, that helps you to get responses
Edited by: Srini VEERAVALLI on Apr 18, 2013 6:32 AM
Whats the solution or fix?
Edited by: Srini VEERAVALLI on Apr 18, 2013 6:55 AM

MB13,HDD WD BLUE it was incorrectly defined as by 7200 instead of 5400

MB13,HDD WD BLUE it was incorrectly defined as by 7200 instead of 5400

ahhh I see what you mean. the model you ordered is a 5400 rpm hdd but is showing as 7200 rpm..I misunderstood. I am as confused as you are

BMM - Decision criteria on how to define LTS for a multi-source object

I am curious to know what others use as their decision criteria when determining how to setup a BMM logical table that has multiple sources that map to multiple columns in the logical table.
For example,
If you have defined logical table Dim - Customer in the BMM that has 4 fields:
Dim - Customer
Customer Id
Customer Name
Customer Address
Customer Phone
The sources for this logical table from the physical layer are:
CUSTOMER (all customers exist here)
CUSTOMER_ADDRESS (A customer may or may not have an address, but can have only one address to simplify this conversation)
CUSTOMER_PHONE (A customer may or may not have a phone, but can have only one phone to simplify this conversation)
Field Mappings from Logical Table to Physical Table are:
Dim - Customer
Customer Id - CUSTOMER
Customer Name - CUSTOMER
Customer Address - CUSTOMER_ADDRESS
Customer Phone - CUSTOMER_PHONE
How would you setup the logical table and LTS's for this object in the BMM knowing the following requirements?:
1. The Address and Phone tables should only be joined in when fields from those tables are used in a report/query.
2. Since a customer may or may not have an address or phone, the BMM table needs to be setup such that adding those fields into a query will not filter all customers that dont have data for those fields, i.e. display null if it does not exist.
My initial approach for resolving this would be to set it up as follows:
A single Logical Table Source: LTS_CUSTOMER
Three Tables added to the LTS:
CUSTOMER, CUSTOMER_ADDRESS, CUSTOMER_PHONE
Two joins defined for the three tables:
CUSTOMER - CUSTOMER_ADDRESS (LEFT OUTER JOIN)
CUSTOMER - CUSTOMER_PHONE (LEFT OUTER JOIN)
Issues/Questions:
- The problem I have run into is that any query that uses Customer Id or Customer Name still causes a join to the CUSTOMER_ADDRESS and CUSTOMER_PHONE table even though I didn't use a field from those tables. I assume this is because OBIEE things that any query to that Logical Table using that LTS has to query it as the LTS is defined (so all three tables are joined in)
- Is there a way around this? If so, is it to specify separate LTS tables for the Logical Table Dim - Customer? If you do this, then there is no way to specify a LEFT OUTER JOIN and the query will just default to what is specified in the Physical Layer as an inner join.
- Curious as to what peoples thoughts are in general for how to decide whether to specifiy multiple sources in a single LTS or just add multiple sources to the Logical Table and the decision criteria for going either way.
Thanks in advance.
K
Edited by: user_K on Jun 3, 2010 11:09 AM
Edited by: user_K on Jun 3, 2010 11:10 AM

Thanks a lot for the example, that fixed the problem.
I've been reading the NSAPI programmers guide several times now and I was under the impression that you should either use <object> or <client>, never thought about this approach. Now when I re-read it is makes sense, but wasn't very clear at first.
I think I'll e-mail Sun to suggest an addition of the <Object> tag in their <Client> tag example (http://docs.sun.com/source/817-6252/npgobjcn.html#wp1045056) to make things a little more clear.
Thanks again, now I can finally implement the final configuration settings and plan for the actual switch later this evening.

URGENT!!! Incorrectly defined LTS

Similar Messages

Maybe you are looking for