Skip to end of metadata
Go to start of metadata


Introduce Object Navigator.


Object Navigator feature in PLM 7.01 provides:

- Navigation to other relevant objects via same screen.

- Relevant information which is easy to access.

- Scope for enhancement.

- Center for User Interaction.


-          In Customizing for the object navigator, you define Object Types, Relations between the object types, and Object-Type-Dependent Settings.
-          You define which relations are displayed in each view of an object type in the object navigator. |
-          You define whether certain attributes are displayed in heterogeneous views (that is, views that contain different object types).
-          You can also define new object types (both SAP and non-SAP object types) and relations in Customizing

The Customizing of the object navigator can be found under:   
Transaction SPRO è Cross-Application Components è Cross-Application Components è Processes and Tools for Enterprise Applications è Object Navigator è Make Settings for Object



Transaction SPRO è Logistics - General è Product Lifecycle Management (PLM) è PLM Web User Interface è Settings for Object Navigator Make Settings for Object Navigator

 Object Types:


In the Customizing the relation between the Object type and the implement class is defined. e.g. the Object PLM_BOMMAT (Material BOM) is implemented in the class /PLMI/CL_NAVO_MBOM.

The implemented classes can be found in the package BS_PLM_NAV.


Relations: In this table, you create relations between object types, which 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.


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.

View Variants:

In this table, you define variants of the views that you defined in the Views table. For example there can be two different roles in a company. Some users are only allowed to view materials and other users are allowed to view material and material BOM's.


Relations per View Variant

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 (i.e. one child object) must be set to Display Always.


Interesting functionmodules that read customizing from table /PLMB/NAV_TPVREL: FUNCTION /plmb/nav_relation_read FUNCTION /NAV_TP_VARIANT_READ


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.


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.


MPN (Manufacturer Part Number, Object Navigator 7.01)

While Manufacturing a product, the components can be manufactured by the firm itself or can be procured from vendors.

In SAP ERP, this kind of information can be stored in different ways.

  • The most common way is to use the Approved Manufacturer Parts List (AMPL, transactions MP01, MP02), related to an existing internal material with one or many manufacturer part numbers (type HERS materials) defined for it.
  • Other options exist in ERP Purchasing to indicate which manufacturer parts can be sourced at which point in time.

           -  These are the Purchasing Info Record (PIR, transactions ME11-ME13)

           -  Source List (SL, ME01-ME03).

  • Purchasing view  : Another option is to directly maintain a manufacturer part and a manufacturer in the maintenance of the internal material (which is only applicable if there is a 1:1 relationship between them). 

Object Navigator screen for Material and MBOM provides a  consolidated view of the vendors

            In a tab called 'Manufacturer Parts Number' .

            A new customizing table /PLMI/MPN_CUST (Switchable ) is created to enable which information categories will be set .Depending on the customizing, the MPN data is fetched from the corresponding sources. By default PV, AMPL & MPN information categories will be set to active .   

Where can I find the customizing?

UI definition in Customizing:


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.  

Define MPN Information Categories




In this Customizing activity, you specify the MPN information categories that should be active. These information categories are used to generate the manufacturer parts list on the Manufacturer Parts tab page for materials and bills of material (BOM). You use the following MPN information categories:

  • Approved Manufacturer Parts List
  • MPN Material
  • Purchasing Info Record
  • Source List

Depending on the MPN information categories used in your enterprise, you can activate any one or none or all of the above. Note that the AMPL is dependent on MPN; both information categories must be active simultaneously.



MPN relations

Defined Set of Object  Relations for PLM Object type MPN are:

Ø  Object Type Class for MPN : /PLMI/CL_NAVO_MPN

Ø  Relation Class for Material : /PLMI/CL_NAVR_MAT2MPN

Ø  Relation Class for MBOM : /PLMI/CL_NAVR_MBOM2MPN


        Calls /PLMI/CL_NAVO_MPN-> get_mpn_data_all().

 The same method is used in /PLMI/CL_NAVR_MAT2MPN ~EXPLODE  also calls the same BO method

Ø   /PLMI/CL_NAVR_MBOM2MPN~Single_explosion

                        1.  /plmi/cl_mbom_bo=>get_rel_mbom2item

                        2.  /plmi/cl_mbom_bo=>get_item_details

                        3. /PLMI/CL_NAVO_MPN-> get_mpn_data_all().

Related Content

Related Documents

Related SAP Notes/KBAs

  • No labels