Results for “validation_code”

50+ results




Overview
Explore in AI Chat

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

Overview

OKL_FE_CRITERIA_SET is the eligibility criteria header table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available in release 12.1.1 and 12.2.2. The object resides in the OKL schema and holds the header-level attributes that govern how eligibility criteria are grouped, sourced, and validated during lease and finance origination processing. Each row represents one criteria set, which serves as a parent container for the individual criterion lines stored in OKL_FE_CRITERIA. In practice, criteria sets allow the application to evaluate a prospective contract, customer, or asset against a defined collection of business rules before approval, pricing, or booking proceeds.

From a data modeling perspective, the mined relationship structure suggests this table behaves as a hub-leaning entity. Its sole inbound foreign key relationship is a child reference from OKL_FE_CRITERIA, meaning the table functions primarily as a parent or root record that other objects point to, rather than accumulating descriptive detail from multiple sources. Analysts designing a Data Vault or dimensional representation should therefore treat CRITERIA_SET_ID as a stable business key around which criterion lines and related satellite attributes are organized.

Key Information Stored

The table is documented with eleven physical columns. The most significant are:

  • CRITERIA_SET_ID — the surrogate primary key defined by OKL_FE_CRITERIA_SET_PK. It also appears in the unique index OKL_FE_CRITERIA_SET_U1, making it the effective business-key candidate for the header record and the join column to child criteria lines.
  • OBJECT_VERSION_NUMBER — the standard Oracle EBS optimistic locking column, incremented on each update to detect concurrent modification.
  • SOURCE_ID — identifier of the source entity from which the criteria set was derived or against which it applies.
  • SOURCE_OBJECT_CODE — a code indicating the type of the source object referenced by SOURCE_ID, allowing one criteria set table to serve multiple origination contexts.
  • MATCH_CRITERIA_CODE — controls how the child criteria are combined logically (for example, whether all criteria must match or any may match).
  • VALIDATION_CODE — identifies the validation outcome or rule associated with the set.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing who created and last modified the row and when.

Common Use Cases and Queries

Typical usage centers on retrieving a criteria set and expanding its criteria lines, or reporting on sets by source object. A representative join is:

  • SELECT cs.criteria_set_id, cs.source_object_code, cs.match_criteria_code, c.criteria_id FROM okl.okl_fe_criteria_set cs, okl.okl_fe_criteria c WHERE cs.criteria_set_id = c.criteria_set_id;
  • Filtering sets by SOURCE_OBJECT_CODE to inspect which origination flows reuse a given criteria group.
  • Audit reporting using LAST_UPDATED_BY and LAST_UPDATE_DATE to track configuration changes over time.
  • Concurrency troubleshooting keyed on OBJECT_VERSION_NUMBER when users report conflicting edits.

Related Objects

The documented foreign-key relationship links this header to its detail table:

  • OKL_FE_CRITERIA — joins via OKL_FE_CRITERIA.CRITERIA_SET_ID = OKL_FE_CRITERIA_SET.CRITERIA_SET_ID; stores the individual criterion lines belonging to each set.
  • OKL_FE_CRITERIA_SET_PK / OKL_FE_CRITERIA_SET_U1 — the primary key and unique index enforcing uniqueness of CRITERIA_SET_ID.

Because the documented metadata lists only this single child relationship, further dependent views and APIs should be confirmed against the specific 12.1.1 or 12.2.2 installation before reliance.