Search Results okl_contract_status_pub




Overview
Explore in AI Chat

Overview

OKL_CONTRACT_STATUS_PUB is the public API package body for Oracle Lease and Finance Management (OKL), the EBS module that manages lease and loan contracts within Oracle Enterprise Asset Management / ETRM. In Oracle EBS 12.1.1 and 12.2.2, this package is the supported external entry point for reading and changing the lifecycle status of lease contracts. Lease contracts pass through a defined status model (for example, entered, approved, active, terminated, and expired), and this package is the interface through which other EBS modules and custom extensions request a status query or transition without directly updating the underlying OKL tables. Its "PUB" classification marks it as a public, supported API; it delegates business validation and persistence to the companion private package OKL_CONTRACT_STATUS_PVT and the shared OKL_API and OKC_API error-handling utilities. In the shipped instance the object is owned by APPS and reported as VALID. The documented metadata shows it is referenced by 37 other packages, confirming that it is a widely consumed integration point in the lease status flow.

Key Procedures and Functions

Four documented subprograms constitute the public surface of the package:

  • GET_CONTRACT_STATUS — Returns the current status (and related status information) for a given lease contract. It is the read interface used by forms, concurrent programs, and custom code that need to test the status of a contract before acting on it.
  • UPDATE_CONTRACT_STATUS — Performs the primary status change on a lease contract. It validates the requested transition and handles the persistence of the new status. This is the standard API for programmatic status maintenance.
  • CASCADE_LEASE_STATUS — Propagates a status change from a parent lease contract to dependent or associated records, so that downstream entities remain consistent with the master contract status.
  • CASCADE_LEASE_STATUS_EDIT — The edit/maintenance variant of the cascade operation, used when the cascaded status values themselves must be corrected or re-derived rather than propagated as a wholesale change.

Parameter lists are not reproduced here; callers should obtain signatures from the package specification rather than reconstructing them.

Tables Accessed

The documented dependency information lists no directly named base tables; the package instead operates through APPS synonyms and the OKL API layer. All persistence of contract status is performed by delegated calls, principally into OKL_CONTRACT_STATUS_PVT, with error handling supplied by OKL_API and contract-level validation supplied by OKC_API. No tables are shown as being referenced back to this package; it is a pure consumer of the underlying OKL and OKC data model.

Usage Notes

This package is typically invoked from the Lease Management forms when a user submits or approves a contract, from concurrent programs that advance contract status in batch, and from customer extensions that must change or inspect contract status in a controlled manner. Because it is a PUB package and is referenced by 37 other packages, it is the recommended interface; direct DML against the underlying OKL status columns should be avoided. Calls should follow the standard EBS API conventions — initialize the API environment, pass a consistent p_api_version and p_init_msg_list, inspect x_return_status, and read messages from the API message stack rather than assuming success. Cascade operations should be invoked with care, as they touch dependent records beyond the single contract.