Results for “okc_number_schemes_tl”

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

Overview

OKC_NUMBER_SCHEMES_TL is the translation table for numbering schemes within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, documented as VALID in the OKC schema for releases 12.1.1 and 12.2.2. Its stated purpose is to hold language-specific translations of numbering scheme definitions, allowing contract administrators in multilingual deployments to view scheme names and descriptions in their session language. The table carries exactly ten documented columns and pairs with its base (non-translated) counterpart to deliver the standard Oracle multi-language architecture: one row per scheme per installed language.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is marked standalone. From a modeling perspective, this classification suggests the table functions as an independent reference or descriptor set rather than a true hub or link, though its composite key over NUM_SCHEME_ID and LANGUAGE means it behaves in practice as a satellite-like translation store keyed to a parent scheme identifier. Modelers should treat the standalone tag as a suggestion derived from FK absence, not as a declaration that the object has no logical parent.

Key Information Stored

Ten columns are documented for OKC_NUMBER_SCHEMES_TL, of which the most significant are:

• NUM_SCHEME_ID — Surrogate-style identifier of the numbering scheme. Together with LANGUAGE it forms the primary key OKC_NUMBER_SCHEMES_TL_PK.
• LANGUAGE — The language code for the translated row. Also part of the composite primary key and of the unique index OKC_NUMBER_SCHEMES_TL_U1.
• SOURCE_LANG — The source language from which the translation was derived, used by the translation framework to track origin and detect staleness.
• SCHEME_NAME — The translated display name of the numbering scheme. This column is a documented business-key candidate, forming unique index OKC_NUMBER_SCHEMES_TL_U1 (SCHEME_NAME, LANGUAGE).
• DESCRIPTION — Free-text translated description of the scheme's purpose or pattern.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle WHO columns providing audit and concurrency context for each translation row.

Note the distinction between the surrogate primary key path (NUM_SCHEME_ID, LANGUAGE) and the business-key candidate (SCHEME_NAME, LANGUAGE). Application logic typically resolves a scheme by its numeric ID, while user-facing lookups and data-quality checks may rely on the uniqueness of the translated name per language.

Common Use Cases and Queries

Typical scenarios include presenting contract numbering schemes in the user's language, auditing translation completeness across installed languages, and reporting on scheme metadata for contract administration. Because the table is language-keyed, queries normally join to the base table on NUM_SCHEME_ID and filter by LANGUAGE.

• Retrieve a translated scheme name: SELECT scheme_name, description FROM okc_number_schemes_tl WHERE num_scheme_id = :id AND language = USERENV('LANG');
• Detect missing translations: compare base-table scheme IDs against TL rows for a given LANGUAGE using an outer join on NUM_SCHEME_ID.
• Validate business-key uniqueness: query on SCHEME_NAME and LANGUAGE to confirm no duplicate names exist within a language.
• Audit recent translation changes using LAST_UPDATED_BY and LAST_UPDATE_DATE for compliance reporting.

Related Objects

The metadata classifies this object as standalone with no documented foreign keys. Nonetheless, the following are the most significant related objects by logical dependency:

• OKC_NUMBER_SCHEMES_B (or equivalent base table) — the non-translated parent keyed by NUM_SCHEME_ID; the standard join partner for TL resolution.
• OKC_NUMBER_SCHEMES_TL_PK — composite primary key index on NUM_SCHEME_ID and LANGUAGE.
• OKC_NUMBER_SCHEMES_TL_U1 — unique index on SCHEME_NAME and LANGUAGE, enforcing business-key integrity.
• OKC Contract Numbering APIs — PL/SQL packages that consume scheme identifiers when generating contract numbers, resolving translated names for display.
• FND_LANGUAGES — language reference used to validate the LANGUAGE and SOURCE_LANG values.
• FND_USER — referenced indirectly through CREATED_BY and LAST_UPDATED_BY for audit attribution.