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.
...
- 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
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.Jira Legacy server SSDT System JIRA serverId 925ea1db6d21ed14-0df83f48-3e913cc2-bcfbad28-6b1c8a04f6ca6548879d10d6 key USASR-5073
- 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.
...
- 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.
- A job to schedule the form generation
- A new tab has been added to the W2 Reporting view to print W2 Forms.
- YTDRPT Replacement–Reports>YTD Report
...
- 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. 1.25 INV-366
- Corrected a problem introduced on the 1.25.0 release (INV-366) 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 the acquisition's fund is blank/zero and the fund dimension of the account code is left blank. The Fixed Asset by Source report It has been corrected to display the fund's value on the report even if the fund is not defined in Core→Fund.1.25.1 INV-401
- 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
- Causing migration balancing issues because the SCFA detail Detail report wasn’t including neg acq acquisitions but the SCFA summary was. 1.25 INV-341This has been corrected.
- The Function and Asset Class report types were not including the adjustment amounts for Transfers transfers correctly (on both summary and detail). These were corrected to look at the Fund transfers and include those items that changed fund type. 1.25.1 inv-361
- Causing migration balancing issues because the SCDEP summary wasn’t include all acqs correctly 1.25 INV-341
- Summary report only
- was not looking at all acquisitions when calculating acquisition error adjustments. 1.25 INV-341
- updated the transfer amounts to be the original cost if there are no acquisitions for the item 1.25 INV-341
- Items that were both acquired and disposed of in the current year were not reporting acquisitions amounts correctly. 1.26 INV-298
- Also, disposition adjustments were showing up as a positive value instead of a negative value. 1.26 INV-298
- 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 . 1.26 INV-298were 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. 1.25 INV-375
- 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. 1.26 INV-298
- 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
- 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
- Fixed Asset By Source 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. 1.25 INV-375
- 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. 1.26 INV-360
- 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. 1.26 INV-345
- 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
- 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).
...