Results for “value_char”

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

Overview

CS.CS_CSZ_SRCH_CRIT_VALUES is a Service (CS) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores the individual criteria values that make up saved search criteria used by the Service/TeleService search framework, allowing users to define and reuse parameterized searches across service requests, interactions, and related service entities. Each row represents a single value entry belonging to a parent search criterion, and the table is the child (detail) side of a master-detail relationship to CS_CSZ_SRCH_CRITERIA. When the metadata's heuristic Data Vault classification was mined from the foreign key structure, the object was assessed as satellite-leaning: it hangs off a parent key and carries the descriptive, changeable value payload, rather than acting as a hub of business entities or a many-to-many link between them.

Key Information Stored

The table's physical schema is documented with twelve columns. The most significant are outlined below.

• CRITERIA_ID — The foreign key to CS_CSZ_SRCH_CRITERIA, identifying the parent search criterion to which this value belongs. This column participates in both the primary key and the unique index.
• VALUE_SEQ — A sequence number that orders and distinguishes multiple values within the same criterion, supporting multi-value (for example, IN-list) criteria. It also participates in the primary key and unique index.
• VALUE_CHAR — The stored value as character data, used for text, code, or lookup-typed criteria.
• VALUE_NUM — The stored value as numeric data, used for range or numeric comparison criteria.
• VALUE_DATE — The stored value as a date, used for date-based search predicates.
• OPERATOR_CODE — Identifies the comparison operator (for example, equals, greater than, less than, like) applied to the value when the criterion is executed.
• OBJECT_VERSION_NUMBER — The standard EBS optimistic locking column used by the underlying framework to detect concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard EBS audit columns recording who created and last modified the row, and when.

The surrogate primary key is CS_CSZ_SRCH_CRIT_VALUES_PK, defined on the composite of CRITERIA_ID and VALUE_SEQ. The unique index CS_CSZ_SRCH_CRIT_VALUES_U1 is defined on the identical column pair, meaning the documented business key coincides with the surrogate key. The type-specific value columns (VALUE_CHAR, VALUE_NUM, VALUE_DATE) constitute a polymorphic value pattern, in which only the column appropriate to the criterion's data type is expected to be populated for a given row.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include auditing the operand values behind saved searches, reconstructing the effective search logic for a given criterion, and troubleshooting criteria that return unexpected results.

To retrieve all values for a specific criterion and reuse of a saved search, a query of the following form is used:

SELECT CRITERIA_ID, VALUE_SEQ, OPERATOR_CODE, VALUE_CHAR, VALUE_NUM, VALUE_DATE FROM CS_CSZ_SRCH_CRIT_VALUES WHERE CRITERIA_ID = :p_criteria_id ORDER BY VALUE_SEQ;

To trace a saved search back to its parent criterion definition, join the two tables on the shared key:

SELECT c.CRITERIA_ID, v.VALUE_SEQ, v.OPERATOR_CODE, v.VALUE_CHAR FROM CS_CSZ_SRCH_CRITERIA c, CS_CSZ_SRCH_CRIT_VALUES v WHERE c.CRITERIA_ID = v.CRITERIA_ID;

An audit query keyed on LAST_UPDATE_DATE and LAST_UPDATED_BY identifies recently modified search criteria values, which is useful when validating configuration changes after a release or patch.

Related Objects

• CS_CSZ_SRCH_CRITERIA — The parent table. Joined on CS_CSZ_SRCH_CRITERIA.CRITERIA_ID = CS_CSZ_SRCH_CRIT_VALUES.CRITERIA_ID; this is the sole documented foreign key relationship.
• CS_CSZ_SRCH_CRIT_VALUES_PK — The primary key constraint enforcing uniqueness of CRITERIA_ID and VALUE_SEQ.
• CS_CSZ_SRCH_CRIT_VALUES_U1 — The unique index on CRITERIA_ID and VALUE_SEQ.
• CS Service search framework components — The Service module's search query-building logic consumes these value rows when a saved search is executed, resolving OPERATOR_CODE and typed values into the runtime predicate.

Because the documented relationship data identifies only one inbound reference, dependent objects beyond CS_CSZ_SRCH_CRITERIA should be confirmed against the deployment's actual data dictionary before being treated as authoritative.