Search Results okl_contract_pub




Overview

OKL_CONTRACT_PUB is the public application programming interface for Oracle Lease and Finance Management (OKL), the EBS module that supports leasing, financing, and contract lifecycle processing. In Oracle EBS 12.1.1 and 12.2.2, the package body APPS.OKL_CONTRACT_PUB exposes a controlled, PL/SQL-callable entry point for creating, maintaining, and validating lease contract data without requiring direct DML against the underlying OKC and OKL base tables. Its object status is VALID and it is owned by the APPS schema, which is consistent with the seeded EBS API standard.

The package acts as a thin public wrapper over the private implementation package OKL_CONTRACT_PVT and coordinates calls into OKL_API, OKL_KHR_PVT, OKL_KLE_PVT, OKC_API, and OKL_OKC_MIGRATION_PVT. It also inherits standard EBS API error-handling and message infrastructure through FND_API and FND_MSG_PUB, allowing callers to use the conventional p_init_msg_list, x_return_status, and x_msg_count/x_msg_data conventions. The body contains 38 documented procedures and functions and is referenced by approximately 58 other database objects, confirming its role as a shared, foundational API within the leasing stack.

Key Procedures and Functions

The documented interface is organized into logical CRUD, locking, and validation groups:

Each mutating procedure follows the EBS API pattern of validating input, applying the change through the private package, and returning status and message information to the caller.

Tables Accessed

The documented table dependencies accessed through APPS synonyms are:

  • OKC_K_HEADERS_B — the core contract header base table in the Oracle Contracts (OKC) schema. OKL_CONTRACT_PUB reads and writes this table to persist contract header attributes, identifiers, and status.
  • PLITBLM — the standard EBS PL/SQL table used by FND_MSG_PUB to store validation and error messages generated during API execution.

Additional base tables such as contract lines and governance records are touched indirectly through OKL_CONTRACT_PVT and the OKC/OKL private packages listed as dependencies. OKL_CONTRACT_PUB is not referenced by any database object, meaning it sits at the top of the dependency chain as a public entry point.

Usage Notes

OKL_CONTRACT_PUB is typically invoked from Oracle Forms-based leasing setups, concurrent programs, migration or conversion routines, and custom PL/SQL integrations that need to create or maintain lease contracts. Because it is a PUB-classified API, callers should invoke it rather than issuing direct DML against OKC_K_HEADERS_B or other underlying tables; this preserves validation logic, MOAC/security handling, and message propagation. Standard practice is to pass an initialized message list, call the desired procedure, then check x_return_status and retrieve messages from FND_MSG_PUB when the return status is not SUCCESS. Locking procedures should be called before updates in concurrent processing scenarios to enforce concurrency control, and validation procedures are useful as a pre-commit check.