Search Results okc_std_articles_tl_pk

Overview

The OKC_STD_ARTICLES_TL table is a core translation table within the Oracle E-Business Suite (EBS) Contracts Core module (OKC). Operating under the Multi-Language Support (MLS) architecture, it stores the language-specific, translatable text for standard contract articles. Its primary role is to separate language-sensitive descriptive data from the base transactional data held in the OKC_STD_ARTICLES_B table. This design enables a single standard article definition to support multiple language installations, allowing the Contracts application to display article names, descriptions, and other text in a user's session language. It is a critical component for global deployments of Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table holds the translated versions of columns from its base table. While the specific column list is not detailed in the provided metadata, standard MLS table design dictates that its core structure includes a composite primary key and translatable attributes. The documented primary key consists of the ID (linking to OKC_STD_ARTICLES_B.STD_ARTICLE_ID) and the LANGUAGE code (e.g., 'US', 'DE', 'JA'). Typical translatable columns in such a table would include:

• NAME: The translated name or title of the standard contract article.
• DESCRIPTION: The detailed translated description of the article's purpose and content.
• SOURCE_LANG: A column indicating the original language in which the record was created.

All user-facing text associated with a standard article is stored in this table, ensuring linguistic flexibility.

Common Use Cases and Queries

This table is primarily accessed by the application's MLS engine to retrieve the correct language text. Common operational and reporting use cases include generating contract templates in a specific language, auditing translation completeness, and supporting data migration for new language deployments. A typical query to retrieve a standard article's information in the current session language would join the base and translation tables.

SELECT b.std_article_id,
       tl.name,
       tl.description,
       b.article_effective_date
FROM   okc_std_articles_b b,
       okc_std_articles_tl tl
WHERE  b.std_article_id = tl.id
AND    tl.language = USERENV('LANG')
AND    b.std_article_id = :article_id;

Another common pattern is to check for missing translations for a given article by comparing available languages against the installed language list.

Related Objects

The table has defined, integral relationships with other key objects in the Contracts Core schema, primarily through its primary key constraint.

• OKC_STD_ARTICLES_B: This is the base transactional table. The OKC_STD_ARTICLES_TL.ID column is a foreign key referencing OKC_STD_ARTICLES_B.STD_ARTICLE_ID. Every record in the TL table must correspond to a parent record in the B table.
• OKC_STD_ARTICLES_TL_PK: The primary key constraint on the columns (ID, LANGUAGE) enforces uniqueness for each language translation of a standard article.

Applications and public APIs, such as those in the OKC_STD_ARTICLES_PKG, will perform operations on this table to manage translated content, but the direct foreign key relationship is exclusively with its base table, OKC_STD_ARTICLES_B.