How to locate invalid date in GL_DetailPosting?

SUGGESTED

Running the G/L Reculate Account Balance Utility after changing from non-calendar year to a caledar year, following Sage Knowledgebase article.  Received message "Record with invalid posting date encountered in GL_DetailPosting file.  The recalc cannot continue. OK."  Rebuilt all Key files in G/L as well as Sort files.  This did not resolve the problem.  Reviewed all 187,000+ records in GL_DetailPosting file through DFDM and did not see any Posting Date values that looked missing or invalid.  Any suggestions on how to find this particular record with an invalid psting date?   By the way, this was all done in a test company, so the "live" company is still intact.

  • 0
    Via Sage KB:

    One or more transactions were entered with an future or invalid date. To resolve this issue, please try the following:

    Verify if future years exist in Fiscal Year Maintenance.

    Open General Ledger, Setup, Fiscal year Maintenance.
    Click look up in Fiscal Year field
    Select the highest fiscal year listed
    Verify the each periods ending date are correct

    If future years exist, use the GLWURD utility to delete the future year transactions. See related article below, How to Delete Future Years and Transactions

    If future years do not exist, please try creating one fiscal year prior to the earliest fiscal year defined. (ex. if the earliest fiscal year listed in fiscal year maintenance is 2001, create 2000 fiscal year)
  • 0
    Can't say I have ever seen this in the gl detail posting file before, but my usual trick is to run a report in ranges on the data and bracketing down on it. Try printing g/l detail reports year by year. When you find a year that errors out then narrow the months down and eventually the g/l accounts until you find it.

    If that doesn't work, then try creating a crystal report on the gl_detailposting file and start bracketing in. Usually a bad date returns an error 9.
  • 0 in reply to TomTarget
    I usually find the Crystal Report option is fastest. Look at the record count when you get the error...
  • 0 in reply to Wayne Schulz
    SUGGESTED
    Thanks, everyone, for responding. Wayne, your answer was the correct one in this case. There were no future years, so I added a year at the beginning of the string of years (in Fiscal Year Maintenance). No more errors and the Recalculate Account Balances Utility successfully completed.
  • 0 in reply to Watson_Holyfield

    Interestingly enough, I just had a client where the the 2016 fiscal year did not automatically get created. Added it manually and did a recalculate and everything was good.

    Would sure love to know how that happened.  Version 2015.

  • 0 in reply to TomTarget
    I have a client who has an odd month ending date,(the 25th) with the exception of the last month of the year. One year the last month ended on the 25th also. The new year started on the first of the month, so there were 11 days that did not fall in any year in Fiscal year maintenance and the same problem occurred. When they correct year end date was entered, those dates fell in a defined year and all was well.