Search Results po_line_types_tl




Overview
Explore in AI Chat

Overview

The PO_LINE_TYPES_TL table resides in the PO (Purchasing) schema and serves as the translated (multi-language) companion to the base line type definition used by Oracle Purchasing. In Oracle EBS 12.1.1 and 12.2.2, purchasing documents such as purchase orders, RFQs, and quotations rely on line types to classify each line's behavior — for example, distinguishing goods, services, outside processing, or fixed-price lines. The _TL suffix denotes a translation table, meaning it stores the language-dependent descriptive text (such as the user-visible line type description) separated from language-independent attributes held in the base table PO_LINE_TYPES_B.

Per the heuristic Data Vault classification mined from the object's foreign-key structure, this object is modeled as standalone. From a dimensional-modeling standpoint, this suggests treating PO_LINE_TYPES_TL as a reference or lookup satellite that carries descriptive, language-specific attributes keyed by the language and the line type identifier, rather than participating in a broader hub-and-link topology.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • LINE_TYPE_ID — Surrogate identifier referencing the parent line type in the base table; a component of the primary key and central join key.
  • LANGUAGE — The NLS language code identifying the translation; combined with LINE_TYPE_ID it forms the primary key.
  • LINE_TYPE — The internal name/code of the line type; also documented as a business-key candidate via unique index PO_LINE_TYPES_TL_U2.
  • DESCRIPTION — The translated, user-facing description displayed in Purchasing forms and reports.
  • SOURCE_LANG — Indicates the source language from which the translation was derived.
  • ZD_EDITION_NAME — The editioning column introduced in 12.2.2, supporting online patching and edition-based redefinition; it appears in both unique indexes.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard EBS audit columns capturing who created and last modified each row and when.

The surrogate primary key is PO_LINE_TYPES_TL_PK (LANGUAGE, LINE_TYPE_ID). Two unique indexes act as business-key candidates: PO_LINE_TYPES_TL_U1 (LINE_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) and PO_LINE_TYPES_TL_U2 (LINE_TYPE, LANGUAGE, ZD_EDITION_NAME). The second uniquely identifies a line type by its internal code per language and edition.

Common Use Cases and Queries

Typical reporting needs involve joining the translation table to the base table to render descriptive line type labels in the user's language. A common pattern is:

  • Joining PO_LINE_TYPES_TL to PO_LINE_TYPES_B on LINE_TYPE_ID to resolve the translated DESCRIPTION for a given line type.
  • Filtering by LANGUAGE = USERENV('LANG') (or the session NLS language) to return the correct translation.
  • Listing all available line types with their descriptions for configuration or validation reports.
  • Auditing which line types have translations defined, using SOURCE_LANG to detect untranslated entries.

A representative query joins the two tables on LINE_TYPE_ID and restricts by the active language to present the line type code alongside its description.

Related Objects

The most significant related objects include:

  • PO_LINE_TYPES_B — The base (language-independent) line type table; joined on LINE_TYPE_ID.
  • PO_LINE_TYPES_VL — The translated view exposing the current-language DESCRIPTION over the base and _TL tables.
  • PO_LINES_ALL — Purchase order lines referencing a line type via LINE_TYPE_ID.
  • PO_LINE_LOCATIONS_ALL — Shipment/line location detail indirectly dependent on line type behavior.
  • PO_HEADERS_ALL — Document headers whose line defaults derive from line type configuration.
  • PO_DOCUMENT_TYPES_ALL — Document types that constrain permissible line types.

These relationships make PO_LINE_TYPES_TL a small but essential reference table underpinning purchasing document classification and localization.