Archiving / Purge Issues for Benefits Administration
(Doc ID 607160.1)
Last updated on FEBRUARY 02, 2023
Applies to:
PeopleSoft Enterprise HCM Benefits Administration - Version 7.5 and laterInformation in this document applies to any platform.
Symptoms
PeopleSoft does not deliver particular parameters for archiving and purging BAS_PARTIC records. The role of the Benefits Administration start date is considered when determining the amount of history to maintain. At minimum, maintain BAS_PARTIC records back to at least the most recent open enrollment and probably a few months before that. Explore the possibilities of doing a purge of BAS_PARTIC_COST before purging the other BAS_PARTIC tables, as cost will only be needed when events are reprocessed and are not required for Use History functions. The amount of event re-opening and intervening events also plays into this consideration.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |