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

Hi Gregor!
Thanks a lot for your help!
It's almost working as I want it to work.
But there's something I'm probably doing wrong.
I'm selecting B as a "free characteristic" in the query and hide it, and put B__C in the rows section, then choose "Master Data" for both "Access Type for Result Values" and "Filter value selection..." for both characteristics. After that I execute the query and see that everything seems to be as it should be, and after I enter data for something, it automatically distributes by the branches that have that country as an attribute.
That's weird. Because when I do as you told me to, using the flag "Characteristic Rel-ps" for "Access Type for Result Values", put B__C and B in rows (B is hidden) and execute the query, I get multiple repeating rows for each branch that has the selected country as an attribute. And system tells me that "3 characteristic combinations generated successfully" (that is correct - I have 3 branches for the selected country).
I've tried setting "Char rel-ps" for both of the characteristics, then for only one each of them - and I still get the same picture.
Could you please tell me what I might be doing wrong here? And why it seems to be working with "Master data" chosen for "Acc. type for result values"?..
Thanks!
Best regards,
Andrey
Edited by: Andrey Makeev on Feb 3, 2012 6:45 AM

Similar Messages

Can we use Navigational attributes as Virtual Characteristics

Hi,
I need to derive the virtual characteristic based on 2 infoobjects in the multiprovider. One of the infoobject is a navigational attribute. I am using the BADI approach to create the virtual characteristic. Can we use navigational attributes to pass values to derive the virtual Char or is there any limitation.
Basically can I use the below code to read navigational attr
when <b>'0EMPLOYEE_0JOB'</b> OR '0PROFIT_CTR'.
          l_s_chanm-chanm = <chanm_used>.
          l_s_chanm-mode = rrke_c_mode-read.
          append l_s_chanm to c_t_chanm.
Thanks,
Kal

Hi Kal,
          I think you model a virtual KFig in the way you have suggested.I think the routine will work.Its looking similar populating a field using read masterdata.I think it will work.
Regards
Karthik

Difference between drill down and filter using navigation attributes?

hi all,
can anyone let me know the difference between filter and drilldown options using navigational attributes. pls explain with examples for filter and drill down and how it varies.
thanxs
haritha

Jst to add up with an example :
Say you have a cost center variance analysis report with cost elements in the filter. ( not present in the default report result )
Filter - You can right click on a particular cost center & say " Keep Filter Value " - it will result in only showing that cost center & you can wish to select other filter value doing " Select Filter Value ".
Drill Down - If u wish to see the cost elements associated with cost centers you can right click on Cost Center & do " Drill Down To - Cost Element " or Drill Across.

Reports using navigational attributes

Hi All,
I have a question, where I need list of queries which use two infoobjects(0sales_off & 0sales_dist) as navigational attributes of 0CUSTOMER.
Is there any easier way to find out this or any table will help? Please let me know..
Thanks,
Chandra

Hi Vikram,
We fetched ELTUID from RSZRANGE table. But RSZELTPRIO table does not have entries.
So we mapped TELTUID field (from RSZELTXREF table) to COMPUID(from RSZCOMPDIR table) .
This Solution is working only if selections /variables are defined on navigational attribute.
eg: q001 -> zcustomer_0sales_dist - simply dragged to free characteristics panel
q002 -> zcustomer_0sales_dist - dragged to free characteristics panel and restricted by varaible zsa_sofs
above solution is working for qoo2 but not for q001.
Regards
Kusuma
Edited by: ksheersagar kusuma on Feb 24, 2010 3:12 PM

How to use Navigational attributes in BEx

Hi experts,
I have searched many threads regarding navigational attributes in BEX.
But unable to find any info.
How the navigational attributes are used in BEx query designer.
What is the difference between characteristics and Nav attr in Query designer.
Every one n saying Nav attr are used for drill down purpose.
What exactly is this drill down .
Please send me any related documents also.
Please answer me.
Thanks in advance
Sundar

Hi,
Characteristic attributes can be converted into navigation attributes. They can be selected in the query in exactly the same way as the characteristics for an InfoCube. In this case, a new edge/dimension is added to the InfoCube. During the data selection for the query, the data manager connects the InfoProvider and the master data table (u2018joinu2019) in order to fill the Query.
Navigational attribute is like any other master data attribute except that we can navigate (filter, drill down and selection) in reports on this characteristic.
Drilldown means after you executed the query , you want to see further detailed data with particular combination ,
in that case you navigate further or do restiction that is drilldown.
If you restict a navigational attribute in Query , then it behaves like a normal characteristic and not as a navigation attribute.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a63e7e07211d2acb80000e829fbfe/content.htm
Also check the link:
http://help.sap.com/saphelp_nw70/helpdata/en/43/f234619e3c4c5de10000000a155369/frameset.htm
Regards,
Amit

