Results for “okc_std_article_versions_b”
2 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_STD_ART_VERSIONS_V is an APPS-owned database view within the Oracle E-Business Suite Contracts Core (OKC) module. It presents a version-oriented, security-filtered projection of standard contract clause and article text, functioning as a reporting and integration layer over the underlying version table OKC_STD_ARTICLE_VERSIONS_B and the operational table OKC_ARTICLE_VERSIONS. The view is documented as VALID and is available in both Oracle EBS 12.1.1 and 12.2.2.
The view exposes article/version data using a naming convention aligned with standard article editing (SAE) semantics: columns are aliased to SAE-oriented names such as SAE_ID, SAV_RELEASE, TEXT, SHORT_DESCRIPTION, and DATE_ACTIVE. This aliasing indicates that the view is primarily intended for consumption by standard article maintenance or by reports and integrations that expect the SAE column model rather than the raw OKC_ARTICLE_VERSIONS schema. A SFWT_FLAG column is hard-coded to 'N', indicating that rows returned represent standard (non-edited) source records in this context.
Underlying Base Objects
The documented base objects referenced by the view are the MO_GLOBAL package, the OKC_ARTICLES synonym, the OKC_ARTICLE_ADOPTIONS synonym, and the OKC_ARTICLE_VERSIONS synonym. The view text selects from OKC_ARTICLE_VERSIONS (aliased VER) and applies an EXISTS filter built from two mutually exclusive branches combined via UNION ALL:
- The first branch matches standard articles in OKC_ARTICLES_ALL where STANDARD_YN = 'Y', using an ORG_ID predicate derived from the CLIENT_INFO session value (via USERENV('CLIENT_INFO')) and matched to the article ID.
- The second branch matches locally adopted global article versions in OKC_ARTICLE_ADOPTIONS, matching GLOBAL_ARTICLE_VERSION_ID to the version and LOCAL_ORG_ID to the session organization.
The NVL around the parsed CLIENT_INFO value (falling back to -99) means the multi-org filter resolves to a sentinel value when no client information is set. This ORG_ID- and adoption-driven predicate is the mechanism that renders the view "secure" by org and by adopted global content, which is characteristic of OKC standard article reporting views.
Key Columns
The view exposes the following significant columns:
- ROW_ID – the physical row identifier of the underlying version table (VER.ROWID), usable as a surrogate key.
- SAE_ID – mapped from ARTICLE_ID, identifying the parent standard article.
- SAV_RELEASE – derived via NVL(VER.SAV_RELEASE, TO_CHAR(VER.ARTICLE_VERSION_NUMBER)), giving the assigned release label or, when absent, the article version number.
- OBJECT_VERSION_NUMBER – optimistic locking/version counter.
- SFWT_FLAG – constant 'N' flag in this view.
- DATE_ACTIVE – from START_DATE, the effective date of the version.
- TEXT – the article version text (ARTICLE_TEXT).
- SHORT_DESCRIPTION – from ARTICLE_DESCRIPTION.
- ARTICLE_STATUS – status code of the article version.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – the standard DFF/attribute columns.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns.
Common Use Cases and Queries
Because the view already applies the org and adoption security predicate, it is the preferred source for reports and integrations that must return only standard article versions visible to the current operating unit, without reimplementing the CLIENT_INFO parsing logic.
A typical listing of active standard article versions might be written as:
- SELECT SAV_RELEASE, SAE_ID, DATE_ACTIVE, SHORT_DESCRIPTION FROM OKC_STD_ART_VERSIONS_V WHERE ARTICLE_STATUS = 'ACTIVE' ORDER BY SAE_ID, DATE_ACTIVE;
- SELECT SAE_ID, SAV_RELEASE, TEXT FROM OKC_STD_ART_VERSIONS_V WHERE SAE_ID = :p_article_id;
Other practical scenarios include joining SAE_ID to OKC_ARTICLES_ALL (or OKC_ARTICLES) to retrieve the article name and short code for clause-library reports, exporting version text for contract document assembly interfaces, and driving pick-lists that let users select the release of a standard article. Because the ORG_ID and adoption predicates depend on the session's CLIENT_INFO (as initialized by MO_GLOBAL and the Multi-Org session), consumers running outside the normal EBS session context must set CLIENT_INFO correctly or the view will fall back to the -99 sentinel and return no rows.
-
View: OKC_STD_ART_VERSIONS_V 12.1.1
View for table OKC_STD_ARTICLE_VERSIONS_B
APPS.OKC_STD_ART_VERSIONS_V·↳ MO_GLOBAL·↳ OKC_ARTICLES·↳ OKC_ARTICLE_ADOPTIONS·Explore OKC module →
-
View: OKC_STD_ART_VERSIONS_V 12.2.2
View for table OKC_STD_ARTICLE_VERSIONS_B
APPS.OKC_STD_ART_VERSIONS_V·↳ MO_GLOBAL·↳ OKC_ARTICLES·↳ OKC_ARTICLE_ADOPTIONS·Explore OKC module →