Search Results icc_expenditure_type




Overview
Explore in AI Chat

Overview

APPS.PA_CMT_BURDEN_SUMMARY_V is an Oracle E-Business Suite (EBS) reporting view that presents summarized cross-charge burden costing information generated by the Oracle Project Costing burden engine. The name incorporates the "CMT" prefix, denoting the Costing Management Transaction (CMT) infrastructure introduced to support multi-source, multi-destination burden processing. The view consolidates burden summary rows in which a single source transaction (a raw cost distribution on the sending organization) is paired with a corresponding destination distribution (the receiver of the cross-charged burden), exposing both perspectives side by side in one row.

The view is primarily consumed by burden costing reports, cross-charge reconciliation queries, intercompany burden analysis, and integration extracts that must relate the originating expenditure to its burdened counterpart. It serves as a stable, denormalized interface over the more granular PA_CMT_BURDEN_DETAIL_V, allowing report writers to avoid joining the detail view twice (once for the source side and once for the destination side).

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over the following referenced objects:

  • PA_CMT_BURDEN_DETAIL_V (VIEW) — the primary source of data. PA_CMT_BURDEN_SUMMARY_V projects and re-labels columns from this detail view, aliasing each as either a source_* or dest_* attribute.
  • PA_BURDEN_COSTING (PACKAGE) — the PL/SQL package that performs burden compilation and summary run processing. It populates the underlying burden costing tables that flow into the detail view, and provides the run identifiers referenced by burden_sum_source_run_id.
  • PA_CLIENT_EXTN_BURDEN_RESOURCE (PACKAGE) — the client extension hook used to derive burden resource information (for example, labor or equipment resource identifiers) during burden costing, which is reflected in columns such as bom_labor_resource_id and bom_equipment_resource_id.

Key Columns

The column list is organized around paired source and destination attribute sets, followed by amounts, currencies, and resource keys.

  • Source side: source_project_id, source_task_id, source_org_id, source_pa_period, source_gl_period, source_txn_source, source_line_type, source_ind_cost_code, source_expenditure_type, source_ind_expenditure_type, source_exp_category, source_revenue_category, source_cost_base, source_compiled_multiplier, source_ind_rate_sch_id, source_ind_rate_sch_rev_id, source_burden_cost, and source_burden_sum_rej_code. Notably, cmt_expenditure_type is exposed as source_expenditure_type, while icc_expenditure_type is exposed as source_ind_expenditure_type — the "ind" prefix denoting the indirect/cross-charge expenditure type.
  • Destination side: dest_project_id, dest_task_id, dest_org_id, dest_ind_exp_type (mapped from icc_expenditure_type), dest_txn_ref1, dest_pa_period, dest_gl_period, dest_txn_source, dest_exp_category, dest_revenue_category, dest_line_type, and dest_ind_cost_code.
  • Amounts and currency: acct_raw_cost, acct_burdened_cost, denom_raw_cost, denom_burdened_cost, acct_currency_code, denom_currency_code, acct_rate_date, acct_rate_type, acct_exchange_rate, project_currency_code, project_rate_date, project_rate_type, and project_exchange_rate.
  • Resource references: vendor_id, inventory_item_id, bom_labor_resource_id, bom_equipment_resource_id, resource_class, and source_system_linkage_function.

Common Use Cases and Queries

A frequent requirement is to retrieve all burden rows associated with a specific indirect (ICC) expenditure type, which is exactly the term the user searched. Because the view exposes that attribute on both the source and destination sides, filters must specify which perspective is intended.

  • By source ICC expenditure type: SELECT source_project_id, source_task_id, source_ind_expenditure_type, source_burden_cost FROM apps.pa_cmt_burden_summary_v WHERE source_ind_expenditure_type = :icc_expenditure_type;
  • By destination ICC expenditure type: SELECT dest_project_id, dest_task_id, dest_ind_exp_type, acct_burdened_cost FROM apps.pa_cmt_burden_summary_v WHERE dest_ind_exp_type = :icc_expenditure_type;
  • Cross-charge reconciliation: join source and destination projects to compare raw versus burdened amounts across organizations using source_org_id, dest_org_id, and burden_sum_source_run_id to isolate a specific burden summary run.
  • Rejection analysis: filter on source_burden_sum_rej_code IS NOT NULL to identify summary rows rejected by the burden engine and investigate the originating compilation run.

Because the view is keyed on a concatenated descriptor combining currency, project, task, organization, period, transaction source, line type, indirect cost code, resource class, and linkage function, it is well suited to grouping and aggregation within burden reporting extracts.