SCT Plus to SCT Banner Migration Tools SunGard SCT Application Practices Migration Guide. July 2005

Transcription

1 SCT Plus to SCT Banner Migration Tools SunGard SCT Application Practices July 2005

2 Business Information This documentation is proprietary information of SunGard SCT and is not to be copied, reproduced, lent or disposed of, nor used for any purpose other than that for which it is specifically provided without the written permission of SunGard SCT. Prepared By: SunGard SCT 4 Country View Road Malvern, Pennsylvania United States of America SunGard All rights reserved. The unauthorized possession, use, reproduction, distribution, display or disclosure of this material or the information contained herein is prohibited. In preparing and providing this publication, SunGard SCT is not rendering legal, accounting, or other similar professional services. SunGard SCT makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization's own choosing. SunGard, the SunGard logo, SCT, the SCT logo, and Banner, Campus Pipeline, Luminis, PowerCAMPUS, SCT Matrix, SCT Plus, SCT OnSite and SCT PocketRecruiter are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. All other trade names are trademarks or registered trademarks of their respective holders.

3 SCT Plus to SCT Banner Migration Tools Table of Contents Preface About This Manual... vii Organization... vii How to Contact SunGard SCT... vii SunGard SCT Support Services... viii Chapter 1 - Conversion Processing Conversion Preparation Evaluation Conversion Preparation Summary Conversion Scripts Chapter 2 - Finance (FRS) Conversion Introduction Overview of Accounting Elements Migration Overview of Vendors and Fixed Assets Migration Financial Accounting: SCT Banner Finance Ledger Accounting Elements Chart of Accounts Migration Validation Tables and Order of Conversion Converter Tool Load Hints Spreadsheets Chart of Accounts Load Sequence Create Clean Conversion Environment FTVCOAS Table FTVSDAT Table FTVATYP Table FTVACCT Table FRBGRNT Table FTVFTYP Table FTVFUND Table GXVBANK Table FTVORGN Table FTVPROG Table FTVACTV Table FTVLOCN Table FTVACCI Table FTVFSYR and FTVFSPD Table FTVFBAL Table FTVACTL Table FTVFMGR Table FOBSYSC Table iii

4 Table of Contents FOBSEQN Table Rules Codes Modifications Chart of Accounts Crosswalk Entities GURFEED: General Ledger Fund and Operating Ledger Balances Loading GL, Project to Date and Budget Balances SCT Plus FRS Vendors Conversion Loading Vendors from SCT Plus FRS into SCT Banner General Person Module General Person SPRIDEN Table General Person SPRADDR Table General Person SPRTELE Table General Person SPBPERS Table General Person Module Validation Tables Vendor FTVVEND Table FTVVEND Support and Validation Tables Ship To Codes FTVSHIP Table Income Tax FAB1099 Table FAB1099 Support and Validation Tables Direct Deposit GXRDIRD Table Direct Deposit GXRDIRD Support and Validation Tables FOBTEXT Table FOBTEXT Support and Validation Tables GOREMAL Table GOREMAL Support and Validation Tables FTVVENT Table FTVVENT Support and Validation Tables Fixed Assets SCT Plus FRS Conversion Loading Fixed Assets from SCT Plus FRS into SCT Banner Fixed Assets Validation FFBMAST Table FFBMAST Support and Validation Tables FFRMASA Table FFRMASA Support and Validation Tables FFRMASF Table FFRMASF Support and Validation Tables FFRFUSN Table FFRFUSN Support and Validation Tables FOBTEXT Table FOBTEXT Support and Validation Tables Chapter 3 - Student (SIS) Conversion iv Student Conversion Catalog Module Location Management Module (Building and Room definitions) Schedule Module General Person Module Overall Module Faculty Load Module Location Management Module (for Housing Assignments) Recruiting Module SCT Plus to SCT Banner Migration Tools July 2005

5 Table of Contents Admissions Module General Student Tables Registration Tables Grades & Academic History Tables Accounts Receivable Module Transfer Articulation Module Chapter 4 - Financial Aid (FAM) Conversion Financial Aid Conversion Required System Tables General Person and Term Code Data Rule and Validation Tables Base Table Satisfactory Academic Progress Data Tracking Requirements Budget Data Funds Management Data Award History Data Supplemental Chapter 5 - Human Resources (HRS) Conversion Human Resources Conversion Rule and Validation Tables Benefits/Deduction Rule Information Delivered Rule and Validations Tables that should not be changed Position Control Data Person Data Labor Account Distribution Mapping Deduction Data Conversion of SCT Banner Tables Containing Dollar/Hours Accumulations Chapter 6 - Advancement (ADS) Conversion Advancement Conversion Biographic and Demographic Information Constituent and Organization Required Tables Constituent Optional Tables Constituent and Organization Optional Tables Campaign and Designation Conversion Pledge Conversion Gift Conversion Matching Gift Conversion Scripts to Populate History Tables Appendix A - Conversion Troubleshooting July 2005 Loader Errors... A-3 SQL*Loader Processing Errors... A-3 Conversion Errors... A-3 ORA-02291: integrity constraint... A-3 SCT Plus to SCT Banner Migration Tools v

6 Table of Contents Column conv failure:err ORA-01403: no data found... A-3 Invalid Data Format... A-3 Missing required value... A-3 vi SCT Plus to SCT Banner Migration Tools July 2005

7 Table of Contents ORA-00001: unique constraint (SATURN.PK_SCBCRKY) violated... A-4 ORA-06502: PL/SQL: numeric or value error: character string buffer too small... A-4 Other Supporting Documentation... A-4 July 2005 SCT Plus to SCT Banner Migration Tools vii

