Search Results product_item

Overview

APPS.OKS_SERV_PRODEXC_V is a service contract exception view in Oracle E-Business Suite (documented against ETRM 12.1.1 / 12.2.2). It presents product-level exception records defined for service availability rules, joining those exceptions to the system item master so that the numeric item identifier is resolved to a business-readable product name and description. In the service contracts schema the view acts as a reporting and integration facade over the OKS_SERV_AVAIL_EXCEPTS table, exposing only exception rows whose object type is 'OKX_SYSITEM' — that is, exceptions scoped to an inventory item rather than to another JTOT-classified object. Because the view performs the item join internally, consumers do not need to know the OKX_SYSTEM_ITEMS_V structure or the meaning of the JTOT_OBJECT1_CODE discriminator.

Underlying Base Objects

The view is defined over exactly two documented base objects, both resolved through APPS synonyms:

• OKS_SERV_AVAIL_EXCEPTS (SYNONYM) — the exception table carrying the rule identifier (SAV_ID), the target object keys (OBJECT1_ID1, OBJECT1_ID2), the JTOT object code, effectivity dates, revisions, manufacturing organization, and the standard 15-attribute flexfield columns plus WHO audit columns.
• OKX_SYSTEM_ITEMS_V (VIEW) — the item master view supplying NAME, DESCRIPTION, and ORGANIZATION_ID, keyed on ID1.

The join predicate is prd.id1 = exc.object1_id1, restricted by exc.jtot_object1_code = 'OKX_SYSITEM'. This is an inner equi-join, so exception rows that reference a non-item object code, or that fail to match a valid item, are excluded from the result set.

Key Columns

• ID, SAV_ID — the exception record identifier and the parent service availability rule it qualifies.
• OBJECT1_ID1, OBJECT1_ID2 — the JTOT object key; ID1 corresponds to the item identifier used in the join to OKX_SYSTEM_ITEMS_V.
• JTOT_OBJECT1_CODE — the object discriminator, always 'OKX_SYSITEM' in this view.
• MANUFACTURING_ORG_ID — the organization context for the exception.
• REVISION_LOW, REVISION_HIGH — the item revision range to which the exception applies.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effectivity window governing when the exception is in force.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments carried from the base table.
• PRODUCT_ITEM, PRODUCT_DESCRIPTION, ORGANIZATION_ID — derived from OKX_SYSTEM_ITEMS_V; PRODUCT_ITEM is the item name and ORGANIZATION_ID the owning inventory organization.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• OBJECT_VERSION_NUMBER — optimistic locking token.

Common Use Cases and Queries

Typical usages include listing the products excepted from a service availability rule, verifying effectivity windows before contract authoring, and feeding downstream extracts with resolved item names. The following query lists active, item-scoped exceptions:

• SELECT sav_id, product_item, product_description, revision_low, revision_high, start_date_active, end_date_active FROM apps.oks_serv_prodexc_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));
• SELECT organization_id, product_item, COUNT(*) FROM apps.oks_serv_prodexc_v GROUP BY organization_id, product_item ORDER BY 3 DESC;
• SELECT id, sav_id, product_item, attribute_category, attribute1, attribute2 FROM apps.oks_serv_prodexc_v WHERE sav_id = :p_sav_id;

Because the view filters on a fixed JTOT code and joins to the item master, it is safe to use directly in concurrent programs, OA Framework inquiries, and BI Publisher data models without re-implementing the OKX_SYSITEM restriction logic.