Results for “pa_alloc_run_basis_det”

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

Overview

PA_ALLOC_RUN_BASIS_DET is a transaction detail table in the Oracle Projects (PA) module of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. Its documented description is "Basis information for an allocation run." The table records the basis amounts and percentages used by the allocation engine when distributing costs, revenue, or quantities across projects and tasks during a given allocation run. Each row ties a specific basis line back to the allocation run that generated it, the project and task it applies to, and the allocation rule line that governs it.

Under a heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link table. It resolves relationships among allocation runs (PA_ALLOC_RUNS_ALL), projects (PA_PROJECTS_ALL), tasks (PA_TASKS), and allocation rules, rather than acting as a standalone hub of business entities or a pure descriptive satellite.

Key Information Stored

The documented physical schema in 12.2.2 contains 14 columns. The most significant are:

• RUN_ID — Foreign key to PA_ALLOC_RUNS_ALL. Identifies the allocation run that produced the basis detail. This is the primary grouping key for any query.
• RULE_ID — Identifier of the allocation rule associated with the basis line.
• LINE_NUM — Sequence number of the basis line within the run or rule, providing ordering.
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL; the project to which the basis applies.
• TASK_ID — Foreign key to PA_TASKS; the task to which the basis applies.
• RESOURCE_LIST_MEMBER_ID — Identifier of the resource list member used as the allocation basis source.
• AMOUNT — The basis amount drawn from the source, used to compute allocation shares.
• BASIS_PERCENT — The computed percentage of the total basis attributable to this line.
• LINE_PERCENT — The percentage applied at the individual line level for the allocation.

Standard WHO audit columns are also documented: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. No surrogate single-column primary key is documented in the excerpt; the effective row identity is the composite of RUN_ID, RULE_ID, and LINE_NUM, with PROJECT_ID and TASK_ID serving as business-key candidates.

Common Use Cases and Queries

Typical reporting scenarios include tracing which projects and tasks received basis weight during a run, reconciling basis percentages to 100 percent per rule, and auditing amounts used to drive an allocation. A representative query joins the run and project entities:

• SELECT d.RUN_ID, d.RULE_ID, d.LINE_NUM, d.PROJECT_ID, d.TASK_ID, d.AMOUNT, d.BASIS_PERCENT, d.LINE_PERCENT FROM PA_ALLOC_RUN_BASIS_DET d WHERE d.RUN_ID = :run_id ORDER BY d.RULE_ID, d.LINE_NUM;
• Join to PA_ALLOC_RUNS_ALL on RUN_ID to obtain run dates and status alongside basis detail.
• Join to PA_PROJECTS_ALL on PROJECT_ID and PA_TASKS on TASK_ID to present project and task names in allocation basis reports.

Related Objects

The documented foreign keys define the principal dependencies:

• PA_ALLOC_RUNS_ALL — joined on RUN_ID; parent record of each allocation run.
• PA_PROJECTS_ALL — joined on PROJECT_ID; the project dimension of the basis.
• PA_TASKS — joined on TASK_ID; the task dimension of the basis.
• Allocation rule and resource list tables referenced by RULE_ID and RESOURCE_LIST_MEMBER_ID support rule-level reconciliation.

Together these relationships position PA_ALLOC_RUN_BASIS_DET as the linkage layer between allocation runs and the project/task structures they allocate across.