Results for “bill_rate_unit”

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

Overview

PA.PA_EMP_BILL_RATE_OVERRIDES is a transaction-level table within the Oracle Projects (PA) module that stores non-standard employee bill rates negotiated for specific projects and tasks. While the standard billing rate derivation in Oracle EBS relies on rate schedules assigned to employees, organizations, and projects through the core bill rate infrastructure, this table captures the exception path: agreements between a delivery organization and a customer that deviate from published or schedule-driven rates for a named person performing a named scope of work.

Each row binds a person to a project and task combination for a defined date range, with the negotiated rate expressed as an absolute amount, a currency, and an optional discount. Because the table is keyed on the combination of employee, project, task, and effective start date, it functions as a temporal override register rather than a master list of employees or projects.

From a Data Vault modeling perspective, the heuristic classification of this object is a link. The table exists primarily to associate independent business entities — person, project, and task — and to record the negotiated commercial terms that apply to that association over time. Surrounding employee, project, and task attributes would be modeled as hubs or satellites; the override record itself is the connective, relationship-bearing artifact.

Key Information Stored

The table documents 17 columns in the ETRM 12.2.2 physical schema. The most significant are:

• EMP_BILL_RATE_OVERRIDE_ID — the system-generated surrogate identifier. It is enforced by the unique index PA_EMP_BILL_RATE_OVERRIDES_U2 and provides a single-column handle for the override record.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL, identifying the project to which the negotiated rate applies.
• TASK_ID — foreign key to PA_TASKS, narrowing the override to a specific task or work breakdown element.
• PERSON_ID — the employee or contingent worker whose billing is being overridden.
• RATE — the negotiated bill rate amount.
• RATE_CURRENCY_CODE — the currency in which RATE is denominated, permitting cross-currency projects.
• BILL_RATE_UNIT — the unit of measure against which the rate applies (for example, hourly or daily).
• DISCOUNT_PERCENTAGE and RATE_DISC_REASON_CODE — the discount applied relative to a reference rate and the coded business justification for that discount.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective window during which the override governs billing.
• RECORD_VERSION_NUMBER — optimistic locking control used by the Oracle Forms and OAF layers.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO columns providing audit lineage.

The business key candidates are represented by unique index PA_EMP_BILL_RATE_OVERRIDES_U1 (PROJECT_ID, TASK_ID, PERSON_ID, START_DATE_ACTIVE), which also forms the primary key constraint PA_EMP_BILL_RATE_OVERRIDES_PK. This composite key confirms that no two active override periods may begin on the same date for the same person, project, and task.

Common Use Cases and Queries

The primary use case is rate resolution during billing generation. Oracle Projects consults override records before falling back to standard rate schedules, so reporting and reconciliation queries typically filter on project, task, person, and an effective date.

• Active override lookup: select RATE, RATE_CURRENCY_CODE, BILL_RATE_UNIT from PA_EMP_BILL_RATE_OVERRIDES where PROJECT_ID = :p_project and TASK_ID = :p_task and PERSON_ID = :p_person and trunc(sysdate) between START_DATE_ACTIVE and nvl(END_DATE_ACTIVE, sysdate).
• Override inventory for a project: join to PA_PROJECTS_ALL and PA_TASKS to produce a listing of every negotiated rate on the engagement, useful during contract audits and margin reviews.
• Discount exposure: aggregate DISCOUNT_PERCENTAGE by RATE_DISC_REASON_CODE to quantify how much revenue is being conceded and for what stated business reason.
• Expiration monitoring: filter on END_DATE_ACTIVE within the next 30/60/90 days to drive renewal or renegotiation workflows.
• Reconciliation to billing: compare override RATE values against revenue generated in expenditure and billing item tables for the same person and period to detect unbilled or mis-rated time.
• Currency exposure: group by RATE_CURRENCY_CODE to identify overrides denominated outside the project's functional currency.

Related Objects

The following objects are the most significant dependencies and references for this table:

• PA_PROJECTS_ALL — joined on PROJECT_ID; the parent project definition supplying project number, name, and currency.
• PA_TASKS — joined on TASK_ID; supplies task number, name, and task-level billing attributes.
• PER_ALL_PEOPLE_F — the HR source for PERSON_ID, providing the employee's name, number, and assignment history.
• PA_BILL_RATE_SCHEDULES and the related rate schedule override tables — the default rate infrastructure that this table supersedes when a non-standard rate is negotiated.
• PA_PROJECT_CUSTOMERS — identifies the customer receiving the billed rate, relevant when multiple customers share a project.
• PA_EXPENDITURES_ALL and PA_BILL_ITEMS_ALL — the transactional outputs against which overridden rates are ultimately applied and validated.
• PA_EMP_BILL_RATE_OVERRIDES_PK and the associated unique indexes — the integrity enforcement mechanisms that guarantee non-overlapping, uniquely identified override periods.

Together these objects define the complete path from negotiated agreement to billed revenue, with PA_EMP_BILL_RATE_OVERRIDES occupying the exception layer between standard rate schedules and actual billing transactions.