Results for “inc_b”

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

Overview

APPS.CS_SR_UWQ_EMP_COUNT_V is a reporting view within the Oracle E-Business Suite Service (CS) module, deployed in release 12.1.1 and 12.2.2. The name encodes its purpose: "UWQ" refers to the Universal Work Queue, and "EMP_COUNT" indicates that the view was created to support employee-based workload counting and resource assignment analysis. The view projects a narrow, filtered subset of service incident records — specifically those owned by employees, as distinguished by the resource type designation RS_EMPLOYEE. This aligns directly with the term "rs_employee" that users search on, since RS_EMPLOYEE is the resource type literal stored on the incident record when the owning resource is an internal employee rather than a partner, group, or other resource classification.

Because the view is owned by APPS and is read-only in nature, it serves as a convenience layer for report queries, concurrent program data sources, and integration extracts that need a stable, pre-filtered cursor over open employee-owned incidents without re-implementing the underlying predicate logic each time.

Underlying Base Objects

The view is defined solely over a single documented base object, CS_INCIDENTS_B_SEC, which is itself a view (the secure, or "_SEC", variant of the incidents base entity). CS_INCIDENTS_B_SEC enforces security and organizational access rules on top of the underlying incident transaction table, so any query against CS_SR_UWQ_EMP_COUNT_V inherits that row-level security behavior. The dependency chain is therefore: CS_SR_UWQ_EMP_COUNT_V to CS_INCIDENTS_B_SEC to the physical incident tables beneath it.

The defining query applies two mandatory filters: STATUS_FLAG = 'O' and RESOURCE_TYPE = 'RS_EMPLOYEE'. The first restricts output to open records in the secure incident view; the second restricts output to incidents whose owning resource is an employee. No joins or aggregates are present in the view definition, so it is a straight projection with predicates, and its performance characteristics mirror those of the parent secure view plus the selectivity of the two filters.

Key Columns

• INCIDENT_ID — Surrogate primary key of the incident, usable for joins to other service objects.
• INCIDENT_NUMBER — The user-facing incident or service request number.
• INCIDENT_STATUS_ID — Foreign key to the incident status lookup, indicating the workflow state of the record.
• RESOURCE_ID — Alias of INCIDENT_OWNER_ID, representing the employee resource currently assigned as owner.
• RESOURCE_TYPE — The resource classification; by construction this is always RS_EMPLOYEE when rows are returned.
• OWNER_ID — Alias of INCIDENT_OWNER_ID, exposing the owner identity under a second logical name for downstream consumers.
• INCIDENT_SEVERITY_ID — Foreign key to the severity lookup, supporting prioritization and workload weighting.

Note that INCIDENT_OWNER_ID appears twice under the aliases RESOURCE_ID and OWNER_ID, which permits consumers to reference the same column under either semantic label without additional joins.

Common Use Cases and Queries

Typical usage includes workload dashboards that count open employee-owned incidents, Universal Work Queue configuration diagnostics, and data extracts that feed assignment or escalation logic. A representative query retrieves the count of open employee-owned incidents by severity:

• SELECT incident_severity_id, COUNT(*) FROM apps.cs_sr_uwq_emp_count_v GROUP BY incident_severity_id;
• SELECT incident_number, resource_id, owner_id FROM apps.cs_sr_uwq_emp_count_v WHERE incident_status_id = :p_status;
• SELECT resource_id, COUNT(*) FROM apps.cs_sr_uwq_emp_count_v GROUP BY resource_id ORDER BY 2 DESC;

Because the view already constrains STATUS_FLAG and RESOURCE_TYPE, consumers should not re-apply those filters; doing so is redundant. Any query should be run against the APPS schema, and access to the view depends on the responsibility and security profile of the calling user, since CS_INCIDENTS_B_SEC enforces secure access beneath it.