Logical Dimension Fields

Hi,
I need to count the distinct number of a field value that is on a dimension table and not in the fact table.
My fact is something like this: amount_sold, year, id_shop, id_brand
with the 3 dimensions Time, Brand, Shop
The dimension SHOP contains this hierarchy: shop->area->country
The table the dimension table SHOP contains these fields: id_shop (contained in the fact table), ........., id_area, ........., id_country, .........
I need to count the dsitinct area that have sold.
What I did to count the dsitinct area's IDs is:
1) addedd the dinesion table SHOP to the fact source tables
2) logically mapped the ID_AREA of the new source table with a "count distinct" aggregation rule
It dosen't work.
Can someone help me ?
Many thanks,
Andrea

Why don't you perform COUNT operation within the logical dimension table itself !!!!
I think COUNT and COUNT DISTINCT are exempted from being in a logical fact table.Sorry but I don't understand how to do it.
I've created in the logical dimension table a new logical field which source field is the ID I'd like to count ...
I've set its aggregation rule to "count distinct".
I've drag&drop it to the presentation and use it ... I get an error (the table names are differente from the above ...)
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14020] None of the fact tables are compatible with the query request NUM_IMPIANTI:[DAggr(L_IMPIANTO_IP.NUM_IMPIANTI [ ] by [ L_DATA_INIZIO_LAVORO.Anno Inizio Lavoro [ ] , L_IMPIANTO_IP.Id Impianto Ip [ ] ] SB Impianto Detail)]. (HY000)
SQL Issued: SELECT "- Inizio Lavoro"."Anno Inizio Lavoro" saw_0, "- Misure".NUM_IMPIANTI saw_1 FROM "Intervento Pronto - Lavori" ORDER BY saw_0

Similar Messages

[39008] Logical dimension table ... has a source ... that does not join to

Oracle BI 11g
Hi,
I have this set of tables:
1) Table "Sales" with fields: ID, Billdate, ProductID, Amount
2) Table "Products" with fields: ID, ProductName, BrandID, TypeID
3) Table "Brands" with fields: ID, Name
4) Table "ProductTypes": ID, Name
In Physical layer I add these tables and create Physical Diagram with constraints like this:
[Brands] -------------------->[Products]
[ProductTypes] ---------->[Products]
[Products] -----------------> [Sales]
In Logical Layer I create logical table T1 Products with sources:
- LTS1 Brands,
- LTS2 ProductTypes,
- LTS3 Products
and fields:
- ProductID
- ProductName
- Brand
- ProductType
After that I create Dimention With Level-Based Hierarchy (H1 Products):
Total Products
- Brands
-- ProductTypes
--- Detail Products
When I try "Check Global Consistency" I get warning: "[39008] Logical dimension table T1 Products has a source LTS1 Brends that does not join to any fact source."
And after that when I try to make Analysis in Oracle BI, for example:
H1 Products | Amount
and then drill down item "Total Products" I receive error:
"State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail: [,Brand,,,,,,,,,]. (HY000)"
What's wrong? Where do I mistake? And why I don't get any messages about Logical Table Source LTS2 Product Type?

Hi,
you can create a single LTS for the product with the join for all 3 tables. Do you have a particular reason for the modelling that you have used?
Regards,
Gianluca

Logical Dimension tabel does not join to any fact source