8 Preface About This Manual This manual is designed to introduce technical staff members to the technical operations and capabilities of the SCT Plus to SCT Banner Migration Tools. Technical staff members include operations personnel, DBAs, programmer analysts, systems analysts, and other technical specialists. Staff members should be familiar with the hardware system in use at your site and you should have a basic understanding of Oracle products. Organization This document describes the steps required to successfully use the SCT Plus to SCT Banner Migration Tool set. The implementation process described lists detailed conversion procedures by SCT Plus product. This document is organized into the following sections: Chapter 1, Conversion Processing Chapter 2, Finance (FRS) Conversion Chapter 3, Student (SIS) Conversion Chapter 4, Financial Aid (FAM) Conversion Chapter 5, Human Resources (HRS) Conversion Chapter 6, Advancement (ADS) Conversion This manual also includes a separate troubleshooting area, Appendix A - Conversion Troubleshooting, used to address various error conditions generated while converting legacy data. Refer to this section of the document as necessary. How to Contact SunGard SCT Your comments are valuable. Call or write us at: SunGard SCT 4 Country View Rd. Malvern, PA toll-free (outside Pennsylvania) (inside Pennsylvania) SunGard SCT Support Services ActionLine The ActionLine is a telephone support service available to SunGard SCT maintenance customers. The ActionLine is intended to help users resolve any questions or concerns that relate to SunGard SCT products and services. Contact the ActionLine at: toll-free ActionLine ActionFax ActionWeb The ActionWeb is a secured area of SunGard SCT's World Wide Web site dedicated to viii SCT Plus to SCT Banner Migration Tools July 2005

9 Preface ActionLine and other related services available to clients. Users must be registered to obtain access to the secured site. Today, users can request an account to gain access to ActionWeb pages by accessing The ActionWeb allows you to: Contact the ActionLine. Check the status of your contacts with the ActionLine. Browse known issues. Review frequently asked questions Within the ActionWeb you can take advantage of the following online functions: Create an initial contact with the ActionLine organization, including emergency service contacts. If the description of the problem cannot fit into a 2,000-character space, users can shorten the description and indicate that an additional follow-up message(s) will follow. The additional message(s) should reference the same contact number assigned to the initial message, and be sent to the applicable ActionMail address. Update open contacts. View all opened and resolved contacts of your organization in detail. Within Extended Search, find current information about your ActionLine contacts, Known Issues, FAQs, your site s TCP/Maintenance contract dates; download documentation, software modifications and updates; and search through the SunGard SCT knowledge database. Initiate direct contact with the ActionLine manager. Initiate direct contact with your Professional Services representative. Create new Requests for Product Enhancements (RPEs), view existing RPEs, and update existing RPEs with comments. Search for defect descriptions and work-arounds in the Known Issues section. Choose the Frequently Asked Questions (FAQ) section to take you to the FAQ section within the Extended Search category. July 2005 SCT Plus to SCT Banner Migration Tools ix

10

11 Chapter 1 - Conversion Processing Conversion Preparation Evaluation Conversion Preparation Summary Conversion Scripts

12 Chapter 1 - Conversion Processing 1-2 SCT Plus to SCT Banner Migration Tools July 2005

13 Chapter 1 - Conversion Processing Conversion Preparation The automated installation procedure loads the raw SCT Plus data from the extracts into the conversion tables. After this process is complete, users should review the validation tables, crosswalks and conversion specifications to determine if modifications are necessary or desired in any area. Keep in mind that all required validation tables must be completed before conversion can begin. Evaluation Validation Table The first step in preparing to run the conversion scripts is to evaluate the validation tables. After the validation table program has been run and certain tables populated with SCT Plus DBD values, users must evaluate the validation tables to determine which SCT Banner validation tables were successfully loaded with all values, which validation tables require manual population or additional values, and which validation tables require crosswalks before proceeding with the conversion. This evaluation of the SCT Banner validation tables should be done with the participation of the SunGard SCT product functional and technical consultants assigned to the project and the members of the SCT Banner implementation team for the product being implemented. The DBD extract program is run at the same time as all other extracts for a product. The output for the extract program is then included with all other flat file output for the product, is installed in the ~p2b/product/sqlldr directory, and is used to populate certain SCT Banner validation tables. During the install process, the DBD values that can be loaded electronically will be loaded into the appropriate SCT Banner validation tables. In some cases an electronic load is not possible, and some validation tables must be populated manually. Please examine the validation_error.log to determine which values were successfully inserted. Clients have the option of retaining certain existing DBD codes and translations in selected SCT Banner validation tables or of changing the existing codes upon migration to SCT Banner. In situations where DBD values must be changed because of a size incompatibility with SCT Banner or where users wish to change the values, a crosswalk may be populated using the CUACVAL form in the SCT Converter Tool. Crosswalk Conversion scripts are delivered with crosswalk entities for many fields in SCT Banner where a validation table is referenced. Users will need to review each column to determine whether or not a crosswalk is needed. If it is determined that crosswalks are needed, users should complete the crosswalk form, CUACVAL, with the desired SCT Banner values. The crosswalk table, CURCVAL, is populated during the automated install process with legacy values extracted by the DBD extract program. Users can add to this list of legacy values if necessary, and can complete the SCT Banner value column with the new value. Keep in mind that any value in the SCT Banner Value column must be included in the validation table for which the crosswalk is being created. If a crosswalk is required, the SCT Banner column must invoke the F_CVT_CURCVAL function, and the correct parameters must be included in the function call. If it is determined that all legacy DBD values were loaded successfully into a particular SCT Banner validation table and that a crosswalk is not required for the SCT Banner column, the user should eliminate the crosswalk function from the column specifications on the CUACNVT form of the SCT Converter Tool, regenerate the conversion script, and replace the delivered conversion script with the new one in the appropriate ~p2b/product/plus directory on the database server. July 2005 SCT Plus to SCT Banner Migration Tools 1-3

14 Chapter 1 - Conversion Processing For example, if the STVCITZ validation table is successfully populated with all legacy subject codes, a crosswalk is not needed for the SPBPERS_CITZ_CODE column. The user should remove the F_CVT_CURCVAL conversion function that references the crosswalk entity of STVCITZ, regenerate the spbpers_convert.sql conversion script, and replace the delivered convert script with the new one. If, on the other hand, users wish to change all legacy citizen codes, users will complete the STVCITZ crosswalk entity, and leave in the F_CVT_CURCVAL conversion function. It is not necessary to regenerate the spbpers_convert.sql script if the only change made is to complete a crosswalk form. Conversion Specifications (per table) After all validation tables and crosswalks have been evaluated and adjusted as necessary, users should review other conversion specifications for each SCT Banner table with the appropriate functional users or someone knowledgeable of institutional data standards to determine if there are any changes desired in any specifications. For example: Do the users wish for all names to be in UPPERCASE or Mixed Case? Another good example of a situation that calls for review of conversion specifications with users involves the Term Code Validation Table, STVTERM. This table is not populated from the DBD extract because it contains detail that must be supplied by the client. However, after STVTERM has been populated, it may be necessary to complete the STVTERM crosswalk entity to equate the new SCT Banner terms to the incoming legacy terms if clients have changed their term code system. In the case of STVTERM, another possibility for translating term code values is to use a delivered database function, F_CVT_TERM, which transforms the incoming legacy term code into SCT Banner formatted term codes. Users should evaluate the function carefully to determine if it meets their needs. It is possible to edit any function to customize it to the needs of the institution; however, it is recommended that users copy existing function code and rename the function before editing, thereby preserving the original or delivered functions for future reference. Users should follow the SCT Converter Tool documentation for assistance in modifying delivered database functions and using delivered crosswalk entities. Conversion Preparation Summary Evaluate validation table error log Review all validation tables for product to ensure completeness Review conversion specifications in SCT Converter Tool Complete crosswalks where necessary Eliminate crosswalk functions where necessary and regenerate script Determine if other adjustments are necessary or desired Regenerate tablename_convert.sql scripts if changes are made and FTP new scripts to server 1-4 SCT Plus to SCT Banner Migration Tools July 2005

