Sage 100

 View Only
  • 1.  FYI - We have found two MAS 90 4.50 bugs that are

    Posted 10-07-2011 10:21
    FYI - We have found two MAS 90 4.50 bugs that are pending fixes. One has to to with Payroll. Deductions based on Regular Hours Worked do not pull into payroll data entry as auto deductins after being converted. The problem seems to occur with Deduction Codes based on Regular Hours Worked when the description is in all capital letters. The other problem is when converting Crystal forms and reports. The error message is - Failure: a minimum crytals print engine version 11.5.0.0 is required during conversion. Resolution is to copy the CRPE32.DLL file from C:\Program Files\Business Objects\Common\3.5\Bin into the C:\Windows\System32 folder The other problem we had was Bank Codes converting without description and general ledger accounts. This is a data issue. There were blank Bank Codes in data files.


  • 2.  RE: FYI - We have found two MAS 90 4.50 bugs that are

    Posted 10-07-2011 11:26
    I posted this question on the The Community also - What was the severity level assigned to these? Are we to expect a hot fix or in the next scheduled PU or some day when they get around to it? I would expect these to be hot fixes but one never knows with Sage.


  • 3.  RE: FYI - We have found two MAS 90 4.50 bugs that are

    Posted 10-07-2011 11:39
    The Payroll bug was only given a severity level of 4. However, I was told that a hot fix would be hopefully released soon. The Crystal conversion bug was given a severity level of 3. I do not anticipate a hot fix, probably will be fixed in the Product Update.


  • 4.  RE: FYI - We have found two MAS 90 4.50 bugs that are

    Posted 10-07-2011 13:48
    Will have to keep our fingers crossed. Based on my past experience, I am not holding my breath!!!!! oSeverity 3 - Recognized as a medium impact program issue which is not expected to have a significant adverse effect on the ability to process data for most customers, or at least one acceptable workaround for the issue exists. Correction is normally considered for the next major version release. oSeverity 4 - Recognized as a low business impact program issue which typically does not have a significant adverse affect on the ability of any customer to process data. The issue is monitored on an ongoing basis to determine whether or not other customers encounter similar scenarios, and correction in a future version release is considered accordingly.