We have the PeopleSoft Benefits Administration module implemented and would like to archive the bas partic tables to improve Ben Admin run time and move the Ben Admin Start Date to reduce the retroactive period Ben Admin has to 'look at' for processing (currently 1/1/2006).  When we originally implemented, we ran the snapshot process setting SNP events to validate the converted Base Benefits data against the new eligibility rules.  
 
If we archive the history rows in the bas partic tables, we want to re-baseline the employees' eligibility as of a certain date so Ben Admin has a least one row of Bas Partic data to hit against.  We plan to run the snapshot process to set a new SNP event with the effective date equal to the new Ben Admin Start Date.  Bas partic records prior to this new Ben Admin Start Date will be archived.  All existing employees will have a new bas partic record effective on the new Ben Admin Start Date.  
 
·Has anyone taken a similar approach when archiving bas partic data and/or moving the Ben Admin Start Date?  I want to validate our approach makes sense.
·Is anyone aware of issues running another snapshot as of a more current date (using new Snapshot ID, etc.) aside from having to deal with ineligibility issues that show on new SNP event?
·If we archive the Bas Partic tables and leave all the data in the Base Benefits tables, has anyone experienced issues if the Base Benefit data is changed?

Any feedback is appreciated - concerns, potential issues, etc.

Thanks,
 
Kate
 
Proposed Bas Partic Tables to archive:
PS_BAS_PARTIC
PS_BAS_PARTIC_ELIG        
PS_BAS_PARTIC_DPND       
PS_BAS_PARTIC_PLAN       
PS_BAS_PARTIC_COST       
PS_BAS_PARTIC_OPTN