Results for “integration_id”

50+ results




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

Overview

PA_BILL_RATES_ALL is the Oracle Projects (PA) transactional table that stores the bill rates and markup percentages belonging to standard bill rate schedules. Each row defines the rate or markup that Oracle Projects applies when generating revenue and invoices for a given combination of bill rate schedule, person, job, expenditure type, non-labor resource, or resource class. The table is owned by the PA schema and is present and valid in both Oracle E-Business Suite 12.1.1 and 12.2.2.

The "ALL" suffix indicates that the table is partitioned by operating unit through the ORG_ID (multi-organization) column, so a single physical table serves all operating units while row-level security restricts visibility. From a Data Vault modeling perspective, the documented foreign-key structure classifies this object heuristically as a link: it sits at the intersection of several reference entities—bill rate schedules, jobs, job groups, expenditure types, non-labor resources, currencies, and people—and resolves them into a rate or markup value effective over a dated interval. Consumers should treat this classification as a modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table contains 23 columns in the documented 12.2.2 schema. The most operationally significant are listed below.

The primary key constraint is PA_BILL_RATES_PK, defined over BILL_RATE_ORGANIZATION_ID, STD_BILL_RATE_SCHEDULE, PERSON_ID, START_DATE_ACTIVE, JOB_ID, EXPENDITURE_TYPE, NON_LABOR_RESOURCE, and ORG_ID. The unique index PA_BILL_RATES_U1 extends this business key with RESOURCE_CLASS_CODE and RES_CLASS_ORGANIZATION_ID, reflecting the full grain at which a rate line must be unique. Note that BILL_RATE_SCH_ID and INTEGRATION_ID are surrogate/interface identifiers rather than business-key candidates.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include verifying that every active schedule has effective-dated rate lines, resolving the rate applied to a specific person or job for a given period, and auditing markup percentages prior to revenue generation.

  • Listing active rates for a schedule: SELECT person_id, job_id, expenditure_type, rate, rate_currency_code FROM pa_bill_rates_all WHERE std_bill_rate_schedule = :schedule AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE) AND org_id = :org_id;
  • Finding person-specific overrides: filter on PERSON_ID IS NOT NULL and compare against the corresponding job-level line.
  • Markup analysis: query rows where MARKUP_PERCENTAGE IS NOT NULL to review schedule-level markup policy.
  • Effective-dating gaps: identify overlapping or missing START_DATE_ACTIVE/END_DATE_ACTIVE intervals for the same business key.

Related Objects

The most significant objects related to PA_BILL_RATES_ALL, based on the documented foreign keys and primary key, are:

  • PA_STD_BILL_RATE_SCHEDULES_ALL — joined via BILL_RATE_ORGANIZATION_ID and STD_BILL_RATE_SCHEDULE; the parent schedule definition.
  • PER_JOBS — joined via JOB_ID.
  • PER_JOB_GROUPS — joined via JOB_GROUP_ID.
  • PA_EXPENDITURE_TYPES — joined via EXPENDITURE_TYPE.
  • PA_NON_LABOR_RESOURCES — joined via NON_LABOR_RESOURCE.
  • FND_CURRENCIES — joined via RATE_CURRENCY_CODE.
  • PER_ALL_PEOPLE_F — the logical source of PERSON_ID values used by rate resolution.