Search Results mtl_transaction_flow_header_u1

Overview

MTL_TRANSACTION_FLOW_HEADERS is an Oracle Inventory (INV) seed table that stores the configuration of inter-company transaction flows used in Drop Ship and Global Procurement business scenarios. Each row defines a directed relationship between a start operating unit and an end operating unit, together with the flow type, an optional qualifier, a default inventory organization, and the effective date range during which the flow is active. The table resides in the APPS_TS_SEED tablespace, reflecting its role as a configuration repository rather than a high-volume transactional entity.

Within the Oracle EBS 12.1.1 and 12.2.2 data model, the object functions as an independent reference table with no documented foreign key dependencies to parent entities. The heuristic Data Vault classification mined from the foreign key structure is standalone. From a modeling perspective, this suggests the table is best treated as its own hub-like reference artifact, with its unique business key serving as the natural identifier and the descriptive attributes around pricing, organization defaults, and effective dating behaving as satellite-style context. It is not modeled as a link, since the relationship between start and end organizations is captured intrinsically through the column pairs rather than through a separate association table.

Key Information Stored

The table contains 33 documented columns. The most significant are summarized below.

• HEADER_ID — Surrogate primary key (MTL_TRANSACTION_FLOW_HEADER_PK) uniquely identifying each flow definition.
• START_ORG_ID — Start operating unit for the inter-company flow.
• END_ORG_ID — End operating unit for the inter-company flow.
• FLOW_TYPE — Numeric flow classification: 1 = Shipping Flow, 2 = Procuring Flow.
• ORGANIZATION_ID — Default inventory organization. For shipping flows this is the ship-from organization; for procuring flows this is the ship-to organization.
• QUALIFIER_CODE — Lookup code drawn from MFG lookups with lookup type INV_TRANSACTION_FLOW_QUALIFIER.
• QUALIFIER_VALUE_ID — Qualifier value; in release 115.10 and later this carries the item category identifier.
• START_DATE / END_DATE — Effective dating window during which the flow is active.
• ASSET_ITEM_PRICING_OPTION / EXPENSE_ITEM_PRICING_OPTION — Pricing behavior for capitalized versus expensed items in the flow.
• NEW_ACCOUNTING_FLAG — Indicator governing accounting treatment under the newer inter-company accounting model.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield storage for customer-specific extensions.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for auditability.

The unique business-key candidate is MTL_TRANSACTION_FLOW_HEADER_U1, spanning START_ORG_ID, END_ORG_ID, FLOW_TYPE, QUALIFIER_CODE, QUALIFIER_VALUE_ID, START_DATE, END_DATE, and ORGANIZATION_ID. A second nonunique index, MTL_TRANSACTION_FLOW_HEADER_U2, supports HEADER_ID lookups.

Common Use Cases and Queries

Typical use cases include validating that a permitted inter-company flow exists between two operating units before a drop ship or global procurement transaction is processed, and reporting on active flows by organization or flow type.

A common pattern resolves an active flow by organization pair and flow type:

• SELECT header_id, start_org_id, end_org_id, organization_id, qualifier_code FROM mtl_transaction_flow_headers WHERE start_org_id = :p_start AND end_org_id = :p_end AND flow_type = 1 AND SYSDATE BETWEEN NVL(start_date, SYSDATE) AND NVL(end_date, SYSDATE + 1);

Reporting queries frequently join ORGANIZATION_ID to HR_OPERATING_UNITS to render operating unit names, and to MTL_PARAMETERS to resolve the default inventory organization. Administrators also inspect the ATTRIBUTE flexfield columns to confirm customer-specific configurations during upgrades or troubleshooting.

Related Objects

• MTL_PARAMETERS — joined on ORGANIZATION_ID to resolve inventory organization attributes.
• HR_OPERATING_UNITS — joined on START_ORG_ID and END_ORG_ID to obtain operating unit names.
• FND_LOOKUPS — joined on QUALIFIER_CODE (lookup_type = 'INV_TRANSACTION_FLOW_QUALIFIER') to decode the qualifier.
• MTL_TRANSACTION_FLOW_HEADER_U1 / U2 — indexes enforcing uniqueness and supporting lookup by HEADER_ID.
• MTL_SYSTEM_ITEMS_B and MTL_ITEM_CATEGORIES — referenced indirectly via QUALIFIER_VALUE_ID, which carries the item category identifier.
• MTL_TRANSACTIONS — downstream transactions whose drop ship and global procurement processing depends on flow definitions established here.