Skip to Content
avatar image
Former Member

Use of navigation attributes in APO DP

I am trying to clarify how navigation attributes compare with full planning characteristics in APO DP (V5).

In general, I know that navigation attributes are used for selection and navigation in APO DP.

But suppose I have a navigation attribute called 'product type' for planning characteristic 'product'. Isn't it also possible to forecast and make adjustments at the 'product type' level.

If the answer is yes, what is the real difference between the use of navigation attributes and planning characteristics?

Thanks for any help with this.

Bob Austin

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Feb 23, 2007 at 11:54 AM

    Performance wise, it might be faster to store in PLOBS, than the navigational attributes. Before you make your mind,

    Navigational attributes a very helpful if the attribute value changes. Eg. Product A is now classified as Type X, later if you wish to change to Type Y.

    1. If the Type is stored in PLOBS then you have run realignment.

    2. If it was a Navigational attribute to "Product", then master data population of the Info object will make the change.

    I think the most important point is to decide how this value relates to Others & your business case. Is the relation is one-to-one ?


    Thanks for rewarding points if this is helpful.

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 23, 2007 at 12:17 PM

    Planning Characteristics are used for planning and managing data (Edit, Save). Characteristic-based Aggregation / Disaggregation, background job running is possible at this level. Aggregates can be built only for Planning Characteristics.

    Notes are attached at Planning Characetristic level. Statistical Forecast should be run at Planning Characteristic level.

    Navigational attributes can effectively be used for Selection Profiles only and displaying data. It should not be used for managing the data since aggregation and disaggregation may not work correctly. Fixing functionality does not work with navigational attributes.

    So to answer your question - if you plan to manage forecast data at product type level then it should be a planning characteristic and not a navigational attribute.



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 25, 2007 at 03:44 AM

    You do not see difference in Attribute and characteristics in the interactive planning screen. So you should be able to create selections and do general navigation

    just a little more detail on the difference between nav attributes and planning char

    But creating forecast profiles might be a problem- Selections with navigational attributes do not create forecast assignment table entries. As of SCM4.1, the attribute information can be stripped out of the selection via BADI, allowing an assignment entry to be created.

    Maintenance of CVCs also have to be done differently. Navigational attributes are not same as CVCs. Instead they point at the value of another characteristic. We create master data for nav attrib in the Admin workbench. Also If you plan to use navigational attributes on standard characteristics, say in 9AMATNR, then you could have issues in SNP since SNP does not support Nav attrib

    Also realignment of Navigational attributes is not a standard process but can be done.

    Add comment
    10|10000 characters needed characters exceeded