Disadvantage of having Navigational Attributes

Hi there,
Pl. clarify the disadvantage of having a navigational attributes instead of low performance.
Regards
Sridevi

If a navigation attribute is used in an aggregate, the aggregate has to be adjusted using a change run as soon as new values are loaded for the navigation attribute (when master data for the characteristic belonging to the navigation attribute is loaded).
This change run is usually one of the processes critical to the system performance of a productive BI system.
This is why avoiding using navigation attributes, or not using navigation attributes in aggregates, you can improve the performance of this process. On the other hand, not using navigation attributes in aggregates can lead to poor query response times. The data modeler needs to find the right balance
Regards,
Sergio

Similar Messages

Navigational Attribute Filter value selection not showing full name

Hi Experts,
We are having Navigational Attribute TM Responsible. We have created variable in BEX for it. When we are searching for value selection for this in RSRT, its showing only last name and key part. But If I dont pass any values, and display the result its showing full name. Please find the screen shots.
Customer needs full name to be available for selection in filter in above picture 1.
Please suggest what needs to be done.
Thanks,
Govind

Hi All,
The issue is resolved. Making display as Long text at Infoobject level and at Query display level was not working. Hence I tried to change the display at Multiprovider level as shown below. This fixed the issue.
Right click Navigational attribute -> Provider specific properties
Made the display as Long text.
This setting resolved the problem.
Thanks for help and replies.
Thanks,
Govind

Line Item Dimension and Navigational attribute

Hi Gurus,
Can somebody tell me how line item Dimensions and navigational attributes works technically?
What are the pros and cons for them?
Regards
Alex

Hi Alex,
You will use navigational attributes based on how you want to track and report history. Let me explain with an example.
Customer Bubba is assigned Sales Group XYZ in Jan 2007. In July the Sales Group on the Customer Master record is changed to ABC. Your are looking at the sales report.
1). If you want to see all the sales made to Customer Bubba at the time of reporting (current) then you will use navigational attributes You will create 0SALESGRP as the navigational attribute of 0CUSTOMER . Then all sales to the customer will show up under Sales Group ABC.
2). If you want to see all the sales made to the customer at the time the actual transaction occured then you will add Sales Group as a characteristic of the InfoCube. Then sales from Jan - June 2007 will show under Sales Group XYZ and from July - Present will show under Sales Group ABC.
Performance issue occurs because navigational attribute is stored outside of the dimension table of the cube and is stored in separate master data tables. So query has to perform additional table read. So essentially there are advantages and disadvantages of usng navigational attributes. It is business requirement that will drive the use of navigational attribute.
Hope this helps!!!. Please assign points.

Data issue with Navigational Attribute in the report

Hi Experts,
We have a report which has Material and Material Group in the report. Material Group is a navigational attribute of 0Material. We have some 31 material groups in the ODS. However, the report is diaplaying only 3 material Groups. If I use Material Group directly( not as an attribute of material) then it is displaying all the 31 material groups correctly.
We have a hierarchy which is loaded through Flat file on Material Group. We need the hierarchy to be displayed for all the material groups in the ODS. Please let me know what could be causing this issue?
Thanks and Regards,
Kavitha Jagannath

Hello Kavitha,
Check if the Material Masterdata is having these Material groups. If not then load this Material masterdata and activate it.
As your query is using Material group as Navigational attribute then the data should come from this Material Masterdata.
If your Material has only 3 of th eMat Groups then report will show only 3. Better update this Material masterdata.
Regards,
Pratap Sone

Poor Performance with Webi on top of BW - Large Navigational Attributes

We have recently developed a reporting model based on having a BW cube of approx 20 million records. This has 2 very large line item dimensions (one 14 million records, on 6 million records) that both have navigational attributes stored against them.
We need the design to be like this because the attributes change monthly and we do not wish to do a complete drop and reload of cube data each month (this takes 10-12 hours).
When we build a Universe on top of the cube and try Webi reporting the performance is dreadful - many reports time out completely. This happens whether or not the large line item dimensions are selected in the query. The BW query is very simple just 2 key figures and approx 30 Navigational Attributes as default values. No filters are applied.
For example a query that just contains Calander Year and one key figure either times out after 10 minutes or fails.
Our source of the data is Oracle tables and the same query runs in 2 1/2 minutes and the query runs in RSRT in approx 5 minutes with no problems so it is definately a problem with BOBJ to MDX to BW.
We are on BW7.01 SP5 and XI3.1 SP2. SAP have recommend going to SP3 and using query stripping to help with this but I doubt if this will work.
We have tried building aggregates, splitting into yearly cubes etc but nothing seems to help.
My question is do the large navigational attributes mean Webi simply can't cope with this?
Thanks

