cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Arithmetic Overflow error converting numeric to data type numeric in BEx upon execution.

Former Member
0 Likes
2,759

Hi Experts,

I am in a serious problem and I have to deliver this tomorrow please help me to resolve this issue. I have never encountered this error before.

I am getting this error when i am executing my query through Analyzer I tried in RSRT too but in RSRT it automatically goes to Debugger mode.

I have tried to create new fresh query also but the same issue i am facing. Also, I am not calculating anything from key figures.

Below is the error screen shot form analyzer, Please help me to understand and solution.

your input will be much appreciated.

Thanks

Ansh

View Entire Topic
Former Member
0 Likes

Hi Experts,

I am still looking for the solution please help me to resolve it.

I have read SAP Note 1557321. It is completely saying about KF and SQL.

In my problem  Dates field and KF are not working together in query run time.

If i remove Dates field upon execution its works and vice versa.

I really need help.

Thanks

Ansh

Loed
Active Contributor
0 Likes

Hi,

Why don't you open a SAP ticket? They will be your last resort if no one can answer your problem in the forum..

Regards,

Loed

Rushikesh_Yeole
Contributor
0 Likes

I think before raising SAP ticket;

Please share ST 22 dump and query formulaes ragarding to particular characteristics Date.

Are you using char as key figure?

Have you displayed DSO data with this char? (Confirm wheather data is correct for Date in all rows)

Is it cutsomized char? If so check conversion routine/data type? Check with 0CALDAY

roland_szajko
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Ansh

What do you mean under Dates field? Is this a characteristic or a key figure? If you use date as key figure ensure that the aggregation is either min or max. If its sum, then you have a problem, since the date type cannot be aggregated with SUM.

Also check the work process trace of the wp in which the query was running. The wp trace contains information about the specific SQL statement which could not be performed. Based on that, you can find the key figure which causes the overflow.

If you are using hana, the following notes could be helpful:

2080238

2078235


br

Roland