Search Results okc_contract_rel_objs_n4

Overview

OKC.OKC_K_REL_OBJS is a core contract repository table within the Oracle E-Business Suite Contract Management (OKC) schema. It is an intersection entity that links a contract header or contract line to other objects in the schema in a predefined manner. Its primary purpose is to establish and preserve the lineage between a contract and the source or target documents from which it originated or to which it relates — most notably orders and quotes originating in Oracle Order Management and Oracle Quoting.

Functionally, the table supports scenarios such as linking an extended warranty contract header to the sales order header that generated it, and simultaneously linking each individual contract line to the corresponding order line. This bidirectional association is essential for downstream processes including order-to-contract conversion, warranty entitlement, and service contract coverage reporting.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, confirming its classification as transactional data. Its indexes reside separately in APPS_TS_TX_IDX. A heuristic Data Vault classification derived from the foreign key structure suggests this object is best modeled as a link table: its foreign keys to OKC_K_HEADERS_B, OKC_K_LINES_B, and FND_SECURITY_GROUPS, combined with its relationship-typed RTY_CODE, indicate a many-to-many association entity rather than an independent hub.

Key Information Stored

The table contains 30 documented columns. The most operationally significant include:

• ID — NUMBER, the surrogate primary key. It is the single column of the unique index OKC_CONTRACT_REL_OBJS_U1. It is system-generated and has no business meaning; APIs rely on it for row identification.
• CHR_ID — the ID of the contract header associated with the relation. Foreign key to OKC_K_HEADERS_B and served by index OKC_CONTRACT_REL_OBJS_N1.
• CLE_ID — the ID of the contract line for which the relation object is defined. Foreign key to OKC_K_LINES_B and served by index OKC_CONTRACT_REL_OBJS_N2.
• RTY_CODE — VARCHAR2(30), the relationship object type code that distinguishes the nature of the relationship (for example, order versus quote origination).
• OBJECT1_ID1 — VARCHAR2(40), the first part of the primary key of the referenced external object, resolved against an OKX view. Indexed by OKC_CONTRACT_REL_OBJS_N4.
• OBJECT1_ID2 — VARCHAR2(200), the second part of the referenced object's primary key.
• JTOT_OBJECT1_CODE — VARCHAR2(30), foreign key to JTF_OBJECTS_B, identifying which OKX view the OBJECT1_ID1/OBJECT1_ID2 pair points to.
• OBJECT_VERSION_NUMBER — sequential concurrency-control value initialized to 1 and incremented on update by the OKC APIs.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used for multi-tenant data isolation and row-level security.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns providing audit lineage.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) extension columns for customer-defined attributes.

Common Use Cases and Queries

The principal use case is tracing contract-to-source-document relationships, particularly for warranty and service contracts generated from orders. A typical query joins the relation table to contract headers and lines:

• Identify the order behind a contract: SELECT chr.chr_id, rel.object1_id1, rel.object1_id2 FROM okc_k_rel_objs rel, okc_k_headers_b chr WHERE rel.chr_id = chr.id AND rel.rty_code = :p_rty;
• Reconcile contract lines to order lines: SELECT rel.cle_id, rel.object1_id1, rel.object1_id2 FROM okc_k_rel_objs rel WHERE rel.cle_id = :p_cle_id;
• Determine the referenced OKX view by joining JTOT_OBJECT1_CODE to JTF_OBJECTS_B.
• Enforce record currency in custom API integrations by checking OBJECT_VERSION_NUMBER before updates.
• Restrict reports to the correct operating unit or tenant by filtering on SECURITY_GROUP_ID.

This object is also relevant to order-to-contract conversion reports, service entitlement inquiries, and any custom extension that must navigate between EBS contracts and external object identifiers.

Related Objects

• OKC.OKC_K_HEADERS_B — referenced via CHR_ID; the parent contract header.
• OKC.OKC_K_LINES_B — referenced via CLE_ID; the parent contract line.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security grouping.
• JTF_OBJECTS_B — referenced via JTOT_OBJECT1_CODE; defines the OKX view backing OBJECT1_ID1/OBJECT1_ID2.
• OKX views — target objects identified by JTOT_OBJECT1_CODE, exposing the external primary key components.
• OKC_CONTRACT_REL_OBJS_U1 — the unique index on ID that enforces surrogate key uniqueness.
• OKC_CONTRACT_REL_OBJS_N1, N2, N4 — nonunique indexes on CHR_ID, CLE_ID, and OBJECT1_ID1 supporting join and lookup performance.
• OKC contract APIs — the public OKC packages that manage rows in this table, using OBJECT_VERSION_NUMBER for optimistic locking.