Search Results post_split_contract

Overview

OKL_SPLIT_CONTRACT_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Oracle Lease and Finance Management (OKL) application family within ETRM. It exposes the contract split business process, allowing a single lease or loan contract to be divided into two or more successor contracts while preserving the financing and accounting relationships of the original instrument. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references resolve under the privileges of the calling schema rather than the package owner.

Contract splitting is used in leasing operations whenever a portion of an existing contract must be carved out and managed separately — for example, a partial asset sale, a mid-term restructure, or the reallocation of specific assets and payment schedules to a new contract number. The package encapsulates the validation, creation, and posting steps required to execute this operation transactionally across the underlying OKC and OKL base tables. The source header identifies the file as OKLPSKHS.pls and the version as 115.6, last updated in 2004, which is consistent with the long-standing API surface retained across EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes five documented procedures, all declared as PUBLIC and intended for external callers. Each procedure follows the standard EBS API convention of accepting p_api_version and p_init_msg_list, and returning x_return_status, x_msg_count, and x_msg_data for standard message-stack handling.

• SET_CONTEXT — Establishes the runtime application context (responsibility, application, and user identifiers) required before the split process can execute. This is typically invoked first so that subsequent calls inherit correct security and multi-org context.
• CHECK_SPLIT_PROCESS — Validates whether a given contract is eligible for splitting. It returns a process action indicator, a transaction identifier, and up to two child contract header identifiers, allowing the caller to determine the appropriate next step without mutating data.
• CREATE_SPLIT_CONTRACT — Performs the actual creation of the split structure, taking the source contract number and a collection of top-line rows, and returning the newly built top-line collection. The ktl_tbl_type subtype is anchored to OKL_SPLIT_CONTRACT_PVT.KTL_TBL_TYPE.
• POST_SPLIT_CONTRACT — Commits and posts the split, accepting the identifiers of the two newly created contracts and a commit flag, and finalizing the transaction in the database.
• CANCEL_SPLIT_PROCESS — Reverses or aborts an in-progress split for a specified contract identifier, restoring the pre-split state.

Tables Accessed

The package reads and writes the core contract tables through APPS synonyms. OKC_K_HEADERS_B is the base table for contract header records; it supplies the contract identifier, contract number, and the child header identifiers returned by the check and post routines, and receives the rows for the newly created contracts. OKL_TRX_CONTRACTS links contracts to their originating transactions and provides the transaction identifier returned by CHECK_SPLIT_PROCESS. Additional views such as OKC_K_HEADERS_V supply the contract number and ID type anchors used in the parameter declarations.

Usage Notes

OKL_SPLIT_CONTRACT_PUB is a PUB-classified API, meaning it is a supported integration point for customer and partner code, not merely an internal helper. It is invoked from the Lease Management contract forms, from concurrent programs that batch-process contract restructures, and from custom PL/SQL that automates splitting. Callers must invoke SET_CONTEXT before any processing procedure, then call CHECK_SPLIT_PROCESS to confirm eligibility, CREATE_SPLIT_CONTRACT to build the successor rows, and finally POST_SPLIT_CONTRACT to commit. CANCEL_SPLIT_PROCESS is used to back out an incomplete split. Standard practice is to check x_return_status against OKL_API.G_RET_STS_SUCCESS after each call and to read the message stack via x_msg_count and x_msg_data when errors occur. The package is referenced by one other package in the ETRM metadata, indicating it is a dependency in the broader OKL API chain rather than an isolated utility.