Search Results assignment_key

Overview

The Oracle E-Business Suite view APPS.OKE_K_ALL_ACCESS_BASIC_V is a contract security assignment view belonging to the OKE – Project Contracts product family. Its documented description in the ETRM repository is "Contract Security Assignment basic view," and it carries a status of VALID within the APPS schema. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the foundational data source used by the Project Contracts security framework to resolve which resources — employees, roles, and sites — hold access to a given contract header (K_HEADER_ID). Rather than storing data itself, the view derives an access picture by combining project party assignments with contract header creation metadata.

The view is named "basic" because it exposes the minimal, unexpanded access assignment set. Higher-level access views and the OKE security engine build upon this basic layer to apply date-range filtering and assignment-type logic. It is a read-only object and is not intended for direct DML.

Underlying Base Objects

The documented base objects referenced by the view are:

• OKE_K_HEADERS (SYNONYM) — the Project Contracts header table, supplying contract identity via K_HEADER_ID.
• PA_PROJECT_PARTIES (SYNONYM) — project party assignments filtered to RESOURCE_TYPE_ID = 101 and OBJECT_TYPE LIKE 'OKE%', providing the primary assignment records.
• FND_USER (SYNONYM) — used to resolve the creator (CREATED_BY) of each contract header to an employee, generating an implicit "CREATED_BY" assignment.
• OKE_K_SECURITY_PKG (PACKAGE) — supplies GET_ASSIGNMENT_DATE, which drives the effective-date filtering of assignments.

Structurally, the view text joins OKE_K_HEADERS against a UNION ALL of project party rows and creator-derived rows, then against an aggregation subquery that computes an ASSIGNMENT_KEY. The key is constructed using a DECODE priority scheme: contract header assignments ('OKE_K_HEADERS') map to priority 1, program assignments ('OKE_PROGRAMS') map to 2 or 3 (with object ID 0 mapping to 3), and all others to 4. Sites are inferred from an assignment key prefix of '3'. Date filtering ensures only assignments active on the assignment date are retained.

Key Columns

• ASSIGNMENT_TYPE / OBJECT_TYPE — the decoded assignment category; the first character of the assignment key prefix yields 'SITE' where prefixed by 3, otherwise the underlying party object type.
• K_HEADER_ID — the Project Contracts header identifier to which access is granted.
• RESOURCE_SOURCE_ID — the resource (typically an employee) deriving the assignment.
• PROJECT_ROLE_ID — the project role associated with the party assignment, where applicable.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range of the assignment; NULL end date denotes an open-ended assignment.
• CREATION_DATE — creation timestamp of the header or assignment record.

Common Use Cases and Queries

This view is used to audit and report contract access, to troubleshoot why a user can or cannot view a contract, and to feed custom security or reporting extensions. A typical query returns all access assignments for a contract:

SELECT assignment_type, k_header_id, resource_source_id, project_role_id, start_date_active, end_date_active FROM apps.oke_k_all_access_basic_v WHERE k_header_id = :p_header_id;

Because the view embeds OKE_K_SECURITY_PKG.GET_ASSIGNMENT_DATE, results are evaluated as of the current assignment date. Users requiring historical point-in-time reporting should join back to PA_PROJECT_PARTIES directly rather than relying solely on this view.