Mapping measures to fact tables crashes (in OLAP Catalog)

I've got some problem with an olap catalog I create.
Describing briefly my situation I may say that I have got a few measures (dimensioned with the same dimensions) but they load data from different fact tables. Using the CWM2 packages I try to create a cube in the olap catalog but when it comes to mappings of my second measure it crashes.
- first loop:
map_facttbl_levelkey(measure1, facttable1)
map_facttbl_measure(measure1, facttable1)
It passes OK
- second loop:
map_facttbl_levelkey(measure2, facttable2)
map_facttbl_measure(measure2, facttable2)
map_facttbl_measure throws the following exception:
ORA-01422: exact fetch returns more than requested number of rows
Do you know what is wrong? Do I do something that I shouldn't?

In case if I am not clear above, this is what we are expecting for QTD. Would the cube do this rollup? if so what should we do to achieve this?
Account
Account Type
Period
Total Amount
QTD
Child 1
EOP
201304
10
10
Child2
NO EOP
201304
100
100
Parent
201304
110
110
Parent
201305
220
320
Child 1
EOP
201305
20
20
Child2
NO EOP
201305
200
300
Parent
201306
330
630
Child 1
EOP
201306
30
30
Child2
NO EOP
201306
300
600

Similar Messages

Can a measure map to multiple fact tables

Hi Experts,
Can A Measure in an Universe map to multiple fact tables? For example, we have sales detail table by day and store and product, and have sales summary table by day and region and (product) department. We like to create a measure to map to both detail table and summary table. When I run query includes store and product, the query will automatically use the sales detail table; and query can automatically choose the summary table when it only includes region and department. Our database table could be in Teradata and Oracle. Can we achieve it and how? If a measure can't achieve this (dimension awareness), what the other option we can have and how to do it?
Thank you,
Richard

Hi Sion,
After I make the tables incompatible with the dimension objects on different levels, the measure can point to the right table if my query only include Store and Product or only include Region and Department. But in some scenario, the business could ask to include both Store and Region or Item and Department in same query. The current approach doesn't work on this further request. In our database, we have store table including Region with other higher level organization information, Product table including Department with other higher level product information, and we also have separated Region table and Department table. Could we make the objects more flexible u2013 query will be against aggregation sales table if dimension objects in query are only on higher level and will against detail sales table if some of dimension objects are on high level and some on low level?
Many thanks,
Richard

Non-numeric Measures in fact table

I have been told measures should be numeric items from the fact table i base my cube on. Yet some of these columns are non-numeric. Reports are asking me to tally up the totals for these boolean measures in my reports. Has anyone done this before? If I have a measure that is a 'Y' or a 'N', how do I total up the numbers for each in Analytic Workspace Manager?

I am attempting to understand. In AWM, I will have a
dimension. The hierarchy of this dimension will have
2 levels...'Total' and 'YesorNo'
Then I will map the column to that 2nd level?
I don't quite understand. What about the measures?
I have no measures currently. And these columns are
e in the fact table...I can't map a text field to a
level...plus there are also nulls in there in the
form of other letters (ie '0').
Any more clarification would help significantly.
Thanks!you must edit your cube, and add it with measure u want.
then simply map the "YesorNo" column to Aggregate table (use proper operation such as SUM, COUNT, DISTINCT etc in Agg properties), and define the output as number. later u can map this agg.output to your cube table.
hope it can help.

How to create summation column with different measures of fact table

If I have a salary fact table with columns MONTHID | BASIC-SALARY | TRAVEL-ALLOWANCE
and in Deski, I drag all the three columns to form a horizontal table
then is it possible to create a summation column to show total salary?
I don;t want to create a variable because in that case the formula need to be changed everytime there is a new allowance.
regards,
binayak

