Search Results okc_rg_party_roles




Overview

The OKC_RG_PARTY_ROLES table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module. It functions as a critical junction table that establishes the relationship between contract parties and the rule groups applied to a contract. Specifically, it defines which party from a contract (the subject) is acting upon which other party (the object) within the context of a specific business rule group. This mapping is essential for the enforcement of complex contract terms, validations, and business logic that are party-specific, enabling the Contracts application to dynamically apply rules based on the roles participants play in a contractual agreement.

Key Information Stored

The table's primary purpose is to link three key entities: a Rule Group, a Contract Party Role, and a defined Role Definition. While the full column list is not detailed in the provided metadata, its foreign key relationships explicitly identify the core data points. The table stores a unique identifier (ID) as its primary key. Each record holds a reference to a Rule Group (RGP_ID), a specific Contract Party Role instance (CPL_ID), and a Role Definition (RRD_ID). The RRD_ID determines whether the linked party is functioning as the subject or the object of the rule group. This structure allows a single rule group to be evaluated with different party pairings, providing flexibility in contract rule management.

Common Use Cases and Queries

This table is primarily accessed by the Contracts engine during the processing and validation of contract terms. A common operational use case is to determine all rule groups and their applicable parties for a specific contract, often for auditing or troubleshooting rule application. For reporting, one might analyze which party roles are most frequently associated with certain types of rule groups. A typical query would join OKC_RG_PARTY_ROLES to OKC_RULE_GROUPS_B, OKC_K_PARTY_ROLES_B, and OKC_RG_ROLE_DEFS to produce a human-readable report of rule assignments.

  • Sample Query Pattern: SELECT rgp.name, p_role.role_code, rrd.meaning FROM okc_rg_party_roles rgpr JOIN okc_rule_groups_b rgp ON rgpr.rgp_id = rgp.id JOIN okc_k_party_roles_b p_role ON rgpr.cpl_id = p_role.id JOIN okc_rg_role_defs rrd ON rgpr.rrd_id = rrd.id WHERE rgp.document_id = :contract_id;

Related Objects

The OKC_RG_PARTY_ROLES table is centrally connected to several other core Contracts tables, as defined by its foreign key constraints.

  • OKC_RULE_GROUPS_B (via RGP_ID): This is the master table for rule groups. The relationship ties the party role assignment to a specific set of business rules.
  • OKC_K_PARTY_ROLES_B (via CPL_ID): This table stores the specific instances of parties and their roles (e.g., "Buyer," "Supplier") within a contract. The link identifies the actual party involved.
  • OKC_RG_ROLE_DEFS (via RRD_ID): This reference table defines the possible roles a party can assume within a rule group context, such as "Subject" or "Object," which dictates the party's function in rule evaluation.