Search Results oks_serv_avails_pk

Overview

OKS_SERV_AVAILS is a Service Contracts (OKS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores availability information for a service. It is owned by the OKS schema and holds a VALID status. Functionally, the table records the periods during which a service or object is available, together with any exception handling that qualifies that availability. It is therefore consulted during service contract authoring, scheduling, and entitlement evaluation, where the application must determine whether coverage, resources, or service windows are open for a given object.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. This suggests treating OKS_SERV_AVAILS as a descriptive satellite attached to a parent business key, capturing attributes that change over time rather than defining new core entities. The parent key is carried through the object columns and the JTF_OBJECTS_B reference rather than being generated wholly within this table.

Key Information Stored

The table contains 31 documented columns. The primary key is OKS_SERV_AVAILS_PK, defined on the ID column, which is also backed by the unique index OKS_OKS_SERV_AVAILS_U1 and serves as the surrogate identifier. The parent business key is represented by OBJECT1_ID1, OBJECT1_ID2, and JTOT_OBJECT1_CODE; the latter is a foreign key to JTF_OBJECTS_B. Together these identify the object whose availability is being described.

• ID — surrogate primary key (OKS_SERV_AVAILS_PK).
• OBJECT1_ID1, OBJECT1_ID2, JTOT_OBJECT1_CODE — business-key columns identifying the parent object; JTOT_OBJECT1_CODE references JTF_OBJECTS_B.
• START_DATE_ACTIVE, END_DATE_ACTIVE — the effective date range for which the availability record applies.
• GENERAL_YN — flag indicating whether the availability is general rather than specific.
• EXCEPT_OBJECT_TYPE — categorizes the object type subject to an availability exception.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-tenant data segregation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield (DFF) segments for customer-defined extensions.

Common Use Cases and Queries

Typical reporting scenarios include listing active availability windows for a service object, identifying objects with exceptions, and auditing changes to availability configuration. Because the table is date-effective, most queries filter on the active date range.

• Availability lookup: SELECT ID, OBJECT1_ID1, OBJECT1_ID2, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OKS.OKS_SERV_AVAILS WHERE JTOT_OBJECT1_CODE = :code AND SYSDATE BETWEEN START_DATE_ACTIVE AND END_DATE_ACTIVE;
• General versus specific availability: SELECT GENERAL_YN, COUNT(*) FROM OKS.OKS_SERV_AVAILS GROUP BY GENERAL_YN;
• Exception review: join to OKS_SERV_AVAIL_EXCEPTS on SAV_ID to list exception records linked to each availability row.
• Audit trail: order by LAST_UPDATE_DATE using the audit columns to track recent maintenance.

Related Objects

• OKS_SERV_AVAIL_EXCEPTS — child table referencing OKS_SERV_AVAILS via SAV_ID; holds exception details for each availability record.
• JTF_OBJECTS_B — referenced through JTOT_OBJECT1_CODE; provides the base object definition.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; enforces security grouping.

The primary access path is through the OKS_SERV_AVAILS_PK index on ID and the unique index on the same column, with secondary access via JTOT_OBJECT1_CODE. In 12.2.2 the structure is unchanged from 12.1.1 apart from standard column additions maintained by the Oracle Application Object Library audit framework.