Results for “pay_backpay_sets”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_BACKPAY_SETS is a core configuration table within the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. It identifies backpay, or RetroPay, sets used by the payroll engine to calculate and process retroactive payments. A backpay set groups together the rules and payroll actions that control how an employee's historical earnings differences are recalculated and disbursed when prior payroll results change. Each row represents a distinct backpay set definition that the payroll run references when determining retroactive liability.

Based on the foreign key structure mined from the metadata, PAY_BACKPAY_SETS carries a hub-leaning Data Vault classification. This means the table behaves primarily as a central reference entity whose surrogate key (BACKPAY_SET_ID) is referenced by dependent child tables, rather than acting as a pure link or satellite. This classification is a modeling suggestion: the table's role as a stable, uniquely-identified business concept aligns with a hub pattern, while descriptive attributes such as name and description would typically be split into a satellite in a formal Data Vault design.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • BACKPAY_SET_ID — The surrogate primary key, defined by the unique index PAY_BACKPAY_SETS_PK. This is the numeric identifier that child tables reference.
  • BACKPAY_SET_NAME — The user-facing name of the backpay set, serving as a natural business-key candidate that end users recognize in the application.
  • BACKPAY_SET_TYPE — Classifies the backpay set type, driving how the payroll engine applies retroactive processing logic.
  • LEGISLATION_CODE — The legislative jurisdiction under which the backpay set operates, ensuring country-specific retro rules apply.
  • BUSINESS_GROUP_ID — The enterprise or business group that owns the set, providing multi-tenant separation within the HR schema.
  • DESCRIPTION — Free-text explanation of the set's purpose for administrative clarity.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording row creation.

The surrogate key (BACKPAY_SET_ID) is distinct from the business-key candidate (BACKPAY_SET_NAME), which is unique from a business perspective but is not enforced by a separate documented unique index.

Common Use Cases and Queries

Typical use cases include auditing retroactive payroll configuration, reporting which backpay sets are active per legislation, and tracing payroll actions back to their governing set. The following query lists all backpay sets for a given legislation:

  • SELECT BACKPAY_SET_ID, BACKPAY_SET_NAME, BACKPAY_SET_TYPE, DESCRIPTION FROM HR.PAY_BACKPAY_SETS WHERE LEGISLATION_CODE = :p_legislation ORDER BY BACKPAY_SET_NAME;

To find which backpay rules belong to a set, join to the child table:

To identify payroll actions configured against a set:

Reporting use cases include retrospective liability analysis, configuration review before a payroll run, and troubleshooting of unexpected retro calculations.

Related Objects

The documented foreign key relationships identify the principal dependent objects:

  • PAY_BACKPAY_RULES — References PAY_BACKPAY_SETS via BACKPAY_SET_ID. Holds the individual rules that define how retro calculations are performed for a set.
  • PAY_PAYROLL_ACTIONS — References PAY_BACKPAY_SETS via BACKPAY_SET_ID. Associates payroll actions with the governing backpay set.

In practice these are the two child tables that most directly depend on PAY_BACKPAY_SETS, forming a hub-and-child pattern consistent with the heuristic Data Vault classification. Both joins use the BACKPAY_SET_ID surrogate key, which reinforces its role as the stable central identifier for retroactive payroll configuration.