I want to create a new “Dimension” table. This will be an Account Geographic dimension. My Business and Physical model are setup as follows:
1.     Account Address (WC_ADDR_F) is joined to Account (W_ORG_D) which is joined to multiple Fact tables (Ex: Order Item (W_ORDERITEM_F)
2.     When I perform “Global Consistency” check it comes back with no errors or warnings.
I create the Account Geographic dimension as follows:
1.     I right click on the subject area and select New Object->Dimension and name it “Account Geographic Dimension”. I do not select or change anything else.
2.     I right click on the new dimension and select New Object->Logical Level. I name the level “All” and check the “Grand total level” check box. Nothing else is changed.
3.     I right click on the “All” level and select New Object->Child Level. I name the level “Country”, set number of elements to 200.
4.     I right click on the “Country” level and select New Object->Child Level. I name the level “State”, set number of elements to 250.
5.     I drag the “Country” element from the Logical table (Account Address) to the “Country Level” on the new Dimension (Account Geographic Dimension)
6.     I drag the “State” element from the Logical table (Account Address) to the “State Level” on the new Dimension (Account Geographic Dimension)
7.     I then select the “Country” level properties and add a new key. For the key I select the “Country” column that I just dragged up there.
8.     I then select the “State” level properties and add a new key. For the key I select the “State” column that I just dragged up there.
My goal is that when an Analyst selects the “Country” column in Answers from the “Account Address” area that the user would be able to drill down from “Country” to “State”.
When I perform “Global Consistency” I now get the following warning:
WARNINGS:
BUSINESS MODEL CCCi Analytics:
[39008] Logical dimension table Account Address has a source CCCi_Dim_WC_ADDR_F_AccountAddress that does not join to any fact source.
Why do I now get an error no the Account Address table for not connecting to a Fact table? The error message references the “Account Address” dimension table which I believe is the source to the Account Geographic Dimension. If this is the source table, why did it not get a warning message before I created the new dimension?
Thanks…

Here is the solution that I was able to get to work:
1.     I did not have to reduce the business model to a star but was able to keep it a snowflake
Final design (which was same as the original) here is the Business Model (snowflake schema)
1.     Account Hierarchy (logical) -> Account (logical) -> Order Item Fact
2.     Account Address (logical) -> Account (logical) -> Order Item Fact
In this model the logical tables Account Hierarchy and Account Address snowflake off of the Account table which joins to the Fact table. I then:
1.     Created an “Account” dimension
2.     Created a child “Account Total” level
3.     Created two (2) children off of the “Account Total” level: (1) Account Address Country and (2) Account Hierarchy Top Level
a.     Key for “Account Address Country” was the Country column from Account Address (logical)
b.     Key for “Account Hierarchy Top Level” was the Top Level Account Name from Account Hierarchy (logical)
4.     Off of “Account Address Country”:
a.     Created a (1) child off of “Account Address Country” called “Account Address State” with the State field from the Account Address (logical) as the key
b.     Created a (1) child off of “Account Address State” called “Account Address Detail” with the ROW_WID from the Account Address (logical) as the key
c.     Created a (1) child off of “Account Address Detail” with the ROW_WID from the Account (logical) as the key
5.     Off o “Account Hierarchy Top Level”:
a.     Created a (1) child off of “Account Hierarchy Top Level” called “Account Hierarchy Level 1” with the Top Account ID from Account Hierarchy (logical) as the key
b.     Created (1) child off of “Account Hierarchy Level 1” called “Account Hierarchy Detail” with the ROW_WID from “Account Hierarchy” as the key
c.     Crated a (1) child off of “Account Hierarchy Detail” with the ROW_WID from the Account (logical) as the key
The global consistency check completed with no errors or warning with this design. It appears that perhaps you need to have all of the logical table keys in the dimension path that trace to the Fact table. One other note, cannot repeat use of other columns in the dimension except for the key of the first logical table.
Please let me know if I missed something.

Not able to find logical dimension tab in BMM layer in OBIEE 11G

Hi All,
Recently i ran in to a interested problem. We are using Oracle BI Administration Tool version 11.1.1.6.6, Repository Version:320.
I'm not able to see logical dimension tab to create dimensional hierarchy.
I followed normal method like all versions. Business model -> New Object -> (No logical dimension). I'm able to see logical display folder and logical Table.
I have only client tool on my machine. Please could anyone suggest me How should i resolve this problem.
Any help is appreciated.
Thanks,
Ashwini K.

Hi Srinu,
I joined all dimensions to facts, and i'm sure that i'm trying to create hierarchy for dimension tables. In oracle Administration Tool Repository version : 308, i'm able to see logical dimension tab at BMM-> New Object ->Logical dimension.
Any help

Append hyphen automatically after the wrapping of text in the dimension field

Post Author: Nita_here
CA Forum: WebIntelligence Reporting
I want to Append hyphen automatically after the wrapping of text in the dimension field.
e.g the text reads "I want to wrap this text". then if cell width exceeds after "I want to wrap" then it should be displayed like this "I want to wrap-" "this text".
Thanks in advance,
Nita

Post Author: Nita_here
CA Forum: WebIntelligence Reporting
Thanks for your input.
Let me tell you what I have understood. I will create a variable having the formula (which i have earlier written) in universe. Whenever i need to use the formula in infoview, I will call the variable instead. That's fine. But again, I will have the same problem. If I do any change in infoview level, the cell width is bound to change as it is not the free standing cell, its a column among othe one. e.g.
A B C
1 2 3
4 5 6
(you can think B as the column). Any change(addition, deletion of columns) will certainly change the cell width of B. So, again I need to calculate the things, which i dont want.
Nita_here: I manually calculated that after 12 characters, the cell wraps the text.
I wonder if there would be a way to do the things dynamically.
Thanks in advance,
Nita

Consistency Warning: [39008] Logical dimension table ... has a source ...

Hi and many thinks for reading,
I have a problem (which is quite common as I saw, though I could'nt find a solution which resolves my issue yet) with the consistency.
My physical layer looks like this:
Table_A
Table_B
Table_C
Table_D
Table_E
In the Business Model I have just the same tables and the following joins in the Logical Table Diagram:
Table_A -> Table_B
Table_C -> Table_A
Table_D -> Table_A
Table_E -> Table_A
The consistency check is delivering the following two warnings:
Warning
Logical Table Source
Table_A
[39008] Logical dimension table Table_A has a source Table_A that does not join to any fact source.
Warning
Logical Table Source
Table_B
[39008] Logical dimension table Table_B has a source Table_B that does not join to any fact source.
While working in BI answers I manage to retrieve all data from Tables C, D, E. But for tables A and B I can retrieve just the columns which are defined in the join Table_A->Table_B. All other columns deliver the following error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Table_A.Column_X. Please fix the metadata consistency warnings. (HY000)
If i retrieve one Column from Table_A and one from Table_E, I have the following error:
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 Table_E) does not contain mapping for [Table_B.Column_X]. (HY000)
(yes its Table_B not a)
I would like to fix this errors but am not sure where the problem is hidden.
Any help is kindly appreciated.
Evgeny

Hi Goran,
thanks for you help.
I tried to create the BMM in the two way but, it doesn't work out neither way. The Administration tool is recognizing the repository as consistent, thought it has some warnings, but in BI Answers I cant retrieve even a single column from one table.
I am also not sure, how does it work, that you just add TableB to the logical TableA, who would the programm know which rows belong together? I assume one must establish a logical connection between TableA and TableB to make it compatible?
About my tables:
Actually TableA, TableB and TableC are recognized dimensions (white) and TableD and TableE are recognized as facts (yellow) in the Administration tool. Though I dont agree with this assignment. TableA is definitly a fact table (it is also the center of the star schema) while the other tables are the dimension tables. Not sure how the Administration tool is distinguishing between facts and dimensions...
Here are my warnings:
BUSINESS MODEL TAB: (with two logical tables)
[39008] Logical dimension table TableA has a source TableA that does not join to any fact source.
[39008] Logical dimension table TableA has a source TableB that does not join to any fact source.
BUSINESS MODEL TACDE: (with three logical table sources)
[39008] Logical dimension table LT2 has a source TableE that does not join to any fact source.
[39008] Logical dimension table LT2 has a source TableD that does not join to any fact source.
[39008] Logical dimension table LT2 has a source TableC that does not join to any fact source.
And the errors in Answers:
Retrieving ColumnX from TableA in the first model
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: TableA.ColumnX. Please fix the metadata consistency warnings. (HY000)
Retrieving ColumnX from TableA in the second model
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 12170, message: ORA-12170: TNS:Connect timeout occurred at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
Thanks for further help!
Evgeny

Implementing Logical FACT & Logical dimension from 2 different data sources

Hi Gurus,
Here is my situation. We have 2 Different Data sources. One is SRMW and the other one is a different source. What we are trying to implement here is we wanted to create logical dimensions and logical facts as well in the BMM layer. For ex: w_day_d from SRMW and other time dimension from another source makes a logical table. And similarly a fact from SRMW and and another similar fact (Same data types though) will make a logical fact in the BMM.
I have done the POC of it, but the only problem is that i was able to fetch the data from only one data source not the other source.
Any suggestions ??
Thanks in Advance.

What I already mentioned is that you have to create multiple logical table sources and set the fragmentation content on each logical table source.
When you have two physical tables for the product dimension, for example DIM_PRODUCT_A and DIM_PRODUCT_B, you must add them to your logical table Products as two separate logical table sources and map all columns to the corresponding logical table columns on the Column Mapping tab.
Hereafter you should go to the Content tab of each logical table source and describe what content is in the logical table source.
For example for the logical table source of DIM_PRODUCT_A:
"BM"."Product"."Product Name" <= 'Product 2'
and for the logical table source of DIM_PRODUCT_B.
"BM"."Product"."Product Name" >= 'Product 3'
Then you must also check "This source should be combined with other sources at this level"
When you run a query in Answers only on the product table, two queries will be generated to get values from both tables.
Regards,
Stijn

[39008] Logical dimension table has a source that does not join to any fact

Dear reader,
After deleting a fact table from my physical layer and deleting it from my business model I'm getting an error: [39008] Logical dimension table TABLE X has a source TABLE X that does not join to any fact source. I do have an other fact table in the same physical model and in the same business model wich is joined to TABLE X both in the physical and business model.
I cannot figure out why I'm getting this error, even after deleting all joins and rebuilding the joins I'm getting this error. When I look into the "Joins Manager" these joins both in physical as well as logical model do exist, but with consistency check it warns me about [39008] blabla. When I ignore the warning and go to answers and try to show TABLE X (not fact, but dim) it gives me the following 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: 14026] Unable to navigate requested expression: TABLE X.column X Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT TABLE X.column X saw_0 FROM subject area ORDER BY saw_0
There is one *"special"* thing about this join. It is a complex join in the physical layer, because I need to do a between on dates and a smaller or equal than current date like this example dim.date between fact.date_begin and fact.date_end and dim.date <= current_date. In the business model I've got another complex join
Any help is kindly appreciated!

