BPC 7.5NW Report Issues When Requesting Year To Date Data

Question

Dynamic reports built with 2 row expansions (Cost Ctr, Account) up to 3 columns (not expansions, set to different categories with excel formulas for variance calculations...Act vs. Bud for example) result in error messages (error retrieving data and another related error messge) when requesting YTD data vs. Periodic data.  The report runs fast and properly with Periodic measure.  When running with the YTD measure, attempts to reduce the report data volume by removing comparative categories and removing formatting (after ranges) still results in YTD data retrieve errors.
Has anyone else had similar issues with BPC 7.5NW, SP9, and YTD data not pulling into reports?  What are the common causes for issues with YTD data retrieval?  Given the design by SAP of the BPC NW product and promotion of using BPC for both Periodic and YTD data, should I expect this report to work properly, meaning that I can get output with YTD data without long runtimes or errors that result in terminating the report?  Thank you.

Answer 1

Hi,
This would do it :SQL> !cat q.sql
with t (dt, val) as (
     select to_date('2011/01/04','yyyy/mm/dd'), 123 from dual union all
     select to_date('2011/04/09','yyyy/mm/dd'), 234 from dual union all
     select to_date('2011/06/28','yyyy/mm/dd'), 345 from dual union all
     select to_date('2011/10/18','yyyy/mm/dd'), 456 from dual union all
     select to_date('2011/12/23','yyyy/mm/dd'), 567 from dual union all
     select to_date('2012/01/07','yyyy/mm/dd'), 678 from dual union all
     select to_date('2012/05/13','yyyy/mm/dd'), 789 from dual union all
     select to_date('2012/07/19','yyyy/mm/dd'), 890 from dual union all
     select to_date('2012/08/30','yyyy/mm/dd'), 901 from dual union all
     select to_date('2012/09/22','yyyy/mm/dd'), 012 from dual
------ end of sample data ------
select *
from t
where dt >= trunc( add_months(trunc( &&dateexec. ,'month'),-1) ,'year')
and dt < trunc( &&dateexec. ,'month')
undefine dateexecThe dateexec parameter is just here to "simulate" sysdate of different points in year.
<i>(your actual query would have sysdate where the dateexec parameter appears)</i>
SQL> @q
Enter value for dateexec: sysdate
DT                         VAL
07/01/2012 00:00:00        678
13/05/2012 00:00:00        789
19/07/2012 00:00:00        890 sysdate does the current year up to previous month.
SQL> @q
Enter value for dateexec: to_date('20120122','yyyymmdd')
DT                         VAL
04/01/2011 00:00:00        123
09/04/2011 00:00:00        234
28/06/2011 00:00:00        345
18/10/2011 00:00:00        456
23/12/2011 00:00:00        567when ran in january, it retrieves all the previous year.