Search Results okl_data_src_fnctns_pub_w




Overview
Explore in AI Chat

Overview

OKL_DATA_SRC_FNCTNS_PUB_W is a public PL/SQL package in the APPS schema that forms part of the Oracle Lease and Finance Management (OKL) module within Oracle E-Business Suite. Its name indicates that it governs data source functions — the configurable components through which the ETRM (Enterprise Transaction and Reporting Management) subsystem identifies and resolves the sources of data used during contract authoring, pricing, and related processing. In ETRM terms, a data source function defines how a particular field or value is derived or fetched when a lease or financial contract is created or maintained, and this package serves as the public (wrapped/API-facing) entry point for creating, changing, and removing those definitions.

The package is classified as an "OTHER" API. It is not a full FND-style table-handler API, but it does depend on FND_API for standard API infrastructure such as message handling and return-status conventions. It exposes both lock-based and persistent operations, allowing callers to serialize changes against the underlying data source function records.

Key Procedures and Functions

The documented public interface contains five procedures/functions. Their names indicate the standard CRUD-plus-validation lifecycle applied to data source function records:

  • INSERT_DATA_SRC_FNCTNS — Creates a new data source function definition. It populates the underlying definition tables with the attributes that describe how a given data element is sourced.
  • LOCK_DATA_SRC_FNCTNS — Acquires a lock on an existing data source function record so that concurrent modifications cannot proceed in parallel. This is typically called before an update or delete to enforce record-level consistency.
  • UPDATE_DATA_SRC_FNCTNS — Modifies the attributes of an existing, previously locked data source function definition.
  • DELETE_DATA_SRC_FNCTNS — Removes a data source function definition, subject to the same locking discipline.
  • VALIDATE_DATA_SRC_FNCTNS — Performs validation of the supplied attributes before the record is committed, returning validation status through the standard API return-status mechanism.

Because the metadata does not expose the individual parameter lists, the exact signature of each routine cannot be asserted here. It can be reasonably stated, however, that these routines follow the standard ETRM public-API pattern of a p_api_version/p_init_msg_list preamble with x_return_status and x_msg_count/x_msg_data outputs, consistent with their FND_API dependency.

Tables Accessed

No base tables are recorded as directly referenced through APPS synonyms in the documented metadata; the package resolves its data source function records through the OKL foundation tables that hold data source function definitions. It does, however, depend on the standard JTF collection types — JTF_DATE_TABLE, JTF_NUMBER_TABLE, and the JTF_VARCHAR2_TABLE_100/200/500/800/2000 arrays — which are used to pass bulk or multi-value attribute sets between the API and its callers. The presence of these collection types suggests that the package can process data source function attributes in a set-based manner rather than strictly one record at a time. The package is self-referential: it both references and is referenced by OKL_DATA_SRC_FNCTNS_PUB_W (the wrapped body or the specification/body pair), and no other packages in the ETRM schema are documented as depending on it.

Usage Notes

OKL_DATA_SRC_FNCTNS_PUB_W is typically invoked by the ETRM setup or contract-authoring forms and by internal ETRM processing that needs to register or alter data source function configurations. Because it is a public package, it is also a valid integration point for custom code that must manipulate data source functions programmatically; such code should call LOCK before UPDATE or DELETE, and should always inspect x_return_status and drain the message stack via FND_MSG_PUB before continuing. Direct DML against the underlying tables is not recommended, as it bypasses the validation and locking enforced by this API. The package is valid in both 12.1.1 and 12.2.2; functional behavior is consistent across those releases, and the dependency set reflects only standard APPS and SYS infrastructure (FND_API, JTF tables, STANDARD).