Results for “okc_folder_contents_u1”

12 results




Overview
Explore in AI Chat

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

Overview

OKC.OKC_FOLDER_CONTENTS is a transactional intersection table in the Oracle Contracts (OKC) schema that stores the association between contract folders and the clauses (articles) they contain. Each row represents one clause-to-folder membership, establishing which reusable contract terms belong to a given folder structure. The table was introduced in release 11.5.10 as a replacement for the legacy OKC_STD_ART_SET_MEMS structure, and it remains valid and actively used in Oracle EBS 12.1.1 and 12.2.2.

Folders provide the organizational hierarchy for authoring and maintaining contract templates; this table supplies the content layer of that hierarchy by pointing each folder at one or more rows in OKC_ARTICLES_ALL. Because every row captures a relationship between two independent entities rather than descriptive attributes, the heuristic Data Vault classification for this object is link. That classification is a modeling suggestion only, useful when mapping the EBS schema into a vault-style warehouse.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its unique index OKC_FOLDER_CONTENTS_U1 resides in APPS_TS_TX_IDX. The user search term "okc_folder_contents_u1" refers to that unique index, which enforces the business rule that a given clause may appear only once within the same folder.

Key Information Stored

Eight columns are documented for the table. The most significant are the two key-bearing attributes and the standard concurrency and auditing columns:

  • FOLDER_ID — the folder identifier; foreign key to OKC_FOLDERS_ALL_B. This identifies the parent folder that owns the content line.
  • MEMBER_ID — the clause identifier; foreign key to OKC_ARTICLES_ALL. This identifies the clause or article attached to the folder.
  • OBJECT_VERSION_NUMBER — sequential number initialized to 1 on insert and incremented on each update. Contract APIs use it for optimistic locking so that changes are not lost when stale records are submitted.
  • CREATED_BY, CREATION_DATE — standard "Who" columns recording the creating user and timestamp.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard "Who" columns recording the most recent modification and the login session that performed it.

The composite unique index OKC_FOLDER_CONTENTS_U1 (FOLDER_ID, MEMBER_ID) is the business-key candidate and the basis of the documented primary key OKC_FOLDER_CONTENTS_PK1. A non-unique index, OKC_FOLDER_CONTENTS_N1, exists on MEMBER_ID alone and supports reverse lookups from clause to folder. There is no separate single-column surrogate key; the row is uniquely identified by the folder-and-clause pairing itself.

Common Use Cases and Queries

Typical scenarios include listing all clauses in a contract folder, determining which folders reference a particular clause before changing or retiring it, and reconciling folder contents when template sets are copied or upgraded. A useful query pattern joins the table to both parent objects:

  • Folder content listing: SELECT fc.folder_id, fc.member_id FROM okc.okc_folder_contents fc WHERE fc.folder_id = :folder_id;
  • Clause usage lookup: SELECT fc.folder_id FROM okc.okc_folder_contents fc WHERE fc.member_id = :article_id; — this benefits from OKC_FOLDER_CONTENTS_N1.
  • Descriptive join: joining FOLDER_ID to OKC_FOLDERS_ALL_B and MEMBER_ID to OKC_ARTICLES_ALL to retrieve folder names and clause titles for reporting.

Reports commonly count clauses per folder to audit template completeness, and data-migration scripts insert rows here when rebuilding folder structures from legacy OKC_STD_ART_SET_MEMS data.

Related Objects

The table participates in a small, well-defined dependency network:

  • OKC.OKC_FOLDERS_ALL_B — referenced through FOLDER_ID; the folder definition header.
  • OKC.OKC_ARTICLES_ALL — referenced through MEMBER_ID; the clause or article master.
  • OKC_FOLDER_CONTENTS_U1 — unique index enforcing the folder/member business key.
  • OKC_FOLDER_CONTENTS_N1 — non-unique index supporting clause-based lookups.
  • APPS.OKC_FOLDER_CONTENTS — the APPS synonym through which concurrent programs and forms access the table.

No database objects are documented as being referenced by OKC_FOLDER_CONTENTS other than these parents, and the table itself is referenced only through the APPS synonym, keeping its dependency footprint narrow and its role clearly scoped to folder-to-clause linkage.