Project Hierarchy Display (SAP Library - Project Information System)

Project Hierarchy Display

The hierarchy display depends on:

Objects selected by the database
Project view selected
Constraints in the object display

This means that the hierarchy depends on various factors, such as authorizations, the database profile, user-defined selections, and filters set.

View from the Project Structure

If you use the hierarchy display as viewed from the project structure, note the following:

The network header assignment to the project definition or WBS element is not inherited by the activity or activity element. You must maintain the assignment specifically in the activities.
The network header assignment to a WBS element has priority over an assignment to a project definition.
Networks which are not assigned to a project definition selected for display in the information system are displayed at the highest level.
The hierarchy display for the WBS elements in the report is determined by the relationships between them.

If the commercial evaluation indicator is active in the database profile, note the following:

Only the network header or the activities and activity elements are displayed, depending on whether the network is header-assigned or activity assigned.
Material components are only displayed if they are part of valuated project stock. In this case, they are directly subordinate to assigned WBS elements.

Example: Project Information System Hierarchy

Effects of Authorizations

The project hierarchy is always displayed in its entirety. Objects for which you do not have authorization will be shown with only minimal data.

The following objects are displayed if you have no authorization:

Project definition
WBS element
Network header
Activity
Material component
Sales and distribution document

Project texts and production resources and tools, for example, are not displayed.

Effects of Dynamic Selections

If you use dynamic selections to exclude elements from the evaluation, the system does not select them from the database. Depending on the database profile, this may mean that the hierarchy is not displayed in full. The system automatically hides the levels with no elements. For example, if a superior WBS element is hidden, the subordinate level 3 WBS element appears in level 2. The costs of the hidden WBS element are not rolled up.

Note

Dynamic selections temporarily alter the appearance of the project hierarchy in the evaluations. They have no effect on the hierarchy itself.

Caution

The effect of the dynamic selections on object selection is largely dependent on the settings in the database profile.

Example: Dynamic Selections

Effects of Filters

Filters have no effect on database selection, but temporarily hide elements in the evaluation. Superior elements which do not satisfy the filter criteria can, at your option, be displayed with minimal data or not at all. There is no shifting of hierarchy levels.