Results for “article_subject_code”

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

Overview

OKE_ARTICLE_SUBJECTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKE - Project Contracts product family, which covers the contracts authoring and delivery functionality shared with the OKC (Contracts Core) module. The view presents the set of valid "article subjects" used to classify and organize contract articles, clauses, and related contract terms during contract authoring.

Functionally, the view exposes a filtered, denormalized list of lookup values that define the subject categories applicable to contract articles. It is a read-only presentation layer intended for inquiry, reporting, and integration rather than transactional data entry. Because it derives entirely from the standard Oracle Application Object Library (FND) lookup infrastructure, it participates in the same multi-language (translatable) framework used throughout EBS, and it respects lookup enablement and effective date ranges. Report developers, extension builders, and integration specialists reference this view when they need to resolve an article subject code into its user-facing name for display in custom reports, SOA/BPEL integrations, or Discoverer/BI Publisher reports.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUP_VALUES_VL, itself a view in the APPS schema. The "_VL" suffix indicates a translatable view that joins the base lookup values table with its translation table, returning the language-appropriate meaning and description. The documented filter is:

• WHERE LOOKUP_TYPE = 'OKC_SUBJECT'

This restriction narrows the entire contents of FND_LOOKUP_VALUES_VL down to the single lookup type used by Oracle Contracts to identify article subjects. Consequently, OKE_ARTICLE_SUBJECTS_V contains no data of its own; every row corresponds to a lookup value defined under the OKC_SUBJECT lookup type. Changes to the underlying lookup configuration (adding, disabling, or date-limiting a subject code) are immediately reflected in the view, so it should always be queried at runtime rather than cached.

Key Columns

The view exposes the following columns, which correspond to the selected lookup attributes:

• ARTICLE_SUBJECT_CODE — the lookup code; the internal identifier used to store the article subject on contract records.
• ARTICLE_SUBJECT_NAME — the lookup meaning; the user-facing display name of the article subject, returned in the session's language.
• DESCRIPTION — the detailed description of the article subject, also language-dependent.
• START_DATE_ACTIVE — the date from which the subject becomes active and selectable.
• END_DATE_ACTIVE — the date after which the subject is no longer active.
• ENABLED_FLAG — indicates whether the subject is currently enabled ('Y') or disabled ('N').

Together, START_DATE_ACTIVE, END_DATE_ACTIVE, and ENABLED_FLAG determine whether an article subject is available for use at any given point in time.

Common Use Cases and Queries

Typical scenarios include populating a list of values on a custom contract form, building a validation query in an interface program, and producing reference reports of active article subjects. A representative query returning only currently active and enabled subjects is:

• SELECT article_subject_code, article_subject_name, description FROM 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 article_subject_name;

Because the view is built on FND_LOOKUP_VALUES_VL, it automatically returns the meaning and description in the user's current language, making it suitable for multilingual reporting without additional joins. Developers should avoid inserting or updating through this view, as it is strictly a read-only projection over the lookup framework.