Creating a Calculated Measure - Teradata Schema Workbench

Teradata Schema Workbench User Guide

Product
Teradata Schema Workbench
Release Number
16.20
16.10
15.10
Published
June 2015
Language
English (United States)
Last Update
2018-05-25
dita:mapPath
gvf1512702977003.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-4106
Product Category
Teradata Tools and Utilities
With two normal stored measures called Product Cost and Product Selling Price, you could create a third measure called Product Profit. This measure would be derived using the following formula: Product Profit = Product Selling Price - Product Cost.
  1. From Schema Tree View, right-click a cube, and click New Calculated Measure.


    The Schema Element Properties View appears in the right pane.

  2. In the Name box, type a name for the new calculated measure.
  3. Click the Caption box. The caption automatically fills with the same name as the cube.

    The caption is a name that is displayed and can be localized to different languages in the BI client application. See Cube Schema Localization.



  4. [Optional] To prevent visibility to BI client applications, clear the Visible check box.
  5. Type the MDX query language formula in the MDX Expression box and click Validate Expression to validate the MDX expression. See MDX Expressions in Calculations.

    Using fully qualified, bracket-delimited identifier names in your MDX is strongly recommended. For a list of supported MDX functions, methods and operators, see Supported MDX Functions and Operators.

    If an MDX validation error occurs, see MDX Validation Errors.

  6. Type a format string or select a format string from the Format String menu. (See Format Strings.)
  7. Type a number in the Solve Order box. A cube can have calculated measures and other calculations such as calculated members. The value of a calculated measure or member’s Solve Order is used for disambiguating intersecting calculations. For example, calculations intersect when one calculation is on rows and the other is on columns. The specific Solve Order value does not matter. What matters is how the Solve Order value of one calculation compares to another.

    The Solve Order value must be an integer greater than or equal to zero. Calculated measures are evaluated in order starting with the lowest Solve Order value first, continuing on with the next lowest value

    Find useful information by searching for solve order in the Microsoft Developer Network Library at http://msdn.microsoft.com/library/.

    Unless you are sure a non-default solve order is required, leave the value at zero.

You can organize calculated measures by specifying display folders. After you define the folder in Teradata Schema Workbench and publish the schema, the calculated measures will be grouped together when accessed in applications such as Excel.