Results for “okc_folders_all_tl”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_FOLDERS_ALL_TL is the translation table for Oracle Contracts Core folders in Oracle E-Business Suite 12.1.1 and 12.2.2. The OKC schema organizes contract-related content into folders, which act as logical groupings for clauses, templates, deliverables, and other contract artifacts. OKC_FOLDERS_ALL_TL stores the language-dependent (translatable) attributes of those folders — primarily the folder name and description — while the base table OKC_FOLDERS_ALL holds the language-independent columns. The "_TL" suffix is the standard EBS convention for a translation entity that carries one row per base record per installed or defined language.

The table is owned by OKC and is documented as VALID in the ETRM 12.2.2 physical schema with 10 columns. Under a heuristic Data Vault classification mined from the foreign-key structure, this object is modeled as standalone. Because it has no outgoing foreign keys to other tables and instead hangs off the base folder entity keyed by FOLDER_ID and LANGUAGE, a Data Vault modeler would more naturally treat it as a satellite attached to the folder hub, carrying descriptive, language-qualified attributes. This classification is a modeling suggestion only, not a functional constraint in EBS.

Key Information Stored

The table's contents are best understood as the multilingual descriptive layer of a contract folder. The most important columns are:

  • FOLDER_ID — the surrogate identifier of the parent folder, shared with OKC_FOLDERS_ALL and forming the leading column of the primary key.
  • LANGUAGE — the language code for this translated row, the trailing column of the primary key and unique index.
  • SOURCE_LANG — the language from which the row was derived, supporting the standard EBS translation-maintenance model (usually the base language, such as US).
  • FOLDER_NAME — the display name of the folder as presented to users in that language; this is the principal business attribute used in list-of-values and search.
  • DESCRIPTION — the longer free-text explanation of the folder's purpose or scope.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "Who" audit columns that record insert and update ownership and timing.

The primary key is OKC_FOLDERS_ALL_TL_PK1 on (FOLDER_ID, LANGUAGE). The unique index OKC_FOLDERS_ALL_TL_U1 covers the same (FOLDER_ID, LANGUAGE) pair and is the documented business-key candidate, guaranteeing exactly one translated name and description per folder per language. The surrogate key remains FOLDER_ID when combined with the language, since the folder identifier alone is not unique across languages in this table.

Common Use Cases and Queries

The most frequent access pattern is joining the translation table to its base table to resolve a folder name for a specific session language. A typical query joins on FOLDER_ID and filters by LANGUAGE. Reporting layers often use NVL or a fallback join so that a missing translation returns the base-language name rather than null. Example pattern:

  • SELECT b.folder_id, t.folder_name, t.description FROM okc_folders_all b, okc_folders_all_tl t WHERE b.folder_id = t.folder_id AND t.language = USERENV('LANG').
  • Translation-coverage audits: count base folders that lack a row in the _TL table for a target language to find untranslated folders.
  • Concurrent-program-driven translation maintenance, where SOURCE_LANG is used to identify rows copied from the base language.
  • Contract authoring and template setup reports that list available folders by localized name for users in non-English environments.

Related Objects

  • OKC_FOLDERS_ALL — the base table holding language-independent folder attributes; joined on FOLDER_ID.
  • OKC_FOLDERS_ALL_TL_PK1 / OKC_FOLDERS_ALL_TL_U1 — the primary key and unique index enforcing one translation per folder per language.
  • OKC_FOLDERS_B and OKC_FOLDERS_TL variants used within older or alternate folder structures, depending on the EBS release level.
  • OKC_FOLDER_ITEMS — associates folders with the contract clauses and templates they contain, referenced via the folder identifier.
  • FND_LANGUAGES — provides the valid values for LANGUAGE and SOURCE_LANG.
  • OKC_CONTRACTS_ALL and clause/template base tables that consume folders during contract authoring.

Together these objects support folder definition, translation, and consumption across the Contracts Core module.