Results for “okc_tmpl_draft_clauses”

50+ results




Overview
Explore in AI Chat

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

Overview

OKC_TMPL_DRAFT_CLAUSES is a Contracts Core (OKC) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the association between contract templates and the clause (article) content staged within a template draft. It acts as the working repository for clause-level template authoring: each row links a template definition to a specific article and article version, capturing the section placement, label, and selection behaviour that the template author has configured. The table is populated and maintained by the Contract Template authoring flows in the Oracle Contracts module and is consumed when a template is converted into an actual contract or when template content is rendered for review.

From a data-modeling perspective, the mined foreign-key structure suggests a standalone classification under a heuristic Data Vault model. In practice, however, OKC_TMPL_DRAFT_CLAUSES functions as a link-style association table straddling OKC_ARTICLES_ALL and OKC_ARTICLE_VERSIONS, with TEMPLATE_ID, ARTICLE_ID and ARTICLE_VERSION_ID forming the effective business key. The absence of inbound foreign keys from other documented tables supports treating it as an isolated association entity rather than a shared hub or satellite.

Key Information Stored

The documented physical schema contains fifteen columns. The most significant are grouped below.

  • Business key columns: TEMPLATE_ID identifies the owning template; ARTICLE_ID identifies the clause/article selected from the article library (OKC_ARTICLES_ALL); ARTICLE_VERSION_ID pins the exact released version of that article (OKC_ARTICLE_VERSIONS). The unique index OKC_TMPL_DRAFT_CLAUSES_U1 (TEMPLATE_ID, ARTICLE_ID, ARTICLE_VERSION_ID) confirms this triplet as the primary business-key candidate.
  • Workflow sequencing: WF_SEQ_ID drives ordering of the clause within the template, and the alternate unique index OKC_TMPL_DRAFT_CLAUSES_U2 (TEMPLATE_ID, ARTICLE_ID, WF_SEQ_ID) enforces that a given article appears at most once per workflow position within a template.
  • Presentation attributes: SECTION_NAME and ARTICLE_LABEL provide the displayed section heading and clause label used when the template is rendered.
  • Behaviour flags: MULTIPLE_SCNS_YN indicates whether multiple sections are permitted for the clause; PREV_VAL_VERSION_YN signals use of the previous valid version; SELECTED_YN records whether the author has marked the clause as included.
  • Audit and concurrency: OBJECT_VERSION_NUMBER supports optimistic locking; CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY and LAST_UPDATE_LOGIN satisfy standard EBS WHO-column auditing.

Common Use Cases and Queries

Typical usage centres on template content reporting, validation of draft assemblies, and troubleshooting template rendering.

  • Listing all clauses for a template: SELECT article_id, article_version_id, wf_seq_id, article_label FROM okc_tmpl_draft_clauses WHERE template_id = :p_template_id ORDER BY wf_seq_id;
  • Checking for duplicate article placements across sequence positions by counting ARTICLE_ID per TEMPLATE_ID.
  • Verifying that SELECTED_YN and PREV_VAL_VERSION_YN flags match downstream contract generation output.
  • Auditing recent authoring activity using LAST_UPDATE_DATE and LAST_UPDATED_BY for governance and change-tracking reports.

Related Objects

  • OKC_ARTICLES_ALL — joined on ARTICLE_ID; supplies the article definition and library attributes.
  • OKC_ARTICLE_VERSIONS — joined on ARTICLE_VERSION_ID; supplies the versioned clause text and metadata.
  • OKC_TEMPLATES_ALL (via TEMPLATE_ID) — the header table that owns each template draft, referenced implicitly through TEMPLATE_ID.
  • OKC_TMPL_DRAFT_* companion tables — other draft-level tables sharing TEMPLATE_ID for sections, groups, or rules.
  • OKC_CONTRACTS_ALL / OKC_TMPL_CONTRACTS — contract instances generated from templates, consuming the clause selections recorded here.

Together these objects define the template authoring chain: articles and versions are sourced into OKC_TMPL_DRAFT_CLAUSES, sequenced and flagged within a template, and then consumed when the template is instantiated into a live contract.