Search Results okl_gtt_pvt




Overview
Explore in AI Chat

Overview

OKL_GTT_PVT is a private PL/SQL package body in the APPS schema that supports the Global Template Transfer (GTT) functionality within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. GTT enables the propagation of lease template definitions and template set configurations across operating units and business entities, ensuring consistent contract and lease structures throughout a multi-org deployment. Because the package is classified as a private (PVT) API, it is intended for internal consumption by the OKL application layer rather than as a published integration interface.

The package forms part of the OKL State Transition / template generation toolset, working alongside OKL_ST_GEN_TEMPLATES and OKL_ST_GEN_TMPT_SETS. It depends on shared infrastructure such as FND_API and FND_GLOBAL for error handling and session context, MO_GLOBAL for multi-org security, OKC_API and OKC_P_UTIL for contract core utilities, OKL_API and OKL_ACCOUNTING_UTIL for lease-specific services, and PLITBLM for PL/SQL table list management.

Key Procedures and Functions

The documented program units within OKL_GTT_PVT cover the full standard private-API lifecycle for template transfer records:

  • QC — A quality-control/consistency validation routine that verifies the integrity of template data prior to processing. It is invoked before insert, update, or copy operations to confirm that required attributes and relationships are valid.
  • CHANGE_VERSION — Manages concurrency control by evaluating and updating the object version identifier on a template record, protecting against lost updates when multiple sessions attempt to modify the same row.
  • API_COPY — Performs row duplication logic, replicating an existing template or template set record as part of a copy or transfer operation, typically assigning new identifiers and resetting version attributes.
  • INSERT_ROW — Creates a new template transfer record in the underlying tables after validation via QC. It encapsulates column defaults, WHO columns, and DML against the GTT tables.
  • UPDATE_ROW — Modifies an existing record, applying the changed attributes and refreshing the version indicator, subject to the checks performed by CHANGE_VERSION.
  • DELETE_ROW — Removes a template transfer record, managing referential dependencies and any associated child rows to preserve data integrity.

These units are exposed only to other OKL packages; the metadata records nine documented procedures or functions in total, with the additional units remaining internal helpers of the same private framework.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • OKL_ST_GEN_TEMPLATES — Stores state transition / template generation definitions. OKL_GTT_PVT inserts, updates, deletes, and copies rows here as part of template transfer operations.
  • OKL_ST_GEN_TMPT_SETS — Stores template set groupings used to bundle multiple templates for generation. The package maintains set membership and header records here.
  • PLITBLM — The Oracle PL/SQL table list management package used for ID list handling in bulk DML operations; it is referenced as a supporting utility rather than a business table.

Usage Notes

OKL_GTT_PVT is not referenced by any database object directly and is not exposed as a public integration API. It is invoked indirectly by higher-level OKL packages — the metadata records that it is referenced by six other packages — which drive global template transfer from the Lease Management user interface and accompanying concurrent programs. Typical invocation scenarios include transferring lease templates between operating units, seeding templates during implementation, and bulk maintenance of template sets. Custom developers should not call these private routines directly; instead, the supported public OKL accounting and template APIs should be used, since signatures, validation behavior, and versioning semantics of OKL_GTT_PVT are subject to change between releases. The package is validated and present in both Oracle EBS 12.1.1 and 12.2.2, and the behavior described here applies to either release.