Skip to Content
author's profile photo Former Member
Former Member

Using navigation attributes in planning queries

Hi all!

In one of the SAP demos I saw something like: we've got a "Store" char in planning query, and Region, Format and Climate added as free characteristics. Region, Format and Climate are navigation attributes of the Store characteristic. And when user drags, for example, Region into the planning table, he or she can enter the values on region level, and when saving the data it's being automatically distributed by all the Stores that have that Region as an attribute.

I have a somewhat similar task - I have a "Branch" characteristic that has "Country" as a navigation attribute. I have to plan data for that navigation attribute, the country, and I expect the data to be distributed by all the branches that have that country as an attribute. But when I add it to the planning query, I've got repeating rows for each branch in each country even though I don't see the branches.

What should I do to accomplish this task?

Thanks!

Best regards,

Andrey

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Feb 02, 2012 at 06:09 PM

    Hi Andrey,

    maybe you have marked 'Country' as a navigation attribute in the cube and also contained 'Country' as a characteristic in the cube.

    For your purpose it should be enough to mark 'Country' as a navigation attribute.

    Example:

    Branch := B in the cube

    Country := B__C as a navigation attribute

    Create a query with B__C, B drilled-down in the rows. Then you should get exactly the combinations of posted value you have in the cube consistent with combinations of B, B__C in the master data table. The system automatically uses system defined characteristic relationships that check the consistency of (b,c) tupels with value b in B and c in B__C.

    To create all valid B__C, B combinations in the query use the flag 'acess mode for result values' based on characteristic relationships in the query (not master data!).

    Regards,

    Gregor

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.