Search Results okc_article_adoptions

Overview

The OKC_ARTICLE_ADOPTIONS table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for managing the lifecycle and deployment of global contract clause versions across different local operating units within an enterprise. Its primary role is to track the adoption status of a standardized, global clause as it is made available, localized, or formally adopted for use in local contracts. This enables a structured governance model where legal or central contracting teams can control clause libraries while allowing local business units the flexibility to adapt them to regional requirements.

Key Information Stored

The table's structure is designed to link a global clause version to a specific operating unit and record its adoption state. The primary key is a composite of GLOBAL_ARTICLE_VERSION_ID and LOCAL_ORG_ID, ensuring a unique record for each global clause version per organization. Key columns include GLOBAL_ARTICLE_VERSION_ID, which references the source clause version in OKC_ARTICLE_VERSIONS; LOCAL_ORG_ID, which identifies the local operating unit from HR_ALL_ORGANIZATION_UNITS; and LOCAL_ARTICLE_VERSION_ID, which is a foreign key to OKC_ARTICLE_VERSIONS and stores the ID of the locally created or modified version of the clause, if one exists. The table's core function is to store the adoption status, typically as 'AVAILABLE', 'LOCALIZED', or 'ADOPTED', defining the clause's usability in the local unit.

Common Use Cases and Queries

A primary use case is auditing and reporting on the rollout and compliance of global clause libraries. Administrators can generate reports to see which operating units have adopted specific clauses. Common SQL queries involve joining to related tables to get descriptive information. For example, to list all adoption records for a specific global clause version:

• SELECT oaa.*, hou.NAME org_name FROM okc_article_adoptions oaa, hr_organization_units hou WHERE oaa.local_org_id = hou.organization_id AND oaa.global_article_version_id = <version_id>;

Another critical scenario is determining the effective clause text for a contract line in a given operating unit, which requires checking this table to see if a localized (ADOPTED or LOCALIZED) version exists before defaulting to the global version. Data fixes may also target this table to correct adoption statuses or orphaned records pointing to invalid local version IDs.

Related Objects

OKC_ARTICLE_ADOPTIONS has integral relationships with other core Contracts tables. Its two most critical foreign keys reference the OKC_ARTICLE_VERSIONS table: one for the global source version (GLOBAL_ARTICLE_VERSION_ID) and one for the locally created version (LOCAL_ARTICLE_VERSION_ID). This creates a parent-child relationship between global and local clause versions. The third key foreign key references HR_ALL_ORGANIZATION_UNITS (LOCAL_ORG_ID) to identify the operating unit. This table is central to the global clause functionality, and processes within the OKC clause management APIs will heavily interact with it to create, update, and query adoption records.