Search Results csp_notification_details




Overview
Explore in AI Chat

Overview

The CSP_NOTIFICATION_DETAILS table is a core data object within the Oracle E-Business Suite (EBS) Spares Management (CSP) module. It functions as a detailed transactional log for warehouse notifications, which are critical communications regarding the handling, replenishment, or movement of spare parts inventory. The table stores specific line-item details that instruct warehouse personnel on the exact actions required for each inventory item referenced in a broader notification header. Its primary role is to bridge high-level notification instructions with executable tasks for individual stock-keeping units, ensuring accurate fulfillment of spares logistics processes.

Key Information Stored

Each record in CSP_NOTIFICATION_DETAILS corresponds to a single inventory item action within a notification. The table's structure is defined by its primary and foreign keys, which enforce data integrity and establish critical relationships. The primary identifier is the NOTIFICATION_DETAIL_ID. The NOTIFICATION_ID column is a foreign key that links the detail line to its parent record in the CSP_NOTIFICATIONS table, grouping all actions for a single notification event. For inventory identification, the table uses INVENTORY_ITEM_ID and SOURCE_ORGANIZATION_ID, which together form a foreign key to the MTL_SYSTEM_ITEMS_B table, precisely identifying the spare part and its sourcing inventory organization. While the provided metadata does not list all columns, typical detail tables in this context would also store quantities, unit of measure, suggested sourcing subinventory or locator, and status flags for the proposed action.

Common Use Cases and Queries

This table is central to operational reporting and process execution in spares management. Common use cases include generating pick lists for warehouse personnel, analyzing notification fulfillment rates, and auditing part movement history. A typical query would join this table to its parent and item master to create a detailed notification report. For example:

  • Detail Line Report: SELECT cnd.notification_detail_id, cn.notification_number, msi.segment1 item_code, cnd.quantity FROM csp_notification_details cnd JOIN csp_notifications cn ON cnd.notification_id = cn.notification_id JOIN mtl_system_items_b msi ON cnd.inventory_item_id = msi.inventory_item_id AND cnd.source_organization_id = msi.organization_id WHERE cn.status = 'OPEN';
  • Process Integration: Data from this table is often consumed by subsequent warehouse management or inventory transaction processes to execute the physical movement of goods, such as a transfer to a service depot or a replenishment order.

Related Objects

The CSP_NOTIFICATION_DETAILS table exists within a tightly integrated schema. Its most critical relationships are enforced through foreign key constraints, as documented in the ETRM.

  • CSP_NOTIFICATIONS: This is the parent header table. Every record in CSP_NOTIFICATION_DETAILS must reference a valid NOTIFICATION_ID in CSP_NOTIFICATIONS, defining the overarching notification event.
  • MTL_SYSTEM_ITEMS_B: The standard Oracle Inventory table for item definitions. The foreign key on INVENTORY_ITEM_ID and SOURCE_ORGANIZATION_ID ensures that every detail line references a valid item in the specified sourcing organization.
  • CSP_NOTIFICATION_DETAILS_PK1: The primary key constraint on NOTIFICATION_DETAIL_ID, guaranteeing each detail line is uniquely identifiable.