Search Results okc_contacts_h




Overview

OKC_CONTACTS_H is the history (audit) table for OKC_CONTACTS, owned by the OKC schema within the Contracts Core module of Oracle E-Business Suite. It preserves prior and current versioned copies of contact records attached to contract documents, storing the same attribute set as the base table across 37 columns while adding a version discriminator that enables point-in-time reconstruction. In Oracle EBS 12.1.1 and 12.2.2, OKC_CONTACTS_H is populated whenever a contract contact row is inserted, updated, or versioned, and it is read primarily by contract history and audit inquiries rather than by transactional entry forms.

From a Data Vault modeling perspective (heuristic, derived from the documented key and foreign-key structure), OKC_CONTACTS_H is best characterized as a standalone satellite-like or history structure: it carries descriptive contact attributes keyed by a surrogate ID plus MAJOR_VERSION, with only a single residual reference to SECURITY_GROUP_ID. The metadata classifies it as "standalone," meaning it does not participate in the dense link network seen in the operational contact tables.

Key Information Stored

The table is keyed by the unique index OKC_CONTACTS_H_PK on (ID, MAJOR_VERSION), which is also mirrored by OKC_CONTACTS_H_U1. ID is the surrogate identifier inherited from the base OKC_CONTACTS record; MAJOR_VERSION identifies which historical iteration of that record the row represents. Both are required to retrieve a specific historical state.

The principal business content columns include:

Common Use Cases and Queries

The table supports audit and point-in-time reporting. A typical query retrieves the latest historical version of a contact:

  • SELECT * FROM okc.okc_contacts_h WHERE id = :p_id AND major_version = (SELECT MAX(major_version) FROM okc.okc_contacts_h WHERE id = :p_id);
  • Joining to FND_SECURITY_GROUPS on security_group_id to enforce data segregation in custom reports.
  • Comparing successive MAJOR_VERSION rows to identify changes in PRIMARY_YN, CRO_CODE, or RESOURCE_CLASS over a contract's life for change-audit extracts.
  • Feeding contract audit reports, DFF-dependent extracts, and historical reconciliation between OKC_CONTACTS and its archived states.

Related Objects

  • OKC_CONTACTS — the base transactional table whose rows are versioned into this history table.
  • FND_SECURITY_GROUPS — referenced via the SECURITY_GROUP_ID foreign key; required for security-group filtering.
  • OKC_CONTACTS_H_PK / OKC_CONTACTS_H_U1 — unique indexes enforcing (ID, MAJOR_VERSION) uniqueness.
  • OKC_CONTACT_ROLES / contact role reference objects — resolve CRO_CODE into meaningful role names.
  • OKC_K_HEADERS (contract headers) — linked through DNZ_CHR_ID for contract-level reporting.
  • OKC_CONTACT_POINTS — associated via CPL_ID for contact point detail.