Results for “cs_sr_uwq_group_count_v”

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

Overview

CS_SR_UWQ_GROUP_COUNT_V is a Service (CS) module database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the Universal Work Queue (UWQ) by returning the count of Service Requests (incidents) associated with a user's resource groups. UWQ is the agent-facing dashboard within Oracle Service that aggregates and prioritizes work items across queues, and this view supplies the group-level SR metrics that drive those queue displays.

The view is a read-only, query-oriented object. It exposes a filtered projection of open Service Requests (status flag 'O') whose owning resource type is a group (GROUP_TYPE = 'RS_GROUP'). Because it is consumed by UWQ runtime queries rather than by direct transactional DML, it functions as a lightweight reporting and integration surface for SR workload counts by group.

The view is recorded as VALID and is registered under the CS - Service product family in ETRM 12.2.2 documentation.

Underlying Base Objects

Per the documented metadata, the view is defined solely over CS_INCIDENTS_B_SEC, itself a view (a security-enabled subset of the incidents entity). The definition selects from CS_INCIDENTS_B_SEC INC_B and applies two predicates: STATUS_FLAG = 'O' (open incidents only) and GROUP_TYPE = 'RS_GROUP' (incidents owned by a resource group rather than an individual). The _SEC suffix on the base object indicates that underlying security rules — typically organization/resource visibility constraints enforced elsewhere in the CS security model — are already applied at that layer, so CS_SR_UWQ_GROUP_COUNT_V inherits the caller's visibility scope.

The view projects seven columns from the base object without joins, aggregations, or additional filtering, meaning the "count" semantics are realized by the consuming UWQ query (typically a COUNT or GROUP BY over RESOURCE_ID) rather than embedded in the view definition itself.

Key Columns

• INCIDENT_ID — Primary identifier of the Service Request (incident) record.
• INCIDENT_NUMBER — User-facing SR number used for display and drill-down in UWQ.
• INCIDENT_STATUS_ID — Foreign key to the incident status; combined with the 'O' filter it denotes open work.
• RESOURCE_ID — Populated from OWNER_GROUP_ID; identifies the resource group that owns the SR. This is the primary grouping key for count queries.
• RESOURCE_TYPE — Populated from GROUP_TYPE; constrained to 'RS_GROUP', confirming the count is per group.
• OWNER_ID — From INCIDENT_OWNER_ID, the individual owner where assigned.
• INCIDENT_SEVERITY_ID — Severity classification, useful for prioritizing counts within a queue.

Common Use Cases and Queries

Typical use is UWQ-driven counting of open SRs per resource group, often filtered to a user's accessible groups via the inherited security layer. A representative query totals open SRs per group:

• SELECT resource_id, COUNT(incident_id) sr_count FROM cs_sr_uwq_group_count_v GROUP BY resource_id;
• SELECT resource_id, incident_severity_id, COUNT(*) FROM cs_sr_uwq_group_count_v GROUP BY resource_id, incident_severity_id;
• SELECT incident_number, incident_status_id FROM cs_sr_uwq_group_count_v WHERE resource_id = :group_id;

These patterns support agent dashboards, workload balancing, and severity-weighted queue metrics. Because filtering and security are delegated to CS_INCIDENTS_B_SEC, consumers should not expect the view to enforce resource-level restrictions beyond those inherited from the base object.