Results for “pa_alloc_target_lines_v”

28 results




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

Overview

PA_ALLOC_TARGET_LINES_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the target-side allocation lines that define how a burden or cost allocation rule distributes amounts across receiving projects, tasks, and organizations. Allocation rules in Oracle Projects consist of source lines, which identify the costs to be allocated, and target lines, which identify the recipients and the percentage each receives. This view exposes the target side in a denormalized, user-readable form suitable for reporting, concurrent processing, and integration.

The view joins the base allocation target table to HR organization units and their translations, to PA_PROJECTS_ALL, PA_TASKS, and the PA_LOOKUPS view for the SERVICE_TYPE lookup. Because it resolves organization and task names and project numbers, it is far more convenient than querying PA_ALLOC_TARGET_LINES directly. The user's search term, BILLABLE_ONLY_FLAG, is one of the columns surfaced by this view and controls whether only billable source transactions are included when the allocation rule executes.

Underlying Base Objects

The documented base objects are PA_ALLOC_TARGET_LINES (SYNONYM), PA_PROJECTS_ALL (SYNONYM), PA_TASKS (SYNONYM), PA_LOOKUPS (VIEW), HR_ORG_UNITS_NO_JOIN (VIEW), and HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM), with references to the HR_GENERAL and HR_SECURITY packages.

  • PA_ALLOC_TARGET_LINES is the driving table; every row in the view corresponds to one target line.
  • PA_PROJECTS_ALL supplies PROJECT_NUMBER (SEGMENT1) and PROJECT_NAME.
  • PA_TASKS supplies TASK_NUMBER and TASK_NAME for the receiving task.
  • PA_LOOKUPS resolves SERVICE_TYPE to its meaning via LOOKUP_TYPE = 'SERVICE TYPE'.
  • HR_ORG_UNITS_NO_JOIN and HR_ALL_ORGANIZATION_UNITS_TL supply the project and task organization names, with language resolved through USERENV('LANG').

All joins to the HR, project, task, and lookup objects are outer joins (+), so target lines are retained even when the referenced project, task, or organization cannot be resolved.

Key Columns

Common Use Cases and Queries

Typical uses include auditing allocation rule setup, verifying that target percentages total 100 percent per rule, and reporting which targets are flagged billable-only. The following query lists all target lines for a given rule:

  • SELECT rule_id, line_num, project_number, project_name, task_number, task_name, line_percent, billable_only_flag, exclude_flag FROM pa_alloc_target_lines_v WHERE rule_id = :p_rule_id ORDER BY line_num;

To isolate billable-only targets:

  • SELECT rule_id, line_num, project_number, task_number, line_percent FROM pa_alloc_target_lines_v WHERE billable_only_flag = 'Y';

A validation query to confirm each rule's target percentages sum correctly:

  • SELECT rule_id, SUM(line_percent) FROM pa_alloc_target_lines_v WHERE NVL(exclude_flag,'N') = 'N' GROUP BY rule_id HAVING SUM(line_percent) <> 100;

Because the view preserves outer joins, it is safe for diagnostic reports that must display incomplete or orphaned target definitions.