Issue when using Navigation attributes for filtering in BEX

Hello,
We are encountering an issue when applying filter on Navigation attributes in BEx query built on top of a BW HANA Virtual Provider.
The interface is as below :
HANA Calculation View -> SAP BW 7.4 Virtual InfoCube -> Multiprovider -> BEx Query.
We have directly mapped the base Infoobject from HANA View to BW Virtual Provider and using this in BEx query free characteristics. We also have used the navigational attribute of this Infoobject in our Report variable screen as well as an Auth relevant object.
Eg if ZMATERIAL is the base infoobject and ZMATERIAL__ZXYZ navigational attribute is used in the report variable screen and as Authorization variable.
This is causing the query to fail.
The query also fails if I apply any filter values on any Navigational attribute with error message :
"Termination message sent ERROR DBMAN (305): Error reading the data of InfoProvider"
Using the navigational attribute with authorization variable fails with below :
"Termination message sent ERROR DBMAN (099): Invalid query;Failed to find attribute ZMATERIAL__ZXYZ [...]"
Appreciate any inputs on this issue and how this can be fixed.
Thanks,
Tintu

Hi Andrey,
Thank you for your input.
Based on the OSS note , it says to import BW7.4 SP7. We are already on BW7.4 SP7
We get error "Termination message sent ERROR DBMAN (099): Invalid query;Failed to find attribute
ZMATERIAL__ZXYZ" whenever we try to apply filters on any of the navigational attribute.
Thanks,
Tintu

Using navigational attributes in selection for a forecast profile

Hello All,
I could understand that the forecasting can be done on navigational attributes.
But when I goto transaction /SAPAPO/MSDP_FCST2, I could not create a selection on navigational attribute.
Because I could not see the navigational attribute field in the selection screen for selection criteria/profile creation.
Does anyone have any idea of how to do this?
Also I saw the method SEL_CHANGE of BADI /SAPAPO/SDP_FCST5. But the documentation is confusing, since it says that using this method, we could delete the navigational attributes from the selection condition. Could any one suggest me how to use this BADI if I cannot create a selection with navigational attribute?
Thanks,
Suresh

Hi Sunitha,
Thanks a ton for your reply.
The real problem is the OSS note is confusing.
OSS Note for this method says "This method can be used to change the selection to be stored in
in the generated selection table. Navigation attributes can be removed, such as the function of assigning a forecast
profile to the selection can also be allowed for selections with navigation attribute without a basic characteristic."
I am really confused what it says.
If we can't create a navigational attribute for a selection, how could we delete it from a selection?
Thanks,
Suresh

Navigation Attributes & Planning Characteristics

Hi,
We plan to maintain some of the characteristics as Navigation Attributes. We understand that there are performance issues if we use navigation attributes in planning area.
I have a query: If we do not navigate data based on navigation attribute in interactive planning, even then the performance be low or only when we select navigation attribute in interactive planning?
regards,
Mohit

By definition, nothing is stored in live cache against navigation attributes. So if you load a selection containing navigational attribute or drill down by navigational attribute, in theory this should be much faster vis a vis reading from live cache (not withstanding the general computing theory of memory resident processing). This statement (of mine) is contra positive to SAP warnings on performance when using navigational attributes. There are a dozen notes on this to scare users.
There is no definitive answer I guess... at least empirically. It depends eventually on the query size. When query is large, it is hard to blame navigational attributes alone (if you are using some). It can be more so because of transaction time (SQL>LC routine > SQL) in the live cache as well. Sometimes reading a simple relational table (if indexed) can be much faster than reading non-relational (live cache) tables.
I am not a techspert and authority on this. This response is based on my painful experiences. For me anything more than couple of seconds on interactive DP is a waste of time.
Thanks
Borat

Navigation Attributes

dear All,
Is there any thumb rule to decide whether a characteristic should be defined as an attribute/navigational attribute.
the reason is from a realignment point of view, navigational attributes can be easily realigned by just updating the master data. For plain attributes, we need to carry out the realignment.
Can i use navigational attributes in planning?
regards,
Kedar

