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.

Similar Messages

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

SAP:E:000:Table 'T100 ' does not contain an entry for ' 000'?

Gurus,
when user is updating size grid in matl master, the third party legacy system is reciving the bwlow error:
SAP:E:000:Table 'T100 ' does not contain an entry for ' 000'
could u all pls advise as why this error occured?
Thanks in advance..

t100 is the table that holds all messages in SAP.
The key to access this table is the message class and the message number.
Reading the message that you provided, it looks like SAP is searching for a message number 000 without having a message class.
Do you use any exit with own programming ?
You probably need to debug the program to find the root cause

ORA-12014: table 'DBA' does not contain a primary key constraint

Hai
when implementing basic replication i got the below error.
ORA-12014: table 'DBA' does not contain a primary key constraint
I was wondering primary key is enable at remote table
Any idea about this
Regards
mohan
I am giving below example
AT master site
global_names=false in init.ora file
sql>create table dba(no number primary key);
table created
and create snapshot log
sql>create snapshot log on m1;
materilized view created
AT SNAPSHOT SITE
1.Create service using net8 stiring name like n1
2.create database link
sql>create public database link m3 connect to system identified by manager using 'n1';
Database link created.
3.when creating snapshot site i got below error
SQL> create snapshot snap1 refresh fast start with sysdate next sysdate+1/(24*60
*60) as select * from dba@m3;
create snapshot snap1 refresh fast start with sysdate next sysdate+1/(24*60*60)
as select * from dba@m3
ERROR at line 1:
ORA-12014: table 'DBA' does not contain a primary key constraint

Hello,
Please repost this question in the appropriate section of the Discussion Forum.
This forum is for general suggestions and feedback about the OTN site.
You can also use our new offering called OTN Service Network:
For Oracle Advice/Minimal Support (fee based) on the Oracle Database Server, Oracle9i Application Server Containers for J2EE (OC4J), Oracle9i JDeveloper, Reports, Forums, SQL*Plus, and PL/SQL, please go to: http://www.oracle.com/go/?&Src=912386&Act=45
For customers with paid support (Metalink) please go to:
http://www.oracle.com/support/metalink
Regards,
OTN

Update function in logical data source does not get called.

I created a logicial datasource that contains two functions, one read and one update. The test runs and returns the expected values, however the update is not actually updating the database. Any reason this might occur? Thanks.

A common problem with this issue is that the datagraph that the client is sending does not indicate an update. Search for : testing update in ALDSP edocs, somewhere around the third search result there will be a document describing how to test updates - including how to capture datagraphs generated by the Test View. (search is broken at this moment, otherwise I'd give you the link ) Then you can make changes in the Test View, click on "Submit" and you will see the corresponding datagraph to make that change.
At the very least, the datagraph will need an 'old value' in the changeSummary. For instance, the datgraph to change a customers first name from John to Jonathan would look something like ...
<datagraph>
<changeSummary ... >
<FIRST_NAME>John</FIRST_NAME>
</changeSummary>
<CUSTOMER>
<LAST_NAME>Smith</LAST_NAME> 
<FIRST_NAME>Jonathan</FIRST_NAME> 
</CUSTOMER>
</datagraph>

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

Table parameter does not contain values in RFC call

Hello Experts,
I created RFC in R/3 with table parameter I_CUSTOMER. This RFC will be called by the CRM to pass all the customers data to R/3. The RFC was triggered by CRM passing 20 entries in I_CUSTOMER. However, when the debugger jumps in R/3 the table I_CUSTOMER in R/3 is empty. Can anyone help me to resolve the issue? any idea? thanks in advance!
Best Regards,
Alezandro

Hi Alezandro ..
what is the type of table parameter I_CUSTOMER u have declared??
if CRM is passing 20 values through I_CUSTOMER, u must take
type <b>TABLE TYPE</b> which is to be created in dictionary.
if it doesn't helps u ...can u be more clear??
Ram

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.

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

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

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

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

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

Repos - logical table source does not contain mapping

Similar Messages

Maybe you are looking for