Results for “cs_sr_saved_searches_vl”

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

Overview

CS_SR_SAVED_SEARCHES_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the CS (Service) product family and exposes the set of saved searches that users have defined against Service Requests. A saved search captures a named, reusable query definition — for example a filter set that isolates high-priority, open Service Requests for a specific customer or change number — so that service agents do not have to rebuild the criteria each time they work a queue. The view presents that configuration data in a translation-aware, reporting-friendly form.

Because the view terminates in the _VL suffix, Oracle EBS treats it as a "view with language" that resolves the display name through the session language. This makes it suitable for concurrent programs, BI Publisher data templates, OAF pages, and custom reports where a user-facing search name must be rendered in the correct locale. It is a read-only reporting and integration surface; row-level maintenance is performed against the underlying base tables through the Service Request forms and the corresponding OAF/BC4J entities.

Underlying Base Objects

The view is defined over two synonyms that resolve to the base tables of the saved-search entity:

• CS_SR_SAVED_SEARCHES_B — the base (transactional) table holding search header attributes such as SEARCH_ID, the owning USER_ID, WHO columns, the 15 DFF attribute columns, CONTEXT, OBJECT_VERSION_NUMBER, and SECURITY_GROUP_ID.
• CS_SR_SAVED_SEARCHES_TL — the translation table holding the translatable NAME, LANGUAGE, and SOURCE_LANG columns.

The join key is SEARCH_ID. The view applies the predicate B.LANGUAGE = USERENV('LANG'), meaning it returns at most one translated row per search, matched to the language of the current database session. This is standard Oracle EBS multi-language design: _B stores non-translatable data once, _TL stores the language-dependent text once per installed language, and the _VL view collapses the pair into a single row for consumers.

Key Columns

• ROW_ID — the ROWID of the base-table row, exposed as a surrogate identifier and used for optimistic locking in some integrations.
• SEARCH_ID — the primary identifier of the saved search and the join key between the base and translation tables.
• USER_ID — the application user who owns or created the saved search; the primary filter for "my searches" personalization.
• NAME, LANGUAGE, SOURCE_LANG — the translated display name of the search together with its current language and the language in which it was originally authored.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns for lifecycle reporting and data lineage.
• OBJECT_VERSION_NUMBER — the optimistic-locking version token maintained by the framework.
• SECURITY_GROUP_ID — the multi-org / security grouping identifier, relevant when access is scoped by operating unit or security profile.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield context and segment columns, allowing customer-specific extensions to be surfaced.

Common Use Cases and Queries

Typical scenarios include reporting which saved searches exist per user, auditing searches that reference a particular query pattern, and feeding saved-search metadata into custom Service Request dashboards. A basic listing of the searches owned by the current session user is:

• SELECT search_id, name, language, creation_date, last_update_date FROM cs_sr_saved_searches_vl WHERE user_id = fnd_global.user_id ORDER BY name;
• Listing all searches for a specific owner: SELECT search_id, name FROM cs_sr_saved_searches_vl WHERE created_by = :user_id;
• Inspecting DFF extensions: SELECT search_id, name, context, attribute1, attribute2 FROM cs_sr_saved_searches_vl WHERE context IS NOT NULL;

Because the view restricts rows by USERENV('LANG'), reports must be run under a session whose language has a corresponding translation row in CS_SR_SAVED_SEARCHES_TL; otherwise no NAME is returned. When the requested business object is not a saved search — for example when a user searches for "how to search chg no in service now" — the appropriate EBS data source is the Service Request / change-number tables rather than this view, which stores only the search definition itself and not the resulting tickets.