Results for “rejection_reason”

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

Overview

PA_ALLOC_EXCEPTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Projects (PA) product family. It exposes the contents of the PA_ALLOC_EXCEPTIONS table joined to lookup, project, task, and message data, presenting a fully described, user-facing representation of allocation exceptions raised during the project cost allocation process. Allocation in Oracle Projects distributes indirect and burden costs across projects and tasks; when a run cannot distribute a given amount, an exception row is written and the view makes that row readable.

Because raw exception records store only coded values, the view resolves those codes through PA_LOOKUPS and FND_MESSAGE so that exception type, exception level, and rejection reason appear as meaningful text. The view is therefore the standard access point for reports, concurrent program output, and integration extracts that need allocation-failure detail without re-implementing the lookup resolution logic. It is valid and available in both 12.1.1 and 12.2.2.

Underlying Base Objects

The documented base objects referenced by the view are:

• PA_ALLOC_EXCEPTIONS (synonym) — the driving table holding one row per exception raised by an allocation run, keyed by RUN_ID and carrying EXCEPTION_TYPE, LEVEL_CODE, PROJECT_ID, TASK_ID, EXCEPTION_CODE, and REJECTION_CODE.
• PA_LOOKUPS (view) — joined twice, aliased L1 and L2, to translate EXCEPTION_TYPE via lookup type ALLOC_EXCEPTION_TYPE and LEVEL_CODE via lookup type ALLOC_EXCEPTION_LEVEL.
• PA_PROJECTS_ALL (synonym) — outer-joined on PROJECT_ID to supply PROJECT_NUMBER (SEGMENT1) and PROJECT_NAME.
• PA_TASKS (synonym) — outer-joined on TASK_ID to supply TASK_NUMBER and TASK_NAME.
• FND_MESSAGE (package) — invoked per row through FND_MESSAGE.GET_STRING to convert EXCEPTION_CODE into a localized message, falling back to the code itself when no message is defined.

The outer joins to projects and tasks are significant: exceptions can be raised at a run or project level without a specific task, so the view preserves such rows while leaving project and task columns null.

Key Columns

• RUN_ID — identifier of the allocation run that produced the exception.
• EXCEPTION_TYPE / EXCEPTION_MEANING — the coded exception category and its ALLOC_EXCEPTION_TYPE lookup meaning.
• LEVEL_CODE / LEVEL_MEANING — the level at which the exception occurred (the EXCEPTION_LEVEL lookup meaning); this is the column most relevant to searches for "exception_level", reported here as LEVEL_MEANING.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — project context of the exception, null when not project-specific.
• TASK_ID, TASK_NUMBER, TASK_NAME — task context, null when the exception is not task-specific.
• REJECTION_CODE / REJECTION_REASON — the resolved failure reason, derived from EXCEPTION_CODE through FND_MESSAGE.GET_STRING.

Common Use Cases and Queries

Typical uses include diagnosing why a cost allocation run failed to distribute amounts, feeding exception dashboards, and extracting failure detail for reconciliation. A representative query groups exceptions by run and level:

• SELECT RUN_ID, EXCEPTION_TYPE, LEVEL_MEANING, COUNT(*) FROM PA_ALLOC_EXCEPTIONS_V GROUP BY RUN_ID, EXCEPTION_TYPE, LEVEL_MEANING ORDER BY RUN_ID;
• SELECT PROJECT_NUMBER, TASK_NUMBER, REJECTION_REASON FROM PA_ALLOC_EXCEPTIONS_V WHERE RUN_ID = :run_id;
• SELECT * FROM PA_ALLOC_EXCEPTIONS_V WHERE LEVEL_CODE = 'PROJECT';

Reports that must filter or group by exception level should reference LEVEL_CODE for the code and LEVEL_MEANING for display text.