Results for “billing_title”

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

Overview

PA.PA_JOB_BILL_TITLE_OVERRIDES is a Projects (PA) module table that stores non-standard job billing titles negotiated for specific projects and tasks. Within Oracle EBS 12.1.1 and 12.2.2, it functions as a configuration and reference table that allows organizations to depart from the default billing title associated with a job (from PER_JOBS) by capturing a project- and task-specific override text. This capability is essential when contractual or customer-specific arrangements require a billing descriptor on invoices or revenue documents that differs from the enterprise-wide job name.

Based on the foreign key structure mined from the metadata, the heuristic Data Vault classification for this object is link. This is a modeling suggestion rather than a physical implementation detail: the table resolves associations among jobs, projects, and tasks, with the effective dating columns supplying the change-tracking context that a satellite would otherwise carry. The link interpretation reflects the table's role in binding three business entities together with negotiated override values.

Key Information Stored

The table contains 13 documented columns. The most significant are summarized below.

• JOB_BILL_TITLE_OVERRIDE_ID — The unique surrogate identifier, enforced by unique index PA_JOB_BILL_TITLE_OVERRIDES_U5. This is the business-key candidate for the internal identifier.
• JOB_ID — References PER_JOBS, identifying the job whose default billing title is being overridden. Part of the composite primary key PA_JOB_BILL_TITLE_OVERRIDES_PK.
• PROJECT_ID — References PA_PROJECTS_ALL, identifying the project for which the override applies. Part of the composite primary key.
• TASK_ID — References PA_TASKS, identifying the specific task scope. Part of the composite primary key.
• START_DATE_ACTIVE — The effective start date of the override; completes the composite primary key and supports date-effective resolution.
• END_DATE_ACTIVE — The date on which the override ceases to apply, enabling historical tracking of negotiated titles.
• BILLING_TITLE — The non-standard billing title text presented on billing and revenue outputs for the scoped job, project, and task.
• RECORD_VERSION_NUMBER — Supports optimistic locking and concurrency control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the record and when.

Common Use Cases and Queries

Typical scenarios include verifying which negotiated billing title applies to a given job/project/task combination on a specific date, auditing overrides that were superseded by END_DATE_ACTIVE, and feeding billing and invoicing reports with the correct descriptor. A representative query resolving the active override is:

• SELECT o.billing_title FROM pa.pa_job_bill_title_overrides o WHERE o.job_id = :job_id AND o.project_id = :project_id AND o.task_id = :task_id AND TRUNC(SYSDATE) BETWEEN o.start_date_active AND NVL(o.end_date_active, TRUNC(SYSDATE));
• Auditing expired overrides by filtering on end_date_active IS NOT NULL and ordering by start_date_active.
• Joining to PER_JOBS to compare the overridden title against the default job name for variance reporting.

Related Objects

• PER_JOBS — Provides the base job definition; joined on JOB_ID.
• PA_PROJECTS_ALL — The project master; joined on PROJECT_ID.
• PA_TASKS — The task detail; joined on TASK_ID.
• PA_JOB_BILL_TITLE_OVERRIDES_PK — Primary key constraint over JOB_ID, PROJECT_ID, TASK_ID, START_DATE_ACTIVE.
• PA_JOB_BILL_TITLE_OVERRIDES_U5 — Unique index over JOB_BILL_TITLE_OVERRIDE_ID.

Project billing and revenue processes referencing job billing titles depend on this table to produce contractually correct output.