Navigational attribute in query

hi,
i have 0pp_c03 cube in production planning. There is 0material as master infoobject and 0material_zmw as navigational attribute i am using it to evaluate values in my formula.
In my cube i have 0material, 0order
now if i want to see value of the formula then  i have to explicity select navigation attribute
i.e
0material 0order 0matieral_mw  Formula -- >
values are display correctly
but if i against 0material 0order the value
of the formula is display as X .
Actually i wanted to display as aggregrate of evaluated value in the formula is there any way we can do it against 0material 0order.

For Example
0material 0order 0material_mw  formula/1000
1          1        1250         1.25
1          2        1250         1.25
Result i am expecting is
0material   formula/1000
1              2.50

Similar Messages

  • "Error determining attribute" after adding navigational attribute to query

    Hello all,
    We are getting a "Error Error determining attribute, Abort System error in program SAPLRRK0 and form RSRDR;SRRK0f30-01-" error message when running a query after adding a navigational attribute. We tried adding the attribute of the characteristic directly in the query and this works ok. But when we try using the navigational attribute we get the error. We would like to use the navigational attribute so we can filter based on this attribute.
    We've searched for notes regarding this problem and haven't found any. Any suggestions?
    Thanks, Ron

    hi,
    Please check if  number of the fields after adding the Navigationl attribute the should not cross 50.
    Check the RSRV test for the master data whose navigational attribute u r trying to add.
    Thanks
    Mukesh

  • Navigational attribute and query result

    gurus
    i have business organization under which i have various materials. my data flows through ods into cube. and in the cube i have my business org and materials ids
    now the problem is some of my materials have changed Buss ORG like
    Mat 1    used to be under   Buss Org 1
    now
    Mat 1    is under    Buss org 2
    and when the users run the report they should be able to see mat 1 under buss org 2. (even the history should go under buss org 2)
    and now i have to change my design
    options i have
    1) since my data is available in ods if i propose buss org as a navigation attribut and create a new cube without buss org in the cube will it work
    2) i will go with the existing design and load the new data which mean i have two sets of data
    one with material 1 under buss org 1 (which is history) and
    material 1 under buss org 2 (from now)
    now if i propose buss org as navigation attribute and use this in query will i see both history data and new data under Buss org 2.
    please do reply
    thanks

    thanks for a very useful information bhanu
    lets say my records in cube are
    Mid         Bussorg         Qty
    10048        GMI             100
    10048        GMR             200
    now initially 10048 was under busorg GMI but its now under GMR.
    if i take BusOrg char into my query i will get two BusOrg for the same Mat
    i want even my history to be moved under new BusOrg
    its like when i run the report it should give me
    10048      GMR              300
    this is how i want the result
    if i propose BusOrg as navigational attr and take that into query will i get the same result?

  • Need to add navigational attribute in query level

    Hi,
        Im new to bi . in dso i have  a navigational attribute  0CRM_MKTELM _ 0BPARTNER . 0CRM_MKTELM is a master data and  0BPARTNER also a master data that dso is used in infoset , 0country is the attribute of 0bpartner. i need to bring the 0country into my query . how can i do that     
    Regards,
    Senthil

    If you want to use 0COUNTRY as a navgational atttr. first go to info object 0BPARTNER and make 0COUNTRY as a navigational attr. save activate.
    The go to cube or DSO and check Navigational attr box infront of this info object,
    And then it will be available as a navigational attr in your query.
    Hope this helps,
    Assgn points if helpful.
    Regards

  • 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

  • Time Dependent Navigational Attributes in Query

    Hi,
      Location & Job are the Time Dependent Navigational Attributes of an Emp No and
    Created a Info Set (outer Join) based on Emp No and DSO....
    Created a Query based on the infoset and the Location * Job are Free Chars in the report
    In the query property setting entered KEYDATE as 31.12.999
    When i executed report and drilldown on Job or location it is displaying me 2 records for each employee one with Blank and the other with information.....
    It should display only one record..most recent record avaliable in Emp master data
    Where was i doing wrong

    Hi,
    Thanks for the update.
    I can't do a innerjoin as per my requirment it should be a outer join
    Thanks

  • Unable to Restrict Navigational Attribute in Query Designer

    Hi BI Experts,
    I had a Requirement to restrict on navigational attribute.......
    i have checked in every levels such that
    1.at info object level ....checked  type as navigational
    2.at info cube level checked the navigational on.
    still iam unable to restrict on navigational attribute................in the context menu its giving the options cut, remove and where used list .........its not giving option to restrict...........
    its very urgent ...........please give any suggestions how to restrict on navigational attr

    Dear Ram,
    Dont expand the InfoObject and see the Attributes ( They r Dis Attrs )
    Just expand the Dimension --- Nav Attrs are available  ?
    Dont put them in Filter pane..( if available )
    Drop them under Rows.
    But restrict them under Default values ( By clicking on Filter pane ).
    Regards,
    Ram.

  • 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

  • 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

  • Navigational attribute Vs normal infoobject in Query

    Hi
    I have  some infoobjects named ..1)ITEM....2)STATUS....3)SALES etc in cubes...
    I have to design a query showing this data...the report should show Item Status also...I can use normal infoobject STATUS from infocube in report to show Item Status....I have one more possibilitySTATUS is added as navigational attribute of infoobject ITEM..So I can use this navigational attribute also..which one should I use normal infoobject STATUS or navigational attribute STATUS of infoobject ITEM to show item status in report?how to decide on this?
    Thanks for your guidance.

    Hi Hayward,
    Status as direct Object
    When you use Status as an object added in cube you get the data of the day the cube was loaded. Let say for example your cube is loaded weekely on sundays, so the field status will give status as on sunday, even when it is run on other subsequent days of the week. So as correctly pointed in above posts values you get in status are not real time but historical.
    Status as Navigational Attr of Item
    When you use Status as Navigational attribute of Item then you get current data because in almost all cases Master Data Objects are loaded on daily basis and thus it picks the latetst Status of Items.
    In case your cube is loaded daily then it won't make much difference that whether you are using it as a standalone object or as navigational attribute of Item.
    Hope it helped
    Regards
    Raj Rai

  • 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

  • Navigational attribute issue in query

    Hi gurus,
    Here is a very tricky issue that I am facing. If anyone could please help me with a workaround for the same.
    I have an infoObject called ZDIV_CUS which is basically 0CUSTOMER with 0DIVISION compounded to it. Hence, when I load data into ZDIV_CUS, I would have one record for a unique combination of customer and division. In functional words, I would have one customer maintained for multiple divisions. ZDIV_CUS also has other navigational attributes as 0SALES_OFF, 0SALES_DIST & 0SALES_GRP. Also, I have 0MATERIAL, which has 0DIVISION as a navigational attribute in my cube.
    Hence the master data for ZDIV_CUS looks as follows -
    0DIVISION    0CUSTOMER    0SALES_OFF    0SALES_GRP    0SALES_DIST
    01           100000       L001          L01           L010100
    02           100000       L005          L08           L020150
    01           100001       L001          L01           L050150
    03           100001       L005          L02           L052542
    The transactional data in my cube is as follows -
    0MATERIAL    0CUSTOMER    0DIVISION    0SALES_OFF   0NET_SALES   0MATERIAL_DIVISION (Material master div)
    102152          100000       01           L002         110000       02
    102545          100001       02           L002         12000000     02
    The above data is all transactional except for 0MATERIAL_DIVISION which comes from material division.
    My query is built in such a way that the division comes from 0MATERIAL (restricted to variable in the selection screen). ZDIV_CUS and its navigational attributes are being used in my query. The initial display is shown as per ZDIV_CUS_0SALES_OFF (i.e. sales office from ZDIV_CUS)
    The problem is that say for eg for the above mentioned scenario, the user executes the query for division 01 and the below mentioned output comes up -
    0MATERIAL_DIVISION     ZDIV_CUS    0MATERIAL    ZDIV_CUS_0SALES_OFF     0NET_SALES
    02                     100000      102152       L001                    110000
    If we take a closer look, we would know that ZDIV_CUS_0SALES_OFF should pick up value L005 and not L001 since the division for which the query is run is 0MATERIAL_DIVISION and not 0DIVISION.
    Request help to resolve the abovementioned issue.
    Thank you,
    Sree

    Can any one answer for Issue-2. Even I am also facing the same.
    Thanks in Advance.

  • Navigation Attribut is not shown in two rows in the Query

    Hello,
    we are using a multiprovider with the infoobject 0material. In the multiprovider we use a navigation attribut MH_PR_ST of 0material.
    Normally, the query rows should show the material number and the corresponding attribut MH_PR_ST, but in some materials in the multiprovider exist some rows where the attribute is shown correctly from the master data table and in some rows the attribute is not shown.
    Therefore in the query two rows are shown:
    Material No. MH_PR_ST Key Figure
    4711           A                    10
    4711           #                       5
    Sum                                  15
    With all other navigation attributs there is only 1 row.
    Do you have any good ideas?
    Thank you very much + best regards,
    Ilona

    Hi,
    Assuming the second row comes from one of your basic cube; since it looks that 0MATERIAL is populated (it is coorectly identified), ensure that the identification of the nav 0MATERIAL__MH_PR_ST is done properly in your multiprovider.
    hope this helps...
    Olivier.

  • Navigational Attributes are not shown in query

    Dear all,
    I have a problem in a query. I need to present values using by using Navigational attribute in the query, the thing is that it does not recognize my navigational attribute. I have checked the characteristic in the Multiprovider and Infocube as navigational. And in the Multiprovider I have identified the navigational attribute from the right source.
    What I think is strange is that I can see the navigational attribute when I see the data in infocube but not in the query. Does anyone knows what I might be doing wrong?
    Best Regards and many thanks,
    Mazzz

    Hi
      plese try to find out the data for this fields through LISTCUBE,if you gets data here for that navigation attr then it has to appear in your query designer also.
    and also once again check your idetification for the navigation attr in multi provider  whether its taken from write souce or not.and plese chk through your cube also for the navigatin.
    in cube navigational attr has to mark then in the same way in the multi provider also
    mahesh
    Edited by: Mahesh Kumar on Jun 2, 2008 10:47 AM

  • 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

Maybe you are looking for