Search Results okc_terms_templates_all




Overview
Explore in AI Chat

Overview

The OKC_TERMS_TEMPLATES_ALL table is the master repository for contract terms templates within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the foundational data object for defining and storing reusable templates that standardize the legal, commercial, and operational terms and conditions for contracts. These templates are critical for ensuring consistency, accelerating contract authoring, and enforcing organizational policies across various contract types, such as sales, procurement, and service agreements. The table supports a multi-organization architecture, as indicated by the "_ALL" suffix, allowing templates to be shared or partitioned across different operating units.

Key Information Stored

The table's primary identifier is the TEMPLATE_ID column, which is the primary key. While the provided metadata does not list all columns, the foreign key relationships reveal other critical attributes. The PARENT_TEMPLATE_ID column enables hierarchical template structures, allowing for inheritance and versioning. The TMPL_NUMBERING_SCHEME column links to the OKC_NUMBER_SCHEMES_B table, defining the sequence or pattern for generating contract numbers when a template is used. Other typical columns in such a master table would include TEMPLATE_NAME, DESCRIPTION, TEMPLATE_STATUS (e.g., 'DRAFT', 'APPROVED', 'ACTIVE'), TEMPLATE_TYPE, START_DATE, END_DATE, and attributes for tracking creation and modification (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

A primary use case is the administration of the template library, often performed via the Oracle Contracts Core user interface. Common reporting and validation queries involve listing all active templates for a specific operating unit or contract type. For instance, to retrieve a basic list of templates, a query might be: SELECT template_id, template_name, description FROM okc_terms_templates_all WHERE template_status = 'ACTIVE' AND sysdate BETWEEN start_date AND nvl(end_date, sysdate);. Another frequent operation is querying the template hierarchy to understand parent-child relationships: SELECT child.template_id, child.template_name, parent.template_name AS parent_template FROM okc_terms_templates_all child LEFT JOIN okc_terms_templates_all parent ON child.parent_template_id = parent.template_id;. Technical consultants may also query this table to diagnose template assignment issues or to audit template usage history.

Related Objects

The table maintains integral relationships with several other OKC objects, as documented by its foreign keys:

  • OKC_NUMBER_SCHEMES_B: Joined via TMPL_NUMBERING_SCHEME to control contract numbering.
  • OKC_TERMS_TEMPLATES_ALL (Self-Referential): Joined via PARENT_TEMPLATE_ID to establish template hierarchies.
  • OKC_ALLOWED_TMPL_USAGES: Joined via TEMPLATE_ID to define which business documents (e.g., Sales Order, Purchase Order) a template can be used for.
  • OKC_TEMPLATE_USAGES & OKC_TEMPLATE_USAGES_H: Joined via TEMPLATE_ID to track instances where a template has been applied and maintain its history.
  • OKC_XPRT_QUESTION_ORDERS & OKC_XPRT_TEMPLATE_RULES: Joined via TEMPLATE_ID, linking templates to the Expert rules engine for clause selection and questionnaire logic.

These relationships position OKC_TERMS_TEMPLATES_ALL as a central hub in the contract terms authoring and management framework.