Search Results set_value

Overview

OKL_MASS_RBK_CRITERIA_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKL – Leasing and Finance Management product family and exposes the configuration data used by the Mass Rebook (Rebook) concurrent process. The view presents one row per criteria line defined for a rebook request, together with the corresponding set value that the process applies when the criteria evaluate to true. In effect, it is the read model for the rule engine that governs mass rebook processing: selection criteria are expressed through CRITERIA_CODE, OPERAND, CRITERIA_VALUE1 and CRITERIA_VALUE2, while SET_VALUE carries the value written to the target attribute when the rule fires.

Because the view is a straight projection over a single base table with no joins or aggregation, it is inexpensive to query and is well suited for extracts, BI Publisher reports, and interfaces that must mirror the setup of a mass rebook run without touching the underlying table directly. Its definition guarantees stability of column names and ordering, which makes it a safer integration surface than the base table for custom code.

Underlying Base Objects

The view is defined entirely over the synonym OKL_MASS_RBK_CRITERIA, which resolves to the APPS-owned base table of the same name. The view text is a simple SELECT list aliasing each column, plus ROWID exposed as ROW_ID for row identification. No other tables, views, or outer joins participate in the definition, and no WHERE clause filters the result set. Consequently, the row count and cardinality of OKL_MASS_RBK_CRITERIA_V equal those of OKL_MASS_RBK_CRITERIA, and all DML is directed at the base table in practice. The view is documented as VALID in the ETRM metadata, confirming that the base synonym resolves correctly in a standard installation.

Key Columns

• ROW_ID – the base table ROWID, useful for de-duplication and for correlating view rows back to the physical row.
• ID – primary identifier of the criteria line.
• REQUEST_NAME and LINE_NUMBER – identify the mass rebook request and the sequence of the criteria line within it.
• RBR_CODE – rebook code that scopes the rule to a particular rebook action.
• CRITERIA_CODE, OPERAND, CRITERIA_VALUE1, CRITERIA_VALUE2 – together define the left-hand attribute, the comparison operator, and the one or two comparison values that form the rule predicate.
• SET_VALUE – the value assigned to the target attribute when the predicate is satisfied; this is the column returned by the user's search term and is the core output of the rule.
• DESCRIPTION and TSU_CODE – descriptive text and the transaction/setup unit context for the line.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – the standard Oracle flexfield descriptive columns for extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include auditing the criteria configured for a mass rebook request, exporting setup for migration between environments, and verifying that each criteria line has a SET_VALUE before launching the process. A representative query retrieves all lines for a request, ordered by sequence:

• SELECT request_name, line_number, rbr_code, criteria_code, operand, criteria_value1, criteria_value2, set_value FROM okl_mass_rbk_criteria_v WHERE request_name = :p_request ORDER BY line_number;
• SELECT id, criteria_code, set_value FROM okl_mass_rbk_criteria_v WHERE set_value IS NULL; — identifies incomplete rules.
• SELECT request_name, COUNT(*) FROM okl_mass_rbk_criteria_v GROUP BY request_name; — counts criteria per rebook request.

Because the view is unfiltered, always constrain queries by REQUEST_NAME, RBR_CODE, or TSU_CODE to limit the result set in production volumes.