Page Comparison

This process should be done after when the district has imported their data into Redesign migrates from Classic to Redesign. For districts that have already migrated to Redesign prior to February 2020, this process can be performed immediatelyat any time. This process only needs to be completed one time (per advance) to link legacy repay transactions to the appropriate advance transaction. Any future repayments on the advance transactions will be created using the standard Repay Advance procedure.

See also Link A Legacy Repay to an Advance.

Utilize the SSDT Transfer Advance Activity Report to Review Transactions

1. The SSDT Transfer Advance Activity Report can be run for Transaction Types Advance and Legacy_Repay to generate a list of transactions by cash account. 
   
   Image Modified

   Note
   icon false
   Redesign utilizes each transaction's account code to determine the Transaction type when Classic data is imported. If the parameters of the account used in Classic were different than the standard function and object codes for an Advance then the Transaction type is set to Classic_Transfer_Advance. For districts with these type of transactions, this should also be included in the Query Parameters entered for Transaction Type when running the SSDT Transfer Advance Activity Report (ex. Advance,Legacy_Repay,Classic_Transfer_Advance).

   
   

2. This report may be helpful in locating which Repays belong to which Advances. Review the transaction account code and amount.
   
   Some repayments are for the full amount of the Advance so they are easy to locate:
   
   
   
   Some are only partial repayments so they may be more difficult to determine without looking at the account code:
   
   

Link Legacy Repays to an Advance

...