Has Sage stopped issuing PU support for 2018.x Job Cost?

SOLVED

Despite 2018 being on the list of the supported versions, I am having a hard time finding where a fix was issued on version 2018 for this bug: 

Error: "Record: J/Cxxx is missing from SY0CTL.SOA" or "Error 11 SWVDTE 0520" or "The J/C Accounting Date (MM/DD/YYYY) does not fall within the Current and One Future Period for the module" when accessing Job Cost tasks  ( Link

I believe I was able to find the fix released in 2019.3 as DevID 111506 Knowledgebase ID 101930

However, I haven't been able to locate the same fix in the latest 2018.9 product update.

Shouldn't 2018 have received the fix or are only selective fixes issued for 2018? And if so, why is it selective for a product listed as being fully supported? 

TIA

  • 0
    SUGGESTED

    The last PU with program fixes for 2018 was PU8 (August 2019).  PU9 and the upcoming PU10 contain only hot fixes that were released and A/P year end changes.  That said I'm checking if we can get a hot fix for this issue for the 2018 release.

    Thanks John  

  • +1 in reply to jcnichols
    verified answer

    Hi Wayne. The program correction will be included in the next 2018 PU10.

    I can process a hot tip if needed, you can safely copy ...\MAS90\SOA\swvdte from a 2019 PU3 installation to the 2018 system to resolve the error. Thanks John

  • 0 in reply to jcnichols

    John, when is PU 10 scheduled for release?  Will this be a June update or September.

  • 0 in reply to btmlinesoft

    The earliest would be September. It's depended on the 1099 changes.

    Thanks John

  • 0 in reply to jcnichols

    Thanks, John that is good info. I'm still not altogether sure what "supported version" means to Sage. In the past I understood it to mean that any release within N-x would receive a full product update. I admit that I never fully compared one version's PU to another to see if that was the case. 

    In this instance, it seems like a large number of Job Cost fixes made it to 2019.x but only a couple into 2018.x

    I'm a big advocate of staying on current releases. However, as the installed base of Sage users trends toward 10+ user sites with 3+ enhancements ( and that's usually a baseline ) installing upgrades is not that easy because not all ISVs are ready/stable within a reasonable time. And there are sometimes prominent Endoresed ISVs lagging 6+ months from Sage 100 release date making it almost impossible to plan for an upgrade timeframe agreeable to the customer.

    Therefore there are instances where we have to lumber along in 2018 or 2019 ( N-1 or N-2 ) which makes the ability to obtain a full PU important to those customers.  

    Thank you and everyone in the engineering area fo your help and support - it is greatly appreciated!