Results for “transaction_source_type_name”

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

Overview

MTL_SUMMARY_TEMP_V is an APPS-owned database view within the Oracle E-Business Suite Inventory (INV) module. The ETRM metadata for this object carries the terse description "10SC ONLY," indicating that the view is scoped to a specific implementation or configuration rather than being a general-purpose, out-of-the-box reporting object. It is documented as a VALID view in both Oracle EBS 12.1.1 and 12.2.2, residing in the APPS schema.

The view exposes summarized inventory transaction activity, aggregated by session and by a defined summary type. Because it joins item identifiers to a concatenated key flexfield representation, it presents transaction summary rows in a form suitable for downstream reporting and integration, allowing consumers to read quantity and value rollups without reconstructing the item flexfield themselves. Its role is therefore one of convenience and presentation: it denormalizes a temporary summary table into a more consumable structure that includes human-readable item segments.

Underlying Base Objects

The view is defined over two documented base objects. The first is MTL_SUMMARY_TEMP, referenced as a synonym, which supplies the core transactional summary data: session context, summary classification, subinventory, locator, transaction descriptors, item and organization identifiers, and the numeric aggregates. The second is MTL_SYSTEM_ITEMS_KFV, also referenced as a synonym, which is the key flexfield view of MTL_SYSTEM_ITEMS. It contributes the PADDED_CONCATENATED_SEGMENTS column.

The join condition is an equi-join on both INVENTORY_ITEM_ID and ORGANIZATION_ID, ensuring that each summary row is matched to the correct item definition within the correct inventory organization. Because the item key flexfield is organization-specific, joining on both keys is essential to prevent cross-organization mismatches. The view text itself performs no aggregation; the summary values are already materialized in MTL_SUMMARY_TEMP, and the view simply enriches and projects them.

Key Columns

• SESSION_ID — Identifier grouping summary rows produced within a single processing session.
• SUMMARY_TYPE — Classifies the basis of the summary (for example, period or transaction grouping).
• SUBINVENTORY / LOCATOR_ID — The subinventory and locator at which the summarized activity occurred.
• TRANSACTION_SOURCE_TYPE_NAME / TRANSACTION_TYPE_NAME / TRANSACTION_ACTION_NAME — Descriptive names for the transaction source, type, and action.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — The item and organization keys, also used to join to the item flexfield view.
• PADDED_CONCATENATED_SEGMENTS — The formatted concatenated item key flexfield, drawn from MTL_SYSTEM_ITEMS_KFV, suitable for display and reporting.
• NET_QTY — The net summarized quantity for the grouping. This is the column most relevant to a search on "net_qty," representing the signed quantity rollup.
• NET_VAL — The net summarized value corresponding to NET_QTY.
• NUM_TXNS — The count of transactions contributing to the summary row.
• ABS_QTY / ABS_VAL — Absolute quantity and value totals, capturing movement magnitude independent of sign.

Common Use Cases and Queries

The view is typically queried to review net and absolute inventory movement by item, organization, subinventory, and locator for a given session, using the concatenated segments for readability. A representative query follows:

• SELECT session_id, summary_type, subinventory, padded_concatenated_segments, net_qty, net_val, num_txns, abs_qty, abs_val FROM apps.mtl_summary_temp_v WHERE organization_id = :org AND net_qty <> 0 ORDER BY session_id, padded_concatenated_segments;
• SELECT inventory_item_id, padded_concatenated_segments, SUM(net_qty) net_qty, SUM(net_val) net_val FROM apps.mtl_summary_temp_v WHERE session_id = :session GROUP BY inventory_item_id, padded_concatenated_segments;

Because the object is documented as "10SC ONLY," its availability and semantics may vary by environment; consumers should confirm applicability before relying on it in production reporting or integrations.