Results for “cs_incidents_b_sec”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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
- INCIDENT_ID — Primary key; unique identifier of the incident.
- INCIDENT_NUMBER — User-visible incident/ticket number.
- INCIDENT_DATE, CLOSE_DATE, EXPECTED_RESOLUTION_DATE, ACTUAL_RESOLUTION_DATE — Lifecycle timing fields.
- INCIDENT_STATUS_ID, INCIDENT_TYPE_ID, INCIDENT_URGENCY_ID, INCIDENT_SEVERITY_ID — Classification and status lookups.
- INCIDENT_OWNER_ID, OWNER_GROUP_ID — Ownership and assignment for routing.
- CUSTOMER_ID, ACCOUNT_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID, INSTALL_SITE_USE_ID — Customer and party/site references.
- INVENTORY_ITEM_ID, CUSTOMER_PRODUCT_ID, CURRENT_SERIAL_NUMBER, SYSTEM_ID — Installed-base product context.
- INCIDENT_ATTRIBUTE_1 … INCIDENT_ATTRIBUTE_15 — Extensible flexfield/DFF storage for customer-defined incident data.
- ORG_ID — Operating unit, the MOAC partitioning key.
- OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard WHO/audit and optimistic locking columns.
- KB_SOLUTION_ID, KB_TYPE, RESOLUTION_CODE — Knowledge and resolution linkage.
- WORKFLOW_PROCESS_ID, CUSTOMER_TICKET_NUMBER, ORIGINAL_ORDER_NUMBER — Process and external-reference identifiers.
- RECORD_IS_VALID_FLAG, PUBLISH_FLAG, INTERFACED_TO_DEPOT_FLAG — Status control flags.
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;
-
View: CS_INCIDENTS_B_SEC 12.2.2
APPS.CS_INCIDENTS_B_SEC·↳ CS_INCIDENTS_ALL_B·Explore CS module →
-
View: CS_INCIDENTS_B_SEC 12.1.1
Not implemented in this database·Explore CS module →
-
View: CS_SR_UWQ_EMP_COUNT_V 12.2.2
This view is used by the UWQ (Universal Work Queue) to query up the count of Service Requests against the user logged in.
APPS.CS_SR_UWQ_EMP_COUNT_V·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
This view is used by the UWQ (Universal Work Queue) to query up the count of Service Requests against the user's groups.
APPS.CS_SR_UWQ_GROUP_COUNT_V·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
View: CS_SR_UWQ_TEAM_COUNT_V 12.2.2
This view is used by the UWQ (Universal Work Queue) to query up the count of Service Requests against the user's teams.
APPS.CS_SR_UWQ_TEAM_COUNT_V·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
This view is used by the UWQ (Universal Work Queue) to query up the count of Service Requests against the user's groups.
APPS.CS_SR_UWQ_GROUP_COUNT_V·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
View: CS_SR_UWQ_TEAM_COUNT_V 12.1.1
This view is used by the UWQ (Universal Work Queue) to query up the count of Service Requests against the user's teams.
APPS.CS_SR_UWQ_TEAM_COUNT_V·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
View: CS_SR_UWQ_EMP_COUNT_V 12.1.1
This view is used by the UWQ (Universal Work Queue) to query up the count of Service Requests against the user logged in.
APPS.CS_SR_UWQ_EMP_COUNT_V·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
View: CS_NEW_INCIDENTS_V_SEC 12.2.2
This is a secured view created on top of the view CS_NEW_INCIDENTS_V
APPS.CS_NEW_INCIDENTS_V_SEC·↳ CSC_HZ_PARTIES_SELF_V·↳ CS_HZ_SR_CONTACT_POINTS·↳ CS_INCIDENTS_ALL_TL·Explore CS module →
-
View: CSD_REPAIR_ESTIMATE_V 12.1.1
Fetches the estimate header for repair orders.
APPS.CSD_REPAIR_ESTIMATE_V·↳ CSD_REPAIRS·↳ CSD_REPAIR_ESTIMATE·↳ CS_INCIDENTS_B_SEC·Explore CSD module →
-
View: CSD_REPAIR_ESTIMATE_V 12.2.2
Fetches the estimate header for repair orders.
APPS.CSD_REPAIR_ESTIMATE_V·↳ CSD_REPAIRS·↳ CSD_REPAIR_ESTIMATE·↳ CS_INCIDENTS_B_SEC·Explore CSD module →
-
Service Request
APPS.CS_SERVICE_REQUEST_PUB_V·↳ CSI_ITEM_INSTANCES·↳ CS_INCIDENTS_ALL_TL·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
This view is being used by Service History Tab
APPS.CS_SR_SERVICE_HISTORY_V·↳ CSI_ITEM_INSTANCES·↳ CS_INCIDENTS_ALL_TL·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
View: CS_NEW_INCIDENTS_V_SEC 12.1.1
This is a secured view created on top of the view CS_NEW_INCIDENTS_V
APPS.CS_NEW_INCIDENTS_V_SEC·↳ CSC_HZ_PARTIES_SELF_V·↳ CS_HZ_SR_CONTACT_POINTS·↳ CS_INCIDENTS_ALL_TL·Explore CS module →
-
This view is being used by Service History Tab
APPS.CS_SR_SERVICE_HISTORY_V·↳ CSI_ITEM_INSTANCES·↳ CS_INCIDENTS_ALL_TL·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
View: CS_SR_SEARCH_NO_CONT_V 12.2.2
This view is used in the SR find window on Bali spread table and in the Service History Bali Spreadtable of SR Tab
APPS.CS_SR_SEARCH_NO_CONT_V·↳ CSI_ITEM_INSTANCES·↳ CS_INCIDENTS_ALL_TL·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
This is a secured view on cs_incidents_links_to_v
APPS.CS_INCIDENT_LINKS_TO_V_SEC·↳ CS_INCIDENTS_ALL_TL·↳ CS_INCIDENTS_B_SEC·↳ CS_INCIDENT_LINKS·Explore CS module →