Search Results oke_k_all_access_v




Overview
Explore in AI Chat

Overview

OKE_K_ALL_ACCESS_V is a security-enabled reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts module. It is documented in ETRM as the "Contract Security Assignment display view," and it exposes the association between a contract (identified by its OKE header) and the people and roles granted access to that contract through the contract security model. In EBS 12.1.1 and 12.2.2 the object is registered with a status of VALID, indicating that it compiles without error against the delivered schema and is safe for dependency-based reporting.

Because contract security in OKE is enforced through assignment levels and role-based access, the view provides a flat, denormalized projection of that configuration. Reporting tools, custom concurrent programs, and integration extracts can query it directly instead of reconstructing the security assignment logic from the base tables. The reference to OKE_K_SECURITY_PKG among its dependencies confirms that the view participates in the same contract security framework that governs runtime access within the Project Contracts application.

Underlying Base Objects

The documented view text selects from four sources. OKE_K_ALL_ACCESS_BASIC_V is the immediate base view supplying the assignment rows, including the assignment level, header identifier, person, role, and the active date range. OKE_K_HEADERS is the master contract header entity, referenced by its K_HEADER_ID synonym and supplying the displayed contract number (K_NUMBER_DISP) plus the effective start and end dates used to bound the assignment record.

Two further objects resolve descriptive attributes. PA_PROJECT_ROLE_TYPES supplies the role meaning text associated with each ROLE_ID, and PER_ALL_PEOPLE_F supplies the person's full name for each PERSON_ID. The view's dependency list also names OKE_K_SECURITY_PKG and PA_ROLE_JOB_BG_UTILS, which support the security and role-resolution logic used by the basic access view beneath it. In implementation terms, the join enforces that the assignment row is current with respect to the contract header: the truncated creation date of the assignment must fall between the truncated effective start and end dates of the header.

Key Columns

  • ASSIGNMENT_LEVEL — Indicates the scope at which contract access is granted, distinguishing how broadly the assignment applies.
  • K_HEADER_ID — The unique internal identifier of the OKE contract header to which the access assignment belongs; the primary join key to OKE_K_HEADERS.
  • K_NUMBER (K_NUMBER_DISP) — The displayed contract number, the business-facing identifier for the contract.
  • PERSON_ID — The identifier of the person granted access, joined to PER_ALL_PEOPLE_F.
  • PERSON_NAME (FULL_NAME) — The full name of the assigned person.
  • ROLE_ID — The project role identifier assigned to the person, joined to PA_PROJECT_ROLE_TYPES.
  • ROLE_NAME (MEANING) — The descriptive name of the role, such as the responsibility level implied by the assignment.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date range during which the security assignment is active.

Common Use Cases and Queries

Typical usage centers on security auditing, access reporting, and data extraction for downstream systems. A common pattern is listing all access assignments for a given contract, filtered by contract number:

  • SELECT k_number, person_name, role_name, start_date_active, end_date_active FROM apps.oke_k_all_access_v WHERE k_number = :contract_number ORDER BY person_name;
  • SELECT assignment_level, role_name, COUNT(*) FROM apps.oke_k_all_access_v GROUP BY assignment_level, role_name;
  • SELECT p.k_number, a.person_name, a.role_name FROM apps.oke_k_all_access_v a, apps.oke_k_headers p WHERE a.k_header_id = p.k_header_id AND a.end_date_active IS NULL;

These queries support audits of who can access which contracts, verification of role coverage across a contract portfolio, and periodic extracts into enterprise reporting or identity-management systems. Because the view already resolves names and roles, it reduces the need for custom joins and helps ensure consistent interpretation of OKE contract security data.