Symptom: Customer runs a Statement of Revenues and Expenditures that includes a custom column called Percentages. The report does not run and produces the error message below.
Product Line:
The results of your search are shown below. To refine your search, revise your keywords, and/or select the appropriate check boxes to the right.
Symptom: GL report can show a zero beginning balance on every other line of the report
Conditions: Running a standard or expanded GL report
Product Line:
Symptom:
When using ‘Substitute G/L Report Group Set for G/L Codes’ in conjunction with ‘check Available budget during Posting’, nothing is allowed to post.
Product Line:
Symptom:
Error received when running leave history report: A constant expression was encountered in the ORDER BY list, position 3.
Product Line:
Symptom: After a partial disposal of the asset the accumulated depreciation on the summary asset ledger is incorrect. It does not match the Maintain>Asset form or the asset transfer register. Prior to doing the partial disposal it did.
Product Line:
Symptom: Customer is attempting to run either a State MT UT-5 or a Federal 941 for the 3rd quarter of 2010. When they run it they get an error message “Error Processing Data File” in the collecting employee information.
Product Line:
Symptom: Printing a security list report is incorrect; users with only executive view rights appear to have full rights to all modules and transactions.
Conditions: Running security report and having executive view.
Product Line:
Symptom: After importing a fixed width file using a T1 DEF file specifying online Post (OL) only the first document shows in a posted transaction report. If the DEF file is edited to a Batch to Post (BP) all documents in the .txt file import and post correctly.
Product Line:
Symptom: Customer runs a Statement of Revenues and Expenditures that includes some date override custom budget columns. Those columns produce zero amounts even though there are amounts posted to the budget periods being covered in the custom column.
Product Line:
Symptom: When a user exported a normal trial balance in version 10.2.x, the GL account code exported as a non-text field, on which formulas could be used.
Product Line:
Symptom: The Comments field on the Create/Modify Purchase Orders screen no longer left justifies subsequent lines, it just places all of the entries into one really long line. Hitting the enter key moves the entire line down instead of just the curser for a new line.
Product Line:
Product Line:
Symptom: Customer is set up for invalid account code combinations on a GL and Restriction Segment (Operating Unit).
Product Line:
Symptom: Multiple vendors are set up to receive EFT payments. Some vendors continue to receive checks despite the conditions being correct to receive EFT.
Fixed in v2014.0
Product Line:
Symptom:
...
Product Line:
Symptom:
After running DIC’s it was noted that ENC41 and ENC 42 failed. The encumbrance rebuild was run and DIC’s were run again. ENC 38 then failed. Subsequent re-running of the rebuild failed to correct the issue.
Product Line:
Symptom:
Receive error: there are no earning associated with Deduction Code:<deduction code> to generate the distribution.
Product Line:
Symptom:
Scrolling is slow to respond when detail is lengthy.
Product Line:
Symptom:
Editing format for bank account display from Default to Last 4 Characters Only, does not save.
Product Line:
Symptom:
Import uses employee pay rate instead of using the rate on timesheet that exists on the employee’s default timesheet.
Product Line:
Symptom:
Summary asset ledger with net book value column included on a disposed asset shows value although it should be $0.
Product Line:
Symptom:
Error “<segment> is required” is received when trying to transfer depreciation.
Product Line: