| Info |
|---|
A Redesign Technical Setup and Migration Guide is available in an effort to consolidate the various pieces of our documentation relevant to setting up a new school on USXS-R. |
...
| Note |
|---|
SSDT strongly recommends ITCs run test imports on their district's data one to two months before the dual-processing period. When running a test import, please review the Data Data Cleanup section on the 'Post Import Procedures to ensure account and transaction totals, including running a Carryover Reconciliation Report, are correct and any necessary corrections addressed. |
Before extracting a district's data from the Classic system (in order for it to be imported in USAS-R), the following may need to be addressed:
- Review outstanding .BATCH files
- Future PO files with .BATCH, .INPROGRESS and .REJECTED extensions in Classic will automatically import into the posting period based on the PO date in the batch file. Recommend districts review all future PO files with these extensions to see if any need to be included in the extract. Any old future PO files that do not need to be posted in Classic should be cleaned up in the district's data directory before extracting data for the Redesign.
- Outstanding BRDDIS batch files must be posted in Classic before extracting data. If some of those batch files are old BRDDIS batch files that do not need to be posted in Classic, they should be cleaned up in the district's data directory before extracting data for the Redesign.
- Outstanding PAYROLL batch files must be posted in Classic before extracting data.
- Review outstanding requisitions
- If you have outstanding requisitions from prior years that you do not intend on converting to purchase orders, you can delete the unnecessary requisitions before extracting your data.
- Classic Reports REQSUM or REQDET an be used to review Requisitions
- Review outstanding invoices
- Please review invoices with future period dates. To easily detect these transactions, after running a test import of their data, go to Core>Posting Periods to see if there are periods created after the current period. (i.e. If your test import was done in February 2020 and when reviewing your posting periods, there was a posting period automatically created for December 2020, chances are there is a transaction in Classic with a future date. ) Under Transactions>Activity Ledger Query, you can enter a date range for the future period to locate the transactions with a future period date. Because Classic invoicing doesn't contain future date restrictions, it could be users inadvertently created an invoice for a future period. If you find outstanding invoices that need to be changed to reflect the correct date, they can be updated in Classic before the final import is performed.
Re-Import Data Precautions
...