Search Results cs_incidents_b_sec




Overview
Explore in AI Chat

Overview

CS_INCIDENTS_B_SEC is a Service (CS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the "B" (base) entity attributes of service incidents — the foundation records created and managed by the Oracle TeleService / Depot Repair incident framework. Within the EBS architecture, the suffix "_B_SEC" signals that the view is a security-wrapped projection of a base table, intended to provide controlled, read-oriented access to incident header data without exposing the full internal column set of the underlying entity. Because incidents are partitioned by operating unit (ORG_ID) and governed by Multi-Org Access Control (MOAC), this view is commonly referenced in reports, concurrent programs, OAF pages, and integrations where a security-filtered incident base is required.

The view is documented as "Not implemented in this database" in the source ETRM repository, meaning its actual DDL is deployed only in environments where the CS incident schema is installed and licensed. Its structure, however, is published and stable across 12.1.1 and 12.2.2.

Underlying Base Objects

ETRM metadata identifies a single referenced base object: CS_INCIDENTS_ALL_B, resolved through a synonym. CS_INCIDENTS_ALL_B is the multi-org base table that stores one row per service incident, holding the common header attributes shared by all incident subtypes. CS_INCIDENTS_B_SEC is therefore a direct, column-selective view over that table. It does not aggregate, join, or transform data; its role is to present the base layer under a security-oriented name, allowing APPS-level grants and security policies to be applied consistently. The corresponding translated/"T" and unique/"U" layers (CS_INCIDENTS_ALL_TL, CS_INCIDENTS_ALL_TL etc.) supply the descriptive, language-dependent fields, while this view carries the language-independent base columns.

Key Columns

Common Use Cases and Queries

Typical uses include incident aging reports, backlog analytics, integration extracts to external ITSM systems, and reconciliations between TeleService incidents and installed-base records. Because the view carries ORG_ID, queries should respect MOAC filters.

Sample: incident counts by status and operating unit.

SELECT incident_status_id, org_id, COUNT(*) FROM cs_incidents_b_sec GROUP BY incident_status_id, org_id;

Sample: open incidents for a customer with expected resolution dates.

SELECT incident_number, incident_date, expected_resolution_date FROM cs_incidents_b_sec WHERE customer_id = :p_customer_id AND close_date IS NULL ORDER BY incident_date DESC;

Sample: incidents linked to a specific inventory item.

SELECT incident_number, current_serial_number, owner_group_id FROM cs_incidents_b_sec WHERE inventory_item_id = :p_item_id;