Search Results okc_rep_contact_roles_tl




Overview
Explore in AI Chat

Overview

OKC_REP_CONTACT_ROLES_TL is the translation table for Contact Roles within the Oracle Contracts Core (OKC) module. In Oracle E-Business Suite 12.1.1 and 12.2.2, contact roles define the functional capacity in which a party or contact participates on a contract — for example, a signatory, a technical contact, or a billing contact. Because Oracle EBS is a multi-language application, every user-facing role definition requires a translated name and description per installed language. OKC_REP_CONTACT_ROLES_TL fulfills that requirement by storing the language-specific text associated with each contact role defined in the base OKC_REP_CONTACT_ROLES_B table.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling context. This suggests it be treated as an independent satellite-like structure rather than a hub or link, since it carries descriptive, language-dependent attributes keyed by the parent entity plus language, and does not itself act as a junction between two business entities.

Key Information Stored

The table is documented with 11 columns, of which the following are most significant:

  • CONTACT_ROLE_ID — Surrogate identifier inherited from the base contact roles entity; combined with LANGUAGE it forms the primary key of this translation table.
  • LANGUAGE — The language code for the translated row, typically in Oracle NLS format (for example, US or DE). Part of the composite primary key.
  • NAME — The translated, user-visible name of the contact role displayed in Contracts forms, lists of values, and reports.
  • DESCRIPTION — The translated descriptive text elaborating the purpose or usage of the contact role.
  • SOURCE_LANG — Indicates the source language from which the translation was derived, supporting Oracle's translation framework.
  • ZD_EDITION_NAME — Editioning column introduced in the 12.2 online patching architecture, identifying the edition in which the row is visible.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle WHO columns capturing audit and concurrency information.

Two unique indexes are documented as business-key candidates: OKC_REP_CONTACT_ROLES_TL_U1 on (CONTACT_ROLE_ID, LANGUAGE, ZD_EDITION_NAME) and OKC_REP_CONTACT_ROLES_TL_U2 on (NAME, LANGUAGE, ZD_EDITION_NAME). The U1 index enforces uniqueness of the translation per role and language; U2 enforces uniqueness of the translated name within a language, preventing ambiguous duplicate role names.

Common Use Cases and Queries

Reporting and integration scenarios typically join this table to the base contact roles table to resolve localized labels for a specified session language. A representative query pattern retrieves role names for the current environment language:

  • Join OKC_REP_CONTACT_ROLES_B to OKC_REP_CONTACT_ROLES_TL on CONTACT_ROLE_ID and filter LANGUAGE = userenv('LANG') to obtain display names for LOVs or extracts.
  • Query by NAME to locate a CONTACT_ROLE_ID when integrating external systems that reference roles by descriptive name rather than identifier.
  • Audit translation completeness by comparing distinct CONTACT_ROLE_ID values in the base table against those present in the TL table for each installed language.
  • Bulk maintenance scripts that insert or update translated NAME and DESCRIPTION values, always populating SOURCE_LANG and the WHO audit columns.

Related Objects

  • OKC_REP_CONTACT_ROLES_B — The base (non-translated) contact roles table; joined on CONTACT_ROLE_ID, supplying the language-independent definition.
  • OKC_REP_CONTACTS — Associations linking contacts to roles; references CONTACT_ROLE_ID to indicate which role a contact fulfills.
  • OKC_REP_CONTACT_ROLES_VL — The MLS view layered over the _B and _TL tables, exposing translated columns for forms and reports.
  • OKC_REP_CONTACT_ROLES_TL_U1 / U2 — Unique indexes enforcing the documented business keys.
  • FND_LANGUAGES — Reference for valid LANGUAGE codes.