Вот пример для MSAS2k, можно ли пример с использование новинок Юкона?
От:John Desch [MS] (
jdesch@msonline.microsoft.com)
Тема:Re: Writeback -> USE_WEIGHTED_ALLOCATION
Making the following assumptions:
1. The time dimension uses a Year, Quarter, Month, Day structure in a star
schema
2. The product dimension uses a Family, Group, Item structure in a star
schema
I was able to get the following UPDATE CUBE statement to successfully
execute.
UPDATE CUBE [Sales] SET
([Products].[All Products].Dryers, [Measures].[Sales Units]) = 3000
USE_WEIGHTED_ALLOCATION BY
IIF([Time].[Year].UniqueName="[Time].[All Time].[2001]",
([Time].[All Time].[2000],[Products].CurrentMember)/
([Time].[All Time].[1999],[Products].CurrentMember),
([Time].[All Time],[Products].[Dryers])/
([Time].[All Time],[Products].[Washers]))
However, based on your last posting, I suspect that's not exactly what
you're wanting to do.
One of the issues that you're going to encounter is that unless you're
writing back to the DataMember of a Parent-Child dimension, any writeback
occurs at the cell level and is going to impact aggregate values in both
the Time and Product Dimension.
If you're wanting to update at the Time.Year level and have the data
allocated to the Time.Quarter, Time.Month membersbased on actual costs, the
only possibility I can think of would be to build the Time Dimension as a
Parent-Child dimension and set the Members With Data property of the
dimension to either "Non-Leaf Data Hidden" or "Non-Leaf Data Visible" and
add a Custom Rollup something like:
IIF(IsLeaf(Time.CurrentMember),
CalculationPassValue(Time.Currentmember,0),
rollupchildren(Time.currentmember,"+"))
Likewise, if you're wanting to update at the Product.Family level and have
the data allocated to the Product.Group and Product.Item members, the same
approach described above should work.
Regards,
John Desch, MCDBA, MCSD
This posting is provided “AS IS” with no warranties, and confers no rights.
