Search Results p_commit

Overview

The APPS.OKC_IMP_TERMS_TEMPLATES_PUB package body is a public (PUB) API within the Oracle E-Business Suite Contracts (OKC) module, specifically serving the Enterprise Contracts Terms and Templates (ETRM) functionality. Its primary business function is to provide a stable, publicly callable interface for importing, creating, updating, and deleting terms templates, template sections, articles, and deliverables — the structural building blocks of contract terms documents in Oracle Contracts.

In the 12.1.1 and 12.2.2 releases, this package acts as a thin public wrapper around the private implementation package OKC_IMP_TERMS_TEMPLATES_PVT. As shown in the source header (OKCPITTB.pls 120.1.12020000.2), each public procedure simply delegates to its private counterpart, passing along the caller's table-based parameters and the commit flag. This publish/private separation follows the standard Oracle EBS API architecture: the public package defines the supported interface, while the private package contains the actual business logic.

The user search term p_template_id appears in this package as an input parameter, most notably in CREATE_TEMPLATE_REVISION, where it identifies the source template from which a new revision or copy is generated. Other procedures operate primarily on collection (table) parameters rather than single template identifiers.

Key Procedures and Functions

The package exposes twelve documented procedures and functions:

• CREATE_TEMPLATE — Creates one or more terms templates via a template collection parameter.
• CREATE_ARTICLE — Creates articles belonging to terms templates.
• CREATE_SECTION — Creates sections within terms templates.
• CREATE_DELIVERABLE — Creates deliverables associated with terms templates or sections.
• UPDATE_TEMPLATE — Updates existing terms templates through a template collection.
• CREATE_TEMPLATE_REVISION — Produces a new revision of an existing template. Notably, it accepts p_template_id as an input, along with a p_copy_deliverables flag (defaulting to 'Y') and returns the new template identifier via x_new_template_id. This is the procedure most directly associated with the p_template_id search term.
• DELETE_ARTICLES, DELETE_SECTIONS, DELETE_DELIVERABLES — Remove the corresponding structural elements from templates.
• CREATE_TMPL_USAGE, UPDATE_TMPL_USAGE, DELETE_TMPL_USAGE — Manage template usage records, which associate templates with the business contexts in which they may be applied.

Each create/update routine supports a p_commit parameter defaulting to fnd_api.g_false, allowing callers to control transaction boundaries — a standard convention that permits atomic multi-step operations across several API calls.

Tables Accessed

The metadata identifies no explicitly documented base tables for this package. This is expected because the public package body contains no direct SQL; all table access occurs in the delegated private package OKC_IMP_TERMS_TEMPLATES_PVT. Based on the terms-template domain, the private implementation reads and writes the OKC terms template tables — including the template header, template section, article, and deliverable tables (for example, the OKC_TERMS_TEMPLATES and related child tables) — and the template usage tables. Because no APPS synonyms are documented in the supplied metadata, the specific table list should be confirmed against the private package body in the target instance.

Usage Notes

This public API is intended to be invoked by:

• Oracle Contracts forms — When users create, copy, revise, or delete terms templates and their sections, articles, or deliverables through the ETRM UI, the form invokes this API layer.
• Concurrent programs and batch imports — Bulk import of terms templates and template structures, including creation of template revisions via CREATE_TEMPLATE_REVISION using p_template_id.
• Custom integrations — External or customer-written code that must create or maintain templates should call this PUB package rather than the private package, ensuring upgrade-safe behavior.

Callers should pass the appropriate commit flag to control when work is committed, and should follow the collection-based parameter pattern for create/update operations. Because the package is referenced by zero other packages, it functions as a top-level entry point rather than an internal dependency.