Results for “oks_resource_groups_v”

32 results




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

Overview

The view APPS.OKS_RESOURCE_GROUPS_V is a reporting and integration object within the Oracle E-Business Suite Service Contracts (OKS) module. It exposes resource group records that are eligible for assignment to service contract coverages, presenting a unified, denormalized projection of group identity, descriptive attributes, lifecycle dates, and a computed status indicator. The view is owned by the APPS schema and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2 environments. As documented in the ETRM repository, its stated purpose is to provide "Resource Groups for Service Contracts Coverages."

Rather than storing data of its own, the view functions as a presentation layer over the JTF resource group definitions owned by Oracle CRM Foundation (JTF). This design allows Service Contracts functionality — particularly coverage definition, resource qualification, and assignment rule processing — to query a consistent, OKS-oriented resource group interface while the authoritative master data remains within the shared JTF resource model. Because the view flattens the resource group into a single addressable row per group, it is well suited for LOV queries, concurrent program extracts, and inbound integration interfaces.

Underlying Base Objects

The documented definition references a single base object: JTF_RS_GROUPS_VL, itself a view over the JTF resource group tables. In the view text supplied in the ETRM metadata, this base view is aliased as RSC. Because JTF_RS_GROUPS_VL is a translated (VL) view, it supplies the language-specific GROUP_NAME and GROUP_DESC values that OKS_RESOURCE_GROUPS_V surfaces as NAME and DESCRIPTION. The join is effectively a one-to-one projection with column renaming and syntactic augmentation; no additional Oracle EBS tables are joined within the view text.

This tight coupling means the view inherits the security and multi-org characteristics of the JTF resource group layer. Any change to the underlying resource group record — activation, deactivation, renaming, or email update — is immediately reflected in query results.

Key Columns

  • RESOURCE_NUMBER — The identifier most users search for; aliased from RSC.GROUP_NUMBER. It is the business-facing group number used to reference a resource group in Service Contracts coverage setups.
  • RESOURCE_TYPE — A literal constant, 'RS_GROUP', distinguishing these rows from other resource types in the resource model.
  • NAME — The language-specific resource group name, sourced from RSC.GROUP_NAME.
  • DESCRIPTION — The translated group description (RSC.GROUP_DESC).
  • START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date bounds of the group record.
  • STATUS — A computed column using nested DECODE and SIGN expressions comparing TRUNC(SYSDATE) against the active date range. It returns 'A' when the group is active today, or 'I' when the current date falls before the start date or after the end date (the view treats END_DATE_ACTIVE as inclusive via NVL(..., SYSDATE)).
  • EMAIL_ADDRESS — The group's email address, inherited from the JTF resource group definition.
  • ID1 — The group identifier (RSC.GROUP_ID), useful for programmatic joins back to JTF.
  • ID2 — A literal '#', a placeholder retained for interface compatibility.

Common Use Cases and Queries

A frequent requirement is locating a resource group by the business number that users search on. The following query retrieves the group's number, name, status, and email:

  • SELECT resource_number, name, resource_type, status, email_address FROM apps.oks_resource_groups_v WHERE resource_number = :p_number;

Because the view computes a status flag, it is also practical to list only currently active groups for use in a coverage assignment interface or validation routine:

  • SELECT resource_number, name, start_date_active, end_date_active FROM apps.oks_resource_groups_v WHERE status = 'A' ORDER BY name;

The ID1 column supports joins back to JTF resource group tables when additional detail is required. Integrating parties should note that the view is read-only and that all mutation occurs against the JTF base objects; consequently the view is best treated as a query and validation surface rather than a target for DML.