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.

Similar Messages

How to separate non metric fields in Fact tables

Hi All,
I am having metric fields along with some non metric fields in fact tables(All the fields has to be present in fact table only). Is it possible to group all non aggregated fields and aggregated fields in the same fact tables. Please advise.
regards,
Guru

check this
OBIEE, Endeca and ODI: Fact and Dimension from single source Table
Thanks,
Saichand

Is it possibe to have non numeric measures in cube??

Hi is it possible to have non numeric measures in a cube?? As i get an error during deployment of mapping of this cube if i have non numeric measures in a cube ....

Normally a measure should perform an aritmetic operation, like a sum( price paid ), or average( processing duration ). With a non-numeric measure you could do count, count distinct and that's about it. Non-numeric measure makes little sense, in my opinion a non-numeric property of a measure is a dimension.

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

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

None of the fact tables are compatible error

Hi All,
I do see this error (none of the compatible fact table) after setting the content level aggregation on the dimension tables and the fact table. This error i get only when i try to pull the calculated item which is based on a attribute in the fact table. I have an attribute like year in the fact table i need to display like 'CY'||'2013' in a calculated logical column and when i pull this into answers i get this error -
1) joins are ok ; only one fact table and 3 dimension tables
2). content level on the fact table are specified at the detail level and also for the dimensions
any suggestions - thanks for your time

can anyone please provide some suggestions -
> i looked at the fact table LTS and specified the logical level for each dimension as the detail
> specified the LTS for each dimension table
> I have a column in my fact table which is calendar year and i want to have a derived column like rep_cal_year with 'CY'||cal_year - so when i pull this derived column in my answers i get the error - none of the fact tables are compatibile with the query;
what could be missign?

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

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

Select only non-numeric characters

