Search Results oke_k_roles_v




Overview
Explore in AI Chat

Overview

OKE_K_ROLES_V is an APPS-owned, VALID database view shipped with the Oracle E-Business Suite Project Contracts (OKE) module. Its documented description is "Security Role View." The object is delivered in support of Oracle Project Contracts role-based security and is present across EBS 12.1.1 and 12.2.2. The view exposes a filtered list of project role types that are authorized to act as contract members, providing a denormalized, presentation-ready row set for forms, reports, and integration logic that need to resolve which roles may be assigned as contract personnel.

Because it is a view rather than a table, OKE_K_ROLES_V is read-only and inherits the security posture of the underlying APPS synonyms and views. It is most directly relevant to implementers and developers searching on the term pa_role_controls, since that base table drives its filter predicate. The "K" naming convention is consistent with other OKE/PA security and lookup views used by Oracle Project Contracts.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, OKE_K_ROLES_V is defined over the following referenced base objects:

The view text joins PA_PROJECT_ROLE_TYPES (aliased PRT) to PA_ROLE_CONTROLS (aliased RC) on PROJECT_ROLE_ID, retaining only rows where ROLE_CONTROL_CODE equals 'ALLOW_AS_CONTRACT_MEMBER'. In effect, OKE_K_ROLES_V answers the question: "Which project roles are permitted to serve as contract members?" This makes PA_ROLE_CONTROLS the authoritative control table and PA_PROJECT_ROLE_TYPES the descriptive source.

Key Columns

The documented columns map from the select list as follows:

  • ROLE_ID — projected from PROJECT_ROLE_ID; the unique identifier of the project role type.
  • CODE — projected from PROJECT_ROLE_TYPE; the internal role type code.
  • NAME — projected from MEANING; the user-facing role name.
  • DESCRIPTION — projected from DESCRIPTION; free-text description of the role.
  • START_DATE_ACTIVE — the date on which the role becomes active.
  • END_DATE_ACTIVE — the date on which the role ceases to be active.

Callers should apply date-range predicates against START_DATE_ACTIVE and END_DATE_ACTIVE to restrict results to currently effective roles; the view itself exposes these columns but does not filter on them.

Common Use Cases and Queries

Typical uses include populating a role LOV on Project Contracts contract-member forms, validating contract team assignments in integrations, and driving security reports. Implementers frequently need to confirm that a role has been enabled in PA_ROLE_CONTROLS before it appears as a contract member option.

Return only active roles:

  • SELECT role_id, code, name, start_date_active, end_date_active FROM apps.oke_k_roles_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Resolve a role by code:

  • SELECT role_id, name, description FROM apps.oke_k_roles_v WHERE code = :role_code;

To troubleshoot a missing role, query the control table directly: SELECT * FROM apps.pa_role_controls WHERE project_role_id = :role_id AND role_control_code = 'ALLOW_AS_CONTRACT_MEMBER'; Rows absent here will never surface through OKE_K_ROLES_V, which is the most common cause of "role not available" issues in Project Contracts security setup.