Search Results okl_release_pvt




Overview
Explore in AI Chat

Overview

OKL_RELEASE_PVT is a private PL/SQL package in the APPS schema that supports the Oracle Lease and Finance Management (OKL) release processing flow within Oracle E-Business Suite 12.1.1 and 12.2.2. Release processing governs the termination or buyout of an existing lease contract before its scheduled maturity, allowing a lessee to exit the agreement through a defined financial settlement. This package encapsulates the internal business logic that creates, validates, and activates the release contract generated during that process, and it computes the expected cost associated with the early termination.

As a private (PVT) package, OKL_RELEASE_PVT is not intended for direct invocation by external integrations. It is the implementation layer beneath the public API OKL_RELEASE_PUB, which exposes the supported entry points for callers. The package is documented with a status of VALID and carries an API classification of PVT, confirming its role as internal infrastructure rather than a published interface.

Key Procedures and Functions

The package exposes four documented program units:

  • CREATE_RELEASE_CONTRACT — Constructs the release contract record from the source lease agreement, deriving the header, line, and governance structures required to represent the termination or buyout transaction.
  • VALIDATE_RELEASE_CONTRACT — Applies the business validation rules that must be satisfied before a release contract can proceed, checking contract consistency and related setup conditions.
  • ACTIVATE_RELEASE_CONTRACT — Transitions a validated release contract into active status, triggering the downstream accounting and asset impacts associated with the settlement.
  • CALCULATE_EXPECTED_COST — Computes the expected cost of the release, drawing on the payment schedule, asset, and depreciation data required to quantify the buyout or termination amount.

Tables Accessed

The package reads and writes through APPS synonyms across several EBS schemas. Core contract data is held in OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_PARTY_ROLES_B, OKC_LINE_STYLES_B, and OKC_GOVERNANCES, which together represent the contract header, lines, party roles, line styles, and governance terms. Financial settlement data is sourced from AR_PAYMENT_SCHEDULES_ALL to establish the stream of payments being settled. Fixed asset information is drawn from FA_ADDITIONS, FA_ADDITIONS_B, FA_BOOKS, FA_BOOK_CONTROLS, and FA_DEPRN_PERIODS, which supply asset identification, book configuration, and depreciation period context needed to value leased assets at release. Customer identity data is resolved through HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_ACCT_SITES_ALL.

Usage Notes

OKL_RELEASE_PVT is invoked indirectly through OKL_RELEASE_PUB, which is the documented public wrapper for release processing. It is referenced by four other packages, including OKL_CONTRACT_BOOK_PVT, OKL_CREATE_KLE_PVT, and OKL_RELEASE_PVT_W, indicating participation in contract booking, KLE (lease) creation, and related release workflows. The package depends on shared OKL and OKC utilities such as OKL_API, OKC_API, OKL_CONTRACT_PUB, OKL_KHR_PVT, OKL_OKC_MIGRATION_PVT, OKL_TCN_PVT, and OKL_TRX_CONTRACTS_PVT, and on the STANDARD package.

Because the package is private, customizations should target OKL_RELEASE_PUB rather than OKL_RELEASE_PVT directly. Direct calls bypass supported validation and are vulnerable to changes between releases, particularly across the 12.1.1 to 12.2.2 upgrade path where private package signatures are not guaranteed to remain stable.