truncation error in process log

[Gary Atkinson]

First, I did do a search and found someone had logged a similar issue earlier.  I am seeing the following error in our “charges” process”

[msg :RecF:WARN/0:charges_xlate:04/02/2007 06:08:30] Truncation occurred on decimal part of numeric value 250.000

[msg :RecF:WARN/0:charges_xlate:04/02/2007 07:31:11] Truncation occurred on decimal part of numeric value 600.000

[msg :RecF:WARN/0:charges_xlate:04/02/2007 08:07:35] Truncation occurred on decimal part of numeric value 500.000

Weird part is I do not have a thread named “charges_xlate”.  I believe the reason this error is occuring because their is a string comparsion on a numeric field somewhere in some xlate.  We went to 5.5 a few weeks back and we didn’t  see this error before on 5.2.  What is the best way to track down, which xlate is causing this error?

Topic

[James Cobane]

Gary,

The ‘charges_xlate’ is not referencing a Xlate file; it is informing you that the error is occurring in the translation thread of the ‘charges’ process.  Take a look at any inbound threads within the ‘charges’ process and review their routing to identify the potential Xlates causing the error.  If you turn up EO, you should be able to more quickly zero in on the actual Xlate causing the problem.

Hope this helps.

Jim Cobane

Henry Ford Health

[Gary Atkinson]

Found the messages that are causing the truncation warning.  I looked in the xlate for the thread and see the values in the warning stem from to possible fields FT1:10 or ZPM:11.  Field 10 in FT1 is just a straight copy.  The ZPM segment is not translated at all.  We tried takening the ZPM out of the variant totally, but cloverleaf complained that the segments were now out of order.  Could it be that there are 3 decimal places in the value? Any other suggestions?  😕

[Author]

Replies