Results for “pay_backpay_rules”

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

Overview

PAY_BACKPAY_RULES is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the set of balances that a RetroPay process must recalculate when backpay is triggered. Each row associates a defined balance — and, where applicable, a specific input value — with a backpay set, giving the payroll engine an explicit rule-driven scope for retroactive recalculation rather than recalculating every balance indiscriminately.

Based on the foreign key structure mined from the metadata, the table is best modeled as a link entity. It resolves a many-to-many style association between backpay sets (PAY_BACKPAY_SETS) and defined balances (PAY_DEFINED_BALANCES), with the optional INPUT_VALUE_ID adding a further level of granularity. It carries no independent descriptive payload beyond standard audit columns, which reinforces its classification as a link rather than a hub or satellite.

Key Information Stored

The table exposes eight documented columns. The three business-meaningful columns form the primary key and are the columns most relevant to any query or integration:

• DEFINED_BALANCE_ID — Identifies the defined balance (from PAY_DEFINED_BALANCES) that the RetroPay process is permitted to recalculate. Part of the composite primary key.
• INPUT_VALUE_ID — Narrows the rule to a specific input value assigned to the balance element. Part of the composite primary key; permits balance-element-level rather than aggregate-level rules.
• BACKPAY_SET_ID — Identifies the backpay set (from PAY_BACKPAY_SETS) to which this rule belongs. Part of the composite primary key and the grouping column for all rules applied together.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit trail columns recording when and by whom the rule row was last modified.
• CREATED_BY, CREATION_DATE — Standard audit columns recording rule row creation.

The surrogate identifier is not a generated sequence value; PAY_BACKPAY_RULES_PK is itself a composite business key over (DEFINED_BALANCE_ID, INPUT_VALUE_ID, BACKPAY_SET_ID). Practitioners should therefore treat this three-column combination as the unique business-key candidate and avoid assuming a single-column primary key exists.

Common Use Cases and Queries

Typical usage centers on auditing and troubleshooting which balances a RetroPay run will recalculate, and on comparing rules across backpay sets during setup migration or regression testing.

• List every balance included in a given backpay set:

SELECT r.backpay_set_id, r.defined_balance_id, r.input_value_id
FROM   hr.pay_backpay_rules r
WHERE  r.backpay_set_id = :p_backpay_set_id;

• Find which backpay sets reference a particular balance (impact analysis before changing a balance definition):

SELECT s.* , r.backpay_set_id
FROM   hr.pay_backpay_rules r
       JOIN hr.pay_backpay_sets s ON s.backpay_set_id = r.backpay_set_id
WHERE  r.defined_balance_id = :p_defined_balance_id;

• Detect duplicate or orphaned rule rows, and review recent maintenance via the audit columns (LAST_UPDATED_BY, LAST_UPDATE_DATE).
• Reporting: render a human-readable rule listing by joining to the balance and backpay set definitions for setup documentation and post-patch validation.

Related Objects

• PAY_BACKPAY_SETS — Parent grouping object; joined on PAY_BACKPAY_RULES.BACKPAY_SET_ID = PAY_BACKPAY_SETS.BACKPAY_SET_ID.
• PAY_DEFINED_BALANCES — Defines the balance being recalculated; joined on PAY_BACKPAY_RULES.DEFINED_BALANCE_ID = PAY_DEFINED_BALANCES.DEFINED_BALANCE_ID.
• PAY_BALANCE_INPUT_VALUES — Candidate source for INPUT_VALUE_ID resolution against balance input values.
• PAY_ELEMENT_TYPES / PAY_BALANCES — Related payroll definition objects typically joined through PAY_DEFINED_BALANCES for reporting.
• PAY_RETRO_RUNS and the RetroPay process — Runtime consumers that read these rules to determine recalculation scope.