October Recap
USAS-R Releases
Bug Fixes
Corrected a problem that prevented removing budget ledgers when June is reopened. This bug could cause the carryover amounts to appear inflated. SSDT had previously sent out a message discouraging districts from reopening the prior fiscal year. Once this release is installed, districts are free to reopen the prior fiscal year as needed.
Removed a debug comment from the application log. This removed an INFO row that would previously be added in the App Log each time the Account grid was loaded.
Patches
Created a patch to remove a requisition from workflows that was no longer synced for a specific district.
Improvements
Created rules to prevent posting budgeting transactions if the accounts are inactive. There is one rule for each the budget and revenue side. The rules will look at the account and parent accounts and prevent posting budgeting transactions if the accounts are not active.
org.ssdt_ohio.usas.model.budgetTransaction.BudgetTransactionRequireActiveAccounts
org.ssdt_ohio.usas.model.anticipatedRevenueTransaction.AnticipatedRevenueTransactionRequireActiveAccounts
https://mcoecn.atlassian.net/browse/USASR-5073 This rule is set to be reviewed further. If districts encounters a "rollback" error when attempting to apply Proposed Amounts or attempting to update an account to inactive, the rules can be disabled on the Rules grid by unchecking Enabled box. Make sure to click Activate on the Rules grid after the change.
Removed the ability to select the columns to appear in the report bundle grids visible when you create a new report bundle. The menu icon previously on the top right of the grid is no longer available to allow removing columns from the grids that show in the report bundle UI. Any users who previously had problems getting the columns to display will now be able to see all of the columns.
The Duo 2FA Implementation was modified to only be required through the User Interface
SOAP calls and direct report downloads will only require a username and password
The Two Factor Authentication flag on the User is modifiable via the admin role only.
Internal
Added an annotation to a repository method that was previously missed.
USPS-R Releases
Date | Version | Type |
---|---|---|
Oct 7, 2022 | 6.76.0 | Regular |
Oct 21, 2022 | 6.77.0 | Regular |
Oct 28, 2022 | 6.77.1 | Hotfix |
Bug Fixes
Multiple bug fixes in the W2 form printing service
Box 19 (YTD deduct total from all CITY Payroll Items) was not populating correctly
Overflow forms were not being included (when somebody has multiple items that span across a second form)
If there was no employee on report, it did not let you know. It just opened the form and stayed open.
If print employee using Google Chrome or Microsoft Edge document, You could see all employees. If printing using Acrobat Adobe you would only see 1st employee and blank forms for remaining employees (only field headings show; no employee data shows).
Some box 12 codes/amounts were missing for employees. Appeared to be the ones that were added as adjustment journals to Federal such as adoption, life insurance, etc.
Box 12 items did not overflow
State items did not overflow
Pay Report - was not showing advance error adjustment amounts for Employer STRS when in advance.
Employer Distribution - When processing a retirement item (Employer STRS/SERS) if there was a position level withheld for the SERS / STRS item, then some amount of the position level gross was not valid for the Employee Level withholding.
Earnings Register - voided refund transactions were not showing as voided on the Earnings Register Report
Prevent deleting Payroll Item when an error adjustment exists on the item--
Mass Change Service - mass change for Payroll Item Error Adjustments was causing an issue loading Payroll Item user interface
EMIS Contractor with a missing compensation prevented the extract report from completing.-- Update existing record with current compensation, or delete the old one and create the EMIS Contractor record
Improvements
Extract Payroll Item Error Adjustments into a new Entity
Error Adjustments and Employer Error Adjustments now have their own grids that can be found in the Core menu.
This will allow for greater filtering and reporting of both processed and outstanding error adjustments.
You can still interact with error adjustments from the Payroll Item Edit window, but the grids had to be moved to the bottom of the window.
SOAP Service - return payroll beginning date and payroll ending date with payments. Previously they were not being returned and that effected KIOSK pay slips
Payables Summary Report - add excel & csv options
Payables Detail Report - add excel & csv options
Duo 2fa is only required through the User Interface
SOAP calls and direct report downloads will only require a username and password
New Features
New Pay Distributions Grid
Similar to the changes we made with the new Payroll Accounts Grid
Each Pay Distribution will be displayed in the grid and allow for filtering.
has all fields currently available for filtering
Like the New Payroll Accounts grid, a grid Report option will eventually be available
W2 Form Printing
A new tab has been added to the W2 Reporting view to print W2 Forms.
This option is for legal sized pressure seal W2's
The W2 report tab form option should be used to create any 8.5 x 11 forms needed.
Still to come...
A job to schedule the form generation
Merging thousands of pdf's is time consuming, to help with this there will be a job to process the forms in the background.
A job to create individual pdf for Kiosk
This job will create an individual pdf for each employee and store them in the file archive to be accessed by the Kiosk.
YTDRPT Replacement–Reports>YTD Report
Inventory Releases
Bug Fixes
Reports:
Fixed Asset By Source report
Updated to look for the item's asset_fund if the acquisition account code fund dimension is blank. If the fund cannot be determined the item will be listed as having an INVALID fund on the report.
Corrected a problem introduced on the 1.25.0 release that caused the Fixed Asset by Source report to incorrectly inflate values. The problem was caused when trying to retrieve the fund associated with an item when the acquisition's fund is blank/zero and the fund dimension of the account code is left blank. It has been corrected to display the fund's value on the report even if the fund is not defined in Core→Fund.
Please be aware, if the fund dimension of the acquisition's account code is blank/zeroes, it will currently show as INVALID on the report. (We have since created INV-408 to improve this)
Schedule of Change In Fixed Assets report
Detail report wasn’t including neg acquisitions but the summary was. This has been corrected.
The Function and Asset Class report types were not including the adjustment amounts for transfers correctly (on both summary and detail). These were corrected to look at the Fund transfers and include those items that changed fund type
updated the transfer amounts to be the original cost if there are no acquisitions for the item
Schedule of Change in Depreciation
Summary wasn’t include all acquisitions correctly. This has been fixed
Depreciation values for disposed of items in the current fiscal year should depreciate up through the disposal date only. This was fixed. Previously the system was calculating depreciation for the full fiscal year.
On both Schedule of Change in Fixed Assets and Schedule of Change in Depreciation
Items that were both acquired and disposed of in the current year were not reporting acquisitions amounts correctly. This has been fixed.
Disposition adjustments were showing up as a positive value instead of a negative value. This has been fixed
Book Value:
Corrected a problem where FTD depreciation was being calculated for items that were fully depreciated and had a LTD of zero.
Depreciation values for disposed of items in the current fiscal year should depreciate up through the disposal date only. This was fixed. Previously the system was calculating depreciation for the full fiscal year
Important: if you had items that were displaying incorrect depreciation amounts because the items were both acquired and disposed of in the current year, you should
for previously closed fiscal years, reopen and close the fiscal year to recalculate depreciation values
for current fiscal year items the depreciation will be correct, you can confirm by running the Book Value and Schedule of Change in Depreciation report
Transaction>Items
Depreciate option: Updated to correct problem with FTD depreciation. Only impacted districts who had used Depreciate button. The current year LTD depreciation is correct, but the FTD depreciation was not calculating incorrectly; for fully depreciated items (it was still calculating FTD).
Any district who had incorrect depreciation due to this, if they closed that FY they will need to reopen and reclose the FY. To determine if there is a depreciation problem, run the Schedule of Change in Depreciation or the Book Value report after the FY was closed and review depreciation amounts.
Depreciation option: Updated to correct problem with it not subtracting salvage value when recalculating depreciation.
If you have items that have a salvage value the calculated depreciation may not be correct, select those items from the grid and click the 'Depreciate' button. You can run a projection report first to verify the depreciation is correct. Then, uncheck the projection only value and generate again to correct the depreciation values.
Updated to require a Lease Type if the acquisition method selected is Leased. Also, the calculation for setting an item as capitalized was updated to look at both the acquisition method and lease type - mimics Classic’s behavior
Corrected item migration import to show the true value of the acquisition date. Previously when importing an item, if the acquisition date was blank, the UI would display the current system date.
Note, capitalized items with blank acquisition dates will show under Acquisitions Prior to System Startup on the Fixed Assets by Source report - mimics classic behavior