Results for “okl_validations_b”

50+ results




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

Overview

OKL_VALIDATIONS_B is a table in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, residing in the OKL schema. It stores the individual validation lines that belong to a Validation Set. In Lease and Finance Management, validation sets define the rules applied to contracts, quotes, and related business objects to enforce data integrity, credit policy, and workflow preconditions. Each row in OKL_VALIDATIONS_B represents one validation line — the specific function to execute and the severity of failure when that function returns a negative result.

The documented physical schema for ETRM 12.2.2 lists 26 columns. The primary key is defined by OKL_VLD_PK on the ID column, and a unique index OKL_VLD_UC1 also exists on ID. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone, meaning the table has no documented parent or child relationships within the mined FK graph. It can therefore be treated as an independent reference/configuration entity rather than a hub, link, or satellite in a strict Data Vault sense, though its validation lines are conceptually dependent on the parent validation set.

Key Information Stored

The most significant columns in OKL_VALIDATIONS_B include:

  • ID — Surrogate primary key (OKL_VLD_PK) and the unique business-key candidate (OKL_VLD_UC1). Uniquely identifies each validation line.
  • VALIDATION_SET_ID — Identifies the parent Validation Set to which this line belongs; the principal grouping column for retrieving all lines of a set.
  • FUNCTION_ID — References the validation function or rule executed for this line; defines the logic that is evaluated.
  • FAILURE_SEVERITY — Determines the severity applied when the validation function fails (for example, error versus warning), controlling whether processing is blocked or merely flagged.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent update control.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the row, and when.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, allowing customers to extend validation lines with site-specific attributes without modifying the base schema.

The surrogate key ID is distinct from the business grouping represented by VALIDATION_SET_ID; the unique index OKL_VLD_UC1 documents that ID alone is the enforced uniqueness constraint in the shipped schema.

Common Use Cases and Queries

Typical uses include inspecting which validations are configured for a given set, diagnosing why a contract or quote failed validation, and auditing failure severity assignments. A representative query retrieves all lines for a set:

  • SELECT v.ID, v.VALIDATION_SET_ID, v.FUNCTION_ID, v.FAILURE_SEVERITY FROM OKL.OKL_VALIDATIONS_B v WHERE v.VALIDATION_SET_ID = :p_set_id ORDER BY v.ID;
  • Audit and change-tracking: SELECT ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKL.OKL_VALIDATIONS_B WHERE LAST_UPDATE_DATE >= :p_since;
  • Reporting on severity distribution: SELECT FAILURE_SEVERITY, COUNT(*) FROM OKL.OKL_VALIDATIONS_B GROUP BY FAILURE_SEVERITY;
  • DFF extraction: SELECT ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1 FROM OKL.OKL_VALIDATIONS_B WHERE ATTRIBUTE_CATEGORY IS NOT NULL;

Related Objects

Because the mined FK structure classifies OKL_VALIDATIONS_B as standalone, no explicit foreign-key joins are documented. The following related objects are significant based on the column semantics (VALIDATION_SET_ID and FUNCTION_ID):