Search Results copy_lease_contract

Overview

OKL_COPY_CONTRACT_PUB is the public application programming interface for the contract and lease duplication facility within Oracle Enterprise Asset Management and the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. In releases 12.1.1 and 12.2.2 this package serves as the supported entry point through which a user or calling program creates a new lease, loan, or service contract by copying the structure, terms, and associated data of an existing source contract. The package encapsulates validation of copy eligibility, derivation of configuration defaults for the target contract, and the orchestration of subordinate copy operations that replicate components, lines, rules, party roles, and contract articles into the newly created agreement.

The package is classified as PUB, indicating that its procedures form part of the stable, externally callable API surface. It deliberately exposes only those signatures intended for consumption by forms, concurrent programs, and custom extensions, while delegating implementation detail to the companion OKL_COPY_CONTRACT_PVT private package. The source header identifies the file as OKLPCOPS.pls, last revised at version 120.2.

Key Procedures and Functions

The documented API comprises sixteen subprograms whose responsibilities are summarized below. Parameter lists are intentionally omitted, as the published signatures must be referenced directly from the package specification.

• COPY_LEASE_CONTRACT and COPY_LEASE_CONTRACT_NEW — the principal routines for duplicating a lease contract. The former performs the established copy operation; the latter carries the revised logic introduced for newer contract structures and is the variant typically invoked by current application flows.
• COPY_CONTRACT — a generalized entry point that copies a source contract of any supported class into a new target agreement.
• COPY_COMPONENTS — replicates the component records that define the financial and asset structure of the source contract.
• COPY_CONTRACT_LINES — duplicates the contract line detail associated with the source agreement.
• COPY_RULES — reproduces the accounting and processing rules attached to the original contract.
• COPY_PARTY_ROLES — copies the parties and their assigned roles so that the target contract retains the same counterparties and responsibilities.
• COPY_ARTICLES and COPY_LATEST_ARTICLES — copy contract terms and clauses, with the latter restricting the copy to the most recent version of each article.
• IS_COPY_ALLOWED and IS_SUBCONTRACT_ALLOWED — validation functions that determine whether the source contract is eligible for duplication or for treatment as a subcontract.
• DERIVE_LINE_STYLE — derives the line style attribute applied to the target contract.
• UPDATE_TARGET_CONTRACT — applies final attribute updates to the newly created contract.

Tables Accessed

The package operates against the OKL and OKC contract schema through APPS synonyms, reading the source contract header, component, line, rule, party role, and article tables and inserting corresponding rows for the target contract. Validation routines consult the same structures to establish copy eligibility. Where the metadata does not enumerate individual table names, the relevant objects should be confirmed against the package body and the OKL data model documentation.

Usage Notes

OKL_COPY_CONTRACT_PUB is most commonly invoked from the Lease and Finance Management contract entry forms when a user selects a copy action on an existing agreement, and from concurrent programs that perform bulk contract replication. Custom code should call only the PUB procedures, typically COPY_LEASE_CONTRACT_NEW, and should not call the private package directly. The package is referenced by sixteen other packages, confirming its role as a shared service. Callers must supply a valid source contract identifier, observe the IS_COPY_ALLOWED and IS_SUBCONTRACT_ALLOWED checks before initiating a copy, and handle the standard OKL_API error message constants declared in the package specification.