Search Results okc_terms_templates_all_pk

Overview

OKC_TERMS_TEMPLATES_ALL is the master table for contract terms templates within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, and it is valid in both the 12.1.1 and 12.2.2 releases. A terms template defines the reusable commercial and legal structure applied to contract documents: the clauses, questions, and rules that drive how specific contract types are authored, validated, and approved. The table therefore sits at the center of the Oracle Contracts terms authoring model, holding the definitional record for every template available to a given operating unit.

Mined from its foreign-key structure, the table's heuristic Data Vault classification is hub-leaning. Modeling tools should consider treating TEMPLATE_ID as a hub business key, with descriptive and state-bearing attributes carried in a companion satellite keyed on that identifier. The self-referencing foreign key on PARENT_TEMPLATE_ID records template versioning and inheritance hierarchies rather than a true many-to-many relationship.

Key Information Stored

The table's documented physical schema contains 50 columns in release 12.2.2. The most significant are summarized below.

• TEMPLATE_ID — the surrogate primary key, enforced by OKC_TERMS_TEMPLATES_ALL_PK and by unique index OKC_TERMS_TEMPLATES_ALL_U1.
• TEMPLATE_NAME and ORG_ID — together with WORKING_COPY_FLAG, they form the second unique index (OKC_TERMS_TEMPLATES_ALL_U2), which is the natural business-key candidate for a template within an operating unit.
• INTENT — the template's business intent, distinguishing the purpose for which the template is authored.
• STATUS_CODE, START_DATE, and END_DATE — the lifecycle state and effective-dating window governing template availability.
• GLOBAL_FLAG and HIDE_YN — control whether the template is visible across operating units or suppressed from selection lists.
• PARENT_TEMPLATE_ID — self-referencing pointer linking a template to the parent from which it was derived or versioned.
• WORKING_COPY_FLAG and TRANSLATED_FROM_TMPL_ID — identify draft copies and linguistically derived variants, complemented by LANGUAGE.
• TMPL_NUMBERING_SCHEME — foreign key to OKC_NUMBER_SCHEMES_B, supplying the numbering source used by the template.
• CONTRACT_EXPERT_ENABLED, TEMPLATE_MODEL_ID, PRINT_TEMPLATE_ID, APPROVAL_WF_KEY, and CZ_EXPORT_WF_KEY — configuration pointers to the authoring model, print layout, and workflow processes associated with the template.
• Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the 15 flexfield ATTRIBUTE columns.

Common Use Cases and Queries

The table is queried most often for template discovery, version lineage, and deployment validation. A typical listing of active templates in an operating unit is:

• SELECT template_id, template_name, intent, status_code FROM okc_terms_templates_all WHERE org_id = :org_id AND NVL(hide_yn,'N') = 'N' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• Lineage and version reporting joins the table to itself on PARENT_TEMPLATE_ID = TEMPLATE_ID to trace a template back through its derivation chain.
• Data-migration scripts frequently use ORIG_SYSTEM_REFERENCE_CODE, ORIG_SYSTEM_REFERENCE_ID1, and ORIG_SYSTEM_REFERENCE_ID2 to reconcile templates loaded from external or legacy systems.
• Reporting on clause automation sources the XPRT_* columns (XPRT_REQUEST_ID, XPRT_CLAUSE_MANDATORY_FLAG, XPRT_SCN_CODE) to confirm which templates participate in Oracle Procurement clause extraction.
• Since TRANSLATED_FROM_TMPL_ID and LANGUAGE are populated, multilingual implementations query the table to confirm that a translated template exists for each active base template.

Related Objects

The following objects are the most significant dependents and references identified in the documented relationship data. Each joins to OKC_TERMS_TEMPLATES_ALL on TEMPLATE_ID unless noted otherwise.

• OKC_ALLOWED_TMPL_USAGES — restricts which template is permitted for a given contract usage.
• OKC_TEMPLATE_USAGES and OKC_TEMPLATE_USAGES_H — the current and historical record of where a template has been applied.
• OKC_XPRT_TEMPLATE_RULES — extraction and rules configuration bound to the template.
• OKC_XPRT_QUESTION_ORDERS — sequencing of dynamic questions presented when the template is used.
• OKC_NUMBER_SCHEMES_B — referenced through TMPL_NUMBERING_SCHEME to supply template document numbering.
• OKC_TERMS_TEMPLATES_ALL — self-referencing through PARENT_TEMPLATE_ID for version and inheritance tracking.