Results for “wip_resource_id”

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

Overview

PA_CDL_BURDEN_DETAIL_V is an Oracle EBS Projects (PA) view owned by the APPS schema, classified as a user-customizable view in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the summarization criteria used by the burden summarization process for expenditure items in Oracle Project Costing. The view presents the detail-level rows that feed the burden summarization engine, combining expenditure item attributes with compiled multiplier information to produce burdened cost amounts across multiple cost bases (raw, denominated, accounting, and project).

Because it is defined as a user-customizable view, functional users can modify the set of columns selected for summarization, adjusting the grouping grain applied when burden costs are aggregated. This makes the view a critical control point for organizations that need to tailor how burden costs roll up to summary tables such as PA_BURDEN_SUM_DETAILS. It serves as both a reporting surface for burden details and an integration point for downstream processes that consume burdened expenditure information.

Underlying Base Objects

The view is defined over two primary sources in its SELECT statement: the global temporary / staging structure PA_EI_CDL_CM_GTEMP (aliased GTEMP) and the PA_COMPILED_MULTIPLIERS table (aliased CM). The join is performed on IND_COMPILED_SET_ID and COST_BASE, with a filter requiring COMPILED_MULTIPLIER <> 0, ensuring only active multiplier combinations are returned.

The documented referenced base objects also include PA_IND_COST_CODES, PA_BURDEN_COSTING (package), PA_CURRENCY (package), and GMS_AWARD_DISTRIBUTIONS. The dependent view PA_CDL_BURDEN_DETAIL_V serves as the foundation upon which the customizable summary view logic is applied. The scalar subquery against PA_IND_COST_CODES resolves the expenditure type associated with the indirect cost code carried on the multiplier row.

Key Columns

• PROJECT_ID, TASK_ID, EXPENDITURE_ITEM_ID, LINE_NUM — Core identifiers linking the burden detail back to the originating project, task, and expenditure item.
• ORGANIZATION_ID, EXPENDITURE_ITEM_DATE, PA_DATE, PA_PERIOD_NAME — Organizational and date/period context used for summarization boundaries.
• COST_BASE, COMPILED_MULTIPLIER, IND_COMPILED_SET_ID, IND_COST_CODE — The burden multiplier definition and the indirect cost code applied.
• BURDEN_COST, DENOM_BURDENED_COST, ACCT_BURDENED_COST, PROJECT_BURDENED_COST — The four burdened cost amounts, each computed as the corresponding CDL raw cost multiplied by COMPILED_MULTIPLIER.
• DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE — Currency context for each cost basis.
• ATTRIBUTE1–ATTRIBUTE10, ATTRIBUTE_CATEGORY — Descriptive flexfield columns exposed for user customization of summarization grain.
• BURDEN_SUM_SOURCE_RUN_ID, BURDEN_SUM_REJECTION_CODE — Summarization run traceability and rejection handling.
• BILLABLE_FLAG, PERSON_TYPE, SYSTEM_LINKAGE_FUNCTION — Additional classification attributes for reporting and filtering.

Common Use Cases and Queries

A typical use case is auditing burdened cost components for a given expenditure item or project before summarization, verifying that the compiled multiplier is applied correctly across all four cost bases. Another is reconciliation between detail burden rows and the summarized burden tables produced by the Burden Summarization process. Because the view is customizable, users frequently query it to confirm the current summarization column set.

Sample query to inspect burdened cost detail for a project:

• SELECT PROJECT_ID, TASK_ID, EXPENDITURE_ITEM_ID, COST_BASE, COMPILED_MULTIPLIER, PROJECT_BURDENED_COST, ACCT_BURDENED_COST FROM PA_CDL_BURDEN_DETAIL_V WHERE PROJECT_ID = :p_project_id AND EXPENDITURE_ITEM_DATE BETWEEN :p_start AND :p_end;
• SELECT BURDEN_SUM_SOURCE_RUN_ID, BURDEN_SUM_REJECTION_CODE, COUNT(*) FROM PA_CDL_BURDEN_DETAIL_V GROUP BY BURDEN_SUM_SOURCE_RUN_ID, BURDEN_SUM_REJECTION_CODE;

These queries support validation of burden summarization outcomes and identification of rejected or unprocessed burden detail rows.