Incorrect date format between provider and queries

[silvio_messias]

Hi BW experts!

I have a key figure (last date) defined as DATS and aggregation defined as MAX.

In my provider the data was storaged correct, as following above:

(dates in format dd.mm.yyyy)

. Customer 1, last date 21.03.2006;

. Customer 2, last date 10.03.2006;

. Customer 3, last date 26.01.2006.

But, in my queries (by EXCEL) these data are showed so:

1 | 21/03/2006

2 | 03/10/2006 (incorrect, correct is 10/03/2006)

3 | 26/01/2006

I checked my pc and SU01 configurations. In both of them there are date format dd/mm/yyyy.

Anybody can help me. please?

Thanks,

Silvio Messias

[Former Member · Accepted solution]

Hi

I have not seen this problem, but I would suspect it is the agg on the date that is causing this.

try to remove it and see what happened?

Also, if the data is grouped try to drill in to see if indeed the dates are summed up.

I hope it helps.

Reg's

Edan

[silvio_messias · Accepted solution]

Hi Edan, thanks for your answer.

But, I don´t think so. The SAP Help says "Minimum and maximum can be set, for example, for date key figures."

(http://help.sap.com/saphelp_sem40bw/helpdata/en/75/21054da1392649948e5b94e4fc4bce/frameset.htm).

The fact is that I need the last customer´s purchase and I use this key figure to do this. My scenario is a ODS that contain all purchase documents and a CUBE aggregating these data.

If I remove this option I don´t have the result that I expect.

Do you have any idea?

Thanks,

Silvio Messias.

[Former Member · Accepted solution]

Hi Silvio,

Are you sure you don't have 10/03/2006. Can you see if you have two dates 03/10/2006 and 10/03/2006? I was thinking of some alternatives.

Regards

[silvio_messias · Accepted solution]

Hi George,

I checked my provider and I didn´t find 03/oct/2006 for this customer.

There is only one record with 03/mar/2006 and the system show me this as 03/oct/2006.

Regards,

Silvio Messias.

[silvio_messias · Accepted solution]

Edan, your answer showed me the best way! I attempted against aggregation parameters and solved the problem. Thanks!

The parameter "Exception Aggregation" was "maximum". So, I modified this for "last value" and used aggregational behavior (0calday).

Before, the configuration for this KF was:

Aggregation: maximum

Exception Aggregation: maximum

Aggregation Behavior:

Now, is:

Aggregation: maximum

Exception Aggregation: last value

Aggregation Behavior: 0CALDAY

Thanks!

Silvio Messias