Search Results cust_status




Overview
Explore in AI Chat

Overview

APPS.OKS_SERV_CUSTEXC_V is a reporting and integration view in the Oracle E-Business Suite service (OKS) module. It exposes the exception records that govern service availability restrictions applied to specific customers. The view joins the service availability exception base table to a party view so that each exception row is enriched with the customer account number, account name, and the current customer status. It is typically consumed by service contract, depot repair, and field service functionality that must determine whether a given customer is excluded from a standard service availability definition.

Because the view surfaces CUST_STATUS directly from the party source, it is commonly referenced in reporting where the operational state of the customer must be evaluated alongside the exception definition itself. The user search term "cust_status" corresponds exactly to the aliased column derived from PARTY.STATUS in the view definition.

Underlying Base Objects

The view is owned by APPS and is defined over two referenced objects as documented in the ETRM metadata:

  • OKS_SERV_AVAIL_EXCEPTS (SYNONYM) — the primary service availability exception table, aliased as EXC. This table stores the exception identifier, the availability definition it belongs to, the subject object reference, validity dates, revision ranges, manufacturing organization, and a standard set of DFF attribute columns.
  • OKX_PARTIES_V (VIEW) — the trading community party view, aliased as PARTY. It supplies the party number, party name, and party status.

The join condition is PARTY.ID1 = EXC.OBJECT1_ID1, restricted by EXC.JTOT_OBJECT1_CODE = 'OKX_PARTY'. Consequently, only exception rows whose subject object is a party record are returned, ensuring the join is meaningful and that the status returned truly reflects the customer on the exception.

Key Columns

Note that a duplicate OBJECT_VERSION_NUMBER and the audit columns follow the underlying exception table definition, so the view does not itself alter those values.

Common Use Cases and Queries

Typical scenarios include identifying customers excluded from service coverage, filtering exceptions by customer status, and auditing active exceptions within a date window. A representative query is:

  • SELECT account_number, account_name, cust_status, start_date_active, end_date_active FROM apps.oks_serv_custexc_v WHERE cust_status = 'A';
  • SELECT * FROM apps.oks_serv_custexc_v WHERE sav_id = :p_sav_id AND sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate + 1);
  • SELECT cust_status, COUNT(*) FROM apps.oks_serv_custexc_v GROUP BY cust_status;

These queries support operational decisions about service entitlement and are safe to embed in concurrent programs or BI Publisher reports, provided the calling responsibility has select privilege on the APPS synonym and its underlying objects.