Fact table showing incorrect quantity measure

Hi,
I have a scenario where i have a fact table with multiple rows and two quantity fields. My source system holds sales by "package" which can contain any number of components. The grain of my invoice table is component level. See
structure below:
PACKAGE1
- Component1 - each package contains 2 of these
- Component2 - each package contains 1 of these
So if i am reporting a sale of PACKAGE1, for a quantity of 2 - component1 had a total sales quantity of 4 and component2 has a total sales quantity of 2. However the package was only sold 2 of, but because of the sum aggregation, i see a total quantity
sold for PACKAGE1 of 6, but it should only show 2 at that level. I have looked at semi-additive measures but am unsure of how this would work in this scenario, or which option would work best for me here.
My fact table has 2 rows, each of which reference the component as one dimension and the package as another dimension.
As a workaround, I have created a calculation to divide the quantity by the number of package components (so it would show a 1 for each of the component lines in my fact table), but then the sales quantities of the components reported are incorrect.
What is the best approach for this?
Thanks in advance,
Dom

Hi Dominic,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Thanks,
Simon Hou
TechNet Community Support

Similar Messages

DB2 | table shows incorrect columns

Has anybody encountered this? Using IDM 6 and 7.
I have configured the database table adapter to connect to a DB2 table. The DB2 version is 7.1, so we are forced to use Type 2 jdbc driver (and not type 4).
I then installed db2connect and configured a dsn and connected to that dsn in the database table adapter wizard. It all connects fine and I can see all tables views etc that are accessible to the user configured inside the dsn.
It so happens that there are 2 tables with the same name with different owners (creators). But the dropdown listing all tables do not show the table owners - only table names are shown. I can see my table listed twice, but regardless of which one I pick, the same columns are shown and it happens to belong to the wrong table - not the table I am interested in.
Is there some setting I can use somewhere (dbconnect or java) where I can force jdbc to pull a specific table (owned by a specific user)? Or is there any workaround at all for this?
Thanks

Thanks.. - OK this is what I ended up doing. Since the user did not own ANY tables (or objects) in DB2, I created a database table resource for a local mysql table.
Then I went into debug and changed the type back to DB2 and put the correct table name with the owner prefix. Of course I had to change the name to something more appropriate. I removed the id and imported back into IDM. Now I had a new resource - I click on this and edited the schema to include the other columns. And it works fine so far.
best regards

Modelling 2 Fact Tables with Non-Conforming Dimension in OBIEE 11g

Hi all,
I have two fact tables (Fact 1 and Fact 2) and two dimension tables (Product and Rule). The Product dimension table is a conforming dimension and is used in both fact tables, but the Rule dimension is a non-conforming dimension which is used only one fact table. I'm using OBIEE 11g (11.1.1.6.0).
====
Fact 1
====
Sales ID | Product ID | Quantity | Sales Description | Sales Status
S001 | P001 | 100 | bla bla bla bla bla | N
S001 | P002 | 200 | bla bla bla bla bla | N
S002 | P001 | 200 | lab lab lab lab lab | Y
S002 | P003 | 250 | lab lab lab lab lab | Y
Notes for Fact 1:
- One Sales ID can have multiple Product IDs
- Sales Description and Sales Status are the same for one Sales ID (repeating Sales Description and Sales Status for the same Sales ID)
====
Fact 2
====
Sales ID | Product ID | Rule ID | Score
S001 | P001 | R001 | 2
S001 | P001 | R002 | 3
S001 | P002 | R003 | 1
S002 | P001 | R003 | 1
S002 | P003 | R002 | 2
S002 | P003 | R004 | 5
Notes for Fact 2:
- One combination of Sales ID and Product ID can have multiple Rule ID
I'm wondering how best to model these tables so that I can create this report (number of the dimension and fact tables created in the business model, level mapping, aggregation rule, etc)? Any suggestion/advice on how to achieve this?
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
S001 | P001 | 100 | bla bla bla bla bla | N | R001 | 2
S001 | P001 | 100 | bla bla bla bla bla | N | R002 | 3
S001 | P002 | 200 | bla bla bla bla bla | N | R003 | 1
S002 | P001 | 200 | lab lab lab lab lab | Y | R003 | 1
S002 | P003 | 250 | lab lab lab lab lab | Y | R002 | 2
S002 | P003 | 250 | lab lab lab lab lab | Y | R004 | 5
Thank you very much!