Hi,
Have you specified the Content level of the Fact table and mapped it with the dimension in question? Ideally this should be done by default since one of the main features of the Oracle BI is its ability to determine which source to use and specifying content level is one of the main ways to achieve this.
Another quick thing that you might try is creating a dimension (hierarchy) in case it is not already present. I had a similar issue few days back and the warning was miraculously gone by doing this.
Regards

Unable to create logical dimension in bmm layer

Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!

Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful

Logical dimension table

Hi All,
I am creating logical columns using two logical dimensions in a separate logical table. Do I need create complex joins for the new logical table, two source logical dimension tables have complex joins created already. Could you anyone provide some clarification on this.
Thanks in advance,
RK

As mma1709 mentioned,
you must be careful with the joins of this new logical table with your fact...
When you check for errors in the administrators,are there any??
if no,at any report with this column you have any problems??
hope i helped....
http://greekoraclebi.blogspot.com/
///////////////////////////////////////

Restrict Select-Options for Logical Database field

The way we restrict select options for custom defined select option fields on selection screen.. can we restrict select options for standard Logical Database fields?
i.e. report uses PNPCE logical database and has field called PERNR. I want to restrict select options for this PERNR field so that it has options for 'Select single values' only.
Thanks,
Falguni
Edited by: Falguni V on Nov 13, 2010 6:42 AM