15 Chapter 1 - Conversion Processing Conversion Scripts After conversion specifications have been evaluated, modified as desired, regenerated and sent (via FTP) to the database server, users can begin running the PL/SQL conversion scripts for each table per product, in the order suggested in the product sections of this guide. The PL/SQL conversion scripts will first be run in Convert mode, which transforms the raw SCT Plus data to SCT Banner-ready data within the conversion table, according to set specifications. This part of the process requires operator intervention to enter parameters indicating the types of files to process and the action that should be taken on the files. The process produces log files (tablename_n.log) that reside in the ~/p2b/product/plus directory. It may be necessary to run the convert script in convert mode several times. If data errors exist because of missing required values, missing validation codes, or any other of the common data errors that could cause problems, users should examine carefully each log file produced, and should evaluate and deal with the errors before proceeding. Errors are displayed in the CUICERR form of the SCT Converter Tool. Refer to the Conversion Troubleshooting section of this guide for help in determining the source of potential data errors. Also, consult Oracle s Server Messages manual for information on specific Oracle errors. Users may decide to correct all errors as they appear or may choose not to load the particular rows where the errors exist. At the satisfactory completion of the Convert phase of the migration, when all data errors have been dealt with, users should re-run the convert script in Insert mode to insert the data into the target SCT Banner table. There may again be data errors in this phase, caused by the enforcement of referential integrity constraints. Users should consult the CUICERR form/curcerr table if errors are encountered, and should evaluate and correct the errors, repeating the Insert process until all data is inserted into the target SCT Banner table. Product conversion sections in this guide indicate the order in which the tables should be loaded and also provide- some helpful conversion hints for the particular product. For specific help in using the SCT Converter Tool, users should consult the SCT Converter Tool User Guide. July 2005 SCT Plus to SCT Banner Migration Tools 1-5

16 Chapter 1 - Conversion Processing 1-6 SCT Plus to SCT Banner Migration Tools July 2005

17 Chapter 2 - Finance (FRS) Conversion Introduction Overview of Accounting Elements Migration Overview of Vendors and Fixed Assets Migration Financial Accounting: SCT Banner Finance Ledger Accounting Elements Chart of Accounts Migration Validation Tables and Order of Conversion Converter Tool Load Hints Spreadsheets Chart of Accounts Load Sequence Create Clean Conversion Environment FTVCOAS Table FTVSDAT Table FTVATYP Table FTVACCT Table FRBGRNT Table FTVFTYP Table FTVFUND Table GXVBANK Table FTVORGN Table FTVPROG Table FTVACTV Table FTVLOCN Table FTVACCI Table FTVFSYR and FTVFSPD Table FTVFBAL Table FTVACTL Table FTVFMGR Table FOBSYSC Table FOBSEQN Table Rules Codes Modifications Chart of Accounts Crosswalk Entities GURFEED: General Ledger Fund and Operating Ledger Balances Loading GL, Project to Date and Budget Balances SCT Plus FRS Vendors Conversion Loading Vendors from SCT Plus FRS into SCT Banner General Person Module General Person SPRIDEN Table General Person SPRADDR Table General Person SPRTELE Table General Person SPBPERS Table General Person Module Validation Tables Vendor FTVVEND Table

18 Chapter 2 - Finance (FRS) Conversion FTVVEND Support and Validation Tables Ship To Codes FTVSHIP Table Income Tax FAB1099 Table FAB1099 Support and Validation Tables Direct Deposit GXRDIRD Table Direct Deposit GXRDIRD Support and Validation Tables FOBTEXT Table FOBTEXT Support and Validation Tables GOREMAL Table GOREMAL Support and Validation Tables FTVVENT Table FTVVENT Support and Validation Tables Fixed Assets SCT Plus FRS Conversion Loading Fixed Assets from SCT Plus FRS into SCT Banner Fixed Assets Validation FFBMAST Table FFBMAST Support and Validation Tables FFRMASA Table FFRMASA Support and Validation Tables FFRMASF Table FFRMASF Support and Validation Tables FFRFUSN Table FFRFUSN Support and Validation Tables FOBTEXT Table FOBTEXT Support and Validation Tables SCT Plus to SCT Banner Migration Tools July 2005

