Results for “okc_folders_all_b”

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

Overview

OKC_FOLDERS_ALL_B is the foundational table of the Contracts Core (OKC) module in Oracle EBS 12.1.1 and 12.2.2. It stores the folders created for an operating unit organization. In functional terms, a folder is the container into which reusable contract clauses and articles are organized, allowing contract authors to assemble documents from a controlled library rather than drafting each agreement from scratch. Prior to release 11.5.10 these containers were held in FND_LOOKUP_VALUES and were known as "Article Sets"; OKC_FOLDERS_ALL_B replaced that mechanism and remains the system of record for folder definitions in both 12.1.1 and 12.2.2.

The table is owned by the OKC schema and is documented as a satellite-leaning object under a heuristic Data Vault classification. Applied as a modeling suggestion only, this means the table behaves principally as a descriptive satellite keyed by an identifier, rather than as a pure hub of business entities or an associative link resolving many-to-many relationships. The presence of ORG_ID also gives the table a multi-tenant, organization-scoped character.

Key Information Stored

The table is documented with 25 physical columns. The most significant are:

• FOLDER_ID — the surrogate primary key, enforced by OKC_FOLDERS_ALL_PK1 and by the unique index OKC_FOLDERS_ALL_B_U1. It is the value propagated to dependent tables.
• ORG_ID — the operating unit to which the folder belongs; it carries a foreign key to HR_ALL_ORGANIZATION_UNITS and drives Multi-Org (MOAC) security.
• SAT_CODE — the business-facing classification code for the folder, determining the folder's category or system designation.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording creation and last modification context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF-enabled descriptive flexfield segment set, reserved for client-specific extensions and not interpreted by base product logic.

FOLDER_ID is the surrogate key; no independent business key column is separately documented beyond the unique index on FOLDER_ID itself, so ORG_ID combined with SAT_CODE is the practical natural identifier when resolving a folder to a specific organization.

Common Use Cases and Queries

Typical uses include clause-library reporting, migration validation, and building custom contract-authoring integrations. A canonical join resolves folders to their organization name and to the contents they hold:

SELECT f.folder_id, f.org_id, f.sat_code, c.clause_id
FROM   okc_folders_all_b f,
       okc_folder_contents c,
       hr_all_organization_units h
WHERE  f.folder_id = c.folder_id
AND    f.org_id    = h.organization_id
AND    f.org_id    = :p_org_id;

Because the table is MOAC-enabled, query users should initialize the Org context through MO_GLOBAL before executing ad-hoc SQL. Audit queries commonly filter on LAST_UPDATE_DATE within a date range to identify folders touched during a configuration change or patch window. Reporting extracts typically project FOLDER_ID, ORG_ID, SAT_CODE, and the audit columns only, since the DFF attributes are sparsely populated.

Related Objects

• OKC_FOLDER_CONTENTS — the child table that associates individual clauses or articles with a folder; joined on FOLDER_ID, it is the primary detail-level analogue of this header record.
• HR_ALL_ORGANIZATION_UNITS — the parent of ORG_ID, supplying the operating unit name and hierarchy for Multi-Org filtering and reporting.
• OKC_FOLDERS_ALL_TL — the translation table for folder names and descriptions, joined to the base table on FOLDER_ID for language-specific output.
• OKC_FOLDERS_V — the business view exposing folder data with translation and organization context, commonly used by concurrent programs and OAF pages.
• OKC_ARTICLES_ALL_B and its contents table — the clause-level store that feeds the folders through OKC_FOLDER_CONTENTS.
• OKC_CONTRACTS_ALL_B — contracts that reference folder-derived clause sets during authoring.

All design references should be validated against the deployed schema, as column counts and index names in a customer instance may differ from the ETRM baseline.