Search Results okc_k_party_roles_b




Overview

The table OKC_K_PARTY_ROLES_B is a core data structure within the Oracle E-Business Suite Contracts Core module (OKC). It serves as the definitive repository for establishing and managing the complex relationships between contracts, the involved parties, and the specific roles those parties fulfill. This table is fundamental to the contract's legal and operational framework, enabling the system to track responsibilities, rights, and obligations for each entity associated with a contract, whether at the header or individual line level. Its design supports the multifaceted nature of business agreements where a single party can play multiple roles (e.g., buyer, supplier, bill-to) and a single role can be filled by multiple parties.

Key Information Stored

The table's primary function is to link three key identifiers. The CHR_ID column stores the contract header identifier, linking to OKC_K_HEADERS_B. The CLE_ID column optionally stores the contract line identifier, linking to OKC_K_LINES_B, allowing for party roles to be defined at a granular line level. The party and role information is encapsulated through foreign key relationships, notably to JTF_OBJECTS_B via JTOT_OBJECT1_CODE to define the role object. The table's primary key is the ID column. A critical self-referencing foreign key on CPL_ID indicates the table's support for hierarchical or successor relationships between party role records, which is essential for managing changes over the contract lifecycle.

Common Use Cases and Queries

A primary use case is generating a complete list of all parties and their roles for a given contract, which is vital for compliance, reporting, and operational execution. Another common scenario involves identifying all contracts where a specific organization or person fulfills a particular role, such as "Supplier" or "Approver." Sample queries include:

  • Retrieving all party roles for a contract header: SELECT * FROM okc_k_party_roles_b WHERE chr_id = <contract_id>;
  • Finding all contracts where a specific party (object) is the "BILL_TO" role: SELECT chr_id FROM okc_k_party_roles_b WHERE jtot_object1_code = 'BILL_TO' AND object1_id1 = <party_id>;
  • Reporting on the distribution of roles across contract lines: SELECT cle_id, jtot_object1_code, COUNT(*) FROM okc_k_party_roles_b WHERE cle_id IS NOT NULL GROUP BY cle_id, jtot_object1_code;

Related Objects

OKC_K_PARTY_ROLES_B is a central hub with extensive relationships. Its primary foreign keys link to the core contract tables OKC_K_HEADERS_B and OKC_K_LINES_B. It has a self-reference for hierarchical data. The table is referenced by numerous other entities that extend or utilize the party-role relationship, including OKC_CONTACTS for contact assignments, OKC_RG_PARTY_ROLES for security rules, and OKC_CHANGE_PARTY_ROLE for tracking changes. Furthermore, it integrates with other product families, as evidenced by references from Oracle Lease and Finance Management (OKL) tables like OKL_K_PARTY_ROLES and OKL_PARTY_PAYMENT_DTLS, demonstrating its critical role in the enterprise contract ecosystem.