Search Results oks_serv_custexc_v




Overview
Explore in AI Chat

Overview

OKS_SERV_CUSTEXC_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OKS (Service Contracts) product family and is described in the ETRM metadata as the "View for Service Availability Exceptions and Parties." Its purpose is to present service availability exception records alongside the customer or party information associated with each exception, so that downstream reports, concurrent programs, and integration interfaces can retrieve exception details together with the account number, account name, and customer status in a single query.

The view is classified as VALID and is not a table, so no DML is possible against it. It functions as a reporting and integration surface rather than an operational entity. Because the customer attributes are resolved through the party layer, the view is particularly relevant when a user searches for or references the OKX_PARTY entity, since the join predicate explicitly filters on JTOT_OBJECT1_CODE = 'OKX_PARTY'.

Underlying Base Objects

The view is defined over two documented referenced base objects:

  • OKS_SERV_AVAIL_EXCEPTS (aliased EXC), referenced through a synonym. This is the driving table holding the service availability exception rows, including object references, revision ranges, effective dates, and the standard DFF attribute columns plus WHO audit columns.
  • OKX_PARTIES_V (aliased PARTY), a view over the party model. This supplies the account number, account name, and customer status.

The two objects are joined on PARTY.ID1 = EXC.OBJECT1_ID1, and the join is constrained by EXC.JTOT_OBJECT1_CODE = 'OKX_PARTY'. This means the view only returns exception rows whose referenced object type is OKX_PARTY, i.e., exceptions tied to a party/account. Rows in OKS_SERV_AVAIL_EXCEPTS pointing at other object types are filtered out. OKX_PARTIES_V itself resolves ID1 to the underlying party identifier, which is why the view is a natural starting point when working with OKX_PARTY references.

Key Columns

The view exposes all exception columns from OKS_SERV_AVAIL_EXCEPTS plus three party-derived columns.

Common Use Cases and Queries

Typical uses include service availability reporting, exception auditing by customer, and integration extracts that must carry the account context. All queries are read-only SELECT statements. A simple customer-facing listing is:

  • SELECT id, account_number, account_name, cust_status, start_date_active, end_date_active FROM oks_serv_custexc_v;

To inspect exceptions for a specific account and active window:

  • SELECT c.sav_id, c.id, c.account_name, c.revision_low, c.revision_high FROM oks_serv_custexc_v c WHERE c.account_number = :p_account AND SYSDATE BETWEEN c.start_date_active AND NVL(c.end_date_active, SYSDATE + 1);

Because the underlying join is constrained to the OKX_PARTY object code, joins back to party or service availability entities are straightforward, and no additional object-type filtering is required. Care should be taken that the outer join behaviour of the party view is understood: rows in OKS_SERV_AVAIL_EXCEPTS without a matching party would not be returned by this view, so callers needing all exceptions irrespective of party should query the base table directly.