19 Chapter 2 - Finance (FRS) Conversion Introduction The SCT Banner Finance product provides clients with a great degree of flexibility in setting up accounting structures. Because SCT Banner s unique structure offers this flexibility, a straight translation from SCT Plus FRS to SCT Banner Finance is not preferred. In place of a direct migration of SCT Plus FRS chart elements into SCT Banner Finance, SunGard SCT recommends that clients use the opportunity of implementing SCT Banner to take advantage of the new flexible chart of accounts structures that SCT Banner Finance can provide. There may be some cases where select data can be successfully migrated electronically. However, much of this first phase of a SCT Banner Finance implementation will be best accomplished with a combination of manual data entry, client-populated spreadsheets, which are then loaded electronically, and electronic migration of select data using crosswalks to accurately translate accounting values from SCT Plus FRS to SCT Banner Finance. Overview of Accounting Elements Migration Due to the differences between SCT Plus FRS and SCT Banner accounting structures, SunGard SCT recommends creating a new SCT Banner chart of accounts using SCT Banner definitions. After a review of the existing SCT Plus FRS chart of accounts, clients can create the new SCT Banner chart of accounts structure using SCT Banner definitions by a combination of 1) manual data entry directly into SCT Banner forms, 2) manual data entry into Excel spreadsheets (to create flat files for electronic loading into a SCT Banner crosswalk table comparing the SCT Plus FRS chart to the newly created SCT Banner chart), and 3) electronic migration of select data such as beginning balances and project to date balances using the crosswalk tables. This section outlines the steps necessary to implement the SCT Banner Chart of Accounts. The assumption is that the Finance migration team, using this section, has had a thorough introduction to the SCT Banner Finance chart of accounts methodology and has a basic understanding of the use of the tables presented in this section. A second assumption is that the Finance migration team will have had SCT Converter Tool training. Overview of Vendors and Fixed Assets Migration Due to the slight differences between SCT Plus FRS and SCT Banner vendors and fixed assets setup, SunGard SCT recommends evaluating clients current data in SCT Plus FRS to establish migration criteria to resolve some of the issues associated with migrating vendors and fixed assets from SCT Plus FRS into SCT Banner. These issues involve determination of how data should be manipulated (e.g. vendor number truncation and address line data cleanup) and how data should be cross-walked (e.g. fixed assets crosswalk codes such as acquisition method, asset type etc.). After a review of the existing SCT Plus FRS data (including the accounting elements required for Fixed Assets capitalization and depreciation), clients can decide on how data is manipulated in the tool and what would be the defaults for many fields in both vendors and fixed assets tables. The vendors and fixed assets migration sections outline the steps necessary to migrate SCT Plus FRS vendors and fixed assets into SCT Banner vendors and fixed assets modules. The assumption is that the Finance migration team, using this section, has had a thorough introduction to the SCT Banner Finance chart of accounts methodology, vendors data architecture, fixed assets setup/management methodology and has a basic understanding of the use of the tables presented in this section. A second assumption is that the Finance migration team will have had SCT Converter Tool training. July 2005 SCT Plus to SCT Banner Migration Tools 2-3

20 Chapter 2 - Finance (FRS) Conversion Financial Accounting: SCT Banner Finance Ledger Accounting Elements Chart of Accounts Migration The following steps outline the necessary tasks involved in implementation of SCT Banner Financial Accounting. This implementation is accomplished through a combination of manual data entry into SCT Banner and/or Excel spreadsheets and electronic migration of data using the SCT Converter Tool. 1. A SunGard SCT consultant will introduce the SCT Plus FRS client to SCT Banner Financial Accounting methodology and explain the differences between the SCT Plus FRS and SCT Banner Finance chart of accounts. This first training/consulting session will give the client the background needed to begin construction of an SCT Banner chart of accounts. SunGard SCT provides Excel spreadsheet templates and other supporting documents for each of the chart elements. 2. The client is responsible for building SCT Banner Finance chart of accounts on the spreadsheets provided and will crosswalk within each spreadsheet an equivalent SCT Plus FRS value for each new SCT Banner Finance chart of accounts element. 3. The completed spreadsheets are saved as comma-delimited ASCII files and are used within the context of the SCT Converter Tool to create the crosswalks necessary. These files are also used to populate selected large validation tables such as FTVFUND and FTVORGN. Smaller validation tables are manually populated (e.g. FTVCOAS). 4. The crosswalk data from the spreadsheets linking SCT Plus FRS chart values (SCT Plus FRS Account and Object Codes) to SCT Banner chart values (Fund, Organization, Account and Program Codes) will then be loaded into crosswalk tables within the SCT Converter Tool. 5. Validate the chart of accounts by processing test transactions and running hierarchical reports to make sure the new chart structure is producing the desired results. SunGard SCT recommends implementing SCT Banner Finance at the beginning of a fiscal year. However, it is possible to implement SCT Banner Finance mid-year, given that clients are aware of the extra conversion efforts needed to bring monthly GL and Operating Ledger balances into SCT Banner ledgers. Validation Tables and Order of Conversion This section outlines the detail steps that are necessary to set up a SCT Banner chart of accounts. The steps that follow are necessary for each of the individual SCT Banner chart of account tables. The next section describes SCT Banner validation table layout with SCT Converter Tool load hints applicable to the migration of chart data. Converter Tool Load Hints Spreadsheet Data File The data necessary for that field is found in the spreadsheet data file provided by the client. This data will need to be loaded and inserted into the tables. Optional Spreadsheet Data File The data necessary for that field is found in the spreadsheet data file provided by the client. This data is optional and can be left blank. SYSDATE Enter SYSDATE in the Convert Function field of the SCT Converter Tool. This assigns the system date in the date field. 2-4 SCT Plus to SCT Banner Migration Tools July 2005

21 Chapter 2 - Finance (FRS) Conversion Blank No Load or Insert Refers to the SCT Converter Tool fields of Load and Insert. This message indicates there should be no data available in the data file for that field. When this message appears in the Converter Tool Hints column, the Load and Insert boxes on the SCT Converter Tool should be unchecked. Default = Value These hints indicate default values that must be inserted into the designated SCT Banner column, whether the value is on the spreadsheet or not. The hints included give sample default values, which may be changed according to client-specific needs. Validation The SCT Converter Tool provides validation functionality to allow users to validate the values being entered. For example, when entering the Account Type values into the Account Code table, incoming values may be validated against the FTVATYP table to verify that the value has been loaded previously. This can be done using the validate single function of SCT Converter Tool. Spreadsheets Each delivered spreadsheet is created according to the structures of the SCT Banner tables and referenced forms. The spreadsheets are designed for multiple uses and may contain fields that need not be populated to create the chart of accounts. The SunGard SCT consultant needs to evaluate which fields will need to be completed on the spreadsheets based on the modules that are being implemented on the initial visit. Delivered spreadsheets include: 1. Chart of Accounts Code (FTMCOAS) 2. System Data Maintenance (FTMSDAT) 3. Account Types (FTMATYP) 4. Account Codes (FTMACCT) 5. Grant Codes (FRAGRNT) 6. Fund Types (FTMFTYP) 7. Fund Codes (FTMFUND) 8. Bank Codes (GXRBANK) 9. Organization Codes (FTMORGN) 10. Program Codes (FTMPROG) 11. Activity Codes (FTMACTV) 12. Location Codes (FTMLOCN) 13. Index Codes (FTMACCI) 14. Control Accounts Maintenance (FTMACTL) 15. Fund Balance Account Code Maintenance Form (FTMFBAL) 16. Financial Manager Maintenance Form (FTMFMGR) 17. Finance System Level Decisions (FOASYSC) Once the spreadsheets are complete and saved in comma-delimited format, change the filename to the following format: tablename_cvt.dat to proceed with the loading of data. July 2005 SCT Plus to SCT Banner Migration Tools 2-5

