Results for “group_end_date_active”

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

Overview

AST_RS_GRP_VALID_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AST (TeleSales) product family. It exposes the currently valid relationship between resource groups and TeleSales roles, joining group definitions to the role relations that link resources of type RS_GROUP to a role. Because the view is filtered at query time to return only rows whose effective date ranges include the current system date, it functions as a point-in-time validation view rather than as a historical ledger of assignments. Consumers therefore use it to determine which TeleSales groups and role memberships are active today, which is the typical requirement for telemarketing assignment, campaign execution, and operational reporting. The view is read-only and is intended primarily for inquiry and integration rather than transactional maintenance; group and role data are created and maintained through the underlying TeleSales administration screens.

Underlying Base Objects

The view text is defined over two base views in the JTF resource schema, joined on group identity:

• JTF_RS_GROUPS_VL (aliased RS) — supplies the group header information, including GROUP_ID, GROUP_NUMBER, GROUP_NAME, GROUP_DESC, the EXCLUSIVE_FLAG, and the group-level active date range.
• JTF_RS_ROLE_RELATIONS_VL (aliased ROL) — supplies the role relation records that bind a resource to a role, including ROLE_RELATE_ID, ROLE_ID, ROLE_NAME, the resource type and resource id, the member/admin/lead/manager flags, the role type code, and the role-level active date range.
• FND_GLOBAL (package) — documented as a referenced object, consistent with the standard Oracle EBS practice of deriving the effective application context and, where applicable, the current date for date-range validation within the view's WHERE clause.

The join condition restricts output to rows where the group id matches the role resource id and the role resource type is explicitly 'RS_GROUP'. A further predicate limits role records to ROLE_TYPE_CODE = 'TELESALES', so the view returns only TeleSales role relations and excludes other role types defined in the resource schema. Both the group and the role date ranges must encompass TRUNC(SYSDATE), with NVL and TRUNC applied so that open-ended dates are treated as unbounded.

Key Columns

• GROUP_ID, GROUP_NUMBER, GROUP_NAME, GROUP_DESCRIPTION — identity and descriptive attributes of the TeleSales resource group.
• EXCLUSIVE_FLAG — indicates whether membership in the group is exclusive; this is the column most frequently cited in searches against this view and is central to determining whether a resource may belong to multiple groups simultaneously.
• GROUP_START_DATE_ACTIVE, GROUP_END_DATE_ACTIVE — effective date range of the group record as exposed by the view.
• ROLE_RELATE_ID, ROLE_ID, ROLE_NAME, ROLE_MEANING, ROLE_TYPE_CODE — identifiers and descriptive attributes of the associated role relation; ROLE_TYPE_CODE is effectively fixed to TELESALES by the view predicate.
• ROLE_RESOURCE_TYPE, ROLE_RESOURCE_ID — the resource type and identifier that the role relation points to; ROLE_RESOURCE_TYPE is always 'RS_GROUP' in this view.
• ROLE_MEMBER_FLAG, ROLE_ADMIN_FLAG, ROLE_LEAD_FLAG, ROLE_MANAGER_FLAG — role capability indicators describing the nature of the membership.
• ROLE_START_DATE_ACTIVE, ROLE_END_DATE_ACTIVE — effective date range of the role relation.

Common Use Cases and Queries

Typical uses include validating that a group is assignable before a TeleSales campaign is launched, reporting on the composition of exclusive versus non-exclusive groups, and confirming that a role relation remains within its active window. A simple listing of active groups and their exclusive setting is shown below.

• SELECT group_number, group_name, exclusive_flag FROM ast_rs_grp_valid_v ORDER BY group_number;
• SELECT r.group_number, r.role_name, r.role_member_flag, r.role_admin_flag FROM ast_rs_grp_valid_v r WHERE r.exclusive_flag = 'Y';
• SELECT r.group_id, r.group_name, COUNT(*) role_count FROM ast_rs_grp_valid_v r GROUP BY r.group_id, r.group_name;

Because date filtering is embedded in the view definition, no additional effective-date predicate is required; queries run against this view always reflect the state of group and role relations as of the current date.