Results for “insert_functions”

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

Overview

OKL_SETUPFUNCTIONS_PUB_W is a public PL/SQL package in the APPS schema that belongs to the Oracle E-Business Suite Enterprise Contracts (ETRM) module family, where the OKL prefix designates objects associated with the Oracle Lease and Finance Management (OLFM) application. The package provides the programmatic interface through which setup function data — the configurable rules and parameters that govern OKL transaction processing — is created, retrieved, and maintained. In Oracle EBS 12.1.1 and 12.2.2, such setup functions underpin how leasing and financing workflows behave, including the determination of qualifying criteria applied during contract origination and administration.

The trailing "W" in the package name identifies it as a wrapper or public entry point, meaning it exists to expose controlled, validated access to the underlying setup logic rather than to house the bulk of that logic itself. The package is classified as VALID in the APPS schema and carries an API classification of OTHER, indicating that it is a supporting utility interface rather than a formal business API documented within the standard OLFM API set.

Key Procedures and Functions

The ETRM documentation lists three documented program units within OKL_SETUPFUNCTIONS_PUB_W. Because no parameter signatures are published in the metadata, only their functional roles are described here.

• GET_REC — A retrieval function that returns setup function records. It is used to fetch the current definition of a setup function, typically by a caller-supplied key, so that dependent processing can evaluate the configuration without querying the base tables directly.
• INSERT_FUNCTIONS — A procedure that creates new setup function records. It encapsulates the validation and defaulting required before a new setup function may be persisted, ensuring the records conform to the expectations of downstream OKL processing.
• UPDATE_FUNCTIONS — A procedure that modifies existing setup function records. It applies changes to previously defined setup configurations while preserving the integrity constraints enforced by the wrapper layer.

Tables Accessed

The documented metadata does not enumerate the base tables read or written by this package; no table references are reported through APPS synonyms. Functionally, the package operates against the OKL setup function and setup function value tables that store the header and detail definitions of each configured setup function. These are the tables that GET_REC reads from and that INSERT_FUNCTIONS and UPDATE_FUNCTIONS write to. Because the metadata records no explicit table list, any table names inferred here should be confirmed against the Oracle ETRM data model or the package body source in the specific 12.1.1 or 12.2.2 instance.

Usage Notes

OKL_SETUPFUNCTIONS_PUB_W depends on the Oracle Application Object Library FND_API package, which supplies the standard error-handling and message-stack utilities used across EBS public APIs (for example, FND_API.G_RET_STS_SUCCESS and FND_API.G_RET_STS_ERROR conventions). It also depends on the SYS.STANDARD package type definitions.

The package is typically invoked by OLFM setup forms and by custom or extension code that needs to read or maintain setup function configuration without bypassing validation. It would also be called from concurrent or batch routines that seed setup function data during implementation or upgrade. The ETRM metadata records no other APPS packages referencing it, so its callers are expected to be forms, concurrent programs, or bespoke PL/SQL rather than sibling APIs. As with all EBS wrapper interfaces, callers should honor the return status conventions and inspect the FND message stack on error to obtain the failure reason.