Search Results okc_contacts

Overview

The OKC_CONTACTS table is a core data object within the Oracle E-Business Suite (EBS) Contracts Core module (OKC). It serves as the central repository for storing detailed information about individuals designated as contact points or otherwise formally named within a contract. This table is fundamental to managing the human relationships associated with contractual agreements, enabling functionalities such as communication, role assignment, and accountability tracking. Its existence is critical for linking specific persons to the broader contractual parties and roles defined elsewhere in the application, thereby providing a complete picture of all entities involved in a contract.

Key Information Stored

The table stores attributes that uniquely identify and describe a contact within the context of a contract. While the full column list is not detailed in the provided metadata, the structure indicates the presence of key identifiers and foreign key relationships. The primary key column is ID, which uniquely identifies each contact record. A critical foreign key is CPL_ID, which links the contact to a specific contract party role record in the OKC_K_PARTY_ROLES_B table, establishing which party the contact belongs to. Another significant column is JTOT_OBJECT1_CODE, which references JTF_OBJECTS_B and is typically used to define the contact's role or object type within the JTF (Trading Community Architecture) framework. Additional columns likely store standard contact details such as name, job title, phone numbers, email address, and address information.

Common Use Cases and Queries

This table is primarily accessed to retrieve or report on all contacts associated with specific contracts or parties. Common business scenarios include generating contact lists for a contract, validating contact information during contract authoring, and supporting communication workflows. A typical query would join OKC_CONTACTS to OKC_K_PARTY_ROLES_B and the main contract header table (e.g., OKC_K_HEADERS_B) to list contacts for a given contract number. For example:

• Identifying all contacts for a contract: SELECT c.* FROM okc_contacts c, okc_k_party_roles_b pr WHERE c.cpl_id = pr.id AND pr.dnz_chr_id = <contract_id>;
• Finding contacts based on a specific role type by joining with JTF_OBJECTS_B.
• Reporting on sales credits by joining with OKS_K_SALES_CREDITS where the contact is credited for sales.

Related Objects

The OKC_CONTACTS table is integral to the Contracts Core data model, with several key dependencies. Its primary relationship is with OKC_K_PARTY_ROLES_B, which defines the party (e.g., customer, supplier) the contact is associated with. It references JTF_OBJECTS_B to categorize the contact's role. Furthermore, it is referenced by the OKS_K_SALES_CREDITS table in the Service Contracts module, indicating that contacts can be assigned sales credit for contracts. This table is also likely accessed by standard Oracle Contracts APIs and views that manage contact information for transactional and reporting purposes.