Search Results pa_utils2




Overview
Explore in AI Chat

Overview

PA_CDL_BURDEN_DETAIL_V_R is a user-customizable reporting view in the Oracle E-Business Suite Projects (PA) module. It exposes the summarization criteria used for burden summarization of expenditure items, providing the dimensional and descriptive attributes that drive how raw expenditure costs are aggregated and burdened during the cost distribution and burdening process.

The view is defined over the base view PA_CDL_BURDEN_DETAIL_V, which itself is a denormalized projection of cost distribution lines joined to expenditure items, compiled multipliers, and organization information. The "_R" suffix indicates that this is the customizable, "regular" variant — a copy that implementers may modify to add, remove, or rename columns without altering the seeded definition of the underlying view. This design pattern allows an installation to tailor the summarization grain (for example, adding descriptive flexfield attributes as grouping keys) while preserving upgrade-safe integrity of the standard object.

The view is typically consumed by the burden summarization concurrent programs and by diagnostic or reconciliation reports that examine how expenditure was grouped before burden cost was calculated and posted.

Underlying Base Objects

The view is documented as based on PA_CDL_BURDEN_DETAIL_V. In the SELECT text supplied in the metadata, the following physical objects are referenced:

The ETRM metadata records no separately documented base tables for this view, and it is noted as not implemented in the reference database — implying the view may exist in some environments and not others depending on patch level or customization.

Key Columns

The most significant column for users searching on "get_pa_period_name" is PA_PERIOD_NAME. It is derived using a DECODE: when PREV_IND_COMPILED_SET_ID is null, the CDL PA_PERIOD_NAME is used directly; otherwise the view calls PA_UTILS2.GET_PA_PERIOD_NAME(EI.EXPENDITURE_ITEM_DATE, EI.ORG_ID), falling back to CDL.PA_PERIOD_NAME when the function returns null. This ensures the summarization period reflects the expenditure item date for re-summarized records.

Common Use Cases and Queries

A frequent requirement is to determine the effective burden period for expenditure items, particularly when items have been re-summarized or adjusted. The following query shows the derived period alongside the expenditure item date:

  • SELECT project_id, task_id, expenditure_item_id, expenditure_item_date, pa_period_name, burden_cost FROM pa_cdl_burden_detail_v_r WHERE project_id = :project_id ORDER BY expenditure_item_date;
  • Reconciliation of summarized burden by organization and cost base: SELECT organization_id, ind_cost_code, cost_base, SUM(burden_cost) FROM pa_cdl_burden_detail_v_r GROUP BY organization_id, ind_cost_code, cost_base;
  • Customization extension: because this view is user-customizable, an implementer may add organization or DFF columns to meet local summarization requirements without modifying PA_CDL_BURDEN_DETAIL_V.

Because the period derivation depends on PA_UTILS2.GET_PA_PERIOD_NAME and the PREV_IND_COMPILED_SET_ID flag, any analysis of PA_PERIOD_NAME should account for whether the row originates from a prior compiled set, as this changes whether the item date or the stored period name governs.