Search Results alloc_exception_level

Overview

APPS.PA_ALLOC_EXCEPTIONS_V is a reporting view in Oracle E-Business Suite that exposes allocation exception records generated during the Project Accounting allocation process. Allocation runs distribute indirect or burden costs across projects and tasks; when the allocation engine cannot process a particular row, it writes an exception record to PA_ALLOC_EXCEPTIONS and associates it with the originating run. This view denormalizes those raw exception rows into a human-readable form by resolving lookup codes to their meanings, attaching project and task identifiers, and translating message codes into language-specific text via FND_MESSAGE.

The view is primarily consumed by allocation exception inquiry screens, concurrent program output, and diagnostic reports that help implementers determine why a given allocation run produced incomplete or rejected distributions. Its columns are stable and are commonly referenced in custom SQL against the PA schema.

Underlying Base Objects

The view definition joins five documented objects:

• PA_ALLOC_EXCEPTIONS (SYNONYM) — the driving table E; holds one row per exception with run_id, exception_type, level_code, project_id, task_id, and exception_code.
• PA_LOOKUPS (VIEW) — joined twice as L1 and L2. L1 resolves lookup_type = 'ALLOC_EXCEPTION_TYPE' against exception_type; L2 resolves lookup_type = 'ALLOC_EXCEPTION_LEVEL' against level_code. This is where the user's search term, exception_level, originates: it is the MEANING of the level_code lookup, exposed as the alias EXCEPTION_LEVEL.
• PA_PROJECTS_ALL (SYNONYM) — outer-joined on project_id to supply segment1 (project number) and name.
• PA_TASKS (SYNONYM) — outer-joined on task_id to supply task_number and task_name.
• FND_MESSAGE (PACKAGE) — invoked inline to return a translated string for exception_code, falling back to the raw code when no message exists.

Because both project and task joins are outer joins, exception rows that are not tied to a specific project or task (for example run-level failures) are still returned.

Key Columns

• RUN_ID — identifier of the allocation run that produced the exception.
• EXCEPTION_TYPE / EXCEPTION_TYPE (MEANING) — coded value and its decoded description from PA_LOOKUPS.
• LEVEL_CODE / EXCEPTION_LEVEL — the level at which the exception occurred, and its decoded meaning from lookup type 'ALLOC_EXCEPTION_LEVEL'.
• PROJECT_ID, PROJECT, NAME — project identifier, project number (segment1), and project name.
• TASK_ID, TASK, TASK_NAME — task identifier, task number, and description.
• EXCEPTION_CODE — the resolved FND message text, or the raw code if no message is registered.

Common Use Cases and Queries

Typical usage is post-run troubleshooting. The following query lists all exceptions for a single allocation run, decoded and ordered by level:

• SELECT run_id, exception_type, exception_level, project, name, task, exception_code FROM apps.pa_alloc_exceptions_v WHERE run_id = :run_id ORDER BY exception_level, project, task;

To find which levels and types recur most often across recent runs:

• SELECT exception_level, exception_type, COUNT(*) FROM apps.pa_alloc_exceptions_v GROUP BY exception_level, exception_type ORDER BY 3 DESC;

To isolate project-specific errors before drilling into tasks:

• SELECT project, name, task, task_name, exception_code FROM apps.pa_alloc_exceptions_v WHERE project_id = :project_id;

Because the view performs lookup and outer-join expansion on every access, filtering on RUN_ID or PROJECT_ID is recommended for performance on large exception tables.