Results for “billing_extension_id”

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

Overview

PA_BILLING_ASSIGNMENTS_ALL is the Oracle Projects (PA) table that stores the assignment of billing extensions to a project type, a specific project, or a task. A billing extension defines additional revenue or billing calculations — such as labor multipliers, burden-based rates, or event-driven charges — and this table controls where and under what terms each extension applies. It is the configuration link that determines which billing logic is applied to a given project, project type, or task within an operating unit. The table resides in the PA schema and is an _ALL table, meaning it is partitioned by operating unit via the ORG_ID column, supporting multi-organization deployments in Oracle EBS 12.1.1 and 12.2.2.

Mined from the documented foreign-key structure, the heuristic Data Vault classification for this object is a link. As a modeling suggestion, PA_BILLING_ASSIGNMENTS_ALL behaves as an associative table that resolves many-to-many relationships among billing extensions, project types, projects, tasks, and distribution rules, while also carrying descriptive and rate-related attributes.

Key Information Stored

The table contains 45 documented columns. The most significant are:

• BILLING_ASSIGNMENT_ID — Surrogate primary key component; uniquely identifies each assignment row (combined with ORG_ID).
• ORG_ID — Operating unit identifier; the second component of the primary key and the multi-org discriminator.
• BILLING_EXTENSION_ID — Foreign key to PA_BILLING_EXTENSIONS, identifying the billing extension being assigned.
• PROJECT_TYPE — Foreign key to PA_PROJECT_TYPES_ALL, when the extension applies at the project type level.
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL, when the assignment targets a specific project.
• TOP_TASK_ID — Foreign key to PA_TASKS, when the assignment targets a task.
• DISTRIBUTION_RULE — Foreign key to PA_DISTRIBUTION_RULES, linking the assignment to an account distribution rule.
• AMOUNT and PERCENTAGE — Numeric values used by the extension calculation.
• ACTIVE_FLAG — Controls whether the assignment is currently active.
• RATE_OVERRIDE_CURRENCY_CODE, PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE — Currency contexts for rate and exchange-rate derivation.
• PROJECT_RATE_TYPE, PROJFUNC_RATE_TYPE, FUNDING_RATE_TYPE — Rate types applied at project, project functional, and funding levels.
• PROJECT_RATE_DATE, PROJFUNC_RATE_DATE, FUNDING_RATE_DATE and the corresponding exchange-rate columns — Rate dating and conversion factors.
• RECORD_VERSION_NUMBER — Optimistic locking / concurrency control.
• Standard _ALL columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and ATTRIBUTE1–ATTRIBUTE15 (DDF extensibility).

The business-key candidate is captured by the unique index PA_BILLING_ASSIGNMENTS_U1 (BILLING_ASSIGNMENT_ID, ORG_ID, ZD_EDITION_NAME), which extends the primary key with the edition name in the 12.2.2 schema.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include identifying which extensions apply to a project, verifying rate overrides, and auditing active assignments by operating unit.

• List all active assignments for a project:

SELECT ba.billing_assignment_id, be.name, ba.active_flag
FROM   pa_billing_assignments_all ba,
       pa_billing_extensions be
WHERE  ba.billing_extension_id = be.billing_extension_id
AND    ba.project_id = :project_id
AND    ba.org_id = :org_id;

• Join to PA_PROJECTS_ALL to retrieve project-level assignment detail.
• Join to PA_TASKS on TOP_TASK_ID for task-level billing logic.
• Join to PA_DISTRIBUTION_RULES to reconcile distribution rule usage.
• Report extension usage by project type for configuration auditing.
• Extract rate type and currency data for financial reconciliation.

Related Objects

The documented foreign keys define the principal related objects:

• PA_BILLING_EXTENSIONS — joined on BILLING_EXTENSION_ID.
• PA_PROJECT_TYPES_ALL — joined on PROJECT_TYPE.
• PA_PROJECTS_ALL — joined on PROJECT_ID.
• PA_TASKS — joined on TOP_TASK_ID.
• PA_DISTRIBUTION_RULES — joined on DISTRIBUTION_RULE.

These relationships, combined with the ORG_ID multi-org column and PA_BILLING_ASSIGNMENTS_U1, position this table as a central configuration link within Oracle Projects billing.