Search Results mtl_summary_temp




Overview

MTL_SUMMARY_TEMP is a transient working table owned by the INV (Inventory) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. As its name and ETRM description ("Transaction summaries") indicate, it holds aggregated inventory transaction data produced during summary generation and cost processing routines rather than serving as a permanent master or transactional table. Rows are populated during inventory period-close, transaction summarization, and cost manager processing, then consumed by downstream programs that post summarized quantity and value information to the general ledger and cost interfaces.

Consistent with the ETRM metadata, the table is classified heuristically as standalone in Data Vault terms. This is a modeling suggestion rather than a formal designation: the object behaves more like a staging or work satellite than a true hub or link, because it stores session-scoped measures and descriptors keyed to a temporary process rather than durable business entities. Its only documented foreign key points to CST_COST_GROUPS, implying that cost-group-level summarization is one of its primary organizing dimensions.

Key Information Stored

The table contains 15 documented columns. The most operationally significant are:

  • SESSION_ID — Identifies the process run or session that populated the rows. This is the principal access key for retrieving a given run's output and is the closest thing to a surrogate key for the working set.
  • SUMMARY_TYPE — Distinguishes the category of summarization being performed, allowing a single session to hold multiple aggregation views.
  • ORGANIZATION_ID, INVENTORY_ITEM_ID — The inventory organization and item dimensions; these are the core business keys around which quantity and value are aggregated.
  • SUBINVENTORY, LOCATOR_ID — The physical stocking location dimension, supporting subinventory-level and locator-level rollups.
  • TRANSACTION_SOURCE_TYPE_NAME, TRANSACTION_TYPE_NAME, TRANSACTION_ACTION_NAME — Textual descriptors of the source, transaction type, and action, used to group and report movements.
  • COST_GROUP_ID — References CST_COST_GROUPS and drives cost-group-level segmentation of the summarized values.
  • NET_QTY, ABS_QTY, NET_VAL, ABS_VAL, NUM_TXNS — The aggregated measures: net and absolute quantities, net and absolute values, and the count of underlying transactions.

Common Use Cases and Queries

Typical usage centers on post-run verification and reconciliation of summarization output. A common pattern retrieves all rows for the most recent session and joins item or cost-group descriptors for reporting:

  • Diagnosing period-close discrepancies by comparing NET_QTY against ABS_QTY to detect offsetting transactions that cancel in net terms.
  • Reconciling summarized value (NET_VAL) to the general ledger by cost group, joining MTL_SUMMARY_TEMP.COST_GROUP_ID to CST_COST_GROUPS.
  • Auditing transaction volume by source and action using NUM_TXNS grouped by TRANSACTION_SOURCE_TYPE_NAME and TRANSACTION_ACTION_NAME.
  • Validating item/organization level rollups before cost interface posting.

Illustrative query:

SELECT session_id, organization_id, inventory_item_id, subinventory, SUM(net_qty), SUM(net_val), SUM(num_txns) FROM inv.mtl_summary_temp WHERE summary_type = :p_type GROUP BY session_id, organization_id, inventory_item_id, subinventory;

Because the table is transient, queries should always be scoped by SESSION_ID or SUMMARY_TYPE and should not be relied upon for historical reporting after purge.

Related Objects

The most significant relationships are: