on 2010 Jul 22 7:44 AM
Hi Expert's,
I have query with restrictions as Assignment status- Missing and Upper and for Asset status -Donated,Lost,Stolen and Disposed.
But query will execute in Bex analyzer/ Execute on the web but when I execute the query through portal it is throwing an error.
When I did some trial and error exercise on this query I came to that the issue is related to the restrictions.The query works fine for the restriction Assignment status as u2018Missingu2019 and Asset status as u2018Lost u2018but for other restrictions the issue is again same.
1.Is it the issue with the query design?
2.Is the issue with the software?
Do I need to rise a OSS? please help me to resovle this issue.
Points will be definitely assigned.
Thanks,
Vasu
Edited by: vasu vassu on Jul 22, 2010 8:44 AM
Hi,
If query is ok on one application (Analyzer) then query design is correct. Issue is with application (Web/portal) or settings.
Try to execute on web through Query designer execution button, check if it is still showing error.
One more thing check if the data is available for the restirction value in case of master data. I mean the values on which you are restricting the report, the same value is there in master data or not.If not then please mantain the same.
I hope it wil help.
Thanks,
S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In query designer execution and also query on web exection works fine.For asset status we have values Lost and Stolen but other two ie Donated and Disposed are not available.But here for stolen restriction also it is throwing an error.
For Assignment status - Missing is available but upper is not available.Hope I am clear .
though there are entries I am getting same errro .but some entries are not there let me try with entries?
error message is in portal:
Here is portal error:
The initial exception that caused the request to fail was:
Java.lang.UnSupportedOperationException
Edited by: vasu vassu on Jul 22, 2010 1:32 PM
Hi,
Is this error with only this report or with some other reports as well?
Some time this occur due to java patch so check if this error is for one or more reports.
If this is with only this query then execute the query in RSRT and generate the query first. Are you getting any warning/error over there? Try these things it will provide better picture.
Sometimes removing restriction and charectristics from query saving that and add it agin works. You may try that as well.
I hope this will help.
Thanks,
S
User | Count |
---|---|
70 | |
10 | |
10 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.