Use of navigation attributes in APO DP

[Former Member]

I am using APO DP version 5.

In general I am forecasting at the level of product at customer.

I have already modelled navigation attributes for the individual InfoObjects of product and customer.

But I also want to model a navigation attribute at the <u>combined</u> 'product at customer' level (example would be the 'status' of the combination, which could be 'live' or 'not live').

Any recommendations about how to configure a navigation attribute at this combined level?

Thanks, Bob Austin

[Former Member · Accepted solution]

I have same scenario, what you can do is use the existing avilable filed which has navigational attribute already defined (but field should be ideal) then update the generic indicator as ZZZ and then use that as your navigational attribute in the Livechace.

hope this will help you.

[Former Member · Accepted solution]

Thanks for your prompt answer.

But I do not fully understand what you are describing.

Can you send any relevant screenshots of configuration to bob.austin@atosorigin.com?

Thanks...

[Former Member · Accepted solution]

Hi Bob,

I have the same question: how to define navigational attributes of combined info-objects?

If you have a solution or some screenshots, please let me know. (j.vroemen@pyramid.nl)

thanks in advance

Jean

[Irmi_Kuntze · Accepted solution]

In BW there exist something called "Compounding", which unfortunately does not work with DP.

Therefore I usually introduce a new characterstic which in your case I would call "part@customer" which would be both concatenated.

E.g. if you part is "1234" and your customer is "ABC", then the value for that would be "1234@ABC".

This characteristic then can have own attributes.

When you update your data from BW, you just need a little update routine that concatenates both values.

In the DP planning books I would hide the characteristic and only show the attributes.

Disatvantage: You have more effort if you need to do stuff like realignment.

Hope that helps

Irmhild

[Former Member · Accepted solution]

Irmhild,

Thanks for this.

If I understand you correctly, you are proposing the following:

- have an <u>additional</u> planning characteristic 'product@customer' in the planning object structure

- for this additional planning characteristic, have various required navigational attributes (eg 'status' of the product at customer)

- maintain the master data for the additional planning characteristic

- in interactive DP, can then select/navigate by the navigational attributes

Please confirm.

Thanks, Bob.

[Irmi_Kuntze · Accepted solution]

Bob,

That is exactly what I meant.

It creates not more cvc, just more administrative work.

If you have a better idea, please let me know!

Irmhild

[Former Member · Accepted solution]

Hi all,

I just have the same situation at my current client (SCM 5.0), but I tried the compounding of characteristics and assigning some navi attributes to it. It works fine in DP, as long as you have a char which is not compounded.

e.g. Article (not compounded) + Article/Region (compounded, which carries navi attributes)

When doing the selection, you display the Article and filter/select by the navi-attribute of the compounded char.

Downside is, when creating the POS, the compounded chars are pulled in no matter you want it or not...

[Former Member]

I don't understand what you mean as the solution. Can be explain it in more detail?

Thanksl

Ken