Navigation attributes in APO DP

[Former Member]

I am using APO DP V5.

I have a planning characteristics of product and customer. I also have a characteristic of 'product group'. I am trying to clarify the <u>real difference</u> between modelling this characteristic as a planning characteristic or as a navigation attribute of product.

Based on my testing, using product group as a navigation attribute, I can select by product group and apply fixing and disaggregation.

So, what is the 'added value' of modelling 'product group' as a planning characteristics?

Any feedback appreciated.

Thanks, Bob Austin

[Former Member · Accepted solution]

Hello Group APO,

Performance wise, modeling product group as characteristic will mean less database joins during execution. Modeling it as navigational attribute will mean having to execute extra database join during execution. You can decide if the extra join will impact you depending on the number of CVCs you expect to have.

[Former Member]

To quote OSS note 413526

When defining a planning area you have the option of using either basic

characteristics or navigation attributes. With regard to the design the

following aspects should be considered:

• Navigation attributes:

===========================================================

• The use of navigation attributes adversely affects performance during

data selection and during navigation in the interactive planning. The

number of used navigation attributes is important and not the different

specifications of a navigation attribute.

• It is very easy to realign the planning objects since only the master

record table of the affected InfoObject has to be changed.

• Navigation attributes can not be used as a characteristic during the

definition of a fixed aggregate.

• During the disaggregation a navigation attribute can never represent the

lowest planning level.

• Navigation attributes can not be used in the promotion planning, in

other words an 'assign object' is not possible for navigation attributes.

• Basic characteristics:

===========================================================

• In comparison with navigation attributes, the exclusive use of basic

characteristics improves the performance.

• It is possible to realign the planning objects, but this is more

complicated.

• Basic characteristics can be used during the definition of aggregates.

Both navigation attributes and basic characteristics can be used during the

data extraction.

It is therefore not possible to give a clear-cut recommendation for or

against navigation attributes.

[Former Member]

Hi Bob

As Emmaneul mentioned, the performance is a bit slow on attributes because there are two table joins that need to be read. Product group to product will be a one to many relation so it should not be much of an issue and your CVC in the MPOS will not be greatly reduced anyhow. So there is no great advantage spacewise either. So you loose performance and dont gain in saving table size

But, It's easier to maintain navigational attirbutes.

You can select using navigational attributes in interactive planning as you do with regular characteristics

You can have problems if you plan to use forecast profiles with the attributes or if you want to do a realignment.

I also think there is some issue with using attributes as a characteristic in release to SNP