Results for “create_program”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.OKL_VENDOR_PROGRAM_PUB_W package is a public API wrapper belonging to the Oracle Contracts Core (OKL) module of Oracle E-Business Suite. Its role is to expose a stable, versioned interface for creating and maintaining vendor program records — the contractual and financial arrangements established between a lessor or financing entity and its vendor partners. In the leasing and financial services lifecycle supported by OKL, vendor programs serve as the parent constructs that govern pricing, rate structures, and program-specific terms applicable to individual lease or loan agreements. The "_PUB_W" suffix identifies the package as a published wrapper that insulates calling code from the underlying implementation, allowing Oracle to evolve internal logic without breaking integrations. The package header carries a version reference of 120.8 dated 2005/12/29, indicating a long-standing, stable interface that predates the 12.1.1 and 12.2.2 releases in which it continues to be shipped. Both releases include this wrapper as part of the standard APPS schema installation.

Key Procedures and Functions

The documented public interface comprises two procedures:

• CREATE_PROGRAM — Creates a new vendor program record. It accepts the standard Oracle API control parameters (API version, initialization flag, return status, message count, and message data) plus a bulk set of attributes describing the program, including descriptive fields, effective dates, numeric configuration values, and status indicators. A parent agreement number parameter allows the new program to be associated with an existing parent agreement. The procedure returns a comprehensive set of output parameters, including numeric identifiers and status values for the created program, date fields, and numerous descriptive attributes reflecting the persisted record after creation.
• UPDATE_PROGRAM — Modifies an existing vendor program. It follows the same API conventions and parameter-family structure as CREATE_PROGRAM, allowing callers to change program attributes, dates, and status values while returning the resulting state of the record.

Both procedures follow Oracle's standard API error-handling pattern: callers inspect x_return_status for success, unexpected error, or expected error conditions, and use x_msg_count and x_msg_data (or the message stack via FND_MSG_PUB) to retrieve diagnostic detail. No parameter lists are reproduced here beyond what the documented header confirms; consumers should reference the installed package specification for exact signatures.

Tables Accessed

The ETRM metadata identifies no tables referenced through APPS synonyms for this package. In practice, OKL vendor program APIs operate against the OKL program tables — principally OKL_PROGRAMS and its related entities, such as program rules and program-vendor associations — which store the program definition, effective dating, and linkage to parent agreements. Because the documented metadata does not enumerate these tables, integrators should confirm actual dependencies by inspecting the package body on their specific instance, and must not assume the table list is limited to the public synonym view.

Usage Notes

This package is typically invoked from Oracle Forms-based setup and maintenance screens within the Contracts Core module, where users define and revise vendor program terms. It may also be called by concurrent programs that mass-create or migrate program definitions, and by customer extensions or integrations that need to establish vendor programs programmatically during data conversion or interface from external leasing systems. Recommended usage includes initializing the message list, supplying a valid API version, checking return status immediately after each call, and committing only after validation of returned output parameters. Because the wrapper was introduced long before 12.1.1 and remained unchanged through 12.2.2, custom code written against it remains portable across both releases. Note that the search term "office 2021 oem key" is unrelated to this object; this documentation addresses only the OKL vendor program API.