Search Results oks_oks_serv_avails_u1

Overview

OKS.OKS_SERV_AVAILS is a transactional configuration table in the Oracle E-Business Suite Service (OKS) module. It stores the general service availability definitions for a service item, capturing whether a given service is broadly available for a party or product. The table is populated through the header region of the Service Availability setup user interface, and its records form one half of the availability model used throughout the enterprise.

Availability determination is accomplished by combining this table with OKS.OKS_SERV_AVAIL_EXCEPTS, which stores exceptions to the general rules. Together, the two tables express the inclusion and exclusion logic that governs which services may be sold against service programs, warranties, and extended warranties. These rules are honored by upstream applications such as quoting and Order Management at the point a service item is selected.

From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning. It carries descriptive attributes and effectivity dates attached to a business key rather than representing a pure hub or association link, making it a candidate for satellite treatment in a dimensional or vault-style design.

Key Information Stored

The table is defined in the APPS_TS_TX_DATA tablespace with 31 documented columns. The most significant are:

• ID — the internal unique identifier and the surrogate primary key (OKS_SERV_AVAILS_PK). It is also the column behind the unique index OKS_OKS_SERV_AVAILS_U1.
• OBJECT1_ID1 — the item identifier for which service availability is defined.
• OBJECT1_ID2 — documented as not used in the current data model.
• JTOT_OBJECT1_CODE — foreign key to JTF_OBJECTS_B, identifying the OKX view and source object containing the service item.
• GENERAL_YN — the controlling flag. When the "generally available" checkbox is checked, two records are written to this table (party and product) and the flag is set to 'Y'; when unchecked, it is set to 'N', meaning the service is not generally available.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effectivity dates bounding the availability window.
• EXCEPT_OBJECT_TYPE — indicates the object type against which exceptions are applied.
• OBJECT_VERSION_NUMBER — optimistic locking counter, set to 1 on insert and incremented on update by the APIs.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard DFF flexfield extension block.

Common Use Cases and Queries

The most frequent query pattern resolves generally available services for a given item while filtering out exception rows. A typical construct joins to the exception table to identify services that remain sellable:

• Reporting on which service items are flagged generally available: select from OKS_SERV_AVAILS where GENERAL_YN = 'Y', restricted by effectivity dates.
• Diagnosing why a service cannot be quoted — inspect both the general row and any countersigned exception in OKS_SERV_AVAIL_EXCEPTS.
• Data migration and interfaces for Service Availability setup commonly write to this table through the OKS APIs, which maintain OBJECT_VERSION_NUMBER.
• Auditing changes over time using LAST_UPDATE_DATE and the audit columns.

Related Objects

• OKS.OKS_SERV_AVAIL_EXCEPTS — references this table via SAV_ID → ID; stores availability exceptions.
• JTF.JTF_OBJECTS_B — referenced by JTOT_OBJECT1_CODE; provides the source object/view metadata for the service item.
• FND.FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for data security.
• OKS.OKS_SERV_AVAILS_PK — the primary key constraint on ID.
• OKS_OKS_SERV_AVAILS_U1 — the unique index on ID in APPS_TS_TX_IDX.
• OKS Service Availability setup UI and the public OKS APIs that insert and update availability records.