Search Results pa_std_bill_rate_schedules




Overview
Explore in AI Chat

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, PA_STD_BILL_RATE_SCHEDULES is a Projects (PA) module view that exposes standard billing rate schedule definitions. The ETRM metadata classifies the object as a single-organization (Single-Org) view, meaning its result set is intentionally restricted to the operating unit context of the querying session rather than returning the full multi-organization data set. This design traces to the Oracle Multi-Org (MOAC) architecture introduced in Release 12, in which operating-unit security is enforced at the view layer so that application forms, concurrent programs, and reports automatically see only the records belonging to the current organization.

Standard billing rate schedules drive the automatic derivation of bill rates on eligible project and task assignments. Each schedule defines rate lines by job group and currency, and the schedule can optionally be shared across operating units. The view therefore functions as the read interface for rate schedule data used in billing, revenue generation, and rate validation flows.

Underlying Base Objects

The view is defined over the table PA_STD_BILL_RATE_SCHEDULES_ALL, which stores rows for every operating unit. The single-org view applies a WHERE clause that compares the row's ORG_ID to the organization identifier retrieved from the USERENV('CLIENT_INFO') session context:

  • NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTR(USERENV('CLIENT_INFO'),1,10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTR(USERENV('CLIENT_INFO'),1,10))), -99)

This pattern is the standard Oracle Multi-Org view predicate: rows whose ORG_ID is null or matches the session's operating unit are returned. The ETRM excerpt notes the object is "Not implemented in this database," indicating the view was not instantiated in the sampled environment, and no referenced base objects are separately documented. In a functioning installation, the base table PA_STD_BILL_RATE_SCHEDULES_ALL and its associated rate line table (for example, PA_STD_BILL_RATE_SCHEDULE_LINES) constitute the physical storage behind this view.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating that a rate schedule exists before assignment to a project, reconciling schedules by currency or job group, and joining schedule headers to rate lines for billing extracts. Because the view is org-filtered, reports run in a specific operating unit return only that unit's schedules unless the share flag permits broader access.

  • List active schedules for the current operating unit: SELECT bill_rate_sch_id, std_bill_rate_schedule, rate_sch_currency_code FROM pa_std_bill_rate_schedules WHERE schedule_type = 'STANDARD';
  • Filter by job group and currency: SELECT std_bill_rate_schedule, job_group_id, rate_sch_currency_code FROM pa_std_bill_rate_schedules WHERE job_group_id = :job_group_id;
  • Identify schedules shared across operating units: SELECT std_bill_rate_schedule, org_id FROM pa_std_bill_rate_schedules WHERE share_across_ou_flag = 'Y';

When multi-organization access is required beyond the session context, query the base table PA_STD_BILL_RATE_SCHEDULES_ALL directly, since the view intentionally suppresses cross-org visibility.