Results for “oki_sold_itm_lines”

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

Overview

OKI_SOLD_ITM_LINES is a Contracts Intelligence (OKI) module table that stores information about top-level lines belonging to a contract of the sell intent. In Oracle E-Business Suite, Contracts Intelligence provides analytical and reporting structures over contract repositories, distinguishing between sell-intent and buy-intent contracts. This table specifically captures the sold — that is, revenue-bearing — line structure, holding the priced unit lines from which downstream contract analytics, margin analysis, and renewal tracking are derived.

The object is documented as obsolete and is flagged as "Not implemented in this database" in the ETRM metadata. Its extraction/documented physical schema pertains to release 12.1.1, and the object is expected to be present with equivalent structure in 12.2.2 where the OKI schema is deployed. The heuristic Data Vault classification supplied by the metadata is standalone, suggesting that from a modeling perspective OKI_SOLD_ITM_LINES is best treated as an independent satellite-like structure rather than a hub or link, owing to the absence of formal outbound foreign keys other than the security predicate. The table is owned by the OKI schema and contains 58 documented columns.

Key Information Stored

The most operationally significant columns are:

• CLE_ID — the surrogate primary key, enforced by OKI_SOLD_ITM_LINES_PK and mirrored as the unique business-key candidate in OKI_SOLD_ITM_LINES_U1 (CLE_ID). It uniquely identifies each sold contract line.
• CHR_ID — the contract header reference linking the line to its parent sell contract.
• CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, and COMPLETE_CONTRACT_NUMBER — the human-readable contract identifiers, including the modifier-qualified concatenated form.
• LINE_NUMBER — the line sequence within the contract.
• SCS_CODE and STS_CODE — status and source classification codes for the line.
• START_DATE, END_DATE, DATE_TERMINATED, DATE_RENEWED — the temporal lifecycle of the line, supporting active, terminated, and renewed segmentation.
• SOLD_ITEM, ITEM_ID — the sold item description and its inventory item reference.
• UOM_CODE, NUMBER_OF_ITEMS, UNIT_PRICE, UNIT_PRICE_PERCENT — pricing and quantity attributes.
• CURRENCY_CODE, PRICE_NEGOTIATED, PRICE_NEGOTIATED_RENEWED — transactional currency pricing, with renewal variants.
• SOB_PRICE_UNIT, SOB_PRICE_NEGOTIATED, SOB_CURRENCY_CODE and the corresponding BASE_PRICE_*/BASE_CURRENCY_CODE columns — set-of-books and base-currency converted amounts.
• AUTHORING_ORG_ID, INVENTORY_ORGANIZATION_ID — organizational ownership and fulfillment context.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, providing multi-tenant data security.

Common Use Cases and Queries

Typical usage centers on contract revenue analytics, price realization reporting, and renewal/termination analysis. A representative query joins lines to their header using CHR_ID:

• Report sold lines by contract: SELECT LINE_NUMBER, SOLD_ITEM, UNIT_PRICE, CURRENCY_CODE FROM OKI_SOLD_ITM_LINES WHERE CHR_ID = :p_chr_id ORDER BY LINE_NUMBER;
• Identify lines nearing expiry: SELECT COMPLETE_CONTRACT_NUMBER, END_DATE FROM OKI_SOLD_ITM_LINES WHERE END_DATE BETWEEN SYSDATE AND SYSDATE+90;
• Analyze negotiated price variance against unit price for margin review.
• Segment revenue by AUTHORING_ORG_ID or INVENTORY_ORGANIZATION_ID for organizational reporting.

Reports are frequently filtered through SECURITY_GROUP_ID to respect operating unit access.

Related Objects

• FND_SECURITY_GROUPS — joined on OKI_SOLD_ITM_LINES.SECURITY_GROUP_ID for row-level security enforcement.
• OKI contract header tables — referenced via CHR_ID, supplying contract-level attributes.
• OKI_PURCHASED_ITM_LINES / buy-intent counterparts — the parallel structure for procurement-side contracts.
• OKI_CONTRACTS_* analytical views — contract intelligence reporting views that project sell-intent line metrics.
• Contracts Core (OKC) tables — upstream sources from which OKI extracts contract lines.

Because the object is obsolete and not implemented in every database, implementations should verify its presence before authoring dependent extracts or reports.