SAP HANA Developer Guide - Get a Free Blog

5. Optional Step: To filter and view the table data in the modeled view, which is relevant to a specific client as
specified in the table fields, such as, MANDT or CLIENT, at runtime perform the following:
1. Select the Semantics node, in the Properties panel edit the Default Client property.
Note: The default value for the property is the one that is specified as a preference. At runtime, if the
property is set to Dynamic then, the value set for the Session Client property is used to filter table
data. The Session Client property is set while creating a user.
Note: You can choose to create hierarchies in order to define relationships between attributes.
Note:
You can choose to associate an attribute with another attribute, which describes it in detail. For
example, when reporting via Label Mapping (also known as Description Mapping), you can associate
Region_ID with Region_Text.
Before SP05, you could associate an attribute with another attribute in a model. In the runtime
object an .description column is generated and is shown during data preview. Now, from
SP05 onwards the behavior is as follows:
○ For an attribute (CUSTOMER) you can now maintain label mapping by selecting another
attribute (TEXT) from the same model as "Label Column" in the Semantics node. The result is
"TEXT" displaying as the label column in data preview. Note that the CUSTOMER.description
column is not generated and is not shown in data preview anymore.
○ If you have created an object using the old editor (which supported the old style of description
mapping) and try to open it using the new editor you will see a new column
CUSTOMER.description (as an attribute) which is hidden and disabled because this column
cannot be used in other places such as parameter/variable, calculated column, restricted
column and so on. You cannot maintain properties for this attribute for example, description.
CUSTOMER.description displays in the data preview as long as you do not change it in the
editor. You can change its name. After changing the name you can maintain its properties and
use it like other attributes.
6. Activate the view using one of the following options in the toolbar:
○ Save and Activate - to activate the current view and redeploy the affected objects if an active version of
the affected object exists. Otherwise only current view gets activated.
○ Save and Activate All - to activate the current view along with the required and affected objects.
Note: You can also activate the current view by selecting the view in the Navigator panel and choosing
Activate in the context menu.
You can find the activated model in the related package. If you want to modify this model, from the context menu,
choose Open and make the necessary changes.
108
Restriction: The behavior of attribute views with the new editor is as follows:
● When an object (a table of an attribute view) is removed and added again in an attribute view in order
to reflect the recently modified columns with its data type, it reflects the previous state of the columns
alone. For more information, see SAP Note 1783668.
P U B L I C
© 2012 SAP AG. All rights reserved.
SAP HANA Developer Guide
Setting Up the Analytic Model