A
$
^
(78^*)5$#7
)!@#$0-99
_454*(&--0
+@#$%564
=123
How select only non-numeric characters from above table?

Nilesh Hole,Pune, India wrote:
but i want a uniqe query.
suppose table have n number of rows then how i will wirte a query.Not sure what you mean? Do you want to select a list of distinct non-numeric characters used in your table? Then:
column "Distinct non-numeric chars" format a30
with t as (
           select '!' a from dual union all
           select '@' from dual union all
           select '#' from dual union all
           select '$' from dual union all
           select '%' from dual union all
           select '^' from dual union all
           select '&' from dual union all
           select '*' from dual union all
           select '(78^*)5$#7' from dual union all
           select ')!@#$0-99' from dual union all
           select '_454*(&--0' from dual union all
           select '+@#$%564' from dual union all
           select '=123' from dual union all
           select '135790' from dual
select distinct substr(a,column_value,1) "Distinct non-numeric chars"
from (
         select regexp_replace(a,'[[:digit:]]') a
           from t
           where not regexp_like(a, '^[[:digit:]]+$')
        table(
              cast(
                   multiset(
                            select level
                              from dual
                              connect by level <= length(a)
                   as sys.odcinumberlist
Distinct non-numeric chars
+
=
$
Distinct non-numeric chars
^
14 rows selected.
SQL> SY.

Compare non numeric data using arithmetic operations

Hi
Is there anyway to compare the non numeric data in a table to a numeric number.
Want to run a query like
SELECT rank_id
                                      FROM   mas_rank
                                      WHERE rank_code > 26 Rank_code contains numeric as well as some non numeric data
Thanx for the help

Yes, it will work if you just say > '26' See this demo :
SQL> create table mas_rank(rank_id number,rank_code varchar2(2));
Table created.
SQL> insert into mas_rank values (100,'aa');
1 row created.
SQL> insert into mas_rank values (101,'ab');
1 row created.
SQL> insert into mas_rank values (102,'ad');
1 row created.
SQL> insert into mas_rank values (103,'ag');
1 row created.
SQL> insert into mas_rank values (104,'ac');
1 row created.
SQL> insert into mas_rank values (105,'22');
1 row created.
SQL> insert into mas_rank values (106,'25');
1 row created.
SQL> insert into mas_rank values (107,'26');
1 row created.
SQL> insert into mas_rank values (108,'27');
1 row created.
SQL> insert into mas_rank values (109,'aa');
1 row created.
SQL> insert into mas_rank values (110,'28');
1 row created.
SQL> SELECT rank_id
2                                        FROM   mas_rank
3                                        WHERE rank_code not in ('ab','ad','ag')
4                                                 and rank_code > 26;
                                               and rank_code > 26
ERROR at line 4:
ORA-01722: invalid number
SQL> ed
Wrote file afiedt.buf
1 SELECT rank_id
2                                        FROM   mas_rank
3                                        WHERE rank_code not in ('ab','ad','ag')
4*                                                and rank_code > '26'
SQL> /
   RANK_ID
       100
       104
       108
       109
       110
SQL>Regards
Girish Sharma

Can date be included in the fact table as a measure?

Dear All,
I have to migrate a database form relational model to dimensional model. It a kind of human resource database. I don't know what MEASURES should I keep in the fact table. There are only dates, like date the employee joined the institution and the date he will leave. Most of the other fields are non-numeric. well date is also non-numeric but we can calculate the duration the employee worked from these dates.
What do you suggest?

I'd be careful about adding a "measure" of duration worked (be it days, months, years - doesn't matter). Causes lots of churn. For example, if you choose a measure of "duration_worked_in_days" - every single row in the fact table would be obsoleted every single day....
What types of questions do you expect the fact table to answer?
I'm working on a HR mart right now, and my fact data is around pay rates (not actual pay), i.e. annual salary, hourly salary, etc. My records also have two "date" dims - effective start date and effective end date. Meaning if my annual salary is $50 a year between 1/1/2008 and 12/31/2008, that's what the row shows. When (or if) I get a pay raise (/cut), the "current" record gets end dated, and a new record inserted.
When you say that a fact table "must" contain measure columns - I assume you're using the actual OWB fact / dimension objects, vs. just tables? Very common in a HR data warehouse to have a "factless" fact table.
Hope this helps,
Scott

Essbase answers - None of the fact tables are compatible with the query request "member"

Hi,
I have modelled an Essbase database into the repository.
If I pull the measure, period and year dimension in and filter on the year (member) and display the year (member) along with the period (alias) and measure it errors with =>
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: 14020] None of the fact tables are compatible with the query request Fiscal Year.Fiscal Year Code. (HY000)
However, all other things being equal if I change the year displayed to the alias then it works.
Anyone tell me why??
Is there a limitation that Essbase brings through that you cannot view what you filter on?
thanks,
Robert.

Hi
i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting 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 Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
Gl Balances : D1
Code Commbination: F1
Gl Sets Of Books : F2
I have checked the joins in physical and BMM layer..all are fine..

Issue with non calculated column in a fact table

Hi All,
With 3 facts(Fact1,Fact2,Fact3) and 2 Confirmed Dimensions my joins work fine in Criteria when I include All calculated columns from facts. If I try to include a non calculated column from Fact1(Which is a number Data type) Columns from Fact2 and Fact3 show Null values. I know it is not recommended to include dimension columns in fact , does OBIEE not support Number type non calculated columns as well? Is there any work around that I can bring in my non calculated column from Fact and still get results for other fact columns.Iam at 11.1.1.7 of OBIEE
Let me know if Iam not clear.
Your help is much Appreciated.
Thanks,
Vineela.

i would like to add 2 fields into my fact tables - LOAD ID (populated by a sequence during each load) and LOAD DATE.
as these fields are not related to any reporting dimensions, it is still possible to add them in OWB ? the fact wizard always ask for a foreign key to a dimension ...
Duncan,
If you want to add non dimensional attributes to a fact by using OWB, you can create additional measures to it and use them as attributes.
Igor

Non dimensional attributes in a fact table

i would like to add 2 fields into my fact tables - LOAD ID (populated by a sequence during each load) and LOAD DATE.
as these fields are not related to any reporting dimensions, it is still possible to add them in OWB ? the fact wizard always ask for a foreign key to a dimension ...

i would like to add 2 fields into my fact tables - LOAD ID (populated by a sequence during each load) and LOAD DATE.
as these fields are not related to any reporting dimensions, it is still possible to add them in OWB ? the fact wizard always ask for a foreign key to a dimension ...
Duncan,
If you want to add non dimensional attributes to a fact by using OWB, you can create additional measures to it and use them as attributes.
Igor

Constructing Calculated Measures in MDX for different measures using same columns in a fact table

Hello,
i have a fact table with 2 columns corresponding to dimensions Dim1, Dim2. In the same table i have 4 other columns Value_Type(int), INT_VALUE(int), FLOAT_VALUE(float), TEXT_VALUE(string). There are a number of measures which are identified by Value_Type and
depending on their nature could be written in one of the 3 columns (INT_VALUE(int), FLOAT_VALUE(float), TEXT_VALUE(string)) Let's say Measure1 with Measure_Type=1 is age, 2 is account balance and 3 is Name for clarity. There could be other measure types that
use these 3 same columns for data. So the sample fact table looks like this
Dim1 Dim2 Measure_Type INT_VALUE FLOAT_VALUE TEXT_VALUE
10 10 1 25
10 10 2 2000,34
10 10 3 John
10 20 1 28
10 20 2 3490,23
10 20 3 Frank
My task is to write an MDX query for each Dim1, Dim2 combination which returns all 3 measures in the same row. The idea is to construct a calculated member for each Measure that returns value from the right field. For example for Measure1 we take INT_VALUE
with measure_type=1. The problem is i don't know how to construct MDX query for these calculated members. Can you please help me?
So my final goal is to write an MDX query that returns all measures in one row for each set of Dim1, Dim2
SELECT [Measure1], [Measure2], [Measure3] ON COLUMNS,
NON EMPTY [Dim1].[Dim1].[Dim1].Members*[Dim2].[Dim2].[Dim2].Members ON ROWS
FROM [Cube]
Dim1 Dim2 Measure1 Measure2 Measure3
10 10 25 2000,34 John
10 20 28 3490,23 Frank

Hi Kosmipt,
I would combine the "INT_VALUE", "FLOAT_VALUE" and "TEXT_VALUE" columns into one with STRING data type for the fact table. And there should be one dimension to store the Measure_Type informations. Then in cube, you can write MDX scope for every one of
"Measure_Type" dimension members. For example,
scope(
            [Measures].[M]
    [DimMType].[MType].&[1]= CINT([Measures].[M]);
end scope;
Once the cube is built by the above way, you can write MDX like something like the following to achieve your purpose.
WITH member [Measures].[Measure1] AS ([DimMType].[MType].&[1],[Measures].[M])
         member [Measures].[Measure2] AS ([DimMType].[MType].&[2],[Measures].[M])
         member [Measures].[Measure3] AS ([DimMType].[MType].&[3],[Measures].[M])
thanks,
Jerry

Non-numeric Measures in fact table

Similar Messages

Maybe you are looking for