22 Chapter 2 - Finance (FRS) Conversion Chart of Accounts Load Sequence Following are the steps for loading the tables for the Finance Chart of Account elements. Create Clean Conversion Environment Before beginning any loading of data, make sure that the SCT Banner Finance database is cleaned of all delivered seed data (except for those required seed data in some tables such as FTVSDAT, FTVRUCL, FTVEDIT, FTVRULP etc.). FTVCOAS Table FTVCOAS Chart of Account (Manual) Use the FTMCOAS Document to assist in manually completing the FTMCOAS form in SCT Banner. You do not need to enter the accounting elements at this point (e.g. interfund due to and interfund due from accounts). These values can be entered in the future after loading the FTVACCT table. FTVSDAT Table FTVSDAT Internal Account Types, Funds Types and Control Sequences (Electronic) File specifications can be modified in the SCT Converter Tool if necessary. The table-create script, the control file and the convert script must be re-produced from the SCT Converter Tool and executed to create the temp table. The FTVSDAT table layout is shown below. The SCT Converter Tool hints column includes suggestions for loading data from the ftvsdat_cvt.dat file. The data described is from the ftvsdat_cvt.dat file. Column Data Type Constraints SCT Converter Tool Hints FTVSDAT_SDAT_CODE_ENTITY VARCHAR2 (8) Not Null Data File FTVSDAT_SDAT_CODE_ATTR VARCHAR2 (30) Data File FTVSDAT_SDAT_CODE_OPT_1 VARCHAR2 (8) Data File FTVSDAT_SDAT_CODE_OPT_2 VARCHAR2 (8) Blank No Load or Insert FTVSDAT_CODE_LEVEL NUMBER (2) Blank No Load or Insert FTVSDAT_COAS_CODE VARCHAR2 (1) Default = Chart Code FTVSDAT_EFF_DATE DATE Not Null Default = Chart Effective Date FTVSDAT_TERM_DATE DATE Blank No Load or Insert FTVSDAT_NCHG_DATE DATE Blank No Load or Insert FTVSDAT_STATUS_IND VARCHAR2 (1) Not Null Default = A FTVSDAT_ACTIVITY_DATE DATE Not Null SYSDATE FTVSDAT_USER_ID VARCHAR2 (30) Not Null USER FTVSDAT_TITLE VARCHAR2 (35) Not Null Data File FTVSDAT_SHORT_TITLE VARCHAR2 (20) Data File FTVSDAT_DATA VARCHAR2 (15) Data File 2-6 SCT Plus to SCT Banner Migration Tools July 2005

23 Chapter 2 - Finance (FRS) Conversion FTVATYP Table FTVATYP Account Type Code (Electronic) Use FTMATYP Excel Spreadsheet to load client s defined Account Types. Put FTMATYP spreadsheet columns in the correct format to load into the FTVATYP table. Name spreadsheet = ftvatyp_cvt and save in comma delimited format (.csv). Rename file ftvatyp_cvt.dat during FTP to database server. File specifications can be modified in the SCT Converter Tool if necessary. The table create script, control file, and convert script must then be re-produced from the SCT Converter Tool and executed to create the temp table. The following is a table layout of the FTVATYP table. Column Data Type Constraints SCT Converter Tool Hints FTVATYP_COAS_CODE VARCHAR2 (1) Not Null Default = Chart Code FTVATYP_ATYP_CODE VARCHAR2 (2) Not Null Spreadsheet Data File FTVATYP_EFF_DATE DATE Not Null Default = Chart Effective Date FTVATYP_ACTIVITY_DATE DATE Not Null SYSDATE FTVATYP_USER_ID VARCHAR2 (30) Not Null USER FTVATYP_NCHG_DATE DATE Not Null Default = FTVATYP_TERM_DATE DATE Blank No Load or Insert FTVATYP_TITLE VARCHAR2 (35) Not Null Spreadsheet Data File FTVATYP_STATUS_IND VARCHAR2 (1) Not Null Default = A FTVATYP_INTERNAL_ATYP_CODE VARCHAR2 (2) Not Null Spreadsheet Data File FTVATYP_ATYP_CODE_PRED VARCHAR2 (2) Spreadsheet Data File FTVATYP_NORMAL_BAL VARCHAR2 (1) Not Null Spreadsheet Data File FTVACCT Table FTVACCT Account Code (Electronic) Use FTMACCT Excel Spreadsheet to load client s defined Account Codes Put FTMACCT spreadsheet columns in the correct format to load into the FTVACCT table. Name spreadsheet = ftvacct_cvt and save in comma delimited format (.csv) Rename file ftvacct_cvt.dat during FTP to database server. July 2005 SCT Plus to SCT Banner Migration Tools 2-7

24 Chapter 2 - Finance (FRS) Conversion File specifications can be modified in the SCT Converter Tool if necessary. The table create script, control file, and convert script must be re-produced from the SCT Converter Tool and executed to create the temp table. The following is a table layout of the FTVACCT table. Column Data Type Constraints SCT Converter Tool Hints FTVACCT_COAS_CODE VARCHAR2 (1) Not Null Default = Chart Code FTVACCT_ACCT_CODE VARCHAR2 (6) Not Null Spreadsheet Data File FTVACCT_EFF_DATE DATE Not Null Default = Chart Effective Date FTVACCT_ACTIVITY_DATE DATE Not Null SYSDATE FTVACCT_USER_ID VARCHAR2 (30) Not Null USER FTVACCT_NCHG_DATE DATE Not Null Default = FTVACCT_TERM_DATE DATE Blank No Load or Insert FTVACCT_TITLE VARCHAR2 (35) Not Null Spreadsheet Data File FTVACCT_ATYP_CODE VARCHAR2 (2) Not Null Spreadsheet Data File FTVACCT_NORMAL_BAL VARCHAR2 (1) Not Null Spreadsheet Data File FTVACCT_STATUS_IND VARCHAR2 (1) Not Null Default = A FTVACCT_ACCT_CODE_PRED VARCHAR2 (6) Spreadsheet Data File FTVACCT_DATA_ENTRY_IND VARCHAR2 (1) Not Null Spreadsheet Data File FTVACCT_ACCT_CODE_FRINGE VARCHAR2 (6) Blank No Load or Insert FTVACCT_FRINGE_PCT NUMBER (6,3) Blank No Load or Insert FTVACCT_ACCT_CODE_POOL VARCHAR2 (6) Optional Spreadsheet Data File FTVACCT_ACCT_CODE_ASSET VARCHAR2 (6) Optional Spreadsheet Data File FTVACCT_ITYP_SEQ_CODE NUMBER (2) Blank No Load or Insert FTVACCT_ACCT_CLASS_CODE VARCHAR2 (2) Optional Spreadsheet Data File FTVACCT_ACCT_CODE_DEPR_EXP VARCHAR2 (6) Optional Spreadsheet Data File FTVACCT_ACCT_CODE_DEPR_ACCUM VARCHAR2 (6) Optional Spreadsheet Data File FRBGRNT Table FRBGRNT Grant Maintenance (Electronic) Use the FRAGRNT Excel Spreadsheet to load client s defined grant codes. Put FRAGRNT spreadsheet columns in the correct format to load into the FRBGRNT table. Name spreadsheet = frbgrnt_cvt and save in comma delimited format (.csv) Rename file frbgrnt_cvt.dat during FTP to database server. File specifications can be modified in the SCT Converter Tool if necessary. The table create script, control file, and convert script must be re-produced from the SCT Converter Tool and executed to create the temp table. 2-8 SCT Plus to SCT Banner Migration Tools July 2005

