Search Results g_insert_mode

Overview

The APPS.OKL_LESSEE_AS_VENDOR_PVT package body is a private (PVT) API belonging to the Oracle Lease and Finance Management (OKL) module within Oracle E-Business Suite. Its business purpose is to establish and maintain the relationship between a lessee and a corresponding supplier (vendor) record in the context of a lease or contract. In lease management scenarios, particularly those involving "pay as vendor" or pay-through arrangements, a lessee party may need to be represented as a vendor so that disbursements, payables, and financial settlements flow correctly to that party. This package encapsulates that logic, providing controlled insert and update operations that persist the lessee-as-vendor linkage while enforcing validation and messaging conventions consistent with the ETRM/OKL public and private API framework.

As a PVT (private) package, it is not intended for direct customer invocation. It is a supporting layer beneath higher-level public APIs and is referenced by two other packages within the application, indicating that the documented CREATE_LESSEE_AS_VENDOR and UPDATE_LESSEE_AS_VENDOR routines are consumed internally by related processing.

Key Procedures and Functions

The documented package exposes two procedures:

• CREATE_LESSEE_AS_VENDOR — Establishes a new association between a lessee and a vendor record. It is the insert-path entry point invoked when a lessee must be registered as a payable party for a contract. Validation enforces that the required vendor identifier is present before the record is committed.
• UPDATE_LESSEE_AS_VENDOR — Modifies an existing lessee-as-vendor association, allowing the vendor linkage on a contract party role to be corrected or reassigned. Its validation path differs from the create path, reflecting update-versus-insert mode semantics.

The package body also contains supporting validation logic, evidenced by a validate_vendor function that inspects the vendor identifier according to the operating mode (G_INSERT_MODE versus G_UPDATE_MODE). In insert mode the vendor ID must be neither null nor the missing-value sentinel OKL_API.G_MISS_NUM; in update mode only a null check applies. Failures raise G_EXCEPTION_HALT_VALIDATION and are translated to OKL_API.G_RET_STS_ERROR, while unexpected errors return OKL_API.G_RET_STS_UNEXP_ERROR with a message set via OKL_API.Set_Message. This pattern is standard across OKL private APIs.

Tables Accessed

According to the documented ETRM metadata, the package reads and writes through APPS synonyms of the following base tables:

• OKC_K_HEADERS_B — The contract header base table. The lessee-as-vendor relationship is anchored to a contract, so the package references the header to associate the vendor linkage with the correct contract.
• OKC_K_PARTY_ROLES_B — The contract party roles base table. This stores the parties participating in a contract and their roles. The lessee-as-vendor registration modifies the party role record so that the lessee is recognized as a payable counterparty.

These tables reside in the Oracle Contracts (OKC) core schema and are shared with the OKL lease application.

Usage Notes

Because this is a PVT-class API, it should not be called directly from custom code or PL/SQL. It is invoked indirectly through higher-level OKL public APIs and internal package logic; the metadata records two dependent packages that reference it. Typical invocation flows include lease authoring and contract party maintenance screens in the Lease Management responsibility, where adding or amending a lessee vendor requires the party role record to be synchronized. During upgrades or patches (for example, 12.1.1 to 12.2.2), the package version header indicates it has been stable since its original release, and no customer-level customization should wrap it. Developers troubleshooting vendor-assignment failures in lease contracts should inspect the underlying contract header and party role records rather than call this private API, and should rely on the public OKL API return-status conventions when diagnosing messages surfaced through OKL_API.Set_Message.