Results for “cst_opi_mmt_mta_v”

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

Overview

CST_OPI_MMT_MTA_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, catalogued under the BOM (Bills of Material) product family. It is referenced by the Inventory Intelligence team for the calculation of transfer cost in a Free On Board (FOB) context. In practical terms, the view consolidates material transaction header information from MTL_MATERIAL_TRANSACTIONS with the corresponding accounting distribution lines from MTL_TRANSACTION_ACCOUNTS, producing a single row per transaction that reconciles the transacted quantity, the transfer cost, and the actual cost posted to the general ledger. Because it bridges operational inventory movement data with accounting valuation data, the view is typically consumed by cost management, inventory valuation, and transfer pricing reporting rather than by core transaction processing.

Underlying Base Objects

The view is defined over the following base objects, all accessed through APPS synonyms in the 12.2.2 environment:

• MTL_MATERIAL_TRANSACTIONS (MMT) — the transaction header table supplying transaction identity, date, organization, item, locator, transaction type and action, source information, transfer organization and subinventory, FOB point, primary quantity, and transfer cost.
• MTL_TRANSACTION_ACCOUNTS (MTA) — the accounting distributions table supplying base transaction value, organization context, and accounting line type.
• MTL_PARAMETERS — the inventory organization parameter table, referenced in the documented object list for organization-level context.

The join between MMT and MTA is performed on TRANSACTION_ID. The view text applies a filter restricting rows to ACCOUNTING_LINE_TYPE = 1 (the inventory valuation line), excludes transaction type 25, and enforces a quantity match condition that is relaxed for transaction actions 1 and 24. Cost is aggregated with SUM(MTA.BASE_TRANSACTION_VALUE) and the result set is grouped by the transaction attributes. The definition is composed of two branches combined by UNION ALL, reflecting the parallel treatment of different accounting or transfer scenarios.

Key Columns

• TRANSACTION_ID / TRANSACTION_DATE — unique identifier and effective date of the material transaction.
• ORGANIZATION_ID — inventory organization sourced from the accounting line, defining the valuation entity.
• INVENTORY_ITEM_ID, SUBINVENTORY_CODE, LOCATOR_ID — the item and its precise storage position.
• TRANSACTION_TYPE_ID, TRANSACTION_ACTION_ID, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_SOURCE_ID, TRANSACTION_SOURCE_NAME — classification of the movement and its originating source.
• TRANSFER_ORGANIZATION_ID, TRANSFER_SUBINVENTORY, TRANSFER_LOCATOR_ID — destination attributes for inter-org and intra-org transfers.
• FOB_POINT — the ownership transfer point that governs which organization bears transfer cost.
• PRIMARY_QUANTITY — transaction quantity in the primary unit of measure.
• TRANSFER_COST — the transfer cost recorded on the transaction header.
• ACTUAL_COST — the aggregated base transaction value from the accounting distributions.

Common Use Cases and Queries

The view is most commonly used to reconcile transfer cost against actual posted cost, to analyze FOB-driven cost allocation between organizations, and to feed inventory intelligence extracts.

SELECT transaction_id, transaction_date, organization_id,
       inventory_item_id, fob_point, primary_quantity,
       transfer_cost, actual_cost
FROM   apps.cst_opi_mmt_mta_v
WHERE  transaction_date BETWEEN :p_from AND :p_to
AND    organization_id = :p_org_id;

To isolate inter-organization transfers and compare header transfer cost with the aggregated accounting value:

SELECT transfer_organization_id, fob_point,
       SUM(transfer_cost) transfer_cost_total,
       SUM(actual_cost)   actual_cost_total
FROM   apps.cst_opi_mmt_mta_v
WHERE  transfer_organization_id IS NOT NULL
GROUP  BY transfer_organization_id, fob_point;

Because the view aggregates accounting lines, queries should avoid joining it to MTL_TRANSACTION_ACCOUNTS directly for the same transaction, as this would multiply the aggregated cost. Filtering by organization and date range is recommended to keep execution plans efficient over the underlying transaction tables.