Results for “operator_code”

1 result




Overview
Explore in AI Chat

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

Overview

OKL_FE_CRITERION_VALUES is a transactional configuration table in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, present and valid in releases 12.1.1 and 12.2.2. It stores the individual line-level values that make up an eligibility criterion definition used by the OKL front-end rules engine. Where OKL_FE_CRITERIA captures the header of an eligibility rule, OKL_FE_CRITERION_VALUES holds the discrete value rows — the actual constants, ranges, or lookup references — that the rule compares against when it evaluates whether a contract, quote, customer, or asset qualifies for a given lease or finance product.

The table is owned by the OKL schema and is documented with 28 columns in the ETRM 12.2.2 physical schema. Its primary key, OKL_FE_CRITERION_VALUES_PK, is defined on CRITERION_VALUE_ID, and a unique index (OKL_FE_CRITERION_VALUES_U1) also exists on that same column. Based on the foreign-key topology mined from the schema, the object is classified heuristically as satellite-leaning in a Data Vault sense: it is a dependent, descriptive child of a parent entity rather than an independent hub. This classification is a modeling suggestion only and not an Oracle-certified designation.

Key Information Stored

  • CRITERION_VALUE_ID — the surrogate primary key and sole unique business-key candidate, uniquely identifying each criterion value line.
  • CRITERIA_ID — the foreign key to OKL_FE_CRITERIA that ties each value row to its parent eligibility criterion.
  • OPERATOR_CODE — the comparison operator (for example, equals, greater-than, between) applied when the value is evaluated.
  • CRIT_CAT_VALUE1 and CRIT_CAT_VALUE2 — the criterion category value pair, holding the literal or range endpoints that the rule compares against. Two slots support range-style operators.
  • ADJUSTMENT_FACTOR — a numeric factor applied to the evaluated amount, allowing tolerance, weighting, or threshold adjustment.
  • OBJECT_VERSION_NUMBER — the optimistic-locking token used by the OAF/ADF framework to detect concurrent edits.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO-audit columns tracking row provenance.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns reserved for client-specific extensions.

The remaining documented columns follow these patterns; the columns above represent the functionally significant set for querying and integration.

Common Use Cases and Queries

Typical usage centers on reviewing or troubleshooting the rules that determine product eligibility. Analysts commonly join value lines back to criteria headers to reconstruct the full rule definition:

  • Eligibility rule inspection: SELECT c.criteria_id, v.operator_code, v.crit_cat_value1, v.crit_cat_value2, v.adjustment_factor FROM okl.okl_fe_criteria c, okl.okl_fe_criterion_values v WHERE c.criteria_id = v.criteria_id AND c.criteria_id = :p_id;
  • Audit of recently changed rule values using LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • Reporting on active criteria with ranges defined in CRIT_CAT_VALUE1/2 to verify threshold coverage.
  • Extract for interface or migration scripts keyed on CRITERION_VALUE_ID.
  • DFF reporting by querying ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for client-defined fields.

Related Objects

  • OKL_FE_CRITERIA — the parent header table; joined via OKL_FE_CRITERION_VALUES.CRITERIA_ID = OKL_FE_CRITERIA.CRITERIA_ID. This is the only documented foreign key.
  • OKL_FE_CRITERION_VALUES_PK — primary-key constraint on CRITERION_VALUE_ID.
  • OKL_FE_CRITERION_VALUES_U1 — unique index on CRITERION_VALUE_ID.
  • Other OKL front-end eligibility tables (e.g., criteria-set definitions) that reference criteria headers and, transitively, their value lines.
  • Standard OKL lease/quote qualifying objects that consume the criteria outcome during product-eligibility evaluation.

Because OKL_FE_CRITERION_VALUES is satellite-leaning, any change to a criterion's value rows should be treated as a data-vault-style delta against the parent criterion, preserved through the WHO-audit and OBJECT_VERSION_NUMBER columns rather than overwritten without trace.