25 Chapter 2 - Finance (FRS) Conversion The following is a table layout of the FRBGRNT table. Note: If a value is inserted for the PI PIDM, then a record must also be generated in FRRGRPI. If a value is inserted for STATUS_CODE, then a record must also be generated in FRVGRST. Column Data Type Constraints SCT Converter Tool Hints FRBGRNT_CODE VARCHAR2 (9) Not Null Spreadsheet Data File FRBGRNT_ACTIVITY_DATE DATE Not Null SYSDATE FRBGRNT_USER_ID VARCHAR2 (30) Not Null USER FRBGRNT_PROP_CODE VARCHAR2 (9) Blank No Load or Insert FRBGRNT_COAS_CODE VARCHAR2 (1) Default = Chart Code FRBGRNT_ORGN_CODE_RESP_OFFICE VARCHAR2 (6) Optional Spreadsheet Data File FRBGRNT_LONG_TITLE VARCHAR2 (256) Spreadsheet Data File FRBGRNT_TITLE VARCHAR2 (35) Spreadsheet Data File FRBGRNT_AGENCY_PIDM NUMBER (8) Optional Spreadsheet Data File FRBGRNT_PI_PIDM NUMBER(8) Optional Spreadsheet Data File FRBGRNT_CURRENT_FUNDING_AMT NUMBER(12,2) Optional Spreadsheet Data File FRBGRNT_CUM_FUNDING_AMT NUMBER (12,2) Optional Spreadsheet Data File FRBGRNT_MAX_FUNDING_AMT NUMBER (12,2) Optional Spreadsheet Data File FRBGRNT_STATUS_CODE VARCHAR2 (2) Default = A FRBGRNT_STATUS_DATE DATE Same as FRBGRNT_PROJECT_START_DATE FRBGRNT_EXPEND_END_DATE DATE Optional Spreadsheet Data File FRBGRNT_TERM_DATE DATE Optional Spreadsheet Data File FRBGRNT_PROJECT_START_DATE DATE Spreadsheet Data File FRBGRNT_PROJECT_END_DATE DATE Optional Spreadsheet Data File FRBGRNT_GRNT_CODE_RELATED VARCHAR2 (9) Blank No Load or Insert FRBGRNT_GRANT_TYPE VARCHAR2 (2) Optional Spreadsheet Data File FRBGRNT_CATEGORY VARCHAR2 (1) Optional Spreadsheet Data File FRBGRNT_SUB_CATEGORY VARCHAR2 (4) Optional Spreadsheet Data File FRBGRNT_CFDA_INTERNAL_ID_NO NUMBER (8) Optional Spreadsheet Data File FRBGRNT_SPONSOR_ID VARCHAR2 (30) Optional Spreadsheet Data File FRBGRNT_AGENCY_CONTACT VARCHAR2 (35) Blank No Load or Insert FRBGRNT_AGENCY_ADDR_CODE VARCHAR2 (2) Blank No Load or Insert FRBGRNT_AGENCY_ADDR_SEQ_NUM NUMBER (2) Blank No Load or Insert FRBGRNT_AGENCY_PHONE_TYPE VARCHAR2 (4) Blank No Load or Insert FRBGRNT_AGENCY_ VARCHAR2 (35) Blank No Load or Insert FRBGRNT_COAS_CODE_IC_CS VARCHAR2 (1) Blank No Load or Insert FRBGRNT_BASI_CODE_IC VARCHAR2 (6) Blank No Load or Insert FRBGRNT_INDR_CODE_RATE VARCHAR2 (6) Blank No Load or Insert FRBGRNT_INDA_CODE_CHARGE VARCHAR2 (6) Blank No Load or Insert FRBGRNT_INDD_CODE_DISTR VARCHAR2 (6) Blank No Load or Insert FRBGRNT_BASI_CODE_CS VARCHAR2 (6) Blank No Load or Insert FRBGRNT_CSTR_CODE_RATE VARCHAR2 (6) Blank No Load or Insert FRBGRNT_CSTA_CODE_CHARGE VARCHAR2 (6) Blank No Load or Insert FRBGRNT_CSTD_CODE_DISTR VARCHAR2 (6) Blank No Load or Insert FRBGRNT_AGENCY_TELE_SEQNO NUMBER (2) Blank No Load or Insert If using Legacy ID; Use function for PIDM translation. If using Legacy or SCT Banner ID, use PIDM function for PIDM translation. July 2005 SCT Plus to SCT Banner Migration Tools 2-9

