|
||
|
|
|
Version 05.12.10.00.12, December 8, 2012 - standard release |
|
Feature: |
Conversion Reports folder has been removed |
Issue #: |
249017 |
Change: |
The Conversion Reports folder has been removed from the Account Management Utilities menu tree. |
Reason: |
The reports that were contained in this folder were removed with the release of DF104. Since the folder is now empty, there is no need to keep this folder. |
Menu: |
FM\AM\UT |
Version 04.10.12.00.04, February 5, 2011 |
|
Feature: |
Update Beginning Balance Utility to Sustain Beginning\Ending Balance Audit |
Change: |
Changes were made to include the beginning balance adjustments in the previous year to allow for a static calculation of the next year’s beginning balance. |
Reason: |
If a district uses the Beginning Balance Utilities (FM\AM\UT\AM\BB) to change an account code's beginning balance in a fiscal year other than its initial fiscal year, the change can be overwritten if the Beginning\Ending Balances audit (FM\AM\AU\AM\BE) runs with a Starting Year that precedes the "changed" year. |
Menu: |
FM\AM\UT\AM\BB |
Version 04.09.06.02.02, January 9, 2010 |
|
Feature: |
Adjust Beginning Balance Utility Will Not Allow Zeros |
Issue #: |
220738 |
Change: |
The Adjust Beginning Balance utility now allows clients to adjust balances to zero and save the changes. |
Reason: |
The Adjust Beginning Balance utility was not allowing clients to reduce their account balances to zero. |
Menu: |
FM\AM\UT\AM\BB\DB |
Version 03.07.10.02.01, October 4, 2008 |
|
Feature |
PO Adjustments |
Issue #: |
209136 |
Change: |
The PO adjustment process was modified to retain AP liquidation of the PO on the batch PO. |
Reason: |
The PO adjustment process was retaining the AP liquidation on the void PO. When the void PO was updated a negative liquidation was created removing the impact of the original update of the AP invoice. |
Menu: |
FM\AM\UT\AA |
Version 03.07.10.00.04, February 9, 2008 |
|
Feature: |
Fiscal Conversion Validation reports |
Issue #: |
51266 |
Change: |
Making sure reports are printed consistently to the correct output destination. |
Menu: |
FM\AM\UT\CR\FC |
Version 03.07.10.00.01, December 8, 2007 |
|
Feature: |
Fiscal Conversion Validation reports |
Issue #: |
51266 |
Change: |
Ability to run all fiscal validation reports at once |
Reason: |
To provide efficient method of validating a fiscal conversion |
Menu: |
FM\AM\UT\FC |
Version 03.07.02.02.01, September 8, 2007 |
|
Feature: |
Account Merge\Change - ESAM - Phase II |
Remedy Ticket: |
52008 |
Change: |
Several changes will be implemented in PMP2 for ESAM.
FYTD Summary Acct Accum Exps FYTD Summary Acct Accum Revs FY Summary Acct Accum Exps FY Summary Acct Accum Revs Monthly Summary Acct Accum Exps Monthly Summary Acct Accum Revs
|
Reason: |
Phase II ESAM changes were made to compliment and enhance the use of equity summary accounts. They provide tracking and security measures dictated by the requirements of this project. |
Menu: |
Account Merge: FM\AM\UT\AM Account Management Reporting: FM\AM\RE\BS FM\AM\RE\RE HR Security: HR\SN\CA |
Version 03.07.02.00.00, April 7, 2007 |
|
Feature: |
New field for WA001BudgetAudit table |
Remedy Ticket: |
89039 |
Change: |
The AuditDescription field was added to the WA001BudgetAudit table. This field corresponds to the Explanation column in the Adjust Beginning Balances screen. It is also the source field for the Explanation column in the Change History Report. |
Reason: |
The Beginning Balance Utilities that were recently developed required the addition of a new field to the WA001BudgetAudit table. This field is to be used for text to describe audit entries in this table. |
Menu: |
Financial Management\Account Management\Utilities\Beginning Balance Utilities |
Version 03.06.06.01.04, November 4, 2006 |
|
Feature |
Beginning Balance Utilities |
Remedy Ticket: |
89039 |
Change: |
The Beginning Balance Utilities enable key WESPaC users to manually add or adjust the beginning balance of funds and accounts. The utilities are composed of a data entry screen, a data process, and two reports. Adjust Beginning Balances Screen – This screen allows the user to define the beginning balance for new funds and accounts, and to adjust beginning balances for existing accounts "rolled" forward from the previous fiscal year. All changes made in this screen must be balanced across accounts within the same fund; that is, the adjustment balance should total 0.00. For example, a $100 increase to an asset account in fund 10 must have a corresponding amount in an equity account in fund 10. Beginning Balances Edit List – This report lists the accounts and beginning balances that have been entered by the user through the Adjust Beginning Balances screen, and that have not been transferred to the fiscal year-to-date table through the Accept Beginning Balances process. This report is useful for reviewing data entered by the user before running the Accept Beginning Balances process. Accept Beginning Balances – This process updates the fiscal year-to-date table with data that was entered by the user through the Adjust Beginning Balances screen. Beginning balances are stored in a temporary table until this process is run. Beginning Balances Change History Report – This is an audit trail report that lists every beginning balance that was modified for a specific date range, as well as every Accept Beginning Balances process that was run during the same period. |
Reason: |
Several ESDs had pointed out that they manually enter some funds and\or accounts into WESPaC, instead of converting them from their auxiliary WISE database through auto-conversion. These new funds and accounts are created with a beginning balance of 0. Users need a way to add a beginning balance to new accounts, and adjust beginning balances that are rolled forward from the previous fiscal year. |
Menu: |
Financial Management\Account Management\Utilities\Beginning Balance Utilities |
Version 03.06.01.1, March 4, 2006 |
|
Feature |
Expanded Account Merge Log |
Remedy Ticket: |
57650 |
Change: |
This new report provides, for each account affected by the Account Merge Utility, detail information about the transactions. Data is provided for old account information (before merge), new account information (before merge), and new account information (after merge). The data provided is the name of the merged table, the name of the merged field, the record identifier, and the amounts. |
Reason: |
The Account Merge Report does not provide detailed information about the results of the merge. |
Menu: |
New report Expanded Account Merge Log:
Previous Account Merge\change report
|
Version 02.05.06.3 , February 4, 2006 |
|
Feature |
Account Merge\Change |
Remedy Ticket: |
57883 |
Change: |
This PCS affects the Skyward Account Merge Utility in Account Management. The rules enforce that only accounts that meet certain criteria are merged together. Tables that are validated are:
Functionality has also been added to add similar WA state fields together when merging accounts. This change is documented fully in PCS F58. |
Reason: |
Previously, WA fields were not reviewed in the account merge process, thus accounts that should not have been merged were allowed to merge, or data was lost in a merge process because fields were not properly calculated. |
Menu: |
Financial Mngmnt\Account Mngmt\Utilities\Account Management folder\Account Merge\change |