You can user AT SELECTION-SCREEN event, and check whether any record is having high value for PNPPERNR.

Logical System field in BD10/BD14 need as a Mandatory Field

Hi All,
Good Day,
We have Logical System field in BD10 or BD14 etc.. TCodes and I would like to make this field as a Mandatory field. The reason for this is, while sending the Materials using BD10, and If I haven't enter any value for this field, IDOCs are getting generated and sending to all the logical systems say Dev, Quality and Production too. I want to avoid this.
So Is there anyway where we can make the filed "Logical System" as a mandatory field.
Thanks in Advance.
Param.

HI Param,
try BAPI_IDOC_INPUT1and check it in WE57 tcode.
hope this helps
regards
Aakash Banga

Creating logical dimension table using common attributes of Facts

I need to create a common logical dimension based on an attribute present in both the fact tables. Example -
Expense fact has 3 columns expense_key, expense_amount and customer_name
Revenue fact has 3 columns revenue_key, revenue_amount and customer_name
I need to create a prompt for customer_name and have a report including expense_amount and revenue_amount.
How can I create the logical dimension table in the Repository and join it to both the fact tables?
Any Suggestions?
Thanks.

Will there be an exact match between the customer names in both the tables? Also, we do not have a common key between both the tables(Customer Name cannot be used as the common key since it is not the primary key. If we make a join on customer Name we would get wrong duplicated data). If all you want is to pass down the filter of customer name and get the revenue and expense, create 2 fact tables(for expense and revenue) with their own dimensions and then pull them into a common subject area. Then use the set operations to create the following report
Customer Name Revenue Expense_Null (just populate 0)
Union All
Customer Name Revenue_Null(just populate 0) Expense
Then use the dashboard prompt on this report.
Thanks,
Venkat
http://oraclebizint.wordpress.com

[39008] Logical dimension table X has a source that does not join to any...

Hi Gurus,
I have warning:
"[39008] Logical dimension table X has a source that does not join to any fact source"
WHERE X:
PROMOTIONS,PRODUCTS, CUSTOMERS, CHANNELS
but all logical table are mapped to fact.
Eveb I can create reports for them
(The metadata was derived from OWB 11gR2, SALES_EE)
Thanks
Laszlo
Thanks for Your earlier answer as well!

Hi,
Did you create hierrarchy on that dimension.?
Add contel level in fact source to hierarrchy detail for the fact that joins the dimension.
Look at this for best practice...http://gerardnico.com/wiki/dat/obiee/hierarchy?s
Please do close your previous thread assigning points by clicking helpful or correct to the replies
Import XML file into rpd file
Thanks,
Srikanth

[39008] Logical dimension table has a source that does not join to any fac

Hi
I have a problem in BMM layer:
*[*39008] Logical dimension table X has a source Y that does not join to any fact source.*
To start with I have three tables joining to Cust (customer) table in physical layer
Cust-Seg (Segments)-------------------------------->>Cust via segment key
Cust-Geo (customer Geographics)-------------->>Cust via address key
in the BMM layer under the CUST table when I pull in Cust- seg it works fine .
But it gives an warning [39008] -if iI create a single LTS for the product with the join for all 3 tables
The Same warning appears when i import th Cust -seg table as Logical table

Have you tried this?
http://obiee11gqna.blogspot.com/2011/02/obiee-error-39008.html

Logical Dimension Fields

Similar Messages

Maybe you are looking for