Hi Dhar, thanks for the suggestions.
I tested what you suggested, but the result is not as per my expectation mentioned above. Here's what I did:
1. In physical layer:
- I joined Fact 1 table with Product dimension table only
- I joined Fact 2 table with Product and Rule dimension tables
2. In business model layer:
- I created 3 logical tables: Fact, Product, and Rule
- The Product table contains the Product ID and Product Name from the Product dimension table in the physical layer
- I created the hierarchy (logical dimension) for Product with only ProductTotal level (as the grand total level) and ProductDetail level that contains Product ID and Product Name
- The Rule table contains the Rule ID and Rule Name from the Rule dimension table in the physical layer
- I created the hierarchy (logical dimension) for Rule with only RuleTotal level (as the grand total level) and RuleDetail level that contains Rule ID and Rule Name
- The Fact table contains 2 logical tables sources: Fact 1 (which logical level in the Content tab is mapped to ProductDetail and RuleTotal) and Fact 2 (which logical level in the Content tab is mapped to ProductDetail and RuleDetail)
- The Fact table contains Sales ID logical column (mapped to both Fact 1 and Fact 2 logical table sources)
- The Fact table also contains Sales Description and Sales Status logical columns (mapped to only Fact 1), which aggregation rule is the default to None
- The Fact table also contains Quantity logical column (mapped to only Fact 1), which aggregation rule is set to Sum
- The Fact table also contains Score logical column (mapped to only Fact 2), which aggregation rule is set to Sum
OBIEE returns the expected result when I retrieve the report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status
However, OBIEE returns an error when I retrieve the reports:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID
or
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
The error is:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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 FACT.SALES_STATUS. (HY000)
And the Score column is blank when I retrieved this report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Score
Any suggestion anyone? Please help. Thanks a lot!
Edited by: stewartlife on Nov 29, 2012 4:01 PM

Reporting that traverses two fact tables

I have searched and am stumped on how to make the work in OBIEE. I can do it with straight SQL on the physical layer, but can't get OBIEE to accept it. I have a customer history fact table that contains several measures and connects to several dimensions. This creates one star. I have a campaign (ad campaign) dim that connects to an Account_Campaign Fact, as one Account may have many campaigns. The Account Dim connects also to the CustHistory fact. When I try and use information from the CustHistoryFact against information in the either the Campaign Dim, or the AccountCampaign fact, I get the following error:"{color:#800000}[nQSError: 14026] Unable to navigate requested expression . . . Please fix the metadata consistency warnings. (HY000){color}"
In the administration tool, everything checks out as consistent, and I have verified that I can get the correct result using SQL on the physical side.
My diagram is roughly
Customer(and other)Dim -< CustHistoryFact >-AcctNbrDim -< AccountCampaignFact >- CampaignDim
Any ideas?

Hi...
From your scenario, there are 2 facts seems CustHistoryFact, AccountCampaignFact.
And dimensions are: Customer(and other)Dim, AcctNbrDim, and CampaignDim
Do one thing, one of good technique to avoid this error is : mention the levels (Hierarchies) in administration tool. i.e. rpd.
For the 2 fact tables, whatever the tables directly connecting to fact tables (or which are having direct joins) need to mention levels in detail level, and for the the dimensions which are not related directly, (or which are not having direct joins to facts) need to mention levels in total level.
I think you might have known about the level mentioning in rpd, go to the particular fact table source in BMP layer, double-click > Content tab, here you find the hierarchies you created, there you need to mention your levels.
For your scenario, For fact CustHistoryFact table source, mention detail level for Customer(and other)Dim and AcctNbrDim
............................................................................, mention total level for CampaignDim
In the same way, for fact AccountCampaignFact table source, mention detail level for CampaignDim and AcctNbrDim
...................................................................................., mention total level for Customer(and other)Dim