26 Chapter 2 - Finance (FRS) Conversion PIDM must exist in FRRGRPI and SPRIDEN. The CFDA_internal_id will need to be crosswalked to an ID number in the FRVCFDA table. You will need to convert all the CFDA IDs into the FRVCFDA table first. FTVFTYP Table FTVFTYP Fund Type Code (Electronic) Use FTMFTYP Excel Spreadsheet to load client s defined Fund Types Put FTMFTYP spreadsheet columns in the correct format to load into the FTVFTYP table. Name spreadsheet = ftvftyp_cvt and save in comma delimited format (.csv) Rename file ftvftyp_cvt.dat during FTP to database server. File specifications can be modified in the SCT Converter Tool if necessary. The table create script, control file, and convert script must be re-produced from the SCT Converter Tool and executed to create the temp table. The following is a table layout of the FTVFTYP table. Column Data Type Constraints FTVFTYP_COAS_CODE VARCHAR2 (1) Not Null Default = Chart Code SCT Converter Tool Hints FTVFTYP_FTYP_CODE VARCHAR2 (2) Not Null Spreadsheet Data File FTVFTYP_EFF_DATE DATE Not Null Default = Chart Effective Date FTVFTYP_ACTIVITY_DATE DATE Not Null SYSDATE FTVFTYP_USER_ID VARCHAR2 (30) Not Null USER FTVFTYP_NCHG_DATE DATE Not Null Default = FTVFTYP_TITLE VARCHAR2 (35) Not Null Spreadsheet Data File FTVFTYP_STATUS_IND VARCHAR2 (1) Not Null Default = A FTVFTYP_INTERNAL_FTYP_CODE VARCHAR2 (2) Not Null Spreadsheet Data File FTVFTYP_TERM_DATE DATE Blank No Load or Insert FTVFTYP_FTYP_CODE_PRED VARCHAR2 (2) Spreadsheet Data File FTVFTYP_FUND_CODE_CAP VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_ACCT_CODE_CAP VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_BAVL_KEY_FUND VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BAVL_KEY_ORG VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BAVL_KEY_ACCT VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BAVL_KEY_PROG VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BAVL_PERIOD VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BAVL_SEVERITY VARCHAR2 (1) Optional Spreadsheet Data File VARCHAR2 (1) Optional Spreadsheet Data File (Default = FTVFTYP_DEF_OVERRIDE_IND F if no value in spreadsheet) FTVFTYP_RUCL_CODE_ROLL_ENC VARCHAR2 (6) Optional Default (if needed) FTVFTYP_COMMIT_TYPE VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BUDGET_ROLL VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BUDGET_DISPOSITION VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BUDGET_ROLL_PERCENT NUMBER (6,3) Optional Spreadsheet Data File FTVFTYP_RUCL_CODE_BUDG_CF VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_CF_TYPE VARCHAR2 (1) Optional Default (if needed) FTVFTYP_BUDG_CLASSIFICATION VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_BUDG_CF_PERCENT NUMBER (6,3) Optional Spreadsheet Data File 2-10 SCT Plus to SCT Banner Migration Tools July 2005

27 Chapter 2 - Finance (FRS) Conversion FTVFTYP_ACCT_CODE_GAIN VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_ACCT_CODE_LOSS VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_DEPR_POST_CODE VARCHAR2 (1) Optional Spreadsheet Data File FTVFTYP_ORGN_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_PROG_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_ACTV_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_LOCN_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFTYP_DEPR_EXP_EQ_DEF_IND VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND Table FTVFUND Fund Code (Electronic) Use FTMFUND Excel Spreadsheet to load client s defined Fund Codes Put FTMFUND spreadsheet columns in the correct format to load into the FTVFUND table. Name spreadsheet = ftvfund_cvt and save in comma delimited format (.csv) Rename file ftvfund_cvt.dat during FTP to database server. File specifications can be modified in the SCT Converter Tool if necessary. The table create script, control file, and convert script must be re-produced from the SCT Converter Tool and executed to create the temp table. The following is a table layout of the FTVFUND table. Column Data Type Constraints SCT Converter Tool Hints FTVFUND_COAS_CODE VARCHAR2 (1) Not Null Default = Chart Code FTVFUND_FUND_CODE VARCHAR2 (6) Not Null Spreadsheet Data File FTVFUND_EFF_DATE DATE Not Null Default = Chart Effective Date FTVFUND_ACTIVITY_DATE DATE Not Null SYSDATE FTVFUND_USER_ID VARCHAR2 (30) Not Null USER FTVFUND_NCHG_DATE DATE Not Null Default = FTVFUND_FTYP_CODE VARCHAR2 (2) Not Null Spreadsheet Data File FTVFUND_TITLE VARCHAR2 (35) Not Null Spreadsheet Data File FTVFUND_STATUS_IND VARCHAR2 (1) Not Null Default = A FTVFUND_DATA_ENTRY_IND VARCHAR2 (1) Not Null Spreadsheet Data File FTVFUND_POOL_IND VARCHAR2 (1) Not Null Default = N FTVFUND_TERM_DATE DATE Blank No Load or Insert FTVFUND_FUND_CODE_PRED VARCHAR2 (6) Spreadsheet Data File FTVFUND_ORGN_CODE_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_PROG_CODE_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_ACTV_CODE_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_LOCN_CODE_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_FUND_CODE_BAVL VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_BAVL_PERIOD VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_BAVL_SEVERITY VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_HIER_TABLE_IND VARCHAR2 (1) Blank No Load or Insert FTVFUND_BAVL_KEY_FUND VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_BAVL_KEY_ORGN VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_BAVL_KEY_ACCT VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_BAVL_KEY_PROG VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_BANK_CODE VARCHAR2 (2) Optional Spreadsheet Data File FTVFUND_FMGR_CODE_PIDM NUMBER (8) Optional Spreadsheet Data File FTVFUND_ACCT_CODE_REV VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_ACCT_CODE_ACCR VARCHAR2 (6) Optional Spreadsheet Data File July 2005 SCT Plus to SCT Banner Migration Tools 2-11

