Search Results burden_cost




Overview
Explore in AI Chat

Overview

PA_PROJ_COST_SL_REP_MRC_V is a reporting view within the Oracle Projects (PA) module that presents project cost transactions, including manufacturing-related costs, resolved down to the General Ledger account level. The view is part of the Multi-Report Currency (MRC) family of PA objects, which in Oracle EBS 12.1.1 and 12.2.2 supports reporting in multiple currencies and subledger-to-GL reconciliation. Its primary role is to expose cost distribution information for project expenditure items together with the accounting flexfield description, burdened and raw cost amounts, and the associated project, task, and organization context.

Because the view surfaces both raw cost and burden cost as discrete columns, it is frequently consulted by users searching for "burden_cost" — that is, implementers and analysts who need to report the burdened portion of a project transaction, the difference between burdened and raw cost as posted to a particular GL code combination. This makes the view relevant for burden analysis, cost auditing, and downstream integration extracts.

Underlying Base Objects

The documented base objects referenced by this view are:

The view joins these objects on expenditure item, expenditure type, code combination, task, project, and system linkage function. The cost distribution lines are further filtered so that TRANSFER_STATUS_CODE is 'A' or 'V', ensuring only accepted or valid distributions are returned. No additional base objects are documented beyond this set.

Key Columns

Common Use Cases and Queries

Typical scenarios include burden analysis, reconciliation of project costs to GL, and extracts feeding a data warehouse. A representative query returning burdened project costs follows:

SELECT PROJECT_NUMBER,
       TASK_NUMBER,
       EXPENDITURE_TYPE,
       GL_DATE,
       RAW_COST,
       BURDEN_COST,
       TOTAL_COST,
       ACCOUNT_DESCRIPTION
FROM   PA_PROJ_COST_SL_REP_MRC_V
WHERE  BURDEN_COST <> 0
  AND  GL_DATE BETWEEN :start_date AND :end_date
ORDER BY PROJECT_NUMBER, GL_DATE;

Because the view is documented as "Not implemented in this database" in the provided ETRM metadata, environments must confirm its existence before relying on it in concurrent programs or BI Publisher reports.