Search Results image_file_name




Overview
Explore in AI Chat

Overview

CS_SR_TYPE_CATEGORIES_VL is a seeded, customer-facing view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CS (Service) product family. It exposes the set of Service Request Type categories — the configurable groupings used to classify Service Requests (SRs) within the Service/TeleService module. Its status is VALID across the 12.1.1 and 12.2.2 releases, and it is documented in the ETRM (E-Business Suite Technical Reference Manual) as containing "information about the Service Request Type categories."

The view follows the standard Oracle EBS MLS (Multi-Language Support) naming convention. The _VL suffix indicates a "view of translated rows" that joins a base table (_B) with its translation table (_TL) and filters the translation rows to the session's current language. This makes the view the correct object to query for display-oriented reporting and integrations, because it returns exactly one translated row per category in the user's active language. The presence of a _VL view also implies a corresponding _V (language-independent) view and that DML is generally performed against the underlying base/translation tables, not the view.

Underlying Base Objects

Per the documented metadata, CS_SR_TYPE_CATEGORIES_VL is defined over two synonym-referenced base objects:

The view text joins the two on SR_TYPE_CATEGORY_ID and restricts the translation row with the condition B.LANGUAGE = USERENV('LANG'), so only the translation matching the caller's language environment is returned. The _B table supplies the identity, ordering, image, date-ranged validity, DFF attributes, and WHO audit columns; the _TL table supplies the displayed NAME, DESCRIPTION, LANGUAGE, and SOURCE_LANG.

Key Columns

  • SR_TYPE_CATEGORY_ID — primary key of the category; the join key between the base and translation tables.
  • NAME, DESCRIPTION — language-specific display labels retrieved from the translation table.
  • DISPLAY_ORDER — controls the sequence in which categories are presented in list-of-values and UI layouts.
  • IMAGE_FILE_NAME — optional graphic associated with the category for UI rendering.
  • START_DATE, END_DATE — effective-dating window that governs when the category is active.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) context and segment values.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns.
  • LANGUAGE, SOURCE_LANG — the language of the returned translation and the source language of the base record.

Common Use Cases and Queries

The view is typically used to populate category selection lists, drive reporting on SR categorization, and supply lookup values to integrations and extensions. Effective-date filtering is a common requirement because seeded categories may be end-dated.

Listing active categories in display order:

  • SELECT sr_type_category_id, name, description, display_order FROM cs_sr_type_categories_vl WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date, SYSDATE) AND NVL(end_date, SYSDATE) ORDER BY display_order, name;

Joining to Service Requests to count usage by category:

  • SELECT c.name, COUNT(*) FROM cs_sr_type_categories_vl c, cs_incidents_all_b s WHERE c.sr_type_category_id = s.sr_type_category_id GROUP BY c.name;

Because _VL views filter on USERENV('LANG'), reports run in different language sessions return translated names automatically, which simplifies multilingual deployments and avoids explicit joins to the translation table in custom code.