Search Results inv_transaction_flow_qualifier

Overview

APPS.MTL_TRANSACTION_FLOWS_V is a VALID database view owned by the APPS schema and registered in FND Design Data as INV.MTL_TRANSACTION_FLOWS_V. It exposes the configuration of inter-company transaction flows — the sourcing and shipping rules that govern how inventory moves between operating units and organizations in a multi-org Oracle E-Business Suite environment. In the context of Oracle EBS 12.1.1 and 12.2.2, the view presents header, line, and node data describing each flow, including the start and end organizations, the intermediate nodes in the flow sequence, the applicable date range, and the pricing and qualifier attributes used to resolve the flow. It is classified as an internal view, and the Oracle documentation explicitly warns that it is for Oracle Internal Use Only and is not supported for direct customer access except through standard Oracle Applications programs. Consequently, it is referenced principally by Oracle's own inventory and inter-company processing logic and should be treated as a reporting aid rather than a public API.

Underlying Base Objects

The view is defined over three documented base objects, each exposed as a SYNONYM in the APPS schema:

• MTL_TRANSACTION_FLOW_HEADERS — supplies the flow header, including HEADER_ID, START_ORG_ID, END_ORG_ID, and the effective START_DATE and END_DATE.
• MTL_TRANSACTION_FLOW_LINES — supplies the sequenced nodes, including LINE_NUMBER, FROM_ORG_ID, TO_ORG_ID, ORGANIZATION_ID, FLOW_TYPE, and the pricing options.
• MTL_INTERCOMPANY_PARAMETERS — supplies the inter-company parameter context, including the qualifier code and qualifier value that determine which item categories a flow applies to.

Because the view joins header, line, and parameter data, it flattens a normalized rule structure into a single queryable result set, which simplifies reporting on flow configuration that would otherwise require multiple joins.

Key Columns

• HEADER_ID — Foreign key to MTL_TRANSACTION_FLOW_HEADERS; identifies the parent flow.
• START_ORG_ID / END_ORG_ID — The start operating unit and the end operating unit of the inter-company flow.
• FROM_ORG_ID / TO_ORG_ID — The shipping (or procuring) organization and the receiving/selling organization for each line node.
• ORGANIZATION_ID — The organization associated with the flow line.
• LINE_NUMBER — The sequence of the intermediate node within the flow.
• FLOW_TYPE — 1 indicates a Shipping Flow; 2 indicates a Procuring Flow.
• QUALIFIER_CODE — The qualifier for the inter-company transaction flow; this is a lookup code in MFG lookups under lookup type INV_TRANSACTION_FLOW_QUALIFIER, which is precisely the term the user searched for.
• QUALIFIER_VALUE_ID — The value for the qualifier; for the 115.10 release, this is the item category identifier.
• START_DATE / END_DATE — The active window for the inter-company transaction flow.
• ASSET_ITEM_PRICING_OPTION — Pricing for asset items in a procuring flow: 1 = PO Price, 2 = Transfer Price.
• EXPENSE_ITEM_PRICING_OPTION — Pricing for expense items in a procuring flow: 1 = PO Price, 2 = Transfer Price.

Common Use Cases and Queries

Typical usage involves auditing which inter-company flows are active between organizations, verifying the qualifier and pricing options applied to a flow, and diagnosing sourcing or transfer-pricing behavior. To resolve the lookup meaning of the qualifier code, join to MFG_LOOKUPS on the INV_TRANSACTION_FLOW_QUALIFIER lookup type.

• List all active flows with their start and end organizations:

  SELECT header_id, start_org_id, end_org_id, line_number,
         from_org_id, to_org_id, flow_type,
         qualifier_code, start_date, end_date
  FROM   apps.mtl_transaction_flows_v
  WHERE  SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

• Decode the qualifier and pricing options:

  SELECT f.header_id, f.from_org_id, f.to_org_id,
         f.qualifier_code, f.qualifier_value_id,
         f.asset_item_pricing_option,
         f.expense_item_pricing_option
  FROM   apps.mtl_transaction_flows_v f
  WHERE  f.flow_type = 2;

All access should respect the Oracle Internal Use Only restriction and be limited to read-only reporting against a supported applications schema.