Results for “oks_k_order_contacts”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKS_K_ORDER_CONTACTS table is a Service Contracts (OKS) module object in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores contact assignments associated with order details in the OKS service contract ordering flow. The table acts as the association between a specific order detail line (COD_ID) and a contact role (CRO_CODE) pointing at a JTF object reference. It is a transactional assignment table rather than a master entity, and it carries the standard EBS WHO columns plus a SECURITY_GROUP_ID for multi-tenant/operating-unit security filtering.

Based on the documented foreign-key structure, the heuristic Data Vault classification is link. Every notable FK on this table references an independent entity — OKS_K_ORDER_DETAILS and JTF_OBJECTS_B — making the row a relationship between those entities rather than an attribute-bearing description of one. A Data Vault model would therefore treat OKS_K_ORDER_CONTACTS as a link table connecting the order-detail hub and the JTF object hub, with the unique index OKS_K_ORDER_CONTACTS_U2 supplying the natural business key of that link.

Key Information Stored

The table exposes 12 documented columns. The most significant are:

• ID — surrogate primary key, enforced by OKS_K_ORDER_CONTACTS_PK and also by unique index OKS_K_ORDER_CONTACTS_U1. This is a system-generated identifier with no business meaning.
• COD_ID — foreign key to OKS_K_ORDER_DETAILS; identifies the order detail to which the contact is attached. This is the dominant business-key component.
• CRO_CODE — contact role code, qualifying the nature of the contact (for example, the role the party plays on the order). Part of the second unique index.
• OBJECT1_ID1 and OBJECT1_ID2 — the object identifier pair that, together with COD_ID and CRO_CODE, forms the business key in OKS_K_ORDER_CONTACTS_U2.
• JTOT_OBJECT_CODE — foreign key to JTF_OBJECTS_B, identifying the JTF object type that the contact reference resolves against.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used for row-level security filtering.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework, incremented on update.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns identifying the creating and updating users and timestamps.

The distinction is important: ID is the surrogate key, while the business-key candidate is the composite (COD_ID, CRO_CODE, OBJECT1_ID1, OBJECT1_ID2) backed by OKS_K_ORDER_CONTACTS_U2.

Common Use Cases and Queries

The table is primarily read in reporting on contract/order contact coverage and in validation logic that determines whether the required contact roles have been captured for an order. A typical join retrieves contacts with their order detail context:

• Joining to OKS_K_ORDER_DETAILS on COD_ID to resolve the order header and line context.
• Joining to JTF_OBJECTS_B on JTOT_OBJECT_CODE to obtain the JTF object definition behind the contact.
• Filtering by SECURITY_GROUP_ID to respect EBS security-group restrictions in multi-org reports.
• Aggregating by CRO_CODE to report which contact roles are represented across a contract set.

A representative pattern is a lookup for all contacts on a given order detail, ordered by creation, using the business-key columns to de-duplicate results:

• SELECT c.ID, c.COD_ID, c.CRO_CODE, c.OBJECT1_ID1, c.OBJECT1_ID2, c.JTOT_OBJECT_CODE FROM OKS.OKS_K_ORDER_CONTACTS c, OKS.OKS_K_ORDER_DETAILS d WHERE c.COD_ID = d.ID
• Add AND c.SECURITY_GROUP_ID = :sgid when operating under security-group enforcement.

Related Objects

The following dependencies are documented or directly implied by the FK metadata:

• OKS_K_ORDER_DETAILS — referenced through COD_ID; the parent order-detail entity.
• JTF_OBJECTS_B — referenced through JTOT_OBJECT_CODE; defines the JTF object type used to resolve the contact reference.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; governs row visibility.
• OKS_K_ORDER_CONTACTS_PK, OKS_K_ORDER_CONTACTS_U1, OKS_K_ORDER_CONTACTS_U2 — the primary and unique indexes that enforce the surrogate and business keys respectively.
• The OKS Service Contracts APIs and concurrent programs that populate and consume order contacts typically insert and update this table through supported interfaces rather than by direct DML.