Data Roller

In order to bring old data into Contract Management, the data roller must be run.

The data roller is a process that will need to be run from the 7i server on the command line. This process will take data from the old table structures and import it into the new table structures.

From a command prompt, navigate to the PowerSchool bin directory. Once there, type the following command:

launcher –a BT70CM.dll –i BT70CM.CMDataMigration

You will be prompted for two pieces of information: the default GL ledger and the default JL ledger. There were several places in the old data structure that assumed the ledger to be the default ledger; the new system will not make that assumption however; the defaults must be put in place.

After entering in the default ledgers, it is likely that you will receive several error messages explaining problems with the data. If you wish to export the errors to a file, you may use the following command:

launcher –a BT70CM.dll –i BT70CM.CMDataMigration > [output file name]

Where [output file name] is the name of the file you wish to output to, including its full path. Please note that you will not see the prompt for the default ledgers, however you will still need to enter them in before the process will continue.

After all the issues listed have been resolved in the database, you can run the command again without the output file. Ideally, the result will look something like what is listed below.

C:\dev\bin>launcher -a BT70CM.dll -i BT70CM.CMDataMigration
Enter the default GL ledger: GL
Enter the default JL ledger: JL
Successfully wrote 12 records to cm_codes. 0 failed.
Successfully wrote 480 records to cm_encum_item. 0 failed.
Successfully wrote 2018 records to cm_encum_acct. 0 failed.
Successfully wrote 778 records to cm_amend_chg. 0 failed.
Successfully wrote 970 records to cm_amend_item. 0 failed.
Successfully wrote 1431 records to cm_amend_acct. 0 failed.
Successfully wrote 211 records to cm_compl_vendor. 0 failed.
Successfully wrote 6420 records to cm_compl_dtl. 0 failed.
Successfully wrote 8 records to cm_cycle_mstr. 0 failed.
Successfully wrote 15 records to cm_cycle_dtl. 0 failed.
Successfully wrote 103 records to cm_subcontractor. 0 failed.

If any failures occur, you can check the event log to see a more detailed description of why each of them failed and attempt to repair the database.