Search Results okc_contacts_h_u1

Overview

The OKC.OKC_CONTACTS_H table is the history (audit) shadow of the base Oracle Contracts contact table OKC_CONTACTS. It resides in the OKC schema within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments and is flagged as VALID with FND design data OKC.OKC_CONTACTS_H. As documented, it is a mirror image of the base table OKC_CONTACTS; every column definition, including the 37 documented columns, mirrors the base object, and the base table should be consulted for detailed column semantics. The table is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10, confirming it is treated as transactional rather than reference data.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. The most natural interpretation is that OKC_CONTACTS_H functions as a versioned satellite: it holds the historical record of contact assignments tied to the contract header (DNZ_CHR_ID) and the contract party (CPL_ID), versioned by MAJOR_VERSION. The versioned satellite framing is a modeling suggestion rather than a physical declaration, because the FK analysis identifies only one outgoing reference, to FND_SECURITY_GROUPS, and no inbound dependencies.

Key Information Stored

The table carries a surrogate composite primary key, OKC_CONTACTS_H_PK, defined on (ID, MAJOR_VERSION). The unique index OKC_CONTACTS_H_U1 is also defined on (ID, MAJOR_VERSION), which enforces the same business key and is the index most directly associated with the search term okc_contacts_h_u1. This documents that ID alone is not unique across the table; uniqueness is achieved only when combined with the version number.

• ID — surrogate identifier shared with the base contact record; the first member of the composite key.
• MAJOR_VERSION — version discriminator; the second member of the primary key and unique index.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle AOL framework.
• DNZ_CHR_ID — contract header identifier; the highest-value business grouping key and the target of the nonunique index OKC_CONTACTS_H_N1.
• CPL_ID — the contract party line identifier to which the contact is attached.
• CRO_CODE — role code describing the contact's function on the contract.
• OBJECT1_ID1 / OBJECT1_ID2 / JTOT_OBJECT1_CODE — the denormalized JTOT subject-triple identifying the related entity.
• CONTACT_SEQUENCE — ordering position of the contact.
• PRIMARY_YN — flags the primary contact for a party.
• RESOURCE_CLASS — classification of the contact resource.
• SECURITY_GROUP_ID — the only documented foreign key, referencing FND_SECURITY_GROUPS.
• START_DATE / END_DATE — effective dating of the contact assignment.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF flexfield segment set.

Common Use Cases and Queries

Because the table is a history image, the most common access pattern is reconstructing the state of a contact as of a point in time, or comparing successive versions of the same contact. The nonunique index OKC_CONTACTS_H_N1 supports retrievals by contract header.

• Current version per contact: select from OKC_CONTACTS_H h where h.major_version = (select max(h2.major_version) from OKC_CONTACTS_H h2 where h2.id = h.id).
• All contacts for a contract: select * from OKC_CONTACTS_H where dnz_chr_id = :p_chr_id order by contact_sequence, major_version.
• Point-in-time view using effective dates: constrain on start_date and end_date, or on creation_date.
• Change tracking and audit: compare attribute1 through attribute15 and cro_code between consecutive major_version values.
• Security-restricted reporting joined to fnd_security_groups on security_group_id.
• Base-versus-history reconciliation: outer join OKC_CONTACTS to OKC_CONTACTS_H to detect rows missing history.

Related Objects

• OKC.OKC_CONTACTS — the base table of which OKC_CONTACTS_H is the mirror image; the primary source for column-level detail.
• OKC.OKC_CONTACTS_H_PK — primary key constraint on (ID, MAJOR_VERSION).
• OKC_CONTACTS_H_U1 — unique index on (ID, MAJOR_VERSION) in APPS_TS_TX_IDX.
• OKC_CONTACTS_H_N1 — nonunique index on DNZ_CHR_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
• OKC.OKC_CONTACT_ROLES — role definition context for CRO_CODE.
• OKC.OKC_K_HEADERS — contract header context for DNZ_CHR_ID.
• OKC_CONTACT_PARTIES / OKC_CPL_LINES — contract party lines referenced by CPL_ID.