Review EBS product's new releases & features, troubleshooting tips & tricks, best practices, upcoming webcasts

Managing Growth of Oracle Payroll Transactional Tables

database administrators are aware that over time that the Oracle
Payroll processes can store potentially large amounts of information to
the database.   They also know, that this can have an adverse effect,
from supplying larger amounts of database storage to potential
performance issues due to queries executing across high volume tables.

To ease this overhead, Oracle Payroll delivers multiple features
that can reduce the amount of payroll data held on the database.  These
features have been documented and are delivered in the whitepaper

Best Practices to Reduce Existing Volume and Limit Future Growth of Transactional Tables (Doc. ID 2031293.1)

This document lists the various features with online references
that detail the process and how to enable / implement the feature if it
is available for localization. These features include:

  • Sparse matrix / Insignificant Run Results
  • Payroll Purge
  • Single Latest Balances Upgrade
  • Database Compression
  • Event Model
  • Run Balances

It is HIGHLY recommended that you discuss these options with your database administrator or payroll manager

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.