Results for “okc_k_items_v”

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

Overview

OKC_K_ITEMS_V is a reporting and integration view owned by the APPS schema within the OKC – Contracts Core product of Oracle E-Business Suite. It is documented as a view over the OKC_CONTRACT_ITEMS table, and in the ETRM 12.2.2 metadata it is defined directly over the OKC_K_ITEMS synonym. The view exposes contract line item data using the naming conventions favored by Oracle Contracts APIs, where the physical table OKC_K_ITEMS is addressed through the CIMB alias (Contract Item "MB" interface). This view presents a stable, API-aligned projection of contract item records, allowing developers and report authors to query contract items without depending on the physical table's internal naming.

The object is marked VALID, confirming the view compiles cleanly against the underlying synonym in both 12.1.1 and 12.2.2. Its placement in the Contracts Core module means it participates in the contract authoring, pricing, and fulfillment data model.

Underlying Base Objects

According to the documented view text, OKC_K_ITEMS_V is defined over a single source: OKC_K_ITEMS (referenced via the synonym). The base table named in the description is OKC_CONTRACT_ITEMS, which is the physical Contracts table that OKC_K_ITEMS exposes. The view performs a straight column projection with no joins, aggregation, or filtering — a classic compatibility view that renames or surfaces columns so they match the OKC API column conventions.

• Owner/schema: APPS
• Referenced base object: OKC_K_ITEMS (SYNONYM)
• Underlying table described: OKC_CONTRACT_ITEMS
• View type: non-join projection view, one row per contract item

Key Columns

The view exposes 25 columns mapped from the synonym. The most significant are:

• ROW_ID – the base table ROWID, used for direct row addressing.
• ID – the primary key of the contract item record.
• OBJECT_VERSION_NUMBER – optimistic locking surrogate used by the Contracts APIs to detect concurrent updates.
• CLE_ID – the contract line (header-level line) identifier to which the item belongs.
• CHR_ID – the contract header identifier, the top-level contract document.
• CLE_ID_FOR and DNZ_CHR_ID – denormalized contract/line references retained for performance and API convenience.
• OBJECT1_ID1, OBJECT1_ID2, JTOT_OBJECT1_CODE – the JTOT ("item" object type) reference, identifying the inventory item through its flexible key components and object code.
• UOM_CODE – unit of measure for the item quantity.
• EXCEPTION_YN – flag indicating an exception condition on the line item.
• NUMBER_OF_ITEMS – quantity of the item on the contract line.
• PRICED_ITEM_YN – indicates whether the item is priced.
• UPG_ORIG_SYSTEM_REF / UPG_ORIG_SYSTEM_REF_ID – references supporting upgrade/migration traceability.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS WHO audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID – standard concurrent program audit columns.

Common Use Cases and Queries

Because the view is a thin projection of the contract items table, it is typically used for read-only reporting, interface extraction, and validation routines. Common scenarios include extracting all items on a contract, checking pricing flags, and joining to contract headers and lines.

• List all items for a given contract header.
• Identify unpriced or exception items for a contract.
• Export item and UOM detail to a downstream pricing or fulfillment system.
• Reconcile item quantities against contract line expectations.

Sample query retrieving items for a specific contract header:

SELECT id, cle_id, chr_id, uom_code, number_of_items, priced_item_yn, exception_yn
FROM apps.okc_k_items_v
WHERE chr_id = :p_chr_id;

Sample query identifying priced items and their unit of measure:

SELECT k.id, k.chr_id, k.cle_id, k.uom_code, k.number_of_items
FROM apps.okc_k_items_v k
WHERE k.priced_item_yn = 'Y'
AND k.number_of_items > 0;

Sample query returning items not yet priced for review:

SELECT k.id, k.chr_id, k.object1_id1, k.jtot_object1_code
FROM apps.okc_k_items_v k
WHERE NVL(k.priced_item_yn,'N') = 'N';

Since OKC_K_ITEMS_V exposes the OBJECT_VERSION_NUMBER, it can be used safely in conjunction with the Contracts APIs, but it must not be used for direct DML; all inserts and updates should flow through the supported OKC APIs against OKC_K_ITEMS.