Understanding the Transaction Purge Process

The Transaction Purge process is comprised of a single application engine (SCC_SL_PURGE) that is associated with a PeopleTools application package (SCC_SL_PURGE). The application package manages the behavior of the run control component as well as the functionality related to the purge process. The logic and scope of the deletion process is managed by the Entity Registry.

The functionality of the purge process is comprised of:

• Running the purge process in test mode. This allows the end user to review the scope of how many temporary IDs will be deleted based on their criteria prior to actually deleting the temp ID's from staging.

  See Viewing the Purge Log Table.

• Specifying a commit level during processing which reflects your system requirements.

• Deleting by Constituent.

  • Delete a specific constituent along with any/all transactions associated to that constituent.

  • Via Population Selection; delete a list of constituents that you specify, including any/all transactions associated.

  • Via Population Selection; delete a set of constituents as defined by a user query, including any/all transactions associated.

• Deleting by transaction codes.

  • Delete staged data for a transaction code with a specific transaction status. You can also specify that constituent data be deleted as long as no other transactions are associated with the constituent.

  • Delete staged data for a transaction code based on a specific status and date criteria.

• Deleting constituents and transaction codes in a single execution of the Transaction Purge process.