Search Results okl_copy_asset_pub




Overview
Explore in AI Chat

Overview

OKL_COPY_ASSET_PUB is a public PL/SQL API package in the Oracle E-Business Suite (EBS) Applications (APPS) schema, belonging to the Oracle Lease and Finance Management (OKL) module of Oracle Enterprise Contracts / ETRM. It provides the programmatic interface for copying asset lines between contract lines and contracts. Asset lines represent the leased assets attached to a contract line, and the ability to copy them is fundamental to lease origination, contract restructuring, renewals, and template-based contracting.

The package is declared AUTHID CURRENT_USER, meaning executing privileges and name resolution are evaluated against the calling schema, which is standard for public EBS APIs that are called from forms, concurrent programs, and custom extensions. Internally, OKL_COPY_ASSET_PUB delegates to the private package OKL_COPY_ASSET_PVT for the actual copy logic, exposing a thin, stable public surface. It shares the klev_tbl_type subtype definition with the private package for passing collections of contract line entity identifiers.

The core business purpose is to duplicate asset line records — and optionally the associated line-level parties and reference information — from a source contract line (identified by a CLE_ID, contract line entity identifier) to a target contract line or contract. A notable capability is the ability to copy assets into a contract created as a template, as signalled by the g_to_template_yn flag. This supports the creation of reusable contract templates that pre-populate standard asset structures.

Key Procedures and Functions

  • COPY_ASSET_LINES — The primary copy routine. It accepts a source contract line entity identifier and a target contract line or contract, along with control flags that govern whether line-level parties are copied and whether renewal references are regenerated. It returns the identifier of the newly created target contract line. An overloaded form accepts a PL/SQL collection of source CLE_IDs rather than a single one, supporting bulk copy of multiple asset lines in a single invocation; in this variant the API returns a corresponding collection of target CLE_IDs.
  • COPY_ALL_LINES — A convenience wrapper that copies all lines associated with a source context into a target contract. It accepts the same control parameters (template indicator, copy reference, party-copy indicator, renewal-reference indicator) and a collection of source CLE_IDs, applying the copy operation across the entire set. This is the entry point of choice when the intent is to replicate a complete contract structure.

Both procedures follow the standard EBS API convention: p_api_version, p_init_msg_list, and the x_return_status / x_msg_count / x_msg_data output parameters for error handling and message propagation. The p_trans_type parameter distinguishes the transaction context of the copy.

Tables Accessed

The documented table reference for this package is PLITBLM, an Oracle Contracts (OKC) storage table for line-level information. Through the private package, asset copy operations also interact with the OKC_K_LINES_V view, from which the package derives contract line identifiers (CLE_ID) and contract identifiers (CHR_ID); global variables g_from_cle_id, g_to_cle_id, g_to_chr_id and the collection g_from_cle_id_tbl are anchored to columns of that view. The writes create new rows representing the copied asset lines, their party relationships (when p_copy_line_party_yn is enabled), and renewal reference data (when p_renew_ref_yn is set).

Usage Notes

OKL_COPY_ASSET_PUB is a public, supported API and is referenced by seven other packages within the ETRM schema, indicating it serves as a foundational building block for higher-level lease and contract operations such as renewals, quotes, and contract authoring flows. Typical invocation paths include the Oracle Lease Management forms when a user copies a contract or line, and concurrent programs that batch-generate contracts from templates. Custom code should call the public package rather than the private partner, always supply a valid p_api_version, check x_return_status against OKC_API.G_RET_STS_SUCCESS, and surface messages from the x_msg_data stack. Because the package runs AUTHID CURRENT_USER, custom schemas must be granted execute on OKL_COPY_ASSET_PUB and appropriate privileges on the underlying OKC tables.