Results for “cs_sr_members_v_sec”

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

Overview

CS_SR_MEMBERS_V_SEC is a secured database view owned by the APPS schema in Oracle E-Business Suite, residing in the CS (Service) product family. As its name and description indicate, it provides a security-filtered projection of the underlying CS_SR_MEMBERS_V view, which exposes service request team members. The view assembles a unified roster of resources — individuals, resource groups, and teams — that can be assigned to service requests, and is therefore central to Service Request team assignment, dispatch, and resource resolution logic in Release 12.1.1 and 12.2.2.

The view is especially relevant to the search term team_resource_id: it resolves team membership into a flat list of member resources by joining the team members view with the resource extensions view on TEAM_RESOURCE_ID. This makes CS_SR_MEMBERS_V_SEC a convenient source for reporting on which individuals belong to which teams and whether they are currently active.

Underlying Base Objects

ETRM documents the view as being defined over four referenced base objects, all themselves views:

• CS_JTF_RS_RESOURCE_EXTNS_SEC — the secured resource extensions view; supplies standalone resource rows filtered by security.
• JTF_RS_GROUP_MEMBERS_VL — resource group membership; joined to resource extensions to yield group members.
• JTF_RS_RESOURCE_EXTNS_VL — the resource extensions view used to supply RESOURCE_NAME and CATEGORY for groups and teams.
• JTF_RS_TEAM_MEMBERS_VL — team membership; joined on TEAM_RESOURCE_ID to the resource extensions view to yield individual team members.

The view text is a three-branch UNION ALL. The first branch emits standalone resources from the secured extensions view with a group type of '999'. The second branch emits resource-group members. The third branch emits team members, restricted to RESOURCE_TYPE = 'INDIVIDUAL'. Each branch applies an effective-date filter using START_DATE_ACTIVE and END_DATE_ACTIVE against SYSDATE, so only currently active resources are returned.

Key Columns

• GROUP_TYPE — identifies the source of the row: '999' for standalone resources, 'RS_GROUP' for group rows, and 'RS_TEAM' for team rows.
• GROUP_ID — the identifier of the containing resource group or team; '999' for standalone resources.
• RESOURCE_ID — the identifier of the individual member resource (or the standalone resource). This is the column that maps directly to the underlying team_resource_id concept for team rows.
• RESOURCE_NAME — the display name of the resource, sourced from the resource extensions view.
• RESOURCE_TYPE — a derived string formed by concatenating the literal 'RS_' with the resource CATEGORY, giving values such as 'RS_EMPLOYEE' or 'RS_PARTNER'.

Common Use Cases and Queries

Typical uses include reporting on service request team composition, resolving a team to its individual members, and listing active resources by category. The view is commonly joined to service request assignment tables on RESOURCE_ID.

List all active team members:

• SELECT group_id, resource_id, resource_name, resource_type FROM cs_sr_members_v_sec WHERE group_type = 'RS_TEAM';

Resolve members of a specific team:

• SELECT resource_id, resource_name, resource_type FROM cs_sr_members_v_sec WHERE group_type = 'RS_TEAM' AND group_id = :team_id;

List active resources of a given category:

• SELECT resource_id, resource_name FROM cs_sr_members_v_sec WHERE resource_type = 'RS_EMPLOYEE';

Because the definition is a union with a security filter inherited from CS_JTF_RS_RESOURCE_EXTNS_SEC, query results are already restricted to the resources the session is permitted to see, making the view suitable for both reporting and programmatic resource lookups.