Results for “pa_alloc_run_targets”

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

Overview

PA_ALLOC_RUN_TARGETS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the target projects and tasks associated with each target line of an allocation run. Allocation in Oracle Projects distributes amounts from source projects and tasks across defined target projects and tasks, and this table captures the per-run, per-target-line resolution of that distribution. Each row effectively pairs an allocation run with a specific rule, target line, and the project/task that receives allocated amounts, optionally including a budget version, an exclusion indicator, and a percentage.

Because the table stores the association between allocation runs (via RUN_ID) and target line definitions (via RULE_ID and LINE_NUM), the heuristic Data Vault classification supplied in the metadata is link. This is a modeling suggestion only: the table behaves as a transactional link resolving many-to-many relationships between runs and target lines, while also carrying descriptive and control attributes (percentages, flags, audit columns) that resemble satellite or contextual payload on that link.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• RUN_ID — Identifies the allocation run instance to which the target record belongs; the primary grouping key for reporting.
• RULE_ID — Foreign key to PA_ALLOC_TARGET_LINES; identifies the allocation rule/target line definition.
• LINE_NUM — Together with RULE_ID, forms the composite foreign key to PA_ALLOC_TARGET_LINES, referencing a specific target line.
• PROJECT_ID — The target project to which amounts are allocated for this run and line.
• TASK_ID — The target task within the project, where task-level allocation is used.
• LINE_PERCENT — The percentage of the source amount assigned to this target line, enabling weighted distribution.
• EXCLUDE_FLAG — Indicates whether the target line is excluded from the allocation run.
• BUDGET_VERSION_ID — Foreign key to PA_BUDGET_VERSIONS; identifies the budget version associated with the target, relevant for budgetary allocation scenarios.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO audit columns.

The surrogate identity of a row is not exposed as a single documented sequence column; the functional/business key candidates are the combination of RUN_ID, RULE_ID, and LINE_NUM. Note that the metadata lists RULE_ID and LINE_NUM together as the foreign key into PA_ALLOC_TARGET_LINES, indicating the composite nature of that reference.

Common Use Cases and Queries

Typical usage centers on auditing and reporting which projects and tasks received allocations for a given run, and on reconstructing the allocation rule targets for a run after the fact.

• Listing all targets for a specific run:

SELECT run_id, rule_id, line_num, project_id, task_id,
       line_percent, exclude_flag, budget_version_id
FROM   pa.pa_alloc_run_targets
WHERE  run_id = :run_id
ORDER BY rule_id, line_num;

• Joining to the target line definition to retrieve rule details:

SELECT t.run_id, t.rule_id, t.line_num, t.project_id, t.task_id,
       t.line_percent, l.rule_name
FROM   pa.pa_alloc_run_targets t,
       pa.pa_alloc_target_lines l
WHERE  t.rule_id  = l.rule_id
AND    t.line_num = l.line_num
AND    t.run_id   = :run_id;

• Filtering active targets only using EXCLUDE_FLAG, and reconciling percentages per run to confirm they sum appropriately.
• Reporting by budget version by joining BUDGET_VERSION_ID to PA_BUDGET_VERSIONS for budget-specific allocation analysis.

Related Objects

• PA_ALLOC_TARGET_LINES — Referenced by PA_ALLOC_RUN_TARGETS.RULE_ID and .LINE_NUM; defines the target line master from which run-level targets are instantiated.
• PA_BUDGET_VERSIONS — Referenced by PA_ALLOC_RUN_TARGETS.BUDGET_VERSION_ID; supplies budget version context for allocation targets.
• PA_ALLOC_RUNS / allocation run tables — Provide the run header context for RUN_ID and drive the allocation process that populates this table.
• PA_PROJECTS_ALL / PA_TASKS — Resolve PROJECT_ID and TASK_ID to project and task names for reporting.
• Oracle Projects Allocation APIs — The allocation execution process that creates and consumes PA_ALLOC_RUN_TARGETS rows.
• PA_ALLOCATION_RULE_DEFINITIONS and related rule tables — Define the source and target rules that this table's records ultimately trace back to.

Together these objects form the allocation reporting and audit chain: run headers, target line definitions, target projects and tasks, budget versions, and the resolved run-level targets held in PA_ALLOC_RUN_TARGETS.