Search Results tot_material_value

Overview

PJM_PROJECT_ONHAND_VALUE_V is a Project Manufacturing (PJM) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide project inventory on-hand valuation for the Web Inquiry, exposing the current on-hand quantity and the associated cost buildup for items that are held against a project and task in a project-enabled organization. The view joins project inventory transactions with the cost layers maintained by Oracle Cost Management, converting the resulting values into a display-formatted string using the functional currency's format mask.

The object is central to the answer for the frequently searched term tot_material_value, because the view projects the material component of the on-hand value—MATERIAL_COST—alongside the other cost elements, and its numeric material column feeds the formatted total that Project Manufacturing cost inquiry screens display as the material value. It is a read-only inquiry construct and is not designed to be updated or used as a posting source.

Underlying Base Objects

The view is defined over the following documented base objects and synonyms:

• PJM_PROJECT_PARAMETERS — supplies the PROJECT_ID context that ties an organization or inventory owner to a project.
• MTL_ONHAND_QUANTITIES and MTL_ONHAND_QUANTITIES_DETAIL — the on-hand quantity fact tables used to derive TRANSACTION_QUANTITY by item, organization, and location.
• CST_QUANTITY_LAYERS — the cost layer records in which the receipt and issue costs for each item are accumulated.
• CST_ITEM_COSTS — provides ITEM_COST and the individual cost element columns (MATERIAL_COST, MATERIAL_OVERHEAD_COST, RESOURCE_COST, OUTSIDE_PROCESSING_COST).
• CST_COST_GROUPS — resolves COST_GROUP_ID to COST_GROUP and DESCRIPTION.
• MTL_SYSTEM_ITEMS_KFV — supplies the CONCATENATED_SEGMENTS item identifier used in the Web Inquiry.
• HR_ALL_ORGANIZATION_UNITS_TL, HR_ORGANIZATION_INFORMATION, MTL_PARAMETERS, and MTL_ITEM_LOCATIONS — resolve organization and location names and attributes.
• FND_CURRENCIES and the FND_CURRENCY_CACHE package — provide CURRENCY_CODE, PRECISION, EXTENDED_PRECISION, and MINIMUM_ACCOUNTABLE_UNIT, and the GET_FORMAT_MASK function used to format the numeric results.
• GL_SETS_OF_BOOKS — supplies the set of books context related to the ledger currency.

Key Columns

• PROJECT_ID, ORGANIZATION_ID, COST_GROUP_ID, INVENTORY_ITEM_ID — the grouping keys for the valuation rows.
• COST_GROUP, DESCRIPTION — cost group identification and description.
• NAME (organization name), CONCATENATED_SEGMENTS (item key) — descriptive attributes for inquiry display.
• SUM(NVL(QTY.TRANSACTION_QUANTITY,0)) — the aggregated on-hand quantity for the group.
• ROUND(LAYER.ITEM_COST, ...) — the unit cost rounded to the currency precision.
• The four formatted cost element columns derived from MATERIAL_COST, MATERIAL_OVERHEAD_COST, RESOURCE_COST, and OUTSIDE_PROCESSING_COST, each computed as the cost multiplied by quantity, divided by the minimum accountable unit and then multiplied back, and finally converted with FND_CURRENCY_CACHE.GET_FORMAT_MASK. These supply the display values that Project Manufacturing inquiries report, including the material portion associated with the search term tot_material_value.

Common Use Cases and Queries

The view is typically queried for project on-hand valuation inquiries and for reconciliation of project inventory balances to the general ledger.

SELECT project_id,
       organization_id,
       cost_group,
       concatenated_segments,
       inventory_item_id
  FROM apps.pjm_project_onhand_value_v
 WHERE project_id = :p_project_id
   AND organization_id = :p_org_id;

To isolate the material value component:

SELECT project_id,
       cost_group,
       inventory_item_id
  FROM apps.pjm_project_onhand_value_v
 WHERE project_id = :p_project_id;

Because the cost element columns are returned as formatted character strings, they are suitable for display but not for arithmetic; consumers requiring numeric totals must reaggregate from CST_QUANTITY_LAYERS and CST_ITEM_COSTS directly. The view should always be queried with an ORGANIZATION_ID and PROJECT_ID predicate to limit the potentially large join across on-hand and cost layer data.