Results for “communication_num”

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

Overview

OKE_K_COMMUNICATIONS_V is an APPS-owned database view that consolidates contract communication records for the Oracle E-Business Suite Project Contracts (OKE) module. Communications in OKE represent formal interactions tied to a contract, such as correspondence, transmittals, notices, and change-related dialog, each linked to a contract header, optional line, deliverable, project, task, or change request. The view denormalizes these records by joining the base communications table to lookup tables, people, project structures, and contract line/deliverable tables, resolving coded values into their translatable meanings.

Because the view flattens the relationships and presents descriptive attributes alongside identifiers, it is well suited for reporting, extract, and integration scenarios. Contract administrators and project accountants can query it without writing complex multi-table joins against FND lookup and HR tables. External systems that must consume or post contract communication data can also read from it, since it exposes both the raw code columns (for example PARTY_ROLE, REASON_CODE, TYPE) and their resolved MEANING values.

Underlying Base Objects

The view is defined over the following base objects:

• OKE_K_COMMUNICATIONS — the driving synonym holding the contract communication rows.
• OKE_COMM_ACTIONS_TL — provides the translated communication action name matched on ACTION_CODE and the user's session language.
• PER_ALL_PEOPLE_F — supplies the OWNER's full name; joined with the outer (+) operator so communications without an owner are retained.
• OKC_K_LINES_B — supplies line number information for the referenced contract line.
• OKE_K_DELIVERABLES_B — provides the deliverable number.
• OKE_CHG_REQUESTS — provides the change request number.
• PA_PROJECTS_ALL and PA_TASKS — provide project segment1 and task number respectively.
• FND_LOOKUP_VALUES_VL — referenced three times for reason, type, and priority meanings.

All lookup and descriptive joins are outer joins, so the view preserves the core communication record even when related attributes are missing.

Key Columns

• K_HEADER_ID, COMMUNICATION_NUM, COMMUNICATION_DATE — identify the communication and its contract header and date.
• K_PARTY_ID, PARTY_ROLE, PARTY_LOCATION, PARTY_CONTACT — capture the external party, its role, location, and contact associated with the communication; PARTY_ROLE is the column most often referenced by users searching on party role semantics.
• ACTION_CODE and COMM_ACTION_NAME — the communication action and its translated name.
• REASON_CODE, TYPE, PRIORITY_CODE — coded classifications resolved to MEANING via lookup joins.
• OWNER, FULL_NAME — the owning employee identifier and name.
• K_LINE_ID, LINE_NUMBER, DELIVERABLE_ID, DELIVERABLE_NUM — linkage to contract lines and deliverables.
• CHG_REQUEST_ID, CHG_REQUEST_NUM — linkage to change requests.
• PROJECT_ID, SEGMENT1, TASK_ID, TASK_NUMBER — project and task context.
• WF_ITEM_TYPE, WF_PROCESS, WF_ITEM_KEY — workflow linkage for communications driven through Oracle Workflow.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY, TEXT — descriptive flexfield and free-text content.
• DELETE_IND — soft-delete flag; active queries should filter this to 'N'.

Common Use Cases and Queries

Typical scenarios include auditing communications by contract, analyzing party roles involved in correspondence, and extracting communication history for a project or deliverable. A common query filters out deleted rows and lists communications with resolved descriptions:

• List all non-deleted communications for a contract header.
• Count communications grouped by PARTY_ROLE to assess party involvement.
• Retrieve communications linked to a specific project, task, or deliverable.
• Report communications by reason, type, or priority using the resolved MEANING columns.

Sample SQL:

• SELECT k_header_id, communication_num, party_role, comm_action_name, type, owner FROM oke_k_communications_v WHERE delete_ind = 'N' AND k_header_id = :header_id;
• SELECT party_role, COUNT(*) FROM oke_k_communications_v WHERE delete_ind = 'N' GROUP BY party_role;
• SELECT communication_num, communication_date, deliverable_num, task_number FROM oke_k_communications_v WHERE project_id = :project_id ORDER BY communication_date DESC;