Search Results okc_resource_groups_v




Overview
Explore in AI Chat

Overview

OKC_RESOURCE_GROUPS_V is a reporting view owned by the APPS schema and shipped as part of the Oracle Contracts Core (OKC) product family. Its documented purpose is to expose the resource groups associated with the Contracts role, allowing Oracle E-Business Suite modules, concurrent programs, and custom extensions to resolve which resource groups participate in contract-related role assignments without querying the underlying resource-management tables directly. The view is classified as VALID in the ETRM 12.2.2 metadata, which indicates that it compiles cleanly against the base objects in a supported release and can be safely referenced by downstream code.

In Oracle EBS 12.1.1 and 12.2.2, views such as this act as an integration surface. Rather than requiring developers to join the JTF resource group tables with the OKX resource role tables and apply the correct filters, the view presents a consolidated, contract-oriented result set. This reduces the risk of inconsistent filtering logic and aligns reporting output with the semantics used internally by the Contracts application.

Underlying Base Objects

The view text is defined as a join between two objects, both of which are themselves views:

  • JTF_RS_GROUPS_VL — the multi-language view over the JTF resource groups entity, providing group identity, numbering, descriptive attributes, and the active date range.
  • OKX_RESOURCE_ROLES_V — the resource-role view, providing the association between a resource (here restricted to resource type RS_GROUP) and the roles it is granted, together with status and delete-flag information.

The join is expressed as RR.RESOURCE_TYPE = 'RS_GROUP' AND RR.RESOURCE_ID = RGP.GROUP_ID, and a SELECT DISTINCT is applied to eliminate duplicate rows that could arise if a group is associated with multiple qualifying role rows. Because both sources are views, OKC_RESOURCE_GROUPS_V inherits their security and language-handling behavior; the VL suffix on JTF_RS_GROUPS_VL indicates that translation of the group name and description is resolved according to the session language.

Key Columns

  • GROUP_ID — the unique identifier of the resource group, carried over from JTF_RS_GROUPS_VL. This is the value matched against RESOURCE_ID in the role view.
  • GROUP_NUMBER — the user-visible group number, typically used as a business key in reports and interfaces.
  • NAME — the translated group name, aliased from GROUP_NAME; the alias is retained in the view definition.
  • DESCRIPTION — the translated description, aliased from GROUP_DESC.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range of the group. A null end date conventionally denotes an open-ended or currently active group.
  • STATUS — the status of the group-to-role association, supplied by OKX_RESOURCE_ROLES_V.
  • DELETE_FLAG — indicates whether the underlying role association has been logically deleted, allowing queries to exclude obsolete rows.

Common Use Cases and Queries

Typical usages include validating group availability before contract role assignment, populating LOVs or custom inquiry screens, and feeding extracts that reconcile contract resource roles. Because the view already encapsulates the role-type filter, most queries are straightforward.

SELECT group_id, group_number, name, status
FROM   okc_resource_groups_v
WHERE  delete_flag = 'N'
AND    (end_date_active IS NULL OR end_date_active > SYSDATE);

To resolve a group by its business number:

SELECT group_id, name, description, start_date_active
FROM   okc_resource_groups_v
WHERE  group_number = :p_group_number;

Reporting extracts frequently join the view to contract role assignment tables on GROUP_ID to list the contracts for which a given group is eligible. When used in this manner, the DISTINCT semantics of the view guarantee that no group is returned more than once, which simplifies aggregation and avoids duplicate contract lines in output. As with all APPS-owned dictionary objects, the view should be referenced through a synonym or fully qualified name, and should not be modified or replaced.