Search Results po_line_types_vl




Overview
Explore in AI Chat

Overview

PO_LINE_TYPES_VL is a multilingual (VL) view owned by the APPS schema within the Oracle Purchasing (PO) module. It presents the definition of purchasing line types — the classifications that determine how a purchase order or requisition line behaves during ordering, receiving, and matching. In Oracle EBS 12.1.1 and 12.2.2 the view combines the language-independent attributes stored in the base table with the translatable text held in the translation table, exposing a single denormalized record per line type in the session's active language.

Because line types drive downstream processing such as receiving enforcement, inspection requirements, and invoice matching rules, the view is widely referenced in reports, concurrent programs, and integration interfaces that need to resolve a LINE_TYPE_ID to a human-readable name or to inspect processing behavior. Reports built on Purchasing, iProcurement, and Payables frequently join to this view to display or filter by line type.

Underlying Base Objects

The documented view text is defined over two synonyms, both resolving to tables in the APPS schema:

The join is performed on LINE_TYPE_ID, with the translation side restricted by T.LANGUAGE = USERENV('LANG'), so the view returns exactly one row per line type for the language of the current session. The ROW_ID column is drawn from the base table's ROWID.

Key Columns

  • LINE_TYPE_ID — Primary key of the line type; the value stored on order lines.
  • LINE_TYPE and DESCRIPTION — The translated name and description from PO_LINE_TYPES_TL.
  • ORDER_TYPE_LOOKUP_CODE — Distinguishes document intent (for example, purchase order versus blanket agreement).
  • RECEIVING_FLAG and OUTSIDE_OPERATION_FLAG — Control whether the line is received and whether outside processing applies.
  • RECEIVE_CLOSE_TOLERANCE — Tolerance governing receipt-based closure of the line.
  • PURCHASE_BASIS and MATCHING_BASIS — Determine purchasing and invoice matching behavior.
  • UNIT_OF_MEASURE, UNIT_PRICE, CATEGORY_ID — Defaults applied when the line type is used.
  • INACTIVE_DATE — Date after which the line type should no longer be selected.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segments.
  • Audit and concurrency columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include validating that an order line points to an active line type, defaulting purchasing attributes during order entry or import, and generating listings of available line types in the user's language. The following query returns active line types ordered by name:

SELECT line_type_id, line_type, description, receiving_flag, matching_basis
FROM po_line_types_vl
WHERE inactive_date IS NULL OR inactive_date > SYSDATE
ORDER BY line_type;

A second pattern resolves a stored ID to its display name when building interface or reconciliation reports:

SELECT plv.line_type, pol.line_number
FROM po_lines_all pol, po_line_types_vl plv
WHERE pol.line_type_id = plv.line_type_id
AND pol.po_header_id = :p_header_id;

Because the view filters on USERENV('LANG'), results vary with the session language; integrations that must be language-independent should query PO_LINE_TYPES_B directly or join the translation table with an explicit language condition.