Results for “per_pay_bases”

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

Overview

PER_PAY_BASES is a Human Resources (PER) module table that stores the definitions of specific salary bases used throughout Oracle E-Business Suite 12.1.1 and 12.2.2. A pay basis record defines how an employee's compensation is calculated and annualized — for example, whether pay is expressed hourly, weekly, monthly, or annually — and it serves as the reference point that assignments, positions, and element links use to derive compensation amounts. The object is owned by the HR schema and is documented as VALID in ETRM for release 12.2.2, containing 59 physical columns.

The table sits at the center of the compensation model rather than at its transactional edge. Many dependent tables across HR, Payroll (PAY), Benefits (BEN), and position control (PQH) carry a PAY_BASIS_ID foreign key back to PER_PAY_BASES. Consistent with that role, the ETRM relationship metadata classifies this object heuristically as hub-leaning within a Data Vault model. This classification is a modeling suggestion only: PER_PAY_BASES behaves like a hub because it anchors a stable, reusable business concept (the pay basis) that is referenced by numerous surrounding link and satellite structures. It is not itself a link or satellite, but the definitional hub to which transactional and assignment-level records connect.

Key Information Stored

The table's surrogate primary key is PAY_BASIS_ID, enforced by the PER_PAY_BASES_PK unique index. Beyond that surrogate, several business-key candidates are documented through unique indexes. PER_PAY_BASES_UK2 covers NAME together with BUSINESS_GROUP_ID, meaning a pay basis is uniquely named within a business group. PER_PAY_BASES_UK3 covers INPUT_VALUE_ID, RATE_ID, and BUSINESS_GROUP_ID, tying a pay basis to a specific input value and rate combination within the business group.

• PAY_BASIS_ID — surrogate primary key identifying each pay basis definition.
• BUSINESS_GROUP_ID — the business group owning the definition; a foreign key to HR_ALL_ORGANIZATION_UNITS and part of both business-key indexes.
• NAME — the user-facing name of the pay basis, unique within its business group.
• INPUT_VALUE_ID — the input value associated with the salary basis, part of PER_PAY_BASES_UK3.
• RATE_ID — foreign key to PAY_RATES, linking the pay basis to its rate definition.
• PAY_BASIS — the code designating the pay basis type (for example hourly versus salaried treatment).
• RATE_BASIS — the basis used to determine the applicable rate.
• ANNUALIZED_HOURS — the hours used to annualize pay for this basis.
• PAY_ANNUALIZATION_FACTOR — the factor applied to convert pay to an annual equivalent.
• GRADE_ANNUALIZATION_FACTOR — the corresponding factor applied to grade-based amounts.
• INFORMATION_CATEGORY and INFORMATION1–INFORMATION20 — a flexfield-style descriptive segment block for additional classification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard EBS descriptive flexfield attribute columns.
• COMMENTS — free-text notes describing the pay basis.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ORM layer.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most frequent requirement is listing the valid pay bases for a business group, typically joined to assignments or positions to explain how compensation is annualized.

SELECT pb.pay_basis_id, pb.name, pb.pay_basis, pb.rate_basis,
  pb.annualized_hours, pb.pay_annualization_factor
FROM per_pay_bases pb
WHERE pb.business_group_id = :p_bg_id
ORDER BY pb.name;

A second common pattern joins pay bases to pay rates to reproduce the effective rate configuration:

SELECT pb.name, pr.rate_id, pr.rate_value
FROM per_pay_bases pb, pay_rates pr
WHERE pb.rate_id = pr.rate_id
AND pb.business_group_id = :p_bg_id;

Because PER_ALL_ASSIGNMENTS_F and HR_ALL_POSITIONS_F carry PAY_BASIS_ID, analysts frequently join those tables to PER_PAY_BASES to report annualized salary, to audit assignments whose pay basis differs from the position default, or to feed warehouse extracts such as HR_EDW_WRK_ACTVTY_F. Payroll and Benefits reporting similarly resolve benefit eligibility rates through BEN_ELIG_PY_BSS_PRTE_F and BEN_PY_BSS_RT_F, both of which reference this table.

Related Objects

PER_PAY_BASES participates in a dense web of documented relationships. It references PAY_RATES through RATE_ID and HR_ALL_ORGANIZATION_UNITS through BUSINESS_GROUP_ID. In the reverse direction, the following significant objects reference PER_PAY_BASES.PAY_BASIS_ID:

• HR_ALL_POSITIONS_F — positions accept a default pay basis.
• PER_ALL_ASSIGNMENTS_F — assignments carry the employee's pay basis.
• PAY_ELEMENT_LINKS_F — payroll element links resolve amounts via the pay basis.
• PQH_POSITION_TRANSACTIONS and PQH_PTX_SHADOW — position control transactions retain the pay basis.
• BEN_ELIG_PY_BSS_PRTE_F and BEN_PY_BSS_RT_F — benefits eligibility and rate records.
• PAY_BATCH_ELEMENT_LINKS — batch payroll processing references the pay basis.
• HR_EDW_WRK_ACTVTY_F and its staging table — Enterprise Data Warehouse workforce activity facts.
• HR_PERSON_DEPLOYMENTS and HR_H2PI_ASSIGNMENTS — deployment and interface structures.

Together these relationships confirm PER_PAY_BASES as a definitional hub for compensation across HR, Payroll, Benefits, and position management in Oracle EBS 12.1.1 and 12.2.2.