This content has been marked as final. Show 4 replies
try to execute the back end SQl in Source and check for which Condition is missing data..need to do some debugging to know what happened afterr load..
Please check how those conditions were used in SQL queries fired to DB and also see if you get any data for those conditions from DB.
As you guessed, the data load on the Essbase might have caused the problem. The measures must be missing in the essbase cube for this combination of the dimensions.
To debug, remove one of the dimensions from the report and test it. Thus, you would be able to figure out the problem causing dimension.
Hope this helps !
Hi User, Vijay,
Yes I have checked the generated SQL queries and the MDX queries as well. Both queries are generated as expected, but returns no result.
But now I have found out how these two different dimensions are different from my other dimensions. Only these two dimensions have a SORT order logical column defined in the BMM layer- which I think is causing the problem, BI Server not able decide which column to sort. So, the sql gives result when I cimment out one of the SORTKEY
"PSS Essbase"."Accounts"."Accounts" s_1,
"PSS Essbase"."Operative Hierarchy"."Operative Hierachy" s_2,
-- SORTKEY("PSS Essbase"."Accounts"."Accounts") s_3,
SORTKEY("PSS Essbase"."Operative Hierarchy"."Operative Hierachy") s_4,
"PSS Essbase"."Facts"."Measure" s_5
FROM "PSS Essbase"
((("Operative Hierarchy"."Operative Hierachy" = 'Europe') AND ("Accounts"."Accounts" = 'Gross Margin'))
OR (("Operative Hierarchy"."Operative Hierachy" = 'Russia Focus Country') AND ("Accounts"."Accounts" = 'Sales ASP')))
ORDER BY 1, 5 ASC NULLS LAST, 4 ASC NULLS LAST
FETCH FIRST 65001 ROWS ONLY
Any views on what happens when we use two dimensions in the same report which have sort columns defined in the repository...