Search Results okl_data_src_fnctns_v




Overview
Explore in AI Chat

Overview

OKL_DATA_SRC_FNCTNS_V is an APPS-owned, VALID database view within the Oracle Lease and Finance Management (OKL) product family. As documented in the ETRM metadata, its stated purpose is to identify "the name of the function that maps to the desired PL/SQL function." In practical terms, the view exposes the registry of data source functions used by Oracle Lease and Finance Management when resolving which PL/SQL routine should execute for a given functional code. These functions underpin the rules, calculations, and data transformations that drive contract generation, pricing, accrual, and accounting logic across the leasing lifecycle.

Because the view consolidates a base table and its translation table into a single language-filtered result set, it is the standard access point for reporting, integration, and diagnostic queries where a developer or analyst needs a human-readable list of available data source functions. It follows the customary Oracle EBS pattern of separating a "_B" base table for language-independent attributes from a "_TL" translation table for descriptive text.

Underlying Base Objects

The view is defined over two documented synonyms:

  • OKL_DATA_SRC_FNCTNS_B — the base table holding the function's language-independent data: identifier, function code, name, version, effective dates, source, multi-org identifier (ORG_ID), and the standard DFF attribute columns.
  • OKL_DATA_SRC_FNCTNS_TL — the translation table supplying the language-specific DESCRIPTION and the SFWT_FLAG, joined on ID.

The join condition is DSFB.ID = DSFT.ID AND DSFT.LANGUAGE = USERENV('LANG'), ensuring the description is returned in the session's current language. This is a classic EBS _B/_TL pairing; any row present in the base table but lacking a translation for the active language is filtered out of the result set.

Key Columns

  • ROW_ID — the rowid of the base table row, useful for direct DML and debugging.
  • ID / OBJECT_VERSION_NUMBER — the primary key and optimistic locking version of the function record.
  • FNCTN_CODE — the functional code that maps to a specific PL/SQL function; the business-facing key used in configuration and rule setup.
  • NAME / DESCRIPTION — the function name and its translated description (DESCRIPTION coming from the _TL table).
  • SFWT_FLAG — the "seed/workflow template" flag sourced from the translation table, indicating whether the row is seeded.
  • VERSION, START_DATE, END_DATE, SOURCE — versioning and effective-dating attributes controlling which function definition applies when.
  • ORG_ID — the operating unit / multi-org discriminator.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns for site-specific extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include reviewing which data source functions are configured for a module, validating effective-dated function versions, and feeding integration scripts or diagnostics that must resolve a FNCTN_CODE to its underlying PL/SQL routine.

Listing all available functions:

SELECT id, fnctn_code, name, description, version, start_date, end_date FROM okl_data_src_fnctns_v ORDER BY fnctn_code;

Resolving a specific function by code:

SELECT fnctn_code, name, description FROM okl_data_src_fnctns_v WHERE fnctn_code = :fnctn_code;

Filtering currently effective definitions for an operating unit:

SELECT fnctn_code, name, version FROM okl_data_src_fnctns_v WHERE org_id = :org_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

Oracle Proprietary, Confidential Information — Legal Notices apply.