Search Results allow_as_contract_member

Overview

APPS.OKE_K_ROLES_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases that exposes the set of project roles which have been explicitly enabled to serve as contract members. The view belongs to the Contracts (OKE) and Projects (PA) functional areas and is owned by the APPS schema. Its purpose is to abstract the join between project role type definitions and their associated role control flags, returning only those roles whose control code equals ALLOW_AS_CONTRACT_MEMBER. In effect, the view presents a filtered master list of contract-eligible project roles, allowing downstream forms, concurrent programs, and external integrations to determine which roles may appear on a contract team without querying the role control configuration tables directly.

Because the view is a simple, non-aggregated projection, it carries no business logic beyond the join predicate. This makes it a convenient, low-risk source for LOV (List of Values) definitions, report parameters, and interface validation routines that must restrict selectable project roles to those permitted as contract members.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the following objects:

• PA_PROJECT_ROLE_TYPES (VIEW) — referenced with alias PRT; supplies the project role identifier, role type, meaning, description, and active date ranges.
• PA_ROLE_CONTROLS (SYNONYM) — referenced with alias RC; supplies the role control code that qualifies a role as contract-member eligible.
• PA_ROLE_JOB_BG_UTILS (PACKAGE) — documented as a referenced object, indicating a dependency relationship within the owning application module, typically invoked by background processing or utility logic rather than by the view's SQL itself.

The join is performed on RC.PROJECT_ROLE_ID = PRT.PROJECT_ROLE_ID, with the additional predicate RC.ROLE_CONTROL_CODE = 'ALLOW_AS_CONTRACT_MEMBER'. This restricts the result set to one row per role per matching control record, which is the definitive criterion for contract membership eligibility.

Key Columns

• PROJECT_ROLE_ID — The primary identifier of the project role type; the join key linking role definitions to their controls.
• PROJECT_ROLE_TYPE — The internal role type classification used to group and distinguish roles.
• MEANING — The user-facing display name of the role, suitable for LOVs and report labels.
• DESCRIPTION — A longer textual explanation of the role's purpose.
• START_DATE_ACTIVE — The date from which the role becomes active and eligible.
• END_DATE_ACTIVE — The date after which the role is no longer active; a null value indicates an open-ended, currently active role.

Note that the active date columns describe the role type itself and are not automatically filtered by the view; consumers requiring only currently active roles must apply their own SYSDATE predicates.

Common Use Cases and Queries

The view is most frequently used to populate role selection lists and to validate contract team assignments. The following query returns all active contract-member roles:

• SELECT project_role_id, project_role_type, meaning, description FROM apps.oke_k_roles_v WHERE (start_date_active IS NULL OR start_date_active <= SYSDATE) AND (end_date_active IS NULL OR end_date_active >= SYSDATE) ORDER BY meaning;

Supporting integration scenarios include:

• LOV definitions for contract team setup forms that must exclude non-eligible roles.
• Concurrent report parameters restricted to roles permitted on contracts.
• Inbound interface validation that rejects role codes not present in this view.
• Audit queries correlating contract members against the current eligible role population to detect configuration drift.

Because eligibility is governed entirely by the ALLOW_AS_CONTRACT_MEMBER control code in PA_ROLE_CONTROLS, any modification to role controls is immediately reflected in the view's output without additional setup.