Thanks for the suggestions.
Although this did not directly help I've now found a solution.
We had a calculated key figure in the query that doing a count of records on a huge navigational attribute. This was causing all queries to run very slowly (even if the key figure wasn't selected in Webi).
Removing it solved the problem. Will have to find another way to do the count key figure.
Thanks

Still having navigation problems and need help with how to debug

Hi,
I've been porting over a servlet project to JSF and I'm still having navigation problems. I thought the problem might have been because the original project used HTML frames and so the "from-view-id" JSP defined the frame/framesets and the specific JSP that does the submit (and so is named in the "from-view-id" is never defined in a "to-view-id" attribute). I've now switched to using an IFRAME, and that resolves that problem. So now the JSP is defined in a "to-view-id" attribute and it includes an named IFRAME that can be used as a target. I press the submit button and I get not the JSP expected butinstead the same JSP displayed inside its own IFRAME.
Here is the code for the submit. I've simplified it as much as possible with a static action (originally it was a call to a method) just to try and get things to work. This is the current version:
<h:commandButton value="View Alias" action="foo" styleClass="select" type="submit" />Here is the navigation rule in faces-config.xml. Again, the problem is that SelectManager get redisplayed in the IFRAME instead of display.jsp.
<navigation-rule>
   <from-view-id>/SelectManager.jsp</from-view-id>
   <navigation-case>
      <from-outcome>foo</from-outcome>
      <to-view-id>/display.jsp</to-view-id>
   </navigation-case>
</navigation-rule>I have also tried it without the "from-outcome-value" which I presume means that the "to-view-id" gets displayed unconditionally and it still fails. Any ideas on how I can debug this? (I'm using GlassFish if that's important to know)
Rob Tanner
Linfield College

Raymond, The real trick is avoid doing technical things when coming down with the flu (I should also add that I'm a JSF newbie). Reading your original message this time I see what you're suggesting and found a conversion error although I don't understand it. Here's the code (including the <h:message/>):
            <h:selectOneMenu value="#{members.dcodes}"
              style="color: #7f0000" id="selector">
              <f:selectItems value="#{members.departmentList}" />
            </h:selectOneMenu>
            <h:message for="selector" style="color:white"/>And here's a snippet of the generated HTML:
<select id="j_id_id26:selector" name="j_id_id26:selector" size="1" style="color: #7f0000">
         <option value="aad" selected="selected">Academic Advising</option>
     <option value="aaf">Academic Affairs</option>
     <option value="adm">Admission</option>
     <option value="up">Upward Bound</option>
</select>If I select "Admission" for example, the error I get is:
Conversion Error setting value 'adm' for 'null Converter'.Since everything is a String value, I don't get the error. Could someone please enlighten me.
Thanks.

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

Variable for navigational attribute affected fiscper input variable

Dear Friends
Initially, the query is having an input variable for fiscper. The query was able to run properly.
When i add a input variable for a navigational attribute to the same query which is based on multiprovider, the fiscper input variable is no longer seen.
So, I removed the global filter for the navigational attribute and it is ok again. I fixed a value for the navigational attribute at filter level is also fine.
Please advise what could be the cause. Thank you so much.
Best regards
Bass

Hi Bass,
Again seems to be a strange issue, if you have two independent characteristic with two different input enabled variables then there is no reason for the variable to not to show up on selection screen.
Once you add the new variable and save the query just make sure that you have earlier variable as it is and check the query properties popup and see the fiscper variable sequence in the variable list.
Regards,
Durgesh.

Authorization on Navigation Attribute

Hi experts,
i'm faced with a problem. I have a navigation attribute in my data model which is authorization relevant. The problem is that the basic characteristic is not authorization relevant. I am not able to make my setting in the analyse authorization as the basic characteristic is not authorization relevant. The basic characteristic is used in some other projects so that i am not allowed to make this characteristic an an authorization relevant one.
Has anyone an idea how to solve this problem?
Thanks all in advance.
Best Regards,
Ali

You did not mention what BW version you are on. This scenario is allowed in 7.0 Analysis Authorizations, but is not allowed in 3.x
In 7.x you can make any navigational attribute authorization relevant on the Attributes tab in RSD1, and the base characteristic does not have to be authorization relevant.
What problems are you having?

Showing navigation attributes in the same column of a query

Hi,
I would like to know if there is a way to define a query such that TWO navigation attributes that reference the same underlying characteristic can be displayed in the SAME column rather than TWO separate columns.
I will describe an example scenario to clarify the requirement. We are using a BI Content InfoCube (0COOM_C02) that has the navigation attributes 0COSTCENTER__0PROFIT_CTR and 0WBS_ELEMT__PROFIT_CTR activated. Both of these attributes reference the characteristic 0PROFIT_CTR. The InfoCube contains transaction data for Cost Centres and WBS Elements.
The requirement is to define a query that summarizes the data by profit centre. At the moment, in order to combine Cost Centre and WBS (Project) data in the same query by Profit Centre, both navigation attributes need to be selected, resulting in the following output:
0COSTCENTER__0PROFIT_CTR......0WBS_ELEMT__PROFIT_CTR......AMOUNT
PC01...............................................Not assigned...................................10,000
PC02...............................................Not assigned...................................20,000
PC03...............................................Not assigned...................................12,000
PC04...............................................Not assigned....................................2,000
Not Assigned....................................PC02..............................................5,000
Not Assigned....................................PC03..............................................8,000
Not Assigned....................................PC05..............................................30,000
Not Assigned....................................PC06..............................................50,000
However, the desired result is to display only one profit centre column using the two profit centre navigation attributes as shown below:
PROFIT CENTRE......AMOUNT
PC01..........................10,000
PC02..........................25,000
PC03..........................20,000
PC04............................2,000
PC05..........................30,000
PC06..........................50,000
Is there a way to achieve the above result using the two navigation attributes only, without having to add 0PROFIT_CTR as a characteristic to the InfoCube?
Any suggestions would be appreciated.
Thanks,
Mustafa.

Hi Mustafa,
You have to use enhancement RSR00001 in the transaction CMOD to start developing your code.
For more information how the customer exit variables are processed, refer to the documentation:
http://help.sap.com/saphelp_nw70/helpdata/EN/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm
A short example can be found here:
http://help.sap.com/saphelp_nw70/helpdata/EN/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
This should help.
Regards,
Daniel

APO Demand Planning - Navigational Attributes BADI

Hi,
I have an issue in that I need a Navigational Attribute to be able to store the GUID for a Forecast Profile to a Selection. In standard, only a selection with Key Characteristics can do this. It is not practical for us to use a Key Characteristic because the realignment would take to long therefore it needs to be a Navigational Attribute.
Having read the note "Use of planning characteristics vs navigation attributes in APO DP " dated 19/10/2009 in SAP Solutions » SCM - APO Forum, it indicates that there is a BADI work around to enable this to be done but cant remember which one.
Does anyone know the BADI can be used to achieve this?
Thanks
Mark

Prabhat
Please refer to OSS note 413526 for a comparison of Navigational Attributes v/s basic characteristics. While most planning tasks can be done with navigational attributes there are a few limitations.
Rishi Menon

Varialbe creation on Navigational attribute ?

HI all ,
I have a navigational attribute 0plant_0comp_code which is restircted with some values in characteristic restrictins pane .
and also i have created one variable with multiple single values .
then how it is going to work ?
regards ,
Srinivas .

If you are maintaining a variable then there is no point of having value restrictions in the query.
Because if user is not giving any input in the query selection (variable), then it will consider value restriction while returning the query result. Which is wrong output as expected by user. Also, it will definitely create a confusion.
If you want to have those values, then for the variable you have created, you can write a code under I_STEP = 1 to make these values as default values for the variable. Which will come when you will execute the query, but can be changed with user defined values.
Pravender
Edited by: Pravender on Jun 14, 2010 1:09 PM

Reg Navigational Attribute in Query

HI
Iam having a strange problem,I wasnt to include a channel levl that is a navigable attribute to customer in my query.The query is reporting from an multi provider.I find that the navigable attribute is checked in my Infocube ,but its not appearing in my query to drag it in the columns.
Is it because it is reporting from Multiprovider should it be generated.If so how?
Thanks
BR

You need to make it as navigational in the multiprovider definition too. Navigational attr of underlying cubes are not automatically included in the multi. You need to manually include them as you do for the chars and KF's

Navigational attribute in aggregates

Pls. answer.
-How do you include the navigational attributes in aggregates. Aggregates are created over the characteristics(InfoObjects), how to include the Nav. attr. to aggregates?
-Does the usage of Nav attr in aggregates reduces the performance?
Thanks,
NN

Navigational attributes do drag down the time a little because of the extra read that needs to happen on the master data table. Even more evident is the increase in the run time of the Attribute Change Run (ACR) job. This would runner longer during the batch process after updates to master data, as the navigational attributes needs to be adjusted in the aggregates with latest values.
So avoid using navigational attributes in the aggreagtes if you can. Also avoid having both the base characteristic and its navigational attribute in the same aggregate. The last I heard this is a definite NO NO.
FYI, if you add the base characteristic...all the navigational attributes are inherently included as well. In other words, if I have 0SOLD_TO in my aggregate, I can run a query on the navigational attrbute 0SOLD_TO_0ZIPCODE which will still use the aggregate.
Hope this helps!

Restrict on Navigation attribute in Integrated Planning

Hello,
I have created an Aggregation Level on the Multiprovider(combines Actual and Plan) and I have created a ready to input query on the multi provider. The query works fine for planning.
However, I would like to restrict the query to show only few accounts. Account type is the navigational attribute on the Sold to party and I want to restrict only the Sold to party of Account type 1 2 3 & 4. When I restrict that in the query the Planned values are not editable. I am not able to input the planned values. I am able to input when I take the navigational attribute away in the query.
Could anyone of you please help me with this. Could anyone please let me know the steps to use the navigational attribute in the input ready query or Integrated Planning
thanks,
KK

Hi,
As Sven has mentioned has mentioned you can lock each record by having a characteristic "0createdby".
But you have to create a characteristic relationship of type "Exit" where in you write a small piece of ABAP code to generate the value of "0createdby", when the end user tries saving a reocrd in to the planning cube.
Kindly refer to the following link for more details on characteristic relationship,
http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3d0f31b70701e10000000a422035/frameset.htm
Regards,
Balajee

Disadvantage of having Navigational Attributes

Similar Messages

Maybe you are looking for