Search Results okc_terms_multirec_grp




Overview
Explore in AI Chat

Overview

The OKC_TERMS_MULTIREC_GRP package is a group-type (GRP) PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema, owned by the Contracts (OKC) product family and specifically associated with the Oracle Terms and Conditions / ETRM (Enterprise Contract Terms Management) module. Its primary business function is to manage and synchronize "multi-record" term structures — the hierarchical groupings of terms, articles, clauses, and variables that make up a contract template or authored contract document. Unlike a pure data-access API package, OKC_TERMS_MULTIREC_GRP is classified as a group package, meaning it encapsulates related business operations that act on multiple records of term structure data as a single unit of work. It provides the programmatic backbone for creating and updating articles, managing article variables and their values, organizing the layout and display sequence of sections, merging reviewed clauses back into a document, and synchronizing contract documents with the Oracle Expert (formerly ASO/expert) rules engine. In Oracle EBS 12.1.1 and 12.2.2, this package underpins the Terms and Conditions authoring and template-management UI flows that rely on multi-record term editing rather than single-record term operations.

Key Procedures and Functions

The package exposes eight documented procedures:

  • CREATE_ARTICLE — Creates a new article (clause/article instance) within a term structure, inserting the necessary rows into the contract article tables.
  • UPDATE_ARTICLE_VARIABLE — Updates the variable values associated with an article, supporting dynamic substitution of term variables within clause text.
  • UPDATE_STRUCTURE — Reorganizes or updates the term-structure layout, including display sequence, labels, and mandatory flags for structure records. This is the procedure most directly associated with the "update_structure" search term.
  • SYNC_DOC_WITH_EXPERT — Synchronizes the authored contract document with the Oracle Expert rules engine so that expert-driven selections and term choices remain consistent.
  • REFRESH_ARTICLES — Reloads or re-evaluates article data to reflect current template or variable state.
  • ORGANIZE_LAYOUT — Arranges the visual/structural layout of sections and articles according to template configuration.
  • MERGE_REVIEW_CLAUSES — Merges clauses that were modified during a review cycle back into the live contract term structure.
  • SORT_CLAUSES — Orders clauses within the structure, typically by display sequence or section.

The package also declares several record and table types (art_var_rec_type, kart_rec_type, organize_rec_type, structure_rec_type, article_rec_type, merge_review_rec_type and corresponding TABLE types) that mirror the columns of the underlying tables, indicating the procedures operate on PL/SQL collections rather than single-row operations.

Tables Accessed

The package reads and writes the core ETRM term-model tables: OKC_K_ARTICLES_B (article base rows), OKC_ARTICLES_ALL (article view/synonym), OKC_ARTICLE_VERSIONS (article versioning), OKC_K_ART_VARIABLES (article variable definitions and values), OKC_ART_VAR_SECTIONS (variable-to-section linkage), OKC_ARTICLE_ADOPTIONS (clause adoption between contracts/templates), OKC_SECTIONS_B (section definitions), OKC_TERMS_TEMPLATES_ALL and OKC_TEMPLATE_USAGES (term templates and their usage), OKC_REVIEW_UPLD_TERMS and OKC_REVIEW_VAR_VALUES (review-cycle uploaded terms and variable values), and PLITBLM (a standard Oracle PL/SQL interlocked table used for bulk operations). These tables support the article, variable, section, template, and review-merge functionality the package implements.

Usage Notes

OKC_TERMS_MULTIREC_GRP is invoked primarily from the Terms and Conditions authoring forms and template-management UI, and secondarily from concurrent programs and custom extensions that need to create or restructure multi-record term structures. It is referenced by four other packages, indicating it functions as a shared service layer within the OKC module. Custom code should call the documented procedures rather than manipulating the underlying tables directly, because the package enforces structure consistency, version tracking, and expert synchronization. The header comment (121.2, 2005/09/13) indicates the package source is mature and stable across 12.1.1 and 12.2.2.