Results for “pa_cost_exceptions_det_v”

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

Overview

PA_COST_EXCEPTIONS_DET_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, defined within the Projects (PA) module. Its purpose is to identify the detailed Cost Distribution Lines (CDL) that block a project accounting period from being closed. When the Period Close process detects expenditures that cannot be transferred to Oracle General Ledger or processed by the costing engine, those exceptions must be surfaced with enough granularity for the cost accountant to resolve them. This view supplies that detail, exposing each offending distribution line alongside the associated project, task, expenditure, vendor, and person context.

The view is primarily a reporting and diagnostics object. It supports the Cost Exceptions inquiry in the Projects responsibility and is commonly consumed by custom reports, reconciliation routines, and integration extracts that need to reconcile unclosed periods. Because it is a view rather than a table, it presents data in real time, reflecting the current state of the underlying transaction and distribution tables.

Underlying Base Objects

The view is defined over PA_COST_EXCEPTIONS_SUM_V (itself a view) joined to four base objects plus two optional lookups. The metadata documents the following referenced objects: PA_COST_EXCEPTIONS_SUM_V, PA_PROJECTS_ALL, PA_TASKS, PA_EXPENDITURES_ALL, PO_VENDORS, and PER_PEOPLE_F. Package dependencies include HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY (via PER_PEOPLE_F), plus PA_EXCEPTION_REASONS_PUB and PA_PROJECT_UTILS, which support the exception-reason and project utility logic surfaced in the view.

• PA_COST_EXCEPTIONS_SUM_V (SMRY) — the driving summary view supplying exception rows, amounts, expenditure identity, and exception reason/corrective action.
• PA_PROJECTS_ALL (PRJ) — joined on PROJECT_ID to obtain PROJECT_NUMBER (SEGMENT1).
• PA_TASKS (TSK) — joined on TASK_ID and PROJECT_ID to obtain TASK_NUMBER.
• PA_EXPENDITURES_ALL (EXP) — outer join on EXPENDITURE_ID providing expenditure group, ending date, and incurred-by person.
• PO_VENDORS (VND) — outer join on VENDOR_ID supplying VENDOR_NUMBER and VENDOR_NAME (supplier/site identification).
• PER_PEOPLE_F (EMP) — outer join on person id supplying FULL_NAME.

The outer joins (+ syntax) ensure exception rows are retained even when vendor or person reference data is missing.

Key Columns

The projection exposes identifiers that tie an exception back to its source transaction, plus descriptive attributes useful for user-facing reporting.

• PROJECT_ID / PROJECT_NUMBER / TASK_ID / TASK_NUMBER — project and task identity for the failing distribution line.
• EXPENDITURE_ID / EXPENDITURE_ITEM_ID / EXPENDITURE_ITEM_DATE / EXPENDITURE_ENDING_DATE / EXPENDITURE_GROUP — the expenditure transaction and item context.
• INVOICE_ID / INVOICE_LINE_NUMBER / INVOICE_DISTRIBUTION_ID / DOCUMENT_PAYMENT_ID / DOCUMENT_TYPE / DOCUMENT_DISTRIBUTION_TYPE — Payables and document linkage for supplier invoice-driven costs.
• SI_ASSETS_ADDITION_FLAG — indicates a self-service assets addition relationship.
• EXPENDITURE_TYPE, SMRY.CDL_LINE_NUM, PA_DATE, PERIOD_NAME — cost distribution line number, accounting date, and period in which the exception occurs.
• QUANTITY, AMOUNT, DENOM_CURRENCY_CODE, DENOM_AMOUNT, PROJECT_AMOUNT, UNIT_OF_MEASURE — monetary and quantity measures of the distribution line.
• VENDOR_ID / VENDOR_NUMBER / VENDOR_NAME and PERSON_ID / PERSON_NAME — supplier and incurred-by person attribution.
• TRANSFER_STATUS_CODE, TRANSFER_REJECTION_REASON, EXCEPTION_REASON, CORRECTIVE_ACTION — the diagnostic heart of the view, explaining why the line blocks period close and how to correct it.

Common Use Cases and Queries

Cost accountants and period-close administrators query this view to list, quantify, and document open exceptions before running Period Close. A typical inquiry filters on PERIOD_NAME and EXCEPTION_REASON to produce an actionable exception log.

• List all blocking lines for a period: SELECT PROJECT_NUMBER, TASK_NUMBER, EXPENDITURE_ID, CDL_LINE_NUM, AMOUNT, EXCEPTION_REASON, CORRECTIVE_ACTION FROM PA_COST_EXCEPTIONS_DET_V WHERE PERIOD_NAME = :period_name;
• Aggregate exception exposure by project: SELECT PROJECT_NUMBER, SUM(AMOUNT) FROM PA_COST_EXCEPTIONS_DET_V WHERE PERIOD_NAME = :period_name GROUP BY PROJECT_NUMBER;
• Analyze rejection reasons: SELECT EXCEPTION_REASON, TRANSFER_REJECTION_REASON, COUNT(*) FROM PA_COST_EXCEPTIONS_DET_V WHERE PERIOD_NAME = :period_name GROUP BY EXCEPTION_REASON, TRANSFER_REJECTION_REASON;
• Vendor-driven exceptions: SELECT VENDOR_NUMBER, VENDOR_NAME, EXPENDITURE_ID, AMOUNT FROM PA_COST_EXCEPTIONS_DET_V WHERE VENDOR_ID IS NOT NULL AND PERIOD_NAME = :period_name;
• Export for reconciliation: join to PO_VENDORS or AP invoice tables via INVOICE_DISTRIBUTION_ID to align Payables and Projects records before correction.

Because all transactional data flows through the summary view and standard base tables, results remain consistent with what the costing engine and Period Close process evaluate at runtime, making the view a reliable single source for exception resolution reporting.