Results for “article_id”

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

Overview

APPS.OKC_TERMS_ART_VERSIONS_V is a Contracts Core (OKC) view that consolidates clause (article) header information from OKC_ARTICLES_ALL with version-level content from OKC_ARTICLE_VERSIONS, and in its second branch with adoption records from OKC_ARTICLE_ADOPTIONS. It exposes a single, denormalized result set in which each row represents one article version, along with the article it belongs to. The view is defined as a UNION ALL of two queries, and its status in the EBS data dictionary is VALID. It is used primarily for reporting and integration on standard contract terms — the boilerplate clauses that OKC manages centrally and reuses across contract templates and authored contracts.

The view is especially relevant when sourcing clause text, display names, and lifecycle information into custom reports, extracts, or downstream systems. Because the view joins article, version, and adoption data, consumers do not need to reconstruct those relationships themselves.

Underlying Base Objects

The view is defined over three documented synonym objects under APPS:

• OKC_ARTICLES_ALL — the article (clause) master, filtered to STANDARD_YN = 'Y' in both branches of the union.
• OKC_ARTICLE_VERSIONS — version-level clause content, joined on ARTICLE_ID.
• OKC_ARTICLE_ADOPTIONS — captures adoption of global clause versions by local organizations, used in the second branch.

The first branch returns standard article versions directly. The second branch returns versions that are global (GLOBAL_YN = 'Y'), approved (ARTICLE_STATUS = 'APPROVED'), and adopted (ADOPTION_TYPE = 'ADOPTED', ADOPTION_STATUS = 'APPROVED'), using the adoption's local organization as the ORG_ID. In that branch, ARTICLE_STATUS is populated from ADP.ADOPTION_STATUS rather than from the version record.

Key Columns

• ARTICLE_ID, ARTICLE_VERSION_ID, ARTICLE_VERSION_NUMBER — identifiers linking the clause to a specific version.
• ARTICLE_TITLE, ARTICLE_NUMBER, DISPLAY_NAME — descriptive attributes; ARTICLE_NUMBER is the user-facing clause number commonly searched as "article_number".
• ARTICLE_STATUS — workflow/lifecycle status of the version (or adoption status in the second branch).
• ARTICLE_TYPE, ARTICLE_INTENT, ADOPTION_TYPE — classification and adoption metadata.
• ARTICLE_TEXT, ARTICLE_DESCRIPTION, ADDITIONAL_INSTRUCTIONS — the clause content and supporting narrative.
• START_DATE, END_DATE, PROVISION_YN, DEFAULT_SECTION — effective-dating and placement attributes.
• ORG_ID — owning or adopting organization; GLOBAL_YN, LOCK_TEXT, INSERT_BY_REFERENCE — global and text-generation controls.

Common Use Cases and Queries

Typical usages include retrieving clause text by article number, auditing clause versions, and extracting approved global clauses adopted into local organizations. A common lookup keyed on the searched term is:

• SELECT article_id, article_version_id, article_number, article_title, article_status FROM okc_terms_art_versions_v WHERE article_number = :p_number;
• SELECT article_id, article_version_number, display_name, article_status, start_date, end_date FROM okc_terms_art_versions_v WHERE article_id = :p_article_id ORDER BY article_version_number DESC;
• SELECT article_number, global_yn, org_id, adoption_type, article_status FROM okc_terms_art_versions_v WHERE global_yn = 'Y';

Because the view is a union, callers should expect at most one row per article/version/org combination and should apply DISTINCT or aggregate functions in reports where clause-level, not adoption-level, output is required.