Results for “sr_type_category_id”

34 results




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

Overview

CS_SR_TYPE_CATEGORIES_TL is the translation table for service request type categories in the Oracle E-Business Suite Service (CS) module. It belongs to the Oracle Service foundation schema and stores language-specific textual attributes for each service request type category defined in the base table CS_SR_TYPE_CATEGORIES_B. In Oracle EBS 12.1.1 and 12.2.2, multilingual deployments rely on this table to render category names and descriptions in the session language of the user, while a single language-independent definition of the category is maintained in the _B table.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This is a reasonable heuristic: the table carries descriptive, language-dependent attributes (NAME, DESCRIPTION) keyed by a surrogate identifier, and it references a parent entity rather than joining two independent business entities. It therefore behaves like a dependent descriptive satellite attached to the CS_SR_TYPE_CATEGORIES_B hub, rather than a hub or link in its own right.

Key Information Stored

The table contains eleven documented columns. The most significant are:

  • SR_TYPE_CATEGORY_ID — The surrogate identifier of the parent service request type category. Together with LANGUAGE it forms part of the primary key CS_SR_TYPE_CATEGORIES_TL_PK and is the foreign key to CS_SR_TYPE_CATEGORIES_B.
  • LANGUAGE — The NLS language code identifying which translation this row provides.
  • NAME — The translated display name of the service request type category as shown to end users.
  • DESCRIPTION — The translated descriptive text for the category.
  • SOURCE_LANG — The language from which this translation was derived, supporting the Multi-Language Support (MLS) translation workflow.
  • OBJECT_VERSION_NUMBER — The optimistic locking column used by the EBS framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit ("WHO") columns recording the actor, timestamp, and login session of the row's creation and most recent modification.

The unique index CS_SR_TYPE_CATEGORIES_TL_U1 is defined on (SR_TYPE_CATEGORY_ID, LANGUAGE), confirming that exactly one translated row exists per category per language — the business-key candidate that enforces translation uniqueness. The distinction between the surrogate PK and this business-key index is important when validating or querying translations.

Common Use Cases and Queries

Typical reporting and integration scenarios for this table centre on producing readable, language-appropriate labels for service request categories in bilingual or multilingual implementations. A common query joins the translation table to its base table to retrieve the name for a specific language:

SELECT b.sr_type_category_id, t.name, t.description
FROM cs_sr_type_categories_b b, cs_sr_type_categories_tl t
WHERE b.sr_type_category_id = t.sr_type_category_id
AND t.language = USERENV('LANG');

To detect categories missing a translation for a target language, a reporting query can outer-join the translation table and filter where the translated NAME is null. Data-migration and data-quality audits frequently compare SOURCE_LANG and LANGUAGE values to confirm translation provenance, and change-tracking reports use LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recently revised terminology. Because the table is satellite-leaning, analytical models that stage the category hierarchy typically load NAME and DESCRIPTION here as descriptive attributes keyed by SR_TYPE_CATEGORY_ID and LANGUAGE.

Related Objects

  • CS_SR_TYPE_CATEGORIES_B — The base (language-independent) table holding the category definition; joined on SR_TYPE_CATEGORY_ID and the FK target of this translation table.
  • CS_SR_TYPE_CATEGORIES_VL / _V — The MLS view that unions base and translation columns to present a single logical category record in the user's language.
  • CS_SR_TYPES / CS_SR_TYPE_CATEGORIES_B linkage — Service request types reference categories; join through the category identifier to surface translated category names on service request type reports.
  • CS_SR_TYPE_SS / CS_INCIDENTS_ALL — Service request and incident entities that ultimately consume category labels for user display and reporting.
  • FND_LANGUAGES — Referenced conceptually through the LANGUAGE and SOURCE_LANG columns to validate installed and translation languages.
  • FND_APPLICATION / FND_OBJECTS — Framework metadata used for MLS registration and access control over the category entity.

Together these objects form the translation layer that allows a single service request category definition to be presented correctly across all installed languages in Oracle EBS 12.1.1 and 12.2.2.