Results for “exception_detail_id”

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

Overview

The ISC_DBI_EXCEPTION_DETAILS_F table belongs to the ISC (Supply Chain Intelligence) product family, a module designated as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. In legacy implementations where Supply Chain Intelligence was deployed, this table served as the persistent store for exception detail records generated by the Daily Business Intelligence (DBI) exception reporting engine. Exception records represent deviations from planned or expected supply chain conditions — for example, inventory shortfalls, supplier performance variances, or resource capacity breaches — that warrant managerial attention.

The ETRM metadata classifies this object heuristically as standalone in the Data Vault model. This is a modeling suggestion: although the table carries a foreign key to BOM_DEPARTMENTS, it does not participate in a dense hub-and-link constellation, so treating it as an independent hub with a small satellite for descriptive attributes is reasonable. The physical table is owned by the ISC schema and contains 17 documented columns in the 12.1.1 release.

Because the module is obsolete, the object is documented as "Not implemented in this database" in current 12.2.2 environments. Organizations that have migrated away from Supply Chain Intelligence will not find this table populated, and it should be considered a candidate for archival or removal during upgrade planning.

Key Information Stored

The most significant columns capture the identity, contextual dimensions, and quantitative measures of each flagged exception:

• EXCEPTION_DETAIL_ID — the surrogate primary key uniquely identifying each exception detail row.
• PLAN_ID — identifies the planning run or DBI plan instance that produced the exception, linking the record to its analytical context.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, indicating the organizational department accountable for or affected by the exception.
• ORGANIZATION_ID — the inventory organization in which the exception condition was detected.
• RESOURCE_ID — the resource (machine, labor, or supplier resource) associated with the exception.
• SR_INVENTORY_ITEM_ID — the sourced inventory item relevant to the exception condition.
• SR_SUPPLIER_ID and SR_SUPPLIER_SITE_ID — the supplier and supplier site tied to sourcing-related exceptions.
• EXCEPTION_TYPE — a coded value classifying the nature of the deviation, driving downstream reporting and drill-down logic.
• NUMBER1 and NUMBER2 — generic numeric measure columns holding the actual, threshold, or variance values that triggered the exception.
• ORGANIZATION_TYPE — indicates the operational category of the organization context (for example, manufacturing or distribution).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking record lifecycle and the last modifying session.

Business-key candidates typically center on the combination of PLAN_ID, EXCEPTION_DETAIL_ID, and EXCEPTION_TYPE, though the documented metadata identifies only EXCEPTION_DETAIL_ID as the reliable unique identifier.

Common Use Cases and Queries

Historical reporting and audit reconstruction are the primary scenarios for querying this table. A typical pattern joins exception details to departments and organizations to produce exception summaries by department:

• Exception dashboards: Aggregate counts by EXCEPTION_TYPE and ORGANIZATION_ID to reproduce the original DBI alert volumes.
• Drill-down analysis: Filter by PLAN_ID to trace which planning runs generated the highest exception density.
• Supplier performance review: Join SR_SUPPLIER_ID and SR_SUPPLIER_SITE_ID to supplier master tables to attribute exceptions to specific vendors.
• Departmental accountability: Join DEPARTMENT_ID to BOM_DEPARTMENTS to route exception reviews to responsible managers.
• Trend analysis: Group by CREATION_DATE to chart exception frequency over time and validate historical KPI trends.

A representative query selects EXCEPTION_TYPE, COUNT(*), and SUM(NUMBER1) grouped by ORGANIZATION_ID and PLAN_ID, restricted to a date range on CREATION_DATE.

Related Objects

The FK relationship metadata identifies the following dependent and referencing objects as most significant:

• BOM_DEPARTMENTS — referenced via DEPARTMENT_ID; supplies the department name and hierarchy for accountability reporting.
• ISC_DBI_EXCEPTION_DETAILS (historical or mirrored view/table structures) — companion objects in the ISC schema providing summary or staged exception data.
• ISC_DBI_PLANS or equivalent planning header tables — referenced conceptually through PLAN_ID to identify the originating collection run.
• MTL_SYSTEM_ITEMS_B — joined through SR_INVENTORY_ITEM_ID to resolve item descriptions and categories.
• PO_VENDORS / PO_VENDOR_SITES_ALL — joined through SR_SUPPLIER_ID and SR_SUPPLIER_SITE_ID for supplier attribution.
• ORG_ORGANIZATION_DEFINITIONS — joined through ORGANIZATION_ID to resolve organization names for reporting.

Because the module is obsolete, no active APIs or public interfaces depend on this table in supported EBS 12.2.2 deployments; it remains relevant only for legacy data archival and historical audit queries.