Search Results po_line_types_tl_u2

Overview

PO.PO_LINE_TYPES_TL is the translation table for Purchasing document line types in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores multilingual descriptions of the line types defined in the Purchasing module, allowing line type names and their descriptive text to be presented in each installed language. The base (untranslated) definition resides in PO.PO_LINE_TYPES_B, while this table supplies the language-specific DESCRIPTION and LINE_TYPE values keyed by LINE_TYPE_ID and LANGUAGE.

The object is seeded as reference data and is stored in the APPS_TS_SEED tablespace, reflecting its role as setup/seed content rather than transactional data. Because its rows are essentially attribute descriptions attached to a stable business entity (the line type), a Data Vault modeling heuristic would classify PO_LINE_TYPES_TL as a satellite, with PO_LINE_TYPES_B acting as the parent hub. The table does not reference any other database object through foreign keys, which is consistent with the metadata's standalone classification.

Key Information Stored

The table carries eleven documented columns. The most significant are:

• LINE_TYPE_ID — Numeric surrogate identifier for the line type; forms part of the primary key PO_LINE_TYPES_TL_PK and is a business-key candidate via PO_LINE_TYPES_TL_U1.
• LANGUAGE — The target language of the translation; paired with LINE_TYPE_ID in the primary key.
• SOURCE_LANG — The language from which the translation was derived.
• DESCRIPTION — Translated descriptive text (240 characters) for the line type.
• LINE_TYPE — The translated document line type name (25 characters), also a business-key candidate via PO_LINE_TYPES_TL_U2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard WHO audit columns capturing creation and modification metadata, with LAST_UPDATED_BY and CREATED_BY referencing FND_USER.USER_ID and LAST_UPDATE_LOGIN referencing FND_LOGINS.LOGIN_ID.
• ZD_EDITION_NAME — Present in the 12.2.2 physical schema, supporting edition-based definition tracking and included in both unique indexes.

The surrogate primary key is PO_LINE_TYPES_TL_PK (LANGUAGE, LINE_TYPE_ID), while PO_LINE_TYPES_TL_U1 (LINE_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) and PO_LINE_TYPES_TL_U2 (LINE_TYPE, LANGUAGE, ZD_EDITION_NAME) represent the documented business-key candidates.

Common Use Cases and Queries

Typical uses include multilingual reporting, validation of translated line type names, and joins to PO_LINE_TYPES_B for complete line type definitions. A representative pattern:

• SELECT lt.LINE_TYPE_ID, lt.LINE_TYPE, lt.DESCRIPTION FROM PO.PO_LINE_TYPES_TL lt WHERE lt.LANGUAGE = USERENV('LANG') — retrieve line type descriptions for the session language.
• Joining to PO_LINE_TYPES_B on LINE_TYPE_ID to pair translated text with base attributes.
• Auditing translation coverage by counting rows per LANGUAGE against SOURCE_LANG.
• Reporting on creation/update activity using the WHO columns for change-tracking.

Related Objects

• PO.PO_LINE_TYPES_B — the base table holding the language-independent line type definition, joined on LINE_TYPE_ID.
• PO.PO_LINE_TYPES_TL (view) — an APPS-layer view over this translation data, referenced in the dependency listing.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.
• PO_LINES_ALL / PO_HEADERS_ALL — transactional Purchasing tables whose line type identifiers resolve to descriptions held here for display and reporting.