Search Results party_role_id




Overview
Explore in AI Chat

Overview

APPS.OKI_K_CONTACTS_V is a reporting view in the Oracle E-Business Suite Contracts (OKC/OKI) schema that consolidates contact assignments attached to contracts and their associated sales/OKI headers. It presents party-level contacts linked to a contract header along with the contact role, the role meaning, and the resolved resource or party-contact name. The view is particularly relevant because its definition explicitly joins to OKX_RESOURCES_V (aliased as OKX) through the predicate ctt.jtot_object1_code = 'OKX_RESOURCE', which explains why a search for "okx_resource" surfaces this object. In Oracle EBS 12.1.1 and 12.2.2 the view is used primarily for operational reporting on contract contacts, for listing who is associated with a given contract, and as a data source for custom inquiries and integrations that need contract-to-resource contact information without navigating the underlying OKC_CONTACTS model directly.

Underlying Base Objects

The view text reveals the following base and reference objects, although the ETRM documented metadata lists no referenced base objects for this view:

  • OKI_SALES_K_HDRS (alias SHD) — the contract/OKI header source providing contract_id, contract_number, contract_number_modifier, and complete_contract_number.
  • OKC_CONTACTS (alias CTT) — the core contact assignment table holding party_contact_id, cpl_id (party_role_id), cro_code (contact_role_code), object1_id1 (the contact or resource id), jtot_object1_code, dnz_chr_id, creation/last_update dates, and the DFF attribute columns.
  • FND_LOOKUPS (alias CRO) — resolves the contact role code (lookup_type = 'OKC_CONTACT_ROLE') to its meaning.
  • OKX_RESOURCES_V (alias OKX) — supplies the resource name for records whose jtot_object1_code is 'OKX_RESOURCE'.
  • OKX_PARTY_CONTACTS_V (alias OKX, second UNION ALL branch) — supplies the name for records whose jtot_object1_code is 'OKX_PCONTACT'.

The definition is a UNION ALL of at least two branches: one resolving resources and one resolving party contacts, both filtered by okc_util.get_k_access_level returning 'R' or 'U' to enforce contract access security.

Key Columns

  • party_contact_id — OKC_CONTACTS.id, the unique contact assignment identifier.
  • contract_id / contract_number / contract_number_modifier / complete_contract_number — contract header identification from OKI_SALES_K_HDRS.
  • party_role_id — the cpl_id linking the contact to a party role.
  • contact_role_code / contact_role_meaning — the OKC_CONTACT_ROLE lookup code and its translated meaning.
  • contact_id — numeric object1_id1 cast from the contact/resource reference.
  • contact_name — the resolved name from OKX_RESOURCES_V (or OKX_PARTY_CONTACTS_V).
  • creation_date / last_update_date — audit columns for the contact assignment.
  • attribute_category and attribute1–attribute15 — the descriptive flexfield columns of OKC_CONTACTS.

Common Use Cases and Queries

The view supports contract contact reporting and resource-based lookups. Typical usage includes:

  • Listing all resource contacts on a contract, filtered by contract number.
  • Reporting contact roles across a contract portfolio.
  • Joining contact names back to resource or HR data for integration extracts.
SELECT contract_number,
       complete_contract_number,
       contact_role_meaning,
       contact_id,
       contact_name
FROM   apps.oki_k_contacts_v
WHERE  contract_number = :p_contract_number
ORDER  BY contact_role_meaning, contact_name;

Because access is governed internally by okc_util.get_k_access_level, users only see contracts for which they hold Read or Update access. Any custom query inherits this security, making the view suitable as a secured reporting source in 12.1.1 and 12.2.2 environments.