Search Results create_release_contract

Overview

OKL_RELEASE_PUB is the public (PUB) API package for Oracle Lease and Finance Management (OKL), the EBS module that manages lease and loan contracts, asset financing, and the associated accounting lifecycle. Its specific business function is to support the release of a contract line or associated instrument from an existing contract structure, producing a standalone release contract. Release processing is used when a lessee or lessor needs to separate, terminate, or restructure a portion of an active contract — for example, releasing returned or end-of-term assets so they can be disposed of, re-leased, or accounted for independently. The package exposes a versioned, standardized PL/SQL interface that forms, concurrent programs, and other EBS modules can call directly, with standard FND_API error handling and message-list conventions.

The package header constant declarations confirm its role as a published API: G_API_TYPE is '_PUB', G_SCOPE is '_PUB', and G_API_VERSION is 1.0. The body header reflects Bug 3948361 and an $Header of 120.3 (2005/10/30), indicating a long-stable API surface maintained across EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

• CREATE_RELEASE_CONTRACT — The main public entry point, and the object matching the user's search term. It creates a release contract from an existing contract header (identified by p_chr_id), taking a release reason code, a release description, a transaction date, and optional source transaction identification. It returns the new release contract's header ID (x_release_chr_id) along with a conversion/release record (x_tcnv_rec). A private API name and version are declared locally, a savepoint is set for rollback safety, and compatibility is validated through FND_API.Compatible_API_Call against the caller's p_api_version. The business logic itself is delegated to OKL_RELEASE_PVT.create_release_contract, keeping the public package a thin validation and message-handling wrapper. Standard x_return_status, x_msg_count, and x_msg_data outputs follow FND_API conventions.
• ACTIVATE_RELEASE_CONTRACT — The companion procedure that activates a previously created release contract, moving it into an active business state so subsequent lease accounting, billing, and asset processing can proceed against it.

Tables Accessed

The documented table reference is OKC_K_HEADERS_B, accessed through an APPS synonym. This is the core contract header table in the Oracle Contracts (OKC) schema, and the package uses it to validate and identify the source contract (p_chr_id is typed as OKC_K_HEADERS_B.ID%TYPE) and to establish the header of the newly created release contract, whose ID is returned in x_release_chr_id. Additional lease-specific table activity occurs inside the private OKL_RELEASE_PVT layer rather than in this public wrapper.

Usage Notes

APPLSYS/APPS-internal code and vertical-industry extensions should call the _PUB layer rather than OKL_RELEASE_PVT directly, because the public wrapper enforces API version compatibility, initializes the FND message stack when p_init_msg_list is OKC_API.G_FALSE-checked, wraps execution in the create_release_contract_pub savepoint, and raises FND_API.G_EXC_UNEXPECTED_ERROR on incompatibility. Typical invocation points include the Lease Management contract form, release-related concurrent programs, and custom integrations performing bulk or automated release processing. Callers must pass p_api_version, inspect x_return_status for FND_API.G_RET_STS_SUCCESS, and drain messages via FND_MSG_PUB when the status is not success. Because the package is marked as referenced by two other packages, it is a dependency point in the lease API stack, and any customization should preserve the documented signature and return-status contract.