Results for “sav_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKS_SERV_AVAIL_EXCEPTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKS (Service Contracts) product family. The view exposes the contents of the service availability exception table, which stores records that define exceptions to standard service availability rules for a given serviced object or item. In EBS 12.1.1 and 12.2.2 this view is registered as VALID and is intended purely as a read layer: it does not itself persist data, but projects the columns of the underlying exception entity so that concurrent programs, forms, OAF pages, and external integrations can query availability exceptions without directly touching the base table. Because the view follows the standard EBS naming convention for a table-backed view (the base table name plus a "_V" suffix), it preserves the same column names and data types as the underlying entity, making it interchangeable with a direct table query while still insulating callers from physical storage changes. The presence of the MANUFACTURING_ORG_ID column links each exception row to a specific manufacturing organization, which is significant in multi-org enabled EBS installations where service applicability can vary by inventory organization.

Underlying Base Objects

According to the documented view text, OKS_SERV_AVAIL_EXCEPTS_V is defined by a single-table SELECT over OKS_SERV_AVAIL_EXCEPTS, which is surfaced in the APPS schema through the synonym of the same name. The view's FROM clause references this base object with the alias SAXB, and every projected column is qualified with that alias, confirming a one-to-one mapping between view columns and base table columns with no joins, unions, aggregations, or filter predicates. This means row cardinality and row ordering characteristics are inherited directly from OKS_SERV_AVAIL_EXCEPTS. The associated parent entity, OKS_SERVICE_AVAILABILITIES, is described in the ETRM metadata as the subject of the view, providing the higher-level availability definition to which individual exception rows (identified by SAV_ID) belong. In 12.2.2 the referenced base object is documented as OKS_SERV_AVAIL_EXCEPTS (SYNONYM), reflecting the standard APPS synonym layering used across the EBS data model.

Key Columns

• ROW_ID — The base table ROWID, used by Oracle Forms and OAF for row identification and optimistic locking.
• ID — Primary identifier of the exception record.
• SAV_ID — Foreign key to the parent service availability definition, linking each exception to its governing availability rule.
• OBJECT1_ID1 / OBJECT1_ID2 — Key components identifying the serviced object or item to which the exception applies.
• JTOT_OBJECT1_CODE — The object type code used by the JTOT (Journey/Total) object framework to interpret OBJECT1_ID1 and OBJECT1_ID2.
• MANUFACTURING_ORG_ID — The manufacturing/inventory organization for which the exception is defined; this is the column most commonly searched when availability exceptions must be segregated by organization.
• REVISION_LOW / REVISION_HIGH — The revision range over which the exception applies, supporting revision-specific availability rules.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date window of the exception.
• OBJECT_VERSION_NUMBER — Optimistic locking and change-detection counter.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments for customer-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS Who-column audit trail.

Common Use Cases and Queries

Typical usage includes diagnosing why a serviced item is treated as unavailable or available in a given organization, validating exception coverage before contract entitlement checks, and extracting exception data for integration or reconciliation reporting. The following query lists exception records for a specific manufacturing organization:

SELECT id, sav_id, object1_id1, object1_id2,
       revision_low, revision_high,
       start_date_active, end_date_active
FROM   apps.oks_serv_avail_excepts_v
WHERE  manufacturing_org_id = :p_org_id
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE);

To join exceptions back to their parent availability definitions, callers can relate SAV_ID to the corresponding availability identifier in OKS_SERVICE_AVAILABILITIES, producing a combined view of availability rules and their exceptions. Because the view applies no filtering, WHERE clauses on date, organization, or revision must be supplied explicitly by the reporting layer to avoid returning the complete exception set.