Search Results new_quantity

Overview

The APPS.PJM_PROJECT_COST_HISTORY_V view is a Project Manufacturing (PJM) reporting object that exposes item cost history information for the Oracle E-Business Suite Web Inquiry interface. In releases 12.1.1 and 12.2.2, this view serves as a denormalized, currency-aware presentation layer over the underlying cost history tables maintained by Oracle Cost Management. Its principal role is to supply the data required by the self-service Web Inquiry pages that allow users to review how an item's cost has changed transaction by transaction within an inventory organization, including quantity movements and the resulting prior, actual, and new cost balances.

The most commonly searched column in this object is TRANSACTION_COSTED_DATE, which records the date on which the cost processor actually costed the transaction. This differs from TRANSACTION_DATE (the date the transaction occurred in inventory). Discrepancies between these two dates are normal and reflect the periodic Cost Management cost processor run, making the distinction essential for reconciliation and audit reporting.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, APPS.PJM_PROJECT_COST_HISTORY_V is defined over the following base objects:

• CST_CG_COST_HISTORY_V (VIEW) — the primary cost group cost history view, referenced in the view text by the alias CCCHV. All cost, quantity, and transaction columns are drawn from this object.
• FND_CURRENCIES (SYNONYM) — referenced by the alias CURR, used to derive the correct rounding precision for monetary columns.
• GL_SETS_OF_BOOKS (VIEW) — supplies the set of books context that links currencies to the operating unit's ledger.
• HR_ORGANIZATION_INFORMATION (SYNONYM) — provides organization classification attributes used to resolve inventory organization context.

Because the view selects from CST_CG_COST_HISTORY_V rather than directly from base cost tables, it inherits the column semantics of that view and simply adds currency precision rounding and the standard inventory organization join criteria.

Key Columns

• INVENTORY_ITEM_ID, ORGANIZATION_ID — identify the item and inventory organization for each cost history record.
• TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, TRANSACTION_COSTED_DATE — the transaction identity, type, occurrence date, and the date the cost processor costed it.
• LAYER_ID, COST_GROUP_ID — the cost layer and cost group associated with the movement.
• PRIOR_COSTED_QUANTITY, PRIMARY_QUANTITY, NEW_QUANTITY — the on-hand quantity before, the transaction quantity, and the resulting quantity.
• PRIOR_COST, ACTUAL_COST, NEW_COST — the unit cost before, the cost applied by the transaction, and the resulting cost.
• ACTUAL_MATERIAL, ACTUAL_MATERIAL_OVERHEAD, ACTUAL_RESOURCE, ACTUAL_OUTSIDE_PROCESSING, ACTUAL_OVERHEAD — cost element detail for the transaction.
• PRIOR_* / NEW_* material, overhead, resource, and outside processing columns — corresponding element breakdowns before and after the movement.

All monetary columns are wrapped in ROUND(...) using NVL(CURR.EXTENDED_PRECISION, NVL(CURR.PRECISION, 0)), so the values returned are pre-rounded to the currency's defined precision.

Common Use Cases and Queries

The view supports cost element reconciliation, project manufacturing cost audit, and cost processor troubleshooting. A typical query filters by organization and item:

• Reviewing all cost movements for an item: SELECT inventory_item_id, transaction_id, transaction_type, transaction_date, transaction_costed_date, actual_cost FROM pjm_project_cost_history_v WHERE organization_id = :org AND inventory_item_id = :item;
• Identifying transactions costed in a period different from the transaction date, using TRANSACTION_COSTED_DATE: SELECT transaction_id, transaction_date, transaction_costed_date FROM pjm_project_cost_history_v WHERE TRUNC(transaction_costed_date) > TRUNC(transaction_date);
• Reconciling prior, actual, and new cost balances across cost elements for a cost group.

Because the view is read-only and joins multiple base objects, queries should always be constrained by ORGANIZATION_ID and INVENTORY_ITEM_ID or by a date range on TRANSACTION_COSTED_DATE to avoid full-table processing.