Search Results okc_number_schemes_b




Overview
Explore in AI Chat

Overview

OKC_NUMBER_SCHEMES_B is the base table in the Oracle Contracts Core (OKC) schema that stores the numbering schemes used to organize sections and clauses within contract templates and contract documents. A numbering scheme defines how articles, sections, and clauses are labelled and sequenced — for example, decimal hierarchies such as 1.1, 1.2, or alpha-numeric patterns — and therefore governs the structural readability of generated contract text. The table exists in Oracle E-Business Suite 12.1.1 and 12.2.2 and is owned by the OKC schema, which forms part of the Oracle Contracts (formerly Oracle Terms and Conditions / ETRM) application stack.

From a data-modeling perspective, the heuristic Data Vault classification for OKC_NUMBER_SCHEMES_B is hub-leaning. It carries a single-column surrogate primary key, NUM_SCHEME_ID, with no foreign key columns of its own, and it is referenced by several dependent tables. This profile is consistent with a hub entity representing a stable business concept (a numbering scheme) whose descriptive attributes could optionally be separated into a satellite. Analysts building a Data Vault or dimensional model should treat this table as a candidate hub, with consumers such as OKC_TEMPLATE_USAGES and OKC_TERMS_TEMPLATES_ALL acting as links or dependent satellites.

Key Information Stored

The documented physical schema for 12.2.2 lists nine columns. The most significant are:

  • NUM_SCHEME_ID — the surrogate primary key, enforced by OKC_NUMBER_SCHEMES_B_PK. All foreign key relationships from dependent tables point to this column.
  • NUM_SCHEME_PREVIEW — a preview or display representation of the numbering scheme, used to render or illustrate the scheme's pattern to users in the Contracts setup UI.
  • NUMBER_ARTICLE_YN — a flag indicating whether articles are numbered under this scheme; this drives whether article-level sequencing is applied when clauses and sections are laid out.
  • OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE — standard "who/when created" audit columns populated from the application user context.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "who/when last modified" audit columns, with LAST_UPDATE_LOGIN capturing the login identifier of the last modifying session.

No unique business-key index beyond the primary key is documented in the supplied metadata; NUM_SCHEME_ID is therefore both the surrogate key and the sole documented identifier for the entity. Business meaning is carried in the descriptive columns, particularly NUM_SCHEME_PREVIEW and NUMBER_ARTICLE_YN.

Common Use Cases and Queries

Typical usage centres on contract authoring configuration and template administration. Common scenarios include listing all defined numbering schemes, identifying which schemes number articles, and retrieving the scheme attached to a given template or document.

  • Enumerating available schemes: SELECT num_scheme_id, num_scheme_preview, number_article_yn FROM okc_number_schemes_b ORDER BY num_scheme_id;
  • Finding which schemes number articles: SELECT num_scheme_id, num_scheme_preview FROM okc_number_schemes_b WHERE number_article_yn = 'Y';
  • Joining to templates to see scheme usage: SELECT t.tmpl_numbering_scheme, n.num_scheme_preview FROM okc_terms_templates_all t, okc_number_schemes_b n WHERE t.tmpl_numbering_scheme = n.num_scheme_id;
  • Audit reporting: querying LAST_UPDATED_BY and LAST_UPDATE_DATE to track who changed scheme definitions and when.

This table is also referenced during contract generation, where the selected scheme determines the numbering applied to compiled clause and section hierarchies.

Related Objects

The following objects reference OKC_NUMBER_SCHEMES_B through documented foreign keys or are otherwise significant consumers:

  • OKC_TERMS_TEMPLATES_ALL — joins on TMPL_NUMBERING_SCHEME = NUM_SCHEME_ID; the primary template-side consumer of numbering schemes.
  • OKC_TEMPLATE_USAGES — joins on DOC_NUMBERING_SCHEME = NUM_SCHEME_ID; records the numbering scheme applied per template usage.
  • OKC_TEMPLATE_USAGES_H — the history/audit counterpart of OKC_TEMPLATE_USAGES, joining on DOC_NUMBERING_SCHEME = NUM_SCHEME_ID.
  • OKC_NUMBER_SCHEMES_B_PK — the primary key constraint enforcing uniqueness on NUM_SCHEME_ID.

These relationships confirm the table's role as a central reference entity within the Contract Terms and Conditions model, referenced whenever numbering behaviour for templates or generated documents must be resolved.