Search Results actual_outside_processing




Overview
Explore in AI Chat

Overview

APPS.PJM_PROJECT_COST_HISTORY_V is a project-facing cost history view in Oracle E-Business Suite, delivered as part of the Projects (PJM) schema but sourced from Cost Management (CST) cost group history data. Its purpose is to expose transaction-level cost history — prior, actual, and new cost components — in a form suitable for project cost reporting, cost analysis, and integration with project accounting inquiries. The view resolves currency precision and set-of-books context so that dollar amounts are rounded consistently for presentation.

The user query "cst_cg_cost_history_v" reflects the more commonly known underlying Cost Management view, CST_CG_COST_HISTORY_V. PJM_PROJECT_COST_HISTORY_V is effectively a project-oriented presentation layer built on top of that cost group cost history view, joining currency and organization information to enrich the base costing rows. In Oracle EBS 12.1.1 and 12.2.2 this view is used primarily for read-only reporting; it is not a transactional (insert/update) object.

Underlying Base Objects

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

  • CST_CG_COST_HISTORY_V (VIEW) — The primary source, supplying inventory item, transaction, organization, layer, quantity, and the prior/actual/new cost component columns.
  • FND_CURRENCIES (SYNONYM) — Provides currency precision attributes (PRECISION and EXTENDED_PRECISION) used in the ROUND expressions applied to every monetary column.
  • GL_SETS_OF_BOOKS (VIEW) — Supplies the ledger/set-of-books context used to determine the reporting currency for rounding.
  • HR_ORGANIZATION_INFORMATION (SYNONYM) — Supplies organization-level attributes, typically the inventory organization and its classification, used to associate cost history with the correct organization.

The SELECT aliases the base view as CCCHV and the currency source as CURR, confirming that CST_CG_COST_HISTORY_V is passed through with currency-driven rounding applied to each amount column.

Key Columns

The view exposes the full set of cost group cost history columns, including:

The ROUND( ..., NVL(CURR.EXTENDED_PRECISION, NVL(CURR.PRECISION, 0)) ) pattern ensures amounts respect the currency definition, defaulting to zero decimal places if no precision is defined.

Common Use Cases and Queries

Typical uses include project cost variance analysis, reconciliation of prior versus new costed values, and drilling into transaction-level cost history by item and organization. A representative query:

  • SELECT inventory_item_id, organization_id, transaction_id, transaction_date, prior_cost, actual_cost, new_cost FROM apps.pjm_project_cost_history_v WHERE organization_id = :org_id AND inventory_item_id = :item_id ORDER BY transaction_date;
  • SELECT cost_group_id, SUM(actual_cost), SUM(new_cost) FROM apps.pjm_project_cost_history_v WHERE transaction_costed_date BETWEEN :from_date AND :to_date GROUP BY cost_group_id;
  • SELECT transaction_type, COUNT(*) FROM apps.pjm_project_cost_history_v WHERE organization_id = :org_id GROUP BY transaction_type;

Because the view is read-only and derives from CST cost group history, queries should be filtered by organization and date range to limit data volume, and results are already currency-rounded for direct reporting.