Search Results okc_bus_doc_types_tl_u2

Overview

OKC.OKC_BUS_DOC_TYPES_TL is the translation (TL) table for Oracle E-Business Suite business document types used by the Contracts (OKC) module. It stores the language-dependent attributes — chiefly the display name and the long description — for each business document type defined in OKC. Every multilingual (MLS) entity in EBS is implemented as a pair of tables: a base table holding the language-independent definition, and a "_TL" table holding one row per installed language for each base record. OKC_BUS_DOC_TYPES_TL is the latter. It resides in the APPS_TS_SEED tablespace, which indicates it holds reference and seed data rather than high-volume transactional data.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. This is a reasonable suggestion: the table carries descriptive, attribute-level content keyed by DOCUMENT_TYPE and LANGUAGE, and is not itself documented as a link between two business hubs. In practice it behaves like a satellite attached to the DOCUMENT_TYPE business key, with LANGUAGE acting as a secondary discriminator for the translated text.

Key Information Stored

The table is documented with 11 columns. The most significant are listed below.

• DOCUMENT_TYPE (VARCHAR2(30), mandatory) — the code that identifies the business document type. This is the business key inherited from the base table.
• LANGUAGE (VARCHAR2(12), mandatory) — the standard MLS language column identifying which installed language this row translates into.
• SOURCE_LANG (VARCHAR2(12)) — the standard MLS source-language column, recording the language the row was originally entered in.
• NAME (VARCHAR2(150)) — the translated name of the document type, the primary user-facing attribute of the row.
• DESCRIPTION (VARCHAR2(4000)) — the user-entered, translated description of the document type.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "who" audit columns present on virtually every table.
• ZD_EDITION_NAME (VARCHAR2(30)) — the editioning support column used in the EBS 12.2 online patching (adop) architecture, allowing multiple editions of the row to coexist during a patch cycle.

The documented primary key is OKC_BUD_DOC_TYPES_TL_PK (DOCUMENT_TYPE, LANGUAGE) — note the documented PK name appears with a "BUD" spelling, distinct from the "BUS" used in the table and index names. Two business-key candidates are recorded: the unique index OKC_BUS_DOC_TYPES_TL_U1 (DOCUMENT_TYPE, LANGUAGE, ZD_EDITION_NAME) — the index referenced in the user's search term, which enforces uniqueness of a document type per language per edition — and OKC_BUS_DOC_TYPES_TL_U2 (LANGUAGE, NAME, ZD_EDITION_NAME), which enforces that translated names are unique within a language.

Common Use Cases and Queries

Because translated names must be surfaced to end users in their session language, this table is most commonly accessed through MLS views or joins keyed on DOCUMENT_TYPE with a language filter. A typical listing query is shown below.

SELECT DOCUMENT_TYPE, NAME, DESCRIPTION
FROM OKC.OKC_BUS_DOC_TYPES_TL
WHERE LANGUAGE = USERENV('LANG');

Reporting scenarios include generating a bilingual catalogue of document types (self-joining the table on DOCUMENT_TYPE across two LANGUAGE values), auditing which types have missing translations (comparing base rows to _TL rows), and reconciling NAME collisions flagged by OKC_BUS_DOC_TYPES_TL_U2. Data-migration or conversion scripts frequently insert directly into this table after establishing the base record, making the U1 and U2 constraints the critical validation points when validating a load.

Related Objects

The metadata records no outgoing references from this table and shows that it is referenced by OKC_OKC_BUS_DOC_TYPES_TL# (the editioning/backing object). The natural join partners in the EBS data model are the base table OKC_BUS_DOC_TYPES_B (or its documented base equivalent), joined on DOCUMENT_TYPE; the OKC Contracts tables such as OKC_K_HEADERS that carry a document type reference; the OKC business document definition and template tables that consume the type code; and the FND_LANGUAGES lookup for resolving LANGUAGE codes to display names. Reporting views over business document setup typically union or join the _B and _TL tables to present a language-complete picture. Because the documented dependency list is narrow, any additional relationships should be confirmed against the actual application schema rather than assumed.