Results for “csp_notification_details”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSP_NOTIFICATION_DETAILS is a transaction-detail table in the CSP (Spares Management) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to hold the details on how to handle a warehouse notification. Where the parent CSP_NOTIFICATIONS record captures the notification event itself, CSP_NOTIFICATION_DETAILS stores one row per item and source context, describing available quantity, ordering timing, and supply source so that planners and the notification engine can act on each line.
The table resides in the CSP schema and is physically documented with 32 columns in ETRM 12.2.2. Its primary key is CSP_NOTIFICATION_DETAILS_PK1, defined on the single column NOTIFICATION_DETAIL_ID. Heuristically, the mined foreign-key pattern classifies this object as a link in a Data Vault sense: it connects a notification (CSP_NOTIFICATIONS) to an inventory item (MTL_SYSTEM_ITEMS_B) and to a security context (FND_SECURITY_GROUPS), rather than functioning as a standalone hub or a pure descriptive satellite.
Key Information Stored
The surrogate primary key is NOTIFICATION_DETAIL_ID. The principal business-key candidates are the composite of NOTIFICATION_ID plus INVENTORY_ITEM_ID plus SOURCE_ORGANIZATION_ID, which together identify a unique notification line for a given item and source organization.
- NOTIFICATION_ID — foreign key to CSP_NOTIFICATIONS; ties the detail line to its parent notification.
- INVENTORY_ITEM_ID and SOURCE_ORGANIZATION_ID — foreign key to MTL_SYSTEM_ITEMS_B, identifying the item and the organization it is sourced from.
- AVAILABLE_QUANTITY — the quantity available for handling the notification line.
- ORDER_BY_DATE — the date by which the item should be ordered, driving planning and replenishment actions.
- SOURCE_TYPE, SOURCE_SUBINVENTORY — the type and subinventory of the supply source.
- ORDER_NUMBER — the associated order identifier for the line.
- REPAIR_SUPPLIER_ID — the supplier associated with repair activity on the line.
- SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security partitioning.
Standard EBS audit columns are also present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus the fifteen ATTRIBUTE columns and ATTRIBUTE_CATEGORY for extensibility.
Common Use Cases and Queries
Planners and support teams use this table to inspect how a given warehouse notification is decomposed into item-level handling instructions. A frequent pattern joins the parent notification to the detail lines and item master:
- Listing all detail lines for a notification:
SELECT NOTIFICATION_DETAIL_ID, INVENTORY_ITEM_ID, AVAILABLE_QUANTITY, ORDER_BY_DATE FROM CSP_NOTIFICATION_DETAILS WHERE NOTIFICATION_ID = :p_id; - Reporting notification demand by item and source org, aggregating AVAILABLE_QUANTITY grouped by INVENTORY_ITEM_ID and SOURCE_ORGANIZATION_ID.
- Identifying lines approaching their ORDER_BY_DATE for replenishment follow-up.
- Joining to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and SOURCE_ORGANIZATION_ID to retrieve item descriptions and organization context.
Because the table is security-grouped, any ad-hoc query should respect SECURITY_GROUP_ID filters consistent with the user's access.
Related Objects
The following objects are the most significant in relation to CSP_NOTIFICATION_DETAILS, based on the documented foreign-key structure:
- CSP_NOTIFICATIONS — parent table joined on CSP_NOTIFICATION_DETAILS.NOTIFICATION_ID = CSP_NOTIFICATIONS.NOTIFICATION_ID.
- MTL_SYSTEM_ITEMS_B — item master joined on INVENTORY_ITEM_ID and SOURCE_ORGANIZATION_ID.
- FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for access partitioning.
- Standard EBS audit and multi-org views over CSP tables that consume the audit columns and ORG context.
- CSP Spares Management notification and planning concurrent programs that read these detail rows to drive replenishment and repair actions.
Together these relationships establish CSP_NOTIFICATION_DETAILS as the operational detail layer linking notifications, inventory items, and security context within Oracle Spares Management.
-
Details on how to handle a warehouse notification.
-
Details on how to handle a warehouse notification.
-
Lists notification recommendations
APPS.CSP_NOTIFICATION_DETAILS_V·↳ CSP_NOTIFICATION_DETAILS·↳ CS_STD·↳ FND_GLOBAL·Explore CSP module →
-
Lists notification recommendations
APPS.CSP_NOTIFICATION_DETAILS_V·↳ CSP_NOTIFICATION_DETAILS·↳ CS_STD·↳ FND_GLOBAL·Explore CSP module →
-
View: CSP_MINMAX_NOTIFS_V 12.1.1
Lists warehouse notifications
APPS.CSP_MINMAX_NOTIFS_V·↳ CSP_NOTIFICATIONS·↳ CSP_NOTIFICATION_DETAILS·↳ CST_ITEM_COSTS_FOR_GL_VIEW·Explore CSP module →
-
View: CSP_MINMAX_NOTIFS_V 12.2.2
Lists warehouse notifications
APPS.CSP_MINMAX_NOTIFS_V·↳ CSP_NOTIFICATIONS·↳ CSP_NOTIFICATION_DETAILS·↳ CST_ITEM_COSTS_FOR_GL_VIEW·Explore CSP module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2