Results for “okc_k_items_u1”

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

Overview

OKC.OKC_K_ITEMS is the contract items table within the Oracle Contracts (OKC) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual items associated with contract lines, providing the link between a contract line and the underlying object being contracted, such as an inventory item, an article, or another entity exposed through an OKX view. The table resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as OKC.OKC_K_ITEMS with a status of VALID.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. The table carries descriptive and state attributes that qualify a parent business key rather than acting as a pure hub or link, suggesting it may be modelled as a satellite keyed to the contract line or contract header, while its foreign key columns to OKC_K_HEADERS_B and OKC_K_LINES_B simultaneously give it link-like characteristics.

Key Information Stored

The surrogate primary key of the table is ID, a NUMBER column uniquely identifying each contract item. The documented unique index OKC_K_ITEMS_U1 enforces uniqueness on this column alone; no separate composite business-key unique index is documented, so ID serves as both the physical and the effective unique identifier.

The principal columns include:

• ID — Surrogate primary key for the contract item.
• CLE_ID — Foreign key to the contract line in OKC_K_LINES_B that owns the item.
• CHR_ID — Foreign key to the contract in OKC_K_HEADERS_B; populated only for parent lines.
• CLE_ID_FOR — Foreign key to OKC_K_LINES_B identifying the parent line when the current item's line is a sub-line.
• DNZ_CHR_ID — Denormalized contract ID retained for performance, indexed by OKC_K_ITEMS_N3.
• OBJECT1_ID1 and OBJECT1_ID2 — Foreign key components pointing to an OKX view identified by JTOT_OBJECT1_CODE; together they form the referenced view's primary key.
• JTOT_OBJECT1_CODE — Foreign key to JTF_OBJECTS_B indicating which OKX view the OBJECT1 columns reference.
• UOM_CODE — Unit of measure for the item, referencing MTL_UNITS_OF_MEASURE.
• EXCEPTION_YN — Flag (Y/N) identifying items de-selected from a master list.
• NUMBER_OF_ITEMS — Quantity of items represented.
• PRICED_ITEM_YN — Flag (Y/N) indicating whether the item is priced.
• OBJECT_VERSION_NUMBER — Optimistic locking counter, set to 1 on insert and incremented on update.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS supporting multi-org security.

Common Use Cases and Queries

Typical reporting retrieves all items belonging to a contract line, or consolidates items under a contract header using the denormalized DNZ_CHR_ID. The following pattern lists items for a given line:

• SELECT i.id, i.cle_id, i.object1_id1, i.jtot_object1_code, i.number_of_items FROM okc.okc_k_items i WHERE i.cle_id = :cle_id;

Exception reporting identifies items excluded from a master list with WHERE exception_yn = 'Y', while pricing analysis filters on PRICED_ITEM_YN = 'Y'. Because the OBJECT1 columns resolve dynamically through JTF_OBJECTS_B, joins to the appropriate OKX view require first reading JTOT_OBJECT1_CODE, a pattern often implemented through the OKC item APIs rather than ad hoc SQL.

Related Objects

The most significant related objects, inferred from the documented foreign key relationships, are:

• OKC_K_LINES_B — Referenced by CLE_ID and CLE_ID_FOR; the parent line structure.
• OKC_K_HEADERS_B — Referenced by CHR_ID; the contract header.
• JTF_OBJECTS_B — Referenced by JTOT_OBJECT1_CODE; resolves the OKX view for the item.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for organization security.
• OKC_ITEM_PARTYS_B — References this table through CIM_ID; stores parties associated with each contract item.

Collectively these relationships place OKC_K_ITEMS at the intersection of contract structure, object resolution, and party assignment within the OKC schema.