Administer > Administer ITBA > Content Administrator > SAP BusinessObjects Enterprise Contexts (Universes)

SAP BusinessObjects Enterprise Contexts (Universes)

A KPI or Metric Context (universe) represents a global business facet related to the aspect of business the KPI or Metric represents. For example, the % of Assets in Maintenance KPI represents one aspect of the AssetManagement universe.

You can add a Context to the Studio and the BA engine and attach KPIs or Metrics to the new Context in the Studio.

ClosedAdd a Context to Studio using Context Designer

You can create new Contexts, using Context Designer. For details, see Semantic Layer - Context Designer

If you have SAP BusinessObjects Enterprise installed, you can also create Contexts (Universes) using BOE. Once you are done you must add these Contexts to the Studio.

ClosedAdd a Context to Studio using BO

  1. Make sure you have modeled the data structure in your database.
  2. Add the universe using the BO Designer according to the Universe Creation Guidelines. For details, see Universe Creation Guidelines.
  3. Export the universe to the BA directory in your BO CMS (Central Management Server) using the BO Designer .
  4. To load the universe to the Studio library you can do one of the following:
    • Run the JMX reload metadata.
      1. Make sure you have JDK installed.
      2. Run jconsole in the Start menu.
      3. In the window that opens, select the Remote Process option, enter <host_name>:<port_number>  and click Connect.
      4. After the application completes its loading, click the MBeans tab.
      5. Click com.hp.btoa.studio.jmx.
      6. Click loadMetaData.
    • Note that if you do not click loadMetaData, the change will be performed by an automatic update after 24 hours or 7 days depending on your configuration. You can modify the configuration using the Meta Data reload rate (Days) parameter in the BA Settings section of the ADMIN Tab. For details, see Settings - BA Settings.
  5. You can now design active or template entities, create the formulas and filters for the KPIs or Metrics, and more.

ClosedUniverse Creation Guidelines

This section explains how you can create Universes that can be used by the IT Business Analytics Studio and the BA Engine.

ClosedGuidelines
  1. Folders represent the name of the entity that is presented.
  2. Classes in the directory represent the attributes of that entity.
  3. Classes should be of type Date, String, or Numeric.
  4. Entities (represented by directories) in the same universe must have a relationship between them.
  5. Hierarchical relationships should be flattened to attributes (Level1, Level2, …). These relationships can be defined in a joined table.
ClosedLimitations
  1. No current support for directories within directories or other hierarchies.
  2. Ensure that there aren’t multiple joins between entities represented in the Universe (This is a Universe limitation). Use aliases to copy.
  3. Folder names should be unique.
  4. Count, in a formula, can only be performed on Numeric and String fields.
  5. Conditions on objects not supported.
  6. Details on objects not supported.
  7. Do not put mappings in the universe – where fields are translated from the value in the database to the value that the universe returns.
ClosedField Types
  • Dimensions
    • Fields that can be broken down per KPIs or Metrics should be marked as Dimensions – see the top mark in the figure below.
    • If the field can only have a limited set of values, then turn on the List of Values field below – see the second mark in the figure below. The studio will only show the first 100 values.

    • Warning - this should only be turned on for fields that have a small set of values – all the values will be loaded into memory in the studio.

  • Measures

    • Fields that are only used as measures in KPI or Metric formulas should be marked as Measures. Make sure to configure as in figure below.

Send Help Center feedback