Search Results okc_xprt_template_rules_s

Overview

The APPS.OKC_XPRT_TMPL_RULE_ASSNS_PVT package body is a private (PVT) API belonging to the Oracle E-Business Suite ETRM (Enterprise Contracts) module, specifically the OKC (Contracts Core) schema family. It governs the association between reusable template rules and the terms templates that consume them. In Oracle Contracts, an expression template or terms template is assembled from one or more rule headers, and each rule header must be attached to a template through an assignment record. This package provides the programmatic mechanism for creating, removing, and reconciling those assignments without requiring direct DML against the underlying rule-association tables.

Because the package is classified as PVT, it is an internal implementation layer. Other public ETRM APIs and the template maintenance forms call into it rather than exposing its logic directly to end users or external integrations. Its documented status is VALID in both 12.1.1 and 12.2.2, and the metadata records no dependent database objects referencing it, confirming that it sits beneath the public contract-management API surface rather than acting as an entry point itself.

Key Procedures and Functions

The package exposes three documented procedures, all centered on the lifecycle of template-to-rule assignments:

• COPY_TEMPLATE_RULE_ASSNS — Duplicates the set of rule associations from a source template to a target template. This supports template versioning and the creation of derivative templates, where an administrator copies an existing terms template and expects its rule wiring to travel with it.
• DELETE_TEMPLATE_RULE_ASSNS — Removes the association records that bind rules to a given template. It is used when a rule is detached from a template, when a template is being reorganized, or when assignments must be cleared before a redefinition.
• MERGE_TEMPLATE_RULE_ASSNS — Reconciles an incoming set of rule assignments against the existing configuration, inserting new associations, updating changed ones, and retaining unchanged ones. This is the standard Oracle API "merge" idiom, allowing callers to pass a desired end state rather than individual row operations.

No parameter lists are documented in the ETRM metadata, so signatures should be confirmed by inspecting the package specification in the target environment before invoking it from custom code.

Tables Accessed

The package reads and writes the core ETRM expression-template structures. OKC_TERMS_TEMPLATES_ALL holds the multilingual template definitions and identifies valid source and target templates. OKC_XPRT_RULE_HDRS_ALL stores the rule headers being associated. OKC_XPRT_TEMPLATE_RULES and its synonym-visible sequence-backed counterpart OKC_XPRT_TEMPLATE_RULES_S carry the rule definitions, while OKC_XPRT_QUESTION_ORDERS and OKC_XPRT_QUESTION_ORDERS_S store the ordered question structures that rules evaluate. PLITBLM is the standard Oracle PL/SQL integer-table type used to pass collections of identifiers into the private APIs. The dependency list also includes FND_API, FND_GLOBAL, FND_LOG, FND_MSG_PUB, and OKC_API, indicating that the package follows the OAF-style API contract: it resolves the current user and login, seeds the message stack, and raises errors through FND_MSG_PUB rather than returning raw Oracle exceptions.

Usage Notes

This package is not intended for direct end-user invocation. It is normally called from the Contract Terms and Templates setup forms in ETRM, from concurrent programs that deploy or migrate template definitions, and from the public OKC template APIs that wrap it. Custom code should locate the corresponding public API or the documented template setup flow rather than calling this private body directly, because private APIs can change between patch levels without notice. Where direct invocation is unavoidable, callers should precede the call with FND_GLOBAL.APPS_INITIALIZE, inspect the message stack afterward for errors, and treat any FND_API.G_EXC_ERROR or G_EXC_UNEXPECTED_ERROR return as a failure requiring rollback. Because the metadata records the package as referenced by three other packages and referencing none of the public ETRM entry points, it should be treated strictly as a subordinate utility layer within the Contracts template framework.