Search Results cs_sr_owners_v




Overview
Explore in AI Chat

Overview

CS_SR_OWNERS_V is a Service (CS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides a single, unified list of service resources that can be assigned as owners of service requests, exposing resources of type EMPLOYEE, TEAM, and GROUP. Rather than querying several Resource Manager tables independently, a form, report, or integration can consume this view to populate owner-selection lists, LOVs, and assignment logic consistently.

In the Oracle EBS reporting and integration layer, the view serves as the canonical enumeration of "who or what can own a service request." Because it normalizes employees, teams, and support groups into one record set, it removes the need for consumers to understand the physical layout of JTF_RS_EMP_DTLS_VL, JTF_RS_GROUPS_VL, and JTF_RS_TEAMS_VL. The view is documented in the ETRM as VALID for release 12.2.2, with equivalent availability in 12.1.1.

Underlying Base Objects

The view text is a three-way UNION ALL, with each branch drawing from a different Resource Manager base object:

The team and group branches are further restricted to usage values of 'SUPPORT', reflecting the Service product's requirement that only support-designated teams and groups appear as owner candidates. Each branch applies an effective-dating filter: TRUNC(SYSDATE) must fall between the start and end active dates, with NVL defaulting a missing boundary to the current date. This makes the view return only currently effective resources at query time.

Key Columns

The RESOURCE_TYPE column is the critical discriminator, since RESOURCE_ID values for employees, teams, and groups originate from separate ID spaces and must not be compared across types.

Common Use Cases and Queries

Typical uses include populating an owner LOV on a Service Request form, driving assignment or workload reports, and feeding integrations that require a flat owner roster. A basic listing returns all currently effective owners:

SELECT resource_id, resource_number, resource_name, resource_type
FROM cs_sr_owners_v
ORDER BY resource_type, resource_name;

To restrict to employee owners only:

SELECT resource_id, resource_name, support_site_id, org_id
FROM cs_sr_owners_v
WHERE resource_type = 'RS_EMPLOYEE';

To return only teams and support groups:

SELECT resource_id, resource_name, resource_type, usage
FROM cs_sr_owners_v
WHERE resource_type IN ('RS_GROUP','RS_TEAM');

Because the view already applies effective-date and SUPPORT usage filters, consumers should not re-apply them; doing so risks excluding valid rows if the underlying definitions change. Join back to the SQL view's base objects only when additional attributes, such as employee organization or group membership detail, are required.