Results for “cst_projmfg_cmt_basic_v”

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

Overview

CST_PROJMFG_CMT_BASIC_V is an APPS-owned view that exposes manufacturing commitment information for project manufacturing (project MFG) transactions. In Oracle EBS 12.1.1 and 12.2.2, it is catalogued under the BOM – Bills of Material product family, but its data content is fundamentally cost and commitment oriented: it consolidates material transaction activity, purchasing references, project/task context, and actual cost amounts into a single reporting structure.

The view serves as a foundational source for commitment reporting and integration in Project Manufacturing environments. It is designed to present commitments arising from manufacturing material issues, purchase order receipts, and related costed inventory transactions, aligning them with project, task, and expenditure type attributes. Because it draws from both costing and purchasing tables, it is often used where users need a unified picture of committed cost at the project or task level rather than purely transactional WIP detail.

The search term "actual_cost" is directly relevant: the view explicitly derives commitment amount columns from cost subqueries (COST1 and COST2) that reference actual unit cost data, multiplying those costs by MMT.PRIMARY_QUANTITY to produce extended commitment amounts. This makes the view a natural reference point for reports that reconcile committed quantities and costs against actual costs recorded in the costing tables.

Underlying Base Objects

The documented base objects confirm the hybrid nature of the view. Costing and inventory sources include MTL_MATERIAL_TRANSACTIONS, MTL_CST_ACTUAL_COST_DETAILS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, and MTL_UNITS_OF_MEASURE_TL. Receiving and purchasing sources include RCV_TRANSACTIONS, PO_HEADERS_ALL, PO_LINES_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, and PO_VENDORS. Project and task context is supplied by PJM_PROJECT_PARAMETERS, PJM_TASK_AUTO_ASSIGN (a package, invoked for automatic task assignment), and PA_PERIODS, while PA_EXPENDITURE_TYPES, CST_COST_ELEM_EXP_TYPES, and the PROJECT_MFG package provide expenditure classification and material subelement costing. WIP objects — WIP_DISCRETE_JOBS, WIP_OPERATIONS, WIP_TRANSACTIONS, and WIP_TRANSACTION_ACCOUNTS — supply manufacturing execution context, and HR_ORGANIZATION_INFORMATION with GL_SETS_OF_BOOKS provide organization and ledger attributes.

Functionally, the view joins these objects around MTL_MATERIAL_TRANSACTIONS as the transaction spine, attaching receipt, purchase order, project, and expenditure type attributes, then augments them with cost values from the costing sources referenced by the COST1 and COST2 inline queries.

Key Columns

• PROJECT_ID and TASK_ID — Project and task context. TASK_ID is defaulted through PJM_TASK_AUTO_ASSIGN.INV_TASK_WNPS when a task is not explicitly assigned.
• TRANSACTION_DATE and PERIOD_NAME / GL_PERIOD_NAME — Transaction date and the corresponding PA and GL period names, supporting period-based commitment reporting.
• ORGANIZATION_ID — Inventory organization for the transaction.
• TRANSACTION_ID — Material transaction identifier, formatted as a 15-character string.
• PRIMARY_QUANTITY and PRIMARY_UOM_CODE — Transaction quantity and its primary unit of measure.
• ACTUAL_COST-derived amounts — Commitment cost columns computed as COST1.ACTUAL_COST*MMT.PRIMARY_QUANTITY and (COST2.ACTUAL_COST+COST1.ACTUAL_COST)*MMT.PRIMARY_QUANTITY, appearing twice to represent both the base and cumulative commitment values.
• PO_HEADER_ID, PO_DISTRIBUTION_ID, LINE_NUM, ITEM_DESCRIPTION, VENDOR_ID, VENDOR_NAME — Purchasing and receipt reference attributes linking the commitment to supplier activity.
• EXPENDITURE_CATEGORY and REVENUE_CATEGORY_CODE — Cost/project accounting classification derived from expenditure type setup.
• CURRENCY_CODE — Ledger currency from GL_SETS_OF_BOOKS, supporting monetary reporting.

Common Use Cases and Queries

Typical scenarios include project commitment reporting, reconciliation of manufacturing commitments to actual costs, and integration feeds into project costing or subledger accounting. Because the view exposes both quantity and derived actual-cost commitment amounts, it is frequently queried to compare committed values against actual costed transactions for the same project and task.

A representative query filters commitments for a project and period:

• SELECT project_id, task_id, transaction_date, period_name, organization_id, inventory_item_id, primary_quantity, currency_code FROM apps.cst_projmfg_cmt_basic_v WHERE project_id = :project_id AND period_name = :period_name;

To focus on commitment valuation, users may select the amount columns derived from actual cost:

• SELECT project_id, task_id, inventory_item_id, primary_quantity, currency_code FROM apps.cst_projmfg_cmt_basic_v WHERE project_id = :project_id ORDER BY transaction_date;

For supplier-oriented analysis, joins on PO and vendor attributes are common:

• SELECT v.project_id, v.task_id, v.vendor_name, v.line_num, v.primary_quantity, v.transaction_date FROM apps.cst_projmfg_cmt_basic_v v WHERE v.vendor_id IS NOT NULL AND v.project_id = :project_id;

Because the view relies on inline subqueries and packages such as PJM_TASK_AUTO_ASSIGN and PROJECT_MFG.MATL_SUBELEMENT, performance-sensitive reports should constrain by PROJECT_ID, ORGANIZATION_ID, and period to limit the transaction set processed.