Results for “okc_subject”

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

Overview

OKE_ARTICLE_SUBJECTS_V is an APPS-owned database view in Oracle E-Busines Suite that exposes the set of valid subject values used within the Oracle Knowledge Center (OKC) and Oracle Contracts (OKE) modules. Physically, it is a thin filtering wrapper over the Oracle Application Object Library (FND) lookup view, restricted to a single lookup type: OKC_SUBJECT. In the contract and knowledge management data model, subjects categorize clauses, articles, and terms, driving how content is indexed, searched, and reused during contract authoring, negotiation, and approval.

The view's role in reporting and integration is primarily that of a controlled reference or lookup source. Because subject values are not stored in a dedicated transactional table but rather maintained through the standard Oracle lookup facility, this view provides a normalized, read-only projection of the subject domain that integrations and reports can consume without embedding the LOOKUP_TYPE = 'OKC_SUBJECT' filter themselves. It is also the subject dimension leveraged by Contract Terms Library features, including clause subject tagging and knowledge-content management.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 identifies exactly one referenced base object: FND_LOOKUP_VALUES_VL, itself a view in the FND schema. OKC_ARTICLE_SUBJECTS_V is therefore a single-source, single-filter view whose definition is simply:

• SELECT LOOKUP_CODE, MEANING, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, ENABLED_FLAG
• FROM FND_LOOKUP_VALUES_VL
• WHERE LOOKUP_TYPE = 'OKC_SUBJECT'

No joins, unions, or aggregations are present. All attribute semantics, translatable columns, and date-effectivity behavior are inherited directly from the FND lookup layer. The relationship is one-to-many from the lookup-type perspective: the FND view holds every lookup type in the application, and this view returns only the OKC_SUBJECT row set. Because the source is a view rather than a base table, no indexes or constraints exist on OKE_ARTICLE_SUBJECTS_V itself; performance is governed entirely by the underlying FND lookup structures.

Key Columns

• LOOKUP_CODE — The internal, language-independent code for the subject; the value stored against articles and clauses.
• MEANING — The translated, user-facing display name for the subject.
• DESCRIPTION — Optional descriptive text elaborating the intent or usage of the subject value.
• START_DATE_ACTIVE — The date from which the subject value becomes active; null implies no effective start restriction.
• END_DATE_ACTIVE — The date after which the subject value is no longer active; null implies the value remains active indefinitely.
• ENABLED_FLAG — The enablement indicator (typically Y/N) controlling whether the subject is selectable in the application.

Effective availability of a subject is determined by combining ENABLED_FLAG with the active date range relative to the current date. Reports that ignore these fields risk presenting obsolete or disabled subject values.

Common Use Cases and Queries

Typical uses include populating list-of-values replacements in custom reports, validating subject assignments on contract articles in interfaces, and producing reference extracts for downstream systems. A common pattern returns only currently valid, enabled subjects:

• SELECT lookup_code, meaning FROM apps.oke_article_subjects_v WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY meaning;
• SELECT lookup_code, meaning, description, start_date_active, end_date_active, enabled_flag FROM apps.oke_article_subjects_v;
• Joining the view to article or clause tables on subject = lookup_code to translate stored codes into display meanings.

Because the view is defined on FND_LOOKUP_VALUES_VL, users must have appropriate privileges on the FND lookup layer, and any new subject values must be created through the standard lookup maintenance UI under lookup type OKC_SUBJECT. The view requires no separate maintenance and automatically reflects lookup changes.