Search Results mtl_transaction_flow_headers




Overview
Explore in AI Chat

Overview

MTL_TRANSACTION_FLOW_HEADERS is an Oracle Inventory (INV) table that stores intercompany transaction flow definitions within Oracle E-Business Suite. Each row defines a directional sourcing relationship between a shipping (start) organization and a receiving (end) organization, together with the business rules that govern how the resulting intercompany transactions are priced and accounted. The table functions as the header-level control record for intercompany flows: it establishes the flow type, the qualifier that scopes its applicability, and the effective date range during which the rule is active. Detail-level attributes — item, category, or customer qualifiers — are resolved through the qualifier columns and their associated value identifiers.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning the FK structure does not surface an obvious parent hub dependency. In practical Data Vault terms, this suggests treating MTL_TRANSACTION_FLOW_HEADERS as a hub-like anchor keyed on HEADER_ID, with its descriptive and effective-dated attributes (pricing options, accounting flags, and qualifier scope) modeled as a satellite. This classification is a modeling suggestion only; implementers should validate against actual usage requirements.

Key Information Stored

The surrogate primary key is HEADER_ID, enforced by MTL_TRANSACTION_FLOW_HEADER_PK. A separate unique index, MTL_TRANSACTION_FLOW_HEADER_U1, defines the business-key candidate: START_ORG_ID, END_ORG_ID, FLOW_TYPE, QUALIFIER_CODE, QUALIFIER_VALUE_ID, START_DATE, END_DATE, and ORGANIZATION_ID. This composite key ensures that no two flows collide for the same organization pair, flow type, qualifier scope, and effective window.

  • HEADER_ID — surrogate primary key, referenced by detail and transaction tables.
  • START_ORG_ID / END_ORG_ID — the shipping and receiving inventory organizations that bound the intercompany relationship.
  • FLOW_TYPE — categorizes the nature of the intercompany flow (for example, procurement, transfer, or shipment-based sourcing).
  • QUALIFIER_CODE / QUALIFIER_VALUE_ID — the qualifier dimension and its specific value that scope the flow to a subset of items, categories, or customers.
  • ORGANIZATION_ID — the operating unit or organization context in which the flow is defined.
  • START_DATE / END_DATE — the effective date range governing when the flow rule applies.
  • ASSET_ITEM_PRICING_OPTION / EXPENSE_ITEM_PRICING_OPTION — control how asset and expense items, respectively, are priced on the intercompany transaction.
  • NEW_ACCOUNTING_FLAG — indicates whether the new accounting model applies to the flow.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for customer-specific extensions.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most frequent requirement is identifying the active intercompany flow for a given organization pair and effective date. A typical query pattern filters on the business key and validates the date window:

  • Active flow lookup: SELECT header_id, flow_type, asset_item_pricing_option, expense_item_pricing_option FROM mtl_transaction_flow_headers WHERE start_org_id = :p_start_org AND end_org_id = :p_end_org AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);
  • Flow inventory by organization: aggregate counts of flows grouped by ORGANIZATION_ID and FLOW_TYPE to audit sourcing coverage.
  • Effective-dating audit: detect overlapping or expired flow windows for a qualifier scope using the U1 business key columns.
  • Pricing configuration reporting: report ASSET_ITEM_PRICING_OPTION and EXPENSE_ITEM_PRICING_OPTION across trading partners to verify pricing policy consistency.
  • DFF extraction: joining ATTRIBUTE_CATEGORY with FND_DESCR_FLEX_COLUMN_USAGES / FND_FLEX_VALUES to surface customer-defined flow attributes in operational reports.

Related Objects

The following objects are most significant when working with intercompany flows: