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!

Similar Messages

  • 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

  • Can Navigational attributes be used to create aggregates ?

    Can Navigational Attributes be used to create aggregates?

    Ok. But I am following 'SAP BW  A step by step guide by Fu and Fu'  (refers 3.5 version of BW ) which states otherwise. Its using the following example.
    1. 3 infoobjects defined for Sales Rep, Sales Region, Sales Office.
    2. Sales Region and Sales Office are defined as navigational attributes.All 3 are under the same dimension
    3. Then its in the book that as Sales Region and Sales Office are hidden inside the Sales Rep Characteristic, we cannot build aggregates on Sales Region and Sales Office.
    Is it something to do the way Cube is modelled. Or is just that Navigational Attributes can be used to build aggregates.

  • Need help on Authorization on Navigational Attribute.

    Hi All,
    I am working on Authorizations.
    I am using the info Object "Material group" which is the Navigational Attribute of 0MATERIAL.
    In Reporting, I have created the Authorization Variable for Material group.
    And after this, i have created the Authorization Object in RSECADMIN and added the info Object "Material group" and harded coded the value as "1000". After this, i have created the Authorization Role in PFCG and added this authorization Object over there.And this role is assigned specific User.
    While Running the report on specific User, for Material group, filteration is not happening over there (Material group = 1000). It is showing all values for this user.
    Can you please help on this issue.
    Thanks,
    Shahina A

    Thanks for your reply. I was on leave for the past 2 days. I have checked as you suggested.
    In 0MATERIAL, 0MATL_GROUP is the attribute and i have made Authorization Relvent for this Attribute.
    And i activated the Info object 0MATERIAL.
    Then i have run the query in RSRT and found an error while running the Report.
    Can u pls help on this issue.
    Diagnosis
    The system determined the authorized characteristic values for the characteristic 0MATERIAL__0MATL_GROUP. It determined that you do not have the (analysis) authorization to view transaction data for any characteristic values or range.
    System Response
    If this situation occurs when a variable is being filled, the query cannot be executed.
    Procedure
    You must have authorization for at least one characteristic value for the characteristic 0MATERIAL__0MATL_GROUP.
    Create the appropriate analysis authorizations for the user.
    If you are only authorized for evaluations that aggregate using the characteristic 0MATERIAL__0MATL_GROUP (for ":" authorizations), use a query without this characteristic. If the characteristic is not used as a filter or in the drilldown, variables should not be used.
    Procedure for System Administration
    Notification Number EYE 018 
    Thanks,
    Shahina A

  • 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

  • Navigational Attribute is not properly displaying

    Hello,
    We have a "Sales Group" navigational attribute YCUST_SAL-YSALE_GRP in a BW report. We have adjusted a sales group for a customer in R3 from F10 to E49 and hte same has been pulled to BW side,.
    we have activated the master data manually and we are able to see the new data is available against the customer.
    But when we refresh teh report, for that customer we are able to see only F10 as the sales group,.
    For cross check, we have sales group display property also. where we are able to see E49.
    Please let us know why we are seeing inconsistency between display and navigational attribute for a same infoobject.
    Thanks. Karthik

    Hello,
    It seems Master data is not activated properly....
    Whether the query is fetching data from Aggregates, if so you have to do Attribute changerun for this infoobject
    goto SE38 and run this program RSDDS_AGGREGATES_MAINTAIN it will Info object name...Provide your info object and execute...
    Your problem will solve.
    Regards,
    pavan.

  • 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.

  • What the big impact change the navigational attribute

    I do have infoset contained 3 DSO,
    1 of the DSO have 0JOB which we need to set as Navigational Attribute..
    The the most impact and precaution that I need to think before take this step..
    i know that base on your experience .. hope that you could share with me ..
    Point will be assign
    thank you

    Hi...
    You can set 0JOB as navigational attribute....no probs...........
    But........navigational attributes require additinal joins during query runtime........so it has an impact on the performance..........It will slow down the query performance.............moreover if u hav aggregates on the cube.......during attribute change run .....adjustment of  aggregates will also slow down.........due to this we should always try to minimize number of navigational attributes..........u also consider how often the query will run.............
    Hope this helps.......
    Regards,
    Debjani......

  • #MULTIVALUE on ratios with navigation attributes

    Dear All,
    I have some problem with table where I put only navigation attributes and ratios... the colomns ratio is "MULTIVALUE" value..
    I would like aggregate ratio on the table...
    Workaround ? Solution ?
    Thanks
    Cédric
    BO edge 3.1 SP3
    SAP BW EHP4

    Hi Igno,
    I agree that it still says that in the best practise (dated back in 2009!), but in my experience in the past years it doesn't work that well. Unless you tailor your BEX query one to one with a report that is... Not the intention of a universe i.m.h.o.
    For standard aggregation keyfigures I always set the aggregation to sum. So I only use database delegation if I really need it because it would not be possible for WebI (for example counts like number of stores with sales).
    Note that I also make sure that I retrieve data on the level that I need (by checking the number of rows retrieved for instance and comparing that with the number of lines in the report. So the database will do all of the aggregation it can do already!
    So you do NOT get the sum a second time! You get it only once, only who handles the summing within the results is different, with database delegated, it is BW, with sum it is WebI. For a plain sum it is Webi and summing within the retrieved results can be handled by WebI perfectly fine (and will match with sums by BEX where you have them) !!!
    Letting BW handle the aggregations means it will retrieve all the extra aggregation points it can find in the report, but only if it can!
    In this particular case the attribute country of the customer is not a known aggregation level for BEX, so it cannot calculate it.
    Also if you create webi based groupings of dimension objects, or even want to re-format one (like month) it does not work.
    Furthermore, if you read my post correctly I do not mention "GROUP BY" but I do say grouping.
    For totals you will always have a certain grouping/combination of dimensions (whether you call them dimension objects (in WebI) or characteristics (in BEX)). I state that to calculate an aggregation for that combination the BEX query needs to have knowledge about it. If it has not, it cannot calculate...
    So I say it should be the preferred way to let WebI handle the aggregation,
    unless it cannot do this correctly, not the other way around.
    Thanks,
    Marianne

  • What is navigational attribute?

    Hi All,
    What is navigational attribute?please tell me in brief.
    How can i use it?
    give me deep idea about it

    HI
    Navigational attr are the attributes that can be used as chars in the query (even as they are not a part of the tranasctional data of the InfoProvider). You can see this link for detailed discussion and example:
    Re: Navigate Attribute
    Key figures can be attributes, but these will only be display attributes. Compounding is a different concept. When you add a compounding char, it means that the value of the basic char does not mean much on its own, and it needs a compounding char to correctly define it. Like Controlling Area is defined as compounded to Cost Element.
    Refer thez thread s talks about nav attr with ex
    Re: Navigate Attribute
    Navigational Attribute
    if u r dealing with a Transitive Attribute. Please see this thread which has a discussion on the same:
    Re: Aggregate by attribute and subattribute
    Re: Second Level Nav. Attribute without reloading
    mahesh

  • Performance issue... navigational attribute used

    hi ,,
       if navigational attrributes are used sytem performnce incerases or decreases ?
      if so why?
    regards
    snigdha

    Hi
    Navigational attributes require additional table joins at runtime (in comparison to dimension characteristics) – but usually the decision for dimension characteristics or navigational attributes is based on business requirements rather than on performance considerations. If your aggregates contain navigational attributes, a change run must be scheduled every time this master data is loaded.
    Dimensional attributes generally have a performance advantage over navigational attributes for query operations. Fewer tables are joined to access the values of dimensional attributes than navigational attributes; therefore less overhead is seen during query execution. The requirements should be carefully analyzed to determine whether a certain attribute needs to be navigational or if dimensional or display attribute

  • Unable to view Navigational Attributes in ODS

    Dear All,
    We have enabled Material Group as Navigational Attribute in Material. Material has been included in ODS as Key Field. In ODS also Material Group is switched as Nav Attr. Now when I check in Reports I am getting # for all Material Groups. I checked in ListCube. Here also I am getting # values.
    I did master Data Activation and also did Attribute change run. Where as I am able to view values for Material Group in Material Master Data.
    Regards
    Ravi Y

    Hi Ravi,
    You could check if the X/Y table of material group are correct.
    Do RSRV  combination check on the info object material and material group. Run all the tests...espeially the consistency of X and Y tables..
    Also, you could probably check if this is some authorization issue... that you dont have authorization to view contents of material group...(may not be the case, but worth a check )...
    Sounds strange though, if all is ok and u still dont see material group. (and sometimes it cud be a refresh issue as lalit suggests....., if it has to get wierd )
    Hope it helps,
    Regards,
    Sunmit.

  • Navigational Attribute data is not display in Cube level and reporting

    Hello ALL
    Iam facing a problem like,I created Navigational attribute and I selected that navigational attribute in cube level also but data is not display in cube level.
    What will be the problem?Pl help me out.
    regards
    balaji

    Hi Dinesh
    You mean base characteristic means loading data after creating Navigational attribute?Is it this way,(orelse can u tell me about this base characterstic)
    Yes after making that particular attribute as a navigational attribute I loaded data in master data tables.
    How to run Attribute change run?can u give me steps
    regards
    balaji

  • Navigational attribute in Cube

    Hi Gurus,
    I want to understand one point before I am going to perform a small enhancement.
    I need to set a navigational attribute in a cube(before it is not checked on "I/O") meaning make this navigational attribute behave as a char., but this cube contains data already, my question is :
    can I make this change ? if yes any other additional effort?
    Thanks in advance

    Hi Ryan,
    The attr needs to be marked and activated as Navigational Attr in the parent char first. Then you can mark it as nav attr in the cube (which contains the parent char). Does not matter if the cube contains data...you can do this activity in a cube with data. Remember to reactivate the cube's update rules and any multiproviders that it is a part of after you make this change.
    Hope this helps...

  • Adding navigational attributes to a cube

    We have upgraded to BW 7.3. Previously when we added navigational attributes to a cube we need to activate the update rules from the ods but now it appears that we don't need to do that anymore. Is this the expected behavaior?  We are using the 3.5 update rules.
    thanks

    HI,
    If you are using 3.5, after selecting nav attr in the cube, the cube structure gets deactivated. The dependent update rules also gets deactivated. You will be forced to activate all again.
    In BW 7.3, SAP would have given privilege to add without activation. It is good for us. So nothing to worry.
    Regards,
    Suman

Maybe you are looking for