Results for “okc_folders_all”

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

Overview

OKC_STD_ART_SET_MEMS_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as OKC.OKC_STD_ART_SET_MEMS_V with a status of VALID. It belongs to the Oracle Contracts (OKC) module and exposes membership records for standard article sets — the reusable clause and article collections defined within the Contract Terms Library. In EBS 12.1.1 and 12.2.2 the view is classified as a "supplementary view used to simplify forms coding," and Oracle explicitly warns that this view is not recommended for direct querying or data alteration because its definition may change dramatically in subsequent minor or major releases. Its principal role is therefore internal: it presents the standard-article-set membership rows in the combination and shape required by the Contracts forms and by the OKC_SAM_PVT package layer, rather than serving as a stable public reporting interface.

Underlying Base Objects

Documented ETRM metadata identifies OKC_FOLDER_CONTENTS (exposed through a synonym) as the referenced base object. OKC_FOLDER_CONTENTS is the intersection table that relates a folder — a container row in OKC_FOLDERS_ALL, the object the user searched for — to the article or clause rows it holds. The view projects the folder-contents rows that represent standard article set membership. In the Contracts data model, OKC_FOLDERS_ALL stores both folders and standard article sets, so the SAE_ID column in this view is a foreign key to OKC_FOLDERS_ALL; it identifies the standard article set folder to which each membership row belongs. The view is referenced by APPS.OKC_SAM_PVT, the standard article set maintenance package, which reads and returns membership rows through this simplified projection. No other base tables are documented for this view.

Key Columns

• ROW_ID (ROWID) — the physical address of the underlying row in the database; useful for row identification in forms but not stable across reorganizations.
• SAE_ID (NUMBER) — foreign key to OKC_FOLDERS_ALL; identifies the standard article set (folder) that owns this membership entry.
• SAT_CODE (VARCHAR2, 40) — surrogate key used for primary unique identifiers, supplying the developer key for the membership record.
• OBJECT_VERSION_NUMBER (NUMBER) — sequential number set to 1 on insert and incremented on update; used by APIs to detect stale records during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns capturing audit and session information for each row.

Notably, the view does not expose the article, clause, or document reference columns themselves; consumers that need the referenced content must join back to OKC_FOLDER_CONTENTS or to the article and clause tables.

Common Use Cases and Queries

Typical usage is diagnostic rather than integrative: confirming which standard article sets reference a given membership code, validating OBJECT_VERSION_NUMBER values before calling OKC_SAM_PVT, or auditing Who columns for recently changed memberships. Because Oracle discourages direct access, production code should reach this data through OKC_SAM_PVT or the supported folder APIs rather than querying the view. A representative query lists all memberships for a specific standard article set:

SELECT sae_id, sat_code, object_version_number, last_update_date FROM apps.okc_std_art_set_mems_v WHERE sae_id = :p_sae_id ORDER BY sat_code;

A second pattern joins the view to OKC_FOLDER_CONTENTS to recover the referenced content identifiers omitted from the projection. All such queries should be treated as read-only and reviewed against each patch level, since the column list and underlying joins may change between EBS releases.