Results for “cs_incident_statuses_tl”

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

Overview

CS_INCIDENT_STATUSES_TL is the translation (TL) table for Service Request statuses within the Oracle E-Business Suite CS - Service product family. In Oracle EBS, a "_TL" table stores the language-dependent, user-visible descriptive attributes of an entity, while the corresponding "_B" (base) table stores the language-independent and surrogate-key attributes. Together, CS_INCIDENT_STATUSES_B and CS_INCIDENT_STATUSES_TL form the complete definition of an incident status — for example, "Open", "Pending Customer", "Closed" — as presented to users of the Service Request (Oracle iSupport and TeleService) application.

Each row in this table represents one status description expressed in one installed language. The table is owned by the CS schema and is documented as VALID in both ETRM 12.1.1 and 12.2.2. Because the base table holds the operational attributes and this table holds only the translated name and description keyed to the base entity, the heuristic Data Vault classification mined from the foreign-key structure is link — a modeling suggestion that positions the row as an association between an incident status identifier, a language, and a source language rather than as a standalone hub or satellite.

Key Information Stored

The documented physical schema for 12.2.2 contains twelve columns. The most significant are:

• INCIDENT_STATUS_ID — the surrogate identifier of the status; the first component of the composite primary key CS_INCIDENT_STATUSES_TL_PK and the foreign key to CS_INCIDENT_STATUSES_B.
• LANGUAGE — the language code of the current translated row; the second component of the primary key and a foreign key to FND_LANGUAGES.
• SOURCE_LANG — the language from which the row was originally entered or translated; also parented to FND_LANGUAGES.
• NAME — the translated display name of the status, and a business-key candidate via the unique index CS_INCIDENT_STATUS_TL_U1.
• DESCRIPTION — the translated long description of the status.
• SECURITY_GROUP_ID — the operating-unit/security grouping used by Multi-Org Access Control; foreign key to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the edition label used by the EBS online patching (adop) infrastructure; part of the unique index CS_INCIDENT_STATUS_TL_U1.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle Applications Who columns that audit the row lifecycle.

The surrogate primary key is (INCIDENT_STATUS_ID, LANGUAGE); the documented business-key candidate is (INCIDENT_STATUS_ID, LANGUAGE, ZD_EDITION_NAME). The distinction matters because code that resolves a status by name should use the unique index, while joins to the base table should always use the surrogate key plus language.

Common Use Cases and Queries

Typical usage involves enriching a Service Request with the localized status label for reporting or for rendering on a form. The standard pattern joins the base table to its translations and filters by the runtime language, using FND_LANGUAGES to resolve the session language:

SELECT b.incident_status_id,
       t.name,
       t.description
FROM   cs_incident_statuses_b b,
       cs_incident_statuses_tl t
WHERE  b.incident_status_id = t.incident_status_id
AND    t.language = USERENV('LANG');

Reporting scenarios include status-distribution analyses of service requests filtered to the reporting language, validation of translation completeness (statuses missing a translation for an installed language), and data-migration or conversion programs that load new statuses into the base table and their translations into this table in the same unit of work. Because ZD_EDITION_NAME participates in the unique index, queries that run under online patching should restrict to the active edition unless the query is deliberately edition-aware.

Related Objects

The most significant objects that this table interacts with, based on the documented foreign keys and primary-key relationships, are:

• CS_INCIDENT_STATUSES_B — the base table supplying the language-independent status definition; joined on INCIDENT_STATUS_ID.
• FND_LANGUAGES — referenced twice, through LANGUAGE and SOURCE_LANG, to validate installed languages and translation sources.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for multi-org security.
• CS_INCIDENTS_ALL — the Service Request (incident) entity whose status is resolved through CS_INCIDENT_STATUSES_B/TL for display and reporting.
• CS_INCIDENT_TYPES_B / CS_INCIDENT_TYPES_TL — the parallel type definition whose translations follow the same _B/_TL pattern.

In practice, custom reports and extensions should query this table through its documented primary key and unique indexes, and should not write to it directly; status translations are normally maintained through the CS setup forms or the supported Service Request APIs that manage the base and translation rows together.