Results for “okl_data_src_fnctns_b”

50+ results




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

Overview

OKL_DATA_SRC_FNCTNS_B is a foundational configuration table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. In release 12.1.1 and 12.2.2, this table stores the definitions of the functions that map to the desired PL/SQL function used by the OKL rules engine — the component that evaluates pricing, scoring, criteria, and operand logic across lease and finance contracts. Each row defines a named, versioned data source function that the rules engine can invoke, together with the identity of the underlying PL/SQL implementation.

The table resides in the OKL schema and, as of ETRM 12.2.2, is documented with 31 physical columns. It is an edtion-enabled object, as evidenced by the ZD_EDITION_NAME column and its participation in the unique indexes. Under a heuristic Data Vault classification, the object is hub-leaning: it holds an immutable business key (the combination of function name and version) and is referenced by multiple dependent tables, which is the characteristic signature of a hub entity.

Key Information Stored

The table's surrogate primary key is ID, enforced by the OKL_DATA_SRC_FNCTNS_B_PK constraint. This is a system-generated identifier used as the target of foreign key relationships throughout the module.

Two unique indexes define the business-key candidates. OKL_DATA_SRC_FNCTNS_B_U1 is a composite of ID and ZD_EDITION_NAME, while OKL_DSF_U2 covers NAME, VERSION, and ZD_EDITION_NAME — meaning a function name is uniquely identified only in combination with a version and an edition. The versioned design allows Oracle to ship successive definitions of the same function without overwriting prior rows.

The most significant columns include:

  • ID — surrogate primary key referenced by dependent configuration tables.
  • NAME and VERSION — the business identifier of the function, forming the core of unique index OKL_DSF_U2.
  • FNCTN_CODE — the code that links the row to the actual PL/SQL function invoked at runtime.
  • SOURCE — indicates the origin or provider of the function definition.
  • ORG_ID — the operating unit context, enabling multi-org deployment of function definitions.
  • START_DATE and END_DATE — effective-dating columns that control when the definition is active.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS concurrency, auditing, and row-versioning columns.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns used to store client-specific extension data.
  • ZD_EDITION_NAME — the editioning discriminator used for online patching in 12.2.

Common Use Cases and Queries

The table is most often queried when troubleshooting or auditing rules-engine behavior — for example, determining which PL/SQL function is bound to a given criteria category, operand, or function parameter. A typical lookup resolves a function identifier to its name and code:

SELECT id, name, version, fnctn_code, source FROM okl.okl_data_src_fnctns_b WHERE id = :p_function_id;

Because the table is edition-enabled and versioned, reporting queries should generally constrain on the current edition and on the active effective dates to avoid returning superseded definitions:

SELECT name, version, fnctn_code FROM okl.okl_data_src_fnctns_b WHERE NVL(end_date, SYSDATE) >= SYSDATE ORDER BY name, version;

Common scenarios include validating that a function named in a criteria definition actually exists and is active, tracing the function parameters attached to a data source, and confirming that custom functions introduced by an implementation are registered with an appropriate name, version, and organization.

Related Objects

The documented foreign keys show that OKL_DATA_SRC_FNCTNS_B acts as the parent — a hub — for three child tables that reference its ID column:

  • OKL_FE_CRIT_CAT_DEF_B — references this table through FUNCTION_ID, linking criteria categories to their function definition.
  • OKL_FNCTN_PRMTRS_B — references this table through DSF_ID, holding the parameters passed to a data source function.
  • OKL_OPERANDS_B — references this table through DSF_ID, describing operands that use the data source function.

Together with the OKL rules-engine configuration tables that surround it, these objects form the metadata layer that lets the Leasing and Finance Management module resolve abstract business rules into executable PL/SQL at runtime.