Results for “pa_alloc_source_lines”

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

Overview

PA_ALLOC_SOURCE_LINES is a Projects (PA) module table that stores the source lines associated with each allocation rule in Oracle E-Business Suite. Allocation rules in PA define how costs, revenue, or other amounts are distributed across projects, tasks, and expenditure categories. Each rule may draw from multiple source definitions, and PA_ALLOC_SOURCE_LINES captures the individual source line criteria that determine which transactions or balances participate in the allocation. The table resides in the PA schema and is marked VALID across Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table hangs off the PA_ALLOC_RULES_ALL hub via RULE_ID and carries descriptive criteria such as flags, category codes, and type attributes. Its grain is one row per source line per allocation rule, making it a dependent descriptive object rather than an independent business entity.

Key Information Stored

The table contains 16 documented columns. The most significant are described below.

• RULE_ID — Foreign key to PA_ALLOC_RULES_ALL identifying the parent allocation rule. Part of the primary key.
• LINE_NUM — Sequence number distinguishing each source line within a rule. Part of the primary key and the primary ordering attribute.
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL, restricting the source to a specific project when populated.
• TASK_ID — Foreign key to PA_TASKS, narrowing the source to a specific task.
• PROJECT_ORG_ID — Organization context for the source project.
• TASK_ORG_ID — Organization context for the source task.
• PROJECT_TYPE — Project type qualifier used in the source selection.
• CLASS_CATEGORY — Class category used to filter eligible projects or tasks.
• CLASS_CODE — Class code paired with CLASS_CATEGORY for source filtering.
• SERVICE_TYPE — Service type indicator for the source definition.
• EXCLUDE_FLAG — Indicates whether the identified source line is included or excluded from the allocation.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard EBS audit tracking.

The surrogate primary key is PA_ALLOC_SOURCE_PK, composed of RULE_ID and LINE_NUM. A unique index, PA_ALLOC_SOURCE_LINES_U1, enforces the same business-key combination (RULE_ID, LINE_NUM).

Common Use Cases and Queries

Typical usage centers on inspecting, auditing, and reporting allocation rule definitions before and after allocation runs.

• Listing all source lines for a given rule: SELECT line_num, project_id, task_id, class_category, class_code FROM pa.pa_alloc_source_lines WHERE rule_id = :p_rule_id ORDER BY line_num;
• Identifying project- or task-specific sources by joining to PA_PROJECTS_ALL and PA_TASKS to resolve names.
• Auditing changes to allocation definitions by filtering on LAST_UPDATE_DATE.
• Reporting exclusion logic by examining EXCLUDE_FLAG across rules.

These queries support period-end allocation review, configuration documentation, and troubleshooting mismatched or unexpected allocation results.

Related Objects

• PA_ALLOC_RULES_ALL — Parent rule table; joined on RULE_ID.
• PA_PROJECTS_ALL — Referenced via PROJECT_ID to resolve source project details.
• PA_TASKS — Referenced via TASK_ID to resolve source task details.
• PA_ALLOC_RUN_SOURCES — Child table keyed on RULE_ID and LINE_NUM, capturing source data for allocation runs.

Together these objects define, execute, and trace allocation logic within the Projects module.