Results for “cs_csz_srch_sorts_u1”

10 results




Overview
Explore in AI Chat

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

Overview

CS.CS_CSZ_SRCH_SORTS is a table in the Customer Care (CS) schema of Oracle E-Business Suite that stores the sorting configuration associated with saved searches defined in the CS_CSZ_SEARCHES table. Each row describes a single sort criterion — the attribute to sort by, its attribute group and type, and the direction of the sort — that is applied to the ORDER BY clause when a saved search is executed. The data is captured and maintained through the Sorting region of the Create/Update Saved Search page within the Service/Telephony and Customer Care search framework.

From a Data Vault modeling perspective, the structure is satellite-leaning. The table carries a composite primary key of SEARCH_ID and SORT_SEQ rather than an independent surrogate business key, and its SEARCH_ID column is a foreign key to CS_CSZ_SEARCHES. This positions the table as a dependent, descriptive satellite attached to the CS_CSZ_SEARCHES hub, holding the ordered sort definition rather than acting as an independent hub or link. The table is stored in the APPS_TS_TX_DATA tablespace with PCT FREE 10, and its unique index resides in APPS_TS_TX_IDX.

Key Information Stored

The table's identity is defined by a composite primary key, CS_CSZ_SRCH_SORTS_PK, comprising SEARCH_ID and SORT_SEQ. The same column pair forms the unique business-key candidate index CS_CSZ_SRCH_SORTS_U1, which is the index referenced by the user's search term. The most important columns are:

  • SEARCH_ID — Numeric identifier of the parent row in CS_CSZ_SEARCHES. It anchors each sort criterion to its owning saved search and is the foreign-key column linking to CS_CSZ_SEARCHES.
  • SORT_SEQ — Numeric sequence that establishes the ordering of sort criteria within a search; together with SEARCH_ID it forms the composite key and the values are also used to build the ORDER BY clause.
  • ATTR_ID — VARCHAR2(30) identifier of the attribute to be sorted by.
  • ATTR_GROUP_ID — Numeric value used for extensible attributes, indicating the attribute group to which the sort attribute belongs.
  • ATTR_TYPE — VARCHAR2(15) attribute type designator.
  • SORT_DIRECTION — VARCHAR2 value specifying sort orientation, with ASC for ascending and DSC for descending.
  • OBJECT_VERSION_NUMBER — Object version number supporting optimistic locking and concurrent update control.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns recording audit and user context for each row.

The surrogate identity is therefore the composite SEARCH_ID/SORT_SEQ pair, while the unique index CS_CSZ_SRCH_SORTS_U1 provides the documented business-key candidate covering the same columns.

Common Use Cases and Queries

Typical usage centers on retrieving, auditing, and troubleshooting the sort order applied to a saved search. A common query pattern joins the sort criteria to their parent search to reconstruct a saved search's full ordering definition:

  • Retrieve all sort criteria for a given search, ordered by sequence: SELECT SEARCH_ID, SORT_SEQ, ATTR_ID, ATTR_TYPE, SORT_DIRECTION FROM CS.CS_CSZ_SRCH_SORTS WHERE SEARCH_ID = :search_id ORDER BY SORT_SEQ;
  • Audit which attributes are most frequently sorted, and in which direction, across all saved searches.
  • Verify sort configuration when a saved search returns unexpected ordering in the Customer Care search UI.
  • Report on extensible-attribute sorting by filtering on ATTR_GROUP_ID and ATTR_TYPE.
  • Trace changes through LAST_UPDATE_DATE, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER for change-management and data-quality reviews.

Related Objects

The principal relationship is to the parent saved-search table, with the FK column SEARCH_ID joining CS_CSZ_SEARCHES.SEARCH_ID. Because CS_CSZ_SRCH_SORTS does not reference any other database object, its dependency graph is narrow and parent-oriented. The most significant related objects are:

  • CS.CS_CSZ_SEARCHES — Parent table holding saved search definitions; joined on SEARCH_ID.
  • CS.CS_CSZ_SRCH_SORTS# — The dependent object referencing this table, per the documented dependency list.
  • CS_CSZ_SRCH_SORTS_PK — Primary key constraint on SEARCH_ID and SORT_SEQ.
  • CS_CSZ_SRCH_SORTS_U1 — Unique index on SEARCH_ID and SORT_SEQ, the business-key candidate referenced in the user's search.

These objects, together with the Create/Update Saved Search page's Sorting region, form the complete functional context in which CS_CSZ_SRCH_SORTS operates.