3 confirmed Dimensions and 2 fact tables

Hi experts,
how can we connect 3 confirmed Dimensions and 2 fact tables without loops and traps please give me a solution

Hi,
Dimensions Tables : Dimension tables are typically small, ranging from a few to several thousand rows. Occasionally dimensions can grow fairly large, however. For example, a large credit card company could have a customer dimension with millions of rows. Dimension table structure is typically very lean, for example customer dimension could look like following:
    Customer_key
    Customer_full_name
    Customer_city
    Customer_state
    Customer_country
Fact Tables :a fact table consists of the measurements, metrics or facts of a business process. It is often located at the centre of a star schema or a snowflake schema, surrounded by dimension tables.
Fact tables contain keys to dimension tables as well as measurable facts that data analysts would want to examine. For example, a store selling automotive parts might have a fact table recording a sale of each item. The fact table of an educational entity could track credit hours awarded to students. A bakery could have a fact table that records manufacturing of various baked goods.
Context Versus Alias Overview :
http://www.dagira.com/2009/07/22/context-versus-alias-overview/
How to create context :
http://www.bidw.org/business-objects/universe-design/understanding-context-and-its-use-in-business-objects-universe/
You can also look on the eFashion universe for more information.
Thanks,
Amit

Answers pointing to a Particular Fact table only

Hi All
I have an issue. Actually i have some attribute dimension tables which are connected to many fact tables and are used in different subject area. Previously it was working fine as subject areas were using the fact table available in tht subject area. But now when i am not using any fact table to show result rather taking only dimension to see result it is throwing one error telling tht for X fact table there is no mapping for the corresponding dimension table. But the pity is tht i vent used tht fact table atall in tht subject area. Now its throwing the same error for many Subject area which ve the same dimension table. And another thing is tht when i am changing the combination means sequence of columns in request its nt showing view display error but for a particular combination sequence in all subject area its throwing the error by pointing to a Pariculat fact table showing no mapping is ther.

Hi,
I think you have to check your (Business) Model again. Do you get warnings when you run a concistency check?
You could force a Subject Area to us a particular Fact Table by defining an implicit fact column on your Subject Area.
Good Luck,
Daan Bakboord
http://obibb.wordpress.com

Fact table with datetime measure showing #value error while browsing the cube

Hi All,
I have a cube with a fact table having datetime measure.
when I browse the cube, I am able to see the data for all measures except for the measure with the datetime as datatype.
Thanks in advance.

Hi jarugulalaks,
Actually this forum is to discuss:
Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
To make this issue clearly, would you mind letting us know more information about this issue? Whether it is the VS IDE issue? Which language are you using? Which kind of app are you developing? Maybe you could share us a screen shot about it.
But like this case posted by you here:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/bc2d30b8-a60d-4f0f-a273-b7cf0f5aaed5/value-error-for-datetime-measure-in-ssas?forum=visualstudiogeneral#bc2d30b8-a60d-4f0f-a273-b7cf0f5aaed5
If it is the SSAS issue, please post this issue to the SSAS forum for dedicated support.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Fact table with 2 time keys, measures showing together in the same report

Hello,
I am using OBI EE and I have the following scenario: a fact table hold information about enquiries. An enquiry may or may not generate an appointment. So in my fact table I have two date columns: enquiry date and appointment booked date (not the date of the appointment itself, but when it was actually booked).
This raises a couple of questions. First question is: I can only have one logical FK to the Times table, how to create two LFKs for those 2 dates? Should I create a logical copy of the Times table in the BMM, along with another time dimension?
Second question is how to display both pieces of data in the same report. For instance, in a summary report per month I want to see the number of enquiries made and appointments booked in each month. Most likely they will be different numbers and refer to different rows in the database. What is the best way to model this in the BMM?
For instance, in October there were 10 enquiries, 8 of them were converted into appointments along with 3 enquires made in September. So, the report should show for October: number of enquires: 10, number of appointments: 11 (8 from October + 3 from September)
Sorry if this is a basic question but I couldn't find around any examples of this scenario.
Thanks,
Luis

