Results for “member_id”

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

Overview

OKC_FOLDER_CONTENTS is a table in the OKC (Contracts Core) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the clauses (articles) that are associated with a contracts folder, functioning as the modern replacement for the pre-11.5.10 table OKC_STD_ART_SET_MEMS. In the Oracle Contracts architecture, folders act as containers that group standard articles, clauses, and contract terms into reusable templates. This table resolves the many-to-many relationship between folders and articles, capturing which article belongs to which folder.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is a link table. It sits between two hubs — folders and articles — and records the associations between them. This classification is a modeling suggestion based on the FK topology rather than a formally designated Data Vault construct, but it accurately reflects the table's role as an intersection entity.

Key Information Stored

The table is documented with eight physical columns in the 12.2.2 schema. The most significant are the two key columns that together form the composite primary key:

• FOLDER_ID — Identifies the parent folder. This column is part of the primary key OKC_FOLDER_CONTENTS_PK1 and carries a foreign key to OKC_FOLDERS_ALL_B.
• MEMBER_ID — Identifies the article (clause) associated with the folder. This column, the term the user searched for, is the second component of the primary key and carries a foreign key to OKC_ARTICLES_ALL.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent-update control, typical of Oracle EBS OA Framework–enabled entities.
• CREATED_BY, CREATION_DATE — Audit columns recording the user and timestamp of row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns tracking the most recent modification and the session login that performed it.

Both the primary key OKC_FOLDER_CONTENTS_PK1 and the unique index OKC_FOLDER_CONTENTS_U1 are defined on the pair (FOLDER_ID, MEMBER_ID). This means the true business key is the folder-to-member combination, not a single surrogate column; the table enforces that a given article may appear only once within a folder. There is no separately generated surrogate identifier documented beyond the composite key.

Common Use Cases and Queries

Analysts and developers query this table to determine folder composition — which clauses are attached to a given template — and to trace where an article is reused across folders. A typical listing of members for a folder is:

• SELECT member_id FROM okc_folder_contents WHERE folder_id = :folder_id;
• SELECT folder_id FROM okc_folder_contents WHERE member_id = :article_id; — reverse lookup of folders referencing an article.
• Joining to OKC_ARTICLES_ALL to retrieve article names and text, and to OKC_FOLDERS_ALL_B to resolve folder metadata, produces clause-set reports for contract authoring.

Reporting scenarios include auditing which clauses appear in standard contract templates, identifying orphaned or duplicate member assignments, and supporting migration or comparison against historical OKC_STD_ART_SET_MEMS data.

Related Objects

• OKC_FOLDERS_ALL_B — Referenced by FOLDER_ID; the parent folder definition.
• OKC_ARTICLES_ALL — Referenced by MEMBER_ID; the article or clause master.
• OKC_STD_ART_SET_MEMS — Legacy predecessor table replaced by this object.
• OKC_FOLDER_CONTENTS_PK1 / OKC_FOLDER_CONTENTS_U1 — Primary key and unique index enforcing folder-member uniqueness.
• Contract authoring APIs and OA Framework pages in the Contracts Core module that read and write folder composition.