Hello Binayak,
as you refer to Deski I recommend to post this query to the [BusinessObjects Desktop Intelligence|SAP BusinessObjects Desktop Intelligence; forum.
This forum is dedicated to topics related to the creation and design of Desktop Intelligence documents such as universe connectivity, prompts, charting, formatting, filter, and formulas.It is monitored by qualified technicians and you will get a faster response there.
Also, all Desktop Intelligence queries remain in one place and thus can be easily searched in one place.
Best regards,
Falk

How map to my particular table to the fact table in obiee 11g...

Hi friends,
I did this simple report in obiee 11g(i.e)
"NATIONALITY COUNT IN DEPARTMENT WISE"
For that i used the following tables:
per_all_assignments_f----->fact table
hr_all_organization_units----->dim table(containing departments)
per_all_people_f---------------->dim table(containing nationality)
I made all the mappings in the physical diagram, as also viewed my report in BI answers
It shows the following results like
NATIONALITY---------------------------------------------------------------------COUNT(NATIONALITY)
AUS------------------------------------------------------------------------------------------------24
AFR------------------------------------------------------------------------------------------------25
PHQ_VB-------------------------------------------------------------------------------------------40
SH_VT----------------------------------------------------------------------------------------------4
The problem is for me it is showing the above results, but the nationality column is of various codes of the country.
Since i doesnt want the code of the nationalitian to display in the results..i need the meaning of each and every nationality..
like,
AUS------------------------Australian
AFR-------------------------African
PHQ_VB----------------------Germanian(assigned)
Since i know that the meaning for the nationalitian is available in "FND_LOOKUP_VALUES"...okay..
I can import "FND_LOOKUP_VALUES" table to the physical layer...but how i can able to give the mapping to the fact table in my physical diagram...
In my report the fact table is "per_all_assignments_f"
As my fact table doesnt contains any matching column corresponding to the dimension table "FND_LOOKUP_VALUES".....
Then how i can give mappings to the fact column???? for viewing the full meaning of the nationalitian in my report.....Help me friends...
Regards,
Harry...

Hi bifact,
I followed the step that U asked me to go but im stuck with later.....
*) I saved the query that i executed in toad with the columns showing country codes and country meaning to the excel sheet...
This is the query that i executed in toad and copied data s in excel sheet..
select z.lookup_code, z.meaning
from per_all_people_f e, per_all_assignments_f f, hr_all_organization_units h, fnd_lookup_values z where
e.person_id = f.person_id and f.organization_id = h.organization_id and e.business_group_id = f.business_group_id
and f.business_group_id = h.business_group_id and f.location_id = h.location_id
AND z.lookup_type(+) = 'NATIONALITY'AND z.lookup_code(+) = e.nationality and sysdate between
e.effective_start_date and e.effective_end_date and e.nationality is not null
*) After that i created a system DSN for the excel drive..
*) After that when i tried to import metadata of the excel data that is saved, it showed me connection failed...
For importing this excel data
what connection details i need to give:--------------------
as well as user name and also password...
Soon after importing this excel you said that to give key connection only to fnd_lookup_tables(dim) and that excel data..
if so, again im not giving key connection to my fact table..
I think again the same error will occur that no logical mapping is not made to fact so again repository is inconsistent...
Hi bifact sorry to ask you, but can you see the steps that i followed is correct and after that wat more steps i need to proceed..Can you tell me in breif manner...Thanks for your help...
Regards,
Harry...

Dimension which belongs to only one of the several fact tables

