Search Results flow_type




Overview
Explore in AI Chat

Overview

The APPS.MTL_PROCURING_TXN_FLOW_HDRS_V view is a specialized reporting and integration interface within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It exposes a filtered subset of transaction flow header records used by Oracle's Supply Chain and Inventory Management modules to track the movement of material between organizations and, specifically, the procurement-related transaction flows that govern how items are sourced, received, and transferred.

The name of the view — "PROCURING_TXN_FLOW_HDRS" — signals its intent: it presents the header-level rows that describe a procuring transaction flow. Legally and architecturally, the view is defined as a simple projection over the underlying base table, applying a single deterministic filter. Its primary purpose is to provide downstream Oracle forms, concurrent programs, and customer-built reports with a clean, pre-filtered dataset that isolates procuring flows without requiring callers to know the internal numeric encoding of the FLOW_TYPE discriminator column.

Because the view is owned by APPS and is not a multi-org secured view in the same manner as the underlying transactional tables, consumers must remain aware of the organization context (through ORG_ID / ORGANIZATION_ID columns and the standard MOAC initialization) when building queries.

Underlying Base Objects

The view is defined exclusively over a single base object:

The ETRM metadata documents the view definition verbatim:

SELECT HEADER_ID, START_ORG_ID, END_ORG_ID, ... , FLOW_TYPE, ...
FROM MTL_TRANSACTION_FLOW_HEADERS
WHERE FLOW_TYPE = 2

This is a one-to-one projection with a row-restricting predicate. No joins, aggregations, or analytic functions are applied. Consequently, every column exposed by the view maps directly to a column of MTL_TRANSACTION_FLOW_HEADERS, and the only transformation is the implicit constant filter FLOW_TYPE = 2. Because the view is read-only and defined over a synonym, no direct DML should be issued against it; changes must be made against the base table by Oracle's seeded business logic.

In Oracle's internal numbering scheme for transaction flow headers, the value 2 corresponds to procuring flows, which is what the view name and the historical usage of this object confirm.

Key Columns

  • HEADER_ID — Primary key of the flow header. Uniquely identifies each procuring flow.
  • FLOW_TYPE — Discriminator column; for this view it is always 2 (procuring). The user's search term "flow_type" directly targets this column.
  • START_ORG_ID / END_ORG_ID — The source and destination inventory organizations for the flow, defining the inter-org routing path.
  • ORGANIZATION_ID — The organization context of the header record.
  • QUALIFIER_CODE / QUALIFIER_VALUE_ID — Identify the qualifier (e.g., supplier, customer, or item category) that scopes the flow, enabling conditional sourcing rules.
  • ASSET_ITEM_PRICING_OPTION / EXPENSE_ITEM_PRICING_OPTION — Govern how asset and expense items are priced during the procuring flow.
  • START_DATE / END_DATE — Effective dates controlling the active window of the flow.
  • NEW_ACCOUNTING_FLAG — Indicator of accounting treatment (e.g., receipt vs. inter-org accounting).
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) columns for extensibility.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical consumers include inter-org transfer setup reports, procurement sourcing validation, and custom data extracts feeding integration layers. The following sample queries reflect standard usage.

List all active procuring flows for an organization:

SELECT header_id, start_org_id, end_org_id, start_date, end_date
FROM   apps.mtl_procuring_txn_flow_hdrs_v
WHERE  organization_id = :p_org_id
AND    SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

Retrieve qualifier-driven flows for a specific supplier:

SELECT header_id, qualifier_code, qualifier_value_id
FROM   apps.mtl_procuring_txn_flow_hdrs_v
WHERE  qualifier_code = 'SUPPLIER'
AND    qualifier_value_id = :p_vendor_id;

Inspect DFF attributes for auditing:

SELECT header_id, attribute_category, attribute1, attribute2
FROM   apps.mtl_procuring_txn_flow_hdrs_v
WHERE  attribute_category IS NOT NULL;

Because FLOW_TYPE is fixed at 2, queries that filter on other flow types (such as shipping or receiving) must target MTL_TRANSACTION_FLOW_HEADERS directly. Applications requiring a union of all flow categories should likewise query the base table rather than this view.