Default perspective and domain publishing

When no perspective is defined manually by the customer, the default perspective is created automatically. This ensures that all standard entities are associated with the perspective, preserving consistency and usability in Business Modeling.

Benefits of default perspectives

Default perspectives ensure that standard entities remain accessible through the perspective, even if none have been manually configured.

Default perspectives reduce manual configuration and potential errors by automatically assigning the default structure.

Features and functionalities

The default perspective is automatically created if none exist.

All standard entities are linked to the default perspective.

A domain cube is created and published for the linked entities, perspectives, and standard configuration set. Within the domain cube, perspectives can be assigned to specific contexts such as the standard configuration set and entities. The contexts serve as the driver dimensions for selecting perspectives in standard reports. A context is a combination of elements from the domain cube's context dimensions. Context dimensions do not need to be part of base cubes because they are used only for filtering.

The default perspective includes all required dimension exclusions as specified in the system requirements.

Process for automatic creation of the default perspective

These steps describe the process of how the default perspective is created:

  1. The presence of defined perspectives is verified.
  2. If no perspectives exist, the default perspective is created.
  3. A domain cube is generated for all entities of a standard type.
  4. Each relevant entity is mapped to the default perspective.
  5. The default perspective is configured with the required dimension exclusions as defined in the BusinessObjectConfiguration table.

What happens in relational modeling?

In relational modeling, four integration tables store data related to perspectives:

  • BusinessObjectConfiguration table. Stores configuration details for business objects.
  • Perspective table. Contains information about each perspective.
  • PerspectiveBusinessObject table. Maps perspectives to business objects.
  • PerspectiveEntityMapping table. Defines entity mappings within a perspective.

To maintain integration tables, go to the EPM Administration and select Dashboard > Data Integrations > Relational Modeling > EPM Integration > General.

The logic treats the dEPM_Perspective table as if it contained a single entry with "Default" as the ID.

The dEPM_PerspectiveEntityMapping table is populated for each standard entity and associates them with the default perspective.

All dimension exclusions are applied according to the requirements that are referenced in the dEPM_BusinessObjectConfiguration table.