!--a11y-->
Definition
Processing screen that presents detail data from the engineering environment that is specific to one iPPE object. This page has an HTML template with HTMLBusiness statements and HTML code.
Use
The structure of the page depends on the object type. Object-specific pages are generated for the following object types:
On each object-specific page, you can use links to display additional data from the engineering environment, and execute object-specific processing functions.
Structure
The following overview shows how an object-specific page is structured.
|
Page Area |
Use |
|
Header graphic Navigation history |
User-specific Settings are defined for the page areas.The historic navigation path contains the number of path items defined in these settings. |
|
Toolbar |
You can call the following functions: access, mail, settings, help, and exit. |
|
Navigation area: |
Views structure the wide range of engineering information, and enable clear presentation of data. The list of views is determined dynamically for each iPPE object. |
|
Views that are displayedfor all iPPE objects |
Contains general information from the master record of the object. Lists the documents that are linked to the selected iPPE object. Lists the work items that exist for the selected iPPE object. |
|
Views that are displayed for specific objects |
Lists the variants for a structure node. Lists the concepts for a variant. |
|
Views that are determined dynamically for an object |
View <Text for relationship type (n)> These relationship types form the basis for assignments (relationship assignment) and relationships within a hierarchical structure relationship is part of) between iPPE objects. The product designer reads relationships for iPPE objects that are defined for the following iPPE application object types:
If assignments exist (relationship assignment) for a selected iPPE object (source object) to other objects (target objects), these relationships are displayed in one or more views. In the settings for the Web user interface, you define whether all relationships are displayed on one view (assignments view), or whether each is displayed on a separate page.
Example: Requirement view (4) In Customizing, the iPPE object types structure node (S_ST) and requirement (A_S_GEN) exist as copies of the engineering node (S_GEN). You define the relationship type requirements (relationship assignment) for these objects. If you display a structure node in the product designer, and assignments to a requirement node exist, the requirements view is also displayed. The list contains four engineering nodes for requirements.
The hierarchical relationships (relationship type is part of) are always display in the navigation area structure and the structure view. |
|
Detail data for views |
Header data on each detail screen of a view shows information on the selected iPPE object and the assigned product class. If a change status exists, the change number is presented as a link. You can use the link to display change data.Below the header data, the detail data of a view is presented (for example, variants). These overviews contain many links to further details (such as the data of the material that is assigned to the variant). |
|
Navigation area: |
Structure information helps you to find your way in complex product hierarchies.
|
Integration
On the object-specific pages, you can evaluate engineering data and execute object-specific processing functions:
Displaying Engineering Data Editing Engineering Data