We are using QAAWS version 12.1.200.882 (BO Xi 3.2).
We need to know the last startdate of the conditions of a contract before a certain date, which is past as a parameter/prompt.
In the query we use a ranking to get the last startdate with a filter on that startdate so that we get only dates before the date from the parameter.
In QAAWS when you test we get the right result. But when we test it in Xcelsius we get the wrong result.
We ran multiple tests and discovered that the filter is being placed outside the ranking. So during the publication of the QAAWS it is generating something else then that is shown during testing.
Does anyone knows about this problem and/or has a solution?
What is the reason you are saying it is a bug in Xcelsius 2008 SP 3?
All prompts are used from Xcelsius into QAAWS. Xcelsius is just gettin the data from QAAWS. We have build the same query in Webi and used it to test it directly on a Oracle database. By changing the place of the conditions outside the ranking, we got the same (bad) result as the QAAWS. That is why we have learned the bug is in QAAWS.
The ranking by the way in Webi was fine and showed the good result.
I made exactly the same query in Webi and checked the SQL directly against the database. I used the ranking part and made it a standard filter in the universe. Then I applied the standard filter against the QAAWS and it gave exactly the same output.
You are right about the aggregated property, it is used inside the Webi report. But if you use the SUM-function around the object the Webi report will still act the same and QAAWS will report exactly the same. Due to the SUM-function a GROUP BY clause will be used and generate only aggregated data and therefore less rows.
About the rank by date, we just use the option “desc” to give the last date the highest ranking and then select the highest ranking. Ranking by MIN(date) is not what we want.
(BOB member since 2010-02-17)
(BOB member since 2010-07-08)