Results for “sort_sequence”

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

Overview

OKL_ANSWERS is a transactional table within the Oracle E-Business Suite Leasing and Finance Management module (OKL). It stores the discrete responses—described in the ETRM metadata as a "state, circumstance, situation, possibility or case"—that constitute the answer values captured against answer sets and rules during lease origination and administration. Each row represents a single answer instance that is linked both to a parent answer set and, where applicable, to a governing rule that determines eligibility, pricing, scoring, or downstream processing behavior.

The table carries two documented unique constraints: the primary key OKL_ANSWERS_PK on the ID column, and the unique index AWR_AWR_UK on the ANT_ID column (also referred to in the metadata as "AWR_AWR_UK"). Under a heuristic Data Vault classification mined from the foreign-key structure, OKL_ANSWERS leans toward the satellite category: it holds descriptive, context-dependent attributes attached to the parent answer set and rule business keys rather than acting as an independent hub or a pure many-to-many link. This classification is a modeling suggestion and should be validated against the surrounding OKL_ANSWER_SETS_B and OKC_RULES_B structures when designing a warehouse layer.

Key Information Stored

The 26 documented columns fall into identifier, sequencing, auditing, and descriptive attribute groups. The most significant columns are:

• ID — Surrogate primary key enforced by OKL_ANSWERS_PK and backed by the unique index OKL_ANSWERS_U1. This is the internal row identifier for each answer.
• ANT_ID — Foreign key to OKL_ANSWER_SETS_B. This is the documented business-key candidate, uniquely enforced by AWR_AWR_UK, and establishes the answer set to which the row belongs.
• RUL_ID — Foreign key to OKC_RULES_B. Links the answer to the rule context that consumes or evaluates it.
• SORT_SEQUENCE — Controls display and evaluation ordering of answers within their set.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates through the OA Framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) column set, allowing customer-specific extension of answer data without schema changes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail capturing user and timestamp metadata for each insert and update.

The distinction between the surrogate key (ID) and the business-key candidate (ANT_ID) is important for integration work: external references should generally resolve through the answer set identifier rather than the internal sequence.

Common Use Cases and Queries

Typical reporting scenarios include extracting all answers for a given answer set, tracing answers consumed by a specific rule, and auditing changes through the WHO columns or object version. The following pattern joins the table to its parent answer set:

• Retrieve answers for a specific set: SELECT id, ant_id, rul_id, sort_sequence FROM okl_answers WHERE ant_id = :ant_id ORDER BY sort_sequence;
• Trace answers used by a rule: SELECT a.id, a.ant_id, a.rul_id FROM okl_answers a WHERE a.rul_id = :rul_id;
• Audit recent changes: SELECT id, ant_id, last_updated_by, last_update_date FROM okl_answers WHERE last_update_date >= :since;
• DFF reporting: query ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 alongside the standard columns to surface customer-specific value sets.

Because OKL_ANSWERS is referenced by OKL_ANSR_CRTRN_VALS through the AWR_ID column, it is also the natural starting point for queries that enumerate criteria values applied to each answer.

Related Objects

The documented relationships connect OKL_ANSWERS to the following significant objects:

• OKL_ANSWER_SETS_B — Parent answer set; joined via OKL_ANSWERS.ANT_ID = OKL_ANSWER_SETS_B.ANT_ID.
• OKC_RULES_B — Rule definition; joined via OKL_ANSWERS.RUL_ID = OKC_RULES_B.RUL_ID.
• OKL_ANSR_CRTRN_VALS — Child criteria value table; joined via OKL_ANSR_CRTRN_VALS.AWR_ID = OKL_ANSWERS.ID.
• OKL_ANSWERS_PK and OKL_ANSWERS_U1 — Primary key constraint and unique index enforcing row identity and the ANT_ID business key.
• AWR_AWR_UK — The unique constraint documented against ANT_ID.

These relationships make OKL_ANSWERS a central join point between answer-set definition, rule evaluation, and criteria-driven decision logic in the leasing and finance domain.