Search Results okl_lla_range_check
Overview
OKL_LESSEE_AS_VENDOR_PVT is a private PL/SQL package in the Oracle Lease and Finance Management (OKL) application, owned by APPS and classified as a PVT (private) API. Its business purpose is to support the creation and maintenance of a supplier or vendor record that corresponds to a lessee on a lease contract. In leasing operations, the lessee is frequently required to act as the vendor of record — for example, when the lessee supplies goods or equipment that the leasing entity then leases back to that same party. This package encapsulates the logic needed to establish and update that lessee-as-vendor relationship within the contract structure, shielding callers from the underlying data model of the Oracle Contracts (OKC) core tables.
The package is declared with AUTHID CURRENT_USER and defines a standard set of global constants following ETRM conventions. These include G_PKG_NAME, the return status constants G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR, the exceptions G_EXCEPTION_ERROR and G_EXCEPTION_UNEXPECTED_ERROR, and the error message tokens G_UNEXPECTED_ERROR, G_SQLERRM_TOKEN, and G_SQLCODE_TOKEN. The presence of the constant G_LLA_RANGE_CHECK, mapped to the message name OKL_LLA_RANGE_CHECK, indicates that the package performs validation on values supplied by the caller and reports a range-check failure when a value falls outside acceptable bounds. Other validation constants include G_NOT_UNIQUE (OKL_LLA_NOT_UNIQUE) and G_REQUIRED_VALUE (OKL_REQUIRED_VALUE).
Key Procedures and Functions
The package exposes two documented public procedures:
- CREATE_LESSEE_AS_VENDOR — Creates the lessee-as-vendor relationship. This procedure validates the supplied data, establishes the required vendor association against the lease contract, and returns a standard status value indicating success, a handled error, or an unexpected error.
- UPDATE_LESSEE_AS_VENDOR — Modifies an existing lessee-as-vendor record. It applies changes to a previously created relationship, again performing the package's standard validation and returning an ETRM status code with associated error tokens where applicable.
Both procedures rely on the shared exception and constant definitions at package level, ensuring consistent error handling and message resolution through the OKL message dictionary.
Tables Accessed
The package operates on the core Oracle Contracts tables exposed through APPS synonyms:
- OKC_K_HEADERS_B — the contract header base table, holding the lease contract header record. The package references this to associate the lessee-as-vendor relationship with a specific contract.
- OKC_K_PARTY_ROLES_B — the contract party roles base table, which records the parties and the roles they play on a contract. The lessee-as-vendor designation is materialised here as a party role assignment.
Usage Notes
As a PVT package, OKL_LESSEE_AS_VENDOR_PVT is not intended to be called directly by end users or external integrations. It is invoked by the public OKL API layer, which marshals user-supplied data, performs public-level validation, and then delegates to this private package for the core insert and update operations against the OKC contract tables. The documented metadata shows it is referenced by two other packages, consistent with this layered design.
Typical invocation paths include Oracle Forms UI flows that capture vendor or supplier information for a lessee on a lease, and any concurrent or programmatic process that programmatically establishes the lessee-as-vendor relationship. Custom code should call the public OKL API rather than this private package to preserve supported behaviour and error handling.
-
PACKAGE: APPS.OKL_LESSEE_AS_VENDOR_PVT
12.2.2
-
PACKAGE: APPS.OKL_LESSEE_AS_VENDOR_PVT
12.1.1
-
PACKAGE: APPS.OKL_FUNDING_CHECKLIST_PVT
12.1.1
-
PACKAGE: APPS.OKL_FUNDING_CHECKLIST_PVT
12.2.2
-
PACKAGE: APPS.OKL_INTERNAL_BILLING_PVT
12.1.1
-
PACKAGE: APPS.OKL_INTERNAL_BILLING_PVT
12.2.2
-
PACKAGE: APPS.OKL_BILLING_UTIL_PVT
12.1.1
-
PACKAGE: APPS.OKL_BILLING_UTIL_PVT
12.2.2
-
PACKAGE: APPS.OKL_CREDIT_CHECKLIST_PVT
12.2.2
-
PACKAGE: APPS.OKL_CREDIT_CHECKLIST_PVT
12.1.1
-
PACKAGE: APPS.OKL_CHECKLIST_PVT
12.2.2
-
PACKAGE: APPS.OKL_CHECKLIST_PVT
12.1.1
-
APPS.OKL_CREDIT_CHECKLIST_PVT dependencies on FND_PROFILE
12.1.1
-
APPS.OKL_FUNDING_CHECKLIST_PVT dependencies on FND_PROFILE
12.1.1
-
APPS.OKL_INTERNAL_BILLING_PVT dependencies on FND_PROFILE
12.1.1
-
APPS.OKL_INTERNAL_BILLING_PVT dependencies on FND_PROFILE
12.2.2
-
APPS.OKL_CREDIT_CHECKLIST_PVT dependencies on FND_PROFILE
12.2.2
-
APPS.OKL_FUNDING_CHECKLIST_PVT dependencies on FND_PROFILE
12.2.2
-
APPS.OKL_BILLING_UTIL_PVT dependencies on FND_PROFILE
12.2.2
-
APPS.OKL_BILLING_UTIL_PVT dependencies on FND_PROFILE
12.1.1
-
APPS.OKL_LESSEE_AS_VENDOR_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_LESSEE_AS_VENDOR_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_INTERNAL_BILLING_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_INTERNAL_BILLING_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_FUNDING_CHECKLIST_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_FUNDING_CHECKLIST_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_BILLING_UTIL_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_BILLING_UTIL_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_CREDIT_CHECKLIST_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_CREDIT_CHECKLIST_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_CHECKLIST_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_CHECKLIST_PVT dependencies on OKL_API
12.2.2
-
PACKAGE BODY: APPS.OKL_CREDIT_PUB
12.1.1
-
PACKAGE BODY: APPS.OKL_CREDIT_PUB
12.2.2
-
APPS.OKL_CREDIT_PUB dependencies on OKL_API
12.1.1
-
APPS.OKL_CREDIT_PUB dependencies on OKL_API
12.2.2
-
PACKAGE BODY: APPS.OKL_FUNDING_PVT
12.1.1
-
PACKAGE BODY: APPS.OKL_FUNDING_PVT
12.2.2
-
APPS.OKL_FUNDING_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_FUNDING_PVT dependencies on OKL_API
12.2.2