SAP ABAP IMG Activity /PLMB/VC_NAV (Make Settings for Object Navigator)
Hierarchy
☛ SAP_BS_FND (Software Component) SAP Business Suite Foundation
   ⤷ CA-EPT-NAV (Application Component) Object Navigator
     ⤷ /PLMB/BA_NAV (Package) Base: PLM Object Navigator
IMG Activity
ID /PLMB/VC_NAV Make Settings for Object Navigator  
Transaction Code /PLMB/38000076   (empty) 
Created on 20080515    
Customizing Attributes /PLMB/VC_NAV   Make Settings for Object Navigator 
Customizing Activity /PLMB/VC_NAV   Make Settings for Object Navigator 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /PLMB/VC_NAV    

Use

In this Customizing activity, you make settings for the object types that you can display on the object navigator screen, as well as which views (which appear as tab pages on the user interface) you can see for each central object type and how the relations between objects in these views are displayed.

In this activity, you can make the following settings:

  • Object Types

    In this table you specify which object types the object navigator can display. You specify object types that you want to use as central objects and object types that you want to display in the views within the object navigator. For each object type you must specify a corresponding class.

    Note:

    • The classes you can enter here must contain the interface class /PLMB/IF_NAVO.
    • The objects types that you can enter here must exist in the table /PLMB/GOS_OTYPE.
    • If you specify an object type that you have defined yourself, you must have also created a class to use with this object type.
  • Views

    In this table, you specify which views are available to use in the object navigator. You must specify these views before you can enter them in the View Layout table below.

  • View Layout

    In this table, you specify for a particular object type, which views appear on the UI when the central object loaded in the object navigator is of this object type. (You define the possible view in the Views table.) You can specify a default view - that is the view that is in the foreground when the user loads an object of this type in the object navigator. All object types also have a General view, which you do not need to specify in this table.

    Note that if you do not select a default view, the General view is used as the default. If a user is assigned to a role that does not have authorization to display a particular view variant, this view does not appear on the UI for the user. Furthermore, if such a view is set as the default, the General view is used as the default view for the user role instead.

  • Relations

    In this table, you create relations between object types that you can display on the views in the object navigator screen. For each relation, you must specify a corresponding class. The classes that you can enter here must contain the interface class /PLMB/IF_NAVR.

    For each relation that you create in this table, you must specify the parent object type, which is defined in the class. Note that if you specify a relation containing object types that you have defined yourself, you must have also created a class for this relation. Each relation entry in this table is unidirectional.

    You can only specify objects here that you have entered in the Object Types table in this Customizing activity.

  • View Variants

    In this table, you define variants of the views that you defined in the Views table. Note that, in this table, you do not assign the view variants to the views. Note that the descriptions you provide here are not used on the object navigator screen. The description of the view itself (which you assign in the View Variant Ranking table) is used.

  • Relations per View

    In this table, you specify which relations you want to display or hide in a particular view variant. If a relation is a 1:n relation, you must make a separate entry for each child object type of the relation. Note that at least one entry (that is, one child object) must be set to Display Always.

  • View Variant Ranking

    In this table, you assign view variants to views. Furthermore, for each view-view variant pair, you specify a ranking.

    In the authorization object PLM_LAYOUT for a particular role, you specify which view variants a user with that role is able to see in the object navigator. If a user is assigned to multiple roles that use different variants, the system displays the view variant for an object that has the highest ranking (1=highest) in this table. You can make use of this, such that the highest ranked view variants are the most detailed in terms of relations, so that a user with authorization in one of his or her roles always sees the most detailed view variant allowed for him or her.

  • Columns of Heterogeneous List

    If a view contains a heterogeneous list of objects, you can specify that certain attributes are displayed for a particular object type, if that object type appears in a heterogeneous list. The attributes that you can specify here are contained in the attribute structure that belongs to the object type

  • Preferred Order of Columns of a Heterogeneous List

    You can specify the order in which attributes of objects in a heterogeneous list appear. In this table, you assign a position for the attributes of all object types that you have entered in the Columns of Heterogeneous List appear.

  • Parameters not Considered for Personalization

    You can specify which parameters are not to be considered in the personalization of Navigator Settings for Object Navigator. To specify parameters, enter their data elements. Personalization in Navigator Settings is then no longer possible for those parameters.

    For example, it is not necessary to personalize time-dependent parameters such as Valid From, since the user wants to see the current data of an object.

Requirements

  • The object types you want to use are defined in the table /PLMB/GOS_OTYPE (see Define Generic Object Types (view /PLMB/V_GOS_OTYP)).
  • For each object type you want to use, a corresponding class exists, which contains the interface class /PLMB/IF_NAVO.
  • For each relation you want to use, a corresponding class exists, which contains interface class /PLMB/IF_NAVR.

Standard settings

Activities

After you have made settings in this Customizing activity, you must assign view variants to roles for your users in Role Maintenance.

Example

You want to make settings for when an object of type "Material" is the central object. For this, you want to provide a view (Bill of Materials). In the bill of materials view, you want the user to be able to see the bill of materials in which this material is used, and furthermore, depending on the user role, be able to drill down to the documents that are related to the bills of materials. You want two variants of the view: The first one only shows the BOMs for a material (restricted view variant), the second also shows the documents for the BOM (complete view variant). You have 2 users, the first is assigned to a role that can only see the restricted view, the second user is assigned to two roles - one is authorized to see the restricted view variant, the other is authorized to see the complete view variant. You want this user to always see the complete view variant.

In the complete view variant, you want the Created On and Created By fields to be displayed for documents. Furthermore, you want the Created On field to appear before the Created By field

Prerequisites

  • The following global objects and corresponding classes exist:

Object Type    Class

MAT    MAT_CLASS

BOM    BOM_CLASS

DOC    DOC_CLASS

  • The following relation classes exist:

Class    Parent Object Type    Child Object Type

MATBOM_CLASS    MAT    BOM

BOMDOC_CLASS    BOM    DOC

  • The attribute structure within the class for the object type DOC contains the following data elements:

Name    Short Description

CREATEON    Created On

CREATEBY    Created By

Settings:

  • In the Object Types table, you make the following entries:

Object Type    Description of Object Type    Class

MAT    Material    MAT_CLASS

BOM    Bill of Material    BOM_CLASS

DOC    Document    DOC_CLASS

  • In the Relations table, you specify the relations that you want to use:

Relation    Description    Class    Parent Object

MAT_TO_BOM    BOMs for Material    MATBOM_CLASS    MAT

BOM_TO_DOC    Documents for BOM    BOMDOC_CLASS    BOM

  • In the Views table, you make the following entry:

View    Description

BOM_VIEW    Bill of Materials

  • In the View Layout table for the object MAT:
    • Specify the view BOM_VIEW
    • Set it as default.

  • In the View Variants table, you specify two variants that you will later&
Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG /PLMB/VC_NAV 0 BSD0000011 Processes and Tools for Enterprise Applications 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
/PLMB/VC_NAV C - View cluster SM34  
History
Last changed by/on SAP  20080731 
SAP Release Created in 701