Results for “burden_amt_display_method”

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

Overview

PA_CAPITAL_PROJECTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the Projects (PA) product family. It presents a consolidated, per-project summary of capital-related cost components: expensed costs, construction-in-process (CIP) costs, capitalizable costs, capitalized costs, and total project costs. The view targets capital projects specifically, meaning projects configured to accumulate costs that are subsequently interfaced to Oracle Assets.

The documentation designates this object as "R10SC Only," indicating it originates from an earlier release-specific construct and remains valid in 12.1.1 and 12.2.2. Because it aggregates cost buckets and applies Projects security functions, the view functions primarily as a reporting and inquiry layer rather than as a transactional object. It is typically consumed by custom reports, Discoverer workbooks, OBIEE/BI Publisher data models, and ad hoc SQL used by capital project accountants and fixed asset teams. Users searching on the term "cip_cost" are directed here because CIP_COST is one of the view's headline calculated columns, representing costs that are capitalizable but not yet capitalized.

Underlying Base Objects

The view is defined over PA_CAPITAL_PROJECTS_BASE_V, joined to PA_PROJECTS (accessed through a synonym) and PA_PROJECT_STATUSES. The base view supplies the cost measures (CAPITALIZED_COST, CAPITALIZABLE_COST, and TOTAL_COSTS) plus capital-processing attributes; PA_PROJECTS supplies project header attributes and ORG_ID; PA_PROJECT_STATUSES supplies status filtering. The documented referenced objects also include the packages PA_MC_CURRENCY_PKG, PA_SECURITY, HR_GENERAL, and HR_SECURITY.

• PA_CAPITAL_PROJECTS_BASE_V — the driving view providing cost rollups and capital configuration columns.
• PA_PROJECTS / PA_PROJECT_STATUSES — project master and status records; the query excludes projects whose system status is "PURGED."
• PA_SECURITY — ALLOW_QUERY restricts rows to projects the user may access; ALLOW_UPDATE and VIEW_LABOR_COSTS expose function-security results as single-character columns.
• PA_MC_CURRENCY_PKG — GET_MRC_SOB_TYPE_CODE governs whether cost measures are populated, returning NULL when the reporting set of books is of type "R."
• HR_GENERAL / HR_SECURITY — HR security utilities referenced by the Projects security stack.

The definition uses an aggregate with GROUP BY over the base view's project-level attributes, then a UNION ALL, indicating a second branch covering reporting-period or additional cost detail.

Key Columns

• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER — primary project identifiers.
• PROJECT_STATUS_CODE, PROJECT_TYPE, PROJECT_ORGANIZATION — classification and owning organization.
• CAPITALIZED_COST — costs already processed through the capital event and transferred to Oracle Assets.
• CAPITALIZABLE_COST — costs eligible for capitalization.
• TOTAL_COSTS — aggregate of all cost components for the project.
• EXPENSED — computed as TOTAL_COSTS minus CAPITALIZABLE_COST, i.e., costs written off rather than capitalized.
• CIP_COST — computed as CAPITALIZABLE_COST minus CAPITALIZED_COST; the residual construction-in-process balance not yet capitalized. This is the column of primary interest to users searching "cip_cost."
• ASSET_ALLOCATION_METHOD, CAPITAL_EVENT_PROCESSING, CAPITAL_COST_TYPE_CODE — capital processing configuration.
• INTERFACE_COMPLETE_ASSET_FLAG, INTERFACE_ASSET_COST_CODE — asset interface state.
• BURDEN_AMT_DISPLAY_METHOD, TOTAL_BURDEN_FLAG — burden presentation controls.
• ORG_ID — operating unit identifier for multi-org filtering.
• ALLOW_UPDATE, VIEW_LABOR_COSTS — Projects security results.

Common Use Cases and Queries

Typical scenarios include reconciling CIP balances before running capital event processing, auditing capitalization progress across a portfolio, and identifying projects where capitalizable cost exceeds capitalized cost. Because the view enforces ALLOW_QUERY, results are automatically restricted to projects visible to the querying user.

SELECT project_number,
       project_name,
       capitalized_cost,
       capitalizable_cost,
       cip_cost,
       expensed,
       total_costs
FROM   apps.pa_capital_projects_v
WHERE  org_id = :p_org_id
  AND  cip_cost > 0
  AND  project_status_code = 'APPROVED'
ORDER BY cip_cost DESC;

A second pattern monitors capitalization readiness by comparing CIP against the interface flag:

SELECT project_id,
       project_number,
       cip_cost,
       interface_complete_asset_flag
FROM   apps.pa_capital_projects_v
WHERE  capital_event_processing = 'Y'
  AND  NVL(interface_complete_asset_flag,'N') = 'N';

Because cost measures depend on PA_MC_CURRENCY_PKG, queries executed under a reporting set of books of type "R" will return NULL for the cost columns; callers should therefore restrict the query to the relevant ledger context. All access should be performed through the APPS schema or a synonym with appropriate grants.