System Testing

Policy

Each time the ERP system is updated with patches or enhancements, updates are loaded into a test environment and all regular processes are tested to ensure functionality before loading the updates into the production environment. Testing plans are designed to be completed in 1-2 business days to ensure updates can be loaded to production timely.

Procedures

Test plans for each module should follow the sequence and timing indicated below to ensure each module that is affected by another module is appropriately tested with the updates. Information Technology staff should communicate with the Controller and all key personnel to inform them when system updates are available and ready to test, and again when updates have been successfully loaded to production.

Responsible position(s):

• As indicated in the steps

Required documents and access:

• Banner

Frequency and timing:

• Ad hoc, as updates are available and new system features are implemented

Steps:

• Chart of accounts maintenance – CONTROLLER creates new FOAPAL elements including restricted and unrestricted sources.
• oFund – FTMFUND Fund Code Maintenance
• 199999 Unrestricted Test
• 299999 Restricted Grant Test
• 919999 Capital Project Test
• 619999 Endowment Test
• oOrganization – FTMORGN Organization Code Maintenance
• 599999 Test Organization
• oAccount – FTMACCT Account Code Maintenance
• 1999 Test Asset
• 2999 Test Liability
• 5999 Test Revenue
• 7799 Test Capital Expense

-

• oProgram – FTMPROG Program Code Maintenance
• ■ 999 Test Program
• oActivity – FTMACTV Activity Code Maintenance (optional)