Search Results hr_u




Overview

APPS.PAY_RATES_V is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents rate definitions maintained within the Oracle Payroll rates framework. The base rate information is stored in PAY_RATES, while the view enriches each row with decoded, human-readable descriptions sourced from multiple lookup and parent-spine objects. This design spares developers and report authors from repeatedly joining lookup tables and applying DECODE logic themselves.

The view was created specifically so that descriptive values — such as the unit of measure, the rate basis, and the assignment rate type — are exposed as named columns rather than raw codes. Because these lookups are resolved inside the view definition, external consumers receive consistent labels regardless of which reporting tool or interface they use. This is particularly relevant when building concurrent program outputs, BI Publisher data templates, or custom API-driven integrations.

Underlying Base Objects

The documented base objects referenced by PAY_RATES_V are:

The joins to HR_R and FND_ART are outer joins (+), meaning rows are still returned when no matching lookup exists. The join to PER_PARENT_SPINES is likewise an outer join on PARENT_SPINE_ID.

Key Columns

Common Use Cases and Queries

Typical uses include payroll rate validation reports, integration extracts for third-party payroll or time systems, and diagnostic queries resolving lookup codes for support activities.

Retrieve rates for a business group:

  • SELECT RATE_ID, NAME, UNIT_MEANING, RATE_BASIS_MEANING, RATE_TYPE_MEANING FROM APPS.PAY_RATES_V WHERE BUSINESS_GROUP_ID = :p_bg_id;

Establish the source of a unit-of-measure label (the "hr_u" lookup join):

  • SELECT RATE_ID, RATE_UOM, UNIT_MEANING FROM APPS.PAY_RATES_V WHERE RATE_UOM IS NOT NULL ORDER BY RATE_UOM;

Report on rates with their parent spine for hierarchy analysis:

  • SELECT PARENT_NAME, NAME, RATE_TYPE_MEANING, RATE_BASIS_MEANING FROM APPS.PAY_RATES_V WHERE PARENT_SPINE_ID IS NOT NULL;

Because lookups are joined with outer joins, defensive filtering on the decoded columns is advisable when consumers require fully populated descriptions.