Search Results okc_bus_doc_types_tl_pk

Overview

OKC_BUS_DOC_TYPES_TL is a core translation table within the Oracle EBS Contracts Core (OKC) module. It stores the translatable attributes of Business Document Types, which define the categories of documents that can be generated, authored, or managed within the Oracle Contracts suite, including contract templates, contract terms, and related authoring artifacts. Because Oracle EBS supports multiple languages through the Multi-Language Support (MLS) architecture, the base definition of a business document type is held in a primary table while language-specific descriptive text is stored in this companion _TL table. Each row represents one language rendering of a given document type, keyed by the combination of document type identifier and language code.

The ETRM metadata classifies this object heuristically as a standalone Data Vault entity. In Data Vault modeling terms, this suggests treating the object as an independent structure rather than a dependent hub or link, since the documented FK/PK relationship analysis surfaces no foreign key dependencies to other tables. Practically, the table functions as a language-dependent descriptive satellite layered over the document type business key.

Key Information Stored

The table is composed of 11 documented columns. The most significant include:

• DOCUMENT_TYPE — identifies the business document type; part of the primary key and the business-key candidate.
• LANGUAGE — the language code for the translatable row; the second component of the primary key and of both unique indexes.
• SOURCE_LANG — the source language from which the translation originated.
• NAME — the translated display name of the document type; part of unique index OKC_BUS_DOC_TYPES_TL_U2.
• DESCRIPTION — the translated descriptive text associated with the document type.
• ZD_EDITION_NAME — the editioning column supporting Oracle EBS Online Patching (adopted in 12.2), included in both unique indexes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record creation and modification.

The surrogate/primary key is documented as OKC_BUD_DOC_TYPES_TL_PK (DOCUMENT_TYPE, LANGUAGE), with a secondary variant OKC_BUS_DOC_TYPES_TL_PK also cited in the metadata. Business-key candidates are represented by unique indexes OKC_BUS_DOC_TYPES_TL_U1 (DOCUMENT_TYPE, LANGUAGE, ZD_EDITION_NAME) and OKC_BUS_DOC_TYPES_TL_U2 (LANGUAGE, NAME, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical usage centers on retrieving language-specific names and descriptions for document types in reports, LOVs, and integration extracts. A common pattern joins the translation table to its base table on DOCUMENT_TYPE while restricting LANGUAGE to the session or reporting language:

• Reporting the localized name of each document type for a given language.
• Auditing translations to detect missing or stale language rows for a document type.
• Extracting bilingual name/description pairs for downstream document generation.
• Validating that NAME values are unique per language (index U2).

Representative SQL: SELECT document_type, language, name, description FROM okc.okc_bus_doc_types_tl WHERE language = USERENV('LANG') AND zd_edition_name = 'SET1'; In 12.2 environments, always include ZD_EDITION_NAME to return rows from the correct patching edition.

Related Objects

The metadata identifies no foreign keys, so related objects are inferred from the business document type model rather than documented FK relationships. The most significant dependencies include:

• OKC_BUS_DOC_TYPES_B — the base (non-translatable) table joined on DOCUMENT_TYPE.
• OKC_BUS_DOC_TYPES_VL — the MLS view exposing translated and base columns via DOCUMENT_TYPE and LANGUAGE.
• OKC_BUS_DOC_TYPE_RELS — relationships between document types.
• OKC_BUS_DOC_TYPE_USES — usage associations for document types.
• OKC_BUS_DOC_TYPE_GROUPS — grouping definitions referencing document types.
• OKC_DOCUMENTS / OKC_DOC_TYPES — runtime document instances that reference the type.

These joins typically key on DOCUMENT_TYPE combined with LANGUAGE for translation-aware retrieval.