Genius, that works perfectly, thanks!
Just one issue that I noticed... I have other dimensions on that fact table, one of them is "channel". Channel is linked to a column in the original fact table, as is Number of Enquiries.
If I include Channel in a report that shows Number of Enquiries and Number of Appointments, the Number of Appointments column only shows zeros, while the Number of Enquiries column still shows the correct numbers:
Month    Channel   Enquiries   Appointments
Jan 09   Email      100           0
         Phone      120           0
Feb 09   Email       87           0
...Then I figured out that I needed to add a PFK for all dimensions to the aliased fact table, not only for the times dimension.
Thanks again
Luis

OBIEE: incorrect selection of fact table when generating SQL

I have 2 dimension tables ("DimA" and "DimB") connected with one fact table ("Fact1").
Also (only) "DimB" is connected with another fact table "Fact2".
When I want to make a report with one attribute ("Attribute_A") from "DimA" and another one ("Attribute_B") from "DimB", I receive a error like this:
"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 Fact2) does not contain mapping for [DimA.Attribute_A]. (HY000)"
Remember that is not supposed "DimA" to be connected with "Fact2", only with "Fact1".
The only factor that I see that can be a problem is the fact that in Presentation Catalog was defined a implicit column from tact table "Fact2".

Hi,
While I don't know the need to generate a report based on 2 dimensions only, I mean you are trying to generate a report between 2 dimensions. Dimensions are not joined together in OBIEE. OBIEE will try to pull any fact and try to obtain the relationship between the two dimensions. In your case it is taking Fact2.
One way could be if u just pull in some measure from Fact1, then u should be able to get the report.
Else u can try setting content level for DimA in fact 2 to grand total level. This can be done even though dimA and Fact2 are not joined. Although I am not sure whether this will work.

Measures values are twice as big compare to corresponding fact table

The version used is SQL Server 2012
We have a CustomerAddressKey in fact tables with many partitions and Regular Dimension Usage between fact table and CustomerAddress dimension. As we do not process all partitions every day sometimes we encounter the issue when users see the old address for
a particular player.
We have played with 2 approaches: Referenced Dimension Usage and modification of CustomerAddress view when only current (latest) address is available.
After we build and process Referenced Dimension Usage version using CustomerAddress as Reference Dimension and Customer as Intermediate dimension and CustomerAddressKey and CurrentCustomerAddressKey.
Everything is OK besides that the measures value for any slice is twice as big as corresponding fact table value.
What did we do wrong?
serguei russky

There are a couple of ways that data can get duplicated in SSAS
One is incorrectly running multiple ProcessAdd operations. ProcessAdd always appends data. So if you run it twice with the same set of rows you end up with duplicate fact rows in your cube. The way to fix this is to run a ProcessFull on the affected partition/s.
The other common thing that can duplicate data is issues with your data and / or schema. The following is just psuedo code, the join conditions should be the same as you've specified in your DSV. If you run these two styles of SQL queries over your raw data
and they return different amounts then you probably have a problem with the way you have populated the data in your reference dimension table.
SELECT SUM( <measure column> )
FROM <fact table>
SELECT SUM( <measure column> )
FROM <fact table>
INNER JOIN <reference dim>
ON ...
INNER JOIN <CustomerAddress dimesion>
ON ...
http://darren.gosbell.com - please mark correct answers

OBIEE Hitting incorrect fact table

Hi,
I have two Fact tables joined with 3 Dimensions..
F1 - D1, D2, D3
F2 - D1, D2, D3
Now I added another dimension D4 and joined it with F2.
While taking D1, D2 D3 while it use to get F1 in the Query now, it started taking F2 and showing incorrect results.. How can this be fixed?

