Search Results okl_copy_contract_pvt




Overview
Explore in AI Chat

Overview

OKL_COPY_CONTRACT_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) Lease Management / Contracts (OKL) module. Its primary business function is to support the duplication of existing lease and service contracts, or selected portions of them, into new contracts. This "copy contract" capability allows users to rapidly create new agreements by reusing the structure, rules, components, party roles, articles, and product options of a source contract, rather than re-entering all configuration data manually. The package is classified as a private (PVT) API, meaning it is intended for internal use by other OKL packages and forms rather than as a public, externally supported interface. It relies on type definitions (subtypes such as clev_rec_type, chrv_rec_type, klev_rec_type, and khrv_rec_type) inherited from OKL_OKC_MIGRATION_PVT and OKL_CONTRACT_PUB, which define the record and table structures used to pass contract, line, and version data between procedures.

Key Procedures and Functions

The package exposes 14 documented procedures and functions that collectively implement the copy workflow:

  • IS_COPY_ALLOWED — Evaluates whether the source contract is eligible to be copied, applying business rules that gate the copy operation.
  • IS_SUBCONTRACT_ALLOWED — Determines whether a sub-contract may be copied under the governing conditions.
  • UPDATE_TARGET_CONTRACT — Applies any required updates to the newly created target contract after the copy completes.
  • DERIVE_LINE_STYLE — Derives the appropriate line style for copied contract lines.
  • COPY_COMPONENTS — Copies the components associated with the source contract.
  • COPY_CONTRACT — The primary entry point that orchestrates copying of a full contract.
  • COPY_LEASE_CONTRACT and COPY_LEASE_CONTRACT_NEW — Specialized routines for copying lease contracts, with the "NEW" variant reflecting a revised implementation path.
  • COPY_CONTRACT_LINES — Copies the individual lines belonging to the source contract, which is the operation most directly associated with the search term "copy_contract_lines."
  • COPY_RULES — Copies the pricing, accounting, or governance rules attached to the contract.
  • COPY_PARTY_ROLES — Copies the party role assignments (customer, lessee, and related roles) to the target contract.
  • COPY_ARTICLES and COPY_LATEST_ARTICLES — Copy contractual articles or clauses; the latter targets only the most recent versions.
  • COPY_PRODUCT_OPTIONS — Copies configured product options for the contract.

Tables Accessed

The package reads and writes against several Oracle Asset (FA), Trading Community (HZ), and Contracts (OKC) tables accessed through APPS synonyms. FA_ADDITIONS_B and FA_ADDITIONS_TL supply asset identification and translated asset descriptions; FA_BOOKS, FA_BOOK_CONTROLS, FA_METHODS, and FA_FLAT_RATES provide depreciation book, control, and rate information relevant to leased assets. FA_DISTRIBUTION_HISTORY contributes asset distribution records. GL_DAILY_CONVERSION_TYPES supports currency conversion lookups. HZ_LOCATIONS, HZ_PARTY_SITES, and HZ_PARTY_SITE_USES resolve party addresses and site usages for the parties involved. MTL_SYSTEM_ITEMS identifies inventory items linked to contract lines, while OKC_CONTACTS and OKC_GOVERNANCES supply contract contacts and governance rules.

Usage Notes

OKL_COPY_CONTRACT_PVT is a private package and should not be called directly by external customizations unless no public alternative exists. It is typically invoked from the Lease Management contract entry forms and from other OKL packages that implement copy, versioning, or migration flows; the metadata indicates it is referenced by four other packages. The COPY_CONTRACT procedure acts as the orchestration entry point, internally invoking the specialized copy routines. Because it inherits migration subtypes and constants from OKL_API, OKL_CONTRACT_PUB, and OKL_OKC_MIGRATION_PVT, callers must pass the corresponding record and table types. Standard OKL message constants are defined for error handling. As with all private APIs, behavior is subject to change between releases, and the "$Header" revision (120.3) reflects an older, largely noship-stable implementation still present in 12.1.1 and 12.2.2.