>>>>Right, but I don't have much info myself. I have an escalation from the client, our client service people checked the stored procedure results that is used for that report. It returned 1 row with sum_cost = 0. That's why this 1.91 value in the report is so strange. I've checked the report file (and the class that generated the report). The report uses a variable which is set to use nvl(sum_cost, 0) as expression with the initial value of 0 and SUM option. It doesn't explain this mystery.
>>>
>>>check the variable.
>>
>>What do you mean?
>
>put code to log the variable value into a file and get it.

You're still clear as mud. How do you record a variable in a report? Besides, I'd rather not change the application at all - any ideas of keeping the existing code and identifying the problem?