Representing a calculation schema within a dimension hierarchy
Hi,
I want to build a reporting hierarchy in SSAS to have it readily available for reporting.
The real hierarchy look like:
http://i59.tinypic.com/2irl0k1.png
However I want it to be like the following:
http://i57.tinypic.com/2v93rl2.png
I have tried to do this with the following statement in the cube design:
Scope([DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB1]);
This = [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB1]
+ [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[TURNOVER];
End Scope;
Scope([DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB2]);
This = [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB2]
+ [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB1];
End Scope;
However, this has an effect on the other dimensions. When I now put just the products on one axis the result is messed up.
How can this be done?
Many thanks in adavance.
Calculated Member are not a solution, because to my knowledge they cannot be placed freely in the hierarchy.
Hi Felix,
It looks like the simple hierarchy you are querying should have been conceived as a ragged hierarchy instead. This is remarkable because the labels have also a financial nature.
Instead of struggling with scope statements, is it an option to build that hierachy like those find in a financial cube?:
http://martinmason.wordpress.com/2012/02/26/the-ssas-financial-cubepart-1ragged-hierarchies/
Philip,
Similar Messages
-
Star Schema Dimension Hierarchy Changes Over Time
Say you have a dimension hierarchy with the level Department that has a child level Division. The Sales Division belonged to the Financials Department up until July 9th, 2011, after which it was moved to the Marketing Department. How can you make it so that both Sales Divisions are interpreted as the same Division, rather than two different Divisions as BI Answers does by default?
I don't think SCD1 would work as BI Answers essentially splits things via both keys and description fields, resulting in odd behavior such as this:
Time
Division
# Employees
All Time
Sales
16
22
Regarding SCD2:
So is there something I need to do on the repository so that BI Answers knows to switch between the two versions of the same Division at that particular time, such that I can make an Analysis such as this:
Month
Division
# Employees
% Change
May
Sales
15
-6%
June
Sales
15
0%
July
Sales
14
-7%
August
Sales
22
+57%
Instead of this:
Month
Division
# Employees
% Change
May
Sales
15
-10%
June
Sales
15
0%
July
Sales
2
14
-87%
0%
August
Sales
22
+57% -
M:N relationships within a dimension: Standard process vs. BI Data model
Hi,
I just completed a review of the u201CMulti-Dimensional Modeling with BIu201D from this link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84 and I have a quick question here:
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
i.e. my understanding is that, based on Standard Process it is NOT possible to place two characteristics in M:N relationships in the SAME dimension but with BI Data Model, this, the author points out is possible
u201Cdue to the usage of surrogate keys (DIM-IDs) in the dimension tables allowing the same material several times in the dimension tableu201D i.e. although material is the unique key of the dimension.
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
ThanksHi Amanda.......
In a dimension table, any number of semantically related dimension attributes are stored in a hierarchy (parent-child relationship as a 1:N relationship). If an M:N relationship exists between dimension attributes, they are normally stored in different dimension tables.
I checked the document.........
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
Here the first thing that I want to tell u is that............the diagram shown here is Classic Start Schema............since Extended Star Schema will never store Master data in Dimension tables.........it stores Masterdata in seperate Master data tables..........and nowadays..............Classic Star schema is obsolet.......Dimension table will only store Dimension id and SID......
Now the Standard process is that..........anything which is Describing a master data..........can be added as an Attribute of that master data.......
Suppose........Employee is the Masterdata.then Ph no can be one of the Attribute of this master data......
So this the Standard Process.........but this cannot be followed every time.........why........already explained.....
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
Bcoz ..........we use compounding Characteris tic to define the Master data uniquely.........and we load compounding Characteristic seoerately...which is independent of the Master data........ie......compounding Characteristic there is a seperate master data tables...........so ..........problem resolved......
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
For Compounding Characteristic............u hav to laod the Coumpoundede master data seperately..which is a overhead...........moreover while query execution......two tables will be accessd..which may result a performance issue.......Performance can be affected when compounded characteristics are used extensively, particularly when a large number of characteristics are included in a compounding. In most cases, the need to compound is discovered during data modeling.
Regards,
Debjani......... -
Hi,
New to SSAS cube in general.
I've build a bunch of reports in Excel using cubevalue functions.
How do i query an attribute within a dimension.
Eg. My Period dimension has Year->Half Year->Quarter-> Month
I want to know how you query which half year a month belongs to.
In SQL you'd just query select halfYear from dimDate where month = '201410'.
How's this done in a cube via excel and SSRS ?Hi,
If you have a user defined hierarchy created by using these attributes you can easily achieve this by using Ancestor member function. Take a look into the following MDX against Adventure Works.
WITH CALCULATED MEMBER [Measures].[Ancestor Quarter] AS ANCESTOR([Date].[Calendar].CURRENTMEMBER, [Date].[Calendar].[Calendar Quarter]).ITEM(0).MEMBER_NAME
CALCULATED MEMBER [Measures].[Ancestor Semester] AS ANCESTOR([Date].[Calendar].CURRENTMEMBER, [Date].[Calendar].[Calendar Semester]).ITEM(0).MEMBER_NAME
SELECT {[Measures].[Sales Amount], [Measures].[Ancestor Quarter], [Measures].[Ancestor Semester]} ON COLUMNS,
{DESCENDANTS([Date].[Calendar].[Calendar Year].&[2007],[Date].[Calendar].[Month]) } ON ROWS
FROM [Adventure Works]
This will query the months of year 2007 and at the same time it is returning to what Quarter and Semester each month belongs to. Here is the final result.
I hope this will give you an idea.
Best regards...
Chandima Lakmal Fonseka -
Calculation issue on attribute dimension
The issue that I'm facing with is as below. I have two pass calc on some of the measures in the outline. Since I'm not doing any calculation on the attribute dimension, when I drill down using this dimension it pops up an error message
"Two-pass calc skipped on member [X] in attribute calc"
Please advise on how to resolve this.
Thr formula has @CURRMBR. The DBAG says that If a member formula contains a run-time dependent function associated with an attribute member name, and the member with the formula is tagged as two-pass, calculation skips the member and issues a warning message.
It also says that Two-pass calculation member property is unavailable for attribute dimensions.
So does it mean that every two pass calc member is skipped?
I'm a bit confused.. how does it work?
Is there a resolution for my issue? Please confirm if there is a way to get this two pass calc done for the formula with @CURRMBR.
Thanks.
null
.Hello,
I will give it a try:
<< I assume you have the two-pass calc member on the accounts dimension and the associated dimension of the attribute dimension is not the accounts dimension either. >>
Attribute dimensios are calculated dynamically. They provide a different view on the members of the associated dimension which they belong to. There are 5 different calculation functions in the rollup of the members on the base dimension (sum, min, max, count, average).
So this is within the associated dimension (sparse) which is linked to the attribute dimension (virtual).
The accounts dimension is always involved in displaying figures. The attribute calculation e.g. sum is done last. So the dynamic calculations have to be done first. This message is likely a warning message that the value displayed is not the result of the two-pass calculation, but from the attribute calculation.
You might review the storage setting of the member. Often the @currmbr is also not necessary in the formula when considering the calculation order of the members.
Hope this helps a bit.
Regards,
Philip Hulsebosch
www.trexco.nl -
Obiee dimension hierarchy ?
what is purpose of od dimensional hierarchy in obiee ?
Dimension Hierarchy -
If you Introduce formal hierarchies into a business model it establishes levels for data groupings and calculations and provides paths for drilldown
Steps to Create a Dimension Hierarchy - >
Create a dimension object.
Add a parent-level object.
Add child-level objects.
Determine number of elements.
Specify level columns.
Create level keys.
Create a level-based measure.
Create additional level-based measures.
Create share measures.
Create rank measures.
Add measures to Presentation layer.
Test share and rank measures.
kp -
Hierarchies within a Dimension
Hello,
The BW Multidimensial modeling states there are 3 types of Hierarchies that BW employs.
Can anyone shed light on what " Hierarchies within a Dimension" does?
Thanks in advance.Hi
Any dimension's members may be organized based on parent-child relationships, typically where a parent member represents the consolidation of the members which are its children.
The result is a hierarchy, and the parent/child relationships are hierarchical relationships. For example, the Time dimension would contain the following hierarchy
Day Week Month Quarter Year.
Based on the business queries, such hierarchies would be formed in all dimensions.
Regards
Sai -
Display two members of same dimension hierarchy using mdx on 2 diff columns
Hi,
Is it possible to print the parent of a member that belongs to a certain level in the hierarchy. For this example, the Dimension hierarchy is a Variable hierarchy based on a Row Source, - BOM - Bill of Materials.
Let say there is a BOM hierarchy with 4 levels.
Finished Good - Comp1 - Comp2 - Comp3.
Then we want to display in the IOP report as follows.
Finished Good Supply Chain--These are the column headers
Finished Good1 Finished Good1
Comp1
Comp2
Finished Good2 Finished Good2
Comp3
Comp4
Comp3
Edited by: user596497 on Mar 16, 2011 1:39 PMThe question is wrong ...
MDX helps you to construct cross-product of indices for the underlying cube and then it tells the system to find whether there is any cell with that index, and if so, returns a value for that combination.
If you put two dimensions next to each other, what does it mean? There is no such combination in the underlying cube as each dimension is uniquely represented. We will throw an error as follows:
You cannot mix-up display semantics with the syntax/semantics of MDX.
"Can only cross join sets with different dimensions Statement"
An internal error occurred during the query execution phase. Please contact your administrator.
Query Definition
WITH SET [AnotherGeography] AS '{[Geography].DefaultMember}' SELECT {Fiscal.DefaultMember} ON COLUMNS, { CrossJoin( {[Geography].DefaultMember}, {[Customers].DefaultMember}, {[AnotherGeography]}, {Hierarchize(Descendants([Product].DefaultMember, [Product].[Product Family], SELF_AND_BEFORE), POST) }, { [Measures].[Target Revenue], [Measures].[Demand Plan Revenue], [Measures].[Market Share], [Measures].[Adjusted Demand Plan Quantity] }) } ON ROWS FROM [Demand]
Can only cross join sets with different dimensions Statement: WITH SET [AnotherGeography] AS '{[Geography].DefaultMember}' SELECT {Fiscal.DefaultMember} ON COLUMNS, { CrossJoin( {[Geography].DefaultMember}, {[Customers].DefaultMember}, {[AnotherGeography]}, {Hierarchize(Descendants([Product].DefaultMember, [Product].[Product Family], SELF_AND_BEFORE), POST) }, { [Measures].[Target Revenue], [Measures].[Demand Plan Revenue], [Measures].[Market Share], [Measures].[Adjusted Demand Plan Quantity] }) } ON ROWS FROM [Demand] -
Maintain the acct key and accruals/provisions in the calculation schema
Dear All,
I have a problem during invoice posting.
I create a new freight condition type & assigned it to the calculation schema. I also create a new account key & assigned to the calculation schema in accrual keys. Then done OBYC settings. During MIGO, its working fine. But when i post the Miro against po, giving an error msg., "Maintain the acct key and accruals/provisions in the calculation schema, Message no. M8434"
plz help me to solve this issue.Have you ticked the 'Acruals' in control data 2 in M/06 for this condition.
Regards,
Piyush -
Maintain the acct key and acurals/provisions in calculation schema-MIRO
Hi,
In PO we have maintained different delivery condition.
When we are doing MIRO we are getting error "maintain the acct key and acurals/provisions in calculation schema" for condition type YLBB and YLBE.
However we have checked condition type and calulation schema and found that acct key and accurals maintained.
YLB9 BivacInspec.fee/Quan
YLBB LPRC charges/Quant.
YLBC Port charges/Quant.
YLBE Clearing Charges/Qt.
Please suggest somesolution.
Thanks
AshokHi Ashok,
In M/08 check whether acct key and acurals/provisions in calculation schema" for condition type YLBB and YLBE are maintained or not.
Also if they are maintained there then check in M/06 for condition type YLBB and YLBE , whether accurals check box are checked or not...If not check and then try.
Cheers!!!
Utsav -
Conditions in Calculation Schema not reflecting in Purch Info Record
Hi,
We are using calculation procedure TAXIN.
We have maintained Calculation Schema & maintained required conditions.
When we checked for maintaining these conditions in Purchasing Info Record, (Transaction Code - ME11 / ME12), these conditions are not appearing in the info record. But, the conditions appearing in the info record are not same as those in the Calculation Schema.
Also, the conditions maintained in Info Record are not getting copied to Purchase Order (except Base Price P000).
What could be the reason behind this? How to correct the same?
Regards,
Prashant KolhatkarTax procedure condtions will not appear in the info record. for the conditon which is not reflecting in the PO, you may check in inforecord whether there is a check mark in condition record saved for approval; if so it is deleted
-
Calculation schema under pricing procedure
in pricing procedure under calculation schema what is <b>Condition formula for alternative calculation type</b> and <b>Alternative formula for condition base value</b>
what is the use of these functions?in this field u can creat ur own formuls to calculat base price or condition type value
this are called routine.
eg if u want to calculate the cond value on some logic the u can write ur logic in this routine and change the valuer of ur base price or Condution type
simple eq will be rounding up the values of condition type 17 is the routien u can use
hope this helps
Reward if useful -
PRICING PROCEDURE-CALCULATION SCHEMA
Dear All,
There are some queries regarding pricing procedure calculation schema.Please help me out:
1) What is the use of the "Requirement" column in calculation schema in real time scenario?
2) What is meant by "Alternative calculation type" and "Alternative base value" column?What is its use in real time scenario?
3) In the Print column if we place "X",it says "Printing at item level (previous procedure)".What does this actually means?
4) What is the use of "Accurals" and what effect does it have in the pricing procedure and pricing calculation?
For all the above queries some real time scenario example willbe highly appreciable.
Regards,
Indranil1) What is the use of the "Requirement" column in calculation schema in real time scenario?
Requirement
Use
If the requirement is fulfilled (SY-SUBRC = 0), then output
determination also takes into consideration output type or the access
sequence, for which the requirement has been specified.
Examples
A possible requirement would be, for example, that a difference shoul
be made between document currency and local currency .
Definition
Number of a subroutine (= form routine), that checks a requirement at a
specific time.
Use
The standard SAP system contains some standard routines for checking
requirements when copying. You can also define your own routines
according to the needs of your company.
Example
If you copy a quotation to a sales order, the system can check every
quotation item to ensure that the customer had not rejected them for any
reason.
2) What is meant by "Alternative calculation type" and "Alternative base value" column?What is its use in real time scenario?
If you are using any Formula to Derive the Condition Type then you can use Alternative formula to the formula in the standard system that
determines a condition.
Alternative formula for condition base value
Formula for determining the condition basis as an alternative to t
standard.
Example
An absolute header discount is, for example, distributed in the st
system according to the cumulative value of the items.
If the system, however, distributes the absolute header discount
according to volume, a header discount of $30 results in the follo
discounts:
Item Value Volume Discount
Stand. disc. Volume disc.
1 $1000 2 cbm $20 $10
2 $500 4 cbm $10 $20
3) In the Print column if we place "X",it says "Printing at item level (previous procedure)".What does this actually means?
If you Put 'X" , it will be shown in the Print Output..
Print ID for condition lines
Controls issue of condition lines when printing documents such as order
confirmations or invoices.
Use
In releases previous to 4.0, the following print indicators are
available :
o ' ' : Condition line is not printed
o 'X' : Condition line is printed at item level
o 'S' : Condition line is printed in totals block
The following standard logic is set out for these printing indicators: -
Accounting Key & Accruals Key in Calculation Schema (Pricing Procedure)
Hi Freinds,
I have a query regarding use of Accounting Key & accruals key in the Calculation Schema (Pricing Procedure).
What is the significance of Accounting key & accruals key in the calcuation schema? Which Accounting & Accruals keys have to be used for Gross price,Discount,Freight, tax etc in the Calculation schema? Please post your precious threads.
Thanks & Regards
Saeed Arifhi
AcyKy - Account Key/ Accrls - Accruals:
for SD module
u2022 The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
u2022 In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
o ERB Rebate sales deduct.
o ERF Freight revenue
o ERL Revenue
o ERS Sales deductions
o ERU Rebate accruals
u2022 For Ex.,
o For all Price condition types like PR00 etc. we assign ERL - Revenue.
o For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
o For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
o For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
u2022 This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
u2022 This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
Similarly for MM Module
Account keys are EIN, FR1, FR2, FR3, FRE, etc...
And in OBYC, we do necessary account determination for the same.
For e.g. Freight Posting in GR
Condition type FRA1, Accrual FR1 and in OBYC, assign Freight Clearing A/c to FR1
During GR;
Stock Account - Dr - 110 INR
GR/IR Clearing A/c - Cr - 100 INR
Freight Clearing A/c - Cr - 10 INR
transaction event key is the Key that identifies different types of G/L account.
The account key enables the system to post amounts to certain types of
revenue account. For example, the system can post freight charges
(generated by the freight pricing condition) to the relevant freight
revenue account.
use
To enable the system to find the relevant account for provisions (for
accrued delivery costs or miscellaneous provisions, for example), you
must assign a transaction/event (internal processing) key to each
condition type that is relevant to provisions in the step Define
Calculation Schema.
if u search on SDN or GOOGLE u will get many threads for this
hope it helps
regards
kunal -
Same Calculation Schema/Pricing Procedure- Same Vendor - Material & Service
Hi experts--
For subject matter(we are facing this issue in our organisation) I did my search and found the below threads but conversation did not provide what solution is to be implemented. Can someone help?
Currently we are using two unique vendor codes for tiding over our MM/SD problem even though vendor is same with same address,PAN & service tax registration.
We are a LSP and only recently went live on ECC 6.0 EnP4
warm regards--
A.VENKAT KRISHNAN
Same Calculation Schema/Pricing Procedure- Same Vendor - Material & Service
Posted: Aug 19, 2011 7:04 AM
Click to report abuse...
One vendor is providing service & material to the same Pur Org
Is it anyway to handle with only one vendor code for service & material procurement in same vendor account group with only one pricing procedure(calculation schema)?
Ramesh Babu Nag... [Active Contributor Silver: 500-1,499 points]
Posts: 535
Registered: 5/29/09
Forum Points: 1,380
Re: Same Calculation Schema/Pricing Procedure- Same Vendor - Material & Service
Posted: Aug 19, 2011 7:16 AM in response to: ARUL MURUGAN1 in response to: ARUL MURUGAN1
Yes, you can do it. There shouldn't be any issueHi,
Yes its possible.
you can use the same calculation schema for both so that with one vendor you can handle both material as well as service purchase.
Please revert if you face any difficulties.
Thanks & Regards,
Maybe you are looking for
-
Using Pages 5.5 How do I enable (view) file extensions? Thanks!
-
in abap objects v have a class cl_gui_alv_grid ,but can v use this class only when we are using a container,i mean in normal abap alv report we cannot use this class??? in normal alv report v use cl_salv_table ... can any1 pls provide me some in
-
My Imac 24 won't boot. Ran system hardware test - checks ok even after extended test. Thought I could reinstall os - but don't know how to do that. - osx disc1 is in machine that won't start
-
Hi all, Apologies if this isnt posted in the correct forum (but I wasnt able to find any mainstream graphic design forums, I know there is ultrashock but that's more flash based, if anyone could point me to some would be great.) Any how my question i
-
Hello Masters, What is the concept of AD-HOC in BW? What are AD-HOC queries and AD-HOC Hierarchies and when do we use them? I am bound to give points Thanks and Best wishes, I-BI