Search Results okc_contact_sources




Overview
Explore in AI Chat

Overview

OKC_CONTACT_SOURCES is a configuration and reference table in the Oracle Contracts Core (OKC) module. It defines the valid data sources that may be used when assigning a Contract Contact to a specific role. In other words, for a given contract role (such as a buyer contact or a seller contact), this table enumerates the recognized origins from which the contact information can be derived, including the associated object type and the transactional direction (buy or sell). The table therefore acts as a control mechanism that constrains which contact definitions are permissible within the contracts data model.

The object resides in the OKC schema and is marked VALID in the ETRM 12.2.2 repository. The documented physical schema contains 16 columns. Based on the foreign key structure, the heuristic Data Vault classification is satellite-leaning. This suggests that, from a dimensional modeling perspective, the table is best treated as a satellite attached to a parent hub or link defined by the role and object code combinations, rather than as an independent hub of business keys. The presence of START_DATE, END_DATE, and OBJECT_VERSION_NUMBER columns reinforces this satellite interpretation, since these attributes support change tracking and effective-dating of the source definitions.

Key Information Stored

The primary key, OKC_CONTACT_SOURCES_PK, is a composite surrogate formed from CRO_CODE, RLE_CODE, BUY_OR_SELL, and START_DATE. A second unique index, OKC_CONTACT_SOURCES_U1, extends these four columns with ZD_EDITION_NAME, confirming the business-key candidate that enforces uniqueness across the edition dimension.

  • CRO_CODE — Identifies the contact source code record; part of the composite primary key.
  • RLE_CODE — The contract role to which the source definition applies; part of the primary key.
  • BUY_OR_SELL — Indicates the transactional direction (buy-side or sell-side); part of the primary key.
  • START_DATE — Effective start date of the definition; part of the primary key and the date-tracking mechanism.
  • END_DATE — Effective end date, supporting historical and current-row queries.
  • JTOT_OBJECT_CODE — Foreign key to JTF_OBJECTS_B, referencing the JTF object that the contact source derives from.
  • CONSTRAINED_YN — Flag indicating whether the source is constrained or freely selectable.
  • OBJECT_VERSION_NUMBER — Optimistic locking and change-version control.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant/security segmentation.
  • ACCESS_LEVEL — Access control level for the row.
  • ZD_EDITION_NAME — Edition identifier used by the editioning framework; part of the unique index U1.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard who-column auditing.

Common Use Cases and Queries

Typical usage centers on validating or listing the sources available for contact assignment in contract roles. A common query retrieves the current effective sources for a given role and direction:

  • SELECT cro_code, rle_code, buy_or_sell, jtot_object_code, constrained_yn FROM okc_contact_sources WHERE rle_code = :role AND buy_or_sell = :direction AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);
  • Joining to JTF_OBJECTS_B to resolve the underlying object description for reporting: SELECT s.cro_code, o.object_name FROM okc_contact_sources s, jtf_objects_b o WHERE s.jtot_object_code = o.object_code;
  • Historical reporting using the date range to reconstruct which sources were valid at a past point in time.
  • Security-filtered extraction using SECURITY_GROUP_ID and ACCESS_LEVEL for role-based reporting.

Reporting use cases include contact-source setup audits, migration validation between environments, and reconciliation of editioned setups across upgrades.

Related Objects

  • JTF_OBJECTS_B — Referenced via OKC_CONTACT_SOURCES.JTOT_OBJECT_CODE; provides the object definition behind each source.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs row-level security segmentation.
  • OKC_CONTACTS — The contract contact instances whose validity depends on the source definitions configured here.
  • OKC_ROLES / role definition tables — Supply the RLE_CODE values consumed by this table.
  • OKC_CONTACT_SOURCES_PK / OKC_CONTACT_SOURCES_U1 — The unique constraints that enforce integrity and edition uniqueness.

Together these objects form the reference and security framework supporting contract contact assignment in Oracle E-Business Suite 12.1.1 and 12.2.2.