Results for “pa_alloc_exceptions”

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

Overview

PA_ALLOC_EXCEPTIONS is a Projects (PA) module table that stores exception records generated during an allocation run in Oracle EBS 12.1.1 and 12.2.2. When the allocation engine executes a rule set against one or more projects and tasks, conditions that prevent a cost line from being allocated successfully — or that warrant operator attention — are written to this table. Each row therefore represents a discrete diagnostic event tied to a specific run, rule, project, and task combination, providing the audit trail that allocation administrators use to reconcile why certain amounts were not distributed as expected.

Under the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link. It does not hold descriptive master data of its own; instead it resolves relationships between PA_ALLOC_RUNS_ALL, PA_PROJECTS_ALL, PA_TASKS, and PA_ALLOC_RULES_ALL, with the exception attributes acting as link-level descriptors. Any warehouse design should preserve RUN_ID, RULE_ID, PROJECT_ID, and TASK_ID as the composite reference path.

Key Information Stored

The documented physical schema in ETRM 12.2.2 lists twelve columns under the PA schema. The most significant are:

• RUN_ID — Foreign key to PA_ALLOC_RUNS_ALL; identifies the allocation run that produced the exception.
• RULE_ID — Foreign key to PA_ALLOC_RULES_ALL; identifies the allocation rule being processed when the exception occurred.
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL; the project against which the run was executed.
• TASK_ID — Foreign key to PA_TASKS; the task within the project.
• LEVEL_CODE — Indicates the allocation level (project, task, or top task) at which the exception was raised.
• EXCEPTION_TYPE — Categorizes the nature of the exception.
• EXCEPTION_CODE — The specific code identifying the exception condition.
• CREATION_DATE, CREATED_BY — Standard audit columns capturing when and by whom the record was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns maintained by the application.

The metadata documents four foreign keys but does not publish a surrogate primary key or unique index. In practice the natural or business key candidates are the combination of RUN_ID, RULE_ID, PROJECT_ID, TASK_ID, LEVEL_CODE, and EXCEPTION_CODE, which uniquely identify a single exception within a run. The absence of a documented single-column primary key reinforces the link classification: this table's identity is derived from the entities it connects rather than from an independent surrogate.

Common Use Cases and Queries

The primary operational use case is troubleshooting failed or partially completed allocation runs. Administrators join PA_ALLOC_EXCEPTIONS to PA_ALLOC_RUNS_ALL to obtain run dates and statuses, and to PA_PROJECTS_ALL for project names. A typical diagnostic query returns all exceptions for a given run:

• SELECT e.RUN_ID, e.RULE_ID, e.PROJECT_ID, e.TASK_ID, e.EXCEPTION_TYPE, e.EXCEPTION_CODE FROM PA_ALLOC_EXCEPTIONS e WHERE e.RUN_ID = :run_id;
• Reporting usage: aggregating exception counts by EXCEPTION_TYPE and EXCEPTION_CODE across a date range to identify systemic configuration problems.
• Joining to PA_ALLOC_RULES_ALL to determine which allocation rules most frequently generate exceptions.
• Joining to PA_PROJECTS_ALL and PA_TASKS to produce a per-project exception register for project accounting review.

Because allocation exceptions can block period-close activities, many implementations build a concurrent program or BI Publisher report that surfaces unresolved exceptions by run and period.

Related Objects

• PA_ALLOC_RUNS_ALL — joined on RUN_ID; parent run header.
• PA_ALLOC_RULES_ALL — joined on RULE_ID; rule definition driving the allocation.
• PA_PROJECTS_ALL — joined on PROJECT_ID; project master.
• PA_TASKS — joined on TASK_ID; task master within the project.
• PA_ALLOC_RUN_DETAILS — typically the sibling detail table for allocation results, useful for cross-referencing the exception against the attempted allocation.

Together these objects form the allocation audit substrate, with PA_ALLOC_EXCEPTIONS serving as the exception-resolution layer between run headers and project/task structures.