Results for “criteria_code”

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

Overview

The OKL.OKL_MASS_RBK_CRITERIA table belongs to the Oracle Lease and Finance Management (OKL) product family within Oracle E-Business Suite. Its documented purpose is to capture Mass Rebook Criteria together with the associated Set Values that drive the mass rebook process. In leasing operations, mass rebook functionality allows a set of contracts to be selected and financially re-processed (rebooked) in bulk rather than individually, and this table provides the rule definitions that determine which contracts qualify and how the rebooking values are applied.

Structurally the table carries 32 columns and is owned by the OKL schema in both ETRM 12.1.1 and 12.2.2. The documented physical schema lists a single primary key, OKL_MASS_RBK_CRITERIA_PK, defined on the ID column, and a unique index OKL_MASS_RBK_CRITERIA_U1 also on ID. The metadata marks the object as standalone in the mined foreign-key relationship analysis, meaning no outbound FK dependencies were detected. From a Data Vault modeling perspective, this object is best characterized as a satellite-style attribute store: it holds descriptive criteria and set-value attributes rather than acting as a pure hub of business keys or a link between hubs. This classification is a heuristic suggestion derived from the standalone FK profile, not a documented Data Vault design.

Key Information Stored

The most significant columns in this table are the following:

• ID — the surrogate primary key and the sole unique-index column; it uniquely identifies each criteria/set-value row.
• REQUEST_NAME — identifies the mass rebook request or process run to which the criteria belong, grouping related criteria rows.
• LINE_NUMBER — the sequence or ordering of each criteria line within a request.
• RBR_CODE — the rebook code that determines the rebook rule, for example the rebook type or transaction type.
• CRITERIA_CODE — the field or attribute being tested as the selection criterion for contract qualification.
• OPERAND — the comparison operator (such as equals, greater than, between) applied to the criteria field.
• CRITERIA_VALUE1 and CRITERIA_VALUE2 — the comparison values; the second value supports range or between operators.
• SET_VALUE — the value to be set on the contract or transaction when the criteria are satisfied.
• DESCRIPTION — free-text description of the criteria line.
• TSU_CODE — the transaction subtype or related code that scopes the criteria to a particular rebook scenario.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns that allow customer-defined attributes to be captured.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO columns providing audit information.

Common Use Cases and Queries

Consultants and developers typically query this table to inspect the criteria that govern a mass rebook request, verify set values applied during rebooking, and produce audit reports of rebook configuration. A representative query lists all criteria lines for a given request:

• SELECT LINE_NUMBER, CRITERIA_CODE, OPERAND, CRITERIA_VALUE1, CRITERIA_VALUE2, SET_VALUE FROM OKL.OKL_MASS_RBK_CRITERIA WHERE REQUEST_NAME = :request_name ORDER BY LINE_NUMBER;
• A diagnostic query checks whether a fully-configured request exists: SELECT ID, REQUEST_NAME, RBR_CODE, TSU_CODE FROM OKL.OKL_MASS_RBK_CRITERIA WHERE RBR_CODE = :rbr_code;
• Reporting joins criteria to audit columns to review change history: SELECT ID, REQUEST_NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKL.OKL_MASS_RBK_CRITERIA WHERE LAST_UPDATE_DATE >= :from_date;

Because the table is standalone, queries generally filter by REQUEST_NAME, RBR_CODE, or TSU_CODE rather than joining through detected foreign keys. Flexfield columns should be resolved using the appropriate descriptive flexfield views if they are enabled for this object.

Related Objects

Given the documented absence of foreign-key relationships, this table is largely referenced by functional key and code rather than enforced database constraints. Significant related objects include:

• OKL_OKC_MASS_REBOOK-type request or process tables, joined on the request identifier corresponding to REQUEST_NAME.
• Rebook code setup objects keyed by RBR_CODE, which define valid rebook rule types.
• Transaction subtype or code tables keyed by TSU_CODE, which scope criteria to rebook scenarios.
• Lease or contract header and line tables that are selected and updated based on the criteria and set values defined here.
• Descriptive flexfield views derived from ATTRIBUTE_CATEGORY and the ATTRIBUTE columns.

Any join to these objects relies on business keys stored in the criteria table rather than on documented PK/FK pairs.