General business objects settings
You can define the access level for every object in the universe. The access level specifies which objects the
user can work with. Every object can have an associated list of values. These values are used for prompts (see
the prompts section below). Restrictions on whether the object can be used in results/conditions/sort are
only relevant for the query definition itself. They have no effect on how the objects can be used in the initial
view editor or when executing an analysis application.
Attributes are interpreted in the same way as dimension objects. This allows you to use attributes regardless
of their dimensions in the resulting application.
The user can define projection functions for measures. These projection functions are also used by default
when navigating/aggregating in the OLAP-like result set after the initial fetch. The following projection
functions are supported:
Data is aggregated with average
Number of occurrences is calculated
Data is aggregated with maximum
Data is aggregated with minimum
No aggregation available; if data needs to be aggre
gated, no value is displayed
Data is aggregated with summation
Value help (list of values)
Value helps defined in the universe are only used in the prompt context in Design Studio. They have no effect
on other areas where member listing is performed.
Only keys are supported in the value help. For example, if you have defined an LOV based on a query or static
list with multiple columns in the business layer, only the key column is used for displaying the list of values.
Supported data types
Fields with the following data types are supported for usage in Design Studio:
Formats defined in the business layer for a business object are not supported. The formatting of objects
depends on the viewing locale and the data type exposed by the universe for example, date formats, numeric
formats. Timestamp data is displayed in the context of the user's timezone. For example, if you have defined a
year using numeric as the data type, the year might be displayed as 2.013 ("." is the thousands separator). To
avoid this, you can change the data type to String in your business layer.
Navigation path definitions are not interpreted.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Application Designer Guide: Designing Analysis Applications
Adding a Data Source