Dont blame OBIEE!! You haven't configured it correctly.
Try to set implicit fact column setting on Subject area. That might help you.
If helps mark

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

Measures in the fact table

Hello,
Can i have measures in the fact table in business layer?
I am using obiee 11g.
like i have a fact table where i have a user i applied aggregation rule of count distinct.
Now i would like to add a lower function to it like count (distinct(lower(username)).
But then it becomes like a measure with fx with the name and not the usual yellow colour.
Wanted to know if its good practice?
Thanks

Hi,
You have two measure columns.
one with lower function
other without lower function.
For your information: Distinct is case sensitive.It will show the difference between 'A' and 'a'.
Regards,
Lakshmipathi.
Edited by: Lakshmipathi on Jul 7, 2011 2:41 PM

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

Dynamic Bands on Fact Table measure

I'm trying to create income bands on my fact table, not sure how to go about it or if its possible.
I have a fact table that consists of
Date, TranType, AdvKey, AdvGrpKey, Amount
Each Adviser belongs to an AdvGrp.
I want to be able to group on AdvKey or AdvGrpKey and have the summed amounts (income) allocated to income bands.
So when I group on Adviser, they will be assigned an income band, ie 0-10k, 10-50k, 50-100k, same applies when the grouping is changed to the Group Level.
The facttable has about 2 million rows.
The income is how much is generated from the advisers and adviser group, so this will change over time.
Can this be done and can it be done dynamically.
I can't think of any way to do it with a dimension, as there is no way to link back to the fact table.
Any ideas on how to solve this would be much appreciated.
Thanks
Jon

Hi Richard,
Thanks for taking the time to respond to my query.
I'm struggling to work out what your query is doing, and how to use it.
So I took your query and replaced bits of it with my data, however the output is not as expected.
While I try to work out what is going on, I'm hoping you happen to read this first, and might be so kind as to throw me a few pointers.
I tweaked my fact table to only have AdvKey now. The parent child relationship is in the DimIFADetails now, which is the Advisor Group level and the Adviser level. The query below is looking at the Advisor Group level.
with
member measures.NewAmount as Measures.Amount * -1
member measures.WTH as (MyGroups.item(Measures.r),Measures.MyRange)
member measures.MyRange as
cstr(round(Measures.NewAmount/10000,0)*10000)+"-"+cstr(round(Measures.NewAmount/1000+1,0)*10000-1)
set MyGroups as
Order(nonempty([Dim IFA Details].[Parent Key].[Adviser Group], Measures.NewAmount)
,Measures.MyRange, BASC)
member measures.r as rank([Dim IFA Details].[Parent Key], MyGroups)
member measures.RangeTot as iif((MyGroups.item(Measures.r-2),Measures.MyRange) = Measures.MyRange ,
Measures.NewAmount +(Measures.RangeTot,MyGroups.item(Measures.r-2)),
Measures.NewAmount)
member Measures.RangeTotal as
iif((MyGroups.item(Measures.r),Measures.MyRange)=Measures.MyRange,
null,Measures.RangeTot)
select {Measures.MyRange,Measures.RangeTotal
, measures.newamount, measures.r, measures.WTH
} on 0,
nonempty(MyGroups,Measures.RangeTotal) on 1
from
[Income and Emails Cube]
My Amount field is negative and shouldnt be so I added a new measure to deal with it now.
Below are the results I am getting
New amount is the summed amount of my adviser groups, the value I wish to put in bands.
The new amount falls in the correct MyRange, so thats good.
But its generating too many MyRange values ie the first six rows and fall into the first MyRange.
Not sure what is going on with RangeTotal.
I put up the other columns hoping it might shed some light, but at this point, I'm a little lost.
I want to be able to switch between showing Advisers and Adviser Groups, and display the bands.
I'm hoping you might hand hold me through this.
Regards
Jon

Fact table showing incorrect quantity measure

Similar Messages

Maybe you are looking for