Hi Kedar,
You cant plan using navigational attributes.You can do one thing if you really want to plan using navigational attributes convert them to separate characteristics and can start planning.
Regarding realignment , you cant do realignment for attributes you need to convert them to characteristics in order to plan.
Please let me know if your question is answered. Please let me know if you have any questions.
Thanks ,
Raj

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

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.

Navigational Attribute Problem in Input Query

Hi,
I am having a problem in input query implementation which uses a navigational attribute. I have, for eg, only one char 'customer' in rows; i want to exclude the customers with the status D (deleted) from displaying (Status is nav. attr. of customer). I tried this by restricting in filter, Status D-"exclude". But as soon as I do this, query no longer remains input ready! (I also tried putting the same restriction in Default Values area rather than Filter, but ended with the same result )
I discovered that if, furthermore, I put Status in rows (with the above said restriction still remaining), query is again input ready.
Can't we exclude values in the filter on an input query? I want to know if this is a restriction with IP or a bug?

Hi Gregor,
Thanks for the explanation. But this makes me wonder, because due to this restriction one of the BIG advantages queries had over the planning layouts of BPS, seems to be gone. I mean, using navigational attributes for filtering; if we have to always have a single value restriction on a nav. attr., this will really be restricting. Is it expected that this will be changed in a later SP?
And there is another problem that is coming due to this. When I use the exclude filter and also the nav. attr. Status in rows, then the query becomes input ready, but there are warning messges displaying when the query opens saying -
Characteristic Customer has no master data for "C1"
Characteristic Customer has no master data for "C2"
etc... (these are the customers with status D). We are on SP15.
Please suggest what should I do to get rid of these messages?
Edited by: Mayank Gupta on Apr 10, 2008

Navigation attributes in APO DP

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

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.

BI-IP / Formula navigation attribute

Hi,
i have the following problem and hope somebody can help.
I have a BI-IP planing function (Fox-Formula) which simply copies the keyfigure Amount from the characteristic company (#) to the characteristic company (8703).
{ KI_LCCUR, 8703 } = { KI_LCCUR,# }.
this characterisic has also a navigation attribute headquarter.
when i run the function the following error message appears:
8703,# is invalid: Valid is 8703,DE. Characteristic "ZCompany"
which means to me the master data for charactersitic company 8703 and its attribute Headquarter # is not valid, which is true. But what do i need to do in order to use the right combination 8703,DE?
Is there a way to make fox formula to find the right value for the attribute? is there a way use navigation attribute in fox formule?
Thanks for your help in advance!
Mike

Hi,
The problem can be due to the mapping in the cube.
Please reactivate your cube.
If you are using a multi-provider, then please check that the navigational attribute is defined in all the cubes in mulitprovider.
Regards,
Amit

Virtual infoprovider with services - Navigational attributes

Hi all,
I have a basic cube in BI system- X , and created a virtual cube in another BI system Y with services to read data from basic cube of BI system X . In BI system Y we built a report on virtual cube. This report (on virtual cube in BI system Y) is using a characteristics say Product group ( which is a navigational attributes of prodect in BI system X).
DataFlow is as under:
Basic cube in BI system X:
Product
Year
Amount
and Product group is switched on as navigational attributes in this basic cube.
Virtual cube in BI system Y:
Product group
Year
Amount
Report in BI system Y:
Product group in rows
Amount in column
This report is not working.
If I do the the following changes as follows then it works:
1.Use Product instead of product group in report
2. Switch off navigational attributes in basic cube.
We are in BW 3.5 and navigational attributes option is ticked on for virtual cube.
In summary, If I do not use navigational attributes in report and switch off navigational attributes from basic cube then report shows data.
Could you please help me to figure out the issue.
Thanks,
Harry

Thanks Naga,
Yes, I tried adding product in virtual cube as well but it did not work. Secondly, we do not want to add product in virtual cube because of data aggregation.
Most strange thing is that, once we switch on any navigational attributes on basic cube, function module stop working (paasing any data to virtual cube report). report says no appropriate data found. We are using sap standard function module "RSDRI_INFOPROV_READ_RFC". I debegged this code and no data in internal tables.
If we switch off all navigational attributes from basic/source cube this function module provide data to internal tables in code.
Why function module is behaving like that.
You guys experience/support/any clue will be appreciated highly.
Thanks,
Harry

Difference between Navigation attribute and normal attribute

Hi Experts,
What is the use of Navigation attribute in place of normal attribute? When we need to use navigation attribute instead of normal attribute?
Thanks!
Sapna

Hi Sapna,
Please try to search...this has been discussed many many times.

Using navigation attributes in planning queries

Similar Messages

Maybe you are looking for