USAS-R Releases

Bug Fixes

• Corrected the ability to use the "Create New" feature when adding Refund transactions.  Previously if a refund with a check had been created, the check information on the new refund was populated with the data from the previous transaction.

• With the release of 8.52.0 we unintentionally introduced a bug with printing POs as a result of the changes we made to improve performance.  The PO XML file generated for printing POs showed a different purchase order date than the PO date visible in the UI.  This hotfix release corrects the bug and includes a patch to correct any purchase orders created since the 8.52.0 release.

...

• Implemented the ability to print 1099s (MISC & NEC) on pressure seal forms.  In order to print on the pressure seal forms you'll need to select the new Output File Type option "Printer/Sealer Copies".   
  
• Once you click "Generate Submission File" the printable 1099s will be generated and a PDF will be available to send to the printer.
• Additional Notes: 
  • • Currently if you select both NEC and MISC "Type of Returns" a single file will generate containing both NEC and MISC 1099s.  This is not ideal for printing on the separate forms and we have updated USASR-5027 to ensure separate files are generated.  
    • During test printing we found that if the vendor's contact info is entered in mixed case it will print on the 1099 that way.  We are updating the generation of the print forms to force all name and address information to be in all CAPITAL letters.  We also found that if the Organization & Vendor's name and address fields are too long (beyond 45 characters) they will not display properly on the printed document.  We will be correcting these issues on USASR-5027 as well.
    • Reminder, SSDT is supporting ONE blank pressure seal form for each of the 1099 types.  The forms are 8 1/2 X 11 Z-Fold.
• Ability to change a vendor on a "new" PO without reopening the posting period associated with the PO date.  You cannot change a PO to remove a vendor, making it a multivendor PO. To change the Vendor, select the Repair option on the PO.  From the vendor tab modify the vendor to a new/different vendor. 
  

...

Bug Fixes

• Correct a query used to determine the max amount for a payroll item
  • issue was employee had multiple missed deductions due to not enough funds for that payroll item with a max amount, it was still adding those up in the max amount as it went, so when she did have enough money, it wouldn't take the missed deductions out, thought it met it's max amount.
• Fix missing method exception in Payroll Detail View when attempting to remove a pay group from a payroll
  • if removing a pay group from payroll, a missing method exception was being produced.
• Hotfix - both bugs introduced on 6.72.0 release - Prevented districts from initializing payroll 
  • Correct null pointer exception that could be caused by a null rate value in a payroll item (employee or employer). This null rate value would prevent payroll from calculating, which would cause issues with initialization, reports, posting, etc.
  • Correct missing method exception the payroll report. If a message needed to be displayed on the pay report, a missing method was returned. This prevented pay report from completing.
• Hotfix
  •  ABS101
    • Correct issue with user stored parameters preventing user from navigating to the ABS101 view 
    • Prevent error in the report when no adjustments or accumulations are found for a given employee
      • Prevented districts from running ABS101.txt report
      • Now it will just give a blank report, if no employee's are found
  • Employer Distributions - Account mapping updated to handle alphanumeric character when applying mapping configuration
    • Districts getting an error when running, it was due to having an alphanumeric character in the payroll account: Example: "905B"

...

• ABS 101 Performance Improvements
  • 90% improvement
• Pay Report Performance Improvements
  • 19-29% improvement
• Add permissions to GM and USPS_STANDARD roles for File Archive (AOS and SOC1)
  • USPS_STANARD
    
    • MODULE_FILE_AUDITREPORT_VIEW
  • GROUP_MANAGER
    • MODULE_FILE_AUDITREPORT_VIEW
    • MODULE_FILE_AUDITREPORT_CREATE
    • MODULE_FILE_AUDITREPORT_UPDATE
• Add distinction to properties in New Contract grid and under More options:
  •  
  •  
• STRS and SERS Item - add validation to rehired date if retiree flag is true
  • If one is checked and not the other, an error will be given
    • Error - SersItem.rehireFlagValid: Rehired employees must have a rehire date (Value: 'false')
    • Error - SersItem.rehireDateValid: Item has rehired date but is not marked as rehired retiree (Value: 'false')
    • Error - StrsItem.rehireFlagValid: Rehired employees must have a rehire date (Value: 'false')
    • Error - StrsItem.rehireDateValid: Item has rehired date but is not marked as rehired retiree (Value: 'false')
• Update module.accounting to compile static - performance
  • Affected Account mapping and Employer Distributions
• EMIS Change for FY 23 on field CK230 - Position 
  • Added to Position Separation and Mass Load Position
    • 4 - Resigned - Took a job outside the field of education
    • 7 - Resigned - Unknown or does not fit into options 4, 5 or 6
• Add warning to EMIS Configuration to notify user that changing EMIS year could cause issues if final collection has not been completed.

  • Enter the Current EMIS Fiscal Year.  This will need to be updated every Fiscal Year when the new FYXX Initial Staff/Course (L) window is opened.

    A warning message has been added to System/Configuration/EMIS Reporting Configuration when selecting Edit/Save from May 1 - Aug 31.  This message should not appear if the system date is not within May 1 - Aug 31:

    Warning:  Changing the EMIS Reporting Year between May 1st and August 31st will impact final staff/course reporting of EMIS data. Be certain your district has completed this reporting for the previous year before saving this change.

    The user can Save or Cancel. 

    If the user Saves in the message, it will save all changes (including if there was a change to the EMIS Fiscal Year).
    If the user Cancels in the message, it will bring them back to the EMIS Reporting Configuration to either make changes or to Save or Cancel.

• New Contract Report - pull the pay group from the New Contract entity and only fall back on the position if required.
  • Report has been updated to only pull in New Contract pay groups, and not from the previous contract, if changed

...

• Transactions>Items: You cannot modify the LTD Depreciation field so we Implemented the ability to post depreciation adjustments for active items that have not been fully depreciated.  You can only create, modify or delete an adjustment for the current fiscal year.
  • The fiscal Year will default to the open period that is marked current.  The default 'type' is Adjustment.  The amount entered will be added (or subtracted if entering a negative amount) to the existing LTD depreciation amount.
  • Once created, the adjustments can be modified or delete in the same fiscal year.  Example: Adjustment made while FY2023 was current (and open).  Your current period is now FY2022.  You cannot change or deleted the adjustment for the item.  You must change your current period back to the fiscal year the adjustment was originally made in (FY2023).

Image RemovedImage Added

• Reports>Created Fiscal Year Ending Balances report. Projection of what the ending balances (original cost) will be for the current fiscal year when the fiscal period is closed.  This is a projection only report.
• System>Configuration: New option 'Password Config' implemented to configure password requirements.  The Password Configuration option is the same configuration you are used to seeing in USAS and USPS.  Password complexity requirements can now be defined in Inventory.
• Implemented the Inventory FYE Report Bundle.  Replacement for Classic's EISCD.  This bundle is implemented when an open fiscal year is closed.  The reports will be zipped and emailed to the email address(es) specified in Core>Configuration.  In order for the report bundle to be emailed, the Email Address in Core>Configuration must be populated with valid email address(es) and the Email Configuration tab under System>Configuration must be populated as well.  The report bundle will not generate if either of these configurations are not populated. 
  
  • • If a district has already closed the fiscal year, it can be reopened and then closed again to generate the report bundle.  
    • Districts must store these reports until the Document Management & Archival project is available.  At that time districts will be able to upload previously generated documents.