When viewing data in Tax Submission, the system recomputes the values then displays the data in grid.

The following issues can arise from this method:

1. History data can be different when the pay code classification changes.
2. Recompute of view data takes approx 40-50s on a large database and can have huge impact on performance.

Recommended solution:

1. Create a detail table that holds the values for the tax submission. This table is populated as part of the background process that creates the file.
2. When viewing data, do not recompute values, rather pick these from the detail table.

PART A - Development work for this case has been completed.

1. The change will be available in version:12.32.0310

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

1. Created a database table to store data for the tax submission. This table is populated as part of the background process that creates the file.
2. When viewing data, we do not need to recompute the values, rather pick these from the detail table
3. If data is not available, the system will compute the data and store it in the new table. This means that "Tax Submissions" that were done before this change is applied will take some time to compute for the first time. After the compute, the view will be fairly quick.

3. Affected Areas:

1. Payroll Tax Submission

4. The issue was caused by:

1. Performance improvement. View data for tax submissions had a lot of computations and was taking over 40 seconds for 200 records on MLC database. 

5. Notes: 
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): System Test

----------------------

PART B - Development Reference (Place descriptor for objects changed):

1. Changes implemented was according to the approved design (Y/N): Yes

2. Other relevant notes: