Decimal overflow error in Inventory batch job

Arturs
Arturs Member Posts: 30
edited 2005-11-21 in Navision Attain
I'm using Navision Attain 3.10 with all Hotfixes.

The problem is when executing batch job "Inventory => Periodic Activities => Adjust Cost - Item Entries" Decimal overflow error runs. This error runs for only one item.

Any suggestions :?:
Regards,
Arturs Gedvillo
CTO

Comments

  • Luc_VanDyck
    Luc_VanDyck Member, Moderator, Administrator Posts: 3,633
    I once had the same problem. When you look at the Value Entries of that Item, you'll see some large values. Correcting these values will solve your problem.
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • Arturs
    Arturs Member Posts: 30
    Luc Van Dyck wrote:
    I once had the same problem. When you look at the Value Entries of that Item, you'll see some large values. Correcting these values will solve your problem.
    Amounts for this item in Value Entry are about 300.00. I don't think it's large and can cause any trouble :?

    ANy other ideas?
    Regards,
    Arturs Gedvillo
    CTO
  • Robson_Gowero
    Robson_Gowero Member Posts: 1
    When we run the Adjust Cost - Item Entries batch job (Navision 3.70) we get a decimal overflow error.

    We have used the debugger and established that it occurs when creating the G/L Entry in Codeunit 12 Gen. Jnl.-Post Line in the function named FinishCodeunit() and is because some Amount value is too big. We have not been able to determine how such huge figures are generated or what part of the data is giving problems.

    I have searched the navision forum and have seen that other people have encountered the same problem. However the solutions which are being offered are not detailed. For example one says you need to take a look at the value entries of the specific item and correct them if they are too big. I have run the value entry table and have not been able to find huge amount figures which are unrealistic. Besides entries in the value entry table are system generated. Then on what basis do I correct them or if they can be corrected at all how do I do it without corrupting my database?

    Robson Gowero

Categories