• PL_JournalPDFLog.M4T *** File discrepancy

    I am trying to apply the Sage 2020.1 update. During the update, when it scans for corruption it says that PL_JournalPDFLog.M4T has an ambiguous "file discrepancy" in it. The instructions say to simply Rebuild Key Files for any discrepancies, but alas…
  • General Journal Posting - duplicating

    Has anyone run into an issue with a general journal posting that occurred months earlier now showing a different result if you were to run the report today? In January we had one entry, and if we run the report today, it shows 3 of the same entry. For…
  • Duplicate Item Numbers

    Hello, I was wondering if anyone else ran across this issue and if so, how it was resolved. We have identical item numbers that appear when we search for an item in item inquiry and item maintenance. Selecting one of the item numbers results in…
  • Open PO Qty vs On PO qty discrepancy

    Hello All, We are using SAGE 100. Somehow On PO qty coming in Stock status report is not Open PO Qty. SAGE is pulling a open PO qty from somewhere - SAGE ppl kindly share your thoughts In the below example, in main I m seeing a open PO qty but in…
  • What does Commit Check Clear Utility actually do?

    I recently found a discrepancy in values between the quantities tab and the cost detail tab within Item inquiry on a few items. After researching in the Knowledge Base, I came across the following steps to clear out the issue: Update all transactions…
  • Inventory Categories. Data Corruption? A mystery

    Sage 100 Version 5.20 Crystal 2011 for Sage Window server 2012 R2 Ok, here is an odd one. We had been having incorrect data running a Inventory List via Crystal. We have a total of 600 items. When I add a filter for Category 2 data I am getting…
  • Sage 100 BoI corrupt records with extended ascii

    We're currently on Sage 100 2014 (Non SQL) and we're currently running into the issues where we are being sent names containing certain ranges of extended ascii characters. For now, we are going to limit ourselves to the first 127 in the ascii table…
  • Providex ODBC Invalid Date - Corrupt Date?

    Have an issue with what I believe is a corrupted date value. It resides in purchase order detail required date and PO header PO date. Running the open order report on "required expire date" for date greater than 12/30 will result in "Vendor Code 9"…
  • Rebuilding Key Files

    Once every 1-2 weeks I rebuild all sort files and am wondering if I should also be rebuilding the key files? Is there any risk/downside to rebuilding the key files? Also, when I am running the utility do I want Integrity Check and Optimize File checked…