Search Results qualifier_code




Overview
Explore in AI Chat

Overview

MTL_PROCURING_TXN_FLOW_HDRS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and defined in the INV (Inventory) product. It presents the header-level records that describe a "procuring" transaction flow — that is, the material movement of goods from a source organization to a destination organization through a procurement-oriented flow. The view is a filtered projection of the transaction flow header repository, restricted to those headers whose FLOW_TYPE equals 2, which identifies the procuring flow class. In Oracle EBS 12.1.1 and 12.2.2 the object holds a VALID status and is exposed primarily for reporting and integration rather than for direct transactional maintenance. Its role is to give inventory, costing, and supply chain users a stable, read-only interface to the header metadata of procuring flows, allowing queries, custom reports, and interfaces to reference a single logical object without re-implementing the FLOW_TYPE filter. Because it is a view rather than a table, it carries no independent storage and reflects the current state of its base data at query time.

Underlying Base Objects

The view is defined over MTL_TRANSACTION_FLOW_HEADERS, referenced in the ETRM metadata as a SYNONYM. The defining view text is a straightforward SELECT of the complete header column list from that base object, terminated by the predicate WHERE FLOW_TYPE = 2. Consequently, every row returned by MTL_PROCURING_TXN_FLOW_HDRS_V corresponds to exactly one row in MTL_TRANSACTION_FLOW_HEADERS whose flow type designates a procuring flow. No joins are performed and no columns are computed or renamed, so the view is a pure row-filtered projection. This has practical implications: the attributes exposed are identical in name, datatype, and meaning to their base-table counterparts, and any change made to a procuring header row in the base table is immediately visible through the view. The header records are complemented elsewhere in the product by transaction flow line and detail objects, and the HEADER_ID column provides the join key linking this header view to those related transaction flow entities.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on active procuring flows by organization or date range, joining flow headers to flow lines for end-to-end analysis, and driving integrations that consume procurement flow configuration. A representative query follows.

  • List active procuring flow headers for an organization: SELECT header_id, start_org_id, end_org_id, start_date, end_date FROM mtl_procuring_txn_flow_hdrs_v WHERE organization_id = :org_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);
  • Enumerate headers by qualifier: SELECT header_id, qualifier_code, qualifier_value_id FROM mtl_procuring_txn_flow_hdrs_v WHERE qualifier_code = :qualifier;
  • Audit recently changed flows: SELECT header_id, last_update_date, last_updated_by FROM mtl_procuring_txn_flow_hdrs_v WHERE last_update_date >= :since ORDER BY last_update_date DESC;
  • Join headers to lines: SELECT h.header_id, l.line_id FROM mtl_procuring_txn_flow_hdrs_v h, mtl_transaction_flow_lines l WHERE l.header_id = h.header_id;

Because the view already enforces FLOW_TYPE = 2, callers should not re-add that predicate; doing so is redundant though harmless. Standard EBS security and organization access rules governing the base table continue to apply.