Report Bursting (Profile Publication) issue with Webi Report

[Former Member]

Hi BOBJ Gurus,

We are facing a very strange issue with profile publication in BOBJ. We have created roughly 12 reports in Webi and we publish all of them using Profile personalization (Report Bursting).All these reports use SAP BI/BW queries as source. All reports work fine with publication except 1 report.

This report is about Customer Trend and we show customer trending for last 13 months along with measured key figures like YTD quantity and YTD amount for each customer. This report data is refreshed every month in SAP BW/BI and every month report should pick YTD value for current reporting month. So following is how our report is:-

                       Oct-11      Nov-11      Dec-11      Jan-12     Feb-12     Mar-12     Apr-12     May-12     June-12     July-12     Aug-12     Sept-12       YTD Quan.   

Customer 1  10               20               30               15          10               20               10          20               15               20               10          10                   190

As you can see each month has an associated quantity and it also has asscoiated YTD value coming from SAP BW/BI. Since we need to show YTD values for current reporting month only, we have used function called LAST in Webi formulas to pick current month record for each customer and get measured value of YTD quantity associated with picked up record.

In above example 190 is correct YTD value what it shoud show but instead of picking current reporting month based on LAST function, when we run report with profile publication, it randmonly picks up different month records for customer (Say in this example july-12) and shows YTD value as 170 instead of 190.

Strange part is that it works fine when we run report online or scheudled it with Prompt values. It DOESN'T work fine when it runs with profile publcation.

Has anyone of you encountered such issue? Please suggest appropriate resolution.

Thanks,

Satyen...

[former_member184594]

LAST function does not really return the latest day or value in your data set. Instead it returns the value which is returned last from database. In some cases, it might be returning the right values for some customers and in others it will return wrong ones.

I didn't understand what your mean by "it doesn't work fine with prompt values when it runs with profile publication." Would you provide what error message you are getting?

[Former Member]

Thanks Zahid,

You are right that LAST function will provide values which are returned last from database but our issue is that our report shows correct result when it is executed online or scheudled to run with Prompt values but it shows incorrect result when same report is esecuted with profile publication. There is not ERROR message which we receive but it is wrong values whcih are reported in published report when report is published using profile.

Initially we thought it could be a problem with report size as when you run report with publication, it picks up ALL data before it applies profile filteration on reporting side. But we played around with # of records settings in Universe and Report but it didn't change anything for us. Moreover when we online run this report wide open (Without any filter with prompt values) it provides correct result.

So our understanding is that there is some type of limitation or issue with profile publication which is causing issue with data.

Does it make sense? Please let me know if you need anyother information. I'd appreciate if you have an idea about this issue and let us know appropriate resolution.

Satyen...

[former_member188911]

Zahid is right. you may have correct results in some circumstances just by chance.

If in BI4.0 have you tried to consider RelativeValue() , it could be of help

thanks

SC

[Former Member]

Simone we are on XI3.1 SP3. As I said data is correct when we run report online or scheudle with prompt values but same report shows incorrect result when we run with profile publication.

[former_member188911]

Hi Satyendra,

Zahid gave you the right answer there is not much you can do about this.

The reason why you get different behavior is because the process flows within the calculation engine are slightly different however you are using the Last() function as it is not intended to be.

Thanks

Simone