Results for “sql_type”

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

Overview

QA_CRITERIA is a transactional configuration table in the Oracle Quality (QA) module of Oracle E-Business Suite, owned by the QA schema. It stores the "show results where" filter criteria used by Quality charting, the Quality Dynamic Reportwriter, and other analytic components that query collection plan results. Each row represents a single filter predicate — an operator applied to a characteristic, or a cross-characteristic formula — that constrains which quality results are displayed in a report or chart. Because a chart or report can carry many predicates, QA_CRITERIA acts as a child detail table beneath a header record that groups the predicate set.

From a dimensional modeling perspective, the FK structure suggests treating QA_CRITERIA as a link table. It sits between QA_CRITERIA_HEADERS and QA_CHARS, resolving the many-to-many association between a criteria set and the quality characteristics it filters on, while carrying its own descriptive attributes such as SQL_TYPE, OPERATOR, LOW_VALUE, and HIGH_VALUE. This classification is a heuristic mined from the foreign-key topology rather than an Oracle-declared designation.

Key Information Stored

• CRITERIA_SEQUENCE — surrogate primary key (QA_CRITERIA_PK) and the single documented unique index column (QA_CRITERIA_U1); the immutable identifier for a filter line.
• CRITERIA_ID — foreign key to QA_CRITERIA_HEADERS; groups this predicate with its sibling predicates into a named criteria set.
• CHAR_ID — foreign key to QA_CHARS; identifies the quality characteristic being filtered.
• ORDER_SEQUENCE — controls evaluation and display order of the predicate within its criteria set.
• SQL_TYPE — indicates how the predicate is constructed, distinguishing characteristic-based comparison from a formula-driven condition.
• OPERATOR — the comparison operator applied (for example equality, range, or set membership).
• LOW_VALUE / LOW_VALUE_ID — the lower bound or single comparison value, in both display and coded-identifier form.
• HIGH_VALUE / HIGH_VALUE_ID — the upper bound for range predicates, in both display and coded-identifier form.
• FXN — the formula or function expression used when SQL_TYPE indicates a calculated predicate.
• TOTAL — aggregation behavior applied to the filtered result set.
• SORT_BY — ordering directive for the report or chart output.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS WHO-column auditability.

The surrogate key is CRITERIA_SEQUENCE; CRITERIA_ID functions as a business-key component since it is the parent reference that, combined with ORDER_SEQUENCE, determines the logical position of the predicate.

Common Use Cases and Queries

Typical reporting retrieves all predicates attached to a criteria set so an administrator can audit or reproduce a chart's filter logic:

• Listing predicate lines for a given header: SELECT criteria_sequence, order_sequence, operator, low_value, high_value FROM qa.qa_criteria WHERE criteria_id = :criteria_id ORDER BY order_sequence.
• Joining to QA_CHARS to resolve the characteristic name behind CHAR_ID, producing human-readable filter documentation.
• Detecting range predicates by querying rows where HIGH_VALUE IS NOT NULL, useful when migrating chart definitions.
• Identifying formula-driven criteria via SQL_TYPE and FXN for impact analysis before characteristic changes.

These queries support QA configuration audits, report definition troubleshooting, and instance-to-instance migration of Quality reportwriter setups.

Related Objects

• QA_CRITERIA_HEADERS — parent table joined on QA_CRITERIA.CRITERIA_ID = QA_CRITERIA_HEADERS.CRITERIA_ID; holds the criteria-set definition.
• QA_CHARS — referenced via QA_CRITERIA.CHAR_ID = QA_CHARS.CHAR_ID; defines the characteristic being filtered.
• QA_CRITERIA_PK / QA_CRITERIA_U1 — the primary key constraint and unique index enforcing row identity on CRITERIA_SEQUENCE.
• QA_RESULTS and collection plan result tables — the downstream data against which these "show results where" predicates are applied.
• Quality Dynamic Reportwriter and charting components — the functional consumers that read QA_CRITERIA to build their runtime WHERE clauses.