Search Results okc_statuses_tl_u1

Overview

OKC.OKC_STATUSES_TL is the translatable (MLS) child table of OKC_STATUSES_B within the Oracle Contracts (OKC) module of Oracle E-Business Suite. It stores language-specific text for contract status codes, supplying the short meaning and free-format description associated with each status defined in the base table. Rows in this table are keyed by code and language, allowing the same contract status to be presented in multiple installed languages while the underlying business definition remains centralized in OKC_STATUSES_B.

Under the heuristic Data Vault classification derived from the documented foreign key structure, this table is modeled as a satellite. It hangs off the OKC_STATUSES_B business key (CODE) and holds descriptive, language-dependent attributes (MEANING, DESCRIPTION) that change over time. The single documented foreign key — SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS — is a hosting/security attribute rather than a true entity relationship, which reinforces the satellite classification. The index OKC_STATUSES_TL_U2 (MEANING, LANGUAGE, ZD_EDITION_NAME) is the composite that the user query term "okc_statuses_tl_u2" refers to: it enforces uniqueness on the translated meaning per language and edition.

Key Information Stored

The table contains thirteen documented columns. The most operationally significant are:

• CODE — VARCHAR2(30). The status code as defined in FND_LOOKUP_VALUES; part of the primary key OKC_STATUSES_TL_PK (CODE, LANGUAGE) and of the unique index OKC_STATUSES_TL_U1 (CODE, LANGUAGE, ZD_EDITION_NAME).
• LANGUAGE — VARCHAR2(12). Standard MLS discriminator identifying the language of the row.
• SOURCE_LANG — VARCHAR2(12). Standard MLS column indicating the installation language from which the row was derived.
• MEANING — VARCHAR2(90). The short, user-facing meaning of the status; it forms the business-key candidate captured by OKC_STATUSES_TL_U2 (MEANING, LANGUAGE, ZD_EDITION_NAME).
• DESCRIPTION — VARCHAR2(1995). Free-format user-entered text describing the status in the given language.
• SFWT_FLAG — Marks a value changed in another language; documented as not fully implemented in 11i.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns for audit and concurrency.
• SECURITY_GROUP_ID — NUMBER, used in hosted environments; references FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — VARCHAR2(30). Editioning column incorporated into both unique indexes to support online patching and multi-edition deployments in 12.2.2.

The primary key is the composite surrogate (CODE, LANGUAGE); the true business keys are the two documented unique indexes, U1 and U2, both of which include ZD_EDITION_NAME.

Common Use Cases and Queries

Because this is a seed/reference table stored in the APPS_TS_SEED tablespace, it is primarily consulted for reporting, prompt lists, and validation of contract status values. Typical usage patterns include:

• Retrieving the translated label for a given status code in a specific language:

  SELECT meaning, description
  FROM   okc.okc_statuses_tl
  WHERE  code = :code
  AND    language = USERENV('LANG');

• Listing all statuses with their English meanings for a lookup LOV:

  SELECT code, meaning
  FROM   okc.okc_statuses_tl
  WHERE  language = 'US'
  ORDER BY meaning;

• Detecting duplicate or missing translations by joining against OKC_STATUSES_B to find codes lacking a row for a required language.
• Investigating index behavior or contention — the term "okc_statuses_tl_u2" is frequently searched when unique-constraint violations occur on MEANING/LANGUAGE during setup or patch application.

The companion query text provided in the ETRM metadata (listing all thirteen columns) is the standard access path for extract and audit reports.

Related Objects

The following objects are most relevant when working with OKC_OKC_STATUSES_TL:

• OKC.OKC_STATUSES_B — The base (non-translatable) table holding the canonical status definitions. Join on CODE. The _TL row inherits its business context from this parent.
• OKC_STATUSES_TL# — The documented dependent object referenced by this table.
• FND_LOOKUP_VALUES — The source of the CODE value, per the column comment; joins on LOOKUP_CODE and LOOKUP_TYPE.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for hosted/multi-tenant installations.
• OKC_STATUSES_TL_U1 / OKC_STATUSES_TL_U2 — The unique indexes that enforce the (CODE, LANGUAGE, ZD_EDITION_NAME) and (MEANING, LANGUAGE, ZD_EDITION_NAME) business keys.
• FND_LANGUAGES — Supplies the LANGUAGE and SOURCE_LANG context for MLS resolution.

All objects reside in the OKC schema and are typically accessed through the APPS synonym layer, consistent with standard Oracle EBS reference-data design.