Seems some future dated non-cash timerecords were processed and closed causing the next TA cycle to be closed for a large number of co-workers. The lawson corrective measure...paint a screen to update the timerecords, purge the employees from the plan, re-enroll employees in the plans, re-convert starting balances and then let the system re-calc everything the next processing period is not a practical solution for the over 1,000 people who were impacted. Can the "run_date" on EMTAMASTR be updated directly (paint screen, add-ins, rngdbdmp/dbimport, sql). The last period end date is off by 1 period (2 weeks).