Search Results from_organization_code




Overview
Explore in AI Chat

Overview

MTL_TRANSACTION_FLOW_LINES_V is an Oracle E-Business Suite Inventory (INV) view owned by the APPS schema. It exposes the intercompany transaction flow lines associated with shipping and procuring flows for each transaction flow header. In the Oracle EBS 12.1.1 and 12.2.2 data models, intercompany transaction flows are persisted in the MTL_TRANSACTION_FLOW_HEADERS and MTL_TRANSACTION_FLOW_LINES tables, which record the logical movement of material between organizations and operating units as part of internal sales order and intercompany invoicing processing. This view provides a denormalized, reporting-friendly projection of the line-level data, joining in descriptive names for the source and destination organizations.

The view is intended primarily for inquiry, reporting, and integration use cases where the caller needs to resolve organization identifiers into human-readable names without writing the multi-table join manually. It is a read-only definition; no DML should be performed against it.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, MTL_TRANSACTION_FLOW_LINES_V is defined over the following referenced objects:

The view is constructed as a UNION ALL of two branches. The first branch returns rows where both FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID are populated, joining all four descriptive tables so that both organization codes are resolved. The second branch handles the remaining cases and suppresses the FROM_ORGANIZATION_CODE value (returning NULL) while still resolving the destination organization code, ensuring that lines with incomplete organization pairing remain visible rather than being eliminated by inner joins.

Key Columns

  • ROW_ID — the ROWID of the underlying MTL_TRANSACTION_FLOW_LINES row, useful for direct keyed lookups.
  • HEADER_ID — foreign key to the parent transaction flow header; lines are grouped under this value.
  • LINE_NUMBER — the sequence of the line within its header.
  • FROM_ORG_ID / FROM_ORG_NAME — the source operating unit identifier and its name from HR_OPERATING_UNITS. This is the column most commonly matched against the search term from_org_name.
  • FROM_ORGANIZATION_ID / FROM_ORGANIZATION_CODE — the source inventory organization identifier and its code from MTL_PARAMETERS.
  • TO_ORG_ID / TO_ORG_NAME — the destination operating unit identifier and name.
  • TO_ORGANIZATION_ID / TO_ORGANIZATION_CODE — the destination inventory organization identifier and code.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment columns.

Common Use Cases and Queries

The view is typically used to report on intercompany movements and to reconcile shipping and procuring flows between operating units. A common requirement is filtering or grouping by the source organization name:

  • Listing all flow lines originating from a named operating unit: SELECT header_id, line_number, from_org_name, to_org_name FROM mtl_transaction_flow_lines_v WHERE from_org_name = :p_org_name;
  • Resolving organization codes for a given header: SELECT line_number, from_organization_code, to_organization_code FROM mtl_transaction_flow_lines_v WHERE header_id = :p_header_id ORDER BY line_number;
  • Producing a from-to matrix for reconciliation: SELECT from_org_name, to_org_name, COUNT(*) FROM mtl_transaction_flow_lines_v GROUP BY from_org_name, to_org_name;

Because the definition uses UNION ALL and inner joins to the descriptive tables, queries should account for rows where FROM_ORGANIZATION_CODE is NULL. Application of standard EBS security predicates through HR_OPERATING_UNITS is advisable when the view is exposed to end users, and results should be filtered by header or organization to limit the volume returned.