Sage 100

 View Only
  • 1.  OM Labor update error

    Posted 10-21-2025 16:11

    Hi,  Have a client on Sage 2020 with OM and they are getting an error 43  in the labor update which usually means there is more than 99 hours for a employee.  Not the case here as there are only about 10 hours total for the day.   I do see a punch in and out that has no work ticket assigned - wondering if that is the issue.  Any suggestions on  what to look for would be great..



    ------------------------------
    Bob Osborn
    Senior Consultant
    DSD
    7142645278
    ------------------------------


  • 2.  RE: OM Labor update error

    Posted 10-22-2025 07:45

    I don't know a lot about OM, but I would look for a numeric field that is really really large.  Is there some unit of measure conversion or labor rate causing the dollar amount to be more than 99,999,999.9999 or something along those lines?  

     

     

     

    **************

    David Overholt

    DWD Technology Group, Inc.

    9921 Dupont Circle Drive West, Suite 300 | Fort Wayne, IN 46825

    260.423.2414 main

    260.399.8655 Direct

    800.232.8913 toll free

    sagesupport@dwdtechgroup.com

    www.dwdtechgroup.com

     

    A black background with white text  Description automatically generated

     






  • 3.  RE: OM Labor update error

    Posted 10-22-2025 09:53

    Do you have the full message with program specifics?  Have you searched the JobOps Partner Portal?  https://portal.jobops.com/search/



    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------



  • 4.  RE: OM Labor update error

    Posted 10-22-2025 11:37

    Hi All,  NORMALLY this error has to do with too many hours (or I was told it could also be too many entries) but neither case existed here.  The hour total was on only about 10 hours.  The JobOp KB only mentions too many hours for the error.   But in reviewing the entries, I noticed that all the work tickets were in History already but the labor record has a flag for "workticketinhistory" which was set to N for them all.  I changed them all to Y and the batch updated.   Advised the client to be careful about this (since the program is not smart enough to figure it out).     Thanks for all the suggestions!



    ------------------------------
    Bob Osborn
    Senior Consultant
    DSD
    7142645278
    ------------------------------