Search Results okc_time_code_units_tl_pk




Overview
Explore in AI Chat

Overview

OKC_TIME_CODE_UNITS_TL is a Multi-Lingual Support (MLS) translation table owned by the OKC schema within the Contracts Core (OKC) product of Oracle E-Business Suite. The table stores the translatable descriptive columns associated with the base table OKC_TIME_CODE_UNITS_B, following Oracle Applications MLS standards. In Oracle EBS 12.1.1 and 12.2.2, the OKC_TIME_CODE_UNITS_B / OKC_TIME_CODE_UNITS_TL pair defines the valid combinations of Unit of Measure (UOM) and Time Code Element (TCE) used throughout contract authoring, pricing, and line-level time-qualified terms.

The base table carries the language-independent key and flag columns, while this companion table supplies the language-specific text attributes—descriptions, comments, and short descriptions—keyed by language code. The object is marked VALID with a documented physical schema of 14 columns. From a Data Vault modeling perspective, the mined relationship structure classifies this object heuristically as standalone; a modeling suggestion would be to treat it as a satellite-like descriptor table hanging off its base entity, since it holds descriptive attributes keyed to the base business key plus LANGUAGE rather than representing independent relationships among business entities.

Key Information Stored

The table is keyed by a composite primary key named OKC_TIME_CODE_UNITS_TL_PK over the columns UOM_CODE, TCE_CODE, and LANGUAGE. A unique index, OKC_TIME_CODE_UNITS_TL_U1, covers the same three columns and confirms this trio as the business-key candidate for row uniqueness across translations.

  • UOM_CODE – Unit of Measure identifier; part of the composite business key linking back to OKC_TIME_CODE_UNITS_B.
  • TCE_CODE – Time Code Element identifier; the second business-key component.
  • LANGUAGE – The language of the translated row, per MLS convention.
  • SOURCE_LANG – Indicates the language in which the base (non-translated) record was originally entered.
  • SFWT_FLAG – The "Seed/Fix/What/Test" style translation-completeness flag used by the Oracle translation framework to indicate whether a row has been translated relative to its source.
  • SHORT_DESCRIPTION – Concise display text for the UOM/TCE combination, commonly shown in LOVs and flexfields.
  • DESCRIPTION – Full descriptive text for the time code unit combination.
  • COMMENTS – Free-form supplemental notes.
  • SECURITY_GROUP_ID – Multi-tenant / security grouping reference; documented FK to FND_SECURITY_GROUPS.
  • Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture row audit history in standard EBS fashion.

The surrogate-vs-business distinction matters: the PK (UOM_CODE, TCE_CODE, LANGUAGE) is effectively the natural business key plus language discriminator, with no separate sequence-generated surrogate column documented.

Common Use Cases and Queries

Typical usage includes populating LOVs for time-code unit selection during contract entry, generating translated documentation, and supporting multilingual reporting of contract terms.

  • Resolving translated descriptions: join the base and translation tables on UOM_CODE and TCE_CODE and filter by LANGUAGE.
  • Finding missing translations: query TL rows where SFWT_FLAG does not equal 'Y' or where LANGUAGE = 'US' only.
  • Listing all descriptions for a given UOM/TCE pair across languages for a translation status report.

A representative query pattern joins OKC_TIME_CODE_UNITS_B b to OKC_TIME_CODE_UNITS_TL t on b.UOM_CODE = t.UOM_CODE AND b.TCE_CODE = t.TCE_CODE WHERE t.LANGUAGE = USERENV('LANG') to return language-appropriate descriptions.

Related Objects

The most significant related objects, based on documented FK/PK relationship data, include:

  • OKC_TIME_CODE_UNITS_B – the base (non-translatable) companion table, joined via UOM_CODE and TCE_CODE.
  • FND_SECURITY_GROUPS – referenced by SECURITY_GROUP_ID.
  • OKC_TIME_CODE_UNITS_TL_PK / OKC_TIME_CODE_UNITS_TL_U1 – the primary key and unique index enforcing the composite business key.
  • OKC Contracts Core – the owning product module and its pricing and clause-time attribute logic.
  • FND_LANGUAGES – the standard EBS language reference underlying the LANGUAGE column.