Search Results update_program

Overview

The APPS.OKL_VENDOR_PROGRAM_PUB package body is the public API layer for Oracle Lease and Finance Management (OLFM/OKL) vendor program processing in Oracle E-Business Suite 12.1.1 and 12.2.2. A vendor program represents a financing arrangement established with an external vendor or partner under which lease contracts are originated, funded, or guaranteed. This package exposes the vendor program lifecycle operations to external callers — forms, concurrent programs, workflows, and custom extensions — while delegating the substantive business logic to the private package OKL_VENDOR_PROGRAM_PVT.

The package follows the standard EBS PL/SQL API architecture. Each public procedure is a thin wrapper that initializes the message stack, invokes the corresponding private procedure, interprets the returned status (FND_API.G_RET_STS_SUCCESS, G_RET_STS_ERROR, or G_RET_STS_UNEXP_ERROR), and raises the matching exception so the caller can trap and handle failures consistently. Message counting and retrieval are performed through FND_MSG_PUB, and the private layer is invoked using named notation for clarity and forward compatibility.

Key Procedures and Functions

• CREATE_PROGRAM — Creates a new vendor program record. It accepts a program header record, an optional parent agreement number, and returns both the standard header record and the OKL-specific key header record. This is the entry point for establishing a vendor program prior to associating lease contracts with it.
• UPDATE_PROGRAM — Modifies an existing vendor program. This is the procedure most frequently targeted by the search term "update_program," and is the supported mechanism for changing vendor program attributes such as dates, amounts, status, and related descriptive fields after initial creation.
• IS_PROCESS_ACTIVE — A query function that reports whether a given vendor program process is currently active. It is commonly used as a guard before initiating further processing, allowing callers to avoid conflicting or duplicate operations against an in-flight workflow activity.

All three entry points are classified as PUB APIs, meaning they are supported for external invocation and are subject to Oracle's public API compatibility guarantees.

Tables Accessed

The package references the following tables through APPS synonyms:

• OKC_K_PROCESSES — Stores the runtime process instances associated with contract and vendor program activity. IS_PROCESS_ACTIVE queries this table to determine whether a process is still open.
• OKC_PROCESS_DEFS_B — Holds the process definitions that describe the available process types. It is joined with the process instance data to resolve the definition governing a given vendor program activity.
• WF_ITEMS — The Oracle Workflow runtime item table. It is consulted to correlate vendor program processing with the underlying workflow item that drives notifications, approvals, and status transitions.

Usage Notes

OKL_VENDOR_PROGRAM_PUB is typically invoked from the OLFM vendor program maintenance forms, from concurrent programs that mass-create or update vendor programs, and from custom PL/SQL that must create or amend vendor programs in a supported manner. Callers should always supply p_init_msg_list as FND_API.G_TRUE at the outermost entry point and G_FALSE for nested calls, then inspect x_return_status and drain the message stack with FND_MSG_PUB.Count_and_get after any non-success return. Because the package is referenced by six other packages, modifications should be limited to those that preserve existing signatures; the public contract must remain stable across 12.1.1 and 12.2.2 environments.