1Z0-531 · Question #7
What is the correct variance formula for an ASO database that recognizes Expense and Non- expense accounts?
The correct answer is E. IIF (IsUda([Measures.currentmember], "Expense"), [Budget]-[Actual], [Actual]-[Budget]). The following MDX formula is appropriate here: IIF ( IsUDA ([Measures].CurrentMember, "Expense"),([Budget] - [Actuals]),([Actuals] - [Budget])) Note #1: Member formula conversions for variance calculations can be accomplished with the help of User Defined Attributes (UDAs) that…
Question
What is the correct variance formula for an ASO database that recognizes Expense and Non- expense accounts?
Options
- A@Var(Actual, Budget);
- B@Var([Actual],[Budget])
- C[Actual] - [Budget]
- D[Budget] -[ Actual]
- EIIF (IsUda([Measures.currentmember], "Expense"), [Budget]-[Actual], [Actual]-[Budget])
How the community answered
(35 responses)- B3% (1)
- C3% (1)
- D11% (4)
- E83% (29)
Explanation
The following MDX formula is appropriate here: IIF ( IsUDA ([Measures].CurrentMember, "Expense"),([Budget] - [Actuals]),([Actuals] - [Budget])) Note #1: Member formula conversions for variance calculations can be accomplished with the help of User Defined Attributes (UDAs) that flag expense items. A combination of UDAs and conditional logic in ASO outlines provides the equivalent of the Expense Reporting functionality available in BSO outlines. Note #2: Note: The MultiDimensional eXpressions (MDX) language provides a specialized syntax for querying and manipulating the multidimensional data stored in OLAP cubes. While it is possible to translate some of these into traditional SQL, it would frequently require the synthesis of clumsy SQL expressions even for very simple MDX expressions. MDX has been embraced by a wide majority of OLAP vendors and has become the standard for OLAP systems. Scenario Variances Using Conditional Logic
Topics
Community Discussion
No community discussion yet for this question.