Search Results from_organization_code




Overview
Explore in AI Chat

Overview

APPS.MTL_TRANSACTION_FLOW_LINES_V is a reporting view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that exposes the line-level details of transaction flow records held in the MTL_TRANSACTION_FLOW_LINES base table. The underlying table stores the participating organizations for a transaction flow, keyed by HEADER_ID and LINE_NUMBER, and holds the "from" and "to" organization identifiers for each leg of a flow. While that base table carries organization identifiers, it does not carry the descriptive organization code (the value many users search for by name, such as to_organization_code) or the operating unit name. This view resolves those identifiers into readable attributes by joining to the operating unit and inventory organization definitions.

The purpose of the view is therefore to present a denormalized, human-readable picture of transaction flow lines, including operating unit names and organization codes for both ends of each flow. It is typically consumed by reports, extracts, and integration interfaces that must translate internal organization identifiers into the codes and names used by end users and downstream systems.

Underlying Base Objects

As documented in the ETRM metadata, the view is owned by APPS and is defined over the following referenced objects:

  • MTL_TRANSACTION_FLOW_LINES (SYNONYM) — the primary driving table, supplying the flow line records (HEADER_ID, LINE_NUMBER, and the from/to organization identifiers).
  • HR_OPERATING_UNITS (VIEW) — joined to supply the operating unit name for the from and to organizations.
  • MTL_PARAMETERS (SYNONYM) — joined to supply the inventory organization code for the from and to organizations.

The view text shows two UNION ALL branches. The first branch joins both FROM and TO organizations to HR_OPERATING_UNITS (aliases HOU1 and HOU3) and to MTL_PARAMETERS (aliases MP2 and MP4), and is restricted to rows where both FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID are populated. This branch supplies both FROM_ORGANIZATION_CODE and TO_ORGANIZATION_CODE. The second branch handles rows where one organization identifier is null: it returns a NULL organization code for the unpopulated side while still resolving the populated side. In both cases the operating unit name is obtained from HR_OPERATING_UNITS using the corresponding *_ORG_ID, and the organization code is obtained from MTL_PARAMETERS using the corresponding *_ORGANIZATION_ID.

Key Columns

The view exposes the following significant columns, based directly on the documented view text:

  • ROW_ID — the ROWID of the underlying MTL_TRANSACTION_FLOW_LINES row.
  • HEADER_ID and LINE_NUMBER — the flow header and line identifiers that together key the line.
  • FROM_ORG_ID / FROM_ORG_NAME — the from-side operating unit identifier and its name (from HR_OPERATING_UNITS).
  • FROM_ORGANIZATION_ID / FROM_ORGANIZATION_CODE — the from-side inventory organization identifier and its code (from MTL_PARAMETERS).
  • TO_ORG_ID / TO_ORG_NAME — the to-side operating unit identifier and its name.
  • TO_ORGANIZATION_ID / TO_ORGANIZATION_CODE — the to-side inventory organization identifier and its code. This is the column users reach for when searching on to_organization_code.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns propagated from the base table.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield attribute columns carried through from the base table.

Common Use Cases and Queries

The most common use is translating organization identifiers into codes and names for reporting on transaction flows between organizations. A typical query resolves the destination organization code for a given flow:

  • Listing all lines for a flow header: SELECT header_id, line_number, from_organization_code, to_organization_code, from_org_name, to_org_name FROM apps.mtl_transaction_flow_lines_v WHERE header_id = :p_header_id ORDER BY line_number;
  • Filtering by destination organization code, which is the exact scenario implied by the search term to_organization_code: SELECT header_id, line_number, from_organization_code, to_organization_code FROM apps.mtl_transaction_flow_lines_v WHERE to_organization_code = :p_to_org_code;
  • Auditing recent flow activity across organizations: SELECT header_id, line_number, from_org_name, to_org_name, to_organization_code, creation_date FROM apps.mtl_transaction_flow_lines_v WHERE creation_date >= :p_from_date ORDER BY creation_date DESC;
  • Extracting both sides of each flow for downstream integration: SELECT header_id, line_number, from_organization_code, to_organization_code, attribute1 FROM apps.mtl_transaction_flow_lines_v;

Because the view performs the operating unit and organization code lookups internally, consumers avoid writing the joins to HR_OPERATING_UNITS and MTL_PARAMETERS themselves. Note that rows with a null organization identifier on one side appear with a NULL organization code in the corresponding column, reflecting the UNION ALL structure of the view definition.