Results for “okl_create_kle_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_CREATE_KLE_PUB is a public PL/SQL API package in the APPS schema belonging to the Oracle E-Business Suite Enterprise Contracts / Lease Management (ETRM) module. Its name derives from "create KLE," referring to the creation of contract lines and line-level asset information used in lease and financing agreements. In EBS 12.1.1 and 12.2.2 it serves as the primary public entry point through which lease contract structure is assembled and maintained — establishing finance-capital cost information, add-on lines, party roles, all-lines records, interest-bearing (internally billed) lines, and asset line details.

The package is classified as a PUB (public) API, indicating that it is intended for external invocation rather than being an internal implementation artifact. It is a thin public wrapper: the documented metadata shows it depends on private implementation packages such as OKL_CREATE_KLE_PVT, OKL_KLE_PVT, OKL_ASD_PVT, OKL_ITI_PVT, OKL_TAL_PVT, and OKL_TAS_PVT, along with Oracle Contracts foundation packages OKC_API, OKL_API, and FND_API. It also references the OKC contract views OKC_K_HEADERS_V, OKC_K_LINES_V, and OKC_LINE_STYLES_V, confirming that it operates on the shared contract-line model.

Key Procedures and Functions

The documented interface exposes thirteen procedures, grouped functionally as follows:

• Finance capital cost: UPDATE_FIN_CAP_COST updates the finance capital cost associated with a lease contract.
• Add-on line maintenance: CREATE_ADD_ON_LINE, UPDATE_ADD_ON_LINE, and DELETE_ADD_ON_LINE provide the full lifecycle for add-on lines attached to a lease.
• Party role maintenance: CREATE_PARTY_ROLES_REC and UPDATE_PARTY_ROLES_REC create and amend party role records linked to the contract or line.
• All-line maintenance: CREATE_ALL_LINE and UPDATE_ALL_LINE create and modify contract lines across line styles.
• Interest-bearing line maintenance: CREATE_INTS_IB_LINE, UPDATE_INTS_IB_LINE, and DELETE_INTS_IB_LINE manage interest-bearing internally billed lines.
• Asset line details: CREATE_ASSET_LINE_DETAILS and UPDATE_ASSET_LINE_DETAILS create and maintain the asset-specific detail rows associated with a contract line.

Each procedure follows standard EBS API conventions, relying on FND_API for message handling and returning standard API status codes rather than raising raw exceptions. Parameter lists are not documented in the metadata and should be confirmed against the live package specification in the target instance.

Tables Accessed

The documented metadata lists one table accessed through an APPS synonym: PLITBLM, an internal EBS table used for temporary or interim line data within the leases/contracts processing chain. The remaining persistence is performed indirectly through the OKC contract header, line, and line-style views (OKC_K_HEADERS_V, OKC_K_LINES_V, OKC_LINE_STYLES_V) and through subordinate PVT packages that write the lease contract line tables. OKL_TXL_ASSETS_V is referenced in the dependency information, indicating that asset and tax line data is read as part of asset line processing.

Usage Notes

OKL_CREATE_KLE_PUB is normally invoked from lease and financing business flows rather than directly by end users. It is referenced by five other packages, including OKL_CREATE_KLE_PUB_W (the workflow wrapper), OKL_EQUIPMENT_EXCHANGE_PVT, OKL_LA_ASSET_PVT, OKL_OPEN_INTERFACE_PVT, and OKL_SERVICE_INTEGRATION_PVT, which reflects its role in equipment exchange, lease asset, open interface, and service-integration processes.

Typical invocation is from these parent packages, from lease-related forms, or from concurrent programs that import and restructure lease contracts. Custom development should treat this as a supported public API, call the procedures in the required sequence (for example, create a line before creating its asset line details), and inspect the returned API status and message stack instead of relying on exception handling. Because behavior can differ between 12.1.1 and 12.2.2, the package specification and dependency chain should be validated in each target instance before use.