Results for “cs_sr_uwq_team_count_v”

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

Overview

CS_SR_UWQ_TEAM_COUNT_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the Service (CS) product family. Its documented purpose is to support the Universal Work Queue (UWQ), the consolidated work-assignment framework used by Oracle Service, Telephony, and related modules. Specifically, the view exposes Service Request (incident) records grouped by team so that UWQ can resolve and display the count of Service Requests associated with a user's teams.

In EBS 12.1.1 and 12.2.2, UWQ aggregates and presents work items from multiple sources. Rather than counting from the base incident tables directly, UWQ queries lightweight, purpose-built views such as this one. The view is therefore not a general reporting object; it is an integration surface tuned for UWQ count and grouping logic. Because the view is defined only over active, open Service Requests owned by resource groups of type RS_TEAM, the counts it returns reflect the "current team queue" as UWQ defines it. Its status is VALID in the documented release, and its output is intended to be consumed by UWQ runtime code rather than by end users directly, though it remains queryable for diagnostic and ad hoc analysis.

Underlying Base Objects

The documented metadata lists a single referenced base object: CS_INCIDENTS_B_SEC, which is itself a view rather than a physical table. CS_INCIDENTS_B_SEC is a security-aware ("_SEC") projection over the Service Request incident data. In EBS, _SEC views typically wrap the underlying incident entity (CS_INCIDENTS_ALL_B / _TL and their associated tables) and apply organization or security predicates, ensuring that only data visible to the current responsibility and user context is returned.

CS_SR_UWQ_TEAM_COUNT_V applies two further filters on top of that projection: STATUS_FLAG = 'O' (open records only) and GROUP_TYPE = 'RS_TEAM' (ownership restricted to resource teams). No joins or aggregations appear in the documented view text; the row-level filtering is performed entirely in the WHERE clause, and any counting is expected to be carried out by the UWQ query that consumes the view. This delegation keeps the view simple and lets UWQ apply its own grouping and aggregation strategy.

Key Columns

• INCIDENT_ID — Primary identifier of the Service Request; joins to incident base entities for further detail.
• INCIDENT_NUMBER — The user-facing Service Request number displayed in UWQ.
• INCIDENT_STATUS_ID — Foreign key to the incident status lookup; supports status-based grouping or filtering in the queue.
• RESOURCE_ID — The owner group identifier (OWNER_GROUP_ID aliased as RESOURCE_ID), representing the team that owns the request.
• RESOURCE_TYPE — The group type (GROUP_TYPE), which the view fixes to RS_TEAM; identifies the owning entity as a resource team.
• OWNER_ID — The individual incident owner (INCIDENT_OWNER_ID) assigned to the request.
• INCIDENT_SEVERITY_ID — Foreign key to the severity lookup, allowing UWQ to prioritize or categorize counts by severity.

Collectively these columns give UWQ the minimum attributes needed to group requests by team and resource and to present counts alongside status and severity context.

Common Use Cases and Queries

Typical scenarios include verifying team-level queue volumes, diagnosing missing or miscounted UWQ entries, and building lightweight operational dashboards. A representative query counting open Service Requests per team follows:

• SELECT RESOURCE_ID, RESOURCE_TYPE, COUNT(*) SR_COUNT FROM APPS.CS_SR_UWQ_TEAM_COUNT_V GROUP BY RESOURCE_ID, RESOURCE_TYPE;
• SELECT INCIDENT_NUMBER, RESOURCE_ID, OWNER_ID, INCIDENT_SEVERITY_ID FROM APPS.CS_SR_UWQ_TEAM_COUNT_V WHERE RESOURCE_ID = :team_id;
• SELECT INCIDENT_STATUS_ID, COUNT(*) FROM APPS.CS_SR_UWQ_TEAM_COUNT_V GROUP BY INCIDENT_STATUS_ID;

Because the view does not itself aggregate, consumers supply GROUP BY and COUNT. Testing should account for the _SEC security layer: results depend on the responsibility and user profile in effect, so a query executed as a UWQ user may return fewer rows than one run with broader data access.