Search Results okc_rep

Overview

OKC.OKC_REP_CONTACT_ROLES_B is a seed-data table within the Oracle Contracts (OKC) schema that stores user-defined Contact Roles. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table functions as the master list of role definitions—such as "Buyer," "Seller," "Legal Contact," or "Notify Contact"—that can be assigned to parties associated with contracts and other OKC entities. Because it resides in the APPS_TS_SEED tablespace, it is treated as reference/seed data intended to be relatively stable across the application lifecycle, with effective dating (START_DATE/END_DATE) providing a form of temporal versioning.

From a Data Vault modeling perspective, the mined FK structure suggests this object is hub-leaning: CONTACT_ROLE_ID acts as a durable business key that is referenced by multiple downstream entities, giving it the characteristics of a hub entity for a "Contact Role" concept. This classification is a heuristic modeling suggestion rather than a physically designated Data Vault construct.

Key Information Stored

The table is defined with ten documented columns, of which the most significant are:

• CONTACT_ROLE_ID – The surrogate primary key (OKC_REP_CONTACT_ROLES_B_PK), a NUMBER sourced from the sequence OKC_REP_CONTACT_ROLES_S. This is also the documented unique business-key candidate via index OKC_REP_CONTACT_ROLES_B_U1 (which additionally includes ZD_EDITION_NAME in 12.2.2).
• START_DATE / END_DATE – Effective and expiration dates of the contact role, enabling date-ranged validity of each role definition.
• OBJECT_VERSION_NUMBER – Set to 1 on insert and incremented on each update; used by OKC APIs for optimistic concurrency control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard "Who" audit columns tracking record creation and modification.
• ZD_EDITION_NAME – Present in 12.2.2 for edition-based redefinition support, allowing online patching of the OKC schema without invalidating existing sessions.

Common Use Cases and Queries

The primary use case is resolving a CONTACT_ROLE_ID to its meaning when reporting on contracts and party contacts. A typical lookup:

• List active roles: query rows where SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE).
• Join to assignments: link OKC_REP_PARTY_CONTACTS to enrich a party–contract relationship with a human-readable role label.
• Contract notifications: join to OKC_REP_CONTRACTS_ALL on NOTIFY_CONTACT_ROLE_ID to identify which role receives notifications.
• Seed/validation reporting: extract CONTACT_ROLE_ID, START_DATE, and END_DATE for setup reviews across instances.

The provided query text (SELECT from the ten columns) can be filtered and joined directly, though in 12.2.2 users should include ZD_EDITION_NAME to avoid cross-edition ambiguity.

Related Objects

Two documented foreign keys reference this table:

• OKC_REP_PARTY_CONTACTS.CONTACT_ROLE_ID → OKC.OKC_REP_CONTACT_ROLES_B – Associates a specific person/party contact with a role for a contract.
• OKC_REP_CONTRACTS_ALL.NOTIFY_CONTACT_ROLE_ID → OKC.OKC_REP_CONTACT_ROLES_B – Identifies the default notification role for a contract.
• OKC_REP_CONTACT_ROLES_B sequence (OKC_REP_CONTACT_ROLES_S) – Source for new primary key values.
• APPS.OKC_REP_CONTACT_ROLES_B – The synonym/APPS-layer reference used for querying.

These relationships establish the table as a foundational reference for OKC contact and notification logic across EBS 12.1.1 and 12.2.2.