Search Results okc_std_art_set_members

Overview

OKC_STD_ART_SET_MEMS_V is a reporting and integration view owned by the APPS schema within the OKC — Contracts Core product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The view is documented as a projection over the OKC_STD_ART_SET_MEMBERS entity, which stores the membership relationships belonging to standard article sets used by Oracle Contracts. In practice, the view is defined over the OKC_FOLDER_CONTENTS synonym, which is the physical repository for folder (article set) membership rows. Its purpose is to expose these membership records in a stable, denormalized form suited to concurrent-program reports, Oracle Answers/XML Publisher data templates, and outbound integrations, without requiring consumers to join or interpret the underlying contracting folder schema directly.

Underlying Base Objects

The documented base object is OKC_FOLDER_CONTENTS, referenced through a synonym from the APPS schema. The view text selects exclusively from this single table, aliased as SAMB, and performs no joins. The naming convention reflects the ETRM contract model: OKC_STD_ART_SET_MEMBERS represents the members of a standard article set, while OKC_FOLDER_CONTENTS is the technical folder/content table in which those members are persisted. Because the view is defined on ROWID and exposes OBJECT_VERSION_NUMBER, it remains updatable at the row level and participates correctly in Oracle Forms–style optimistic locking and OAF-based self-service pages. Column-level privileges are granted to reporting and integration responsibilities through the APPS schema rather than to the base table directly.

Key Columns

• ROW_ID — the ROWID of the underlying OKC_FOLDER_CONTENTS row, exposed for row-level identification and updateability.
• SAE_ID — aliased from MEMBER_ID; the unique identifier of the article set member record.
• SAT_CODE — aliased from FOLDER_ID and converted with TO_CHAR; identifies the standard article set (folder) to which the member belongs. The TO_CHAR conversion produces a character-typed key for concatenation and reporting.
• OBJECT_VERSION_NUMBER — the optimistic locking token maintained for concurrent update control.
• CREATED_BY, CREATION_DATE — standard WHO columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns recording the most recent update user, timestamp, and login context.

Common Use Cases and Queries

Typical usage includes listing the members of a given article set, extracting set membership for contract template migration, and validating that a standard article set is fully populated before contract authoring. The following examples illustrate practical access patterns.

• Retrieve all members of a specific article set:
  SELECT s.SAE_ID, s.SAT_CODE FROM okc_std_art_set_mems_v s WHERE s.SAT_CODE = :p_folder_id;
• List recently modified membership rows for audit:
  SELECT s.SAE_ID, s.LAST_UPDATED_BY, s.LAST_UPDATE_DATE FROM okc_std_art_set_mems_v s WHERE s.LAST_UPDATE_DATE >= SYSDATE - 30 ORDER BY s.LAST_UPDATE_DATE DESC;
• Count members per article set:
  SELECT s.SAT_CODE, COUNT(*) member_count FROM okc_std_art_set_mems_v s GROUP BY s.SAT_CODE;
• Join to the standard article set header using the character-typed set code returned by SAT_CODE.

Because the view is a direct projection of OKC_FOLDER_CONTENTS with no filtering, consumers should always restrict results by SAT_CODE or by audit criteria to avoid full-scan retrieval across all article sets.