Search Results po_document_types_all_tl_pk

Overview

PO_DOCUMENT_TYPES_ALL_TL is the translation (TL) table for purchasing document types in Oracle E-Business Suite, owned by the PO (Purchasing) schema. In Oracle EBS, "document type" is the controlling classification that determines which purchasing document a given record represents — a standard purchase order, a blanket purchase agreement, a contract, a quotation, and so on. The base table PO_DOCUMENT_TYPES_ALL_B stores the language-independent definition, while PO_DOCUMENT_TYPES_ALL_TL stores the language-dependent, translatable attributes for each document type. This separation lets Oracle EBS deploy in multilingual environments: the same document type carries distinct display names per installed language, driven by the LANGUAGE column.

Under the heuristic Data Vault classification supplied in the metadata, this object is treated as standalone. In Data Vault modeling terms, that means it is not modeled as a pure hub, link, or satellite by the mined foreign-key structure, but rather functions as a reference or lookup table accessed independently. The translated type name is the property most consumers need, so the table is best understood as a language-dependent descriptive attribute set for purchasing document types.

Key Information Stored

The table contains twelve documented columns. The most operationally significant are:

• DOCUMENT_TYPE_CODE — the business identifier of the purchasing document type (for example, the code distinguishing a standard purchase order from a blanket agreement). It is part of the primary key and a leading column of the unique index.
• DOCUMENT_SUBTYPE — the subtype that narrows the document type category further; this is critical in releases where purchasing functionality is subclassified. It is also part of the primary key.
• LANGUAGE — the installed language for which this translated row applies (for example, US, ZHS, or D). It is the third component of the primary key and the column that gives this table its "TL" behavior.
• TYPE_NAME — the translated, user-visible name of the document type. This is the value typically surfaced in list-of-values and reports.
• SOURCE_LANG — the language in which the source (base) name was originally entered, used by the translation framework.
• ORG_ID — the operating unit or organization identifier, supporting multi-org access to document type definitions.
• ZD_EDITION_NAME — the edition identifier used by Oracle's editioning and online patching infrastructure, essential in 12.2.x.
• Standard WHO/audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — record row provenance and are used by concurrent programs, change tracking, and audits.

The surrogate-style primary key is PO_DOCUMENT_TYPES_ALL_TL_PK, defined on (DOCUMENT_SUBTYPE, LANGUAGE, DOCUMENT_TYPE_CODE). The documented business-key candidate is the unique index PO_DOCUMENT_TYPES_ALL_TL_U1, defined on (DOCUMENT_TYPE_CODE, DOCUMENT_SUBTYPE, ORG_ID, LANGUAGE, ZD_EDITION_NAME). Queries that must return exactly one row per document type and language should align predicates with U1 to guarantee uniqueness and index access.

Common Use Cases and Queries

The dominant use case is resolving a document type code to its translated display name for a specific language, typically inside a report, list of values, or integration extract. A representative query joins the translation table and restricts to the session or target language:

• SELECT document_type_code, document_subtype, type_name FROM po_document_types_all_tl WHERE language = USERENV('LANG') AND org_id = :org_id;
• Reporting on purchasing document volumes grouped by document type name, joining PO_HEADERS_ALL or PO_DOCUMENT_TYPES_ALL_B to the translated name for a user-friendly label.
• Multilingual data validation: comparing TYPE_NAME across languages for a single DOCUMENT_TYPE_CODE to verify translations are complete and consistent.
• Operating-unit scoped lookups using ORG_ID to restrict the document types visible to a given organization.
• 12.2.x edition-aware extracts that filter on ZD_EDITION_NAME to avoid reading obsolete editioned rows during online patching.

Because translation rows are keyed by language, always filter LANGUAGE explicitly; omitting it can multiply rows in joins with base tables.

Related Objects

The most significant objects that relate to or depend on this table include:

• PO_DOCUMENT_TYPES_ALL_B — the base, language-independent table with which the TL table shares the document type key.
• PO_DOCUMENT_TYPES_ALL_V — the language view that joins the base and translation tables for display.
• PO_HEADERS_ALL — purchasing document headers whose TYPE_LOOKUP_CODE / document type is described by the base row that this TL table translates.
• PO_DOCUMENT_TYPES and related purchasing lookup views — reference the same type codes for validation.
• FND_LANGUAGES — the language master that supplies valid values for LANGUAGE and SOURCE_LANG.
• The Purchasing document creation APIs and concurrent programs that consult the base table and use the TL table to render names in the user's language.

Together these objects form the reference backbone for identifying and labeling purchasing document types across Oracle EBS 12.1.1 and 12.2.2.