Search Results assignment_key

Overview

APPS.OKE_K_ALL_ACCESS_BASIC_V is a security-enabling view within the Oracle E-Business Suite (EBS) Oracle Knowledge and Contracts (OKE) module, which underpins the Project Contracts and Oracle ETRM/OKE knowledge management functionality. The view exposes the set of assignments to which a given user or role currently has access, resolving the assignment security model defined through PA_PROJECT_PARTIES and the OKE_K_SECURITY_PKG package. It is a "basic" access view, meaning it filters assignments by the effective assignment date returned by OKE_K_SECURITY_PKG.GET_ASSIGNMENT_DATE, ensuring that only currently-active assignments are returned. In release 12.1.1 and 12.2.2, this view is typically used as a building block for higher-level reporting views and for the OKE security framework that governs visibility of K_HEADERS and programs. Because access logic is centralized here, downstream reports and integrations can join to this view rather than re-implementing the assignment security rules, thereby guaranteeing consistent row-level filtering across the application.

Underlying Base Objects

The view is defined over four documented base objects: OKE_K_HEADERS, PA_PROJECT_PARTIES, FND_USER, and the OKE_K_SECURITY_PKG package. OKE_K_HEADERS holds the knowledge/contract header records that anchor each assignment. PA_PROJECT_PARTIES supplies the project-party rows restricted to RESOURCE_TYPE_ID = 101 and OBJECT_TYPE LIKE 'OKE%', forming the core assignment set. FND_USER is joined on CREATED_BY to attribute a synthetic "CREATED_BY" assignment to the originating user, allowing the creator to retain access. OKE_K_SECURITY_PKG is invoked through GET_ASSIGNMENT_DATE and related security routines to evaluate the effective date against START_DATE_ACTIVE and END_DATE_ACTIVE, which is how the view decides whether each assignment is currently valid. The view text combines these sources with UNION ALL branches and a MIN(...) aggregation over a composite ASSIGNMENT_KEY, producing one effective assignment key per K_HEADER_ID.

Key Columns

• ASSIGNMENT_KEY — The composite key central to the view's logic. It is derived as MIN(priority || ':' || PROJECT_PARTY_ID), where priority decodes OBJECT_TYPE (OKE_K_HEADERS = 1, OKE_PROGRAMS = 2 or 3 when OBJECT_ID = 0, CREATED_BY = 4). This key uniquely identifies the effective assignment for each header.
• K_HEADER_ID — The knowledge/contract header identifier, linking the assignment back to OKE_K_HEADERS.
• RESOURCE_SOURCE_ID — The resource (typically the employee/user) associated with the assignment.
• PROJECT_ROLE_ID — The project role assigned to the party, used for role-based access determination.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The validity window of the assignment; the view includes only rows where the security date falls within this range (or END_DATE_ACTIVE is null).
• CREATION_DATE — The creation timestamp of the assignment, useful for auditing.
• Object type / SITE flag — The leading DECODE maps assignments whose key begins with "3" to 'SITE', otherwise the project object type is returned, indicating the access level (site versus project).

Common Use Cases and Queries

The view is most frequently queried to determine which K_HEADERS a user can access, and to build security-aware reports for contracts and programs. A typical query joins it to OKE_K_HEADERS to list accessible headers:

• SELECT v.K_HEADER_ID, v.ASSIGNMENT_KEY, v.PROJECT_ROLE_ID FROM APPS.OKE_K_ALL_ACCESS_BASIC_V v WHERE v.RESOURCE_SOURCE_ID = :user_id;
• Reporting on active assignments by role: SELECT PROJECT_ROLE_ID, COUNT(*) FROM APPS.OKE_K_ALL_ACCESS_BASIC_V GROUP BY PROJECT_ROLE_ID;
• Auditing assignment validity: SELECT K_HEADER_ID, START_DATE_ACTIVE, END_DATE_ACTIVE FROM APPS.OKE_K_ALL_ACCESS_BASIC_V WHERE TRUNC(SYSDATE) BETWEEN TRUNC(START_DATE_ACTIVE) AND NVL(TRUNC(END_DATE_ACTIVE), TRUNC(SYSDATE));

Because OKE_K_SECURITY_PKG evaluates the assignment date at runtime, results reflect the current session's security context. Integrations and custom reports should therefore always filter through this view rather than reading PA_PROJECT_PARTIES directly, to preserve the same access semantics enforced by the OKE module.