Search Results bill_rate_unit_m




Overview
Explore in AI Chat

Overview

APPS.PA_BILL_RATES_RC is a supplementary view in the Oracle E-Business Suite Projects (PA) module. The "_RC" suffix denotes a "row context" or reference-coded view that Oracle classifies as a supplementary view intended to simplify Oracle Forms coding. Oracle explicitly warns that this view is not recommended for direct query or data modification, and its definition may change dramatically across minor or major releases. In Oracle EBS 12.1.1 and 12.2.2, the object resides in the APPS schema with status VALID and is registered under FND Design Data as PA.PA_BILL_RATES_RC.

The view exposes bill rate schedule rows enriched with human-readable descriptive attributes, most notably BILL_RATE_UNIT_M — the search term provided — which returns the meaning of the rate unit lookup rather than its internal code. This makes the view valuable for reporting layers, forms personalizations, and integration extracts that require decoded lookup values without joining to FND_LOOKUP_VALUES manually.

Underlying Base Objects

The documented referenced objects are:

  • PA_BILL_RATES (SYNONYM) — the primary transactional source holding bill rate schedule definitions, rates, effective dates, and assignments.
  • PA_RESOURCE_CLASSES_VL (VIEW) — provides resource class code and translated resource class name.
  • HR_ORGANIZATION_UNITS (VIEW) — supplies organization context for the bill rate organization.
  • FND_LOOKUP_VALUES (SYNONYM) — decodes lookup codes, including the bill rate unit meaning exposed in BILL_RATE_UNIT_M.
  • HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) — supply person-level attributes (name, employee number) and enforce HR security predicates.

Because PA_BILL_RATES_RC joins these sources internally, consumers obtain person, job, resource class, and lookup descriptions in a single row, avoiding repeated outer joins in ad hoc queries.

Key Columns

Common Use Cases and Queries

Typical scenarios include extracting bill rate schedules for reconciliation, building rate card reports, and validating rate units in conversion programs.

SELECT bill_rate_sch_id,
       std_bill_rate_schedule,
       full_name,
       job_name,
       bill_rate_unit_m,
       rate,
       rate_currency_code,
       start_date_active,
       end_date_active
FROM   apps.pa_bill_rates_rc
WHERE  bill_rate_unit_m = 'Hour'
AND    TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

A second pattern joins the view to project assignments to confirm effective rates at a point in time:

SELECT r.person_id,
       r.full_name,
       r.job_name,
       r.bill_rate_unit_m,
       r.rate,
       r.rate_currency_code
FROM   apps.pa_bill_rates_rc r
WHERE  r.bill_rate_organization_id = :org_id
AND    r.expenditure_type = :exp_type
ORDER BY r.full_name, r.start_date_active;

Given Oracle's explicit warning, developers should treat PA_BILL_RATES_RC as a convenience surface for read-only reporting and forms behavior, not as a stable integration contract. For production interfaces, base tables such as PA_BILL_RATES combined with FND_LOOKUP_VALUES joins provide a more durable alternative.