Results for “adoption_status”

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

Overview

OKC_ARTICLE_ADOPTIONS is a Contracts Core (OKC) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that records the adoption relationship between a global clause version and its localized counterparts across local operating units. In the Oracle Contracts architecture, global clauses are authored centrally as reusable legal language, while local operating units must explicitly decide whether to adopt, localize, or merely make available each global clause version. This table captures precisely that decision matrix: one row exists per global article version per local operating unit, storing adoption status values such as AVAILABLE, LOCALIZED, and ADOPTED. Rows are written only for local operating units; the global authoring organization itself does not appear here.

The heuristic Data Vault classification mined from the foreign key structure is link. This is a modeling suggestion: the table resolves a many-to-many association between global article versions and local operating units, with audit and lifecycle attributes carried alongside. It should be treated as a relationship or association table rather than a transactional hub or a pure descriptive satellite.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• GLOBAL_ARTICLE_VERSION_ID — identifies the source global clause version from OKC_ARTICLE_VERSIONS. This is the column most commonly searched, and it forms the leading component of both the primary key and the unique business key.
• LOCAL_ARTICLE_VERSION_ID — points to the corresponding localized clause version in OKC_ARTICLE_VERSIONS. It is nullable in concept when a clause is only AVAILABLE, since no local version yet exists.
• LOCAL_ORG_ID — the local operating unit for which the adoption decision is recorded; joins to HR_ALL_ORGANIZATION_UNITS.
• ADOPTION_STATUS — the lifecycle state of the adoption: AVAILABLE, LOCALIZED, or ADOPTED.
• ADOPTION_TYPE — classifies the nature or mode of adoption applied to the global version in that operating unit.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Contracts framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the adoption row and when.

The surrogate primary key is OKC_ARTICLE_ADOPTIONS_PK1, defined on (GLOBAL_ARTICLE_VERSION_ID, LOCAL_ORG_ID). A second unique index, OKC_ARTICLE_ADOPTIONS_U1, spans (GLOBAL_ARTICLE_VERSION_ID, LOCAL_ORG_ID, LOCAL_ARTICLE_VERSION_ID) and serves as the broader business-key candidate, guaranteeing that at most one localized version per global version per operating unit is recorded.

Common Use Cases and Queries

Typical reporting scenarios include determining which operating units have adopted a given global clause, identifying global clauses that have been localized but not formally adopted, and auditing the spread of standard legal terms across the enterprise.

• Adoption listing for a global clause version: SELECT local_org_id, adoption_status, local_article_version_id FROM okc_article_adoptions WHERE global_article_version_id = :global_id;
• Status summary: SELECT adoption_status, COUNT(*) FROM okc_article_adoptions GROUP BY adoption_status;
• Adoption gap analysis — global versions with no ADOPTED row for a given operating unit, implemented by joining GLOBAL_ARTICLE_VERSION_ID against OKC_ARTICLE_VERSIONS and filtering LOCAL_ORG_ID.
• Localization audit — rows where ADOPTION_STATUS = 'LOCALIZED' and LOCAL_ARTICLE_VERSION_ID is populated, confirming that downstream localized text exists.

Because ADOPTION_STATUS changes over time, queries should be scoped by operating unit and joined to OKC_ARTICLE_VERSIONS to retrieve clause names and version numbers for presentation.

Related Objects

• OKC_ARTICLE_VERSIONS — the primary parent, joined twice via GLOBAL_ARTICLE_VERSION_ID and LOCAL_ARTICLE_VERSION_ID; supplies clause text, version numbers, and article metadata.
• HR_ALL_ORGANIZATION_UNITS — source of valid operating unit definitions, joined on LOCAL_ORG_ID.
• OKC_ARTICLES_B and OKC_ARTICLES_TL — article headers and translations reached through OKC_ARTICLE_VERSIONS.
• OKC_ART_PARTIES_B — global or local party linkages on article versions, useful when reporting clause ownership.
• OKC_ARTICLE_ADOPTIONS_PK1 / OKC_ARTICLE_ADOPTIONS_U1 — supporting unique constraints that enforce one adoption record per global version and organization.
• Contracts Core PL/SQL APIs that manage clause adoption during operating unit setup, which read and write this table directly rather than through a public interface.