Search Results okl_setupfunctions_pvt




Overview
Explore in AI Chat

Overview

OKL_DATA_SRC_FNCTNS_PUB is a public PL/SQL API package in the APPS schema that belongs to the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It provides the programmatic interface through which data source functions — the configurable rules that determine where and how lease and contract attributes are sourced during origination and setup — are created, maintained, and validated. Data source functions are a foundational setup entity in OKL: they map contract and lease fields to their originating sources, and they are consumed by the broader setup framework that drives defaulting, derivation, and attribute population on lease and contract records.

The package follows the standard EBS API layering pattern. The _PUB package exposes the supported public interface with locking, validation, and DML operations, and delegates the substantive business logic to the private worker package OKL_DSF_PVT. It also depends on OKC_API, the public API of Oracle Contracts (OKC), reflecting the tight coupling between lease data sources and the underlying contracts data model. The object is documented as VALID and is classified as an API in ETRM 12.2.2.

Key Procedures and Functions

The documented interface exposes eleven procedures and functions, summarized below by name and purpose only. Parameter signatures are intentionally omitted.

  • ADD_LANGUAGE — Registers or installs translated language rows for data source function definitions, supporting the multi-language (MLS) requirements of the setup data.
  • INSERT_DATA_SRC_FNCTNS — Creates a new data source function definition, writing the primary record and any associated detail rows.
  • LOCK_DATA_SRC_FNCTNS — Obtains a pessimistic lock on an existing data source function record to serialize concurrent modifications within a transaction.
  • UPDATE_DATA_SRC_FNCTNS — Modifies an existing data source function definition after the record has been locked and validated.
  • DELETE_DATA_SRC_FNCTNS — Removes a data source function definition, subject to the standard API checks for referenced or in-use records.
  • VALIDATE_DATA_SRC_FNCTNS — Performs the business-rule validation of the data source function attributes and their combinations prior to insert or update.

The conventional invocation sequence is LOCK, then VALIDATE, then INSERT, UPDATE, or DELETE, with ADD_LANGUAGE applied for translated content. All substantive logic is implemented in OKL_DSF_PVT.

Tables Accessed

The ETRM metadata documents a single table referenced through APPS synonyms: PLITBLM. This is the standard EBS multi-language interim/translation table used by MLS-enabled objects; the package interacts with it to stage and apply language-specific attribute values as part of the ADD_LANGUAGE and DML flows. The persistence of the data source function definitions themselves is handled by the private layer and the underlying OKL setup tables, which are not enumerated in the supplied metadata. No direct DML against unresolvable base tables should be assumed from this package.

Usage Notes

OKL_DATA_SRC_FNCTNS_PUB is referenced by three other packages — OKL_DATA_SRC_FNCTNS_PUB_W, OKL_SETUPDSFPARAMETERS_PVT, and OKL_SETUPFUNCTIONS_PVT — indicating that it serves as the shared write interface beneath the OKL setup forms and parameter-configuration logic. The OKL_SETUPFUNCTIONS_PVT reference is directly relevant to the search term "okl_setupfunctions_pvt": the setup functions private package calls into this public API rather than performing direct DML. The _W variant is the standard EBS wrapper used for cover/error handling and organization-level defaulting.

In practice, the package is invoked indirectly when users create or revise data source functions through the OKL setup forms, and directly by custom code, concurrent programs, or data migration scripts that must create or amend data source function definitions in a controlled, validated manner. Custom integrations should call this package in preference to direct table inserts, and should honor the LOCK-VALIDATE-DML sequence to avoid inconsistent setup data. Because the package depends on OKC_API, callers should ensure that any associated contract-side setup exists before invoking it.