Search Results pay_rates_v




Overview

PAY_RATES_V is a VALID view owned by the APPS schema within the PAY (Payroll) product of Oracle E-Business Suite. Per the ETRM metadata, its documented purpose is to "support user interface," meaning it functions as a presentation-layer object that flattens and decorates the underlying payroll rate definition data with human-readable lookup meanings. Rather than exposing opaque codes, the view resolves lookups for rate units of measure, rate basis, and rate type into their corresponding display values, which makes it suitable for direct consumption by forms, OAF pages, concurrent program outputs, and custom reporting or integration layers.

Because payroll rates are frequently referenced in compensation calculations, benefits administration, and element configuration, this view serves as a convenience access path to PAY_RATES without requiring the caller to write the joins and DECODE logic themselves. It is important to note the view is not a base table; it is a read-oriented projection intended for query, not for direct DML.

Underlying Base Objects

The view is defined over the following documented base objects: PAY_RATES (SYNONYM), PER_PARENT_SPINES (SYNONYM), HR_LOOKUPS (VIEW), FND_LOOKUPS (VIEW), HR_GENERAL (PACKAGE), HR_API (PACKAGE), and FND_GLOBAL (PACKAGE).

Notably, the UNIT join is an inner join, meaning a rate whose RATE_UOM does not resolve to a 'UNITS' lookup value will be excluded from result sets — a behavior worth accounting for when validating data completeness.

Key Columns

  • RATE_ID — Primary identifier for the rate record; the join key back to PAY_RATES.
  • NAME — The user-defined name of the rate.
  • RATE_UOM — The unit-of-measure code for the rate. This is the column surfaced by the search term "rate_uom" and drives the join to the UNITS lookup.
  • UNIT_MEANING — The translated meaning for RATE_UOM from HR_LOOKUPS, providing the readable unit of measure.
  • RATE_TYPE / RATE_TYPE_MEANING — The rate type code and its decoded display value via DECODE_LOOKUP.
  • RATE_BASIS / RATE_BASIS_MEANING — The basis code and its lookup meaning.
  • ASG_RATE_TYPE / ASG_RATE_TYPE_NAME — Assignment rate type and its 'PRICE DIFFERENTIALS' lookup name.
  • PARENT_SPINE_ID / PARENT_NAME — Hierarchical parent linkage and descriptive name.
  • BUSINESS_GROUP_ID, ROW_ID, OBJECT_VERSION_NUMBER — Standard multi-tenant, row-identity, and optimistic-locking columns.
  • WHO columnsCREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the REQUEST_ID / PROGRAM_* audit columns.
  • ATTRIBUTE1–ATTRIBUTE20, ATTRIBUTE_CATEGORY — Descriptive flexfield segments.

Common Use Cases and Queries

Typical scenarios include listing all rates with readable units for a business group, filtering by unit of measure, and joining rates to payroll elements for validation.

List rates and their decoded attributes:

SELECT rate_id, name, rate_uom, unit_meaning,
rate_type_meaning, rate_basis_meaning
FROM apps.pay_rates_v
WHERE business_group_id = :p_bg_id
ORDER BY name;

Filter by a specific unit of measure:

SELECT rate_id, name, rate_uom
FROM apps.pay_rates_v
WHERE rate_uom = 'HOUR';

Retrieve lookup meanings for a set of units to confirm valid RATE_UOM values:

SELECT rate_uom, unit_meaning
FROM apps.pay_rates_v
GROUP BY rate_uom, unit_meaning;

Because all joins are either inner on UNITS or outer elsewhere, and the view carries no bind variables, it can be queried freely from BI Publisher, custom PL/SQL, or the EBS web layer. For data-fix or DML operations, developers should target the PAY_RATES base table directly rather than this view.