Open Forum

System Message 118 - Overflow in Floating point, number to large

  • 1.  System Message 118 - Overflow in Floating point, number to large

    Posted 12-05-2017 07:46 AM
    The client is receiving the following error message when running either the Financial Transaction Transfer (FTT) or the Close Period process in Project Controller. This error does not stop the process from completing but is showing every time the process is run.

    z8EvnxaUTbGBWlZ5BoFU_SM118.png
    The client is a multi-currency type of client and is currently working with translation of currency between USD and Chilean Peso. The exchange rate is about 670 Chilean Pesos for every US dollar. This client deals with multi-million US dollar contracts so the translated amounts can into 10 to 12 digit range.

    I have run a SQL profile on each process but the profile results does not return any errors in the file. MS Support is saying that it is an issue with an amount that is not rounded correctly but finding that entry (new or old) is a proverbial needle in a haystack since you need to review all transactional records across multiple modules (AP, GL, AR, PO, etc.) to find a single bad transaction.

    Does anyone have any ideas of where to look for the bad records.

    All help is greatly appreciated


    ------------------------------
    David Safstrom
    Senior Consultant
    NexTec Group
    Roswell GA
    ------------------------------


  • 2.  RE: System Message 118 - Overflow in Floating point, number to large

    Posted 12-06-2017 10:16 AM
    Dave,
    Check the ProjCuryID, ProjCuryBudMulitDiv, ProjCuryBudRate fields in the PjProj table.  I had a client who had trouble with entering project budgets and was receiving same error.

    Steve

    ------------------------------
    Steve Martin
    SL Product Manager
    Intellitec Solutions LLC
    Wilmington DE
    ------------------------------



  • 3.  RE: System Message 118 - Overflow in Floating point, number to large

    Posted 12-07-2017 08:43 AM
    If you do not use the project cury functions you could run mass update to set the cury amounts = to the non cury. There was a bug early in sl2015 where the cury amours were calculated using the budget units. 

    Sent from my iPhone