Create a Dimension to Categorize Data
Select a Semantic Usage of Dimension to indicate that your entity contains attributes that can be used to analyze and categorize measures defined in other entities.
Context
-
Geography - Region, Country, State, City
-
Product - Range, Category, Product
-
Customer
-
Organization - Company, Department, Organization Unit
-
Time - Year, Quarter, Month, Day
Procedure
- In the table editor or view editor output node side panel, complete the General section as follows:
Property
Description
Business Name
Enter a descriptive name to help users identify the object. This name can be changed at any time.
Technical Name
Displays the name used in scripts and code, synchronized by default with the Business Name.
To override the default technical name, enter a new one in the field. Technical names can contain only alphanumeric characters and underscores.Package
Select the package to which the object belongs.
Packages are used to group related objects in order to facilitate their transport between tenants. For more information, see Creating Packages to Export.Release State
[views only] Specifies whether the object is released, providing modelers and consumers with confidence that it will remain available in its current form for the foreseeable future.
For more information, see Releasing Stable Views for Consumption.
Semantic Usage
Select Dimension.
Alternatively, click (Generate)
Generate Semantics
to request SAP Datasphere to suggest a Semantic Usage for your entity, identify the uses of your columns, and apply appropriate semantic types to them (see Generate Semantic Information).Dimension Type
Select whether your dimension is Standard or Fiscal Time.
For Fiscal Time dimensions, see Create a Fiscal Time Dimension.
Expose for Consumption
[views only] Enable this option to make the view available for consumption outside SAP Datasphere via OData or ODBC/JDBC.
This option is not required if you want to expose your data through an analytic model (see Creating an Analytic Model). For an overview about making your data accessible outside SAP Datasphere, see Exposing Data For Consumption.
Run in Analytical Mode
[views only] Enable this option to send the USE_OLAP_PLAN hint to the SQL optimizer.
This may improve view performance, particularly if a union is performed. It is only available if Expose for Consumption is enabled.
For more information, see HINT Details in the SAP HANA Cloud, SAP HANA Database SQL Reference Guide.
Allow Data Transport
[local tables only] [SAP Business Data Cloud formation tenants only] Allow users to include the table data in a package when transporting the table.
This feature is intended to allow you to transport limited quantities of data for static and slowly changing dimensions, text entities, and relational datasets. If the local table is created by the import (or if it already exists but is empty), the transported data will be imported to it.
Storage
[local tables only] [read-only] Displays the table storage.
Status
[read-only] Displays the deployment and error status of the object.
For more information, see Saving and Deploying Objects.
Deployed On
[read-only] Displays the date and time of the last deployment.
Data Validation Status
[views only] Displays the status of the last data validation.
Click the button to open the Data Validation panel (see Validating View Data).
Validated On
[views only] [read-only] Displays the date and time of the last data validation.
- Specify your attributes (see Specify Attributes as Keys, Units, and Other Characteristics).
- Set attributes as keys to indicate that the data they contain can uniquely identify records.
To set an attribute as a key column, select the checkbox in the Key column or hover over the attribute in the side panel and click (Menu)
Set as Key
. - [optional] Create associations to point to other entities (see Create an Association to Define a Semantic Relationship Between Entities).
A Dimension can point to a:
-
Dimension - One attribute in the (source) Dimension must be mapped to each (target) Dimension key column so that all target key columns are mapped.
-
Text Entity - One attribute in the (source) Dimension must be mapped to each (target) Text Entity identifier key column.
-
Hierarchy - Each key attribute in the (source) Dimension must be mapped to a (target) Hierarchy child attribute key column.
-
- Complete or consult other sections as appropriate:
-
Input Parameters - Create input parameters to require the user to enter a value for use in calculated column, filter, and aggregation nodes (see Create an Input Parameter in a Graphical View).
-
Data Persistence - Persist the view data to improve performance (see Persist Data in a Graphical or SQL View).
-
Associations - Create associations to other entities (see Create an Association to Define a Semantic Relationship Between Entities).
-
Data Access Controls - Add data access controls to apply row-based security and control access to individual rows based on various criteria (see Securing Data with Data Access Controls).
-
Business Purpose - Provide a description, purpose, contacts, and tags to help other users understand your entity.
-
Dependent Objects - If your entity is used as a source or association target for other entities, then they are listed here (see Review the Objects That Depend on Your Table or View).
-
- Click (Save)
Save
to save your entity or click (Deploy) to save and deploy it immediately.
For more information, see Saving and Deploying Objects.