Results for “org_code”

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

Overview

CST_MTL_RCV_TXN_V is an APPS-owned view in Oracle E-Business Suite, catalogued under the BOM (Bills of Material) product family. It presents a consolidated, denormalized projection of material transaction and receiving activity, joining inventory transaction data to cost group, legal entity, ledger, and organization context. The view is primarily a costing-oriented read model: it exposes the shipment, transfer, and receipt attributes that cost processors and reconciliation reports require without forcing consumers to reassemble the underlying join graph themselves.

Because the object is a view rather than a table, it holds no data of its own and reflects the current state of its base objects at query time. In both 12.1.1 and 12.2.2 it resides in the APPS schema with VALID status. Its practical role is reporting and integration: costing extracts, receiving-to-costing reconciliation, inter-org transfer analysis, and third-party or custom integrations that need a single SQL source for transaction-level cost movement data. Users searching on the term "mtl_transaction_action" typically arrive here because the view exposes TRANSACTION_ACTION_ID and its decoded MEANING, which is the join path to the MTL_TRANSACTION_ACTIONS lookup used across inventory and receiving flows.

Underlying Base Objects

The view is defined over a wide set of documented base objects anchored on MTL_MATERIAL_TRANSACTIONS. Costing context is supplied by CST_COST_GROUPS and CST_COST_GROUP_ASSIGNMENTS, with organization and ledger context from MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS_TL, and GL_LEDGER_LE_V. Legal entity and first-party identity come from XLE_FIRSTPARTY_INFORMATION_V. Transaction classification is resolved through MTL_TRANSACTION_TYPES, MTL_TXN_SOURCE_TYPES, and MFG_LOOKUPS (for transaction action meanings).

Receiving-specific columns draw on RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_ACCOUNTING_EVENTS, and RCV_ACCOUNTING_EVENT_TYPES. Source-document decoding reaches into PO_HEADERS_ALL, PO_LINES_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_VENDORS, and PO_VENDOR_SITES_ALL for purchasing flows; MTL_SALES_ORDERS_KFV and MTL_GENERIC_DISPOSITIONS for sales order and disposition sources; WIP_ENTITIES for work order sources; MTL_TXN_REQUEST_HEADERS for move orders; MTL_CYCLE_COUNT_HEADERS and MTL_PHYSICAL_INVENTORIES for count sources; and MTL_SYSTEM_ITEMS_VL, MTL_ITEM_LOCATIONS_KFV, MTL_TRANSACTION_REASONS, GL_CODE_COMBINATIONS_KFV, and CST_COST_UPDATES for item, locator, reason, account, and cost-update context.

Key Columns

• TRANSACTION_ID / TRANSFER_TRANSACTION_ID — primary transaction identifiers, linking back to MTL_MATERIAL_TRANSACTIONS.
• TRANSACTION_ACTION_ID and TRANSACTION_ACTION — the action code and its decoded meaning (for example, issue, receipt, transfer), decoded via MFG_LOOKUPS on the MTL_TRANSACTION_ACTIONS lookup type.
• TRANSACTION_SOURCE_TYPE_ID and TRANSACTION_SOURCE_NAME — a DECODE resolves the human-readable source document: purchase order segment, sales order, cycle count, physical inventory, move order, WIP entity, or requisition number, depending on source type.
• TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY, PRIMARY_UOM_CODE — transaction and primary-unit quantities and units of measure.
• ORGANIZATION_ID, TRANSFER_ORGANIZATION_ID, SUBINVENTORY_CODE, LOCATOR_ID, TRANSFER_SUBINVENTORY, TRANSFER_LOCATOR_ID — from/to inventory location context.
• COST_GROUP_ID, COST_GROUP, LEGAL_ENTITY_ID, PRIMARY_LEDGER_ID — costing and financial context.
• INVENTORY_ITEM_ID, DESCRIPTION, REVISION — item identity and revision.
• SHIPMENT_NUMBER, WAYBILL_AIRBILL, FREIGHT_CODE, NUMBER_OF_CONTAINERS — logistics and shipment attributes.
• TRANSACTION_DATE, REASON_NAME, TRANSACTION_REFERENCE — timing and reason attribution.
• LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID — audit and concurrent program lineage.

Common Use Cases and Queries

Typical uses include reconciling inventory transactions against receiving events, analyzing inter-organization transfers, and feeding costing processes that need transaction action and source context in one row.

Transactions by action and source:

SELECT transaction_id, transaction_action, transaction_source_name,
       transaction_quantity, transaction_uom, transaction_date
FROM   apps.cst_mtl_rcv_txn_v
WHERE  organization_id = :org_id
AND    transaction_action_id = :action_id
ORDER BY transaction_date DESC;

Receiving-to-costing reconciliation by shipment:

SELECT shipment_number, inventory_item_id, description, revision,
       transaction_quantity, primary_quantity, cost_group, legal_entity_id
FROM   apps.cst_mtl_rcv_txn_v
WHERE  shipment_number = :shipment_number;

Inter-org transfer analysis:

SELECT organization_id, transfer_organization_id,
       subinventory_code, transfer_subinventory,
       transaction_quantity, transaction_action
FROM   apps.cst_mtl_rcv_txn_v
WHERE  transaction_date BETWEEN :from_date AND :to_date
AND    transfer_organization_id IS NOT NULL;

Because the view resolves transaction action and source names internally, it is an efficient basis for ad-hoc reporting without replicating the DECODE logic against MTL_TRANSACTION_TYPES, MTL_TXN_SOURCE_TYPES, and MFG_LOOKUPS. Filters on ORGANIZATION_ID and TRANSACTION_DATE are recommended for performance given the broad multi-module join graph.