Search Results oks_serv_avail_excepts_pk

Overview

OKS_SERV_AVAIL_EXCEPTS is a Service Contracts (OKS) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that stores exception information associated with a service availability. A service availability (referred to internally as SAV) defines whether a specific item, at a defined manufacturing organization and revision range, is eligible for service during an effective date window. When that eligibility must be narrowed or suppressed for specific conditions, the exception records captured in OKS_SERV_AVAIL_EXCEPTS provide the qualifying detail. The foreign key relationship to OKS_SERV_AVAILS (via SAV_ID) confirms that this is a dependent child of the service availability entity.

Under a heuristic Data Vault classification mined from the foreign key structure, this table is modeled as a link object. It resolves the relationship between a service availability and an external object registered in JTF_Objects_B (via JTOT_OBJECT1_CODE), while also carrying descriptive and audit attributes. This classification should be treated as a modeling suggestion rather than a declared Oracle designation.

Key Information Stored

The table contains 33 documented columns. The most significant are:

• ID — the surrogate primary key, enforced by OKS_SERV_AVAIL_EXCEPTS_PK and also covered by the unique index OKS_SERV_AVAIL_EXCEPTS_U1. This is the single documented business-key candidate.
• SAV_ID — foreign key back to OKS_SERV_AVAILS, identifying the parent service availability to which the exception applies.
• JTOT_OBJECT1_CODE — foreign key to JTF_OBJECTS_B, identifying the object type referenced by the exception.
• OBJECT1_ID1 and OBJECT1_ID2 — the composite object identifier values that point to the specific object instance within the JTF object model.
• MANUFACTURING_ORG_ID — the inventory organization context in which the exception is effective.
• REVISION_LOW and REVISION_HIGH — the revision range bounds that qualify the exception.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the date window during which the exception is active.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Object Library (AOL) framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF-enabled descriptive flexfield columns for customer-defined extensions.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or security-group partitioning.

Common Use Cases and Queries

Typical usage centers on validating whether a given item/revision/organization combination is serviceable. Sample query to inspect all active exceptions for one service availability:

• SELECT e.id, e.sav_id, e.jtot_object1_code, e.object1_id1, e.object1_id2, e.revision_low, e.revision_high, e.start_date_active, e.end_date_active, e.manufacturing_org_id FROM oks.oks_serv_avail_excepts e WHERE e.sav_id = :p_sav_id AND SYSDATE BETWEEN NVL(e.start_date_active, SYSDATE) AND NVL(e.end_date_active, SYSDATE);

Reporting and reconciliation patterns include joining to OKS_SERV_AVAILS to surface the parent availability definition, joining to JTF_OBJECTS_B to resolve object type descriptions, and filtering on MANUFACTURING_ORG_ID for organization-specific entitlement reporting. Because ATTRIBUTE1–15 are available, DFF-based extracts are also common in customer-specific extensions.

Related Objects

• OKS.OKS_SERV_AVAILS — parent service availability entity; join on OKS_SERV_AVAIL_EXCEPTS.SAV_ID = OKS_SERV_AVAILS.SAV_ID.
• JTF.JTF_OBJECTS_B — object registry; join on OKS_SERV_AVAIL_EXCEPTS.JTOT_OBJECT1_CODE = JTF_OBJECTS_B.JTOT_OBJECT_CODE.
• FND.FND_SECURITY_GROUPS — security-group partitioning; join on SECURITY_GROUP_ID.
• OKS.OKS_SERV_AVAIL_EXCEPTS_PK and OKS_SERV_AVAIL_EXCEPTS_U1 — the primary key constraint and unique index enforcing ID uniqueness.
• Service Contracts APIs in the OKS schema that create and maintain service availabilities, including their exception child rows, are the primary programmatic entry points; direct DML against this table should be avoided in favor of the supported Service Contracts interfaces.