Search Results okc_rep_contact_roles_b




Overview
Explore in AI Chat

Overview

OKC_REP_CONTACT_ROLES_B is a foundational setup table within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The table stores the user-defined contact roles that govern how parties and contacts are classified against a contract. A contact role is the semantic label — such as "Buyer," "Seller," "Legal Reviewer," or "Notification Recipient" — that determines the business meaning of an association between a contract and the party or person fulfilling that function. As a repository of user-extensible reference values, the table is populated during implementation and extended over time by contract administrators, and it is referenced transactionally by the contracts and party-contact tables.

From a Data Vault modeling perspective, the mined foreign-key structure suggests that OKC_REP_CONTACT_ROLES_B is hub-leaning. In other words, it behaves like a business-key hub of contact role identities, with the descriptive attributes carried alongside. This classification is heuristic and offered as a design suggestion rather than a documented Oracle architectural statement.

Key Information Stored

The physical schema exposes 10 columns in the OKC schema. The most important of these are:

  • CONTACT_ROLE_ID — the surrogate primary key (OKC_REP_CONTACT_ROLES_B_PK). It uniquely identifies each contact role and is the value propagated to all dependent tables.
  • START_DATE and END_DATE — define the effective-dating window during which the contact role is considered active. Roles outside this range should generally be suppressed from selection lists and validation logic.
  • OBJECT_VERSION_NUMBER — supports optimistic locking and concurrency control in the Oracle Application Framework (OAF) and PL/SQL APIs, incremented on each update.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle "Who" audit columns used for traceability and audit reporting.
  • ZD_EDITION_NAME — the editioning column that enables Oracle EBS 12.2.x Online Patching (Edition-Based Redefinition). It supports multiple logical editions of the same row across patching cycles.

The unique index OKC_REP_CONTACT_ROLES_B_U1 spans (CONTACT_ROLE_ID, ZD_EDITION_NAME) and is the business-key candidate. Because CONTACT_ROLE_ID already forms the primary key, the composite uniqueness over the edition name confirms that the surrogate identifier is stable across editions, while edition-scoped duplicates are permitted internally.

Common Use Cases and Queries

Contact roles are consumed in two principal flows: contract party-contact assignment and contract notification configuration. A typical reporting query lists all roles with their effective dates, excluding edition-internal rows:

SELECT contact_role_id, start_date, end_date
FROM okc.okc_rep_contact_roles_b
WHERE zd_edition_name = 'SET1'
AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

For a contract-centric view, join the roles to the contracts table via the notification role column:

SELECT c.contract_number, r.contact_role_id
FROM okc.okc_rep_contracts_all c, okc.okc_rep_contact_roles_b r
WHERE c.notify_contact_role_id = r.contact_role_id;

To enumerate parties associated with a role, join to OKC_REP_PARTY_CONTACTS on CONTACT_ROLE_ID. Validation routines should confirm that a proposed role is active for the current date, and integrations loading contact data must resolve the role by ID rather than by name, since names are not exposed in the documented physical columns.

Related Objects

  • OKC_REP_PARTY_CONTACTS — references OKC_REP_CONTACT_ROLES_B via CONTACT_ROLE_ID; stores the actual party-contact associations tagged with a role.
  • OKC_REP_CONTRACTS_ALL — references OKC_REP_CONTACT_ROLES_B via NOTIFY_CONTACT_ROLE_ID; identifies the role used for contract notifications.
  • OKC_REP_CONTACT_ROLES_B_PK — primary key constraint on CONTACT_ROLE_ID.
  • OKC_REP_CONTACT_ROLES_B_U1 — unique index on (CONTACT_ROLE_ID, ZD_EDITION_NAME), the business-key candidate supporting EBS 12.2.x editioning.

Together these objects form the reference backbone for contact-role semantics across the Contracts Core module.