Filtering in query through navigational attribute.

Hi all,
I want to restrict my query on the basis of navigational attribute (Material Type) of my info object (0Material) in query designer but when i drag material attribute in Filter tab page it doest work and does not appear in filter tab.
Please help me how can i restrict this in this manner.

if it is selected, then in query, drag drop 0material___type infoobject.. do not use attribute under 0material.. you can find this in the same dimension as of 0material.

Similar Messages

Infoset - Query with navigational attribute as filter

Dear all,
We have created an InfoSet linking an InfoObject 0COORDER to an Info InfoCube containing order data.
We have used a Left outer join to link 0COORDER tol 0COORDER in the InfoCube. The purpose is to be able to report on all 0COORDER even if they have no transaction data.
When creating a query we get a list of all 0COORDER as expected. The problem arises when we try to use the navigational attribute "Status" from the InfoObect 0COORDER as a filter in the query. This does not work at all.
Does anyone know what we are doing wrong here ? We are using BEx Query Designer 7.0.
Kind Regards,
Mikkel

Hi Mikkel
When you say that your Status field does not work at all, what is the error you are getting? Are you able to see this field in the query designer. If that is not the case that means your "status" is not chosen in the infoset design.
If you are able to see it in the designer then please let us know what is the exact error you are getting.
Thanks.

Query on Navigational attribute of navigation attribute

Hello,
we work on BW 7.0 but use still the 3.5 BEX. Is it possible to navigate
on a navigational attribute of a navigational attribute? If yes, is
this only possible in the the next version of BEX? Because in the
version 3.5 I didn't find a possibility to do that.
Thanks.
Regards, Lars.

Hello Lars,
This isn't possible; you can also refer to below thread -
Navigational Attr of Navigational Attr in cube

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

Inconsistencies with Navigation Attributes

Hello all,
We are experiencing some inconsistencies with navigation attributes. Attributes are flagged as navigational on the InfoObject Level and also selected in the InfoProvider's Navigation Attributes folder. However some of them are showing in the Query as Navigation Attributes while other's don't. The same process was followed for all of them. Any ideas why this might happen?
Thank you so much!

Take the "Company", "Area" and "Department" out from the attribute list of the Org Unit !!
then delete "Company", "Area" and "Department" one by one ..
And then try deleting orgunit ..
Regards.

Error Message in Query Filter on attribute of 0MATERIAL filters charac.

Hi All,
i have a query with few variables , i used navigational attributes of 0material......
I am getting the below Warning Message... Ineed to supress the below Error Message....
Please let me know the solution...
Error Message: Filter on attribute of 0MATERIAL filters charac. values without master data
Diagnosis
Currently, it cannot be guaranteed that SIDs and master data exists for all characteristic attributes for the DataStore object to be read.
There is a restriction on a navigation attribute of the listed characteristic in the query. This filters all characteristic values of the master-data bearing characteristic for which there is not yet master data out of the result.
For performance reasons, this filtering is unavoidable.
System Response
Procedure
In case of doubt, find other restirctions directly on the characteristic values of the characteristics contained in the DataStore object.
Procedure for System Administration
Notification Number DBMAN 345
Thanks All

Dear all SAP Gurus,
we've solved this problem and this is the solution:
The warning is triggered by the method CL_RSDRV_ODS_QUERY-PROCESS_SFC_WITH_ATR when the BExFlag of the InfoProvider is not set. Using DSOs for direct update there is no change to change the BExFlag. As a result queries based on a DSO for direct update always throw the above mentioned warning when filter-characteristics are attributes.
Regards, Clemens

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 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?

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

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

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

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

Filtering in query through navigational attribute.

Similar Messages

Maybe you are looking for