Search Results po_document_types_all_tl_u1

Overview

PO.PO_DOCUMENT_TYPES_ALL_TL is a translation (TL) table in the Oracle Purchasing (PO) schema that stores language-specific, displayable names for the document types and subtypes defined in Oracle E-Business Suite. The base (non-translated) definitions reside in PO_DOCUMENT_TYPES_ALL_B; this TL companion holds the rendered TYPE_NAME for each supported LANGUAGE, allowing the same purchasing document type — such as a standard purchase order, blanket agreement, or quotation — to present a localized label in the user interface and in reporting output. The object is stored in the APPS_TS_SEED tablespace, reflecting its role as seed/setup reference data rather than transactional data.

From a dimensional modeling perspective, the mined relationship data classifies this object as standalone, meaning it has no documented foreign-key dependencies on other tables and no tables depending on it through enforced constraints. In Data Vault terms this is best modeled as a satellite attached to a document-type hub, since it carries descriptive, language-dependent attributes (TYPE_NAME) keyed by the document type and subtype rather than representing an independent business entity or a many-to-many link. This is a modeling suggestion only; Oracle does not itself publish Data Vault structures.

Key Information Stored

The table's identity and descriptive columns are the most operationally significant:

• DOCUMENT_TYPE_CODE (VARCHAR2, 25) — the code identifying the purchasing document type; part of the primary key and of the unique business-key index.
• DOCUMENT_SUBTYPE (VARCHAR2, 25) — the subtype that further qualifies the document type; also part of the primary key.
• ORG_ID (NUMBER) — the operating unit / organization identifier, enabling organization-specific translation rows.
• LANGUAGE (VARCHAR2) — the target language of the translation; part of the primary key.
• SOURCE_LANG (VARCHAR2) — the language from which the translation was derived.
• TYPE_NAME (VARCHAR2, 80) — the translated display name of the document type, the primary payload of this table.
• ZD_EDITION_NAME — the editioning column associated with the 12.2 online patching / editioning model.
• Standard WHO audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — which track row provenance and change history.

The surrogate primary key is PO_DOCUMENT_TYPES_ALL_TL_PK on (DOCUMENT_SUBTYPE, LANGUAGE, DOCUMENT_TYPE_CODE). The documented unique index PO_DOCUMENT_TYPES_ALL_TL_U1 — the object named in the user's search — is the business-key candidate on (DOCUMENT_TYPE_CODE, DOCUMENT_SUBTYPE, ORG_ID, LANGUAGE, ZD_EDITION_NAME), which legally guarantees a single translation per document type, subtype, organization, language, and edition. Note that the U1 index extends the primary key with ORG_ID and ZD_EDITION_NAME, distinguishing it as the fuller business-key constraint.

Common Use Cases and Queries

Typical usage centers on joining this TL table to its base companion to return localized labels, and on validating that translations exist for all required languages. A representative query retrieves the localized name for all document types:

• SELECT t.document_type_code, t.document_subtype, t.language, t.type_name FROM po.po_document_types_all_tl t WHERE t.language = USERENV('LANG') ORDER BY t.document_type_code;
• Join to the base table to compare base and translated names: SELECT b.document_type_code, b.document_subtype, t.type_name FROM po.po_document_types_all_b b, po.po_document_types_all_tl t WHERE b.document_type_code = t.document_type_code AND b.document_subtype = t.document_subtype AND t.language = 'US';
• Reporting use cases commonly include listing available purchasing document types per operating unit, auditing missing translations across languages, and driving LOV/picklist displays in custom concurrent programs or reports.

Because the table is seed data, direct DML is generally discouraged; translations should be maintained through the application's Translation / setup screens to keep the base, TL, and TL_U1 structures synchronized.

Related Objects

The metadata records that PO_DOCUMENT_TYPES_ALL_TL references no database object, and is referenced by the following application objects:

• PO_DOCUMENT_TYPES_ALL_TL (APPS synonym/view) — the runtime access point over this table.
• PO_DOCUMENT_TYPES_TL — the companion translated view over document-type definitions.
• PO.PO_DOCUMENT_TYPES_ALL_B — the base-language table holding the non-translated definitions against which the TL rows join on DOCUMENT_TYPE_CODE and DOCUMENT_SUBTYPE.
• Oracle Purchasing document entry and setup forms/LOVs that consume translated document type names via these views.

These references define the practical join surface for reporting: always pair PO_DOCUMENT_TYPES_ALL_TL with its base table on DOCUMENT_TYPE_CODE and DOCUMENT_SUBTYPE, filtering by LANGUAGE and ORG_ID as required.