Search Results oks_serv_prodexc_v




Overview
Explore in AI Chat

Overview

The OKS_SERV_PRODEXC_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) Service Contracts (OKS) module, owned by the APPS schema. It is documented as VALID in both EBS 12.1.1 and 12.2.2 and is described in the ETRM metadata as a "View for Service Product exceptions." Its principal function is to present exception records defined against service products, enriching each stored exception with human-readable product identifiers and descriptions.

This view is particularly relevant to users searching on product_description, because one of its exposed columns, PRODUCT_DESCRIPTION, resolves the descriptive text of the underlying inventory item associated with each exception row. Rather than forcing report authors and integration developers to join the base exception table to the item master themselves, the view encapsulates that join and delivers a denormalized result set suitable for direct consumption in concurrent programs, BI Publisher reports, OAF pages, and downstream interface extracts.

Underlying Base Objects

The view is defined over two documented base objects:

  • OKS_SERV_AVAIL_EXCEPTS (SYNONYM) — the primary table storing service availability exception records.
  • OKX_SYSTEM_ITEMS_V (VIEW) — the system items view that supplies the product item name, description, and organization identifier.

The relationship between the two is enforced through the join predicate PRD.ID1 = EXC.OBJECT1_ID1, filtered by the condition EXC.JTOT_OBJECT1_CODE = 'OKX_SYSITEM'. This means that only exception rows whose object reference resolves to an inventory system item are returned, and each such row is matched to the corresponding item master definition. The view therefore behaves as a specialized join layer over generic exception storage, where the OBJECT1_ID1 and JTOT_OBJECT1_CODE columns constitute the polymorphic foreign key mechanism used throughout OKS exception data.

Key Columns

The view exposes the full column list of the base exception table plus three derived columns. The most significant columns are:

  • ID — the primary key of the underlying OKS_SERV_AVAIL_EXCEPTS record.
  • SAV_ID — the identifier linking the exception to the parent service availability record.
  • OBJECT1_ID1 — the item identifier of the product to which the exception applies, joined to OKX_SYSTEM_ITEMS_V.ID1.
  • OBJECT1_ID2, JTOT_OBJECT1_CODE — the polymorphic object key components; the latter is constrained to 'OKX_SYSITEM'.
  • MANUFACTURING_ORG_ID — the manufacturing organization context for the exception.
  • REVISION_LOW, REVISION_HIGH — the revision range within which the exception applies.
  • START_DATE_ACTIVE, END_DATE_ACTIVE — the effective date window of the exception.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield columns.
  • PRODUCT_ITEM — the item name sourced from PRD.NAME.
  • PRODUCT_DESCRIPTION — the descriptive text of the product sourced from PRD.DESCRIPTION, which is the column most commonly targeted by users searching on "product_description."
  • ORGANIZATION_ID — the item master organization identifier sourced from PRD.ORGANIZATION_ID.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical usage includes auditing which products carry service availability exceptions, validating effective date ranges and revision boundaries, and feeding exception data into reporting or integration layers where product descriptions are required alongside exception attributes.

  • Listing exceptions with product descriptions: SELECT object1_id1, product_item, product_description, revision_low, revision_high FROM oks_serv_prodexc_v WHERE organization_id = :org_id;
  • Filtering by description text: SELECT id, product_item, product_description FROM oks_serv_prodexc_v WHERE UPPER(product_description) LIKE UPPER('%' || :keyword || '%');
  • Checking currently active exceptions: SELECT sav_id, product_item, start_date_active, end_date_active FROM oks_serv_prodexc_v WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Because the view is read-only and already carries audit columns and flexfield attributes, it is safe to use directly in custom reports and interfaces without additional joins for product descriptive information.