Results for “cs_incident_types_vl_sec”

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

Overview

The CS_INCIDENT_TYPES_VL_SEC view is a security-enabled, multi-language (VL) reporting object owned by the APPS schema in Oracle E-Business Suite. It resides within the FND - Application Object Library product grouping and exposes incident (service request) type setup data that has been filtered through the Service (CS) security model. The _SEC suffix indicates that the view returns only those incident types to which the current user has been granted access by Oracle's Service security framework, rather than the complete set of defined types.

Because the view joins the translation table CS_INCIDENT_TYPES_TL to a secured base selection view, it resolves the display name and description to the language of the running session through USERENV('LANG'). This makes it suitable for both multilingual reporting and integration scenarios where incident type lists must be presented in the end user's language while honoring row-level security.

Underlying Base Objects

The view is defined over two referenced base objects, both resolved through synonyms in the APPS schema:

• CS_INCIDENT_TYPES_TL — the translation table holding the language-specific NAME, DESCRIPTION, LANGUAGE, and SOURCE_LANG columns.
• CS_SR_TYPES_SELECT_SEC — the security-filtered selection view supplying the operational and attribute columns of the incident type.

The join predicate links the two on INCIDENT_TYPE_ID, with the additional filter T.LANGUAGE = USERENV('LANG') restricting the translation row to the current session language. The view also exposes the underlying ROWID of the secured base row as ROW_ID, preserving the ability to identify the physical source row for DML or debugging purposes. In EBS 12.1.1 and 12.2.2 the definition is essentially identical; any differences relate to the underlying tables rather than to this view text.

Key Columns

• INCIDENT_TYPE_ID, INCIDENT_SUBTYPE, PARENT_INCIDENT_TYPE_ID — identify the type and its hierarchical position.
• NAME, DESCRIPTION — language-resolved descriptive text from the TL table.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating for the type.
• SEEDED_FLAG, MAINTENANCE_FLAG, CMRO_FLAG — indicate whether the row is Oracle-seeded or user-maintained, and whether it is used for maintenance or CMRO activity.
• WORKFLOW, WEB_WORKFLOW, TASK_WORKFLOW, ABORT_WORKFLOW_CLOSE_FLAG, AUTOLAUNCH_WORKFLOW_FLAG — define the workflow process invoked by the incident type.
• WEB_ENTRY_FLAG, WEB_IMAGE_FILENAME, IMAGE_FILE_NAME — control self-service web entry presentation.
• BUSINESS_PROCESS_ID, STATUS_GROUP_ID, WEIGHT — link the type to a business process, status group, and sort weight.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the standard descriptive flexfield columns.
• DETAILED_ERECORD_REQ_FLAG — indicates whether a detailed electronic record is required.

Common Use Cases and Queries

Typical uses include LOV population, reporting on available incident types per user, and integration extracts that must respect Service security. A basic query is:

• SELECT incident_type_id, name, description, start_date_active, end_date_active FROM cs_incident_types_vl_sec WHERE start_date_active <= SYSDATE AND NVL(end_date_active, SYSDATE+1) > SYSDATE ORDER BY name;
• SELECT incident_type_id, name, workflow, web_entry_flag FROM cs_incident_types_vl_sec WHERE web_entry_flag = 'Y';
• SELECT incident_type_id, name, cmro_flag, maintenance_flag FROM cs_incident_types_vl_sec WHERE cmro_flag = 'Y';

Because access is filtered by the security view, run these queries under an authenticated EBS session rather than as a raw database user to obtain the intended result set.