Results for “oke_k_communications”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_K_COMMUNICATIONS is a transactional table in the OKE (Project Contracts) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores communication definitions related to contract deliverables and project funding within the Project Contracts (Oracle Contract Terms and Deliverables) framework. Each row represents a communications record tied to a specific contract header, capturing contacts, correspondence details, workflow-driven actions, and delivery context.

Based on the foreign key relationships mined from the ETRM metadata, this table exhibits the characteristics of a link (association) entity in a Data Vault model. It resolves many-to-many relationships between the contract header, lines, deliverables, funding sources, change requests, project tasks, and Oracle Workflow items. The primary key OKE_K_COMMUNICATIONS_PK (K_HEADER_ID, COMMUNICATION_NUM) uniquely identifies each communication, while the unique index OKE_K_COMMUNICATIONS_U1 confirms the same business key of header and communication number.

Key Information Stored

The table contains 47 columns. The most significant are:

• K_HEADER_ID — Foreign key to OKE_K_HEADERS; the contract header the communication belongs to.
• COMMUNICATION_NUM — Sequential number identifying the communication within the header; part of the primary key.
• COMMUNICATION_DATE — The effective date of the communication.
• REASON_CODE, TYPE, ACTION_CODE, PRIORITY_CODE — Classification and routing attributes for the communication.
• K_PARTY_ID, PARTY_LOCATION, PARTY_ROLE, PARTY_CONTACT — Party (customer/supplier) identification and contact information.
• OWNER — Assigned owner of the communication record.
• WF_ITEM_TYPE, WF_PROCESS, WF_ITEM_KEY — Oracle Workflow item context for process-driven communications.
• K_LINE_ID, DELIVERABLE_ID, FUNDING_SOURCE_ID, CHG_REQUEST_ID — Foreign keys linking the communication to contract lines, deliverables, funding sources, and change requests.
• PROJECT_ID, TASK_ID — Foreign keys to PA_PROJECTS_ALL and PA_TASKS for project and task association.
• DELETE_IND — Soft-delete flag.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns for user-defined data.
• TEXT — Free-form communication body or notes.

The surrogate primary key is the composite (K_HEADER_ID, COMMUNICATION_NUM), which also serves as the business-key candidate via the unique index.

Common Use Cases and Queries

Reporting on project correspondence, tracking deliverable-related communications, and auditing funding or change-request discussions are the principal use cases. A typical query retrieves all communications for a contract header:

SELECT communication_num, communication_date, type, action_code
FROM oke_k_communications
WHERE k_header_id = :header_id AND NVL(delete_ind,'N') = 'N';

Joining to project and task tables supports project-level reporting:

SELECT c.communication_num, p.name project_name, t.task_number
FROM oke_k_communications c, pa_projects_all p, pa_tasks t
WHERE c.project_id = p.project_id
AND c.task_id = t.task_id;

Workflow integration queries use WF_ITEM_TYPE and WF_ITEM_KEY to trace communications back to workflow processes for status monitoring and notification auditing.

Related Objects

• OKE_K_HEADERS — Parent contract header; join on K_HEADER_ID.
• OKE_K_LINES — Contract lines; join on K_LINE_ID.
• OKE_K_DELIVERABLES_B — Deliverables; join on DELIVERABLE_ID.
• OKE_K_FUNDING_SOURCES — Funding sources; join on FUNDING_SOURCE_ID.
• OKE_CHG_REQUESTS — Change requests; join on CHG_REQUEST_ID.
• PA_PROJECTS_ALL — Projects; join on PROJECT_ID.
• PA_TASKS — Tasks; join on TASK_ID.
• WF_ITEM_TYPES / WF_ITEMS — Workflow integration; join on WF_ITEM_TYPE and WF_ITEM_KEY.

These relationships establish OKE_K_COMMUNICATIONS as a central convergence point for contract, project, funding, and workflow communication data.