Search Results okc_resource_users_v




Overview
Explore in AI Chat

Overview

OKC_RESOURCE_USERS_V is a reporting and integration view owned by the APPS schema within the OKC (Contracts Core) product of Oracle E-Business Suite. It exposes a consolidated, distinct list of individual resources that are assigned to roles in the resource role framework, effectively presenting the set of "resource users" — typically employees, contingent workers, or other party-based individuals — who can be referenced as resources on contracts and related transactions. The view is marked VALID in the ETRM data dictionary for both 12.1.1 and 12.2.2, and its structure is unchanged across those releases.

The view is important because the OKC resource model is built on generic resource and role constructs. Rather than joining resource and role data manually through the top-level OKX views, developers and report authors can query OKC_RESOURCE_USERS_V to obtain a pre-filtered, de-duplicated list of individual resource users, including their active date range and current role status. It is commonly used in contract party/resource lookups, LOV-driven forms, and integration extracts where the caller needs to know which individuals are valid resources.

Underlying Base Objects

The view is defined over two documented view objects together with a package:

  • OKX_RESOURCES_V — the resource master view, supplying resource identity, number, type, name, description, and active date attributes.
  • OKX_RESOURCE_ROLES_V — the resource-to-role assignment view, supplying the role association, role status, and delete flag. This object is the source of the STATUS and DELETE_FLAG columns.
  • FND_GLOBAL — the standard EBS package referenced by the underlying OKX views (typically for session/user context, such as the current user or organization), rather than directly by OKC_RESOURCE_USERS_V itself.

The join is a simple equijoin: RR.RESOURCE_ID = RES.ID1, with a fixed filter of RR.RESOURCE_TYPE = 'RS_INDIVIDUAL'. The RES.ID1 surrogate identifier from OKX_RESOURCES_V is aliased to the view column ID. A SELECT DISTINCT is applied so that multiple role assignments for the same individual do not produce duplicate resource rows unless the combined attribute set differs.

Key Columns

  • ID — the resource identifier, sourced from RES.ID1 in OKX_RESOURCES_V. This is the value typically stored as a foreign key by consuming modules.
  • RESOURCE_NUMBER — the human-readable resource number assigned to the individual.
  • RESOURCE_TYPE — the resource classification. Given the view's internal filter, rows are constrained to individual resources (RS_INDIVIDUAL) on the role side.
  • NAME — the display name of the resource user.
  • DESCRIPTION — descriptive text associated with the resource record.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the resource record is active. These support date-sensitive filtering in reports and lookups.
  • STATUS — the status of the underlying role assignment (from OKX_RESOURCE_ROLES_V).
  • DELETE_FLAG — indicates whether the role assignment has been logically deleted; rows with this flag set should generally be excluded from active-user queries.

Common Use Cases and Queries

Typical scenarios include populating resource-user LOVs, extracting the current roster of individual contract resources for downstream systems, and validating that a given resource ID corresponds to an active, non-deleted individual resource.

Example — retrieve active, non-deleted resource users:

SELECT id, resource_number, resource_type, name, start_date_active, end_date_active
FROM okc_resource_users_v
WHERE (delete_flag IS NULL OR delete_flag = 'N')
  AND (end_date_active IS NULL OR end_date_active >= SYSDATE)
ORDER BY name;

Example — look up a single resource user by ID:

SELECT id, resource_number, name, status
FROM okc_resource_users_v
WHERE id = :resource_id;

Because the view is a de-duplicated projection over the OKX resource and role views, it should be treated as read-only. Date and status filters should always be applied where current, valid resource users are required.