Hi,
I'm newbie in BI. I have good knowledge of DW and Administration (OCP).
Firstly could you give me, please some link expalining aspects of creating "Business Model And Mapping" better than SE Tutoarial.
Now how my problems looks like :
I have several fact tables and dimensions.
But not all dimensions are shared among all facts.
So when i try to put in Answers measurements from all facts it's ok - results are retrieved.
But when i try to add to report some Dimensions attributes which belongs to only one of the facts all facts measurements are gone except measurements for fact table to which dimension attribute is linked to.
I think i know what is the reason but i don't know how to simply solve it :
Below is session trace excerpt only with facts measurements :
RqList
Liczba Transakcji:[DAggr(Fakty - Transakcje (ZSFK).Liczba Transakcji by [ Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c7 GB,
Kwota Opłaty Netto:[DAggr(Fakty - Opłaty za Terminale (CBD).Kwota Opłaty Netto by [ Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c11 GB,
Below iis session trace excerpt with facts measurements and added dimension attribute:
RqList
Liczba Transakcji:[DAggr(Fakty - Transakcje (ZSFK).Liczba Transakcji by [ Słownik - Rodzaje Walut.KOD_WALUTY, Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c7 GB,
Kwota Opłaty Netto:[DAggr(Fakty - Opłaty za Terminale (CBD).Kwota Opłaty Netto by [ Słownik - Rodzaje Walut.KOD_WALUTY, Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c12 GB,
Second plan is the plan when report retrieves only results for one fact table and null's for others
Problem is with attribute : "Słownik - Rodzaje Walut.KOD_WALUTY" which is from dimension which belongs only to one fact table.
So other fact table are not linked to this dimension and therefore this plan cannot retrieve results for them.
It is obvious that some of the facts cannot share some dimensions with others but i would like to join them on other common attribute
and my question is how ?
Thanks's in advance Arkadiusz Masny
Edited by: Arkadiusz Masny on Dec 10, 2009 6:49 AM

It's normal behavior. How would fact measure know the value for accurate "non-fact" dimension
Workaround:
First solution is:
Add into logical source of each fact (in logical layer) tables to which belongs dimension attribute and join dimenstion to that fact.
Second you may:
Create fact table which join all needed dimensions with some useless fact ( i.e. count). Next you have to set option "Implicit Fact Column" in presentation catalog to use this fact table.
I can explain it to you in Polish by mail or phone
You bring me a next topic for my blog (in Polish) http://obiee.pl so I'll write sth about such behavior :)
Regards

SQL Server 2k - Pulling from 2 fact tables causes error

Trying to create a simple RPD as follows:
1 Dimension with Key Fund_ID
2 Fact tables, each with a Key Fund_ID
Created a Physical Layer, connecting Dimension to each Facts based off Fund_ID (One to Many)
Business Model Layer, connected Dimension to each Fact using complex join.
In Answers, the following is true:
Querying Dim and Fact Table A returns Data
Querying Dim and Fact Table B returns Data
Querying Dim AND Fact Table A, AND Fact Table B returns the following error message:
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 A) does not contain mapping for [table B]. (HY000)
It appears to be complaining that it cannot map the fact tables to each other. I tried mapping the two fact tables together (even though that doesn't make DW sense), and the RPD won't validate.
I'm wondering if this is a bug connecting to SQL Server. We do the majority of our RPD development against ORACLE, and this is our first attempt at using SQL Server as a source.
Does anyone have any suggestions on this?
thanks

I doubt it very much its DB specific, the error is from the BI Server ([nQSError: 15018]) rather than SS.
Have you got a dimension hierarchy ? Are your content levels set for all logical tables, do you have 2 logical facts or 1 combined logical fact ? What do your Logical Table sources look like (ie how many per logical table, conent levels ?joins within the LTS?)
I would guess the problem lies in your BMM layer. But should check, is the conformed dimension joined to both fact tables in the physical layer or have your aliased it ?

Relationship between Dimension without linking Fact table

Hi,
My question is like I have five dimensions connected to a fact table through primary - foreign key(Composite Key) relationship. Will this referential integrity help if I want some information between two dimension which are not linked directly and I am not
including any measures from fact table .
Example: Suppose I have customer, Product and Manufacturer Dimensions all linked to a fact table but not linked to each other directly but can I get right result when I want to know what are the manufacturer for each product? or list of
customers using a particular product. Will the referential integrity work ? since they all are related in fact table.
regards
Sanjoy ghosh

Hi Sanjoy -
The answer to your questions depends on your dimensional design and exactly what the fact table represents. Fact tables naturally capture the intersection of the different dimensions. This is true whether you physically implement a
PK - FK relationship in the relational db.
In your case, since customer is involved, sounds like a sales transaction fact. If that's true, you can easily join from customer, through the fact, to the product dimension, to get the list of customers that purchased a particular product.
For the manufacturer for each product, a sales transaction fact will not necessarily answer this question completely. Particularly in the case of products that have no sales for a given period, and thus, don't have any fact records to join from manufacturer
across to product. If you need to solve this question, you have some other options:
- flatten the Manufacturer directly into the Product dimension as attribute of the product (probably the simplest approach and allows you to remove a key from the fact)
- embed the Manufacturer key directly in the Product dimension (if you need the Manufacturer dimension separate for use with other events / facts and more detailed dimensionality - i.e., detailed attributes about the Manufacturer that wouldn't need
to be flattened onto the product)
- build a factless fact that captures the products offered by a given manufacturer at a given point in time (perhaps representing various products catalogs and associated dates. This would allow you to capture rich details about each dimension separately
and use the factless fact to record)
Let me know if that helps.
Brent Greenwood, MS, MCITP, CBIP
// Please mark correct answers and helpful posts //
http://brentgreenwood.blogspot.com

Join fact tables with different grain without upsetting measures?

Say I am a business analyst at a university, and I have two analytical cubes available to me: an Enrollment Cube and an Admissions Cube. The Enrollment Cube has a grain of Student and Semester, whereas the Admission Cube has a grain of Student, Application and Semester (a potential student can have more than one application in a semester). Is there any way for the OLAP developer that makes these cubes to make it so that I can use both cubes' fact tables without messing up their corresponding measures, such that I can create such analyses as the following:
County
Semester
Acceptance Rate (Admission Fact)
Retention Rate (Enrollment Fact)
County A
1
30%
88%
2
60%
87%
3
42%
84%
County B
1
90%
100%

One suggestion is to create a view that joins the 2 fact tables and then create a cube with measures mapped to the view for analysis purposes. However, this would be using the measures of the new cube for the analysis.

Mapping the Fact table to different levels of a dimension

Hi,
I have a fact table which stores the data for 4 levels of the dimensions. The aggregation method was taken care by PL/SQL and the fact table will have the data for all the 4 levels. When im trying to map all the levels to a column in the fact table using the OEM, it is generating the F KEY constraints referncing the columns mapped for the various levels of the dimension.
The problem is that im using a denormalised table for maintaing the values of the dimension. So the columns mapped for the levels(Except for the lowest) can't have the unique key defined on it. The cube is not getting created because of the error in creating the F KEY.
Can u please suggest how to map this fact table.
Thnks,
Manohar Vanama

I am not exactly clear on your schema but I believe you are trying to map tables which are not strict star or snowflake. This means that you cannot use CWM1 (and OEM), unless you change the structure of the tables. You might be able to map the tables with CWM2. The document below will assist you:
Oracle9i OLAP User's Guide
Chapter 4. Designing Your Database for OLAP
Chapter 5. Creating OLAP Catalog Metadata

Fact table mapping/loading

I am new to OWB and trying to use OWB 9.0.4 to create a star schema on a oracle 9.2 DB. Using OWB client, I successfuly created dims and a fact table on the target DB. But I got stuck with how to use OWB to map the fact table with dims and source tables, and using OWB to generate SQL loading scripts which contains PL/SQL statement shown below:
insert into "fact_table" ("fact_count") ( select count(*) from target_table where dim1='dime_value1' and dim2='dim2_value2');
here dim1 and dim2 are the dims assocated with the fact table and they are also mapped to the corresponding target table columns.

Frank,
source table -> aggregator -> target
As input into the aggregator, you specify dim1, dim2 and any numeric value. If you do not have one, use a numeric constant such as 1. In the aggregator, you specify dim1, dim2 as the group by clause (operator properties). You then add a numeric output attribute (edit function), and go to the attribute properties. As a function, specify count from the numeric input attribute.
That would load your measure.
Cube function is not currently supported in the mapping editor, but you could include that in a materialized view that is based on the table.
Mark.

FACT table Mapping

I could not find a clear documentation on how to create a mapping to load CUBE
after creating dimensions. I am using 10.1.0.2 version.
I have two dimensions and one FACT table
DIM1
D1_sk
other attributes
DIM2
D2_SK
other attributes
FACT
D1_sk
D2_sk
measure attributes
In previous forums I came across to use a lookup on dimensions
to load the FACT table.
But what would be my source to perform a lookup on Dimensions ?
because My dimensions are the source for the FACT TABLE.
Can I Join the DIMENSIONS to load the FACT TABLE?
can any one suggest the right approach to creat a FACT table mapping.
Thanks in advance.

Hi,
If you can tell what you are tying to achieve we can give some suggestions. You can use the same sources which you have used to load Dimensions, to load Fact table.
Mahesh

Calc problem with fact table measure used as part of bridge table model

Hi all,
I'm experiencing problems with the calculation of a fact table measure ever since I've used it as part of a calculation in a bridge table relationship.
In a fact table, PROJECT_FACT, I had a column (PROJECT_COST) whose default aggregate was SUM. Whenever PROJECT_COST was used with any dimension, the proper aggregation was done at the proper levels. But, not any longer. One of the relationships PROJECT_FACT has is with a dimension, called PROJECT.
PROJECT_FACT contains details of employees and each day they worked on a PROJECT_ID. So for a particular day, employee, Joe, might have a PROJECT_COST of $80 for PROJECT_ID 123, on the next day, Joe might have $40 in PROJECT_COST for the same project.
Dimension table, PROJECT, contains details of the project.
A new feature was added to the software - multiple customers can now be charged for a PROJECT, where as before, only one customer was charged.
This percentage charge break-down is in a new table - PROJECT_BRIDGE. PROJECT_BRIDGE has the PROJECT_ID, CUSTOMER_ID, BILL_PCT. BILL_PCT will always add up to 1.
So, the bridge table might look like...
PROJECT_ID CUSTOMER_ID BILL_PCT
123          100     .20
123          200     .30
123          300     .50
456 400 1.00
678 400 1.00
Where for project 123, is a breakdown for multiple customers (.20, .30. .50).
Let's say in PROJECT_FACT, if you were to sum up all PROJECT_COST for PROJECT_ID = 123, you get $1000.
Here are the steps I followed:
- In the Physical layer, PROJECT_FACT has a 1:M with PROJECT_BRIDGE as does PROJECT to PROJECT_BRIDGE (a 1:M).
PROJECT_FACT ===> PROJECT_BRIDGE <=== PROJECT
- In the Logical layer, PROJECT has a 1:M with PROJECT_FACT.
PROJECT ===> PROJECT_FACT
- The fact logical table source is mapped to the bridge table, PROJECT_BRIDGE, so now it has multiple tables it maps to (PROJECT_FACT & PROJECT_BRIDGE). They are set for an INNER join.
- I created a calculation measure, MULT_CUST_COST, using physical columns, that calculates the sum of the PROJECT_COST X the percentage amount in the bridge table. It looks like: SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT)
- I brought MULT_CUST_COST into the Presentation layer.
We still want the old PROJECT_COST around until it get's phased out, so it's in the Presentation layer as well.
Let's say I had a request with only PROJECT_ID, MULT_CUST_COST (the new calculation), and PROJECT_COST (the original). I'd expect:
PROJECT_ID MULT_CUST_COST PROJECT_COST
123          $1000     $1000
I am getting this for MULT_CUST_COST, however, for PROJECT_COST, it's tripling the value (possibly because there are 3 percent amounts?)...
PROJECT_ID MULT_CUST_COST PROJECT_COST
123          $1000 (correct)      $3000 (incorrect, it's been tripled)
If I were to look at the SQL, it would have:
          SELECT SUM(PROJECT_COST),
SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT),
               PROJECT_ID
          FROM ...
          GROUP BY PROJECT_ID
PROJECT_COST used to work correctly before modeling a bridge table.
Any ideas on what I did wrong?
Thanks!

Hi
Phew, what a long question!
If I understand correctly I think the problem lies with your old cost measure, or rather combining that with you new one in the same request. If you think about it, your query as explained above will bring back 3 rows from the database which is why your old cost measure is being multiplied. I suspect that if you took it out of the query, your bridge table would be working properly for the new measure alone?
I would consider migrating your historic data into the bridge table model so that you have a single type of query. For the historic data each would have a single row in the bridge with a 1.0 BILL_PCT.
Best of luck,
Paul
http://total-bi.com

OBIEE 10g: Problem on fact table mapping

Hi to everyone,
i have this situation:
1) i have 2 fact tables in phisical model (FHRCTR and HCTOT) this two table is the same in the FK columns.
2) the structure is: FHRCTR[month_fk, transaction_type, measure A], HCTOT[month_fk, measure B]. 'transaction_type' is an attribute of the table not dimension.
3) i have created a logical fact table with this two tables for source.
4) each field of logical table is mapped on the corrispetive field on the both phisical table, except for 'transaction_type' column having as source only FHRCTR table.
5) i've created a report with follow colums: month_fk, transaction_type, measure_A, measure_B
The problem is: if i create the report with the columns in point 5, the measure_B returns null values and the measure_A have a correct value.
Insteed if i create a report without 'transaction_type' column the value of Measure_B and Measure_A are correct.
I remind you that: 'transaction_type' in the logical fact table is mapped only on the FHRCTR table because on HCTOT it doesn't exist.
Can you help me to solve this issue?
Thanks

832596 wrote:
Can you help me to solve this issue?
ThanksI guess when you set some aggregation rule for 'transaction_type' in a repository then all will be ok (for examplу - min). But you'll get results that you don't expect.

Measure value in intermediate fact table

Hi I have a schenario where i have a measure in intermediate fact table ( in a many to many relation ship ) and i am not able to handle this.
I have file summary fact that has file details - names , spaceGB , share details , cost per GB, Total cost of file ( SpaceGB * Cost per GB)
Share dim that has regular relationship.
We have another mapping table (fact) that gives many to many relationship between Shares and Cost Center and there is a allocation percentage associates with a share across different costcenters
Share Costcenter Allocation%
Share 1 CostCeneter1 50%
Share 1 CostCeneter2 50%
everything works fine as long as i dont show allocation % how do i handle allocation % to get cost center cost.

Hi Vin444,
According to your description, there is a measure in intermediate fact table which you are not able to handle this in database level, now what you want is showing intermediate fact table measure value, rithg?
As pey my understanding, you can join the tables based on the intermediate fact table on datasource view. A named query is a SQL expression represented as a table. In a named query, you can specify an SQL expression to select rows and columns returned from
one or more tables in one or more data sources. So in your scenario, you can join the tables using named query instead of database level.
http://msdn.microsoft.com/en-IN/library/ms175683.aspx
http://msdn.microsoft.com/en-IN/library/ms174778.aspx
If I have anything misunderstood, please point it out.
Regards,
Charlie Liao
TechNet Community Support

Mapping measures to fact tables crashes (in OLAP Catalog)

Similar Messages

Maybe you are looking for