Results for “cst_pm_matl_txn_v”

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

Overview

CST_PM_MATL_TXN_V is an Oracle E-Business Suite 12.1.1 and 12.2.2 dictionary view owned by the APPS schema and classified under the BOM (Bills of Material) product family. Its documented purpose is to support the concurrent programs that perform Project Cost Transfer into Oracle Projects, supplying material transaction data that is subsequently interfaced into Oracle Projects as project expenditures. The view consolidates inventory material transaction records with transaction type, organization parameter, item, and secondary inventory attributes so that cost collection and transfer processes can determine which transactions are eligible for project cost transfer and at what cost.

The search term pm_cost_collected corresponds directly to a column exposed by this view. PM_COST_COLLECTED is the flag that indicates whether a given material transaction has already been picked up and collected by the Project Manufacturing cost collection logic, which is the necessary precondition for transferring the cost to Oracle Projects. The view therefore acts as the reporting and integration surface through which collected material costs are surfaced for transfer processing.

Underlying Base Objects

Per the ETRM metadata, CST_PM_MATL_TXN_V is defined over the following base objects (referenced as synonyms): MTL_MATERIAL_TRANSACTIONS, MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS, MTL_TRANSACTION_TYPES, PJM_ORG_PARAMETERS, WIP_ACCOUNTING_CLASSES, WIP_DISCRETE_JOBS, and WIP_FLOW_SCHEDULES.

The core driving table is MTL_MATERIAL_TRANSACTIONS (aliased MMT in the view text). It is joined to MTL_TRANSACTION_TYPES on TRANSACTION_TYPE_ID to derive the transaction TYPE_CLASS; to MTL_PARAMETERS on ORGANIZATION_ID, filtered by PROCESS_ENABLED_FLAG = 'N'; to MTL_SYSTEM_ITEMS on ORGANIZATION_ID and INVENTORY_ITEM_ID for item description and asset flags; and to MTL_SECONDARY_INVENTORIES twice (from and to subinventories) to resolve asset inventory attributes for the source and transfer subinventories. The WIP_FLOW_SCHEDULES reference supports the FLOW_SCHEDULE indicator, and PJM_ORG_PARAMETERS and the WIP accounting objects support Project Manufacturing and outside-processing conditions applied by the full view definition.

Key Columns

• TRANSACTION_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID — primary identifiers for the material transaction, inventory organization, and item.
• TYPE_CLASS — derived via NVL(MTT.TYPE_CLASS, -99); classifies the transaction type and drives the DECODE logic for expenditure organization.
• EXPENDITURE_TYPE, PROJECT_ID, TASK_ID, TO_PROJECT_ID, TO_TASK_ID, SOURCE_PROJECT_ID, SOURCE_TASK_ID — project and task attribution required by Oracle Projects cost transfer.
• PRIMARY_QUANTITY, COSTED_FLAG, COST_GROUP_ID, TRANSFER_COST_GROUP_ID — quantity and cost group context for the transaction.
• PM_COST_COLLECTED — the Project Manufacturing cost collection flag; pm_cost_collected is the searched attribute indicating whether the transaction has been collected for project costing.
• PM_COST_COLLECTOR_GROUP_ID — identifies the cost collector group associated with the transaction.
• EXP_ORG_ID — derived by DECODE(MTT.TYPE_CLASS, 1, MMT.PA_EXPENDITURE_ORG_ID, MMT.ORGANIZATION_ID), resolving the correct expenditure organization.
• TRANSFER_TRANSACTION_ID, TRANSFER_ORGANIZATION_ID, TRANSFER_SUBINVENTORY, INVENTORY_ASSET_FLAG, SI_ASSET_YES_NO, TRANSFER_SI_ASSET_YES_NO, FLOW_SCHEDULE — transfer and asset-related attributes used by downstream processing.
• ACCT_PERIOD_ID, TRANSACTION_DATE, DISTRIBUTION_ACCOUNT_ID — accounting period, date, and distribution account.

Common Use Cases and Queries

The view is principally consumed by the Project Cost Transfer to Oracle Projects concurrent programs. A typical diagnostic query filters on the collected flag to identify collected versus uncollected material transactions for a project or organization.

• Find collected transactions for transfer: SELECT transaction_id, organization_id, project_id, task_id, inventory_item_id, primary_quantity, pm_cost_collected FROM cst_pm_matl_txn_v WHERE pm_cost_collected = 'Y' AND organization_id = :org_id;
• Identify uncollected candidates: SELECT transaction_id, expenditure_type, cost_group_id FROM cst_pm_matl_txn_v WHERE pm_cost_collected = 'N' AND project_id = :project_id;
• Review transfer targets: SELECT transaction_id, source_project_id, to_project_id, transfer_cost_group_id, exp_org_id FROM cst_pm_matl_txn_v WHERE transfer_transaction_id IS NOT NULL;
• Asset inventory analysis: SELECT transaction_id, si_asset_yes_no, transfer_si_asset_yes_no, inventory_asset_flag FROM cst_pm_matl_txn_v WHERE si_asset_yes_no = 'Y';

Because the view applies restrictive predicates (for example, PROCESS_ENABLED_FLAG = 'N' and asset-flag exclusions), users should treat its row set as pre-filtered for eligibility rather than as a complete extract of MTL_MATERIAL_TRANSACTIONS.