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

Similar Messages

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.

Navigational Attributes Not Available in Query Designer

I don't see navigational attributes under Dimensions/DimensionA in Query Designer. Is there a switch to enable/disable nav attr. in BW?

Hi,
Yes you need to switch on Navigational charateristics at DSO/CUBE and then add them to MultiProvider Dimension and assign then assign the fields.
Thanks,
Nagarjuna

Navigational Attribute not found on Query for an Infoset

Hi Experts,
I have created Infoset on two DSO's and when i'm trying to query on it i'm not able to find the Navigational Attribute which are selected on both of the DSO's.So in order to get the Navigational Attribute on the query of the Infoset what should i need to do.
Pls Help.
Thanks in Advance.
Amit

Hi Amit,
There is no other way to achieve this from the Infoset....
As suggested by Tulsi.. u can include them in the DSO level.. but it requires enhancement and reloading etc.. and its costly..
Or is it possible to join the master data infoobject if the design works out.. but this also depends how many number of Attributes from how many number of MD that u are looking into..!!
Thanks
Hope this helps

Navigational attribute problem

Hi all,
Its really strange to say like our master data is getting changed automatically,
for material master data we are loading from ODS in that material their is one nav attr field, when we load some data to that material object it is showing correct data
source
material--versionchange flagflag(nav attr)--
value
12345--AD0--
1000
12345-- MI9--
1500
After attr change run
material--versionchange flagflag(nav attr)--
value
12345--A9--
1500
But after some time(4 to 5 hours)
material--versionchange flagflag(nav attr)--
value
12345--AD0--
1500
12345-- MI0--
1500
see that flag has changed to 0 again.
This material object is loading from only 1 ODS,
is there any chance of changing data like this with out any loads,
but actually M version data is changing so we cant expect any attr change runs,
if the data is changing due to some other issue how to find taht one.
Thanks,
Pavan.

This sounds to me like there is some ABAP running in background that is changing the data directly on the DB table. I would switch on a DB trace in transaction DB01. There you can check which user is manipulating the BD table at which time. You can then check if the user has started a program or if there is a job running for this user at a scheduled time.
Best regards
Dirk

Bex Query's(Composite Provider) Navigational Attribute Error

Hi All,
We have created a BEx query on top of a Composite Provider. In the Composite Provider, we have a few common Navigation Attributes in all Info Providers.
Whenever we tried to show a particular Navigational Attribute (G_TIC9030) in BEx query (RSRT), we will receive the error messages as below.
This problem doesn't occur if we created another test query on each Info Providers of Composite provider. All test queries are able to return result and are showing all the navigational attributes without any errors.
Any idea on how to fix this?
Regards,
Kang

As discussed Kang this looks like the problem described in OSS Note 2019244.
It's not unusual to find a few of these problems in testing.

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

Unable to add Navigational attribute in Qery

Hi All,
Am a beginner in Bex queries. I need to add a Navigational Attribute, in a BEx Query. I did the following:
1. Turned ON the Navigational attribute in the Infocube.
2. As my query is on Multiprovider, i had mapped the specific field as well.
3. In the query, the 'Attribute' folder is added to the particular charcteristic in the infoprovider panel. When i try to drag to the navigational attribute into the 'Free Characrteristics', its not working out.
Am not sure about the procedure for adding the Navigational attribute into the Query. please help me in resolving this.
Thanks,
Chitra.

Hi Chitra,
Check if the navigational attribute is already there in Rows or filters area. it can't be in 2 places at a time.
First make sure the Attribute is navigational enabled at info object level.
Enable the object as navigational at IC level.
as you are using MP... you need to enable the navigational attribute in the MP and identify the object then you will be able to use the navigational attribute in the query.
Regards
KP

F4 Input values for variables based on Navigation Attributes

Hi,
We would like to use the option "Q Only Posted values for navigation" from the set F4 mode 'Query Execution Filter Val. Selectn' in the Multiprovider specific properties.
The problem is that this option Works for Infoobject stored on the infocube, but It doesn't work for Navigation Attributes.
Question : Could you please tell us how to use the option "Q Only Posted values for navigation" with _Navigation Attributes _ ?
Thx.
Radj.
Edited by: Radjech Radjech on Nov 24, 2011 2:22 PM

Hi,
The input help only offers values for which you can select data in the current navigational state
Check the below link ,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20ecb78c-374a-2d10-c6af-f024f19b785d?QuickLink=index&overridelayout=true
Only posted values for navigation - what does it mean?
Regards,
Satya

"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

Problem with Navigation Attributes when upgrading from BI 3.1 to BI 7.0

Hello,
I have the following problem that occured regarding queries during the upgrade from BI 3.1 to BI 7.0:
As far as the queries are concerned it is not possible in the 7.0 system to completely rebuild them according to the queries in 3.1. More specifically this refers to a certain number of navigation attributes that cannot be integrated into the query. In this case the following error message appears: "Error in BW: Missing mapping partprov cha <-> multiprov cha". Moreover, this error message only appears when you try to include navigation attributes into the query that are all attributes of the same specific InfoObject.
I have already checked in the 7.0 system if the relevant objects have the status 'active' and if the identification between the Multiprovider and the InfoObjects used is correct. So, is there anybody who may has another idea why this error message appears respectively who experienced the same/similar problem?
Thanks in advance & Regards

Hello Martin,
yes, I've also checked the identification in the MultiProvider for the navigational attributes. There is nothing missing.
I've also reactivated the objects.
Do you may have another idea?
Thanks and regards, Ines

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.

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

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 Problem in Input Query

Similar Messages

Maybe you are looking for