Search Results okl_fe_criteria_set_pk

Overview

The OKL_FE_CRITERIA_SET table is a core data object within the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, specifically for the OKL (Lease and Finance Management) product module. It functions as the header or master table for defining eligibility criteria sets. In the context of Oracle Lease Management, eligibility criteria are rule-based conditions used to determine the qualification of assets, customers, or transactions for specific lease or financing programs, products, or promotions. This table stores the foundational attributes for each distinct set of rules, providing a structured framework to which detailed individual criteria (stored in a related table) are attached. Its role is central to configuring and enforcing business logic for financial product offerings.

Key Information Stored

While the provided metadata does not list specific columns beyond the primary key, the table's description as the "Eligibility Criteria Header attributes" indicates it stores master information for a criteria set. Based on standard EBS design patterns and the module's function, the table likely contains columns such as: CRITERIA_SET_ID (the primary key, a unique identifier for the criteria set), a NAME or CODE for the set, a DESCRIPTION, an ENABLED_FLAG to control active status, and dates for creation and last update (CREATION_DATE, LAST_UPDATE_DATE). It may also include a SET_TYPE or USAGE_CODE to classify the criteria set (e.g., for asset eligibility, customer credit scoring, or promotional qualification) and a reference to the associated product or program.

Common Use Cases and Queries

This table is primarily accessed during the setup and execution of eligibility checks within lease and finance workflows. Common operational and reporting scenarios include querying all active criteria sets for a given product type or generating a list of criteria sets used in conjunction with specific lease programs. A typical administrative query would retrieve header information for all enabled criteria sets:

• SELECT criteria_set_id, name, description, creation_date FROM okl_fe_criteria_set WHERE enabled_flag = 'Y' ORDER BY name;

For a more comprehensive view, a join with the detail table (OKL_FE_CRITERIA) is standard to report the full rule definition:

• SELECT hdr.name AS criteria_set, dtl.criteria_code, dtl.operator, dtl.value FROM okl_fe_criteria_set hdr, okl_fe_criteria dtl WHERE hdr.criteria_set_id = dtl.criteria_set_id ORDER BY hdr.name, dtl.seq_number;

Related Objects

The OKL_FE_CRITERIA_SET table has a direct parent-child relationship with the detail table that stores individual rule lines. As documented in the provided metadata:

• Primary Key: OKL_FE_CRITERIA_SET_PK on the column CRITERIA_SET_ID.
• Foreign Key Relationship: The table OKL_FE_CRITERIA references OKL_FE_CRITERIA_SET via its CRITERIA_SET_ID column. This establishes a one-to-many relationship where one criteria set header can have many detailed criteria lines. This is the principal structural relationship for the eligibility rules engine.