28 Chapter 2 - Finance (FRS) Conversion FTVFUND_ACCT_CODE_PLANT VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_FUND_CODE_PLANT VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_COST_CODE_GRNT VARCHAR2 (6) Blank No Load or Insert FTVFUND_INDC_CODE VARCHAR2 (6) Blank No Load or Insert FTVFUND_CONP_PROJ_NUM VARCHAR2 (15) Blank No Load or Insert FTVFUND_PROJ_DESC VARCHAR2 (35) Blank No Load or Insert FTVFUND_PROJ_START_DATE_CONP DATE Blank No Load or Insert FTVFUND_PROJ_END_DATE_CONP DATE Blank No Load or Insert FTVFUND_PROJ_COMPLETE_DATE DATE Blank No Load or Insert FTVFUND_FMGR_CODE_PIDM_CONP NUMBER (8) Blank No Load or Insert FTVFUND_ACCT_CODE_EQUITY VARCHAR2 (6) Blank No Load or Insert FTVFUND_FUND_CODE_PLANT_CONP VARCHAR2 (6) Blank No Load or Insert FTVFUND_CLOSE_PROJ_IND VARCHAR2 (1) Default = N FTVFUND_FUND_CODE_SOURCE VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_CIP VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_ASSET VARCHAR2 (6) Blank No Load or Insert FTVFUND_MAX_CONSTR_AMT NUMBER(12,2) Blank No Load or Insert FTVFUND_COST_CODE_CONP VARCHAR2 (6) Blank No Load or Insert FTVFUND_CUM_COST_AMT NUMBER (12,2) Blank No Load or Insert FTVFUND_GRNT_CODE VARCHAR2 (9) Optional Spreadsheet Data File FTVFUND_POOLING_METHOD VARCHAR2 (1) Blank No Load or Insert FTVFUND_ARB_BEGIN_UNIT_VALUE NUMBER(6,2) Blank No Load or Insert FTVFUND_ACCT_CODE_FUND_BAL VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_POOL VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_REAL_GAIN VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_REAL_GAIN VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_REAL_GAIN VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_REAL_LOSS VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_REAL_LOSS VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_REAL_LOSS VARCHAR2 (6) Blank No Load or Insert FTVFUND_DISTRIBUTION_FREQ_INC VARCHAR2 (1) Blank No Load or Insert FTVFUND_DISTRIBUTION_FREQ_RGL VARCHAR2 (1) Blank No Load or Insert FTVFUND_DISTRIBUTION_ST_DATE DATE Blank No Load or Insert FTVFUND_ACCT_CODE_INCOME VARCHAR2 (6) Blank No Load or Insert FTVFUND_DISTRIBUTION_ST_DATE DATE Blank No Load or Insert FTVFUND_ACCT_CODE_INCOME VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_INCOME VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_INCOME VARCHAR2 (6) Blank No Load or Insert FTVFUND_SPENDABLE_RETURN_IND VARCHAR2 (1) Blank No Load or Insert FTVFUND_FUND_CODE_SPEND_INCM VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_SPEND_INCM VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_SPEND_INCM VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_SPEND_INCM VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_SPEND_EXCS VARCHAR2 (6) Blank No Load or Insert FTVFUND_COAS_CODE_MATCH VARCHAR2 (1) Blank No Load or Insert FTVFUND_FUND_CODE_MATCH VARCHAR2 (6) Blank No Load or Insert FTVFUND_FUND_CODE_ENDOW_FUNC VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_SPD_TR_FRM VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_SPD_TR_FRM VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_SPD_TR_FRM VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_SPD_TR_TO VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_RECLASS VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_CONTRA_INC VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_CONTRA_INC VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_CONTRA_INC VARCHAR2 (6) Blank No Load or Insert 2-12 SCT Plus to SCT Banner Migration Tools July 2005

29 Chapter 2 - Finance (FRS) Conversion FTVFUND_ACCT_CODE_CONTRA_RG VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_CONTRA_RG VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_CONTRA_RG VARCHAR2 (6) Blank No Load or Insert FTVFUND_ACCT_CODE_CONTRA_RL VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_CONTRA_RL VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_CONTRA_RL VARCHAR2 (6) Blank No Load or Insert FTVFUND_CURRENT_YEAR_INCOME NUMBER(1) Blank No Load or Insert FTVFUND_ACCT_CODE_TRF_INCOME VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_TRF_INCOME VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_TRF_INCOME VARCHAR2 (6) Blank No Load or Insert FTVFUND_PY_RETAINED_INCOME NUMBER(1) Blank No Load or Insert FTVFUND_ACCT_CODE_TRF_RI_PY VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_TRF_RI_PY VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_TRF_RI_PY VARCHAR2 (6) Blank No Load or Insert FTVFUND_REAL_GL NUMBER (1) Blank No Load or Insert FTVFUND_ACCT_CODE_TRF_RGL VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_TRF_RGL VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_TRF_RGL VARCHAR2 (6) Blank No Load or Insert FTVFUND_REAL_GL_PY NUMBER (1) Blank No Load or Insert FTVFUND_ACCT_CODE_TRF_RGL_PY VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_TRF_RGL_PY VARCHAR2 (6) Blank No Load or Insert FTVFUND_PROG_CODE_TRF_RGL_PY VARCHAR2 (6) Blank No Load or Insert FTVFUND_DISTRIBUTION_IND_INC VARCHAR2 (2) Blank No Load or Insert FTVFUND_DISTRIBUTION_IND_RGL VARCHAR2 (2) Blank No Load or Insert FTVFUND_SPENDABLE_RATE NUMBER (6,2) Blank No Load or Insert FTVFUND_SPEND_FORMULA_FREQ_IND VARCHAR2 (1) Blank No Load or Insert FTVFUND_FBAL_IND VARCHAR2 (4) Optional Spreadsheet Data File FTVFUND_REST_IND VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_PROP_CODE VARCHAR2 (9) Blank No Load or Insert FTVFUND_DEPR_POST_CODE VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_FUND_CODE_ALLOC_TGT VARCHAR2 (6) Blank No Load or Insert FTVFUND_ORGN_CODE_ALLOC_CONTRA VARCHAR2 (6) FTVFUND_ACCT_CODE_ALLOC_CONTRA VARCHAR2 (6) FTVFUND_PROG_CODE_ALLOC_CONTRA VARCHAR2 (6) Blank No Load or Insert Blank No Load or Insert Blank No Load or Insert FTVFUND_ALLOC_PCT NUMBER (5,2) Blank No Load or Insert FTVFUND_ACCT_CODE_GAIN VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_ACCT_CODE_LOSS VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_ORGN_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_PROG_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_ACTV_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_LOCN_CODE_CAP_DEF VARCHAR2 (6) Optional Spreadsheet Data File FTVFUND_DEPR_EXP_EQ_DEF_IND VARCHAR2 (1) Optional Spreadsheet Data File FTVFUND_SRC_CAP_SAME_IND VARCHAR2 (1) Default = N FTVFUND_EXPEND_END_DATE DATE Blank No Load or Insert FTVFUND_CASH_RECEIPT_BANK_CODE VARCHAR2 (2) Blank No Load or Insert If using legacy ID; Use function for PIDM translation. PIDM must also exist in FTVFMGR and SPRIDEN. GXVBANK Table GXVBANK Bank Code (Electronic or Manual depending upon number of values). Use GXRBANK Excel Spreadsheet to load client s defined Bank Codes. These can be July 2005 SCT Plus to SCT Banner Migration Tools 2-13