Results for “cs_sr_members_v”

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

Overview

CS_SR_MEMBERS_V is an APPS-owned database view in the Oracle E-Business Suite Service (CS) module. Its documented purpose is to present "Group and Individual Owners," acting as a unified registry of the resource identities that can be assigned as owners of service requests and related service objects. In a multi-tenant service organization, ownership is not limited to a single individual; a service request may be owned by a person, by a resource group, or by a team. CS_SR_MEMBERS_V normalizes these three ownership models into a single result set so that reporting, LOV queries, and integration layers can present and resolve owners without branching logic.

The view is frequently surfaced when users search on supporting resource objects such as JTF_RS_RESOURCE_EXTNS_VL, since that view is the primary source of resource name, category, and active-date information for the individual members exposed here. The view's role in EBS reporting is to provide a flattened, date-filtered list of owners that can be joined to service request headers and lines for owner-based analysis.

Underlying Base Objects

The view text is a three-way UNION ALL over the following documented base objects:

• JTF_RS_RESOURCE_EXTNS_VL — the resource extension view that supplies RESOURCE_ID, RESOURCE_NAME, CATEGORY, START_DATE_ACTIVE, and END_DATE_ACTIVE for individual resources.
• JTF_RS_GROUP_MEMBERS_VL — the group membership view supplying GROUP_ID, RESOURCE_ID, and CATEGORY for resources that belong to groups.
• JTF_RS_TEAM_MEMBERS_VL — the team membership view supplying TEAM_ID, TEAM_RESOURCE_ID, RESOURCE_TYPE, and CATEGORY for team members.

Each branch joins back to JTF_RS_RESOURCE_EXTNS_VL on RESOURCE_ID and CATEGORY to obtain the display name, and each branch applies an effective-date predicate: TRUNC(SYSDATE) must fall between NVL(TRUNC(START_DATE_ACTIVE), SYSDATE) and NVL(TRUNC(END_DATE_ACTIVE), SYSDATE). This ensures only currently active members are returned. The team branch additionally restricts to RESOURCE_TYPE = 'INDIVIDUAL'.

Key Columns

• GROUP_TYPE — a discriminator identifying the ownership model: the literal '999' for an individual resource, 'RS_GROUP' for a group member, and 'RS_TEAM' for a team member.
• GROUP_ID — the identifier of the owning group or team; for individual resources the literal value 999 is used as a placeholder.
• RESOURCE_ID — the unique identifier of the resource (person) that owns or belongs to the owner entity.
• RESOURCE_NAME — the display name of the resource, sourced from JTF_RS_RESOURCE_EXTNS_VL.
• RESOURCE_TYPE — formed by concatenating the literal 'RS_' with the resource CATEGORY, producing a normalized resource type label.

Common Use Cases and Queries

Typical usage includes building owner LOVs, resolving the display name for an owner stored on a service request, and producing owner workload reports. The following query lists active individual owners only:

SELECT resource_id, resource_name FROM cs_sr_members_v WHERE group_type = '999' ORDER BY resource_name;

To list all members of a specific team:

SELECT resource_id, resource_name FROM cs_sr_members_v WHERE group_type = 'RS_TEAM' AND group_id = :team_id;

To count active owners by ownership model:

SELECT group_type, COUNT(*) FROM cs_sr_members_v GROUP BY group_type;

Because the view already applies effective-date filtering, consumers gain a consistent, point-in-time view of valid owners, which simplifies joins to SR header and assignment tables in both custom reports and integrations.